| OID symbolic | OID numeric | Type | Access | Description |
|---|
| pwVcMplsMIB | 1.3.6.1.4.1.99999.53.0 | | | This MIB module complements the PW MIB module for PW
operation over MPLS.
Copyright (C) The Internet Society (date). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices.
-- RFC Ed.: replace yyyy with actual RFC number & remove this note |
| pwVcMplsObjects | 1.3.6.1.4.1.99999.53.0.1 | | | |
| pwVcMplsTable | 1.3.6.1.4.1.99999.53.0.1.1 | | not-accessible | This table controls MPLS specific parameters when the PW is
going to be carried over MPLS PSN. |
| pwVcMplsEntry | 1.3.6.1.4.1.99999.53.0.1.1.1 | | not-accessible | A row in this table represents parameters specific to MPLS
PSN for a pseudo wire (PW). The row is created
automatically by the local agent if the pwVcPsnType is
MPLS. It is indexed by pwVcIndex, which uniquely
identifying a singular PW. |
| BIT pwVcMplsMplsType | 1.3.6.1.4.1.99999.53.0.1.1.1.1 | Bits | read-write | Set by the operator to indicate the outer tunnel types, if
exists. mplsTe(0) is used if the outer tunnel was set-up
by MPLS-TE, and mplsNonTe(1) is used the outer tunnel was
set up by LDP or manually. Combination of mplsTe(0) and
mplsNonTe(1) may exist together.
vcOnly(2) is used if there is no outer tunnel label, i.e.
in static provisioning without MPLS tunnel. vcOnly(2)
cannot be combined with mplsNonTe(1) or mplsTe(0). |
| INT pwVcMplsExpBitsMode | 1.3.6.1.4.1.99999.53.0.1.1.1.2 | INTEGER | read-write | Set by the operator to indicate the way the PW shim label
EXP bits are to be determined. The value of outerTunnel(1)
is used where there is an outer tunnel - pwVcMplsMplsType
is mplsTe(0) or mplsNonTe(1). Note that in this case there
is no need to mark the PW label with the EXP bits since the
PW label is not visible to the intermediate nodes.
If there is no outer tunnel, specifiedValue(2) indicates
that the value is specified by pwVcMplsExpBits, and
serviceDependant(3) indicates that the EXP bits are setup
based on a rule specified in the emulated service specific
tables, for example when the EXP bits are a function of
802.1p marking for Ethernet emulated service. |
| U32 pwVcMplsExpBits | 1.3.6.1.4.1.99999.53.0.1.1.1.3 | Unsigned32 | read-write | Set by the operator to indicate the MPLS EXP bits to be
used on the PW shim label if pwVcMplsExpBitsMode is
specifiedValue(2), zero otherwise. |
| U32 pwVcMplsTtl | 1.3.6.1.4.1.99999.53.0.1.1.1.4 | Unsigned32 | read-write | Set by the operator to indicate the PW TTL value to be
used on the PW shim label. |
| OID pwVcMplsLocalLdpID | 1.3.6.1.4.1.99999.53.0.1.1.1.5 | MplsLdpIdentifier | read-write | The local LDP identifier of the LDP entity creating
this PW in the local node. As the PW labels are always
set from the per platform label space, the last two octets
in the LDP ID MUST be always both zeros. |
| OID pwVcMplsLocalLdpEntityID | 1.3.6.1.4.1.99999.53.0.1.1.1.6 | MplsLsrIdentifier | read-write | The local node LDP Entity ID of the LDP entity creating
this PW. Should return the value of all zeros if not
used. |
| OID pwVcMplsPeerLdpID | 1.3.6.1.4.1.99999.53.0.1.1.1.7 | MplsLdpIdentifier | read-only | The peer LDP identifier as identified from the LDP
session. Should return the value of zero if not applicable
or not known yet. |
| STO pwVcMplsStorageType | 1.3.6.1.4.1.99999.53.0.1.1.1.8 | StorageType | read-write | This variable indicates the storage type for this row. |
| pwVcMplsOutboundTable | 1.3.6.1.4.1.99999.53.0.1.2 | | not-accessible | This table reports and configure the current outbound MPLS
tunnels (i.e. toward the PSN) or the physical interface in
case of PW label only that carry the PW traffic. It also
reports the current outer tunnel and LSP which forward the
PW traffic. |
| pwVcMplsOutboundEntry | 1.3.6.1.4.1.99999.53.0.1.2.1 | | not-accessible | A row in this table configured the outer tunnel used for
carrying the PW traffic toward the PSN.
In the case of PW label only, it configures the interface
that will carry the PW traffic.
An entry in this table augments the pwVcMplsEntry, and is
created automatically when the corresponding row has been
created by the agent in the pwVcMplsEntry.
This table points to the appropriate MPLS MIB module.
In the MPLS-TE case, the 3 variables relevant to the
indexing of a TE tunnel head-end are used as in
MPLS-TE-STD-MIB are to be configured, and the tunnel
instance indicates the LSP that is currently in use for
forwarding the traffic.
In case of signaled Non-TE MPLS (an outer tunnel label
assigned by LDP) the table points to the XC entry in the
LSR-STD-MIB. If the Non-TE MPLS tunnel is manually
configured, the operator configure the XC pointer to this
tunnel.
In case of PW label only (no outer tunnel) the ifIndex of
the port to carry the PW is configured here.
It is possible to associate a PW to one TE tunnel head-end
and a non-TE tunnel together. An indication in this table
will report the currently active one, In addition, in the
TE case the table reports the active tunnel instance
(i.e. the specific LSP in use). |
| MPL pwVcMplsOutboundLsrXcIndex | 1.3.6.1.4.1.99999.53.0.1.2.1.1 | MplsIndexType | read-write | This object is applicable if pwVcMplsMplsType mplsNonTe(1)
bit is set, and MUST return a value of zero otherwise.
If the outer tunnel is signaled, the object is read-only
and indicate the XC index in the MPLS-LSR-STD-MIB of the
outer tunnel toward the peer. Otherwise (tunnel is set-up
manually) the operator define the XC index of the manually
created outer tunnel through this object. |
| MPL pwVcMplsOutboundTunnelIndex | 1.3.6.1.4.1.99999.53.0.1.2.1.2 | MplsTunnelIndex | read-write | This object is applicable if pwVcMplsMplsType mplsTe(0)
bit is set, and MUST return a value of zero otherwise.
It is Part of set of indexes for outbound tunnel.
The operator set this object to represent the desired
tunnel head-end toward the peer for carrying the PW
traffic. |
| MPL pwVcMplsOutboundTunnelInstance | 1.3.6.1.4.1.99999.53.0.1.2.1.3 | MplsTunnelInstanceIndex | read-only | This object is applicable if pwVcMplsMplsType mplsTe(0)
bit is set, and MUST return a value of zero otherwise.
It indicates the actual tunnel instance that is currently
active and carrying the PW traffic - it should return the
value of zero until if the information from the MPLS-TE
application is not yet known. |
| OID pwVcMplsOutboundTunnelLclLSR | 1.3.6.1.4.1.99999.53.0.1.2.1.4 | MplsLsrIdentifier | read-write | This object is applicable if pwVcMplsMplsType mplsTe(0)
bit is set, and MUST return a value of all zeros otherwise.
It is part of set of indexes for outbound tunnel.
The operator set this object to represent the desired
tunnel head-end toward the peer for carrying the PW
traffic. |
| OID pwVcMplsOutboundTunnelPeerLSR | 1.3.6.1.4.1.99999.53.0.1.2.1.5 | MplsLsrIdentifier | read-write | This object is applicable if pwVcMplsMplsType mplsTe(0)
bit is set, and MUST return a value of zero otherwise.
It is part of set of indexes for outbound tunnel. It is
typically equal to pwVcPeerAddr. |
| NUM pwVcMplsOutboundIfIndex | 1.3.6.1.4.1.99999.53.0.1.2.1.6 | InterfaceIndexOrZero | read-write | This object is applicable if pwVcMplsMplsType mplsTe(0)
bit is set, and MUST return a value of zero otherwise.
The operator configure the ifIndex of the outbound port
in this case. |
| INT pwVcMplsOutboundTunnelTypeInUse | 1.3.6.1.4.1.99999.53.0.1.2.1.7 | INTEGER | read-only | This object indicates the current tunnel that is carrying
the PW traffic.
The value of notYetKnown(1) should be used if the agent is
currently unable to determine which tunnel or interface is
carrying the PW, for example because both tunnels are in
operational status down. |
| pwVcMplsInboundTable | 1.3.6.1.4.1.99999.53.0.1.3 | | not-accessible | This table indicates the PW LDP XC entry in the
MPLS-LSR-STD-MIB for signaled PWs. |
| pwVcMplsInboundEntry | 1.3.6.1.4.1.99999.53.0.1.3.1 | | not-accessible | A row in this table is created by the agent
for each signaled PW, and shows the XC index related to
the PW signaling in the inbound direction in the
MPLS-LSR-STD-MIB that controls and display the information
for all the LDP signaling processes in the local node. |
| MPL pwVcMplsInboundXcIndex | 1.3.6.1.4.1.99999.53.0.1.3.1.1 | MplsIndexType | read-only | The XC index representing this PW in the inbound
direction. Should return the value of zero if the
information is not yet known. |
| pwVcMplsNonTeMappingTable | 1.3.6.1.4.1.99999.53.0.1.4 | | not-accessible | This table indicates outbound Tunnel to a PW in non-TE
applications, maps the PW to it's (inbound) XC entry, and
indicates the PW to physical interface mapping for a PW
label to physical interface a PW label is in use without
outer tunnel. |
| pwVcMplsNonTeMappingEntry | 1.3.6.1.4.1.99999.53.0.1.4.1 | | not-accessible | A row in this table displays the association
between the PW and
- it's non-TE MPLS outbound outer Tunnel or,
- it's XC entry in the MPLS-LSR-STD-MIB,
- it's physical interface if there is no outer tunnel
(PW label only) and manual configuration.
Rows are created in this table by the by the
agent depending on the setting of pwVcMplsMplsType:
- If pwVcMplsMplsType mplsNonTe(1) bit is set, the agent
creates a row for the outbound direction
(pwVcMplsNonTeMappingDirection set to psnBound(1)).
The pwVcMplsNonTeMappingXcIndex holds the XC index in the
MPLS-LSR-STD-MIB of the PSN bound outer tunnel.
pwVcMplsNonTeMappingIfIndex MUST be zero for this row.
- If pwVcMplsMplsType vcOnly(2) bit is set, the agent
creates a row for the outbound direction
(pwVcMplsNonTeMappingDirection set to psnBound(1)).
The pwVcMplsNonTeMappingIfIndex holds the ifIndex of the
physical port this PW will use in the outbound direction.
pwVcMplsNonTeMappingXcIndex MUST be zero for this row.
- If the PW has been set-up by signaling protocol (i.e.
pwVcOwner equal pwIdFecSignaling(2) or
genFecSignaling(3)), the agent creates a row for the
inbound direction (pwVcMplsNonTeMappingDirection set to
fromPsn(2)).
The pwVcMplsNonTeMappingXcIndex holds the XC index in the
MPLS-LSR-STD-MIB of the PW LDP generated XC entry.
pwVcMplsNonTeMappingIfIndex MUST be zero for this row.
An application can use this table to quickly retrieve the
PW carried over specific non-TE MPLS outer tunnel or
physical interface. |
| INT pwVcMplsNonTeMappingDirection | 1.3.6.1.4.1.99999.53.0.1.4.1.1 | INTEGER | not-accessible | Index for the conceptual XC row identifying Tunnel to PW
mappings, indicating the direction of packet flow the entry
is related too.
psnBound(1) indicates that the entry is related to
packets toward the PSN.
fromPsn(2) indicates that the entry is related to
packets coming from the PSN. |
| MPL pwVcMplsNonTeMappingXcIndex | 1.3.6.1.4.1.99999.53.0.1.4.1.2 | MplsIndexType | not-accessible | See the description clause of pwVcMplsNonTeMappingEntry for
the usage guidelines of this object. |
| NUM pwVcMplsNonTeMappingIfIndex | 1.3.6.1.4.1.99999.53.0.1.4.1.3 | InterfaceIndexOrZero | not-accessible | See the description clause of pwVcMplsNonTeMappingEntry for
the usage guidelines of this object. |
| PWV pwVcMplsNonTeMappingVcIndex | 1.3.6.1.4.1.99999.53.0.1.4.1.4 | PwVcIndexType | read-only | The value that represent the PW in the pwVcTable. |
| pwVcMplsTeMappingTable | 1.3.6.1.4.1.99999.53.0.1.5 | | not-accessible | This table enable the retrieval of a PW association to the
outbound MPLS tunnel for MPLS-TE applications. |
| pwVcMplsTeMappingEntry | 1.3.6.1.4.1.99999.53.0.1.5.1 | | not-accessible | A row in this table represents the association
between a PW and it's MPLS-TE outer (head-end) Tunnel.
An application can use this table to quickly retrieve the
list of the PWs that are configured on a specific MPLS TE
outer tunnel.
The pwVcMplsTeMappingTunnelInstance reports the actual
LSP out of the tunnel head-end that is currently
forwarding the traffic.
The table in indexed by the head-end indexes of a TE
tunnel and the PW index. |
| MPL pwVcMplsTeMappingTunnelIndex | 1.3.6.1.4.1.99999.53.0.1.5.1.1 | MplsTunnelIndex | not-accessible | Primary index for the conceptual row identifying the
MPLS-TE tunnel that is carrying the PW traffic. |
| MPL pwVcMplsTeMappingTunnelInstance | 1.3.6.1.4.1.99999.53.0.1.5.1.2 | MplsTunnelInstanceIndex | not-accessible | This object identify the MPLS-TE LSP that is carrying the
PW traffic. Should return the value of zero if the
information of the specific LSP is not yet known.
Note that based on the recommendation in the
MPLS-TC-STD-MIB, instance index 0 should refer to the
configured tunnel interface. |
| OID pwVcMplsTeMappingTunnelPeerLsrID | 1.3.6.1.4.1.99999.53.0.1.5.1.3 | MplsLsrIdentifier | not-accessible | Identifies the Peer LSR when the outer tunnel is MPLS-TE
based. |
| OID pwVcMplsTeMappingTunnelLocalLsrID | 1.3.6.1.4.1.99999.53.0.1.5.1.4 | MplsLsrIdentifier | not-accessible | Identifies the local LSR. |
| PWV pwVcMplsTeMappingVcIndex | 1.3.6.1.4.1.99999.53.0.1.5.1.5 | PwVcIndexType | read-only | The value that represent the PW in the pwVcTable. |
| pwVcMplsConformance | 1.3.6.1.4.1.99999.53.0.2 | | | |
| pwVcMplsGroups | 1.3.6.1.4.1.99999.53.0.2.1 | | | |
| pwVcMplsGroup | 1.3.6.1.4.1.99999.53.0.2.1.1 | | | Collection of objects needed for PW over MPLS PSN
configuration. |
| pwVcMplsOutboundMainGroup | 1.3.6.1.4.1.99999.53.0.2.1.2 | | | Collection of objects needed for outbound association of
PW and MPLS tunnel. |
| pwVcMplsOutboundTeGroup | 1.3.6.1.4.1.99999.53.0.2.1.3 | | | Collection of objects needed for outbound association of
PW and MPLS TE tunnel. |
| pwVcMplsInboundGroup | 1.3.6.1.4.1.99999.53.0.2.1.4 | | | Collection of objects needed for inbound PW presentation.
This group MUST be supported if PW signaling through LDP is
used. |
| pwVcMplsMappingGroup | 1.3.6.1.4.1.99999.53.0.2.1.5 | | | Collection of objects needed for mapping association of
PW and MPLS tunnel. |
| pwVcMplsCompliances | 1.3.6.1.4.1.99999.53.0.2.2 | | | |
| pwMplsModuleFullCompliance | 1.3.6.1.4.1.99999.53.0.2.2.1 | | | The compliance statement for agents that provide full
support for PW-MPLS MIB Module. Such devices can
then be monitored and also be configured using
this MIB module. |
| pwMplsModuleReadOnlyCompliance | 1.3.6.1.4.1.99999.53.0.2.2.2 | | | The compliance statement for agents that provide read
only support for PW-MPLS MIB Module. Such devices can
then be monitored but cannot be configured using this
MIB module. |
