Cisco Prime Network User Guide, 5.1

Adding an MPLS-TP Tunnel

Prime Network automatically discovers MPLS-TP tunnels, endpoints, and midpoints and enables you to add MPLP-TP tunnels to maps.

To add an MPLS-TP tunnel to a map:

Step 1 In the Vision client, display the map to which you want to add the MPLS-TP tunnel.

Step 2 Do either of the following:

• From the File menu, choose Add to Map > MPLS-TP Tunnel.
• In the main toolbar, click Add to Map, then choose Add to Map > MPLS-TP Tunnel.

The Add MPLS-TP Tunnel dialog box is displayed.

Step 3 Do either of the following:

• Choose a search category, enter a search string, then click Go to narrow search results to a range of MPLS-TP tunnels or a specific MPLS-TP tunnel. Search categories include:

– Description

– Name

– System Name

• Choose Show All to display all the MPLS-TP tunnels.

Step 4 Select the MPLS-TP tunnel that you want to add to the map.

Step 5 Click OK.

The MPLS-TP tunnel is added to the map and to the navigation pane.

In Figure 17-3:

• The devices are on the left side of the map, and the MPLS-TP tunnel is displayed in a thumbnail on the right.
• The devices are connected to each other and to the MPLS-TP tunnel via tunnels.
• Physical links connect the devices to the Working and Protected LSPs.
• A redundancy service badge is displayed next to the Protected LSP in the navigation and map panes.
• In the thumbnail:

– The tunnel endpoints are connected to each other via a tunnel.

– A physical link connects the Working and Protected LSPs.

– Business links connect the Working and Protected LSPs to each endpoint.

Figure 17-3 MPLS-TP Tunnel in Vision Map

If an LSP is in lockout state, it is displayed with the lock badge ().

By expanding all aggregations in the MPLS-TP tunnel (see Figure 17-4), you can see components and links in the MPLS-TP tunnel, including:

• MPLS-TP tunnel endpoints
• LSP endpoints
• LSP midpoints

Figure 17-4 MPLS-TP Tunnel Expanded

If an LSP is configured for redundancy service, a redundancy service badge is applied to the secondary (backup) LSP in the navigation and map panes in the navigation and map panes.

For more information about LSP redundancy service, see Viewing LSP Endpoint Redundancy Service Properties.

Viewing MPLS-TP Tunnel Properties

Prime Network discovers and displays MPLS-TP attributes in the MPLS-TP branch in logical inventory as described in this topic.

Additional information about MPLS-TP tunnel properties are available in the following branches:

• Routing Entities—See Viewing Routing Entities.
• LSEs—See Viewing Label Switched Entity Properties.
• Pseudowires— See Viewing Pseudowire End-to-End Emulation Tunnels.

To view MPLS-TP tunnel properties:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > MPLS-TP > MPLS-TP Global.

The routing information is displayed as shown in Figure 17-5.

Figure 17-5 MPLS-TP Tunnel Properties in Logical Inventory

Table 17-3 describes the information that is available for MPLS-TP tunnels. The information that is displayed depends on the configuration.

Step 3 To view additional MPLS-TP tunnel endpoint properties, double-click the required entry in the MPLS-TP Tunnel Endpoints table.

The MPLS-TP Tunnel Properties window is displayed as shown in Figure 17-6.

Figure 17-6 MPLS-TP Tunnel Properties Window

Table 17-4 describes the information available in the top portion of the MPLS-TP Tunnel Properties window. For information about the tabs that are displayed, see Table 17-3 .

Viewing LSPs Configured on an Ethernet Link

A single Ethernet link can support a number of LSPs. The Vision client enables you to view all LSPs on a single Ethernet link and to identify the source and destination labels.

To view LSPs configured on an Ethernet link:

Step 1 In the map view, right-click the required link and choose Properties.

Step 2 In the link properties window, choose the required Ethernet link.

The link properties window refreshes and displays the Labels button as shown in Figure 17-7.

Figure 17-7 Link Properties Window with All Labels Button

Step 3 Click Labels.

The All Labels window is displayed as shown in Figure 17-8 with the LSP sources and destinations.

Figure 17-8 All Labels Table

Step 4 To identify a specific path, click an outgoing label in the Source table. The corresponding in label is selected in the Destination table.

Viewing MPLS-TE and P2MP-MPLS-TE links in a map

Using the link filter available in Prime Network, you can view only the MPLS-TE and P2MP-MPLS-TE links in a map.

Note The MPLS Point-to-Multipoint Traffic Engineering (P2MP TE) feature enables you to forward Multiprotocol Label Switching (MPLS) traffic from one source to multiple destinations.

To view the MPLS-TE and P2MP-MPLS-TE links in a map:

Step 1 Open the required map.

Step 2 Click the Link filter icon in the navigation menu.

Step 3 In the Link Filter window, select the MPLS-TE and P2MP MPLS-TE check boxes.

Step 4 Click OK. The map refreshes and displays only the MPLS-TE and P2MP MPLS-TE links.

Step 5 Right-click on the link and choose the Properties option.

Step 6 In the Link Properties window, the type of link is displayed in the Link Type field, which can be either MPLS-TE and P2MP MPLS-TE based on the link that you have selected. Additional details about the link such as the MPLS TE tunnel, operational status of the tunnel, TE tunnel type are displayed in the Label Switching section. For more information about the Link Properties window, see Viewing LSPs Configured on an Ethernet Link.

Viewing LSP Endpoint Redundancy Service Properties

If an LSP endpoint in an MPLS-TP tunnel is configured for redundancy service, a redundancy service badge is applied to the secondary (backup) LSP endpoint in the navigation and map panes in the Vision client. Additional redundancy service details are provided in the LSP endpoint properties window and the inventory window for the element on which the MPLS-TP tunnel is configured.

To view LSP endpoint redundancy service properties:

Step 1 To determine if an LSP endpoint on an MPLS-TP tunnel is configured for redundancy service, expand the required MPLS-TP tunnel in the navigation or map pane.

