Home/Catalog/ATM-FORUM-M4-MIB

ATM-FORUM-M4-MIB

AI MIB Summary

ATM-FORUM-M4-MIB enables SNMP-based monitoring of Asynchronous Transfer Mode (ATM) network elements by exposing the M4 interface view, specifically tracking physical layer status, virtual path/circuit (VP/VC) connectivity states, and traffic statistics for ATM switches and access nodes.

This MIB module is the SNMP version of the ATM Forum's M4 interface (network element view).
Main OID:
atmfM4MIB.1.3.6.1.4.1.353.100
249
Objects
Active
Status
8
Dependencies

Imported Objects

Objects

249 total
Object Name
atmfM4MIBThis MIB module is the SNMP version of the ATM Forum's M4 interface (network element view).
MODULE-IDENTITY
.1.3.6.1.4.1.353.100
atmfM4MIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1
atmfM4NeVendorThe vendor of the ATM network element.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.1
atmfM4NeVersionThe version of the ATM network element.ro
AutonomousType (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.2
atmfM4NeStartTimeThe time at which the agent was last started; in other words, the time at which sysUpTime was zero.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.3
atmfM4NeAlarmSeverityIndexAn index into the alarm severity profile table, specifying the severity assignments for M4 alarms reported for the ATM network element.rw
Integer32
.1.3.6.1.4.1.353.100.1.4
atmfM4NeSuppressZeroStatsWhen the value of this object is true, no entry will be created in any of the the historical statistics tables for intervals in which all counts are zero.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.5
atmfM4PhysPathTpTableThe ATM Forum M4 interface Configuration table extensions for the physical path termination point.
SEQUENCE OF AtmfM4PhysPathTpEntry
.1.3.6.1.4.1.353.100.1.6
atmfM4PhysPathTpEntryColumns conceptually added to the interface table entry for an ATM interface to model the physical path termination point. The row of the interface table modeling this object should also include columns for the TC Adaptor object and the ATM interface table defined in RFC 1695. The interface table entry for the physical path TP fields of an ATM interface are set up without management system control (or else that setup is outside the scope of M4).
AtmfM4PhysPathTpEntry
.1.3.6.1.4.1.353.100.1.6.1
atmfM4PhysPathTpHwUnitIndexSpecifies the index of the entry in the entPhysicalTable that represents the device (i.e., card) on which the physical path terminates.ro
Integer32
.1.3.6.1.4.1.353.100.1.6.1.1
atmfM4PhysPathTpPortIDIdentifies the port (within the card identified by the hardware unit index) on which the physical path terminates.ro
Integer32
.1.3.6.1.4.1.353.100.1.6.1.2
atmfM4PhysPathTpAlarmSeverityIndexSpecifies the index of the entry in the communications alarm severity profile table that should be used.rw
Integer32
.1.3.6.1.4.1.353.100.1.6.1.3
atmfM4TcAdaptorTableThe ATM Forum M4 interface Configuration table extensions for the TC Adaptor.
SEQUENCE OF AtmfM4TcAdaptorEntry
.1.3.6.1.4.1.353.100.1.7
atmfM4TcAdaptorEntryColumns conceptually added to the interface table entry for an ATM interface to model the TC Adaptor. The row of the interface table modeling this object should also include columns for the physical path TP and the ATM interface table defined in RFC 1695. The interface table entry for the TC Adaptor fields of an ATM interface are set up without management system control (or else that setup is outside the scope of M4).
AtmfM4TcAdaptorEntry
.1.3.6.1.4.1.353.100.1.7.1
atmfM4TcACellScramblingThis attribute is used by the management system to activate and deactivate the ATM cell scrambling function. When the value of this attribute is TRUE, cell scrambling on the interface is activated. This attribute shall be present only for interfaces that support the deactivation of cell scrambling. The ATM Forum UNI specification requires cell scrambling for ATM/SONET interfaces but allows cell scrambling to be controlled (i.e., turned on and off) for ATM/DS3 interfaces.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.7.1.1
atmfM4TcAlarmSeverityIndexSpecifies the index of the entry in the communications alarm severity profile table that should be used.rw
Integer32
.1.3.6.1.4.1.353.100.1.7.1.2
atmfM4AtmLayerTableThe ATM Forum M4 interface Configuration table extensions for the ATM cell layer.
SEQUENCE OF AtmfM4AtmLayerEntry
.1.3.6.1.4.1.353.100.1.8
atmfM4AtmLayerEntryColumns conceptually added to the interface table entry for an ATM interface to model the ATM cell layer. The row of the interface table modeling this object should also include columns for the physical path TP and TC Adaptor object, as well as the ATM interface table defined in RFC 1695. The default configuration of an entry in this table is used whenever the entries for the physical path TP, etc., are created. The management system configures a UNI, B-ICI, or B-ISSI on the interface by first modifying the atmfM4IfType column (this can be done in the same SNMP set-request that sets up the other necessary variables.
AtmfM4AtmLayerEntry
.1.3.6.1.4.1.353.100.1.8.1
atmfM4IfTypeSpecifies the type of ATM cell-layer interface defined on the physical path termination point modeled by this entry in the interface table.rw
Enumeration
.1.3.6.1.4.1.353.100.1.8.1.1
atmfM4IfLoopbackLocationCodeSpecifies the code that shall exist in incoming OAM Loopback cells that are to be looped back at this interface. A value of zero shall indicate that the management system has not set any loopback location code for this interface. Therefore, zero should not be used as the actual loopback location code for any interface. This object shall be present only for table entries that represent an actual ATM cell layer interface (i.e., the atmM4IfType is not none(0)).rw
Integer32
.1.3.6.1.4.1.353.100.1.8.1.2
atmfM4IfSubscriberAddressSpecifies the address or newline-delimited list of addresses assigned to the UNI. This object shall be present only for table entries that represent an UNI interface.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.8.1.3
atmfM4IfPreferredCarrierSpecifies the name of the default carrier to use when one is not explicitly identified in the call set-up message. This object shall be present only for table entries that represent an UNI interface and only when SVC services are supported.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.8.1.4
atmfM4IfFarEndCarrierNetworkSpecifies the adjacent carrier to which the B-ICI transmission path is connected. This object shall be present only for table entries that represent an B-ICI interface and only when SVC services are supported.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.8.1.5
atmfM4VplTableThe ATM Forum M4 VPL Termination Point Configuration table extensions. This table augments the VPL configuration table in RFC 1695.
SEQUENCE OF AtmfM4VplEntry
.1.3.6.1.4.1.353.100.1.9
atmfM4VplEntryAdditional columns for the VPL configuration table entry.
AtmfM4VplEntry
.1.3.6.1.4.1.353.100.1.9.1
atmfM4VplSegEndPtSpecifies whether the VPL termination point is a segment end-point.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.9.1.1
atmfM4VclTableThe ATM Forum M4 VCL Termination Point Configuration table extensions. This table augments the VCL configuration table in RFC 1695.
SEQUENCE OF AtmfM4VclEntry
.1.3.6.1.4.1.353.100.1.10
atmfM4VclEntryAdditional columns for the VCL configuration table entry.
AtmfM4VclEntry
.1.3.6.1.4.1.353.100.1.10.1
atmfM4VclSegEndPtSpecifies whether the VCL termination point is a segment end-point.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.10.1.1
atmfM4VpXConnTableThe ATM Forum M4 VP Cross-Connect Configuration table extensions. This table augments the VP Cross-Connect configuration table in RFC 1695.
SEQUENCE OF AtmfM4VpXConnEntry
.1.3.6.1.4.1.353.100.1.11
atmfM4VpXConnEntryAdditional columns for the VP Cross-Connect table entry.
AtmfM4VpXConnEntry
.1.3.6.1.4.1.353.100.1.11.1
atmfM4VpXConnRecoverIf FALSE, this cross-connection will be removed on failure.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.11.1.1
atmfM4VcXConnTableThe ATM Forum M4 VC Cross-Connect Configuration table extensions. This table augments the VC Cross-Connect configuration table in RFC 1695.
SEQUENCE OF AtmfM4VcXConnEntry
.1.3.6.1.4.1.353.100.1.12
atmfM4VcXConnEntryAdditional columns for the VC Cross-Connect table entry.
AtmfM4VcXConnEntry
.1.3.6.1.4.1.353.100.1.12.1
atmfM4VcXConnRecoverIf FALSE, this cross-connection will be removed on failure.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.12.1.1
atmfM4VpNextVpiTableThe ATM Forum M4 VP Next-VPI value table. This optional table supplied unused VPI values for use in creating entries in the atmVplTable.
SEQUENCE OF AtmfM4VpNextVpiEntry
.1.3.6.1.4.1.353.100.1.13
atmfM4VpNextVpiEntryEach entry in this table represents the 'next' VPI value available for a given ATM interface. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table associated with it.
AtmfM4VpNextVpiEntry
.1.3.6.1.4.1.353.100.1.13.1
atmfM4VpNextVpiValueThis object contains an appropriate value to be used for atmVplVpi when creating entries in the atmVplTable. The value -1 indicates that no unassigned entries are available. To obtain the atmVplVpi value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index (or -1).ro
INTEGER (-1..4095)
.1.3.6.1.4.1.353.100.1.13.1.1
atmfM4VcNextVciTableThe ATM Forum M4 VC Next-VCI value table. This optional table supplied unused VCI values for use in creating entries in the atmVclTable.
SEQUENCE OF AtmfM4VcNextVciEntry
.1.3.6.1.4.1.353.100.1.14
atmfM4VcNextVciEntryEach entry in this table represents the 'next' VCI value available for a given ATM interface. Each VPL Termination Point automatically has an entry in this table associated with it.
AtmfM4VcNextVciEntry
.1.3.6.1.4.1.353.100.1.14.1
atmfM4VcNextVciValueThis object contains an appropriate value to be used for atmVclVci when creating entries in the atmVclTable. The value -1 indicates that no unassigned entries are available. To obtain the atmVclVci value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index (or -1).ro
INTEGER (-1..65535)
.1.3.6.1.4.1.353.100.1.14.1.1
atmfM4CellProtoCurrTableThe ATM Forum M4 Cell Protocol Monitoring Current Data table. This table maintains per-interface statistics for the fifteen-minute interval currently being collected.
SEQUENCE OF AtmfM4CellProtoCurrEntry
.1.3.6.1.4.1.353.100.1.15
atmfM4CellProtoCurrEntryAn entry in the ATM Forum M4 Cell Protocol Monitoring Current Data table. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table associated with it.
AtmfM4CellProtoCurrEntry
.1.3.6.1.4.1.353.100.1.15.1
atmfM4CellProtoCurrSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.15.1.1
atmfM4CellProtoCurrElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.15.1.2
atmfM4CellProtoCurrSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing ATM Cell Protocol Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Counter32
.1.3.6.1.4.1.353.100.1.15.1.3
atmfM4CellProtoCurrProtoErrorsThe number of ATM cells dropped on this interface, due to an unrecognized field or set of fields in the ATM cell header, since the start of this interval.ro
Counter32
.1.3.6.1.4.1.353.100.1.15.1.4
atmfM4CellProtoCurrInOAMCellsThe number of OAM cells received at this interface since the start of this interval.ro
Counter32
.1.3.6.1.4.1.353.100.1.15.1.5
atmfM4CellProtoHistTableThe ATM Forum M4 Cell Protocol Monitoring History Data table. This table maintains per-interface statistics for previous fifteen-minute intervals.
SEQUENCE OF AtmfM4CellProtoHistEntry
.1.3.6.1.4.1.353.100.1.16
atmfM4CellProtoHistEntryAn entry in the ATM Forum M4 Cell Protocol Monitoring History Data table. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table associated with it for each fifteen- minute interval in which statistics are collected for it.
AtmfM4CellProtoHistEntry
.1.3.6.1.4.1.353.100.1.16.1
atmfM4CellProtoHistIndexA number between 1 and 96, which identifies the interval for which the set of statistics in this entry was collected. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
INTEGER
.1.3.6.1.4.1.353.100.1.16.1.1
atmfM4CellProtoHistSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.16.1.2
atmfM4CellProtoHistElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.16.1.3
atmfM4CellProtoHistSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing ATM Cell Protocol Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Counter32
.1.3.6.1.4.1.353.100.1.16.1.4
atmfM4CellProtoHistProtoErrorsThe number of ATM cells dropped on this interface, due to an unrecognized field or set of fields in the ATM cell header, since the start of this interval.ro
Counter32
.1.3.6.1.4.1.353.100.1.16.1.5
atmfM4CellProtoHistInOAMCellsThe number of OAM cells received at this interface since the start of this interval.ro
Counter32
.1.3.6.1.4.1.353.100.1.16.1.6
atmfM4CellProtoErrorTableThe ATM Forum M4 Cell Protocol Monitoring Error Log table. This table maintains a record of the last error of each type encountered on each interface, as a result of ATM Cell Protocol Monitoring.
SEQUENCE OF AtmfM4CellProtoErrorEntry
.1.3.6.1.4.1.353.100.1.17
atmfM4CellProtoErrorEntryAn entry in the ATM Forum M4 Cell Protocol Monitoring Error Log table. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table associated with it for each error that has occurred since agent start-up.
AtmfM4CellProtoErrorEntry
.1.3.6.1.4.1.353.100.1.17.1
atmfM4CellProtoErrorCodeIndicates the type of error for which this entry contains information.
Integer32
.1.3.6.1.4.1.353.100.1.17.1.1
atmfM4CellProtoErrorTimeValue of sysUpTime when the error occurred.ro
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.17.1.2
atmfM4CellProtoErrorReasonThe cell header abnormality type: the reason for discarding the ATM cell (i.e., unassigned VPI/VCI value or VPI/VCI value out of range.ro
Integer32
.1.3.6.1.4.1.353.100.1.17.1.3
atmfM4CellProtoErrorVpiThe VPI value of the discarded cell.ro
INTEGER
.1.3.6.1.4.1.353.100.1.17.1.4
atmfM4CellProtoErrorVciThe VCI value of the discarded cell.ro
INTEGER
.1.3.6.1.4.1.353.100.1.17.1.5
atmfM4TcProtoCurrTableThe ATM Forum M4 TC Adaptor Protocol Monitoring Current Data table. This table maintains per-interface statistics for the fifteen-minute interval currently being collected.
SEQUENCE OF AtmfM4TcProtoCurrEntry
.1.3.6.1.4.1.353.100.1.18
atmfM4TcProtoCurrEntryAn entry in the ATM Forum M4 TC Adaptor Protocol Monitoring Current Data table. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table associated with it.
AtmfM4TcProtoCurrEntry
.1.3.6.1.4.1.353.100.1.18.1
atmfM4TcProtoCurrSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.18.1.1
atmfM4TcProtoCurrElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.18.1.2
atmfM4TcProtoCurrSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing ATM TC Adaptor Protocol Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Counter32
.1.3.6.1.4.1.353.100.1.18.1.3
atmfM4TcProtoCurrDiscardHECViolThe number of ATM cells discarded on this interface, due to an HEC violation, since the start of this interval.ro
Counter32
.1.3.6.1.4.1.353.100.1.18.1.4
atmfM4TcProtoHistTableThe ATM Forum M4 TC Adaptor Protocol Monitoring History Data table. This table maintains per-interface statistics for previous fifteen-minute intervals.
SEQUENCE OF AtmfM4TcProtoHistEntry
.1.3.6.1.4.1.353.100.1.19
atmfM4TcProtoHistEntryAn entry in the ATM Forum M4 TC Adaptor Protocol Monitoring History Data table. Each ATM interface (UNI, BICI, BISSI) automatically has an entry in this table associated with it for each fifteen- minute interval in which statistics are collected for it.
AtmfM4TcProtoHistEntry
.1.3.6.1.4.1.353.100.1.19.1
atmfM4TcProtoHistIndexA number between 1 and 96, which identifies the interval for which the set of statistics in this entry was collected. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
INTEGER
.1.3.6.1.4.1.353.100.1.19.1.1
atmfM4TcProtoHistSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.19.1.2
atmfM4TcProtoHistElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.19.1.3
atmfM4TcProtoHistSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing ATM Cell Protocol Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.19.1.4
atmfM4TcProtoHistDiscardHECViolThe number of ATM cells discarded on this interface, due to an HEC violation, since the start of this interval.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.19.1.5
atmfM4VpUpcNpcCurrTableThe ATM Forum M4 UPC/NPC Disagreement Monitoring Current Data table for VPL termination points. This table maintains per-TP statistics for the fifteen-minute interval currently being collected.
SEQUENCE OF AtmfM4VpUpcNpcCurrEntry
.1.3.6.1.4.1.353.100.1.20
atmfM4VpUpcNpcCurrEntryAn entry in the ATM Forum M4 UPC/NPC Disagreement Monitoring Current Data table for VPL termination points. Each VPL Termination Point automatically has an entry in this table associated with it.
AtmfM4VpUpcNpcCurrEntry
.1.3.6.1.4.1.353.100.1.20.1
atmfM4VpUpcNpcCurrSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.20.1.1
atmfM4VpUpcNpcCurrElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.20.1.2
atmfM4VpUpcNpcCurrSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing UPC/NPC Disagreement Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Counter32
.1.3.6.1.4.1.353.100.1.20.1.3
atmfM4VpUpcNpcCurrDiscardedCellsThe number of discarded cells due to combined CLP=0 and CLP=1 UPC/NPC policing.ro
Counter32
.1.3.6.1.4.1.353.100.1.20.1.4
atmfM4VpUpcNpcCurrDiscardedClp0The number of discarded cells due to CLP=0 only UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Counter32
.1.3.6.1.4.1.353.100.1.20.1.5
atmfM4VpUpcNpcCurrPassedCellsThe number of cells that have been successfully passed by the combined CLP=0 and CLP=1 UPC/NPC policing.ro
Counter32
.1.3.6.1.4.1.353.100.1.20.1.6
atmfM4VpUpcNpcCurrPassedClp0The number of cells that have been successfully passed by the CLP=0 UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Counter32
.1.3.6.1.4.1.353.100.1.20.1.7
atmfM4VpUpcNpcHistTableThe ATM Forum M4 UPC/NPC Disagreement Monitoring History Data table for VPL termination points. This table maintains per-interface statistics for previous fifteen-minute intervals.
SEQUENCE OF AtmfM4VpUpcNpcHistEntry
.1.3.6.1.4.1.353.100.1.21
atmfM4VpUpcNpcHistEntryAn entry in the ATM Forum M4 UPC/NPC Disagreement Monitoring History Data table for VPL termination points. Each VPL Termination Point automatically has an entry in this table associated with it.
AtmfM4VpUpcNpcHistEntry
.1.3.6.1.4.1.353.100.1.21.1
atmfM4VpUpcNpcHistIndexA number between 1 and 96, which identifies the interval for which the set of statistics in this entry was collected. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
INTEGER
.1.3.6.1.4.1.353.100.1.21.1.1
atmfM4VpUpcNpcHistSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.21.1.2
atmfM4VpUpcNpcHistElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.21.1.3
atmfM4VpUpcNpcHistSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing UPC/NPC Disagreement Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.21.1.4
atmfM4VpUpcNpcHistDiscardedCellsThe number of discarded cells due to combined CLP=0 and CLP=1 UPC/NPC policing.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.21.1.5
atmfM4VpUpcNpcHistDiscardedClp0The number of discarded cells due to CLP=0 only UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.21.1.6
atmfM4VpUpcNpcHistPassedCellsThe number of cells that have been successfully passed by the combined CLP=0 and CLP=1 UPC/NPC policing.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.21.1.7
atmfM4VpUpcNpcHistPassedClp0The number of cells that have been successfully passed by the CLP=0 UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.21.1.8
atmfM4VcUpcNpcCurrTableThe ATM Forum M4 UPC/NPC Disagreement Monitoring Current Data table for VCL termination points. This table maintains per-TP statistics for the fifteen-minute interval currently being collected.
SEQUENCE OF AtmfM4VcUpcNpcCurrEntry
.1.3.6.1.4.1.353.100.1.22
atmfM4VcUpcNpcCurrEntryAn entry in the ATM Forum M4 UPC/NPC Disagreement Monitoring Current Data table for VCL termination points. Each VCL Termination Point automatically has an entry in this table associated with it.
AtmfM4VcUpcNpcCurrEntry
.1.3.6.1.4.1.353.100.1.22.1
atmfM4VcUpcNpcCurrSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.22.1.1
atmfM4VcUpcNpcCurrElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.22.1.2
atmfM4VcUpcNpcCurrSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing UPC/NPC Disagreement Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Counter32
.1.3.6.1.4.1.353.100.1.22.1.3
atmfM4VcUpcNpcCurrDiscardedCellsThe number of discarded cells due to combined CLP=0 and CLP=1 UPC/NPC policing.ro
Counter32
.1.3.6.1.4.1.353.100.1.22.1.4
atmfM4VcUpcNpcCurrDiscardedClp0The number of discarded cells due to CLP=0 only UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Counter32
.1.3.6.1.4.1.353.100.1.22.1.5
atmfM4VcUpcNpcCurrPassedCellsThe number of cells that have been successfully passed by the combined CLP=0 and CLP=1 UPC/NPC policing.ro
Counter32
.1.3.6.1.4.1.353.100.1.22.1.6
atmfM4VcUpcNpcCurrPassedClp0The number of cells that have been successfully passed by the CLP=0 UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Counter32
.1.3.6.1.4.1.353.100.1.22.1.7
atmfM4VcUpcNpcHistTableThe ATM Forum M4 UPC/NPC Disagreement Monitoring History Data table for VCL termination points. This table maintains per-interface statistics for previous fifteen-minute intervals.
SEQUENCE OF AtmfM4VcUpcNpcHistEntry
.1.3.6.1.4.1.353.100.1.23
atmfM4VcUpcNpcHistEntryAn entry in the ATM Forum M4 UPC/NPC Disagreement Monitoring History Data table for VCL termination points. Each VCL Termination Point automatically has an entry in this table associated with it.
AtmfM4VcUpcNpcHistEntry
.1.3.6.1.4.1.353.100.1.23.1
atmfM4VcUpcNpcHistIndexA number between 1 and 96, which identifies the interval for which the set of statistics in this entry was collected. The interval identified by 1 is the most recently completed 15 minute interval, and the interval identified by N is the interval immediately preceding the one identified by N-1.
INTEGER
.1.3.6.1.4.1.353.100.1.23.1.1
atmfM4VcUpcNpcHistSuspectIf true, the statistics in this entry may be unreliable.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.23.1.2
atmfM4VcUpcNpcHistElapsedTimeAmount of time, measured in units of 0.01 second, that statistics for this entry (the current interval) have been counted.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.23.1.3
atmfM4VcUpcNpcHistSupprIntvlsThis attribute is non-zero only if the ATM NE is suppressing UPC/NPC Disagreement Monitoring History Data entry creation when the current interval terminates with 'all-zeroes' performance measurements.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.23.1.4
atmfM4VcUpcNpcHistDiscardedCellsThe number of discarded cells due to combined CLP=0 and CLP=1 UPC/NPC policing.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.23.1.5
atmfM4VcUpcNpcHistDiscardedClp0The number of discarded cells due to CLP=0 only UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.23.1.6
atmfM4VcUpcNpcHistPassedCellsThe number of cells that have been successfully passed by the combined CLP=0 and CLP=1 UPC/NPC policing.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.23.1.7
atmfM4VcUpcNpcHistPassedClp0The number of cells that have been successfully passed by the CLP=0 UPC/NPC policing. This object shall be present only if CLP=0 traffic is separately policed.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.23.1.8
atmfM4TestTypes
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1.24
atmfM4TestOAMLoopbackSegThis identifies an OAM Loopback Test on a VPL, VPC, VCL, or VCC termination point, using a segment OAM cell. The test type must have appended to it a code that uniquely identifies an intermediate point responsible for looping back the cell. If this is absent, the loopback is performed at the end of the segment or connection. E.g., the OID { atmfM4TestOAMLoopbackSeg 5 } identifies that the loopback should be performed at the intermediate point labeled 5.
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1.24.1
atmfM4TestOAMLoopbackE2EThis identifies an OAM Loopback Test on a VPL, VPC, VCL, or VCC termination point, using an end-to-end OAM cell.
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1.24.2
atmfM4VpTestTableThe ATM Forum M4 VP Termination Point Test table. This table allows tests to be run on VPL and VPC termination points. The operation of this table is entirely analogous to that of the ifTestTable in RFC 1573, except that the indexes into this table are different.
SEQUENCE OF AtmfM4VpTestEntry
.1.3.6.1.4.1.353.100.1.25
atmfM4VpTestEntryAn entry containing objects for invoking tests on a VPL or VPC termination point.
AtmfM4VpTestEntry
.1.3.6.1.4.1.353.100.1.25.1
atmfM4VpTestObjectSpecifies whether the test applies to the VPL termination point with the specified VPI, or the VPC termination point.
Enumeration
.1.3.6.1.4.1.353.100.1.25.1.1
atmfM4VpTestIdThis object identifies the current invocation of the interface's test.rw
TestAndIncr (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.25.1.2
atmfM4VpTestStatusThis object indicates whether or not some manager currently has the necessary 'ownership' required to invoke a test on this interface. A write to this object is only successful when it changes its value from 'notInUse(1)' to 'inUse(2)'. After completion of a test, the agent resets the value back to 'notInUse(1)'.rw
Enumeration
.1.3.6.1.4.1.353.100.1.25.1.3
atmfM4VpTestTypeA control variable used to start and stop operator- initiated interface tests. Most OBJECT IDENTIFIER values assigned to tests are defined elsewhere, in association with specific types of interface. However, this document assigns a value for a full- duplex loopback test, and defines the special meanings of the subject identifier: noTest OBJECT IDENTIFIER ::= { 0 0 } When the value noTest is written to this object, no action is taken unless a test is in progress, in which case the test is aborted. Writing any other value to this object is only valid when no test is currently in progress, in which case the indicated test is initiated. When read, this object always returns the most recent value that atmfM4VpTestType was set to. If it has not been set since the last initialization of the network management subsystem on the agent, a value of noTest is returned.rw
AutonomousType (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.25.1.4
atmfM4VpTestResultThis object contains the result of the most recently requested test, or the value none(1) if no tests have been requested since the last reset. Note that this facility provides no provision for saving the results of one test when starting another, as could be required if used by multiple managers concurrently.ro
Enumeration
.1.3.6.1.4.1.353.100.1.25.1.5
atmfM4VpTestCodeThis object contains a code which contains more specific information on the test result, for example an error-code after a failed test. Error codes and other values this object may take are specific to the type of interface and/or test. The value may have the semantics of either the AutonomousType or RowPointer textual conventions as defined in RFC 1903 [15]. The identifier: testCodeUnknown OBJECT IDENTIFIER ::= { 0 0 } is defined for use if no additional result code is available.ro
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1.25.1.6
atmfM4VpTestOwnerThe entity which currently has the 'ownership' required to invoke a test on this interface.rw
OwnerString (IF-MIB)
.1.3.6.1.4.1.353.100.1.25.1.7
atmfM4VcTestTableThe ATM Forum M4 VC Termination Point Test table. This table allows tests to be run on VCL and VCC termination points. The operation of this table is entirely analogous to that of the ifTestTable in RFC 1573, except that the indexes into this table are different.
SEQUENCE OF AtmfM4VcTestEntry
.1.3.6.1.4.1.353.100.1.26
atmfM4VcTestEntryAn entry containing objects for invoking tests on a VCL or VCC termination point.
AtmfM4VcTestEntry
.1.3.6.1.4.1.353.100.1.26.1
atmfM4VcTestObjectSpecifies whether the test applies to the VCL termination point with the specified VPI and VCI values, or to the VCC termination point.
Enumeration
.1.3.6.1.4.1.353.100.1.26.1.1
atmfM4VcTestIdThis object identifies the current invocation of the interface's test.rw
TestAndIncr (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.26.1.2
atmfM4VcTestStatusThis object indicates whether or not some manager currently has the necessary 'ownership' required to invoke a test on this interface. A write to this object is only successful when it changes its value from 'notInUse(1)' to 'inUse(2)'. After completion of a test, the agent resets the value back to 'notInUse(1)'.rw
Enumeration
.1.3.6.1.4.1.353.100.1.26.1.3
atmfM4VcTestTypeA control variable used to start and stop operator- initiated interface tests. Most OBJECT IDENTIFIER values assigned to tests are defined elsewhere, in association with specific types of interface. However, this document assigns a value for a full- duplex loopback test, and defines the special meanings of the subject identifier: noTest OBJECT IDENTIFIER ::= { 0 0 } When the value noTest is written to this object, no action is taken unless a test is in progress, in which case the test is aborted. Writing any other value to this object is only valid when no test is currently in progress, in which case the indicated test is initiated. When read, this object always returns the most recent value that atmfM4VcTestType was set to. If it has not been set since the last initialization of the network management subsystem on the agent, a value of noTest is returned.rw
AutonomousType (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.26.1.4
atmfM4VcTestResultThis object contains the result of the most recently requested test, or the value none(1) if no tests have been requested since the last reset. Note that this facility provides no provision for saving the results of one test when starting another, as could be required if used by multiple managers concurrently.ro
Enumeration
.1.3.6.1.4.1.353.100.1.26.1.5
atmfM4VcTestCodeThis object contains a code which contains more specific information on the test result, for example an error-code after a failed test. Error codes and other values this object may take are specific to the type of interface and/or test. The value may have the semantics of either the AutonomousType or RowPointer textual conventions as defined in RFC 1903 [15]. The identifier: testCodeUnknown OBJECT IDENTIFIER ::= { 0 0 } is defined for use if no additional result code is available.ro
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1.26.1.6
atmfM4VcTestOwnerThe entity which currently has the 'ownership' required to invoke a test on this termination point.rw
OwnerString (IF-MIB)
.1.3.6.1.4.1.353.100.1.26.1.7
atmfM4EquipTableThe ATM Forum M4 Equipment table. This table augments the physical entity table.
SEQUENCE OF AtmfM4EquipEntry
.1.3.6.1.4.1.353.100.1.28
atmfM4EquipEntryAn entry in the ATM Forum M4 Equipment table. Each entry of this type represents a piece of equipment within the ATM NE that neither is nor accepts a replaceable plug- in unit.
AtmfM4EquipEntry
.1.3.6.1.4.1.353.100.1.28.1
atmfM4EquipAdminStatusUsed by the adminstrator to lock and unlock the object.rw
Enumeration
.1.3.6.1.4.1.353.100.1.28.1.1
atmfM4EquipLocationThe specific or general location of the component.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.28.1.2
atmfM4EquipOperStatusThis attributes identifies whether or not the component is capable of performing its normal functions.ro
Enumeration
.1.3.6.1.4.1.353.100.1.28.1.3
atmfM4EquipVendorThe vendor of the component.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.28.1.4
atmfM4EquipVersionThe version of the component.ro
AutonomousType (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.28.1.5
atmfM4EquipUserLabelA user-friendly name for the piece of equipment.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.28.1.6
atmfM4EquipAlarmSeverityIndexAn index into the alarm severity profile table, specifying the severity assignments for M4 alarms reported for this component.rw
Integer32
.1.3.6.1.4.1.353.100.1.28.1.7
atmfM4EquipHolderTableThe ATM Forum M4 Equipment Holder table. This table augments the physical table.
SEQUENCE OF AtmfM4EquipHolderEntry
.1.3.6.1.4.1.353.100.1.29
atmfM4EquipHolderEntryAn entry in the ATM Forum M4 Equipment Holder table. Each entry of this type represents a component within the ATM NE that accepts a replaceable plug-in unit.
AtmfM4EquipHolderEntry
.1.3.6.1.4.1.353.100.1.29.1
atmfM4EquipHolderTypeThe type of the component.ro
Enumeration
.1.3.6.1.4.1.353.100.1.29.1.1
atmfM4EquipHolderAcceptableTypesThe types of plug-in units that can be supported by the slot, separated by newline characters. This attribute shall be present only when the Equipment Holder represents a slot.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.29.1.2
atmfM4EquipHolderSlotStatusThis attributes identifies whether or not a plug-in unit is present in the slot. This attribute shall be present only when the Equipment Holder represents a slot.ro
Enumeration
.1.3.6.1.4.1.353.100.1.29.1.3
atmfM4EquipHolderSwLoadAn index into the installed software table, specifying the software that is to be loaded into the plug-in unit whenever an automatic reload of software is needed. This attribute shall be present only when the Equipment Holder represents a slot.rw
INTEGER
.1.3.6.1.4.1.353.100.1.29.1.4
atmfM4PlugInUnitTableThe ATM Forum M4 Plug-In Unittable. This table augments the physical entity table.
SEQUENCE OF AtmfM4PlugInUnitEntry
.1.3.6.1.4.1.353.100.1.30
atmfM4PlugInUnitEntryAn entry in the ATM Forum M4 Plug-In Unit table. Each entry of this type represents a piece of equipment within the ATM NE that is inserted into and removed from an Equipment Holder.
AtmfM4PlugInUnitEntry
.1.3.6.1.4.1.353.100.1.30.1
atmfM4PlugInUnitAdminStatusUsed by the adminstrator to lock and unlock the object.rw
Enumeration
.1.3.6.1.4.1.353.100.1.30.1.1
atmfM4PlugInUnitAvailStatusProvides further information regarding the state of the component.ro
Enumeration
.1.3.6.1.4.1.353.100.1.30.1.2
atmfM4PlugInUnitOperStatusThis attributes identifies whether or not the component is capable of performing its normal functions.ro
Enumeration
.1.3.6.1.4.1.353.100.1.30.1.3
atmfM4PlugInUnitVendorThe vendor of the component.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.30.1.4
atmfM4PlugInUnitVersionThe version of the component.ro
AutonomousType (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.30.1.5
atmfM4PlugInUnitAlarmSeverityIndexAn index into the alarm severity profile table, specifying the severity assignments for M4 alarms reported for this component.rw
Integer32
.1.3.6.1.4.1.353.100.1.30.1.6
atmfM4HwRunningSwTableThe ATM Forum M4 Hardware Unit/Running Software relationship. This table describes the software that is running on each hardware unit in the ATM NE.
SEQUENCE OF AtmfM4HwRunningSwEntry
.1.3.6.1.4.1.353.100.1.32
atmfM4HwRunningSwEntryAn entry in the ATM Forum M4 Hardware Unit/Running Software relationship table. Each entry of this type identifies an entry in the entPhysicalTable and one in the hrRunningSoftwareTable.
AtmfM4HwRunningSwEntry
.1.3.6.1.4.1.353.100.1.32.1
atmfM4HwRunningSwHwIndexThe index, in the entPhysicalTable, of the containing hardware unit in this pair.
INTEGER
.1.3.6.1.4.1.353.100.1.32.1.1
atmfM4HwRunningSwIndexA unique number within the context of the containing hardware unit.
INTEGER
.1.3.6.1.4.1.353.100.1.32.1.2
atmfM4HwRunningSwSwIndexThe index, in the hrRunningSwTable, of the software product represented by this entry.ro
INTEGER
.1.3.6.1.4.1.353.100.1.32.1.3
atmfM4HwInstalledSwTableThe ATM Forum M4 Hardware Unit/Installed Software relationship. This table describes the software that is Installed on each hardware unit in the ATM NE.
SEQUENCE OF AtmfM4HwInstalledSwEntry
.1.3.6.1.4.1.353.100.1.33
atmfM4HwInstalledSwEntryAn entry in the ATM Forum M4 Hardware Unit/Installed Software relationship table. Each entry of this type identifies an entry in the physical entity table and one in the hrInstalledSoftwareTable.
AtmfM4HwInstalledSwEntry
.1.3.6.1.4.1.353.100.1.33.1
atmfM4HwInstalledSwHwIndexThe index, in the entPhysical table, of the containing physical entity in this pair.
INTEGER
.1.3.6.1.4.1.353.100.1.33.1.1
atmfM4HwInstalledSwIndexA unique number within the context of the containing hardware unit.ro
INTEGER
.1.3.6.1.4.1.353.100.1.33.1.2
atmfM4HwInstalledSwSwIndexThe index, in the hrInstalledSwTable, of the software product represented by this entry.ro
INTEGER
.1.3.6.1.4.1.353.100.1.33.1.3
atmfM4HwSwAlarmSeverityIndexAn index into the alarm severity profile table, specifying the severity assignments for M4 alarms reported for this piece of software installed on the hardware unit.rw
Integer32
.1.3.6.1.4.1.353.100.1.33.1.4
atmfM4AlarmSevDefaultThe default severity value used for new profile index/trap ID pairs that have not yet been modified. This value is also used whenever an object's alarm severity profile index is set to 0.rw
AtmfM4AlarmSeverity
.1.3.6.1.4.1.353.100.1.34
atmfM4AlarmSevProfileIndexNextThis object contains an appropriate value to be used for atmfM4AlarmSevProfileIndex when creating entries in the atmfM4AlarmSevProfileTable. The value -1 indicates that no unassigned entries are available. To obtain the index value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index (or -1).ro
Integer32
.1.3.6.1.4.1.353.100.1.35
atmfM4AlarmSevProfileTableThe ATM Forum M4 alarm severity profile table. This table specifies which profiles exist. Creating or deleting an entry in this table automatically creates or deletes the corresponding entries in the atmfM4AlarmSeverityTable.
SEQUENCE OF AtmfM4AlarmSevProfileEntry
.1.3.6.1.4.1.353.100.1.36
atmfM4AlarmSevProfileEntryA group of severities, one for each alarm type in the communications alarm group.
AtmfM4AlarmSevProfileEntry
.1.3.6.1.4.1.353.100.1.36.1
atmfM4AlarmSevProfileIndexA number identifying this alarm severity profile.
Integer32
.1.3.6.1.4.1.353.100.1.36.1.1
atmfM4AlarmSevProfileRowStatusThis object is used to create a new row or to delete an existing row in the table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.36.1.2
atmfM4AlarmSevTableThe ATM Forum M4 alarm severity table. This table associates profile index and trap ID pairs with severities to be used for M4 alarm traps that have occurred. (Note that this table does not apply to cleared alarms.)
SEQUENCE OF AtmfM4AlarmSevEntry
.1.3.6.1.4.1.353.100.1.37
atmfM4AlarmSevEntryAn entry in this table associates an alarm severity profile index/trap ID pair with a severity. Deleting a particular profile's row in the alarm severity profile table deletes all rows in this table with the same profile index. Conceptually, rows corresponding to all possible trap ID's are created in this table when a new alarm severity profile is created, but the agent will return a default value except for those few traps for which values have been set.
AtmfM4AlarmSevEntry
.1.3.6.1.4.1.353.100.1.37.1
atmfM4AlarmSevTrapIdThe ID of the trap type to which this entry applies.
Integer32
.1.3.6.1.4.1.353.100.1.37.1.1
atmfM4AlarmSeverityThe severity to be used for this trap type when the is selected. If no value for this object has ever been set since the corresponding profile was created, the agent should return the value of the object atmfM4AlarmSevDefaultrw
AtmfM4AlarmSeverity
.1.3.6.1.4.1.353.100.1.37.1.2
atmfM4ForwardAllTrapsThis is used as the value of the object atmfM4ForwardedTrapObject when traps from all objects are to be forwarded, or when there is only one object of the type that forwards the specified trap type.
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.1.38
atmfM4TrapForwardingTableThe ATM Forum M4 Trap forwarding discriminator table. This table specifies which traps will be sent to which management system.
SEQUENCE OF AtmfM4TrapForwardingEntry
.1.3.6.1.4.1.353.100.1.39
atmfM4TrapForwardingEntryInformation about a group of traps to be sent to a particular IP address. A new entry must have values for all attributes that do not have default values before its RowStatus column can be set to active(1).
AtmfM4TrapForwardingEntry
.1.3.6.1.4.1.353.100.1.39.1
atmfM4TrapForwardingIndexA unique number identifying the table entry.
Integer32
.1.3.6.1.4.1.353.100.1.39.1.1
atmfM4TrapForwardingDestThe IP address to which traps identified by this table entry should be sent.rw
IpAddress
.1.3.6.1.4.1.353.100.1.39.1.2
atmfM4ForwardedTrapIdThe ID of the trap type to which this entry applies.rw
Integer32
.1.3.6.1.4.1.353.100.1.39.1.3
atmfM4ForwardedTrapObjectThe object to which this entry applies. By convention, this is the name of the first object in the row in the table referenced. The special value { 0 0 } indicates that traps of this type from all objects of the type that can generate it. It should also be used when traps from the ATM NE are to be specified.rw
RowPointer (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.39.1.4
atmfM4TrapForwardingPortThe UDP port on the specified management system to which traps identified by this entry should be sent.rw
Integer32
.1.3.6.1.4.1.353.100.1.39.1.5
atmfM4LowestForwardedSeverityThe lowest severity of traps of this type from the specified object that should be sent to this address. This object has significance only if the trap type specified has a severity associated with itrw
AtmfM4AlarmSeverity
.1.3.6.1.4.1.353.100.1.39.1.6
atmfM4ForwardedIndeterminateWhen this object has the value TRUE, traps with indeterminate severity will be forwarded to the specified event. This object has significance only if the trap type specified has a severity associated with itrw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.39.1.7
atmfM4TrapForwardingRowStatusThis object is used to create a new row or to delete an existing row in the table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.39.1.8
atmfM4TrapLogTableThe ATM Forum M4 Trap Agent log table. This table defines the trap logs currently maintained by the agent. The management system creates entries in this table to specify which types of traps, from which ATM network elements, should be logged. Deleting an entry in this table deletes all entries in the corresponding log.
SEQUENCE OF AtmfM4TrapLogEntry
.1.3.6.1.4.1.353.100.1.40
atmfM4TrapLogEntryInformation about a single trap log.
AtmfM4TrapLogEntry
.1.3.6.1.4.1.353.100.1.40.1
atmfM4TrapLogSrcThe IP address of the SNMP agent whose traps are stored in this log.
IpAddress
.1.3.6.1.4.1.353.100.1.40.1.1
atmfM4TrapLogTypeThe type of traps stored in this log.
Enumeration
.1.3.6.1.4.1.353.100.1.40.1.2
atmfM4TrapLogAdminStatusThe management system uses this object to stop and start the operations of this object.rw
Enumeration
.1.3.6.1.4.1.353.100.1.40.1.3
atmfM4TrapLogOperStatusIndicates whether or not the log is capable of performing its normal operations.ro
Enumeration
.1.3.6.1.4.1.353.100.1.40.1.4
atmfM4TrapLogFullActionIndicates the action that should be performed when no more log entries can be created due to a log-full condition. If the value of this object is wrap(2), each new log entry will cause the deletion of the oldest entry still in the log, for as long as the log is still full.rw
Enumeration
.1.3.6.1.4.1.353.100.1.40.1.5
atmfM4TrapLogRowStatusThis object is used to create a new row or to delete an existing row in the table.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.40.1.6
atmfM4LoggedTrapTableThe ATM Forum M4 Trap Agent logged trap table. This table is used to maintain the traps logged.
SEQUENCE OF AtmfM4LoggedTrapEntry
.1.3.6.1.4.1.353.100.1.41
atmfM4LoggedTrapEntryInformation about a single trap in the log. Entries in this table are created automatically but can be deleted by the management system. Entries that represent 'alarm' log types are augmented by the atmfM4LoggedAlarmEntry table.
AtmfM4LoggedTrapEntry
.1.3.6.1.4.1.353.100.1.41.1
atmfM4LoggedTrapIndexA unique number identifying this entry in the log. When the maximum value for this object has been reached, it will wrap around to 0.
Unsigned32
.1.3.6.1.4.1.353.100.1.41.1.1
atmfM4LoggedTrapTimeThe time at which this trap was logged.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.41.1.2
atmfM4LoggedTrapIDThe type of trap to which this entry applies. Together with the logged trap ID object, this object specifies the entity to which this logged trap referred.ro
Integer32
.1.3.6.1.4.1.353.100.1.41.1.3
atmfM4LoggedTrapObjectThe object to which this entry applies. By convention, this is the name of the first object in the row in the table referenced. Together with the logged trap ID object, this object specifies the entity to which this logged trap referred. The special value { 0 0 } indicates that the trap refers to the ATM NE entity itself.ro
RowPointer (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.41.1.4
atmfM4LoggedTrapRowStatusThis object is used to delete an existing row in the table. Note that the only value to which a management system can set this object is destroy(6).rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.41.1.5
atmfM4LoggedAlarmTableThe ATM Forum M4 Trap Agent logged alarm trap table. This table is used to maintain extra information for logged traps that represent alarm types.
SEQUENCE OF AtmfM4LoggedAlarmEntry
.1.3.6.1.4.1.353.100.1.42
atmfM4LoggedAlarmEntryInformation about the alarm-specific attributes of a single trap in the log.
AtmfM4LoggedAlarmEntry
.1.3.6.1.4.1.353.100.1.42.1
atmfM4LoggedAlarmSeverityThe perceived severity of the alarm, as specified by the agent that generated it.ro
AtmfM4AlarmLogSeverity
.1.3.6.1.4.1.353.100.1.42.1.1
atmfM4LoggedAlarmBackedUpIf the value of this object is true, the agent reported in this trap that the failed object had been backed up. This object is only present if it was included in the alarm trap corresponding to this log entry.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.42.1.2
atmfM4LoggedAlarmBUObjectIndicates the object that provided back-up services to the failed object. This object is only present if it was included in the alarm trap corresponding to this log entry.ro
RowPointer (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.42.1.3
atmfM4LoggedAlarmSpecificProbIndicates further refinements to the problem identified by the alarm type. If more than one specific problem is described in this object, the problem descriptions are separated by newline characters. This object is only present if it was included in the alarm trap corresponding to this log entry.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.42.1.4
atmfM4LoggedAlarmRepairActIndicates proposed repair actions reported by the agent for the the problem identified by the alarm. If more than one action is described in this object, the problem descriptions are separated by newline characters. This object is only present if it was included in the alarm trap corresponding to this log entry.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.42.1.5
atmfM4TrapAlarmSeverityThe perceived severity of the alarm, as specified by the agent that generated it.ro
AtmfM4AlarmLogSeverity
.1.3.6.1.4.1.353.100.1.43
atmfM4TrapAlarmBackedUpIf the value of this object is true, the failed object has been backed up.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.44
atmfM4TrapAlarmBUObjectIndicates the object that provided back-up services to the failed object.ro
RowPointer (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.45
atmfM4TrapAlarmSpecificProbIndicates further refinements to the problem identified by the alarm type. If more than one specific problem is described in this object, the problem descriptions are separated by newline characters.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.353.100.1.46
atmfM4TrapAlarmRepairActIndicates proposed repair actions reported by the agent for the the problem identified by the alarm. If more than one action is described in this object, the problem descriptions are separated by newline characters.ro
Unsigned32
.1.3.6.1.4.1.353.100.1.47
atmfM4MIBTraps
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.2
atmfM4IfAisAlarmIndicates that an AIS alarm condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.1
atmfM4IfLcdAlarmIndicates that an LCD (Loss of Cell Delineation) condition has occurred on the TC Adatpr associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.2
atmfM4IfLofAlarmIndicates that an LOF (Loss of Frame) condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.3
atmfM4IfLopAlarmIndicates that an LOP (Loss of Pointer) condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.4
atmfM4IfLosAlarmIndicates that an LOS (Loss of Signal) condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.5
atmfM4IfPayloadMismatchAlarmIndicates that a payload type mismatch condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.6
atmfM4IfXmissionErrAlarmIndicates that an transmission error condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.7
atmfM4IfPathTraceMismatchAlarmIndicates that path trace mismatch condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.8
atmfM4IfRdiAlarmIndicates that an RDI (Remote Defect Indication) condition has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.9
atmfM4IfSignalLabelMismatchAlarmIndicates that a signal label mismatch has occurred on the physical path TP associated with the specified interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.10
atmfM4HwLineCardAlarmIndicates that a line-card problem condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.23
atmfM4HwPowerAlarmIndicates that a power problem alarm condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.25
atmfM4HwPIUnitMissingAlarmIndicates that a plug-in unit missing condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.29
atmfM4HwPIUnitProbAlarmIndicates that a plug-in unit problem condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.30
atmfM4HwPIUnitMismatchAlarmIndicates that a plug-in unit type mismatch condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.31
atmfM4HwTimingProbAlarmIndicates that a timing problem alarm condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.32
atmfM4HwSwDownloadFailAlarmIndicates that a software download failure has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.39
atmfM4HwVersionMismatchAlarmIndicates that a version mismatch condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.40
atmfM4HwFanFailAlarmIndicates that a cooling fan failure condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.41
atmfM4HwHighTempAlarmIndicates that a high temperature condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.44
atmfM4SwVersionMismatchAlarmIndicates that a version mismatch condition has occurred on the hardware unit associated with the specified index. A hardware index of 0 indicates that the error occurred in the ATM NE but not in any one hardware unit maintained in the MIB table.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.45
atmfM4HwUnitUpIndicates that the operational state of the specified hardware unit has transitioned to 'up'.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.54
atmfM4HwUnitDownIndicates that the operational state of the specified hardware unit has transitioned to 'down'.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.55
atmfM4AtmCellIfCreatedIndicates that an ATM cell layer interface has just been created on the interface.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.56
atmfM4AtmCellIfDeletedIndicates that the ATM cell layer interface has just been deleted.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.57
atmfM4HwUnitCreatedIndicates that the specified hardware unit has been installed at the specified location.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.66
atmfM4HwUnitDeletedIndicates that the specified hardware unit has been removed or de-instaleld from the specified location.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.67
atmfM4IfChangedIndicates that the configuration of the interface has been changed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.353.100.2.70
atmfM4MIBCompliance
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.3
atmfM4Groups
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.3.1
atmfM4Compliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.353.100.3.2
ATM-FORUM-M4-MIB - SNMP MIB Reference | MIBs Explorer