Cisco routers do not send very many traps, but there are literally hundreds
of syslog messages that you may want to consider.
Some other traps to consider:
Cold start
Link down/up
reload (enterprise specific #0)
You can also process the syslog messages in your ruleset(s) if you configure
the routers to generate a trap for a syslog message. All syslog messages
will be sent to NetView as enterprise specific trap #1 under the enterprise
1.3.6.1.4.1.9.9.41.2, which is the ciscoSyslogMIBNotification enterprise.
Your ruleset will basically have to parse each trap to determine what the
syslog message is, and then take the appropriate actions. We have some
rulesets that do the parsing, and then use the snmptrap command to generate
"user-defined" traps with more meaningful message text. We have added a
bunch of traps to NetView's event configuration using our own enterprise ID.
The user-defined traps can be viewed in the Event Log, and also forwarded to
TEC for additional correlation, and other actions.
-----Original Message-----
From: Gord Michaels [SMTP:gord_michaels@HOTMAIL.COM]
Sent: Tuesday, September 14, 1999 14:15
To: NV-L@UCSBVM.UCSB.EDU
Subject: Cisco Router Ruleset...
Hello All.
I am about to start building a Cisco Router ruleset. We have Cisco
7507,
4700, 2515. with T1 connections, etc.
This is my first attempt at using the Ruleset Editor. Up until now,
we have
just used Netview for Status Monitoring mostly.
I have determined that the following events/traps will be applicable
to my
Cisco Router ruleset:
IBM_NVNDWN_EV - tell me if the node goes down.
IBM_NVIDWN_EV - tell me if an interface on the router goes down.
Cisco_Auth_Failure - authentication failure.
But, I was wondering if anyone knows what other traps or thresholds
I should
be interested in seeing and taking action upon in the world of Cisco
routers??
Any advice appreciated.
Sincerely,
Gord.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
|