If the LSP endpoint is configured for redundancy service, the redundancy service badge is displayed in the navigation and map panes as shown in Figure 17-9.

Figure 17-9 LSP Endpoint with Redundancy Service Badge

Step 2 To view properties for the LSP endpoint, navigate to and right-click the required endpoint in the map or navigation pane, and choose Properties.

The LSP endpoint properties window is displayed as shown in Figure 17-10.

Figure 17-10 LSP Endpoint Properties Window

Table 17-5 describes the information displayed in the LSP Endpoint Properties window.

Step 3 To view LSP endpoint redundancy status in inventory, double-click the element on which the MPLS-TP tunnel is configured.

Step 4 Choose Logical Inventory > MPLS-TP > MPLS-TP Global > LSP End Points.

Step 5 The LSP End Points tab contains the following information related to LSP redundancy service (see Figure 17-11):

• Whether the LSP endpoint is Working or Protected.
• The LSP endpoint role, either Active or Standby.
• The operational status of the LSP endpoint, either Up or Down.

Figure 17-11 LSP End Points Tab in Logical Inventory

Applying an MPLS-TP Tunnel Overlay

You can select and display an overlay of a specific MPLS-TP tunnel on top of the devices displayed in a map view. The overlay is a snapshot of the network that visualizes the flows between the sites and tunnel peers. When an MPLS-TP tunnel is selected in the map, the following elements are highlighted in the map:

• Elements on which TP endpoints and LSPs are configured.
• Links that carry TP traffic.

All elements and links that are not part of the MPLS-TP tunnel are dimmed.

To apply an MPLS-TP tunnel overlay:

Step 1 In the Vision client, display the network map on which you want to apply an overlay.

Step 2 From the main toolbar, click Choose Overlay Type and choose MPLS-TP tunnel.

The Select MPLS-TP tunnel Overlay dialog box is displayed.

Step 3 Do one of the following:

• Choose a search category, enter a search string, then click Go to narrow the search results to a range of MPLS-TP tunnels or a specific MPLS-TP tunnel. Search categories include:

– Description

– Name

– System Name

The search condition is “contains.” Search strings are case-insensitive. For example, if you choose the Name category and enter “net,” the Vision client displays VPNs “net” and “NET” in the names whether net appears at the beginning, middle, or at the end of the name: for example, Ethernet.

• Choose Show All to display all MPLS-TP tunnels.

Step 4 Select the MPLS-TP tunnel overlay you want to apply to the map.

The elements and links used by the selected MPLS-TP tunnel are highlighted in the network map, and the MPLS-TP tunnel name is displayed in the window title bar as shown in Figure 17-12.

Figure 17-12 MPLS-TP Tunnel Overlay

Note An overlay is a snapshot taken at a specific point in time and does not reflect changes that occur in the service. As a result, the information in an overlay can become stale. To update the overlay, click Refresh Overlay in the main toolbar.

Viewing Additional VPN Properties

The Vision client allows you to select any element in the navigation pane or map view and view additional underlying properties. To view additional properties for an object, either double-click it or right-click it and choose Properties. Table 17-7 shows the additional properties available for VPN entities.

Creating a VPN

You can change business configurations by manually creating VPNs. The VPNs that are manually created do not contain virtual routers and sites.

To create a VPN:

Step 1 In the Vision client navigation pane, select the map root.

Step 2 From the File menu, choose Add to Map > VPN > New.

Step 3 In the Create VPN dialog box, enter the following:

• Name—A unique name for the new VPN.

Note VPN business element names are case sensitive.

• Icon—To use a custom icon for the VPN, click the button next to the Icon field and navigate to the icon file.

Note If a path is not specified to an icon, the default VPN icon is used (for more information about icons, see Table 17-6).

• Description—(Optional) An additional VPN description.

Step 4 Click OK.

The new VPN is added to the VPN list in the Add VPN dialog box.

For more information about loading the newly created VPN in the service view map, see Adding a VPN to a Map.

Adding a VPN to a Map

You can add a VPN to a map view if the VPN was previously created by a user or discovered by Prime Network and are not currently displayed in the map.

Note Adding a VPN affects other users if they are working with the same map.

To add an existing VPN to a map:

Step 1 In the Vision client, display the map to which you want to add the VPN.

Step 2 Do either of the following:

• From the File menu, choose Add to Map > VPN > Existing.
• In the main toolbar, click Add to Map, then choose Add to Map > VPN > Existing.

The Add VPN dialog box is displayed.

Step 3 Do either of the following:

• Choose a search category, enter a search string, then click Go to narrow search results to a range of VPNs or a specific VPN. Search categories include:

– Description

– Name

The search condition is “contains.” Search strings are case-insensitive. For example, if you choose the Name category and enter “net,” the Vision client displays VPNs “net” and “NET” in the names whether net appears at the beginning, middle, or at the end of the name.

• Choose Show All to display all the VPNs.

Step 4 Select the VPN that you want to add to the map.

Tip Press Shift or Ctrl to choose multiple adjoining or nonadjoining VPNs.

Step 5 Click OK.

The VPN is displayed in the navigation pane and the selected map or subnetwork in the Vision client window content pane. In addition, any tickets are displayed in the ticket area.

When a VPN service is added to a map, then a new link is available between the ethernet flow point that represents the pseudowire headend port and the site in the VPN to which it is connected.

If your network has a L3VPN connected to a pseudowire via a PWHe, then EVC will also include the L3VPN in the EVC that contains the pseudowire.

Removing a VPN from a Map

You can remove one or more VPNs from the current active map. This change does not affect other maps. Removing a VPN from a map does not remove it from the Prime Network database. The VPN will appear in the Add VPN dialog box, so you can add it back to the map at any time.

When removing VPNs from maps, keep the following in mind:

• Removing a VPN affects other users if they are working with the same map view.
• This option does not change the business configuration or database.
• You cannot remove virtual routers or sites from the map without removing the VPN.

