cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4373
Views
0
Helpful
8
Replies

coldStart warmStart syslog and traps

yjdabear
VIP Alumni
VIP Alumni

I still don't know how to make CatOS 7.3 send coldStart and warmStart SNMP traps, after reading this doc.

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_configuration_example09186a0080094aa1.shtml

I saw a warmStart in "show log" on the switch but no SNMP trap was sent, and neither was the syslog message received on the syslog server.

syslog.conf

local7.info /var/log/local7info.log

local6.info /var/log/local6info.log

local5.warn /var/log/local5warn.log

local0.info /var/log/local0info.log

local2.info /var/log/local2info.log

switch config

set snmp rmon enable

set snmp trap enable module

set snmp trap enable chassis

set snmp trap enable bridge

set snmp trap enable repeater

set snmp trap enable vtp

set snmp trap enable auth

set logging console disable

set logging server enable

set logging server 10.26.100.2

set logging level cdp 5 default

set logging level earl 5 default

set logging level fddi 5 default

set logging level ip 4 default

set logging level pruning 5 default

set logging level snmp 5 default

set logging level spantree 5 default

set logging level sys 6 default

set logging level tac 5 default

set logging level tcp 5 default

set logging level telnet 5 default

set logging level tftp 5 default

set logging level vtp 5 default

set logging level vmps 5 default

set logging level kernel 4 default

set logging level filesys 5 default

set logging level drip 5 default

set logging level protfilt 5 default

set logging level security 5 default

set logging level radius 5 default

set logging level udld 5 default

set logging level gvrp 5 default

8 Replies 8

steve.busby
Level 5
Level 5

From your link above, you need to add the trap receiver in your switch config:

How Do I Configure the SNMP Trap Receiver on the Switch?

Issue the command set snmp trap host string .

Note: The command syntax includes:

host -IP address or IP alias of the system

to receive SNMP traps.

string -Community string to use in order to send

authentication traps.

Here is an example:

6509 (enable) set snmp trap 1.1.1.1 public

SNMP trap receiver added.

Issue the show snmp command in order to verify the addition of this set snmp trap statement.

HTH

Steve

Thanks. But the trap receiver is configured, I just left it out when I posted:

set snmp trap enable module

set snmp trap enable chassis

set snmp trap enable bridge

set snmp trap enable repeater

set snmp trap enable vtp

set snmp trap enable auth

set snmp trap 10.153.10.5 public

set snmp trap 10.253.10.6 public

Also, looking at it again, I'm confused whether the following meant the switch sent an SNMP trap or syslog message or both.

2005 Nov 01 13:53:25 est -05:00 %SNMP-5-WARMSTART:Warm Start Trap

Looks like a trap was sent. Do you have any ACLs or firewalls between your switch and the trap receiver server? Anyway to put a sniffer in front of the server to see if the traps are making it that far?

There's no ACL or firewall obstacle in-between. The NMS server in fact received two traps about two line cards failing to come online after the warmStart, but nada about the warmStart itself, in either syslog or trap log.

On CatOS you may generate the SNMP warmStart by issuing the command:

test snmp trap 1

To trigger a coldStart trap:

test snmp trap 0

The traps at the receiver would look something like this:

Nov 5 08:02:48 nms-server2 snmptrapd[83484]: 2005-11-05 08:02:48 14.32.6.12 [14.32.6.12] (via UDP: [14.32.6.12]:49608) TRAP, SNMP v1, community public CISCO-STACK-MIB::wsc6506sysID Warm Start Trap (0) Uptime: 83 days, 15:38:40.87

Nov 5 08:03:22 nms-server2 snmptrapd[83484]: 2005-11-05 08:03:22 14.32.6.12 [14.32.6.12] (via UDP: [14.32.6.12]:49608) TRAP, SNMP v1, community public CISCO-STACK-MIB::wsc6506sysID Cold Start Trap (0) Uptime: 83 days, 15:39:14.72

Very interesting! I sent one of each. The strange thing is neither gets logged in "show logging buffer"

on the switch. I suppose maybe they shouldn't. I do see both of them on the NMS server. I still wonder why the real one (warmStart) showed no trace on the NMS whatsoever.

They wouldn't show up in "show logging buffer"

My guess is that there was no ip connectivity between the switch and the trap listener, and that is why the traps were not received

Good point. That must be why.

Review Cisco Networking for a $25 gift card