Why so many commands need to enable MAC notifcation traps?

From: Hobbs (deadheadblues@gmail.com)
Date: Mon Nov 10 2008 - 01:24:59 ARST

I quote from the doccd:

"You enable the MAC address notification feature by using the *mac
address-table notification* command. You must also enable MAC address
notification traps on an interface by using the *snmp trap
mac-notification*interface configuration command and configure the
switch to send MAC address
traps to the NMS by using the *snmp-server enable traps
mac-notification*global configuration command."

So we have the global command "snmp-server enable traps ...."
Then we have the interface command "snmp trap mac-notification"

That's understandable, I guess so we can pull the plug globally be negating
the global command if we want.

But why do we need mac address-table notification?
Does this command do something else besides work for SNMP?
Why have two global commands that are needed to do 1 thing and 1 thing only?

SW2(config)#snmp-server enable traps mac-notification ?
  change Enable SNMP MAC Change traps
  move Enable SNMP MAC Move traps
  threshold Enable SNMP MAC Threshold traps
  <cr>

SW2(config)#mac address-table notification ?
  change Enable/Disable MAC Notification feature on the switch
  mac-move Enable Mac Move Notification
  threshold Configure L2 Table monitoring

Thanks,

reference:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/release/12.2_44_se/command/reference/cli1.html#wpxref72436

Blogs and organic groups at http://www.ccie.net

This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:30 ARST