To remove a VPN, in the Vision client pane or map view, right-click the VPN and choose Remove from Map.

The VPN is removed from the map view along with all VPN elements, such as connected CE devices. Remote VPNs (extranets) are not removed.

Note If the routing information changes after an overlay is applied, the changes do not appear in the current overlay. Click Refresh Overlay to update the routing information.

Moving a Virtual Router Between VPNs

You can move a virtual router (including its sites) from one VPN to another after you create a VPN and add it to the service view map.

Note Moving a virtual router moves all of its sites as well.

To move a virtual router:

Step 1 In the Vision client navigation pane or map, right-click the virtual router and choose Edit > Move selected.

Step 2 Right-click the required VPN in the navigation pane or map to where you want to move the virtual router and choose Edit > Move here.

Caution Moving a virtual router from one VPN to another affects all users who have the virtual router loaded in their service view map.

---

The virtual router and its sites are displayed under the selected VPN in the navigation pane and in the map.

Applying VPN Overlays

You can select and display an overlay of a specific VPN on top of the devices displayed in a map view. The overlay is a snapshot of the network that visualizes the flows between the sites and tunnel peers. When one network VPN is selected in the network map, the PE routers, MPLS routers, and physical links that carry the LSP used by the VPN are highlighted in the network map. All the devices and links that are not part of the VPN are dimmed.

The VPN service overlay allows you to isolate the parts of a network that are being used by a particular service. This information can then be used for troubleshooting. For example, the overlay can highlight configuration or design problems when bottlenecks occur and all the site interlinks use the same link.

To apply a VPN overlay:

Step 1 In the Vision client, display the network map on which you want to apply an overlay.

Step 2 From the main toolbar, click Choose Overlay Type and choose VPN.

The Select VPN Overlay dialog box is displayed.

Step 3 Do one of the following:

• Choose a search category, enter a search string, then click Go to narrow the search results to a range of VPNs or a specific VPN. Search categories include:

– Description

– Name

The search condition is “contains.” Search strings are case-insensitive. For example, if you choose the Name category and enter “net,” the Vision client displays VPNs “net” and “NET” in the names whether net appears at the beginning, middle, or at the end of the name: for example, Ethernet.

• Choose Show All to display all the VPNs.

Step 4 Select the VPN overlay that you want to apply to the map.

The PE routers, MPLS routers, and physical links used by the selected VPN are highlighted in the network map. The VPN name is displayed in the title of the window.

Note An overlay is a snapshot taken at a specific point in time and does not reflect changes that occur in the service. As a result, the information in an overlay can become stale. To update the overlay, click Refresh Overlay in the main toolbar.

Managing a VPN Overlay Display in the Map View

After a VPN overlay is applied to a map, you can manage its display by using the overlay tools in the main toolbar:

• To display the overlay, click Show Overlay on the main toolbar.
• To hide an active overlay, click Hide Overlay on the main toolbar.

Note The Show Overlay button is a toggle. When clicked, the overlay is displayed. When clicked again, the overlay is hidden.

• To remove the VPN overlay, choose Show Overlay Type > None.

Displaying VPN Callouts in a VPN Overlay

You can display or hide the callouts for VPN links displayed in a VPN overlay to show the details of the sites that are interlinked through the selected links. The callouts (see Figure 17-15) enable you to view the VPN traffic links for a specific link (either bidirectional or unidirectional).

Note The link must be displayed in the VPN overlay and not dimmed for you to display the link callouts.

Figure 17-15 Callouts Window

To display or hide the callouts:

Step 1 In the Vision client window, display the map view with the VPN overlay.

Step 2 Right-click the required link in the map view and choose Show Callouts.

Step 3 To hide the callouts, right-click the link in the map view that is displaying the callouts and choose Hide Callouts.

Viewing VPN Properties

To view the properties of a VPN:

Step 1 In the Vision client navigation pane or map view, do either of the following:

• If the VPN icon is of the largest size, click the Properties button.
• Right-click the VPN and choose Properties.

The VPN Properties window displays the following information:

• Name—Name of the VPN.
• ID—Unique identifier assigned to the VPN.

Step 2 Click Close to close the VPN Properties dialog box.

Viewing Site Properties

The Vision client enables you to view site properties, including the interfaces that are configured on the PE device. The displayed properties reflect the configuration that Prime Network automatically discovered for the device.

To view site properties, in the Vision client navigation pane or map view, right-click the required site and choose Properties.

Table 17-8 describes the information that is displayed in the Router IP Interface Properties window:

Viewing VRF Properties

The Vision client enables you to view VRF properties, including the VRF route distinguisher, import and export route targets, and any provisioned sites and VRF routes.

To view VRF properties, do either of the following in map view:

• Double-click the element configured for VRFs.
• Expand the required VPN and double-click the virtual router.

The VRF properties window is displayed as shown in Figure 17-16.

Figure 17-16 VRF Properties

The VRF Properties window contains the VRF routing table for the device. The table is a collection of routes that are available or reachable to all the destinations or networks in the VRF. The forwarding table also contains MPLS encapsulation information.

Table 17-9 describes the information displayed in the VRF Properties window.

Note The VRF Properties window only displays properties and attributes that are provisioned in the VRF. You might not see all the fields and tabs described in Table 17-9.

Viewing VRF Multicast Configuration details

To view global multicast configuration details for a VRF:

Step 1 Right-click on the required device and select Inventory.

Step 2 In the Inventory window, choose Logical Inventory > VRFs > vrf (where vrf is the required VRF) > IPV4VRF Multicast Configuration or IPV6VRF Multicast Configuration. The route policies configured on the device are displayed in the content pane.

Table 17-10 describes the information that is displayed in the Router IP Interface Properties window:

Viewing VRF Egress and Ingress Adjacents

The Vision client enables you to view the exporting and importing Neighbours by displaying the VRF egress and ingress adjacents. In addition, you can view the connectivity between the VRFs for the route targets and view their properties. For example, if VRF A retrieved route target import X, you can view all VRFs that export X as a route target whether it is in the same or another VPN.

