DC-VPWS-MIB Table View

Table-centric layout grouping table, row, and column objects.

Tables
4
Rows
4
Columns
41
.1.3.6.1.4.1.629.10.19.1.1 · 1 row entry · 20 columns
Uses the mrv variant from /opt/observium/mibs/mrv.
Command help
Walk vpwsConfigTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DC-VPWS-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-VPWS-MIB::vpwsConfigTable'
VPWS Configuration Table.
          
This table specifies information for configuring and
monitoring Virtual Private Wire Services (VPWS).
          
Note that any changes made to this table when
vpwsStatusOperStatus is 'up' may cause the VPWS to be
deactivated (vpwsStatusOperStatus 'down') before the change
is made.  The VPWS will then attempt to re-activate.  The
VPWS may or may not re-activate depending on the validity of
the new configuration.
vpwsConfigEntry row .1.3.6.1.4.1.629.10.19.1.1.1
Represents a configured VPWS.
Column Syntax OID
Index identifying the VPWS instance.
DC-MASTER-TCNumericIndex
Type Constraints:
range: 1..2147483647
.1.3.6.1.4.1.629.10.19.1.1.1.2
The row status for this VPWS Configuration Table entry,
used to create and destroy table entries.
SNMPv2-TCRowStatusr/w
Type Values:
1active
2notInService
3notReady
4createAndGo
5createAndWait
6destroy
Description:
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of …
.1.3.6.1.4.1.629.10.19.1.1.1.3
The administrative status of this VPWS instance, used to
activate and deactivate the VPWS instance.
DC-MASTER-TCAdminStatusr/w
Type Values:
1adminStatusUp
2adminStatusDown
.1.3.6.1.4.1.629.10.19.1.1.1.4
The current operational state of this VPWS instance.

If the operational status is 'up' then the VPWS is
programmed in the data plane.
DC-MASTER-TCNpgOperStatus
Type Values:
1operStatusUp
2operStatusDown
3operStatusGoingUp
4operStatusGoingDown
5operStatusActFailed
8operStatusFailed
10operStatusFailedPerm
11operStatusFailing
.1.3.6.1.4.1.629.10.19.1.1.1.5
A textual name of the VPWS instance. If there is no local
name, or this field is otherwise not applicable, then this
field MUST contain a zero-length octet string.
SNMP-FRAMEWORK-MIBSnmpAdminStringr/w
Type Constraints:
range: 0..255
.1.3.6.1.4.1.629.10.19.1.1.1.6
A textual string containing information about the VPWS
instance. If there is no information for this VPWS
instance, then this field MUST contain a zero-length octet
string.
SNMP-FRAMEWORK-MIBSnmpAdminStringr/w
Type Constraints:
range: 0..255
.1.3.6.1.4.1.629.10.19.1.1.1.7
The auto-discovery protocol used by this VPWS.

Changing this value will cause an interruption to data
flow for this VPWS.
DC-L2VPN-MIBL2vpnADTyper/w
Type Values:
1none
2bgp
.1.3.6.1.4.1.629.10.19.1.1.1.8
The pseudowire signaling protocol used for auto-created
PWs on this VPWS.

If vpwsConfigADType is set to 'none' this field is
ignored.

If vpwsConfigADType is set to 'bgp' this field must be …
DC-L2VPN-MIBL2vpnSigTyper/w
Type Values:
1none
2ldp
3bgp
.1.3.6.1.4.1.629.10.19.1.1.1.9
The MPLS pseudowire encapsulation type used by this VPWS.

Changing this value will cause an interruption to data
flow for this VPWS.
IANA-PWE3-MIBIANAPwTypeTCr/w
Type Values:
0other
1frameRelayDlciMartiniMode
2atmAal5SduVcc
3atmTransparent
4ethernetTagged
5ethernet
6hdlc
7ppp
8cem
9atmCellNto1Vcc
10atmCellNto1Vpc
11ipLayer2Transport
12atmCell1to1Vcc
13atmCell1to1Vpc
14atmAal5PduVcc
15frameRelayPortMode
16cep
17e1Satop
18t1Satop
19e3Satop
20t3Satop
21basicCesPsn
22basicTdmIp
23tdmCasCesPsn
24tdmCasTdmIp
25frDlci
32767wildcard
.1.3.6.1.4.1.629.10.19.1.1.1.10
The layer 2 MTU of this VPWS.

