ayassin

Forgot one point: 1. delete "crypto pki trustpoint" 2. delete the .cer file in nvram 3. then rename the switch to something else 4. then create the ssh key and do a write 5. then rename the switch back to it's original name and "wr" and finish! Then never make ssh generate again on that switch

For some older Cisco Switches e.g. 3550, 3750 cisco names the ssh .cer file like this: hostname#1234.cer When solarwinds comes to this part of the startup-config, it thinks it is at the command prompt and stops at that point (cuts off the rest of the startup-config). When comparing it to the running config, it's allways…

Hi Jiri, it worked, thanks for assistance. Best regards Amir

Hi Jiri, i didn't expect it finding the inventory under reports. I will try it with new discovered devices and give feedback. Thanks Amir

Okay, thank you Jiri, i will open a case, but i'm not very optimistic. Greetz Miro

Hi Jiri, thanks for response, i thought it should be possible to update the inventory from the Orion Web Console, but i can only update the inventory from the Solarwinds Configuration Manager. When i try to update the inventory only from the Web Console there are no interfaces listed Kind regards Amir

Ah hello Jiri, offcourse: after the certificate part there is nothing more, no interfaces etc. the running config is complete 050crypto pki trustpoint TP-self-signed-3583918976 050 crypto pki trustpoint TP-self-signed-3583918976 051 enrollment selfsigned 051 enrollment selfsigned 052 subject-name…

I solved that issue, or better made a workaround. I wasn't able to update the Inventory on the Orion Web Console, but when i started to update the inventory in the SolarWinds Network Configuration Manager it worked. Is there a way to fix this in the Web Console ? Thanks Amir

Do you use X2-10GB-LX4 Tengigabit optics ? If yes, they do have problems with digital optical monitoring. In other words, they do not support it and thats why you get those false warnings. Maybe Solarwinds can fix that by stop monitoring those kind of modules. Have a look here, if your optics are listed: Cisco Digital…

I found it here: SolarWinds Knowledge Base :: What kind of SQL Server licensing does SolarWinds require?

I found the error. The SSH user, which is authenticated over radius, got insufficient rights (Priv 6) to configure the switches. With Priv 15 everything works fine. Thanks Amir

Any Ideas ? Would highly appreciate any suggestions to my question.