Nortel-MsCarrier-MscPassport-AlarmMIB

All MIBs › Nortel-MsCarrier-MscPassport-AlarmMIB

Category: Alarm & Fault Management, Nortel MsCarrier MscPassport

Description: Provides SNMP management objects for alarm reporting and fault status on Nortel MsCarrier MscPassport mobile carrier switches.

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 Nortel-MsCarrier-MscPassport-AlarmMIB?

This is the central alarm and fault-reporting MIB for the Nortel MSC Passport carrier switch, the mobile-carrier variant of the Magellan Passport platform, aggregating fault reports raised by every other component MIB on the switch. It exposes alarm severity (mscSeverity), alarm type and probable cause (mscAlarmType, mscProbableCause), event timestamp (mscEventTime), active-alarm status, and a real-time notification (mscAlarmTrap) for immediate trap delivery. This module exists explicitly to monitor overall hardware and software fault status: it is the point where administrators see which component (via mscComponentRowPointer/mscComponentName) currently has an active alarm, at what severity, and why, spanning hardware faults, software faults, and threshold conditions anywhere in the switch. It depends heavily on the Passport component-instance model shared across all other Passport MIBs, since every alarm references the alarming component. It is deployed as the central fault-management feed a carrier NOC polls or traps to when monitoring MSC Passport nodes in a mobile network backbone. Engineers can download the Nortel-MsCarrier-MscPassport-AlarmMIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in Nortel-MsCarrier-MscPassport-AlarmMIB. 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

Nortel MSC Passport mobile carrier switch

Monitoring Examples

A NOC monitoring system subscribes to mscAlarmTrap notifications and cross-references mscSeverity, mscAlarmType, and mscProbableCause to prioritize incoming faults, using mscComponentRowPointer/mscComponentName to identify exactly which component raised the alarm. mscActiveListStatus shows whether an alarm is still active or has cleared, and mscEventTime timestamps when it occurred. A surge of high-severity alarms sharing the same mscProbableCause across many components points to a common underlying hardware failure rather than isolated incidents.

What Can Be Monitored

active alarm list
alarm severity
alarm type / probable cause
alarm event timestamp
faulting component identity

Imported Objects

From Nortel-MsCarrier-MscPassport-StandardTextualConventionsMIB

DateAndTime
DisplayString
RowPointer
Unsigned32

From Nortel-MsCarrier-MscPassport-TextualConventionsMIB

AsciiString
DigitString
Hex
HexString

From Nortel-MsCarrier-MscPassport-UsefulDefinitionsMIB

mscPassportMIBs	OBJECT-IDENTITY
mscPassportTraps	OBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
mscAlarmTrap	1.3.6.1.4.1.562.36.2.1.3.2
NTF mscCriticalAlarm	1.3.6.1.4.1.562.36.2.1.3.2.0.1			This trap is used to provide a real time indication of a critical Alarm condition. The variables listed in the VARIABLES clause, defined in the `mscMandatoryAlarmInfo' group are present in all critical alarms. Additional variables as defined in the 'mscOptionalAlarmInfo' group may be included if appropriate.
NTF mscMajorAlarm	1.3.6.1.4.1.562.36.2.1.3.2.0.2			This trap is used to provide a real time indication of a major Alarm condition. The variables listed in the VARIABLES clause, defined in the `mscMandatoryAlarmInfo' group are present in all major alarms. Additional variables as defined in the 'mscOptionalAlarmInfo' group may be included if appropriate.
NTF mscMinorAlarm	1.3.6.1.4.1.562.36.2.1.3.2.0.3			This trap is used to provide a real time indication of a minor Alarm condition. The variables listed in the VARIABLES clause, defined in the `mscMandatoryAlarmInfo' group are present in all minor alarms. Additional variables as defined in the 'mscOptionalAlarmInfo' group may be included if appropriate.
NTF mscWarningAlarm	1.3.6.1.4.1.562.36.2.1.3.2.0.4			This trap is used to provide a real time indication of a warning Alarm condition. The variables listed in the VARIABLES clause, defined in the `mscMandatoryAlarmInfo' group are present in all warning alarms. Additional variables as defined in the 'mscOptionalAlarmInfo' group may be included if appropriate.
NTF mscClearedAlarm	1.3.6.1.4.1.562.36.2.1.3.2.0.5			This trap is used to provide a real time indication of a cleared Alarm. The variables listed in the VARIABLES clause, defined in the `mscMandatoryAlarmInfo' group are present in all cleared alarms. Additional variables as defined in the 'mscOptionalAlarmInfo' group may be included if appropriate.
NTF mscIndeterminateAlarm	1.3.6.1.4.1.562.36.2.1.3.2.0.6			This trap is used to provide a real time indication of an indeterminate Alarm condition. The variables listed in the VARIABLES clause, defined in the `mscMandatoryAlarmInfo' group are present in all indeterminate alarms. Additional variables as defined in the 'mscOptionalAlarmInfo' group may be included if appropriate.
mscMandatoryAlarmInfo	1.3.6.1.4.1.562.36.2.1.3.2.7
NUM mscComponentRowPointer	1.3.6.1.4.1.562.36.2.1.3.2.7.1	RowPointer	not-accessible	A pointer to the RowStatus variable of the component emitting the alarm.
STR mscComponentName	1.3.6.1.4.1.562.36.2.1.3.2.7.2	DisplayString	not-accessible	The textual name of the component emitting the alarm in a format suitable for use in commands entered on the `console'. It includes the name of the node from which the alarm was sent, as specified in `ModuleData nodeName'.
DAT mscEventTime	1.3.6.1.4.1.562.36.2.1.3.2.7.3	DateAndTime	not-accessible	The date and time at which the alarmed event occurred.
INT mscActiveListStatus	1.3.6.1.4.1.562.36.2.1.3.2.7.4	INTEGER	not-accessible	The active alarm list status. This may be used by the Manager to add (on receiving a set) and delete (on receiving a clear) alarms from the alarm displays.
INT mscSeverity	1.3.6.1.4.1.562.36.2.1.3.2.7.5	INTEGER	not-accessible	The severity of the alarm which should indicate what priority that fixing this problem should be given. All values are OSI-defined; refer to CCITT X.733/ISO 10164-4 for a more complete description.
INT mscAlarmType	1.3.6.1.4.1.562.36.2.1.3.2.7.6	INTEGER	not-accessible	The alarm type field as defined by OSI which is used to indicate a broad category of what is wrong. The first 6 values are OSI-defined; refer to CCITT X.733/ISO 10164-4 (for the first 5) and CCITT X.736/ISO 10164-4 (for the last) for a more complete description. The value 'operator' is used when an alarm is issued due to an operator command. The values 'debug' and 'unknown' are for compatibility with older switches and are used for debugging alarms and for those which do not fit any of the above, respectively.
INT mscProbableCause	1.3.6.1.4.1.562.36.2.1.3.2.7.7	INTEGER	not-accessible	The probable cause for the alarm which usually qualifies the Alarm Type field. Most values are OSI-defined; refer refer to CCITT X.733 and X.736 (ISO 10164-4 and 10164-7) for a more complete description.
STR mscNtpIndex	1.3.6.1.4.1.562.36.2.1.3.2.7.8	DigitString	not-accessible	An 8-digit code which is an index into an NTP to provide more description of the alarm and possible actions to take. The first 4 digits indicate a 'group' of alarms (belonging to a particular subsystem or component, etc.). The last 4 digits are a subindex arbitrarily assigned by the application which is responsible for them.
STR mscCommentData	1.3.6.1.4.1.562.36.2.1.3.2.7.9	AsciiString	not-accessible	Additional textual information for the network operator to use. It contains only ASCII characters. Note: The total number of bytes in mscCommentData, mscOperatorData, and mscInternalData may not exceed 750 bytes.
mscOptionalAlarmInfo	1.3.6.1.4.1.562.36.2.1.3.2.8
HEX mscNotificationID	1.3.6.1.4.1.562.36.2.1.3.2.8.1	Hex	not-accessible	The notification Id of the alarm. The high-order byte is the card number of the card from which this alarm originated. The low-order 24 bits contain a sequence number which increases each time an alarm is generated. Thus, this id provides a simple way of uniquely identifying an alarm as well as the order in which alarms are generated on a card. For cross-card ordering, one would have to look at the time stamp (see dateAndTime).
NUM mscLpForHierClear	1.3.6.1.4.1.562.36.2.1.3.2.8.2	RowPointer	not-accessible	A pointer to the RowStatus variable of the Logical Processor the component generating the alarm is running on. A component generating an Alarm with `mscActiveListStatus = set' can include this variable in the Alarm. If the identified Logical Processor generates a Hierarchical Clear Alarm, then it will clear the Set Alarm.
STR mscOperatorData	1.3.6.1.4.1.562.36.2.1.3.2.8.3	HexString	not-accessible	Additional hexadecimal information for the network operator to use. Note: The total number of bytes in mscCommentData, mscOperatorData, and mscInternalData may not exceed 750 bytes.
STR mscPid	1.3.6.1.4.1.562.36.2.1.3.2.8.4	DisplayString	not-accessible	A string representation of the internal process id (Pid) of the process which generated the alarm (for internal use only). Note that it may or may not map to the mscComponentName field.
STR mscFileName	1.3.6.1.4.1.562.36.2.1.3.2.8.5	DisplayString	not-accessible	An internal filename (for internal use only).
U32 mscFileLineNumber	1.3.6.1.4.1.562.36.2.1.3.2.8.6	Unsigned32	not-accessible	An internal line number in the file (see filename) referred to above (for internal use only).
STR mscFileVersion	1.3.6.1.4.1.562.36.2.1.3.2.8.7	DisplayString	not-accessible	A version indicator of the file (filename) referred to above (for internal use only).
STR mscInternalData	1.3.6.1.4.1.562.36.2.1.3.2.8.8	HexString	not-accessible	An additional internal hexadecimal information for internal use only. Note: The total number of bytes in comment, operator, and internal data may not exceed 750 bytes.
mscProvisionalAlarmInfo	1.3.6.1.4.1.562.36.2.1.3.2.9
U32 mscCid	1.3.6.1.4.1.562.36.2.1.3.2.9.1	Unsigned32	not-accessible	This is a Custom Identifier(CID) of the component which generated the alarm
alarmMIB	1.3.6.1.4.1.562.36.2.2.4
alarmGroup	1.3.6.1.4.1.562.36.2.2.4.1
alarmGroupCA	1.3.6.1.4.1.562.36.2.2.4.1.1
alarmGroupCA01	1.3.6.1.4.1.562.36.2.2.4.1.1.2
alarmGroupCA01A	1.3.6.1.4.1.562.36.2.2.4.1.1.2.2
alarmNotifications	1.3.6.1.4.1.562.36.2.2.4.2
alarmNotificationsGroupCA01A	1.3.6.1.4.1.562.36.2.2.4.2.1
alarmCapabilities	1.3.6.1.4.1.562.36.2.2.4.3
alarmCapabilitiesCA	1.3.6.1.4.1.562.36.2.2.4.3.1
alarmCapabilitiesCA01	1.3.6.1.4.1.562.36.2.2.4.3.1.2
alarmCapabilitiesCA01A	1.3.6.1.4.1.562.36.2.2.4.3.1.2.2

RFC description

Generates and reports alarms from Nortel MscPassport carrier-class switching systems with detailed severity and probable cause information.

Start monitoring Nortel MSC Passport mobile carrier switch (central alarm/fault reporting) 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 Nortel-MsCarrier-MscPassport-AlarmMIB

What Is Nortel-MsCarrier-MscPassport-AlarmMIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description