PEGASUS-LEAN-TRAP-MIB

All MIBs › PEGASUS-LEAN-TRAP-MIB

Organization: Schmid Telecom, Zurich

Last Updated: 2005-02-02

Category: Optical Networking

Description: Defines lean SNMP trap notifications for the Schmid Telecom Pegasus SDH/PDH microwave radio system.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is PEGASUS-LEAN-TRAP-MIB?

PEGASUS-LEAN-TRAP-MIB is a vendor-specific companion notification module from Schmid Telecom (Zurich), not an RFC standard, that the module identity pegasusLeanTrapModule describes as splitting out the notification types of the base PEGASUS-MIB (imported via pegasusMibModule) for their Pegasus SDSL access system. It defines a single generic pegasusAlarm NOTIFICATION-TYPE carrying sender, senderObjectName, and senderDescription (identifying the affected DSL line card, DSL link, IAD, or V5 interface), together with a large probableCause enumeration (lossOfSignal, dslLoswFailure, alarmIndicationSignal, dataswitchPsu1Fail, deviceFailure, and dozens more) and a perceivedSeverity of critical, major, minor, warning, cleared, or indeterminate. Because the same trap type reports both the raising and clearing of a condition, it is deployed alongside PEGASUS-MIB to give a compact alarm feed for Pegasus SDSL line cards, data switches, and V5 interfaces without requiring a full MIB walk. Administrators can download the PEGASUS-LEAN-TRAP-MIB file to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PEGASUS-LEAN-TRAP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Schmid Telecom Pegasus SDSL access system (line cards, IADs, V5 interfaces)

Monitoring Examples

An operator subscribes to pegasusAlarm traps and inspects the probableCause and perceivedSeverity varbinds for each sender; a trap with sender dslInterfaceAvailabilityStatus, probableCause dslLoswFailure, and perceivedSeverity minor (rather than cleared) indicates an ongoing loss-of-synchronization-word condition on that DSL line card interface.

What Can Be Monitored

pegasusAlarm notifications (combined raise/clear alarm events)
probableCause enumeration (e.g. lossOfSignal, dslLoswFailure, alarmIndicationSignal, deviceFailure, dataswitchPsu1Fail)
perceivedSeverity (critical, major, minor, warning, cleared, indeterminate)
sender / senderObjectName / senderDescription (identification of the affected DSL interface, link, card, or V5 interface)

Imported Objects

From PEGASUS-MIB

pegasusMibModule

MODULE-IDENTITY

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString

OIDs

OID symbolic	OID numeric	Type	Access	Description
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.
leanTrapObjects	1.3.6.1.4.1.6368.2.5.1
OID sender	1.3.6.1.4.1.6368.2.5.1.1	OBJECT IDENTIFIER	accessible-for-notify	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.
STR senderObjectName	1.3.6.1.4.1.6368.2.5.1.2	DisplayString	accessible-for-notify	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.
STR senderDescription	1.3.6.1.4.1.6368.2.5.1.3	DisplayString	accessible-for-notify	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
INT probableCause	1.3.6.1.4.1.6368.2.5.1.4	INTEGER	accessible-for-notify
STR probableCauseText	1.3.6.1.4.1.6368.2.5.1.5	DisplayString	accessible-for-notify
INT perceivedSeverity	1.3.6.1.4.1.6368.2.5.1.6	INTEGER	accessible-for-notify
STR perceivedSeverityText	1.3.6.1.4.1.6368.2.5.1.7	DisplayString	accessible-for-notify
leanNotifications	1.3.6.1.4.1.6368.2.5.2
leanTraps	1.3.6.1.4.1.6368.2.5.2.0
NTF 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.

RFC description

Pegasus LEAN trap notification MIB for cluster management and monitoring. Defines SNMP traps and events for distributed system health and status reporting.

Start monitoring Schmid Telecom Pegasus SDSL access system (line cards, IADs, V5 interfaces) - alarm traps with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download PEGASUS-LEAN-TRAP-MIB

What Is PEGASUS-LEAN-TRAP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description