Hi,
I had some problems on this as well, you can do that if you set on the
"interface" level that you do not what link up/down traps. Hard to do for
every interface - but
at least you can select which you want. (eg. sending link up/down traps for
trunk's or uplinkports/servers might be usefull). I have written some
scripts which grabs
the link up/down traps and after that asks the switch for the port
description - and send a trap/mail to the administrator.
i have no cisco box atm. but it was something like:
conf t
int fa0/1
snmp? ... no link up/down ....
hope this helps.
*************************************************************
Dietmar Gaulhofer, IBM Österreich
Systems Engineer
ITS - Integrated Technology Services - Unit Austria
Email: Dietmar_Gaulhofer@at.ibm.com
Tel: +43/1/21145-2756
**************************************************************
Jeff Fitzwater <jfitz@princeton.edu>@lists.us.ibm.com on 08.10.2003
15:26:03
Please respond to nv-l@lists.us.ibm.com
Sent by: owner-nv-l-digest@lists.us.ibm.com
To: nv-l@lists.us.ibm.com
cc:
Subject: Re: [nv-l] Cat6509 link down/up trap
"Jorge A. Jiles" wrote:
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
Catilina, in your previous message you mentioned that you were running IOS
NOT catOS so the command to enable TRAPS on the port level is enabled by
default.
If you look at your config it should look someting like the following....
NOTE I HAVE SET MY TRAPS TO "DISABLE FOR THIS PORT TO SHOW YOU THE COMMAND.
IF THEY ARE ENABLED YOU WILL NOT SEE THIS COMMAND. YOU CAN RUN IT WITHOUT
THE "NO" IF IT MAKES YOU FEEL BETTER.
interface GigabitEthernet0/4
switchport access vlan 48
switchport trunk encapsulation dot1q
switchport trunk native vlan 48
switchport mode access
switchport nonegotiate
no ip address
no snmp trap link-status !!!!!!!!!!
The other key here is you are missing the command to send "traps" to the
trap-reciever. You have the command with reciever but you did not add
command to send TRAPS.
It should look like this....
snmp-server host xxx.xxx.xxx.xx1 traps <private community>
snmp-server host xxx.xxx.xxx.xx2 traps <private community>
Jeff Fitzwater
OIT Systems & Networking
Princeton University
|