Table Of Contents
Information Model Objects (IMOs)
PTP Layer 2 MPLS Tunnel Interface
Vendor-Specific Inventory and IMOs
Pseudowire
This chapter describes the level of support that Cisco ANA provides for Pseudowire, as follows:
•Information Model Objects (IMOs)
•Vendor-Specific Inventory and IMOs
For information on network topology, see Chapter 38 "Cisco ANA VNE Topology."
Technology Description
This section provides the following Pseudowire technology descriptions:
•PWE3
•PTP Layer 2 MPLS Tunnel Interface
Please see Part 1: Cisco VNEs in this guide for information about which devices support the various technologies.
PWE3
PWE3 provides methods for carrying networking services (such as ATM, Ethernet, TDM, and SONET/SDH) over a packet-switched network (PSN) as outlined in RFC 3985. It is a point-to-point connection between pairs of PE routers. It emulates services like Ethernet over an underlying core MPLS network through encapsulation into a common MPLS format, thus allowing carriers to converge their services with an MPLS network.
TDM PW
TDM Pseudowire is a widely used method for carrying Time Division Multiplexed E1, T1, E3, or T3 circuits across PSNs. It enables:
•Enterprises to run voice, video, and legacy data over the PSN
•Service providers to provide revenue-generating legacy voice and data services over the PSN
•Data carriers to offer PSN-based leased and private lines
ATM PW
ATM Pseudowire (RFC 4816) is a transparent cell transport service that allows migration of ATM services to a PSN without having to provision the ATM subscriber or CE devices. ATM CEs view the ATM transparent cell transport service as if they were directly connected via a TDM leased line. This service is used as an internal function in an ATM service provider's network as a way to connect existing ATM switches via a higher-speed PSN, or to provide ATM backhaul services for remote access to existing ATM networks.
PW-to-TE Tunnel Mapping
PW-to-TE Tunnel Mapping (RFC 5602) permits operation of pseudowire services across MPLS PSNs by mapping pseudowires to MPLS TE tunnels.
Multi-Segment PW
A Multi-Segment Pseudowire (MS-PW) is a statically or dynamically configured set of two or more contiguous PW segments that behave and function as a single point-to-point PW. MS-PW thus extends PW across more than one packet switched network (PSN) domain, multiple provider domains, and different PSN types.
Information Model Objects (IMOs)
This section describes the following IMO:
•PTP Layer 2 MPLS Tunnel Interface (IPTPLayer2MplsTunnel)
PTP Layer 2 MPLS Tunnel Interface
The network/data link layer PTP Layer 2 MPLS Tunnel Interface object is bound by its Containing Termination Points attribute to a data link layer interface object. It is accessed primarily by Label Switching Entity.
For multi-segment PW, at the VNE layer, ANA maintains stitching between two IPTPLayer2MplsTunnel (PW endpoints), as Local Switching Entry under Local Switching Entity.
Table 17-1 PTP Layer 2 MPLS Tunnel Interface (IPTPLayer2MplsTunnel)
Attribute Name Attribute Description Scheme Polling IntervalLocal and Remote Router Addresses
Local and remote router IP addresses
IpCore
Configuration
Local and Remote Virtual Connection Labels
Local and remote virtual connection labels
IpCore
Configuration
Tunnel Identification
Tunnel identifier
IpCore
Configuration
Tunnel Status
Tunnel status (Unknown, Up, Down)
IpCore
Configuration
Local and Remote Tunnel Interface
Local and remote tunnel interface Object Identifier
IpCore
Configuration
IANA Type
Internet Assigned Numbers Authority (IANA) type of the sublayer
N/A
N/A
Containing Termination Points
Underlying termination points (connection or physical)
IpCore
N/A
Contained Connection Termination Points
Bound connection termination points (Tunnel Container)
IpCore
N/A
Pseudowire Type
The MPLS pseudowire type (for example, Ethernet, SAToP, and so on)
IpCore
Configuration
Preferred Path Tunnel
The Object Identifier of the preferred path
IpCore
Configuration
Local MTU
The local MTU
IpCore
Configuration
Remote MTU
The remote MTU
IpCore
Configuration
Peer Status
Status of the signaling peer
IpCore
Configuration
Signaling Protocol
The signaling protocol
IpCore
Configuration
VFI Name
The name of the VFI
IpCore
Configuration
Vendor-Specific Inventory and IMOs
There are no vendor-specific inventory or IMOs for this technology.
Service Alarms
The following alarm is supported for this technology: