Cisco Prime Nerk 43 User Guide

							  
17-75
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Viewing MPLS LDP, Static Information
As part of the topological link support, Prime Network started supporting two new service alarms MPLS 
Link down and MPLS Link up, besides MPLS-TP inventory information. These alarms are raised on 
the MPLS links during misconfigurations of physical links or shut down of physical interfaces. To view 
the service alarms supported by Prime Network, refer Cisco Prime Network Supported Service Alarms
Figure 17-28 Viewing MPLS link configured with LDP and Static 
						

							  
17-76
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Working with FEC 129-based Pseudowire
Working with FEC 129-based Pseudowire
The following topics describe how to use the Vision client to monitor FEC 129-based pseudowires:
FEC 129-based Pseudowire, page 17-76
Viewing FEC 129-based Pseudowire from Logical Inventory, page 17-77
Viewing FEC 129 links from Topology View, page 17-80
FEC 129-based Pseudowire Service Discovery, page 17-82
Viewing FEC 129 Type II-based Pseudowire Tunnel from Pseudowire Map View, page 17-83
Viewing FEC 129 Type II-based Pseudowire Tunnels from Virtual Connection Map View, 
page 17-84
Viewing FEC 129 Type I-based Pseudowire Tunnel from VPLS Map view, page 17-85
Viewing FEC 129 Type I-based Pseudowire Tunnels from Virtual Connection Map View, page 17-86
FEC 129-based Pseudowire
A pseudowire (PW) is a Layer 2 circuit or a service that emulates the essential attributes of a 
telecommunication service (such as T1 line) over an MPLS packet-switched network (PSN). 
Pseudowires can be established between two provider edges (PEs) as a single segment (SS) or 
multisegment (MS) pseudowire. 
The Cisco Prime Network supports FEC 129 pseudowire configured in a single segment mode.
The single segment pseudowire (SS-PW) pseudowire originates and terminates on the edge of the same 
MPLS PSN, especially within the same autonomous system (AS). The pseudowire label is unchanged 
between the originating and terminating provider edge (T-PE) devices.
The FEC 129 pseudowire uses Source Attachment Individual Identifier (SAII), Target Attachment 
Individual Identifier (TAII), and Attachment Group Identifier (AGI) to make a key along with the 
existing attributes such as tunnel ID and peer router IP. 
The FEC 129-based pseudowire can be classified into two types based on the attachment circuit:
Type I—The attachment circuit for type I would be VSI, which in turn connected to bridges on either 
ends. You can identify the Type I pseudowires uniquely with the AGI, SAII, and TAII values.
Type II—The attachment circuit for type II would be Ethernet on which EFP is configured. You can 
identify the Type II pseudowire uniquely with the SAII and TAII values.
In order to configure FEC 129 Type II pseudowire, an Ethernet interface with EFP already 
configured, is selected. Under this Ethernet interface (which becomes SAII), you can configure the 
TAII with the target attachment identifier statement. If the configured target identifier matches a 
source identifier advertised by a remote PE device by way of a BGP auto discovery message, then 
the pseudowire between that source and target pair is signaled. If there is no match between an 
advertised source identifier and the configured target identifier, the pseudowire is not established.
The following topic explain how to view the FEC 129 pseudowire from the inventory view:
Viewing FEC 129 Type I-based Pseudowire from VSI Inventory, page 17-78 
						

							  
17-77
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Viewing FEC 129-based Pseudowire from Logical Inventory
Viewing FEC 129-based Pseudowire from Logical Inventory
To view the FEC 129-based pseudowire information in the logical inventory:
Step 1Right-click the required device in the Vision client and choose Inventory.
Step 2In the Inventory window, choose Logical Inventory > Pseudowires.
NoteThe AGI, SAII, and TAII are the new attributes supported for the FEC 129-based pseudowires.
The Pseudowire Tunnel Edges table is displayed and contains the information described in Table 17-30.
Table 17-30 Pseudowire Tunnel Edges Table
Field Description
Local Interface Name of the subinterface or port. 
Strings, such as Aggregation Group, EFP, VLAN, and VSI, are included in the interface name, and 
the entry is hyperlinked to the relevant entry in logical or physical inventory. 
VC ID Tunnel identifier, hyperlinked to the PTP Layer 2 MPLS Tunnel Properties window.
NoteFor the FEC 128 pseudowire, VC ID is populated whereas for the FEC 129 pseudowire, VC 
ID is not populated.
AGI Attachment Group Identifier (AGI). 
An identifier common to a group of pseudowires that may be connected. The AGI carries VPLS ID 
of the local PE router VPLS instance. The VPLS ID must be the same for all the PEs in the same 
VPLS instance.
SAII Specifies the Source Attachment Individual Identifier (SAII) of the tunnel.
The SAII attribute is configured for FEC 129 Type I and II pseudowires.
TAII Specifies the Target Attachment Individual Identifier (TAII) of the tunnel.
The TAII attribute is configured for FEC 129 Type I and II pseudowires.
Pseudowire Type Type of pseudowire, in this case Ethernet. 
Peer Details of the selected peer, hyperlinked to the peer pseudowire tunnel in logical inventory.
Status Operational state of the tunnel: Up or Down.
Pseudowire Role If the pseudowire is in a redundancy configuration, indicates whether its role is as the primary or 
secondary pseudowire in the configuration.
If the pseudowire is not configured for redundancy, this field is blank.
Preferred Path 
TunnelPath to be used for MPLS pseudowire traffic.
Local Router IP IP address of local tunnel edge, which is used as the MPLS router identifier.
Peer Router IP IP address of the peer tunnel edge, which is used as the MPLS router identifier.
Local MTU Size, in bytes, of the MTU on the local interface. 
Remote MTU Size, in bytes, of the MTU on the remote interface. 
Local VC Label MPLS label that is used by this router to identify or access the tunnel. It is inserted into the MPLS 
label stack by the local router. 
						

							  
17-78
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Viewing FEC 129-based Pseudowire from Logical Inventory
Viewing FEC 129 Type I-based Pseudowire from VSI Inventory
To view the FEC 129 Type I-based pseudowire from VSI logical inventory:
Step 1To view VSI properties in the Vision client, open the VSI Properties window in either of the following 
ways: 
Double-click the required VNE and, in the Inventory window, choose Logical 
Inventory > VSIs >vsi. 
In the navigation pane, expand the VPLS instance, right-click the required VPLS forward, and 
choose Inventory or Properties.  Peer VC Label MPLS label that is used by this router to identify or access the tunnel. It is inserted into the MPLS 
label stack by the peer router.
Signaling Protocol Protocol used by MPLS to build the tunnel, for example, LDP or TDP.
Peer Status Status of the peer link.
Associated EVC 
NameSpecifies the name of the associated Ethernet Virtual Circuits (EVC).
Table 17-30 Pseudowire Tunnel Edges Table (continued)
Field Description 
						

							  
17-79
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Viewing FEC 129-based Pseudowire from Logical Inventory
Table 17-31 describes the information that is displayed for the selected VSI. 
NoteThe AGI, SAII, and TAII are the new attributes supported for the FEC 129 pseudowires.
Table 17-31 VSI Properties in Logical Inventory
Field Description
VSI Name VSI name.
VPN ID VPN identifier used in an MPLS network to distinguish between different 
VPLS traffic.
VSI Mode VSI mode: Point-to-Point (default) or Multipoint.
Discovery Mode VSI discovery mode: Auto-BGP.
Operational State VSI operational status: Up or Down.
Administrative State VSI administrative status: Up or Down.
Local Bridge Local bridge, hyperlinked to the bridge in logical inventory.
Pseudowires Table
Pseudowire ID Pseudowire identifier, hyperlinked to the Tunnel Edges table under 
Pseudowires in logical inventory.
VC ID Pseudowire virtual circuit identifier.
NoteFor the FEC 128 pseudowire, VC ID is populated whereas for the 
FEC 129 pseudowire, VC ID is not populated.
AGI Attachment Group Identifier (AGI). An identifier common to a group of 
pseudowires that may be connected. The AGI carries VPLS ID of the local 
PE router VPLS instance. The VPLS ID must be the same for all the PEs in 
the same VPLS instance.
SAII Specifies the Source Access Individual Identifier (SAII) of the tunnel.
The SAII attribute is configured for FEC 129 Type I and II pseudowires.
TAII Specifies the Target Attachment Individual Identifier (TAII) of the tunnel.
The TAII attribute is configured for FEC 129 Type I and II pseudowires.
Peer IP IP address of the pseudowire peer.
Autodiscovery The pseudowire was automatically discovered using BGP (auto-BGP). 
In this case, the value is True.
Split  Horizon SSH pseudowire policy that indicates whether or not packets are forwarded 
to the MPLS core. In this case, the value is True. 
						

							  
17-80
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Viewing FEC 129 links from Topology View
Viewing FEC 129 links from Topology View
Viewing FEC 129 Pseudowire Properties from Topology View
On adding the two associated VNEs to the map, a link is formed between them. This is the topology view 
and this link depicts the logical association between the associated VNES. Hovering over this link 
displays all the logical links (or protocols) configured between these peers. 
To view the FEC 129 link:
Step 1In the Vision client map view, select a link connected to two devices and open the link quick view 
window.
Step 2Click the link between the two VNEs. Identify the FEC 129 pseudowires based on the unique identifiers 
as mentioned in the Viewing FEC 129-based Pseudowire from Logical Inventory, page 17-77.
NoteIf the link is down, it will be displayed in Red and the active links are displayed as green.
Step 3To view the FEC 129 properties in detail, click Properties in the link properties window. 
Step 4Select the FEC 129 Type I or II link and the link properties are displayed.
Table 17-32 describes the information that is displayed for the FEC 129 link. 
						

							  
17-81
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  Viewing FEC 129 links from Topology View
Table 17-32 FEC 129 Link Properties
Field Description
General Properties
Link Type Link protocol. In this case, PW.
Type Type of link: Dynamic or Static.
Bi Directional Whether the link is bidirectional: True or False.
FEC 129 Properties Properties are displayed for both ends of the MLPPP link.
ID Pseudowire identifier, hyperlinked to the VLAN entry in Bridges in logical 
inventory. 
Peer Identifier of the pseudowire peer, hyperlinked to the entry in the Pseudowire 
Tunnel Edges table in logical inventory.
AGI Attachment Group Identifier (AGI). An identifier common to a group of 
pseudowires that may be connected. The AGI carries VPLS ID of the local 
PE router VPLS instance. The VPLS ID must be the same for all the PEs in 
the same VPLS instance.
NoteThe FEC 129 Type I topology displays AGI in addition to SAII and 
TA I I .
SAII Specifies the Source Attachment Individual Identifier (SAII) of the tunnel.
The SAII attribute is configured for FEC 129 Type I and II pseudowires.
Tunnel Status Operational state of the tunnel: Up or Down.
TAII Specifies the Target Attachment Individual Identifier (TAII) of the tunnel.
The TAII attribute is configured for FEC 129 Type I and II pseudowires.
Peer Router IP IP address of the peer router for this pseudowire.
Pseudowire Type Type of pseudowire, in this case, Ethernet. 
Pseudowire Role If the pseudowire is in a redundancy configuration, then the pseudowire role 
indicates whether its a primary pseudowire or a secondary pseudowire in the 
configuration.
If the pseudowire is not configured for redundancy, the field is blank.
Preferred Path Tunnel Specifies the path that has to be used for MPLS pseudowire traffic.
Local Router IP Specifies the IP address of the tunnel edge, which is used as the router 
identifier.
Local MTU Specifies the byte size of the MTU on the local interface. 
Remote MTU Specifies the byte size of the MTU on the remote interface. 
Local VC Label Specifies the MPLS label that is used by the local router to identify or access 
the tunnel. It is inserted in the MPLS label stack by the local router.
Peer VC Label Specifies the MPLS label that is used by the peer router to identify or access 
the tunnel. It is inserted in the MPLS label stack by the peer router.
Signaling Protocol Specifies the protocol that is used to build the tunnel, such as the LDP or 
TDP.
Peer Status Specifies the status of the peer link. 
						

							  
17-82
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  FEC 129-based Pseudowire Service Discovery
FEC 129-based Pseudowire Service Discovery
The Cisco Prime Network delivers FEC 129-based discovery for various support services such as bridge 
domains, pseudowires, Virtual Connections, and VPLS.
The Cisco Prime Network release supports the following service discoveries:
Bridge Domain Discovery—Discovers bridges domains such as I-Bridges, B-Bridges, and regular 
bridges that are not associated to VFIs or pseudowires. For more information, refer to Working with 
PBB-VPLS.
Pseudowire Discovery—Discovers pseudowires in any one of the following ways:
–Pseudowires that are associated to I-Bridges and B-Bridges in addition to regular bridges. 
NoteAs specified in the Bridge Domain discovery, the regular bridges associated to pseudowires, 
cannot be discovered from the Bridge Domain services.
–All the pseudowires that are associated to Ethernet such as FEC 128, FEC 129 Type II, which 
in turn has an EFP configured. This service discovers the end-to-end pseudowire peers (FEC 
128 or FEC 129 Type II) along with the Ethernet attachments.
NoteThe FEC 129 Type II end-to-end tunnels are identified from the Pseudowire service using the 
SAII and TAII values.
VPLS Discovery—Discovers VPLS in any one of the following ways:
–VFIs associated to I-Bridges, B-Bridges, and regular bridges.
NoteAs specified in the Bridge Domain discovery, the regular bridges associated to VFIs, cannot be 
discovered from the Bridge Domain services.
–VFIs associated to pseudowires such as FEC 128, FEC 129 Type I pseudowires (pseudowires 
which are attached to VFIs which in turn attached to bridges (B-Bridges)) are discovered. This 
service discovers the end-to-end VFIs, which on expanding from the VPLS map view, displays 
the end-to-end pseudowire peers (FEC 128 or FEC 129 type I pseudowires). 
NoteThe FEC 129 Type I end-to-end tunnels are identified from the VPLS service using the 
Attachment Group Identifier (AGI) value along with SAII and TAII values.
NoteIn order to view the B-bridges attached to the VFIs, the bridges must be selected from the Bridge 
Domain service. 
						

							  
17-83
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  FEC 129-based Pseudowire Service Discovery
Virtual Connection or EVC Discovery—Creates an end-to-end complex circuit representing the 
network associations in the core network of all the above discovered elements. Using the Virtual 
Connection map view, the complete topology of the pseudowire is displayed instead of selecting 
each plugin separately from the VPLS or pseudowire map view.
–FEC 129 Type I—Instead of selecting FEC 129 Type I pseudowires and their associated VFIs 
(from the VPLS service) and the associated B-bridges (from the bridge domain service), the 
FEC-129 type 1 end-to-end tunnels can be viewed as a single instance from the Virtual 
Connection service.
The FEC 129 Type I end-to-end tunnels are identified using the AGI value along with SAII and 
TAII values.
–FEC 129 Type II—The FEC 129 Type II end-to-end tunnels and the Ethernet attachments can 
be viewed as a single instance from the Virtual Connections service. 
The FEC 129 Type II end-to-end tunnels are identified using the SAII and TAII values.
The following topics explain how to view the FEC 129-based pseudowire from service discovery:
Viewing FEC 129 Type II-based Pseudowire Tunnel from Pseudowire Map View, page 17-83
Viewing FEC 129 Type II-based Pseudowire Tunnels from Virtual Connection Map View, 
page 17-84
Viewing FEC 129 Type I-based Pseudowire Tunnel from VPLS Map view, page 17-85
Viewing FEC 129 Type I-based Pseudowire Tunnels from Virtual Connection Map View, page 17-86
Viewing FEC 129 Type II-based Pseudowire Tunnel from Pseudowire Map View
To discover the links between the FEC Type II pseudowires:
Step 1Choose Add to Map > Pseudowire to open the Add Pseudowire to Specific plugins dialog box.
Step 2In the Add Pseudowire to Specific plugins dialog box, select Show All to display the list of 
pseudowires.
Step 3To view a specific FEC Type II pseudowire, filter using the pseudowire ID (SAII or TAII) to identify the 
FEC Type II pseudowire.
Step 4Click OK to add the selected FEC 129 type II pseudowire to the map. 
Step 5The selected pseudowire component in the map displays the following links. Click the expand (+) icon 
to view the links:
Association between the EFP of one router (for example, router 1) to the FEC 129 type II 
pseudowire.
Link between the two associated FEC 129 type II pseudowires that are peers.
Association between the FEC 129 type II pseudowire of the other router (for example, router 2) to 
the EFP. 
						

							  
17-84
Cisco Prime Network 4.3.2 User Guide
Chapter 17      Managing MPLS Networks
  FEC 129-based Pseudowire Service Discovery
