ALCATEL-IND1-DOT3-OAM-MIB: View SNMP OID List / Download MIB

This module describes an authoritative enterprise- specific Simple Network Management Protocol (SNMP) Management Information Base (MIB): For the Birds Of Prey Product Line Ethernet in First Mile OAM. The right to make changes in specification and other information contained in this document without prior notice is reserved. No liability shall be assumed for any incidental, indirect, special, or consequential damages whatsoever arising from or related to this document or the information contained herein. Vendors, end-users, and other interested parties are granted non-exclusive license to use this specification in connection with management of the products for which it is intended to be used. Copyright (C) 1995-2002 Alcatel Internetworking, Incorporated ALL RIGHTS RESERVED WORLDWIDE

Branch for 802.3ah OAM Notifications.

A alaDot3OamThresholdEventClear notification is sent when a local or remote threshold crossing event is recovered. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance in the dot3OamEventLogTable.

A alaDot3OamNonThresholdEventClear notification is sent when a local or remote non-threshold crossing event is recovered. The OAM entity can be derived from extracting the ifIndex from the variable bindings. The objects in the notification correspond to the values in a row instance of the dot3OamEventLogTable.

Branch For 802.3ah OAM Objects.

The administrative status requested by management for 802.3ah. The value enabled(1) indicates that 802.3ah should be enabled on this device, on all ports for which it has not been specifically disabled. When disabled(2), 802.3ah is disabled on all ports and all 802.3ah packets will be dropped. A transition from disabled(2) to enabled(1) will cause a reset of all 802.3ah state machines on all ports. Enumeration: 'disabled': 2, 'enabled': 1.

Defines the global clear statistics control for Dot3OAM. The value reset (1) indicates that clear all statistic counters related to all ports in the system. By default, this object contains a zero value. Enumeration: 'default': 0, 'reset': 1.

Defines the global clear event logs control for Dot3OAM. The value reset (1) indicates that clear all event logs related to all ports in the system. By default, this object contains a zero value. Enumeration: 'default': 0, 'reset': 1.

Defines the global clear variable transactions control for Dot3OAM. The value reset (1) indicates that clear all transactions related to all ports in the system. By default, this object contains a zero value. Enumeration: 'default': 0, 'reset': 1.

This object is used to set the number of PDUs that will be sent, when OAM needs to send multiple event notification PDUs.

This table contains the primary controls and status for the OAM capabilities of an Ethernet like interface. There will be one row in this table for each Ethernet like interface in the system that supports the OAM functions defined in [802.3ah].

An entry in the table, containing information on the Ethernet OAM function for a single Ethernet like interface. Entries in the table are created automatically for each interface supporting Ethernet OAM. The status of the row entry can be determined from dot3OamOperStatus. A alaDot3OamEntry is indexed in the alaDot3OamTable by the ifIndex object of the Interfaces MIB.

This object is used to set the timer in seconds to restart the discovery process if no PDUs are received in this time frame.

This object is used to set the interval between two OAMPDUs

This object is used to fetch the next available transaction id required for MIB variable retrieval requests on this interface. To read the remote entity's MIB variables, a unique transaction id is generated for each request. The administrator first needs to get the next available transaction id for the interface, and provide this as index to the alaDot3OamRetrieveRequestTable.

This table contains controls for the loopback state of the local link as well as indicating the status of the loopback function. There is one entry in this table for each entry in dot3OamTable that supports loopback functionality (where dot3OamFunctionsSupported includes the loopbackSupport bit set).

An entry in the table, containing information on the L1 ping. One record/entry shall be maintained per interface. This record shall be automatically created when L1 ping is initiated for the first time on the interface. Subsequent ping operations shall replace the record. Loopback capabilities of the interface can be determined from the dot3OamLoopbackStatus object.

This object is used to set the number of frames to be transmitted from the interface during L1 ping.

This object is used to set the delay between two frames transmitted during L1 ping.