To display the VRF egress and ingress adjacents, you can use either an element configured for VRFs or a virtual router:

• To use an element configured for VRFs:

a. Double-click the element configured for VRFs.

b. In the Inventory window, choose Logical Inventory > VRFs > vrf where vrf is the required VRF.

c. Right-click the required VRF and choose Show VRF Egress Adjacents or Show VRF Ingress Adjacents.

• To use a virtual router, right-click the required VRF in the navigation pane, and choose Show VRF Egress Adjacents or Show VRF Ingress Adjacents.

Table 17-11 describes the information displayed in the Adjacents window.

Viewing Routing Entities

To view routing entities:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity.

The routing information is displayed as shown in Figure 17-17.

Figure 17-17 Routing Entity Table

Table 17-12 describes the information that is displayed in the Routing Entity table.

Viewing IPv4 Label in BGP Routes

The labeled BGP IPv4 (RFC 3107) enables BGP to distribute MPLS label along the routes it advertises. The label mapping information for a particular route is added in the same BGP update message that is used to distribute the route itself. The label mapping information is carried as a part of the Network Layer Reachability Information (NLRI) in the multiprotocol extension attributes. Hence, the use of any other label distribution protocol is eliminated.

The outer label again identifies the LSP and the inner label identifies the MPLS service. In this case, the RFC 3107 edge device replaces the outer label with two labels, generating a three-label stack.

In Prime Network, the IPv4 BGP Label Routing table displays incoming and outgoing labels. Path tracer follows a service that relies on RFC 3107 and it reflects the BGP label in the MPLS label stack.

RFC3107 is supported on the following device types: ASR9K, ASR901, ASR903, and ME3600/3800X.

To view the BGP label information:

Step 1 Double-click the required element in the Vision client.

Step 2 Choose Logical Inventory > Routing Entities > Routing Entity.

Step 3 In the IPv4 BGP Label Routing table, view the details of incoming and outgoing labels.

Table 17-13 describes the information in the IPv4 BGP Label Routing Table tab.

Table 17-13 IPv4 BGP Label Routing Table Properties

Viewing the ARP Table

To view the ARP table:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity > ARP.

Table 17-14 describes the information that is displayed in the ARP table.

Viewing the NDP Table

Neighbor Discovery Protocol (NDP) is used with IPv6 to discover other nodes, determine the link layer addresses of other nodes, find available routers, and maintain reachability information about the paths to other active Neighbour nodes.

NDP functionality includes:

• Router discovery
• Autoconfiguration of addresses (stateless address autoconfiguration [SLAAC])
• IPv6 address resolution (replaces Address Resolution Protocol [ARP])
• Neighbour reachability (neighbour unreachability detection [NUD])
• Duplicate address detection (DAD)
• Redirection

To view the NDP table:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity > ARP Entity.

Step 3 Click the NDP Table tab.

Figure 17-18 shows an example of the NDP Table tab.

Figure 17-18 NDP Table in Logical Inventory

Table 17-15 describes the information displayed for NDP.

Viewing Rate Limit Information

To view rate limit information:

Step 1 Right-click the required element in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity.

Step 3 In the IP Interfaces tab, double-click the required interface to view the IP interface properties. If a rate limit is configured on the IP interface, the Rate Limits tab is displayed.

Note Rate Limit information applies only to certain operating systems, such as Cisco IOS.

Table 17-16 describes the information that is displayed in the Rate Limits tab of the IP Interface Properties dialog box.

Viewing VRRP Information

Virtual Router Redundancy Protocol (VRRP) is a non-proprietary redundancy protocol that is designed to increase the availability of the static default gateway servicing hosts on the same subnet. This increased reliability is achieved by advertising a virtual router (a representation of master and backup routers acting as a group) as a default gateway to the hosts instead of one physical router. Two or more physical routers are then configured to stand for the virtual router, with only one doing the actual routing at any given time. If the current physical router that is routing the data on behalf of the virtual router fails, another physical router automatically replaces it. The physical router that forwards data on behalf of the virtual router is called the master router; physical routers standing by to take over for the master router if needed are called backup routers.

To view VRRP information:

Step 1 Double-click the required element in the Vision client.

Step 2 In logical inventory, choose Logical Inventory > Routing Entities > Routing Entity.

Step 3 In the IP Interfaces tab, double-click the required interface to view the IP interface properties. If VRRP is configured on the IP interface, the VRRP Groups tab is displayed.

Figure 17-19 VRRP Properties in IP Interface Properties Window

Table 17-17 describes the information in the VRRP Groups tab.

Viewing Label Switched Entity Properties

Logical inventory can display any or all of the following tabs for label switched entities, depending on the configuration:

• Label Switching Table—Describes the MPLS label switching entries used for traversing MPLS core networks.
• LDP Neighbours—Details all MPLS interface peers that use the Label Distribution Protocol (LDP). LDP enables Neighbouring provider (P) or PE routers acting as label switch routers (LSRs) in an MPLS-aware network to exchange label prefix binding information, which is required to forwarding traffic. The LSRs discover potential peers in the network with which they can establish LDP sessions in order to negotiate and exchange the labels (addresses) to be used for forwarding packets.

Two LDP peer discovery types are supported:

– Basic discovery—Used to discover directly connected LDP LSRs. An LSR sends hello messages to the all-routers-on-this-subnet multicast address, on interfaces for which LDP has been configured.

– Extended discovery—Used between indirectly connected LDP LSRs. An LSR sends targeted hello messages to specific IP addresses. Targeted sessions are configured because the routers are not physically connected, and broadcasting would not reach the peers. The IP addresses of both peers are required for extended discovery.

If two LSRs are connected with two separate interfaces, two LDP discoveries are performed.

