PW-STD-MIB

Monitored by Observium
        This MIB module contains managed object definitions for
pseudowire operation as in Bryant, S. and P. Pate, 'Pseudo
Wire Emulation Edge-to-Edge (PWE3) Architecture' [RFC3985],
Martini, L., et al, 'Pseudowire Setup and Maintenance Using
the Label Distribution Protocol (LDP)' [RFC4447], and
Townsley, M., et al, 'Layer Two Tunneling Protocol
(Version 3)' [RFC3931].
        
This MIB module enables the use of any underlying packet
switched network (PSN).  MIB nodules that will support
PW operations over specific PSN types are defined in
separate memos.
        
The indexes for this MIB module are also used to index the
PSN-specific tables and the PW-specific tables.  The PW Type
dictates which PW-specific MIB module to use.
        
Copyright (c) 2009 IETF Trust and the persons identified
as authors of the code.  All rights reserved.
        
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the following
conditions are met:
        
- Redistributions of source code must retain the above
  copyright notice, this list of conditions and the following
  disclaimer.
        
- Redistributions in binary form must reproduce the above
  copyright notice, this list of conditions and the following
  disclaimer in the documentation and/or other materials
  provided with the distribution.
        
- Neither the name of Internet Society, IETF or IETF Trust, nor
  the names of specific contributors, may be used to endorse or
  promote products derived from this software without specific
  prior written permission.
        
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
        
