All MIBs › TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB › tmnxRouteNHAdminControlApply
tmnxRouteNHAdminControlApply
Module: TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB
OID (symbolic): TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB::tmnxRouteNHAdminControlApply
OID (numeric): 1.3.6.1.4.1.6527.3.1.2.90.1.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The value of tmnxRouteNHAdminControlApply specifies the copying of tmnxRouteNextHopObjs tables from one instance of tmnxRouteNHTemplateVersion to another. This object reads as 'none(1)' when not editing this table and 'initialize(2)' when editing it.
When set to 'initialize(2)', the rows in tmnxRouteNextHopObjs tables with the version index set to 'admin' are set to the values with the index set to 'oper' in the same tables. Any uncommitted changes are lost, so setting this value corresponds to both BEGIN-TRANSACTION and ABORT-TRANSACTION.
When set to 'commit(3)' (END-TRANSACTION), all of the rows in tmnxRouteNextHopObjs tables with the version set to 'admin' are copied to the same rows with the index set to 'oper'. Then, the new values are applied in the system.
In this way, the (expensive) application can be performed at one time, ensuring a coherent route next-hop configuration.
What is tmnxRouteNHAdminControlApply?
This object controls the two-phase transaction process for editing route next-hop template tables, copying the 'admin' version of the configuration to or from the 'oper' (operational) version. Admins set it to initialize(2) to begin editing, copying operational values into the admin version and discarding any prior uncommitted edits, and to commit(3) to apply all pending admin-version changes to the live operational configuration at once. After configuring several next-hop templates in the admin version, an admin would set tmnxRouteNHAdminControlApply to commit(3) to apply all those changes to the router's live routing behavior in one coherent operation.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.90.1.1.3 snmpwalk -v2c -c public <target> TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB::tmnxRouteNHAdminControlApply
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.90.1.1.3.1 snmpget -v2c -c public <target> TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB::tmnxRouteNHAdminControlApply.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.6527.3.1.2.90.1.1.3.1 i <value>
Start monitoring Nokia/Alcatel-Lucent 7750 SR, 7950 XRS core router (route next-hop template/SRLG config status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB::tmnxRouteNHAdminControlApply OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750 SR, 7950 XRS core router (route next-hop template/SRLG config status) from a single console.
OID Breakdown
Upper-level ancestors (10 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.6527 | timetra | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3 | timetraProducts | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1 | tmnxSRMIB | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1.2 | tmnxSRObjs | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6527.3.1.2.90 | tmnxRouteNextHop | TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB |
| 1.3.6.1.4.1.6527.3.1.2.90.1 | tmnxRouteNextHopObjs | TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB |
| 1.3.6.1.4.1.6527.3.1.2.90.1.1 | tmnxRouteNHAdminControl | TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB |
| 1.3.6.1.4.1.6527.3.1.2.90.1.1.3 | tmnxRouteNHAdminControlApply | TIMETRA-ROUTE-NEXT-HOP-TEMPLATE-MIB |