GMPLS-TE-STD-MIB Table View

The gmplsTunnelTable sparsely extends the mplsTunnelTable of
MPLS-TE-STD-MIB.  It allows GMPLS tunnels to be created between
an LSR and a remote endpoint, and existing tunnels to be
reconfigured or removed.
          
Note that only point-to-point tunnel segments are supported,
although multipoint-to-point and point-to-multipoint
connections are supported by an LSR acting as a cross-connect.
Each tunnel can thus have one out-segment originating at this
LSR and/or one in-segment terminating at this LSR.
          
The row status of an entry in this table is controlled by the
mplsTunnelRowStatus in the corresponding entry in the
mplsTunnelTable.  When the corresponding mplsTunnelRowStatus has
value active(1), a row in this table may not be created or
modified.
          
The exception to this rule is the
gmplsTunnelAdminStatusInformation object, which can be modified
while the tunnel is active.

The gmplsTunnelHopTable sparsely extends the mplsTunnelHopTable
of MPLS-TE-STD-MIB.  It is used to indicate the Explicit Labels
to be used in an explicit path for a GMPLS tunnel defined in the
mplsTunnelTable and gmplsTunnelTable, when it is established
using signaling.  It does not insert new hops, but does define
new values for hops defined in the mplsTunnelHopTable.
          
Each row in this table is indexed by the same indexes as in the
mplsTunnelHopTable.  It is acceptable for some rows in the
mplsTunnelHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table.
          
The storage type for this entry is given by the value
of mplsTunnelHopStorageType in the corresponding entry in the
mplsTunnelHopTable.
          
The row status of an entry in this table is controlled by
mplsTunnelHopRowStatus in the corresponding entry in the
mplsTunnelHopTable.  That is, it is not permitted to create a row
          
in this table, or to modify an existing row, when the
corresponding mplsTunnelHopRowStatus has the value active(1).

The gmplsTunnelARHopTable sparsely extends the
mplsTunnelARHopTable of MPLS-TE-STD-MIB.  It is used to
indicate the labels currently in use for a GMPLS tunnel
defined in the mplsTunnelTable and gmplsTunnelTable, as
reported by the signaling protocol.  It does not insert
new hops, but does define new values for hops defined in
the mplsTunnelARHopTable.
          
Each row in this table is indexed by the same indexes as in the
mplsTunnelARHopTable.  It is acceptable for some rows in the
mplsTunnelARHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table.
          
Note that since the information necessary to build entries
within this table is not provided by some signaling protocols
and might not be returned in all cases of other signaling
protocols, implementation of this table and the
mplsTunnelARHopTable is optional.  Furthermore, since the
information in this table is actually provided by the
signaling protocol after the path has been set up, the entries
in this table are provided only for observation, and hence,
all variables in this table are accessible exclusively as
read-only.

The gmplsTunnelCHopTable sparsely extends the
mplsTunnelCHopTable of MPLS-TE-STD-MIB.  It is used to indicate
additional information about the hops of a GMPLS tunnel defined
in the mplsTunnelTable and gmplsTunnelTable, as computed by a
constraint-based routing protocol, based on the
mplsTunnelHopTable and the gmplsTunnelHopTable.
          
Each row in this table is indexed by the same indexes as in the
mplsTunnelCHopTable.  It is acceptable for some rows in the
mplsTunnelCHopTable to have corresponding entries in this table
and some to have no corresponding entry in this table.
          
Please note that since the information necessary to build
entries within this table may not be supported by some LSRs,
implementation of this table is optional.
          
Furthermore, since the information in this table is actually
provided by a path computation component after the path has been
computed, the entries in this table are provided only for
observation, and hence, all objects in this table are accessible
exclusively as read-only.

This table augments the gmplsTunnelTable to provide
per-tunnel packet performance information for the reverse
direction of a bidirectional tunnel.  It can be seen as
supplementing the mplsTunnelPerfTable, which augments the
mplsTunnelTable.
          
For links that do not transport packets, these packet counters
cannot be maintained.  For such links, attempts to read the
objects in this table will return noSuchInstance.
          
A tunnel can be known to be bidirectional by inspecting the
gmplsTunnelDirection object.

This table augments the mplsTunnelTable.
          
This table provides per-tunnel information about errors.  Errors
may be detected locally or reported through the signaling
protocol.  Error reporting is not exclusive to GMPLS, and this
table may be applied in MPLS systems.
          
Entries in this table are not persistent over system resets
or re-initializations of the management system.