When using auto-discovery and signaling, this specifies
the signaled layer 2 MTU.

Changing this value will cause an interruption to data
flow for this VPWS.
Unsigned32r/w
Constraints:
range: 64-9192
.1.3.6.1.4.1.629.10.19.1.1.1.11
Whether or not the pseudowires use a PW control word.

Changing this value will cause an interruption to data
flow for this VPWS.
SNMPv2-TCTruthValuer/w
Type Values:
1true
2false
Description:
Represents a boolean value.
.1.3.6.1.4.1.629.10.19.1.1.1.12
Whether or not the pseudowires must provide sequenced
delivery of traffic.

Changing this value will cause an interruption to data
flow for this VPWS.
SNMPv2-TCTruthValuer/w
Type Values:
1true
2false
Description:
Represents a boolean value.
.1.3.6.1.4.1.629.10.19.1.1.1.13
The route distinguisher for this VPWS. See [RFC4364] for
a complete definition of a route distinguisher.

This is only used if BGP auto-discovery is enabled
(vpwsConfigADType = bgp).

Changi…
DC-L2VPN-MIBBgpRouteDistinguisherr/w
Type Constraints:
range: 8
.1.3.6.1.4.1.629.10.19.1.1.1.14
The VPN ID to advertise as a BGP extended community, or
zero if none.

If the VPWS uses BGP auto-discovery and LDP signaling
(vpwsConfigADType = bgp and vpwsConfigSigType = ldp) then
this must be set to a …
DC-L2VPN-MIBBgpExtendedCommunityr/w
Type Constraints:
range: 8
.1.3.6.1.4.1.629.10.19.1.1.1.15
The local VPWS site ID, or zero if not specified.

This is only used if BGP auto-discovery is enabled
(vpwsConfigADType = bgp). It can be used with BGP or LDP
signaling.

If auto-discovery i…
DC-L2VPN-MIBL2vpnVeIdOrZeror/w
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.629.10.19.1.1.1.16
The preference that the local PE router is the designated
forwarder for this VPWS. High values are preferred to low
values.

This is only used if BGP auto-discovery is enabled
(vpwsConfigADType = bgp). I…
SNMPv2-SMIUnsigned32r/w
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.629.10.19.1.1.1.17
The size of the label blocks for this VPWS.

This is only used when using BGP auto-discovery with BGP
signaling (vpwsConfigADType = bgp and
vpwsConfigSigType = bgp).

The only currently-permi…
Unsigned32r/w
Constraints:
range: 2-2
range: 4-4
range: 8-8
range: 16-16
.1.3.6.1.4.1.629.10.19.1.1.1.18
Whether or not the BGP NLRI for this VPWS will include a
Circuit Status Vector TLV.

This is only used when using BGP auto-discovery with BGP
signaling (vpwsConfigADType = bgp and
vpwsConfigSigType = bgp).…
SNMPv2-TCTruthValuer/w
Type Values:
1true
2false
Description:
Represents a boolean value.
.1.3.6.1.4.1.629.10.19.1.1.1.19
This field specifies whether mismatches of MTU size with
remote PE routers should be ignored for this VPWS.

If this field is false, PWs will not be established to
remote PE routers that signal a different…
SNMPv2-TCTruthValuer/w
Type Values:
1true
2false
Description:
Represents a boolean value.
.1.3.6.1.4.1.629.10.19.1.1.1.20
This field specifies whether mismatches of encapsulation
type with remote PE routers should be ignored for this
VPWS.

If this field is false, PWs will not be established to
remote PE routers that signal a…
SNMPv2-TCTruthValuer/w
Type Values:
1true
2false
Description:
Represents a boolean value.
.1.3.6.1.4.1.629.10.19.1.1.1.21
.1.3.6.1.4.1.629.10.19.1.2 · 1 row entry · 3 columns
Uses the mrv variant from /opt/observium/mibs/mrv.
Command help
Walk vpwsStatusTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DC-VPWS-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-VPWS-MIB::vpwsStatusTable'
VPWS Status Table (read-only).
          
