All MIBs › TUNNEL-MIB › tunnelInetConfigStatus
tunnelInetConfigStatus
Module: TUNNEL-MIB
OID (symbolic): TUNNEL-MIB::tunnelInetConfigStatus
OID (numeric): 1.3.6.1.2.1.10.131.1.1.3.1.7
Node type: OBJECT-TYPE
Type: RowStatus
Access: read-create
Description: The status of this row, by which new entries may be created, or old entries deleted from this table. The agent need not support setting this object to createAndWait or notInService since there are no other writable objects in this table, and writable objects in rows of corresponding tables such as the tunnelIfTable may be modified while this row is active.
To create a row in this table for an encapsulation method which does not support multiple parallel tunnels with the same endpoints, the management station should simply use a tunnelInetConfigID of 1, and set tunnelInetConfigStatus to createAndGo. For encapsulation methods such as L2F which allow multiple parallel tunnels, the management station may select a pseudo-random number to use as the tunnelInetConfigID and set tunnelInetConfigStatus to createAndGo. In the event that this ID is already in use and an inconsistentValue is returned in response to the set operation, the management station should simply select a new pseudo-random number and retry the operation.
Creating a row in this table will cause an interface index to be assigned by the agent in an implementation-dependent manner, and corresponding rows will be instantiated in the ifTable and the
tunnelIfTable. The status of this row will become active as soon as the agent assigns the interface index, regardless of whether the interface is operationally up.
Deleting a row in this table will likewise delete the corresponding row in the ifTable and in the tunnelIfTable.
What is tunnelInetConfigStatus?
This read-create RowStatus column creates or deletes a row in the version-neutral tunnel configuration table, which in turn causes the agent to create or delete corresponding rows in the ifTable and tunnelIfTable and assign an interface index. Admins use it to provision a new tunnel via SNMP: setting a tunnel ID of 1 and this status to createAndGo works for single-tunnel encapsulation methods like GRE or IP-in-IP, while methods like L2F that allow multiple parallel tunnels require choosing a pseudo-random tunnel ID to avoid collisions. For example, an admin provisioning a new GRE tunnel would set the local and remote address objects, an ID of 1, and this status object to createAndGo in a single SNMP request to bring the new tunnel interface into existence.
OID Breakdown
Upper-level ancestors (7 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.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.10.131 | tunnelMIB | TUNNEL-MIB |
| 1.3.6.1.2.1.10.131.1 | tunnelMIBObjects | TUNNEL-MIB |
| 1.3.6.1.2.1.10.131.1.1 | tunnel | TUNNEL-MIB |
| 1.3.6.1.2.1.10.131.1.1.3 | tunnelInetConfigTable | TUNNEL-MIB |
| 1.3.6.1.2.1.10.131.1.1.3.1 | tunnelInetConfigEntry | TUNNEL-MIB |
| 1.3.6.1.2.1.10.131.1.1.3.1.7 | tunnelInetConfigStatus | TUNNEL-MIB |