• MPLS Interfaces—Contains information on MPLS interfaces and whether traffic engineering tunnels are configured on an interface.
• MPLS Label Range—Identifies whether MPLS uses static or dynamic routing, and the label range.
• Traffic Engineering LSPs—Describes the MPLS traffic engineering Label Switched Paths (LSPs) provisioned on the switch entity. MPLS traffic engineering LSP, an extension to MPLS TE, provides flexibility when configuring LSP attributes for MPLS TE tunnels.
• VRF Table—Describes MPLS paths that terminate locally at a VRF.

To view information for label switched entities:

Step 1 Double-click the required device in the Vision client.

Step 2 In the logical inventory window, choose Logical Inventory > LSEs > Label Switching.

Table 17-18 describes the information that is displayed for label switched entities.

Step 3 Double-click an entry in any of the tables to view additional properties for that entry.

Multicast Label Switching (mLADP)

Multicast Label Distribution protocol (mLDP) provides extensions to the Label Distribution Protocol (LDP) for the setup of point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) Label Switched Paths (LSPs) in MPLS networks. A P2MP LSP allows traffic from a single root (or ingress) node to be delivered to a number of leaf (or egress) nodes.

A MP2MP LSP allows traffic from multiple ingress nodes to be delivered to multiple egress nodes. Only a single copy of the packet will be sent on any link traversed by a multipoint LSP. Container is the holder of MPLS MLDP databases and neighbors instances for Multicast.

Viewing MLDP Database Information

To view the MLDP database information:

Step 1 Double-click the required device in the Vision client.

Step 2 In the logical inventory window, choose Logical Inventory > LSEs > Label Switching > Multicast Label Switching > Databases. The database information is displayed in the MLDP Databases content pane.

Step 3 Select a database from the content pane, right-click and choose the Properties option. The MLDP Database Properties dialog box is displayed. You can click on the tabs to view more details.

Table 17-20 describes the information that is displayed for MLDP Database Properties dialog box.

Viewing the MLDP Neighbors Information

To view information of MLDP neighbors:

Step 1 Double-click the required device in the Vision client.

Step 2 In the logical inventory window, choose Logical Inventory > LSEs > Label Switching > Multicast Label Switching > MLDP Neighbors. The MLDP peer information is displayed in the MLDP Peers content pane.

Step 3 Select a peer id from the content pane, right-click and choose the Properties option. The Peer ID Properties dialog box is displayed.

Table 17-21 describes the information that is displayed for Peer ID Properties dialog box.

Viewing BGP Neighbor Service Alarm with VRF Name

BGP neighbor loss VRF due to oper and BGP neighbor found service alarms are raised on the BGP links for any mis-configurations that shuts down physical interfaces or any other scenario that might break the BGP neighborship. If a BGP neighbor service alarm is configured with the VRF, the VRF name is displayed as part of the Location links for a BGP neighbor loss VRF due to oper and BGP neighbor found service alarms. For example, Figure 17-20 shows the BGP neighbor service alarms displayed with the VRF Name.

Figure 17-20 Service Alarm with VRF Name

To view the VRF details, click the links available in the Location field. For example, the following figure 17-21, shows a link properties of a BGP Service alarm with VRF Name.

Figure 17-21 Link Properties with VRF Information

Viewing MP-BGP Information

The MP-BGP branch displays information about a router’s BGP neighbors and cross-connect VRFs.

Note If there are multiple MP-BGP links between two devices, the Vision client displays each link in the content pane map view.

To view MP-BGP information:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > MPBGPs > MPBGP.

Table 17-22 describes the information that is displayed for MP-BGP.

Viewing 6rd Tunnel Properties

IPv6 rapid deployment (6rd) is a mechanism that allows stateless tunneling of IPv6 over IPv4. For information on the devices that support 6rd, refer to Cisco Prime Network 5.1 Supported VNEs.

To view 6rd tunnel properties:

Step 1 In the Vision client, double-click the required device.

Step 2 In the Inventory window, choose Logical Inventory > 6rd Tunnels.

The 6rd tunnel properties are displayed as shown in Figure 17-22.

Figure 17-22 6rd Tunnel Properties in Logical Inventory

Table 17-23 describes the information displayed for 6rd tunnels.

Viewing BFD Session Properties

Bidirectional Forwarding Detection (BFD) is used to detect communication failures between two elements, or endpoints, that are connected by a link, such as a virtual circuit, tunnel, or LSP. BFD establishes sessions between the two endpoints over the link. If more than one link exists, BFD establishes a session for each link.

Prime Network supports BFD with the following protocols: BGP, IPv4 (static), IPv6 (static), IS-IS, LAG (Ether channel), MPLS TE, MPLS-TP, and OSPF.

To view BFD session properties that are configured on an element:

Step 1 In the Vision client, double-click the required device.

Step 2 In the Inventory window, choose Logical Inventory > Bidirectional Forwarding Detection.

The properties for BFD sessions are displayed as shown in Figure 17-23.

Figure 17-23 BFD Session Properties

Table 17-24 describes the information displayed for BFD sessions.

For MPLS-TP BFD sessions, the information in Table 17-25 is displayed.

Step 3 To view additional properties, double-click the required entry in the Sessions table.

Table 17-26 describes the information that is displayed in the Session Properties window.

BFD Single-Hop Authentication

The BFD Single-Hop Authentication feature enables authentication for single-hop Bidirectional Forwarding Detection (BFD) sessions between two directly connected devices. This feature supports Message Digest 5 (MD5) and Secure Hash Algorithm 1 (SHA-1) authentication types. The BFD templates can be configured only if the BFD sessions are enabled.

BFD Templates Support

BFD (Bidirectional Forwarding Detection Templates) are the new features added in CPT devices. Prime Network uses the below Telnet or CLI Command to get the BFD templates in existing CPT devices.

Show running-config|section bfd-template

Cerent Trap Support

Cerent traps are alarms supported for CPT devices. There are 170 traps supported.There are various kinds of traps supported which are listed below:

• Communications
• Equipment
• Environmental
• Integrity Violation
• Quality of Service