Viewing FEC 129 Type II-based Pseudowire Tunnels from Virtual Connection 
Map View 
The Virtual Connection view displays the logical association between the FEC 129 type II pseudowires 
in a single view. 
To view the end-to-end connection between the FEC 129 type II pseudowire peers:
Step 1Open the Add Virtual Connection to Specific plugin dialog box in either of the following ways:
In the toolbar, choose Add to Map > Virtual Connection. 
In the menu bar, choose File > Add to Map > Virtual Connection. 
Step 2In the Add Virtual Connection to Specific plugins dialog box, select the virtual connection that you 
want to view.
Step 3To view a specific FEC type II pseudowire, filter using the pseudowire ID (SAII or TAII) to identify the 
FEC Type II pseudowire.
Step 4Click OK to add the selected virtual connection component to the map. 
Step 5For the selected virtual connection component in the map, you can view the following FEC 129 Type II 
pseudowire information:
Viewing FEC 129 Type II Pseudowire Links from Virtual Connection View, page 17-84
Viewing FEC 129 Type II Pseudowire Properties from Virtual Connection View, page 17-84
Viewing FEC 129 Type II Pseudowire Links from Virtual Connection View
To view the end-to-end connection between the FEC 129 type II pseudowire peers:
Step 1Click the expand (+) icon to view the links:
Association between the EFP of one router (for example, router 1) to the FEC 129 type II 
pseudowire.
Link between the two associated FEC 129 type II pseudowires that are peers.
Association between the FEC 129 type II pseudowire of the other router (for example, router 2) to 
the EFP.
Viewing FEC 129 Type II Pseudowire Properties from Virtual Connection View
To view the FEC 129 type II pseudowire properties:
Step 1Right-click the selected virtual connection component in the map.
Step 2Click the Properties tab to display the EVC hyperlink.
Step 3Click the EVC hyperlink to view the EVC terminating points.