Page 2 of 2
Re: Network Switch Configuration issue
Posted: Tue Nov 10, 2015 12:45 am
by raamardhani7
hsmith wrote:When you use single quotes, you don't need to escape anything.
This command worked, correct? snmpwalk -v 3 -c public -u 'fslsnmpusr' -a SHA -A 'AuthPass' -x DES -X 'PrivPass' 172.31.0.10
Hi Smith,
snmpwalk is working flawless from the server, but when trying to configure from Portal using Network Switch / Router Monitoring Wizard. I am facing the below error:
Code: Select all
Bandwidth and Port Status
No ports were detected on the switch. Possible reasons for this include:
The switch is currently down
The switch does not exist at the address you specified
SNMP support on the switch is disabled
Troubleshooting Tip:
If you keep experiencing problems with the switch wizard scan, login to the Nagios XI server as the root user and execute the following command:
/usr/bin/cfgmaker --show-op-down --noreversedns --zero-speed '100000000' --enablesnmpv3 --snmp-options=:::::3 --username='fslsnmpusr' --authprotocol='sha' --authpassword='AuthPass' --privprotocol='des' --privpassword='PrivPass' --contextengineid=0 '172.31.0.10'
Re: Network Switch Configuration issue
Posted: Tue Nov 10, 2015 11:42 am
by ssax
Please let us know what special characters (meaning not letters or numbers) your passwords are using so that we can troubleshoot further.
Thank you
Re: Network Switch Configuration issue
Posted: Wed Nov 11, 2015 8:55 am
by raamardhani7
ssax wrote:Please let us know what special characters (meaning not letters or numbers) your passwords are using so that we can troubleshoot further.
Thank you
Password has ! and & in it.
Re: Network Switch Configuration issue
Posted: Wed Nov 11, 2015 11:41 am
by jdalrymple
I don't expect that this will work with the wizard in its current state. I ran into a similar issue using the SNMP wizard for Linux and it resulted in a feature request allowing us to use user defined macros - a feature request yet to be implemented. For reference I'll link this thread to that FR - ID 6739.
In the meantime - just for testing purposes, can you verify that the special characters are indeed the problem by creating a set of creds that don't use the special characters? I'd hate to waste a ton of yours and our time trying to debug inputting those characters without for sure knowing that's the problem.