| OID | 1.3.6.1.2.1.10.131.1.1.2.1.6 |
| Module | TUNNEL-MIB (CISCO) |
| Nom | tunnelConfigStatus |
| Acces | readwrite |
| Status | deprecated |
| 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 tunnelConfigID of 1, and
set tunnelConfigStatus 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 tunnelConfigID and
set tunnelConfigStatus 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.
Since this object does not support IPv6, it is
deprecated in favor of tunnelInetConfigStatus. |
| Syntaxe | RowStatus (SNMPv2-TC) |
| Module | TUNNEL-MIB (ietf) |
| Nom | tunnelConfigStatus |
| Acces | readwrite |
| Status | deprecated |
| 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 tunnelConfigID of 1, and
set tunnelConfigStatus 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 tunnelConfigID and
set tunnelConfigStatus 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.
Since this object does not support IPv6, it is
deprecated in favor of tunnelInetConfigStatus. |
| Syntaxe | RowStatus (SNMPv2-TC) |
| Module | TUNNEL-MIB (Alcatel) |
| Nom | tunnelConfigStatus |
| Acces | readwrite |
| Status | deprecated |
| 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
tunnelConfigID of 1, and set tunnelConfigStatus 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 tunnelConfigID
and set tunnelConfigStatus to createAndGo. In the event
that this ID is already in use and an inconsistent value 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.
Since this object does not support IPv6, it is deprecated
in favor of tunnelInetConfigStatus. |
| Syntaxe | RowStatus (SNMPv2-TC) |