[nv-l]

Alrighty then,

An indepth question that may be asnwered here (I hope). I am using Alcatel MIBs who only have a SNMPv2 version. I have been able to strip out the traps and load them into xnmtrap. They are pulling the correct information, HOWEVER, what they are pulling is the integer vs. the name of what that integer means. below is the portion of the MIB I am trying to pull. there are actually 6 of them but for brevity I only put these two. in xnmtrap I am getting the actual integer of (2) instead of the statement noChange. Now these MIBs are loaded via xnmloadmib2. When I create the trap for them and use the actual object type in the message line I use healthMonRx Status $1, How does xnmptrap lookup the textual description of the OBJECT-TYPE?

healthMonRxStatus OBJECT-TYPE
SYNTAX INTEGER {
crossedBelowThreshold (1),
noChange (2),
crossedAboveThreshold (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Rx threshold status."
::= { healthTrapInfo 1 }

healthMonRxTxStatus OBJECT-TYPE
SYNTAX INTEGER {
crossedBelowThreshold (1),
noChange (2),
crossedAboveThreshold (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"RxTx threshold status."
::= { healthTrapInfo 2 }

###########################################

Below is the entry in trapd.conf. I am only curious that when trapd runs does it go back and look at the OBJECT-TYPE to define the information that is held in the INTEGER?

healthMonDeviceTrap {1.3.6.1.4.1.6486.800.1.3.2.5} 6 1 A 1 0 "Status Events"
$1 $2 $3 $4 $5 $6 :healthMonRxStatus healthMonRxTxStatus healthMonMemoryStatus
EVENT_CLASS TEC_ITS_BASE
SDESC
Device-level rising/falling threshold crossing trap.
EDESC

Thank you for any help

Chris Petrina