This table reports the status of Virtual Private Wire
Services (VPWS).
vpwsStatusEntry row .1.3.6.1.4.1.629.10.19.1.2.1
Represents a VPWS.
Column Syntax OID
The current operational state of this VPWS instance.

If the operational status is 'up' then the VPWS has
been successfully activated.
DC-MASTER-TCNpgOperStatus
Type Values:
1operStatusUp
2operStatusDown
3operStatusGoingUp
4operStatusGoingDown
5operStatusActFailed
8operStatusFailed
10operStatusFailedPerm
11operStatusFailing
.1.3.6.1.4.1.629.10.19.1.2.1.3
The number of Virtual Circuits currently present in this VPWS
instance.

Specifically, this is number of local Attachment Circuits
(ACs) bound to active pseudowires in this VPWS instance.
SNMPv2-SMIGauge32
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.629.10.19.1.2.1.4
Whether or not the PE router is currently the elected
Designated Forwarder for this VPWS instance.

This field is only used if BGP auto-discovery is enabled
(vpwsConfigADType = bgp). Otherwise, it is set …
SNMPv2-TCTruthValue
Type Values:
1true
2false
Description:
Represents a boolean value.
.1.3.6.1.4.1.629.10.19.1.2.1.5
.1.3.6.1.4.1.629.10.19.1.3 · 1 row entry · 8 columns
Uses the mrv variant from /opt/observium/mibs/mrv.
Command help
Walk vpwsBindCfgTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DC-VPWS-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-VPWS-MIB::vpwsBindCfgTable'
VPWS Binding Config Table.
          
This table configures bindings of Attachment Circuits (ACs)
to VPWS instances, pseudowires (PWs), and layer 2 local
switching rules (hairpins).
          
Multiple ACs can be associated with a single VPWS.
          
If the binding corresponds to two VPWS sites that are hosted
by a single PE router, a hairpin can be created between the
two sites' ACs.  Otherwise, a PW set is used to establish
connectivity.
          
The method for associating ACs with PWs depends on whether
auto-discovery is enabled.
          
-  If auto-discovery is disabled (vpwsConfigADType = none)
   then PWs are provisioned in the pwTable.  In this case,
   each AC is bound to a set of provisioned PWs, that are
   identified by a PW Set Index.  PW redundancy
   configuration is not yet supported by L2VM provisioned
   PWs, therefore the PW Set will have a single member, and
   this set index can be set to the pwIndex in the pwTable
   of that PW.  This form of binding is known as a
   double-sided binding since the PW(s) must be provisioned
   in the pwTable at each end of the virtual circuit.
          
-  If auto-discovery is enabled (vpwsConfigADType = bgp)
   then the VPWS service establishes a PW between each pair
   of VPWS sites within the VPWS, using BGP auto-discovery
   to determine which PE router hosts each VPWS site.  In
   this case, each AC is bound to a PW that is identified by
   the local and remote site IDs.  The PE router creates
   these PWs automatically as a result of the BGP
   auto-discovery process.  This form of configuration is
   sometimes known as 'colored pools'.  In this approach the
   operator configures a pool of ACs for each local site,
   and each pool is identified by a site ID or 'color'.  The
   VPWS service establishes a PW between each pair of
   'colored pools' (VPWS sites), and each AC is bound to a
   PW associated with the same 'colored pool' (local site
   ID).
          
-  If auto-discovery is enabled (vpwsConfigADType = bgp)
   then an AC can still be bound to a PW that is provisioned
   in the pwTable MIB, for example to incorporate a legacy
   PE router that does not support auto-discovery into the
   VPWS.
          
The method for associating ACs with other ACs in a hairpin
also depends on whether auto-discovery is enabled.
          
-  If auto-discovery is disabled, the AC is bound to another
   AC directly, by configuring its interface index in this
   table.  In this case the PW set index can also optionally
   be specified to provide redundant connectivity to the
   other site.
          
-  If auto-discovery is enabled, the BGP auto-discovery
   process ascertains that this PE router also hosts the
   remote site, and automatically binds the two ACs.
          
In either case a row in this table only establishes
unidirectional connectivity for a hairpin.  For full
connectivity, the opposite direction will need to be
configured in the same manner (though this need not be in
the same VPWS instance).
          
