PEGASUS-LEAN-TRAP-MIB

File: PEGASUS-LEAN-TRAP-MIB.mib (14583 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC PEGASUS-MIB

Imported symbols

MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE
DisplayString pegasusMibModule

Defined Values

pegasusLeanTrapModule 1.3.6.1.4.1.6368.2.5
Pegasus is an SDSL system manufactured by Schmid Telecom Zurich. The information base is defined in PEGASUS-MIB. This MIB singles out the definitions of notification types from that MIB. This allows us to keep the base MIB clearer, and also to have alternative sets of notifications as separate MIBs. The notification types defined in this module are centered around the idea of having a minimal set of notification types, and add the information to the varbindings list of the notification. Here are some examples. The first two were caused by interrupting the DSL line of an running Iad (DSL link and card both unlocked). The third and fourth are generated when the DSL line is restored. sysUpTime.0 0:0:42:36.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:36.22 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity minor perceivedSeverityText MINOR sysUpTime.0 0:0:42:56.21 snmpTrapOID.0 pegasusAlarm sender dslInterfaceAvailabilityStatus.5.1.ltu senderObjectName LineCard:DSLInterfaceId=LTU,DSLLinkId=0,slotId=5 senderDescription dslInterface 5.1.ltu probableCause dslLoswFailure probableCauseText DSL_LOSW_FAILURE perceivedSeverity cleared perceivedSeverityText CLEARED sysUpTime.0 0:0:42:59.21 snmpTrapOID.0 pegasusAlarm sender dslLinkActiveLoop.5.1 senderObjectName LineCard:DSLLinkId=0,slotId=5 senderDescription dslLink 5.1 probableCause dslUserService probableCauseText DSL_USER_SERVICE perceivedSeverity cleared perceivedSeverityText CLEARED Note - If the Dsl link (or the DSL card) is locked, the traps would have been suppressed. - Two traps are for the DSL interface, with probableCause dslLoswFailure, indicating a condition of loss of synchronization word. The first has perceivedSeverity minor, the second cleared, to show that the condition has ceased and synchronization regained. - Likewise, for the DSL link, a pair of probableCause dslUserService is sent, with severity minor and then again cleared. - The 'affected managed object' is identified by the JMX object name in senderObjectName, and also be the variable name (OID) in sender. The choice of the variable is arbitrary, usually it is the variable with the lowest OID value (the first variable) of tha 'affected managed object'. - The JMX senderObjectName contains a domain (LineCard in our examples), and a list of attributes, e.g. link, interface and slot numbers. The numbers usually start at zero, while the SNMP index values start at one, as is usual with SNMP. To get the SNMP index value, add one to the JMX value.
MODULE-IDENTITY    

leanTrapObjects 1.3.6.1.4.1.6368.2.5.1
OBJECT IDENTIFIER    

leanNotifications 1.3.6.1.4.1.6368.2.5.2
OBJECT IDENTIFIER    

leanTraps 1.3.6.1.4.1.6368.2.5.2.0
OBJECT IDENTIFIER    

sender 1.3.6.1.4.1.6368.2.5.1.1
The 'sender' of the trap is the SNMP object which caused the event or experienced the condition reported by this trap. Typically, the object identifier is the first accessible column of the table entry representing the sender, in the SNMP table representing objects of the senders type.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OBJECT IDENTIFIER  

senderObjectName 1.3.6.1.4.1.6368.2.5.1.2
The canonical form of the JMX object name for the object which sent the trap. This is a compact and unique representation readable both to man and machine.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

senderDescription 1.3.6.1.4.1.6368.2.5.1.3
A description of the sender (affected managed object). The description is human readable, unique, and easy to parse. It consists of a single word describing the kind of sender, optionally followed by a space and a complete SNMP index value for the MIB table related to the sender. The space is omitted if there is no index (pegasusSystem only). The index value is expressed as a sequence of numbers separated by dots. The last number may actually be a string (only with dslInterface, 'ltu' or 'ntu'). The table below contains schematic representations for all types of objects, with ranges for the index values, and examples. In the table, s is a slot number, l a link or trunk number, i an interface number, n a user port number (on the Iad) or a logical comm channel number. dataPort s.l s=1,0
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

probableCause 1.3.6.1.4.1.6368.2.5.1.4
Tok_String
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER disconnectionError(1), communicationError(2), outOfMemory(3), cfgUploadProblem(4), cfgDownloadProblem(5), statusSyncProblem(6), operStateDisabled(7), activeMaintenanceLoop(8), deviceFailure(9), lossOfSignal(10), lossOfFrameAlignement(11), alarmIndicationSignal(12), bitErrorRateToHigh(13), lossOfExternalClock(14), remoteAlarmIndication(15), deviceInactive(16), wrongProgram(17), inTest(18), failed(19), powerOff(20), offLine(21), offDuty(22), dependency(23), degraded(24), notInstalled(25), logFull(26), blocked(27), l1Activation(28), hasLosAtTrefPoint(29), hasL1ActivationFault(30), hasLosAtDigSection(31), iadPowerLoss(32), iadLifeline(33), iadDCContinuity(34), dslConfig(35), dslUserService(36), dslLoopAtt(37), dslLoswFailure(38), dataswitchPsu1Fail(39), dataswitchPsu2Fail(40), dataswitchFanFail(41), dataswitchUrgentExt(42), dataswitchNonurgentExt(43), v5InterfaceIDFailure(44), v5InterfaceProvisMismatch(45), v5LinkIdFailure(46), unsupported2ndV5Card(47), currentLimit(48), watsonDTRFailed(49), softwareMismatch(50), hardwareProblem(51), ethernetIfLinkIntegrityFailed(52), ethernetIfFifoError(53), unknownProbableCause(54), lossOfFrame(55), traceIdMissmatch(56), lossOfMultiframe(57), multiplexSectionRemoteDefectIndication(58), multiplexSectionAlarmIndicationSignal(59), regeneratorSectionTraceIdMismatch(60), outOfLock(61), lossOfPointer(62), remoteDefectIndication(63), payloadLabelMismatch(64), unequipped(65), initFailed(66), watsonRegW2-AlarmA(67), watsonRegW2-AlarmB(68), watsonRegR-LoswFailure(69), watsonRegC-LoswFailure(70), watsonRegR-BerToHigh(71), watsonRegC-BerToHigh(72), watsonTrapPortBindFailed(73), watsonHPOVConnectFailed(74), dslCurrentLimit(75), m16ProgramTransfer(76), writeError(77), maintenance(78), remoteFailureIndication(79), lcasCrcError(80), nonLcasSequenceError(81), rxLowOrderGroupIdMismatch(82), rxHighOrderGroupIdMismatch(83), rxLowOrderDifferentialDelay(84), rxHighOrderDifferentialDelay(85), rxLowOrderDifferentialDelayAllVT(86), rxHighOrderDifferentialDelayAllVT(87), txFifoOverflow(88), rxFifoOverflow(89), emailServiceAlarm(90), licenseMissing(91), licenseInvalid(92), licenseWrongHostId(93), licenseMaxNetworkNodesExceeded(94), alarmFilteringParseError(95), iadNoCOS(96)  

probableCauseText 1.3.6.1.4.1.6368.2.5.1.5
Tok_String
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

perceivedSeverity 1.3.6.1.4.1.6368.2.5.1.6
Tok_String
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  INTEGER critical(1), major(2), minor(3), warning(4), cleared(5), indeterminate(6)  

perceivedSeverityText 1.3.6.1.4.1.6368.2.5.1.7
Tok_String
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  DisplayString  

pegasusAlarm 1.3.6.1.4.1.6368.2.5.2.0.1
The perceivedSeverity changed since the last notification with this probableCause for this sender. If the perceivedSeverity is CLEARED, the alarm condition is no longer present.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE