| tunnelIfLocalAddress |
.1.3.6.1.2.1.10.131.1.1.1.1.1 |
|
The address of the local endpoint of the tunnel (i.e., the
source address used in the outer IP header), or 0.0.0.0 if
unknown.
|
| tunnelIfRemoteAddress |
.1.3.6.1.2.1.10.131.1.1.1.1.2 |
|
The address of the remote endpoint of the tunnel (i.e., the
destination address used in the outer IP header), or 0.0.0.0
if unknown.
|
| tunnelIfEncapsMethod |
.1.3.6.1.2.1.10.131.1.1.1.1.3 |
|
The encapsulation method used by the tunnel. The value
direct indicates that the packet is encapsulated directly
within a normal IPv4 header, with no intermediate header,
and unicast to the remote tunnel endpoint (e.g., an RFC 2003
IP-in-IP tunnel, or an RFC 1933 IPv6-in-IPv4 tunnel). The
value minimal indicates that a Minimal Forwarding Header
(RFC 2004) is inserted between the outer header and the
payload packet. The value UDP indicates that the payload
packet is encapsulated within a normal UDP packet (e.g., RFC
1234). The remaining protocol-specific values indicate that
a header of the protocol of that name is inserted between
the outer header and the payload header.
|
| tunnelIfHopLimit |
.1.3.6.1.2.1.10.131.1.1.1.1.4 |
|
The TTL to use in the outer IP header. A value of 0
indicates that the value is copied from the payload's
header.
|
| tunnelIfSecurity |
.1.3.6.1.2.1.10.131.1.1.1.1.5 |
|
The method used by the tunnel to secure the outer IP
header. The value ipsec indicates that IPsec is used
between the tunnel endpoints for authentication or
encryption or both. More specific security-related
information may be available in a MIB for the security
protocol in use.
|
| tunnelIfTOS |
.1.3.6.1.2.1.10.131.1.1.1.1.6 |
|
The method used to set the high 6 bits of the TOS in the
outer IP header. A value of -1 indicates that the bits are
copied from the payload's header. A value of -2 indicates
that a traffic conditioner is invoked and more information
may be available in a traffic conditioner MIB. A value
between 0 and 63 inclusive indicates that the bit field is
set to the indicated value.
|
| tunnelConfigLocalAddress |
.1.3.6.1.2.1.10.131.1.1.2.1.1 |
|
The address of the local endpoint of the tunnel, or 0.0.0.0
if the device is free to choose any of its addresses at
tunnel establishment time.
|
| tunnelConfigRemoteAddress |
.1.3.6.1.2.1.10.131.1.1.2.1.2 |
|
The address of the remote endpoint of the tunnel.
|
| tunnelConfigEncapsMethod |
.1.3.6.1.2.1.10.131.1.1.2.1.3 |
|
The encapsulation method used by the tunnel.
|
| tunnelConfigID |
.1.3.6.1.2.1.10.131.1.1.2.1.4 |
|
An identifier used to distinguish between multiple tunnels
of the same encapsulation method, with the same endpoints.
If the encapsulation protocol only allows one tunnel per set
of endpoint addresses (such as for GRE or IP-in-IP), the
value of this object is 1. For encapsulation methods (such
as L2F) which allow multiple parallel tunnels, the manager
is responsible for choosing any ID which does not conflict
with an existing row, such as choosing a random number.
|
| tunnelConfigIfIndex |
.1.3.6.1.2.1.10.131.1.1.2.1.5 |
|
If the value of tunnelConfigStatus for this row is active,
then this object contains the value of ifIndex corresponding
to the tunnel interface. A value of 0 is not legal in the
active state, and means that the interface index has not yet
been assigned.
|
| tunnelConfigStatus |
.1.3.6.1.2.1.10.131.1.1.2.1.6 |
|
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.
|
