Nortel-MsCarrier-MscPassport-AlarmMIB: View SNMP OID List / Download MIB

A pointer to the RowStatus variable of the component emitting the alarm.

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'.

The date and time at which the alarmed event occurred.

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. Enumeration: 'message': 0, 'set': 1, 'clear': 2.

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. Enumeration: 'major': 2, 'indeterminate': 0, 'warning': 4, 'critical': 1, 'cleared': 5, 'minor': 3.

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. Enumeration: 'equipment': 3, 'environmental': 4, 'debug': 7, 'processing': 2, 'qualityOfService': 1, 'communications': 0, 'unknown': 8, 'operator': 6, 'security': 5.

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. Enumeration: 'applicationSubsystemFailure': 50, 'debugging': 201, 'localTransmissionError': 3, 'lossOfSignal': 0, 'congestion': 26, 'commSubsystemFailure': 7, 'equipmentFailure': 70, 'delayedInfo': 120, 'softwareProgramTermination': 46, 'softwareProgramError': 45, 'softwareError': 44, 'fileError': 47, 'nonRepudiationFailure': 112, 'networkServerIntervention': 204, 'timingProblem': 61, 'outputDeviceError': 67, 'transmitterFailure': 66, 'remoteTransmissionError': 4, 'unknown': 202, 'breachOfConfidence': 111, 'unexpectedInfo': 84, 'ioDeviceError': 69, 'authenticationFailure': 110, 'lanError': 9, 'degradedSignal': 6, 'intrusionDetection': 101, 'keyExpired': 121, 'underlyingResourceUnavail': 49, 'retransmissionRateReduced': 23, 'queueSizeExceeded': 21, 'multiplexorProblem': 64, 'receiverFailure': 65, 'lossOfFrame': 1, 'otherSecurityService': 114, 'versionMismatch': 41, 'infoModification': 82, 'infoOutOfSequence': 83, 'cableTamper': 100, 'outOfHoursActivity': 122, 'inputDeviceError': 68, 'proceduralError': 92, 'cpuCyclesLimitExceeded': 43, 'responseTimeExcessive': 20, 'callEstablishmentError': 5, 'thresholdCrossed': 24, 'configurationError': 51, 'commProtocolError': 8, 'storageCapacityProblem': 40, 'performanceDegraded': 25, 'framingError': 2, 'atOrNearCapacity': 27, 'outOfService': 91, 'outOfMemory': 48, 'powerProblem': 60, 'adapterError': 71, 'otherPhysical': 102, 'dteDceInterfaceError': 10, 'bandwidthReduced': 22, 'denialOfService': 90, 'otherOperational': 93, 'datasetModemError': 63, 'corruptData': 42, 'operationalCondition': 200, 'processorProblem': 62, 'infoMissing': 81, 'unauthorizedAccess': 113, 'duplicateInfo': 80, 'inactiveVirtualCircuit': 203.

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.

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.

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).

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.

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.

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.

An internal filename (for internal use only).

An internal line number in the file (see filename) referred to above (for internal use only).

A version indicator of the file (filename) referred to above (for internal use only).

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.

This is a Custom Identifier(CID) of the component which generated the alarm

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.

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.

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.

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.

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.

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.