RE: [nv-l] Cat6509 link down/up trap

[James Shanks <jshanks@us.ibm.com>]

You are laboring under a misconception.   Whether you configure trapd.conf  for these traps or not, has NOTHING to do with whether they arrive in NetView.  If you don't see them, then the switches aren't sending them, or they are being sent to the wrong address..   When they aren't configured you still get the trap only it says "No FMT Found" in front of it.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

"Jorge A. Jiles" <Jorge.Jiles@ualberta.ca> Sent by: owner-nv-l-digest@lists.us.ibm.com 10/07/2003 04:14 PM Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Subject:        RE: [nv-l] Cat6509 link down/up trap

Yes, they all have most common traps enabled. Again I want to make sure
that Netview's trapd.conf is correct before blaming the switches'
configuration.

Catalina, here is the configuration of one of the switches. According to
Cisco documentation (see below) the command snmp-server enable traps snmp
should enable authentication failure, warmStart, linkUp, and linkDown
traps, but I only see authentication and warmstart traps getting configure.
I might have to call Cisco on this.....  

>From Cisco Information page:
The following example sends the RFC 1157 authentication failure, warmStart,
linkUp, and linkDown SNMP traps to address 172.30.2.160: 

snmp-server enable traps snmp 
snmp-server host 172.30.2.160 public snmp 


My switch snmp confifuration...

snmp-server community xxxxxx RW 1
snmp-server community xxxxxx RO 1
snmp-server trap-source Loopback0
snmp-server location xxx 
snmp-server contact xxxxxxxxxx
snmp-server enable traps snmp authentication warmstart (note no linkdown/up
traps)
snmp-server enable traps chassis
snmp-server enable traps module
snmp-server enable traps casa
snmp-server enable traps vtp
snmp-server enable traps slb
snmp-server enable traps hsrp
snmp-server enable traps config
snmp-server enable traps entity
snmp-server enable traps bgp
snmp-server enable traps rsvp
snmp-server enable traps frame-relay
snmp-server enable traps syslog
snmp-server enable traps rtr
snmp-server enable traps dlsw
snmp-server enable traps isdn call-information
snmp-server enable traps isdn layer2
snmp-server host xxx.xxx.xxx.xx1 <private community>
snmp-server host xxx.xxx.xxx.xx2 <private community>


Again, thanks for any information.


At 01:10 PM 10/7/2003 -0500, you wrote:
>Are the Cisco 6509s configured to send out link up/down traps? 
>
>I know that we had to enable these traps on the switches in order for
>Netview to receive the traps..
>
>Catalina
>-----Original Message-----
>From: owner-nv-l-digest@lists.us.ibm.com
>[mailto:owner-nv-l-digest@lists.us.ibm.com] On Behalf Of Jorge A. Jiles
>Sent: Tuesday, October 07, 2003 12:55 PM
>To: nv-l@lists.us.ibm.com
>Subject: [nv-l] Cat6509 link down/up trap
>
>Hello all. Netview 7.1 on Solaris8
>
>I'm not receiving link down/up traps from hour Cisco cat6509's (version
>12.1(11)E1). Bellow is part of the configuration of my trapd.conf under
>/usr/OV/conf/C
>
>I'am asumming that Cisco link down/up traps are generic to all Catalyst
>switches. Do I have to load a particular MIB for Cat6509 link traps?
>
>I want to be sure that Netview is configured properly before checking
>the
>switches configuration again. 
>
>
>Cisco_Link_Down {1.3.6.1.4.1.9} 2 0 A 1 0 "Status Events"
>Cisco_Link_Down trap received from enterprise $E with $# arguments:
>ifIndex=$1;  ifDescr=$2;  ifType=$3;  locIfReason=$4
>SDESC
>This event occurs when the Cisco agent detects an interface has gone
>down.
>linkDown Trap signifies that the sending protocol entity recog
>nizes a failure in one of the communication links represented in the
>agent's configuration.
>EDESC
>Cisco_Link_Up {1.3.6.1.4.1.9} 3 0 A 1 0 "Status Events"
>Cisco_Link_Up trap received from enterprise $E with $# arguments:
>ifIndex=$1;  ifDescr=$2;  ifType=$3;  locIfReason=$4
>SDESC
>This event occurs when the Cisco agent detects an interface has come
>back
>up. linkUp trap signifies that the sending protocol entity reco
>gnizes that one of the communication links represented in the agent's
>configuration has come up.
>EDESC
>
>Thanks for any help.
>
>
>
>Jorge A Jiles
>Network Analyst
>Computing & Network Services
>University of Alberta
>Edmonton, Alberta
>Canada
>
>
>
>
>
>


Jorge A Jiles
Network Analyst
Computing & Network Services
University of Alberta
Edmonton, Alberta
Canada