Each VPWS Binding is configured with a PW binding type,
given by vpwsBindCfgPwBindType, which specifies whether the
PW Set to which the AC is bound is identified by a PW Set
index and/or hairpin interface index (and so is provisioned)
or by a local and remote site ID (and so is auto-created as
a result of BGP auto-discovery).
          
This table is indexed on AC interface index to ensure that
each AC is only ever bound to a single VPWS.  The read-only
vpwsBindTable can be used to show the ACs bound to each
VPWS.
          
Note that changes to this table may cause the corresponding
AC to go operationally down as it may involve re-programming
the AC in the data plane.
vpwsBindCfgEntry row .1.3.6.1.4.1.629.10.19.1.3.1
Represents a configured VPWS binding.
Column Syntax OID
The row status for this VPWS Binding Configuration Table
entry, used to create and destroy table entries.
SNMPv2-TCRowStatusr/w
Type Values:
1active
2notInService
3notReady
4createAndGo
5createAndWait
6destroy
Description:
The RowStatus textual convention is used to manage the
creation and deletion of conceptual rows, and is used as the
value of the SYNTAX clause for the status column of a
conceptual row (as described in Section 7.7.1 of …
.1.3.6.1.4.1.629.10.19.1.3.1.3
The administrative status of this VPWS binding, used to
activate and deactivate the VPWS binding.
DC-MASTER-TCAdminStatusr/w
Type Values:
1adminStatusUp
2adminStatusDown
.1.3.6.1.4.1.629.10.19.1.3.1.4
The current operational status of this VPWS binding.

If the operational status is 'up' then the cross-connect
for this binding is programmed in the data plane.
DC-MASTER-TCNpgOperStatus
Type Values:
1operStatusUp
2operStatusDown
3operStatusGoingUp
4operStatusGoingDown
5operStatusActFailed
8operStatusFailed
10operStatusFailedPerm
11operStatusFailing
.1.3.6.1.4.1.629.10.19.1.3.1.5
Index identifying the VPWS instance.

This field must be set to a non-zero value before the VPWS
binding can go into operational status 'up'.

Changing this value will cause an interruption t…
DC-MASTER-TCNumericIndexOrZeror/w
Type Constraints:
range: 0..2147483647
.1.3.6.1.4.1.629.10.19.1.3.1.6
The VPWS pseudowire (PW) binding type. This field specifies
the identifiers used for the PW to which the AC is bound.

If the PW is provisioned in the pwTable, then it is identified
by an index into the p…
DC-L2VPN-MIBL2vpnPwBindTyper/w
Type Values:
1pwMibIndex
2lclRmtVeId
.1.3.6.1.4.1.629.10.19.1.3.1.7
Index for the set of PWs to which the AC should be bound.
The AC is bound to every PW in the pwTable with
pwRedundancySetId set to this value.

This is only used if the PW is provisioned in the pwTable
MIB…
Unsigned32r/w
Constraints:
range: 0-1073741823
.1.3.6.1.4.1.629.10.19.1.3.1.8
The remote VPWS site ID of the PW to bind the AC to, or zero
if not specified.

This is only used if the pseudowire (PW) is created as a
result of BGP auto-discovery, that is if vpwsBindCfgPwBindType
= lcl…
DC-L2VPN-MIBL2vpnVeIdOrZeror/w
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.629.10.19.1.3.1.9
Interface index that the AC should be bound to directly,
via a layer 2 local switching rule (hairpin). Only
relevant if the local PE hosts both VPWS sites concerned
in this binding; otherwise, should be set to zero.
IF-MIBInterfaceIndexOrZeror/w
Type Constraints:
range: 0..2147483647
Description:
This textual convention is an extension of the
InterfaceIndex convention. The latter defines a greater
than zero value used to identify an interface or interface
sub-layer in the managed system. This extension permits…
.1.3.6.1.4.1.629.10.19.1.3.1.10
.1.3.6.1.4.1.629.10.19.1.4 · 1 row entry · 10 columns
Uses the mrv variant from /opt/observium/mibs/mrv.
Command help
Walk vpwsBindTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'DC-VPWS-MIB' -M '/opt/observium/mibs/mrv:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-VPWS-MIB::vpwsBindTable'
VPWS Binding Table (read-only).
          
This table displays the Attachment Circuit (AC) bindings
in a VPWS.
          
Bindings are configured in the vpwsBindCfgTable.
          
This table is read-only.
vpwsBindEntry row .1.3.6.1.4.1.629.10.19.1.4.1
Represents a VPWS binding.
Column Syntax OID
The current operational status of this VPWS binding.

If the operational status is 'up' then the cross-connect
for this binding is programmed in the data plane.
DC-MASTER-TCNpgOperStatus
Type Values:
1operStatusUp
2operStatusDown
3operStatusGoingUp
4operStatusGoingDown
5operStatusActFailed
8operStatusFailed
10operStatusFailedPerm
11operStatusFailing
.1.3.6.1.4.1.629.10.19.1.4.1.4
If the AC is bound to a pseudowire (PW) that is provisioned in
the pwTable, then this field is set to pwMibIndex.

If the AC is bound to a pseudowire that has been created as a
result of BGP auto-discovery…
DC-L2VPN-MIBL2vpnPwBindType
Type Values:
1pwMibIndex
2lclRmtVeId
.1.3.6.1.4.1.629.10.19.1.4.1.5
The PW set index of the PWs bound to this AC. The AC is
bound to the (redundant) set of PWs corresponding to rows
in the pwTable with pwRedundancySetId set to this value.

If the vpwsBindPwBindType is pwM…
DC-MASTER-TCNumericIndex
Type Constraints:
range: 1..2147483647
.1.3.6.1.4.1.629.10.19.1.4.1.6
The interface index that has been assigned for the set of
pseudowires to which this AC is bound.
IF-MIBInterfaceIndex
Type Constraints:
range: 1..2147483647
Description:
A unique value, greater than zero, for each interface or
interface sub-layer in the managed system. It is
recommended that values are assigned contiguously starting
from 1. The value for each interface sub-layer must …
.1.3.6.1.4.1.629.10.19.1.4.1.7
The local VPWS site ID to which this AC is bound, or zero
if not applicable.

This is only relevant if vpwsBindPwBindType = lclRmtVeId.

If vpwsBindPwBindType = lclRmtVeId then the AC is boun…
DC-L2VPN-MIBL2vpnVeIdOrZero
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.629.10.19.1.4.1.8
The remote VPWS site ID to which this AC is bound, or zero
if not applicable.

This is only relevant if vpwsBindPwBindType = lclRmtVeId.

If vpwsBindPwBindType = lclRmtVeId then the AC is bou…
DC-L2VPN-MIBL2vpnVeIdOrZero
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.629.10.19.1.4.1.9
The interface index of the AC bound to this AC directly in
a layer 2 local switching rule (hairpin).

If the vpwsBindPwBindType is pwMibIndex, then this value
will match the configured vpwsBindCfgLclSwitch…
IF-MIBInterfaceIndex
Type Constraints:
range: 1..2147483647
Description:
A unique value, greater than zero, for each interface or
interface sub-layer in the managed system. It is
recommended that values are assigned contiguously starting
from 1. The value for each interface sub-layer must …
.1.3.6.1.4.1.629.10.19.1.4.1.10
The remote route distinguisher, or null if not known.

This is the route distinguisher of the best BGP route
advertising the remote VPWS site ID.

This is only relevant if vpwsBindPwBindType …
DC-L2VPN-MIBBgpRouteDistinguisher
Type Constraints:
range: 8
.1.3.6.1.4.1.629.10.19.1.4.1.11
The address family of the remote address.

This is only relevant if vpwsBindPwBindType = lclRmtVeId.
INET-ADDRESS-MIBInetAddressType
Type Values:
0unknown
1ipv4
2ipv6
3ipv4z
4ipv6z
16dns
25l2vpn
.1.3.6.1.4.1.629.10.19.1.4.1.12
The remote address, or null if not known.

This is the address of the router advertising the best
BGP route to the remote VPWS site ID.

This is only relevant if vpwsBindPwBindType = lclRmtVe…
INET-ADDRESS-MIBInetAddress
Type Constraints:
range: 0..255
.1.3.6.1.4.1.629.10.19.1.4.1.13