All MIBs › PW-STD-MIB
Organization: IETF PWE3 Working Group
Last Updated: 2009-04-21
Category: Pseudowire
Description:
Manages pseudowire (PW) edge-to-edge emulated services over packet switched networks, providing generic PW configuration and performance monitoring.
Imported Objects
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Counter64 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 | |
| mib-2 |
From SNMPv2-TC
| RowStatus | |
| StorageType | |
| TimeStamp | |
| TruthValue |
What Is PW-STD-MIB?
PW-STD-MIB is an IETF standards-track MIB that defines generic managed objects for Pseudowire (PW) emulation edge-to-edge services, per RFC 3985/4447/3931, letting any packet-switched network (MPLS, L2TPv3, etc.) carry Layer 2 services across a PSN core. It exposes a central pseudowire table describing each configured PW's type, owner, PSN type, peer address, and priority, alongside notification objects for PW state-change events. In monitoring terms it is used to track both configuration status (whether a PW is correctly provisioned with the right peer address and type) and operational/software status (via PW up/down notifications), rather than physical hardware, making it the standard way to confirm a pseudowire circuit is established and identify its peer/PSN type when troubleshooting a service outage. Engineers configuring alerts on these objects often consult a PW-STD-MIB OID list first, to map pwTable columns like pwType and pwPsnType to their numeric OIDs for the NMS. It depends on and is meant to be used alongside PSN-specific companion MIBs (e.g., for MPLS or L2TPv3) that supply the underlying tunnel-layer detail referenced by its PSN-type objects. It is deployed on provider-edge routers and switches in carrier networks offering pseudowire/VPWS Layer 2 VPN services.
IPNetwork Monitor allows you to monitor SNMP objects defined in PW-STD-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
What Can Be Monitored
- pseudowire type
- pseudowire owner
- PSN type
- peer address
- setup/holding priority
- pseudowire up/down notifications
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- provider-edge routers/switches supporting pseudowire (PWE3) services
Monitoring Examples
An operator would poll pwTable/pwEntry (indexed via pwIndex, with pwIndexNext used to allocate new entries) to check pwType, pwPsnType, and pwPeerAddr for each configured pseudowire, verify pwSetUpPriority/pwHoldingPriority for MPLS-TE-style priority handling, and watch pwNotifications for a down-state trap; a PW entry showing an unexpected peer address or repeated down notifications would indicate a misconfigured or failing pseudowire circuit.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| pwMIB | 1.3.6.1.2.1.174 | Pseudowire Management Information Base. | ||
| pwObjects | 1.3.6.1.2.1.174.1 | |||
| pwTable | 1.3.6.1.2.1.174.1.1 | not-accessible | Pseudowire table. | |
| pwEntry | 1.3.6.1.2.1.174.1.1.1 | not-accessible | Pseudowire entry. | |
| PWI pwIndex | 1.3.6.1.2.1.174.1.1.1.1 | PwIndexType | not-accessible | Pseudowire index, unique in table. |
| INT pwType | 1.3.6.1.2.1.174.1.1.1.2 | INTEGER | read-create | Pseudowire type. |
| IPt pwPeerAddrType | 1.3.6.1.2.1.174.1.1.1.3 | InetAddressType | read-create | Peer address type. |
| IP pwPeerAddr | 1.3.6.1.2.1.174.1.1.1.4 | InetAddress | read-create | Peer address. |
| U32 pwID | 1.3.6.1.2.1.174.1.1.1.5 | Unsigned32 | read-create | Pseudowire ID. |
| ROW pwRowStatus | 1.3.6.1.2.1.174.1.1.1.6 | RowStatus | read-create | Row status. |
| STO pwStorageType | 1.3.6.1.2.1.174.1.1.1.7 | StorageType | read-create | Storage type. |
| pwConformance | 1.3.6.1.2.1.174.2 |
FAQ
How is PW-STD-MIB used to confirm a pseudowire circuit is up between two provider-edge routers?
Its central pwTable exposes each configured PW's type, owner, PSN type, peer address, and priority, and it defines PW up/down notification objects, so an engineer can confirm a PW is provisioned with the correct peer and type, then rely on the state-change notifications to know when the circuit goes down.
Why would an engineer need companion MIBs alongside PW-STD-MIB when troubleshooting a PWE3 outage?
Because PW-STD-MIB only defines the generic, PSN-independent pseudowire objects; the underlying tunnel-layer detail (e.g., MPLS or L2TPv3 specifics) is supplied by PSN-specific companion MIBs that PW-STD-MIB references via its PSN-type objects, so both are consulted together during troubleshooting.
RFC description
Pseudowire (PW) management information base (RFC 5601) defining managed objects for pseudowire services carried over packet-switched networks.
Start monitoring vendor-neutral, standards-based MIB, provider-edge routers/switches supporting pseudowire (PWE3) services with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.