Server diagnostics for "register trap receiver"
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-24-2021 08:05 AM
Hi,
When using XMC to "register trap receiver" on a device it fails with "set failed"
What is the corresponding diagnostics module on the server to be able to see more detail?
thanks,
When using XMC to "register trap receiver" on a device it fails with "set failed"
What is the corresponding diagnostics module on the server to be able to see more detail?
thanks,
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-16-2021 03:32 AM
snmp is used on many platforms => SSH/CLI diagnostic will not help.
Regards
Zdeněk Pala
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-15-2021 03:09 AM
Removing old config for the trap receiver worked. Thanks @Ludovico Stevens
Unfortunately setting the server diagnostics telnet/ssh to verbose did not give me any information as to what was going wrong.​
Unfortunately setting the server diagnostics telnet/ssh to verbose did not give me any information as to what was going wrong.​
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-30-2021 03:05 AM
I've noticed that the trap registration from XMC/XIQ-SE can fail if the switch already has partial SNMP trap config (e.g. someone tried to add it via CLI). Best is to clean out the snmp trap receiver config on the switch, and then let XMC/XIQ-SE do the config.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-29-2021 03:32 PM
Hello,
I'd start with Diagnostics --> Server --> Server Diagnostics
Set "Telnet/SSH Command Shell to "Verbose", hit OK and try to registration trap receiver.
At least you'll be able to see if the server was able to SSH in and see what commands were ran/failed.
Thanks
-Ryan
I'd start with Diagnostics --> Server --> Server Diagnostics
Set "Telnet/SSH Command Shell to "Verbose", hit OK and try to registration trap receiver.
At least you'll be able to see if the server was able to SSH in and see what commands were ran/failed.
Thanks
-Ryan