The alarms can be categorized by their severity such as Critical, Major, Minor, Not Reported and Not Alarmed. Examples of each severity categories are as follows:

• Critical- Equipment failure
• Major- High Voltage, Battery Failure
• Minor- Loss of frame, Loss of signal
• Not Reported- Unqualified PPM Inserted
• Not Alarmed- Transit Node Clock Traceable

Change Settings in Cisco Transport Controller (CTC)

Any configurations settings made in CPT should be done through CTC. To receive traps in a particular server, that server IP needs to be entered in the device through CTC. Most of the traps are on device dependencies.

CMP Tool

The default trap format can be used to send the alarms through CMP tool which can be generated in Prime Network. The default trap format is given as follows:

<key name="trap"><key name=""><entry name="">sendtrap -V2 10.105.39.217 -ccellbus -r162 -o1.3.6.1.2.1.1.3.0 -mt1166470595 -o1.3.6.1.6.3.1.1.4.1.0 -md1.3.6.1.4.1.3607.6.10.30.0.1670 -o1.3.6.1.4.1.3607.6.10.100.10.20 -mo03/Nov/2001 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.80.1.1670 -mi50 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.20.1.1670 -mi50 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.60.1.1670 -mi1 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.30.1.1670 -mi0 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.40.1.1670 -mi1 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.50.1.1670 -mi0 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.100.1.1670 -md1.3.6.1.4.1.3607.6.10.30.0.2110 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.120.1.1670 -mi30 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.130.1.1670 -mi10 -o1.3.6.1.4.1.3607.6.10.20.30.20.1.140.1.1670 -mi10 -o1.3.6.1.6.3.18.1.3.0 -ma10.104.120.46</entry></key></key>

Link and Port Parameters

The link and port parameters are scripts which can be navigated from Device->Port->Interface-> right click Commands->Configuration->Scripts. The link and port parameters are supported for the following auto populated UI attributes:

Ethernet Parameter Configuration

• MTU
• Link State
• Expected Speed
• Expected Duplex
• Operating Flow Control
• Carrier Delays
• Auto Negotiation

Port Parameter Configuration

• Port Name
• Admin State
• AINS Soak
• Reach
• Wavelength

L2 Parameter Configuration

• CDP
• DOTIX
• DTP
• LACP
• PAGP
• VTP
• STP

The following are the configuration scripts supported,

• Add Loopback
• Remove Loopback
• Configure CDP
• Configure Ethernet
• Configure L2 Control Protocol
• Configure Port Parameters
• Show Ethernet Parameters
• Show L2 Control Parameters
• Show Port Parameters

Viewing Configuration Scripts in Prime Network

Add Loopback

To view the Add Loopback script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Add Loopback

Step 4 Select the value Loopback from the Attribute combo box.

Step 5 Click on Execute Now button.

Step 6 Verify if Loopback is successfully added.

Remove Loopback

To view the Remove Loopback script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Remove Loopback

Step 4 Click on Execute Now button.

Step 5 Verify if Loopback is successfully removed.

Configure CDP

To view the Configure CDP script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Configure CDP

Step 4 Select the value CDP from the Attribute combo box.

Step 5 Click on Execute Now button.

Step 6 Verify if CDP is successfully configured.

Configure Ethernet

To view the Configure Ethernet script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Configure Ethernet

Step 4 Select the value Admin Status from the Attribute combo box.

Step 5 Click on Execute Now button.

Step 6 Verify if Ethernet is successfully configured.

Configure L2 Control Protocol

To view the Configure L2 Control Protocol script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Configure L2 Control Protocol

Step 4 Select the value STP from the Attribute combo box.

Step 5 Click on Execute Now button.

Step 6 Verify if L2 Control Protocol is successfully configured.

Configure Port Parameters

To view the Configure Port Parameters script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Configure Port Parameters

Step 4 Select the value Reach from the Attribute combo box.

Step 5 Click on Execute Now button.

Step 6 Verify if Port Parameters are successfully added.

Show Port Parameters

To view the Show Port Parameters script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Show Port Parameters

Step 4 Click on Execute Now button.

Step 5 Verify if all Port Parameters are listed.

Show Ethernet Parameters

To view the Show Ethernet Parameters script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Show Ethernet Parameters

Step 4 Click on Execute Now button.

Step 5 Verify if Show Ethernet Parameters are listed.

Show L2 Control Parameters

To view the Show L2 Control Parameters script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Show L2 Control Parameters.

Step 4 Click on Execute Now button.

Step 5 Verify if all L2 Control Parameters are listed.

Show Configure Ethernet

To view the Show Configure Ethernet script:

Step 1 Model the device in Cisco Prime Network Administration.

Step 2 Launch the Cisco Prime Network Vision client and choose Inventory

Step 3 In the physical inventory window, choose Physical inventory >IPortConnector >Commands > Configuration >Show Configure Ethernet

Step 4 Click on Execute Now button.

Step 5 Verify if all the configured Ethernets are listed.

Viewing Cross-VRF Routing Entries

Cross-VRF routing entries display routing information learned from the BGP neighbors (BGP knowledge base).

To view properties for cross-VRF routing entries:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > MPBGPs > MPBGP.

Step 3 Click the Cross VRFs tab.

Step 4 Double-click the required entry in the list of cross-VRFs.

The Cross VRF Properties window is displayed, containing the information described in Table 17-27 .

Viewing Pseudowire End-to-End Emulation Tunnels

The Pseudowires branch in logical inventory displays a list of the Layer 2 tunnel edge properties (per edge), including tunnel status and VC labels.

To view pseudowire properties:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > Pseudowires.

The Tunnel Edges table is displayed and contains the information described in Table 17-28 .

