Another update ;) I found that upgrading from 5.0.9 code on the HiperArc to the 5.3.3 allows me to: disable radius auth_fail traps. Turning that off stopped my usrUserManTraps. If someone knows of a way to turn it off on the earlier code for just general knowledge it'd be interesting to know. Anyhow... After upgrading all of my HiperArcs to 5.3.3 (*grumbles something about tcs4.7*) they are all working great, except one chassis. For some reason it keeps sending "ctIncomingConnectionEstablished" and .1.429.1.6.9.1.1.30.1 which my handler can't for some reason translate but I traced .1.429.1.6.9.1.1.30 down to mdmCsCharsLost. Anyhow, here is the info that is being sent to the trap handler: 20021126 1551 SNMP 1.1.1.1 Trap(ctIncomingConnectionEstablished) nmcTrapSequenceNumber.0=1777 nmcStatEventId.0=1777 nmcGmtime.0=1038325859 uchasSlotIndex.1=2 uchasEntityIndex.1=4 uchasEntityObjectID.1=uchasHighDensity24ModemEntity mdmCsCallRefNum.1=16973855 ss7iCfgChassisId.1= usrds0StatSLAPCallID.1=0 20021126 1553 SNMP 1.1.1.1 Trap(ctIncomingConnectionEstablished) nmcTrapSequenceNumber.0=1780 nmcStatEventId.0=1780 nmcGmtime.0=1038326015 uchasSlotIndex.1=2 uchasEntityIndex.1=11 uchasEntityObjectID.1=uchasHighDensity24ModemEntity mdmCsCallRefNum.1=17432612 ss7iCfgChassisId.1= usrds0StatSLAPCallID.1=0 All of the entries seem to be coming from uchasslotindex.1=2 but different entityindecies, which makes it look like it is somehow related to that card, but I do not see anything different about that card than any other. Is there someplace on the hiperarc/hiperdsp or nmc that you can disable this trap? -Trevor
-----Original Message----- From: usr-tc-admin@mailman.xmission.com [mailto:usr-tc- admin@mailman.xmission.com] On Behalf Of Trevor Sent: Thursday, November 21, 2002 10:12 AM To: usr-tc@mailman.xmission.com Subject: RE: [USR-TC] wierd snmp traps
Well, I have a small update to this *grin*. While doing searching through some of the archives, I saw mention of the hiperarc.mib file. I popped that into the trap handler and I've figured out what my " common.2.2-6.1 common.2.2.0-6.1" problems are: usrUserManTraps. It appears these are being generated when authentication fails on the chassis. I have disabled snmp authentication traps on the hiperarc and on the nmc card, but I can force bad authentications from the hiperarc and still get spewed with these traps. I am probably missing another thing to disable but can not figure out what it is.
Thanks for any help! - Trevor