This version of this MIB module is part of RFC 5601;
see the RFC itself for full legal notices.
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Pseudowires
Explore Observium network monitoring
Source file
PW-STD-MIB
Last revised
Identity
pwStdMIB
Base OID
1.3.6.1.2.1.10.246
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'PW-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'PW-STD-MIB::pwStdMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'PW-STD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'PW-STD-MIB::pwStdMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (116)
15 directly used by Observium
.1.3.6.1.2.1.10.246
.1.3.6.1.2.1.10.246.0
.1.3.6.1.2.1.10.246.1
.1.3.6.1.2.1.10.246.1.1
.1.3.6.1.2.1.10.246.1.10
.1.3.6.1.2.1.10.246.1.11
.1.3.6.1.2.1.10.246.1.12
.1.3.6.1.2.1.10.246.1.12.1
.1.3.6.1.2.1.10.246.1.12.1.1
.1.3.6.1.2.1.10.246.1.12.1.2
.1.3.6.1.2.1.10.246.1.12.1.3
.1.3.6.1.2.1.10.246.1.12.1.4
.1.3.6.1.2.1.10.246.1.12.1.5
.1.3.6.1.2.1.10.246.1.12.1.6
.1.3.6.1.2.1.10.246.1.12.1.7
.1.3.6.1.2.1.10.246.1.2
.1.3.6.1.2.1.10.246.1.2.1
.1.3.6.1.2.1.10.246.1.2.1.1
.1.3.6.1.2.1.10.246.1.2.1.10
pwIfIndex r/w
.1.3.6.1.2.1.10.246.1.2.1.11
pwID OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.12
.1.3.6.1.2.1.10.246.1.2.1.13
.1.3.6.1.2.1.10.246.1.2.1.14
.1.3.6.1.2.1.10.246.1.2.1.15
.1.3.6.1.2.1.10.246.1.2.1.16
.1.3.6.1.2.1.10.246.1.2.1.17
Unsigned32
.1.3.6.1.2.1.10.246.1.2.1.18
.1.3.6.1.2.1.10.246.1.2.1.19
pwType OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.2
.1.3.6.1.2.1.10.246.1.2.1.20
.1.3.6.1.2.1.10.246.1.2.1.21
.1.3.6.1.2.1.10.246.1.2.1.22
.1.3.6.1.2.1.10.246.1.2.1.23
OctetString
.1.3.6.1.2.1.10.246.1.2.1.24
.1.3.6.1.2.1.10.246.1.2.1.25
.1.3.6.1.2.1.10.246.1.2.1.26
.1.3.6.1.2.1.10.246.1.2.1.27
Enumeration
.1.3.6.1.2.1.10.246.1.2.1.28
Bits
.1.3.6.1.2.1.10.246.1.2.1.29
pwOwner r/w
Enumeration
.1.3.6.1.2.1.10.246.1.2.1.3
pwOutboundLabel OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.30
pwInboundLabel OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.31
pwName OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.32
pwDescr OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.33
.1.3.6.1.2.1.10.246.1.2.1.34
pwUpTime OBS ✓
.1.3.6.1.2.1.10.246.1.2.1.35
.1.3.6.1.2.1.10.246.1.2.1.36
Enumeration
.1.3.6.1.2.1.10.246.1.2.1.37
pwOperStatus OBS ✓
.1.3.6.1.2.1.10.246.1.2.1.38
pwLocalStatus OBS ✓
.1.3.6.1.2.1.10.246.1.2.1.39
pwPsnType OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.4
Enumeration
.1.3.6.1.2.1.10.246.1.2.1.40
pwRemoteStatus OBS ✓
.1.3.6.1.2.1.10.246.1.2.1.41
.1.3.6.1.2.1.10.246.1.2.1.42
.1.3.6.1.2.1.10.246.1.2.1.43
pwRowStatus OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.44
.1.3.6.1.2.1.10.246.1.2.1.45
.1.3.6.1.2.1.10.246.1.2.1.46
.1.3.6.1.2.1.10.246.1.2.1.47
.1.3.6.1.2.1.10.246.1.2.1.48
.1.3.6.1.2.1.10.246.1.2.1.49
Integer32
.1.3.6.1.2.1.10.246.1.2.1.5
Integer32
.1.3.6.1.2.1.10.246.1.2.1.6
pwPeerAddrType OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.8
pwPeerAddr OBS ✓ r/w
.1.3.6.1.2.1.10.246.1.2.1.9
.1.3.6.1.2.1.10.246.1.3
.1.3.6.1.2.1.10.246.1.3.1
.1.3.6.1.2.1.10.246.1.3.1.1
.1.3.6.1.2.1.10.246.1.3.1.2
.1.3.6.1.2.1.10.246.1.3.1.3
.1.3.6.1.2.1.10.246.1.3.1.4
.1.3.6.1.2.1.10.246.1.3.1.5
.1.3.6.1.2.1.10.246.1.3.1.6
.1.3.6.1.2.1.10.246.1.3.1.7
.1.3.6.1.2.1.10.246.1.3.1.8
.1.3.6.1.2.1.10.246.1.4
.1.3.6.1.2.1.10.246.1.4.1
Integer32
.1.3.6.1.2.1.10.246.1.4.1.1
.1.3.6.1.2.1.10.246.1.4.1.10
.1.3.6.1.2.1.10.246.1.4.1.11
.1.3.6.1.2.1.10.246.1.4.1.2
.1.3.6.1.2.1.10.246.1.4.1.3
.1.3.6.1.2.1.10.246.1.4.1.4
.1.3.6.1.2.1.10.246.1.4.1.5
.1.3.6.1.2.1.10.246.1.4.1.6
.1.3.6.1.2.1.10.246.1.4.1.7
.1.3.6.1.2.1.10.246.1.4.1.8
.1.3.6.1.2.1.10.246.1.4.1.9
.1.3.6.1.2.1.10.246.1.5
.1.3.6.1.2.1.10.246.1.5.1
Unsigned32
.1.3.6.1.2.1.10.246.1.5.1.1
.1.3.6.1.2.1.10.246.1.5.1.2
.1.3.6.1.2.1.10.246.1.5.1.3
.1.3.6.1.2.1.10.246.1.5.1.4
.1.3.6.1.2.1.10.246.1.5.1.5
.1.3.6.1.2.1.10.246.1.5.1.6
.1.3.6.1.2.1.10.246.1.5.1.7
.1.3.6.1.2.1.10.246.1.6
.1.3.6.1.2.1.10.246.1.7
.1.3.6.1.2.1.10.246.1.7.1
.1.3.6.1.2.1.10.246.1.7.1.1
.1.3.6.1.2.1.10.246.1.7.1.2
.1.3.6.1.2.1.10.246.1.7.1.3
.1.3.6.1.2.1.10.246.1.7.1.4
.1.3.6.1.2.1.10.246.1.7.1.5
.1.3.6.1.2.1.10.246.1.8
.1.3.6.1.2.1.10.246.1.8.1
.1.3.6.1.2.1.10.246.1.8.1.1
.1.3.6.1.2.1.10.246.1.8.1.2
.1.3.6.1.2.1.10.246.1.8.1.3
.1.3.6.1.2.1.10.246.1.8.1.4
.1.3.6.1.2.1.10.246.1.8.1.5
.1.3.6.1.2.1.10.246.1.9
.1.3.6.1.2.1.10.246.2
.1.3.6.1.2.1.10.246.2.1
.1.3.6.1.2.1.10.246.2.2
Dependencies (12) 10 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (18)
Collection of objects that are required in all
implementations that support the PW MIB module.
.1.3.6.1.2.1.10.246.2.1.1
Collection of objects required for PW ID configuration
and signaling.
.1.3.6.1.2.1.10.246.2.1.2
Collection of objects required for generalized FEC

configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.3
Collection of objects required for FCS retention
configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.4
Collection of objects required for fragmentation
configuration and signaling.
.1.3.6.1.2.1.10.246.2.1.5
Collection of objects required for PW status configuration
and signaling.
.1.3.6.1.2.1.10.246.2.1.6
Collection of objects for getting the next available

index.
.1.3.6.1.2.1.10.246.2.1.7
Collection of objects for controlling the PW setup and
holding priority.
.1.3.6.1.2.1.10.246.2.1.8
Collection of objects for PW configuration as ifIndex.
.1.3.6.1.2.1.10.246.2.1.9
Collection of general objects needed for managing the
total running performance parameters.
.1.3.6.1.2.1.10.246.2.1.10
Collection of objects needed for a PW running 1-day

interval performance collection.
.1.3.6.1.2.1.10.246.2.1.11
Collection of general objects needed for managing the
interval performance parameters.
.1.3.6.1.2.1.10.246.2.1.12
Collection of 32-bit objects needed for PW performance
collection in 15-minute intervals.
.1.3.6.1.2.1.10.246.2.1.13
Collection of HC objects needed for PW performance
collection in 15-minute intervals.
.1.3.6.1.2.1.10.246.2.1.14
Collection of objects contained in the reverse
mapping tables.
.1.3.6.1.2.1.10.246.2.1.15
Collection of objects for controlling the PW
notifications.
.1.3.6.1.2.1.10.246.2.1.16
Collection of PW notifications objects.
.1.3.6.1.2.1.10.246.2.1.17
Collection of objects for use in implementations that
support the PW signaling.
.1.3.6.1.2.1.10.246.2.1.18
Compliance Statements (2)

OID .1.3.6.1.2.1.10.246.2.2.1
The compliance statement for agents that provide full
support for the PW MIB module. Such devices can
then be monitored and configured using