Table 17-28 Pseudowires Branch 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: Aggregation groups are linked to Ethernet Link Aggregation in logical inventory. ATM interfaces are linked to the port in physical inventory and the ATM interface. ATM VCs are linked to the port in physical inventory and the Port IP Properties table. CEM groups are linked to the port in physical inventory and the CEM Group table. EFPs are linked to the port in physical inventory and the EFPs table. IMA groups are linked to IMA Groups in logical inventory. Local switching entities are linked to Local Switching Entity in logical inventory. VLANs are linked to Bridges in logical inventory. VSIs are linked to the VSI entry in logical inventory.
VC ID	Tunnel identifier, hyperlinked to the PTP Layer 2 MPLS Tunnel Properties window.
SAII	Specifies the Source Access Individual Identifier (SAII) of the tunnel. Note The SAII attribute can be configured only if the Pseudowire type is FEC129 TYPE II.
TAII	Specifies the Target Attachment Individual Identifier (TAII) of the tunnel. Note The TAII can be configured only if the Pseudowire type is FEC129 TYPE II.
Pseudowire Type	Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN Basic, PPP, SAToP or FEC129 TYPE II.
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 Tunnel	Path to be used for MPLS pseudowire traffic.
Local Router IP	IP address of this 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.
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 Name	Specifies the name of the associated Ethernet Virtual Circuits (EVC)

Viewing MPLS TE Tunnel Information

Prime Network automatically discovers MPLS TE tunnels and enables you to view MPLS TE tunnel information in inventory.

To view MPLS TE tunnel information:

Step 1 Right-click the required device in the Vision client and choose Inventory.

Step 2 In the logical inventory window, choose Logical Inventory > Traffic Engineering Tunnels.

Table 17-29 describes the information that is displayed in the Tunnel Edges table.

The Traffic Engineering LSPs tab in the LSEs branch in logical inventory displays TE tunnel LSP information.

For details about the information displayed for TE tunnel LSPs, see Traffic Engineering LSPs.

Locking/Unlocking MPLS-TP Tunnels in Bulk

An MPLS-TP network has one or multiple LSPs running between endpoint devices. If you want to shutdown one of the interfaces in the network, the MPLS-TP packet must be diverted through an alternative LSP. This can be achieved by locking the interface. Before attempting to lock or unlock a tunnel, ensure that MPLS-TP tunnels have been configured for the link. Also, ensure that you have the appropriate rights (Configurator and above) to lock or unlock a tunnel.

The MPLS-TP bulk lockout/unlock option in Prime Network allows you to lock or unlock multiple MPLS-TP tunnels on different VNEs at the same time.

Your permissions determine whether you can run these commands (see Permissions for Managing MPLS Services). To find out if a device supports these commands, see the Cisco Prime Network 5.1 Supported Cisco VNEs.

Locking MPLS-TP Tunnels

To lock MPLS-TP tunnels in bulk:

Step 1 In the map view, right-click the required link and choose Properties.

Step 2 In the link properties window, right-click on the required physical link and choose the Show MPLS-TP tunnels option. The MPLS-TP tunnels’ commands dialog box is displayed, which lists all the tunnels in the selected link.

Step 3 In the MPLS-TP tunnels’ commands dialog box, choose the tunnels that you want to lock and select the Lock Out option in the Commands field.

Step 4 Click Execute Now. You are prompted to confirm the lockout operation.

Step 5 Click Yes to confirm. A message is displayed confirming that the selected tunnels have been locked. The status of the tunnel is automatically updated as Lockout(UP) after this operation.

Unlocking MPLS-TP Tunnels

To unlock MPLS-TP tunnels in bulk:

Step 1 In the map view, right-click the required link and choose Properties.

Step 2 In the link properties window, right-click on the required physical link and choose the Show MPLS-TP tunnels option. The MPLS-TP tunnels’ commands dialog box is displayed, which lists all the tunnels in the selected link.

Step 3 In the MPLS-TP tunnels’ commands dialog box, select the locked tunnels that you want to unlock and select the Unlock option in the Commands field.

Step 4 Click Execute Now. You are prompted to confirm the unlock operation.

Step 5 Click Yes to confirm. A message is displayed confirming that the selected tunnels have been unlocked. The status of the tunnels is automatically updated as Active(UP) after this operation.

Note If you attempt to unlock a tunnel that is not locked, a message is displayed indicating that there are no valid tunnels to perform the unlock operation.

Linear Protection for MPLS-TP

As explained earlier, MPLS-TP is the transport profile that fulfills the deployment in the network for the MPLS technology. This technology provides fast protection switching for end-to-end segments wherein the protection switching time is generally less than 50 milliseconds.

Protection switching is a mechanism wherein route and resources of a protection path are reserved for a selected working path or set of working paths.

Linear protection provides rapid and simple protection switching because it can operate between any pair of points within the network. For every working Label Switched Paths (LSP) in the network, there is a protected LSP that is not related to any other working entity. When a working LSP fails, the protected LSP is ready to take up transmission of data.

In Prime Network, the following commands are available for linear protection:

• Force Switch (Lockout)—This command is used to switch normal traffic from a working LSP to a protected LSP. This command can only be applied on a working LSP. If Force Switch is enabled, then the Working LSP becomes standby and the Protected LSP becomes active.
• Manual Switch—This command is used to switch normal traffic from a working LSP to a protected LSP. This command can be applied only on a working LSP. If Manual Switch is enabled, then the working LSP becomes standby and the protected LSP becomes active.

Note The Force Switch and Manual Switch commands are both used to switch traffic from the working LSP to the protected LSP. However, if the Manual Switch command is used, and there is a failure in the protecting LSP, then the working LSP becomes active. In case of the Force Switch command, then the working LSP does not become active if there is a failure in the protecting LSP.+

• Lockout of Protecting (Lockout)—This command is used to switch traffic from the protected LSP to the working LSP. This command can be applied only on a protected LSP. If Lockout of Protecting is enabled, then the working LSP becomes active and the protected LSP becomes standby.
• Clear Force Switch (no Lockout)—This command is used to clear the force switch on a working LSP after which the working LSP becomes active and the protected LSP becomes standby.
• Clear Manual Switch—This command is used to clear the manual switch made on a working LSP, after which the working LSP becomes active and the protected LSP becomes standby.
• Clear Lockout of Protecting (no Lockout)—This command is used to clear the lockout of protecting made on a protected LSP. The working LSP becomes standby and the protected LSP becomes active after this command is executed.

