SNMP and port down trap 1

[Microbyte]

Here's sample topology

6500 switch A ---
ServerA< |
6500 switch B ---

Server A is dual-homed with ip address 10.0.0.1 is connected to core 6500 switches armed with HSRP.
ServerA has 2 ethernet ports which share 1 IP address (1 MAC) and has a capability to failover to its redundant port when the primary port fails.
Is there a way to send a SNMP messages when the switchA interface where the serverA is connected to goes offline?

within snmp-server command has similar one that i could find.
it's "link up" and "link down", but it is driven by ip address, not by the switch interface number.

Thanks in advance!

Microbyte

 

[vipergg]

Try "logging event link status default " in global mode.

 

[KiscoKid]

I think if you enable SNMP traps globally as you've done with the snmp-server command and then make sure the interface is enabled with the 'snmp trap link-status' command, that should probably do it.

You can debug it to make sure it works with the command 'debug snmp packets' I think it is. Everytime you pull the plug on the port you've enabled for trapping, it should generated a bunch of debug info if it's working properly.

 

[RookThis]

you can add logging event-link status on the interface as well... and I think snmp trap something on the interface too. I can't remember the syntax

 

[Microbyte]

Thanks for replying.

What is the difference between these two commands?

"snmp-server enable traps linkdown linkup"

and

"logging event link status default"

??

Microbyte

 

[KiscoKid]

logging event link status default" configures the switch to log (i.e. to buffer or syslog etc) whenever a switch port link status changes from up to down and vice versa. The global command as outlined here and above enables this for ALL interfaces. You can also specify it on an interface-by-interface level to minimize the messages seen.

In contrast, the "snmp-server enable traps linkdown linkup" allows the switch to generate a trap alarm to an external SNMP manager (like HP Openview) whenever a port changes state. You have to use this command with the 'snmp-server host' command to specify the IP address of the SNMP manager.

As you may appreciate, the commands are subtly different. One logs the port status changes to whatever logging you have in place (the router itself or a syslog server), the other will force a trap alarm to be generated on a remote SNMP manager.