this MIB module.
Required groups
mandatory pwBasicGroup
mandatory pwPerformanceGeneralGroup
optional pwNotificationGroup This group is only mandatory for implementations
that can efficiently implement the notifications
contained in this group.
optional pwPwIdGroup This group is only mandatory for implementations
that support the PW ID FEC.
optional pwGeneralizedFecGroup This group is only mandatory for implementations
that support the generalized PW FEC.
optional pwFcsGroup This group is only mandatory for implementations
that support FCS retention.
optional pwFragGroup This group is only mandatory for implementations
that support PW fragmentation.
optional pwPwStatusGroup This group is only mandatory for implementations
that support PW status notification.
optional pwGetNextGroup This group is only mandatory for implementations
where the pwIndex may be any arbitrary value
and the EMS would require retrieval of the next
free index.
optional pwPriorityGroup This group is only mandatory for implementations
that support the controlling the PW setup and
holding priority.
optional pwAttachmentGroup This group is only mandatory for implementations
that support attachment of two PWs (PW stitching).
optional pwPeformance1DayIntervalGroup This group is only mandatory for implementations
that support PW performance gathering in 1-day
intervals.
optional pwPerformanceIntervalGeneralGroup This group is only mandatory for implementations
that support PW performance gathering in 15-
minute intervals.
optional pwPeformanceIntervalGroup This group is only mandatory for implementations
that support PW performance gathering in 15-
minute intervals.
optional pwHCPeformanceIntervalGroup This group is only mandatory for implementations
where at least one of the interval performance
counters wraps around too quickly based on the
criteria specified in RFC 2863 for high-capacity
counters.
optional pwMappingTablesGroup This group is only mandatory for implementations
that support reverse mapping of PW indexes to
the pwIndex and the peer mapping table.
optional pwSignalingGroup This group is only mandatory for implementations
that support the PW signaling.
optional pwNotificationControlGroup This group is only mandatory for implementations
that support the PW notifications.
Object refinements
ObjectAccessSyntaxDescription
pwAdminStatus
Enumeration
up(1), down(2)
Support of the value testing(3) is not
required.
pwOperStatus
up(1), down(2), notPresent(5), lowerLayerDown(6)
Support of the values testing(3) and dormant(4)

is not required.
pwRowStatus
active(1), notInService(2), notReady(3)
Support for createAndWait is not required. Support
of notReady is not required for implementations
that do not support signaling, or if it is
guaranteed that the conceptual row has all the
required information to create the PW when the
row has been created by the agent or written by
the operator.
pwPeerAddrType readonly
unknown(0), ipv4(1)
Only unknown(0) and ipv4(1) are required.
Implementations that support only IPv4 MAY support
read-only access.
pwPeerAddr An implementation is only required to support
0, 4 address sizes.
pwStorageType readonly
Write access is not required.
pwNotifRate readonly
Write access is not required.

