TIMETRA-APS-MIB: View SNMP OID List / Download MIB
VENDOR: NOKIA
Home | MIB: TIMETRA-APS-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
timetraAPSMIBModule | 1.3.6.1.4.1.6527.1.1.3.29 |
This document is the SNMP MIB module to manage and provision APS functionality for the Alcatel-Lucent SROS products. This includes extensions to the APS MIB defined in RFC 3498. Copyright 2004-2011 Alcatel-Lucent. All rights reserved. Reproduction of this document is authorized on the condition that the foregoing copyright notice is included. This SNMP MIB module (Specification) embodies Alcatel-Lucent's proprietary intellectual property. Alcatel-Lucent retains all title and ownership in the Specification, including any revisions. Alcatel-Lucent grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Alcatel-Lucent products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Alcatel-Lucent makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification. |
||
tApsMIBConformance | 1.3.6.1.4.1.6527.3.1.1.29 | |||
tmnxApsMIBCompliances | 1.3.6.1.4.1.6527.3.1.1.29.1 | |||
tApsMIBCompliance | 1.3.6.1.4.1.6527.3.1.1.29.1.1 |
The compliance statement for revision 1.0 of TIMETRA-APS-MIB. |
||
tApsMIBComplianceV4v0 | 1.3.6.1.4.1.6527.3.1.1.29.1.2 |
The compliance statement for revision 4.0 of the Alcatel-Lucent SROS series systems. |
||
tApsMIBComplianceV7v0 | 1.3.6.1.4.1.6527.3.1.1.29.1.3 |
The compliance statement for revision 7.0 of the Alcatel-Lucent SROS series systems. |
||
tApsMIBComplianceV8v0 | 1.3.6.1.4.1.6527.3.1.1.29.1.4 |
The compliance statement for revision 8.0 of the Alcatel-Lucent SROS series systems. |
||
tApsMIBComplianceV9v0 | 1.3.6.1.4.1.6527.3.1.1.29.1.5 |
The compliance statement for release 9.0 of Alcatel-Lucent SROS series systems. |
||
tmnxApsMIBGroups | 1.3.6.1.4.1.6527.3.1.1.29.2 | |||
tmnxApsSwitchCommand | 1.3.6.1.4.1.6527.3.1.1.29.2.1 |
The group of objects for management of aps switch command applicable to the aps groups implementing linear APS 1+1 architecture. |
||
tmnxApsChanStatus | 1.3.6.1.4.1.6527.3.1.1.29.2.2 |
The group of objects for management of status information applicable to the APS channels implementing linear APS 1+1 architecture. |
||
tmnxApsNotifications | 1.3.6.1.4.1.6527.3.1.1.29.2.3 |
A collection of SONET liner APS notifications. |
||
tmnxApsNotificationsV4v0 | 1.3.6.1.4.1.6527.3.1.1.29.2.4 |
A collection of SONET liner APS notifications for revision 4.0 of the Alcatel-Lucent SROS series systems. |
||
tmnxApsMcGroup | 1.3.6.1.4.1.6527.3.1.1.29.2.5 |
The group of objects for the configuration of a Multi-Chassis APS group. |
||
tmnxApsConfigGroup | 1.3.6.1.4.1.6527.3.1.1.29.2.6 |
The group of objects for the configuration of APS groups added for revision 7.0 of the Alcatel-Lucent SROS series systems. |
||
tmnxApsConfigV8v0Group | 1.3.6.1.4.1.6527.3.1.1.29.2.7 |
The group of objects for the configuration of APS groups added for revision 8.0 of the Alcatel-Lucent SROS series systems. |
||
tmnxApsGroupCommandV9v0Group | 1.3.6.1.4.1.6527.3.1.1.29.2.8 |
The group of APS group command objects for release 9.0 of Alcatel-Lucent SROS series systems. |
||
tmnxApsNotificationsV9v0Group | 1.3.6.1.4.1.6527.3.1.1.29.2.9 |
The group of APS notifications for release 9.0 of Alcatel-Lucent SROS series systems. |
||
tApsMIBObjs | 1.3.6.1.4.1.6527.3.1.2.29 | |||
tApsCommandTable | 1.3.6.1.4.1.6527.3.1.2.29.1 | no-access |
This table augments the apsCommandTable of the APS-MIB |
|
1.3.6.1.4.1.6527.3.1.2.29.1.1 | no-access |
A conceptual row in the tApsCommandTable. This row exists only if the associated apsConfigEntry is active. |
||
tApsExerciseCommandResult | 1.3.6.1.4.1.6527.3.1.2.29.1.1.1 | integer | read-only |
Stores the result of the last exercise command on the APS group and channel specified by the index values. When read this object returns 4(unknown) if no exercise command has been written to this channel since initialization. Enumeration: 'failed': 2, 'preempted': 3, 'passed': 1, 'unknown': 4. |
tApsChanStatusTable | 1.3.6.1.4.1.6527.3.1.2.29.2 | no-access |
This table augments the apsChanConfigTable of the APS-MIB. It contains status information in addition to those mentioned in apsChanStatusTable of the APS MIB. |
|
1.3.6.1.4.1.6527.3.1.2.29.2.1 | no-access |
A conceptual row in the tApsChanStatusTable. This row exists only if the associated apsChanConfigEntry exists. |
||
tApsChanTxLaisState | 1.3.6.1.4.1.6527.3.1.2.29.2.1.1 | integer | read-only |
The current state of the 7x50 APS forced Tx-LAIS on the specified APS channel. Note that the 7x50 products always receive and transmit on the same (active) APS channel. For a Multi-Chassis (MC) APS or a unidirectional APS group, the 7x50 product may transmit (Tx) L-AIS on the inactive APS channel to force the remote end to receive traffic on the 7x50 selected active APS channel. The state clear indicates that the 7x50 product currently doesn't transmit any forced LAIS on the APS channel. The state momentary indicates that the 7x50 product has transmitted forced LAIS on the APS channel for a moment(e.g. 100 msec). The state persistent indicates that the 7x50 product has been persistently transmitting forced LAIS on the APS channel. Enumeration: 'clear': 0, 'persistent': 2, 'momentary': 1. |
tApsMcConfigTable | 1.3.6.1.4.1.6527.3.1.2.29.3 | no-access |
This table augments the apsConfigTable of the APS-MIB. |
|
1.3.6.1.4.1.6527.3.1.2.29.3.1 | no-access |
A conceptual row in the tApsMcConfigTable. This row exists only if the associated apsConfigEntry is active. |
||
tApsMcNeighborAddrType | 1.3.6.1.4.1.6527.3.1.2.29.3.1.1 | inetaddresstype | read-write |
The value of object tApsMcNeighborAddrType specifies the address type of the neighbor's ip-address as specified by tApsMcNeighborAddr in the case of Multi-Chassis APS architecture. |
tApsMcNeighborAddr | 1.3.6.1.4.1.6527.3.1.2.29.3.1.2 | inetaddress | read-write |
The value of tApsMcNeighborAddr variable specifies the neighbor's ip-address only on a Multi-Chassis APS where the working and protect circuits are configured on different routers. The value of tApsMcNeighborAddr set to 0.0.0.0, implies that this APS group is configured as a Single-Chassis APS group. The route to the neighbor must not traverse the MC-APS member (working or protect) circuits. It is recommended that the address configured here is on a shared network between the routers that own the working and protect circuits. By default no neighbor address is configured and both the working and protect circuits are to be configured on the same router (i.e. Single-Chassis APS). |
tApsMcAdvertiseInterval | 1.3.6.1.4.1.6527.3.1.2.29.3.1.3 | unsigned32 | read-write |
The value of tApsMcAdvertiseInterval specifies the time interval, in 100s of milliseconds, between 'I am operational' messages sent by both protect and working circuits to their neighbor for Multi-Chassis APS. The value of tApsMcAdvertiseInterval is valid only for a Multi-Chassis APS as indicated by the value of tApsMcNeighborAddr not set to 0.0.0.0. |
tApsMcHoldTime | 1.3.6.1.4.1.6527.3.1.2.29.3.1.4 | unsigned32 | read-write |
The value of tApsMcHoldTime specifies how much time can pass, in 100s of milliseconds, without receiving an advertise packet from the neighbor before the Multi-Chassis signaling link is considered not operational. It is usually 3 times the value of tApsMcAdvertiseInterval. The value of tApsMcAdvertiseInterval is valid only for a Multi-Chassis APS as indicated by the value of tApsMcNeighborAddr not set to 0.0.0.0. |
tApsMcStatusTable | 1.3.6.1.4.1.6527.3.1.2.29.4 | no-access |
tApsMcStatusTable augments the apsConfigTable of the APS-MIB. It contains status information in addition to those mentioned in apsStatusTable of the APS MIB. |
|
1.3.6.1.4.1.6527.3.1.2.29.4.1 | no-access |
A conceptual row in the tApsMcStatusTable. This row exists only if the associated apsConfigEntry exists. |
||
tApsMcApsCtlLinkState | 1.3.6.1.4.1.6527.3.1.2.29.4.1.1 | integer | read-only |
The value of tApsMcApsCtlLinkState indicates the current state of the 7x50 Multi-Chassis (MC) APS Group Control Link. Note that for a Single-Chassis APS group the state is always up. The state 'up' indicates that the 7x50 MC-APS controller has received a valid control message from its neighboring router within the last tApsMcHoldTime interval, and the MC-APS control link is considered as operational. The state 'dnSignalingFailure' indicates that the 7x50 MC-APS controller hasn't received any control message from its neighboring router or vice-versa within the last tApsMcHoldTime interval.The MC-APS control link is considered as operationally down. The state 'dnIncompatibleNbr' indicates that the 7x50 MC-APS controller has received a control message from a neighboring router within the last tApsMcHoldTime interval, but the member circuit type (i.e. working/protection) of the neighboring router is not compatible with that of the local router. The MC-APS control link is considered as operationally down. Enumeration: 'dnIncompatibleNbr': 2, 'dnSignalingFailure': 1, 'up': 0. |
tApsConfigTable | 1.3.6.1.4.1.6527.3.1.2.29.5 | no-access |
tApsConfigTable augments the apsConfigTable of the APS-MIB. It contains configuration information in addition to those mentioned in apsConfigTable of the APS MIB. |
|
1.3.6.1.4.1.6527.3.1.2.29.5.1 | no-access |
A conceptual row in the tApsConfigTable. This row exists only if the associated apsConfigEntry exists. |
||
tApsProtectionType | 1.3.6.1.4.1.6527.3.1.2.29.5.1.1 | integer | read-write |
The value of tApsProtectionType specifies the protection type of the APS group. The valid options are: onePlusOneSignalling (1) -- Signalling is 1+1, data is 1:1. onePlusOne (2) -- Both signalling and data is 1+1. Enumeration: 'onePlusOne': 2, 'onePlusOneSignalling': 1. |
tApsLineSFHoldTime | 1.3.6.1.4.1.6527.3.1.2.29.5.1.2 | unsigned32 | read-write |
The value of tApsLineSFHoldTime specifies the time, in 100s of milliseconds, that the APS group will remain operational up before reporting a Line Signal Failure due to lais or b2err-sf. |
tApsLineSDHoldTime | 1.3.6.1.4.1.6527.3.1.2.29.5.1.3 | unsigned32 | read-write |
The value of tApsLineSDHoldTime specifies the time, in 100s of milliseconds, that the APS group will remain operational up before reporting a Line Signal Degredation due to b2err-sd. |
tApsRdiAlarmGeneration | 1.3.6.1.4.1.6527.3.1.2.29.5.1.4 | integer | read-write |
The value of tApsRdiAlarmGeneration specifies the method used to generate RDI alarms on all levels (line, path) for the APS physical protecting/working ports referenced by apsChanConfigIfIndex. The modification of the tApsRdiAlarmGeneration value is limited to an APS port with no protecting/working ports, otherwise an INCONSISTENT VALUE error is returned. The available enumerations for tApsRdiAlarmGeneration are: - suppress - RDI alarms are not generated on any level. - circuit - RDI alarms are H/W generated independently on each working and protect circuit on RX failure of that circuit. Enumeration: 'suppress': 0, 'circuit': 1. |
tApsGroupCommandTable | 1.3.6.1.4.1.6527.3.1.2.29.6 | no-access |
tApsGroupCommandTable augments APS-MIB::apsConfigTable. It contains command information in addition to the configuration information in APS-MIB::apsConfigTable. |
|
1.3.6.1.4.1.6527.3.1.2.29.6.1 | no-access |
A conceptual row in tApsGroupCommandTable. This row exists only if the associated apsConfigEntry exists. |
||
tApsAnnexBCommandSwitch | 1.3.6.1.4.1.6527.3.1.2.29.6.1.1 | integer | read-write |
The value of tApsAnnexBCommandSwitch specifies the Annex B supported APS switch command applied to the APS group. The supported values: 'noCmd(1)' -- no command was applied to the group since system -- initialization. 'lockout(2)' -- lockout the APS group. 'clearLockout(3)' -- clear the lockout. Sets to value 'lockout(2)' or 'clearLockout(3)' will be rejected with error inconsistentValue if APS-MIB::apsConfigMode is not equal to 'onePlusOneOptimized(4)'. If 'noCmd(1)' is used in a write operation a wrongValue error is returned. When read this object returns the last command written or 'noCmd(1)'. Enumeration: 'noCmd': 1, 'lockout': 2, 'clearLockout': 3. |
tApsNotificationsPrefix | 1.3.6.1.4.1.6527.3.1.3.29 | |||
tApsNotifications | 1.3.6.1.4.1.6527.3.1.3.29.0 | |||
tApsModeMismatchClear | 1.3.6.1.4.1.6527.3.1.3.29.0.1 |
The tApsModeMismatchClear notification is generated when a mode mismatch condition, indicated by the 'modeMismatch(0)' bit of APS-MIB::apsStatusCurrent, is cleared. |
||
tApsChannelMismatchClear | 1.3.6.1.4.1.6527.3.1.3.29.0.2 |
The tApsChannelMismatchClear notification is generated when a channel mismatch condition, indicated by the 'channelMismatch(1)' bit of APS-MIB::apsStatusCurrent, is cleared. |
||
tApsPSBFClear | 1.3.6.1.4.1.6527.3.1.3.29.0.3 |
The tApsPSBFClear notification is generated when a PSBF (Protection Switch Byte Failure) condition, indicated by the 'psbf(2)' bit of APS-MIB::apsStatusCurrent, is cleared. |
||
tApsFEPLFClear | 1.3.6.1.4.1.6527.3.1.3.29.0.4 |
The tApsFEPLFClear notification is generated when a FEPLF (Far-End Protection-Line Failure) condition, indicated by the 'feplf(3)' bit of APS-MIB::apsStatusCurrent, is cleared. |
||
tApsLocalSwitchCommandSet | 1.3.6.1.4.1.6527.3.1.3.29.0.5 |
The tApsLocalSwitchCommandSet is generated when any of the following APS switch commands are set on APS-MIB::apsCommandSwitch in the local node. The switch commands are 'lockoutOfProtection', 'forcedSwitchWorkToProtect', 'forcedSwitchProtectToWork', 'manualSwitchWorkToProtect', 'manualSwitchProtectToWork'. |
||
tApsLocalSwitchCommandClear | 1.3.6.1.4.1.6527.3.1.3.29.0.6 |
The tApsLocalSwitchCommandClear notification is generated when an APS switch command in the local node gets cleared. Note that a switch command in the local node can be cleared either due to set of the 'clear' switch command on APS-MIB::apsCommandSwitch in the local node, or due to presence of a higher priority condition in the local or remote node. |
||
tApsRemoteSwitchCommandSet | 1.3.6.1.4.1.6527.3.1.3.29.0.7 |
The tApsRemoteSwitchCommandSet is generated when the received K1 byte (APS-MIB::apsStatusK1K2Rcv) from a peer indicates that an APS switch command just got set on APS-MIB::apsCommandSwitch in the remote (peer) node. |
||
tApsRemoteSwitchCommandClear | 1.3.6.1.4.1.6527.3.1.3.29.0.8 |
The tApsRemoteSwitchCommandClear is generated when the received K1 byte (APS-MIB::apsStatusK1K2Rcv) from a peer indicates that an APS switch command just got cleared on an APS channel in the remote (peer) node. |
||
tApsMcApsCtlLinkStateChange | 1.3.6.1.4.1.6527.3.1.3.29.0.9 |
tApsMcApsCtlLinkStateChange notification is generated when there is a change in the value of tApsMcApsCtlLinkState. |
||
tApsChanTxLaisStateChange | 1.3.6.1.4.1.6527.3.1.3.29.0.10 |
tApsChanTxLaisStateChange notification is generated when there is a change in the value of tApsChanTxLaisState. |
||
tApsPrimaryChannelChange | 1.3.6.1.4.1.6527.3.1.3.29.0.11 |
tApsPrimaryChannelChange notification is generated when there is a switch of the primary APS channel. Object apsStatusK1K2Trans indicates the new primary APS channel. |