Status in source: unspecified.
Technical details
{
"smi_kind": "MODULE-IDENTITY",
"definition": [
"pegasusLeanTrapModule",
"MODULE-IDENTITY",
"LAST-UPDATED",
[
"literal",
"223230303530323032303030305a22"
],
"ORGANIZATION",
"\"Schmid Telecom, Zurich\"",
"CONTACT-INFO",
"\"Schmid Telecom AG Binzstrasse 35, CH-8048 Zurich Switzerland Email: xdslsupport@schmid-telecom.ch\"",
"DESCRIPTION",
"\"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.\"",
"REVISION",
[
"literal",
"223230303530323032303030305a22"
],
"DESCRIPTION",
"\"Added new probableCause values.\"",
"REVISION",
[
"literal",
"223230303431323137303030305a22"
],
"DESCRIPTION",
"\"Updated probableCause values.\"",
"REVISION",
[
"literal",
"223230303430333138303030305a22"
],
"DESCRIPTION",
"\"Updated probableCause. Added some new values and modified existing values.\"",
"REVISION",
[
"literal",
"223230303430313135303030305a22"
],
"DESCRIPTION",
"\"Updated probableCause. New value writeError(77).\"",
"REVISION",
[
"literal",
"223230303331313131303030305a22"
],
"DESCRIPTION",
"\"Updated probableCause. New last value is m16ProgramTransfer(76).\"",
"REVISION",
[
"literal",
"223230303330333231303030305a22"
],
"DESCRIPTION",
"\"Appended five new literals into enumeration ProbableCause: - unsupported2ndV5Card(47), - currentLimit(48), - watsonDTRFailed(49), - softwareMismatch(50), - hardwareProblem(51)\"",
"REVISION",
[
"literal",
"223230303230393139303030305a22"
],
"DESCRIPTION",
"\"Inserted four new literals into enumeration ProbableCause: - iadDCContinuity(34), - v5InterfaceIDFailure(44), - v5InterfaceProvisMismatch(45), - v5LinkIdFailure(46) Warning: dslConfig and all other old literals defined after it have changed their ordinal values!\"",
"REVISION",
[
"literal",
"223230303230343235303030305a22"
],
"DESCRIPTION",
"\"Added senderDescription. Renamed 'alarm' to 'pegasusAlarm', to help with name conflicts. Made corresponding changes to trap examples above.\"",
"REVISION",
[
"literal",
"223230303230343032303030305a22"
],
"DESCRIPTION",
"\"Added missing import of DisplayString.\"",
"REVISION",
[
"literal",
"223230303230333134303030305a22"
],
"DESCRIPTION",
"\"Added some trap example dumps and explanation to the module description.\"",
"REVISION",
[
"literal",
"223230303230323138303030305a22"
],
"DESCRIPTION",
"\"The two trap types were collapsed into one. The former changedAlarm is now represented by an 'alarm' with exactly the same parameters. The former newAlarm was used when the perceivedSeverity changed from CLEARED (i.e. alarm not present) to other than cleared. This is now also reported through the single trap type 'alarm'. The senderText variable was removed. Each of sender and senderObjectName alone exactly identifies the object affected, and senderText was redundant.\"",
"REVISION",
[
"literal",
"223230303230323134303030305a22"
],
"DESCRIPTION",
"\"Initial revision.\"",
"::=",
"{",
"pegasusMibModule",
"5",
"}"
],
"syntax_tree": [
[
"LAST-UPDATED",
"200502020000Z"
],
[
"ORGANIZATION",
"Schmid Telecom, Zurich"
],
[
"CONTACT-INFO",
"Schmid Telecom AG Binzstrasse 35, CH-8048 Zurich Switzerland Email: xdslsupport@schmid-telecom.ch"
],
[
"DESCRIPTION",
"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."
],
[
"Revisions",
[
[
"200502020000Z",
[
"DESCRIPTION",
"Added new probableCause values."
]
],
[
"200412170000Z",
[
"DESCRIPTION",
"Updated probableCause values."
]
],
[
"200403180000Z",
[
"DESCRIPTION",
"Updated probableCause. Added some new values and modified existing values."
]
],
[
"200401150000Z",
[
"DESCRIPTION",
"Updated probableCause. New value writeError(77)."
]
],
[
"200311110000Z",
[
"DESCRIPTION",
"Updated probableCause. New last value is m16ProgramTransfer(76)."
]
],
[
"200303210000Z",
[
"DESCRIPTION",
"Appended five new literals into enumeration ProbableCause: - unsupported2ndV5Card(47), - currentLimit(48), - watsonDTRFailed(49), - softwareMismatch(50), - hardwareProblem(51)"
]
],
[
"200209190000Z",
[
"DESCRIPTION",
"Inserted four new literals into enumeration ProbableCause: - iadDCContinuity(34), - v5InterfaceIDFailure(44), - v5InterfaceProvisMismatch(45), - v5LinkIdFailure(46) Warning: dslConfig and all other old literals defined after it have changed their ordinal values!"
]
],
[
"200204250000Z",
[
"DESCRIPTION",
"Added senderDescription. Renamed 'alarm' to 'pegasusAlarm', to help with name conflicts. Made corresponding changes to trap examples above."
]
],
[
"200204020000Z",
[
"DESCRIPTION",
"Added missing import of DisplayString."
]
],
[
"200203140000Z",
[
"DESCRIPTION",
"Added some trap example dumps and explanation to the module description."
]
],
[
"200202180000Z",
[
"DESCRIPTION",
"The two trap types were collapsed into one. The former changedAlarm is now represented by an 'alarm' with exactly the same parameters. The former newAlarm was used when the perceivedSeverity changed from CLEARED (i.e. alarm not present) to other than cleared. This is now also reported through the single trap type 'alarm'. The senderText variable was removed. Each of sender and senderObjectName alone exactly identifies the object affected, and senderText was redundant."
]
],
[
"200202140000Z",
[
"DESCRIPTION",
"Initial revision."
]
]
]
]
]
}