OID .1.3.6.1.2.1.10.246.2.2.2
The compliance statement for agents that provide read-
only support for the PW MIB module. Such devices can
then be monitored but cannot be configured using this
MIB module.
Required groups
mandatory pwBasicGroup
optional pwNotificationGroup This group is only mandatory for implementations
that can efficiently implement the notifications
contained in this group.
optional pwPwIdGroup This group is only mandatory for implementations
that support the PW ID FEC.
optional pwGeneralizedFecGroup This group is only mandatory for implementations
that support the generalized PW FEC.
optional pwFcsGroup This group is only mandatory for implementations
that support FCS retention.
optional pwFragGroup This group is only mandatory for implementations
that support PW fragmentation.
optional pwPwStatusGroup This group is only mandatory for implementations
that support PW status notification.
optional pwGetNextGroup This group is only mandatory for implementations
where the pwIndex may be any arbitrary value
and the EMS would require retrieval of the next
free index.
optional pwPriorityGroup This group is only mandatory for implementations
that support the controlling the PW setup and
holding priority.
optional pwAttachmentGroup This group is only mandatory for implementations
that support attachment of two PWs (PW stitching).
optional pwPeformance1DayIntervalGroup This group is only mandatory for implementations
that support PW performance gathering in 1-day
intervals.
optional pwPerformanceIntervalGeneralGroup This group is only mandatory for implementations
that support PW performance gathering in 15-
minute intervals.
optional pwPeformanceIntervalGroup This group is only mandatory for implementations
that support PW performance gathering in 15-
minute intervals.
optional pwHCPeformanceIntervalGroup This group is only mandatory for implementations
where at least one of the interval performance
counters wraps around too quickly based on the
criteria specified in RFC 2863 for high-capacity
counters.
optional pwMappingTablesGroup This group is only mandatory for implementations
that support reverse mapping of PW indexes to
the pwIndex and the peer mapping table.
optional pwSignalingGroup This group is only mandatory for implementations
that support the PW signaling.
optional pwNotificationControlGroup This group is only mandatory for implementations
that support the PW notifications.
Object refinements
ObjectAccessSyntaxDescription
pwType readonly
Write access is not required.
pwOwner readonly
Write access is not required.
pwPsnType readonly
Write access is not required.
pwSetUpPriority readonly
Write access is not required.
pwHoldingPriority readonly
Write access is not required.
pwPeerAddrType readonly
unknown(0), ipv4(1)
Write access is not required. Only unknown(0) and
ipv4(1) are required.
pwPeerAddr readonly Write access is not required. An implementation
is only required to support 0, 4 address sizes.
pwAttachedPwIndex readonly
Write access is not required.
pwIfIndex readonly
Write access is not required.
pwID readonly
Write access is not required.
pwLocalGroupID readonly
Write access is not required.
pwGroupAttachmentID readonly
Write access is not required.
pwLocalAttachmentID readonly
Write access is not required.
pwRemoteAttachmentID readonly
Write access is not required.
pwCwPreference readonly
Write access is not required.
pwLocalIfMtu readonly
Write access is not required.
pwLocalIfString readonly
Write access is not required.
pwLocalCapabAdvert readonly
Write access is not required.
pwFragmentCfgSize readonly
Write access is not required.
pwFcsRetentionCfg readonly
Write access is not required.
pwOutboundLabel readonly
Write access is not required.
pwInboundLabel readonly
Write access is not required.
pwName readonly
Write access is not required.
pwDescr readonly
Write access is not required.
pwAdminStatus readonly
Enumeration
up(1), down(2)
Write access is not required. The support of value
testing(3) is not required.
pwOperStatus
up(1), down(2), notPresent(5), lowerLayerDown(6)
The support of the values testing(3) and dormant(4)
is not required.
pwRowStatus readonly
active(1)
Write access is not required.
pwStorageType readonly
Write access is not required.
pwOamEnable readonly
Write access is not required.
pwGenAGIType readonly
Write access is not required.
pwGenLocalAIIType readonly
Write access is not required.
pwGenRemoteAIIType readonly
Write access is not required.
pwUpDownNotifEnable readonly
Write access is not required.
pwDeletedNotifEnable readonly
Write access is not required.
pwNotifRate readonly
Write access is not required.
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.2.1.10.246.0.1
This notification is generated when the pwOperStatus
object for one or more contiguous entries in the pwTable are
about to enter the down(2) or lowerLayerDown(6) state from
any other state, except for transition from the
notPresent(5) state. For the purpose of deciding when
these notifications occur, the lowerLayerDown(6) state
and the down(2) state are considered to be equivalent;
i.e., there is no notification on transition from
lowerLayerDown(6) into down(2), and there is a trap on
transition from any other state except down(2) (and
notPresent) into lowerLayerDown(6).

The included values of pwOperStatus MUST each be equal to
down(2) or lowerLayerDown(6). The two instances of
pwOperStatus in this notification indicate the range of
indexes that are affected. Note that all the indexes of
the two ends of the range can be derived from the
instance identifiers of these two objects. For cases
where a contiguous range of cross-connects have
transitioned into the down(2) and lowerLayerDown(6) states
at roughly the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in an
effort to minimize the emission of a large number of
notifications. If a notification has to be issued for
just a single cross-connect entry, then the instance
identifier (and values) of the two pwOperStatus objects
MUST be identical.
.1.3.6.1.2.1.10.246.0.2
This notification is generated when the pwOperStatus
object for one or more contiguous entries in the pwTable are
about to enter the up(1) state from some other state

except the notPresent(5) state and given that the pwDown
notification been issued for these entries. The included
values of pwOperStatus MUST both be set equal to this
new state (i.e., up(1)). The two instances of pwOperStatus
in this notification indicate the range of indexes that
are affected. Note that all the indexes of the two ends
of the range can be derived from the instance identifiers
of these two objects. For cases where a contiguous range
of cross-connects have transitioned into the up(1) state
at roughly the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in an
effort to minimize the emission of a large number of
notifications. If a notification has to be issued for
just a single cross-connect entry, then the instance
identifier (and values) of the two pwOperStatus objects
MUST be identical.
.1.3.6.1.2.1.10.246.0.3
This notification is generated when the PW has been
deleted, i.e., when the pwRowStatus has been set to
destroy(6) or the PW has been deleted by a non-MIB
application or due to an auto-discovery process.