This object is used to start the L1 ping operation. Operator can set only start(1) value and setting of start(1) value is not valid if object value is start(1) or running(2). Whenever efm gets enabled on any port, this object has default(0) value. Default(0) value implies that loopback session has not been started even for a single time. Running(2) is corresponding to the state, when L1 ping is going on, operationSuccessful(3) is corresponding to the state, when L1 ping operation is done successfully. operationUnsuccessful(4) is corresponding to state when operation gets failed due to some reason. Enumeration: 'default': 0, 'start': 1, 'running': 2, 'operationSuccessful': 3, 'operationUnsuccessful': 4.

This object is used to keep the actual frames sent during last L1 ping operation.

This object is used to keep the number of frames received during last L1 ping operation.

This object is used to keep the average delay taken by frames during last L1 ping.

This table contains statistics for the OAM function on a particular Ethernet like interface. There is an entry in the table for every entry in the dot3OamStatsTable. The counters in this table are defined as 32-bit entries to match the counter size as defined in [802.3ah]. Given the OA protocol is a slow protocol, the counters increment at a slow rate.

An entry in the table, containing statistics information on the Ethernet OAM function for a single Ethernet like interface. Entries are automatically created for every entry in the dot3OamStatsTable. Counters are maintained across transitions in dot3OamOperStatus.

Reset all statistics parameters corresponding to this port By default, this objects contains a zero value. Enumeration: 'default': 0, 'reset': 1.

This table records a history of the events that have occurred at the Ethernet OAM level. These events can include locally detected events, which may result in locally generated OAMPDUs, and remotely detected events, which are detected by the OAM peer entity and signaled to the local entity via Ethernet OAM. Ethernet OAM events can be signaled by Event Notification OAMPDUs or by the flags field in any OAMPDU.

An entry in the dot3OamEventLogTable. Entries are automatically created whenever Ethernet OAM events occur at the local OAM entity, and when Event Notification OAMPDUs are received at the local OAM entity (indicating events have occurred at the peer OAM entity). The size of the table is implementation dependent, but when the table becomes full, older events are automatically deleted to make room for newer events. The table index dot3OamEventLogIndex increments for each new entry, and when the maximum value is reached the value restarts at zero.

Reset all event logs corresponding to this port By default, this objects contains a zero value. Enumeration: 'default': 0, 'reset': 1.

A table containing MIB variable retrieval request information

A 802.3ah MIB variable retrieval request entry.

This object is used to set the available transaction id for retrieving the remote MIB variable for this interface. The value for this is obtained from alaDot3OamNextTransactionId, which is part of alaDot3OamTable.

This object is used to set the branch to reference the MIB object to be retrieved. This is set to attribute, package or object depending upon the request for getting the MIB variables. Enumeration: 'attribute': 7, 'object': 3, 'package': 4.

This object is used to set the leaf to reference the MIB object to be retrieved.

This object is used to check the status of a MIB request, Active means that the request is currently in progress), failed means that the request has failed, and success means that the request returned successfully. Enumeration: 'active': 1, 'failed': 2, 'success': 3.

Row Status for initiating a MIB retrieval request.

Reset all variable transactions corresponding to this port By default, this objects contains a zero value. Enumeration: 'default': 0, 'reset': 1.

A table containing MIB variable retrieval response information

A 802.3ah MIB variable retrieval response entry.

The branch to reference the MIB object retrieved. Enumeration: 'attribute': 7, 'object': 3, 'package': 4.

The leaf to reference the MIB object retrieved.

The value of the retrived attribute.

Branch for 802.3ah Module MIB Subsystem Conformance Information.

Branch for 802.3ah Module MIB Subsystem Units of Conformance.

Collection of objects for management of 802.3ah Base Group.

Collection of objects for management of 802.3ah Port Configuration Table.

Collection of objects for management of 802.3ah Loopback Table.

Collection of objects for management of 802.3ah Statistics Table.

Collection of objects for management of 802.3ah Event Log Table.

Collection of objects for management of 802.3ah Retrieve Request Table.

Collection of objects for management of 802.3ah Retrieve Response Table.

A collection of notifications used by 802.3ah to signal to a management entity that local or remote events have recovered on a specified Ethernet link.

Branch for 802.3ah Module MIB Subsystem Compliance Statements.

Compliance statement for 802.3ah.