Figure 17-24 depicts the MPLS-TP topology along with the working and protected LSPs:

Figure 17-24 Linear Protection for MPLS-TP

Note In the above figure, you can find working and protected LSPs between two routers. In case of maintenance or network upgrade, the Force Switch and Manual Switch commands can be used to shut down the working LSP link. Similarly, the Lockout of Protecting command can be used to shut down the protected LSP link.

To switch traffic using the Force Switch or Manual Switch command:

Step 1 In the map view, right-click the required link and choose Properties. A list of tunnels for the selected link is displayed.

Step 2 Right-click on the required physical link and choose the Manage MPLS-TP tunnels option. The MPLS-TP tunnels’ commands dialog box is displayed.

Note If there are no MPLS-TP tunnels configured for the selected link, then a message indicating the absence of MPLS-TP tunnels is displayed.

Step 3 In the MPLS-TP tunnels’ commands dialog box, select the working LSP tunnel and select Force Switch (Lockout) or Manual Switch in the Commands field.

Step 4 Click Execute Now. You are prompted to confirm the operation.

Step 5 Click Yes to confirm. The status of the working LSP is updated as Standby and the status of the protected LSP is updated as Active after this operation.

To switch traffic using the Lockout of Protecting command:

Step 1 In the map view, right-click the required link and choose Properties. A list of tunnels for the selected link is displayed.

Step 2 Right-click on the required physical link and choose the Manage MPLS-TP tunnels option. The MPLS-TP tunnels’ commands dialog box is displayed.

Step 3 In the MPLS-TP tunnels’ commands dialog box, select the protected LSP tunnel and select Lock of Protecting in the Commands field.

Step 4 Click Execute Now. You are prompted to confirm the operation.

Step 5 Click Yes to confirm. The status of the working LSP is updated as Active and the status of the protected LSP is updated as Standby after this operation.

To clear the Force Switch or Manual switch on a working LSP:

Step 1 In the map view, right-click the required link and choose Properties. A list of tunnels for the selected link is displayed.

Step 2 Right-click on the required physical link and choose the Manage MPLS-TP tunnels option. The MPLS-TP tunnels’ commands dialog box is displayed.

Step 3 In the MPLS-TP tunnels’ commands dialog box, select the working LSP tunnel that has been locked and select Clear Force Switch or Clear Manual Switch in the Commands field.

Step 4 Click Execute Now. You are prompted to confirm the operation.

Step 5 Click Yes to confirm. The status of the working LSP is updated as Active and the status of the protected LSP is updated as Standby after this operation.

To clear the Lockout of Protecting on a protected LSP:

Step 1 In the map view, right-click the required link and choose Properties. A list of tunnels for the selected link is displayed.

Step 2 Right-click on the required physical link and choose the Manage MPLS-TP tunnels option. The MPLS-TP tunnels’ commands dialog box is displayed.

Step 3 In the MPLS-TP tunnels’ commands dialog box, select the protected LSP tunnel that has been locked and select Clear Lockout of Protecting in the Commands field.

Step 4 Click Execute Now. You are prompted to confirm the operation.

Step 5 Click Yes to confirm. The status of the protected LSP is updated as Active and the status of the working LSP is updated as Standby after this operation.

Visualization Status Enhancements- MPLS TP Tunnel

In the MPLS TP Tunnel, the following visualization status enhancements have been carried out:

Non Eligible LSPs

If the tunnel is not configured with protected LSP, i.e., the tunnel is configured with working LSP (Active-UP); the information column displays the value as Protected LSP is not configured. See Figure 17-26.This information is displayed for all non-eligible LSPs which are not eligible for bulk flow operations like FS, LOP, MS, LOCK.

Figure 17-25 Viewing the Working LSPs and Protected LSPs

In the above Figure 17-25, both the status of Working LSP and the Protected LSP are in up state. So, the Information field is blank.

Lockout State

In the Lockout State, information value has been changed. If the Working LSP is down, it displays Working LSP is Locked Out. If the Protected LSP is down, it displays that the Protected LSP is Locked Out

Figure 17-26 Viewing the Lockout States of LSP

Figure 17-27 Viewing the Commands for Eligible LSPs

In the above Figure 17-27 the commands that are executed on LSPs on the link are displayed.

It will be enabled only when an eligible LSP is working/protected on the link.

Other Descriptions displayed in the Information Column are :

• If only the Working LSP is configured, you will not be allowed to Lock the Working LSP since, there is no Protected member to carry the traffic; the information column displays the value as Protected LSP is not configured.
• If both the “Working LSP EndPoints” and “Protected LSP EndPoints” are configured in the same physical link, which informs that this tunnel will not be allowed for performing the Lockout operations; the information column displays the value as Both LSPs are configured on the same physical link.
• If the device's Software Version in which the “Manual Switch” feature is disabled; the information column displays the value as Manual switch is disabled.
• If both the Working (Active) and Protected LSPs are in Down state; the information column displays the value as Working and protected LSPs are down.
• If the tunnel is not eligible for any Linear Protection operations as it is disabled, the information column displays the value as Linear Protection is disabled.

Viewing FEC 129 Type I-based Pseudowire from VSI Inventory

To view the FEC 129 Type I-based pseudowire from VSI logical inventory:

Step 1 To 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.

Table 17-31 describes the information that is displayed for the selected VSI.

Note The AGI, SAII, and TAII are the new attributes supported for the FEC 129 pseudowires.

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 1 In the Vision client map view, select a link connected to two devices and open the link quick view window.

Step 2 Click 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.

Note If the link is down, it will be displayed in Red and the active links are displayed as green.

Step 3 To view the FEC 129 properties in detail, click Properties in the link properties window.

Step 4 Select 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.