Table Of Contents

Monitoring MPLS Services

User Roles Required to Work with MPLS Networks

Viewing VPNs in Cisco ANA NetworkVision

Viewing Additional VPN Properties

Managing VPNs

Creating a VPN

Adding a VPN to a Map

Removing a VPN from a Map

Moving a Virtual Router Between VPNs

Working with VPN Overlays

Adding a VPN Overlay to a Map

Managing a VPN Overlay Display in the Map View

Displaying VPN Callouts in a VPN Overlay

Working with CE Devices

Connecting a CE Device

Disconnecting a CE Device

Showing or Hiding a CE Device

Working with Tunnels

Adding a Tunnel to a VPN

Removing a Tunnel

Working with LCAs and LCPs

Creating an LCA

Moving an LCA

Deleting an LCA

Moving an LCP

Jumping to an Adjacent LCP

Monitoring MPLS Services

Viewing VPN Properties

Viewing Site Properties

Viewing VRF Properties

Displaying VRF Egress and Ingress Adjacents

Viewing Routing Entities

Viewing the ARP Table

Viewing the NDP Table

Viewing Rate Limit Information

Viewing a Label Switched Entity

MPLS Interfaces Tab

Label Switching Table Tab

Traffic Engineering LSPs Tab

VRF Table Tab

LDP Neighbors Tab

Viewing MP-BGP Information

Viewing BFD Properties

Viewing a Port Configuration

Viewing Cross-VRF Routing Entries

Viewing Pseudowire End-to End Emulation Tunnels

Viewing MPLS TE Tunnel Information

Monitoring MPLS Services

---

The following topics describe how to view and manage aspects of Multiprotocol Label Switching (MPLS) services using Cisco ANA NetworkVision, including the MPLS service view, business configuration, and maps. The topics also describe the device inventory specific to MPLS VPNs, including routing entities, label switched entities (LSEs), BGP neighbors, Multiprotocol BGP (MP-BGP), VRF instances, pseudowires, and TE tunnels. Topics include:

•User Roles Required to Work with MPLS Networks

•Viewing VPNs in Cisco ANA NetworkVision

•Managing VPNs

•Working with VPN Overlays

•Working with CE Devices

•Working with Tunnels

•Working with LCAs and LCPs

•Monitoring MPLS Services

For more information about MPLS and Cisco ANA, see the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide.

User Roles Required to Work with MPLS Networks

Table 17-1 identifies the roles that are required to work with MPLS networks. Cisco ANA determines whether you are authorized to perform a task as follows:

•For GUI-based tasks (tasks that do not affect devices), authorization is based on the default permission that is assigned to your user account.

•For device-based tasks (tasks that do affect devices), authorization is based on the default permission that is assigned to your account. That is, whether the device is in one of your assigned scopes and whether you meet the minimum security level for that scope.

For more information on user authorization, see the Cisco Active Network Abstraction 3.7.1 Administrator Guide.

Table 17-1 Default Permission/Security Level Required for Working with MPLS Networks  

Task	Viewer	Operator	OperatorPlus	Configurator	Administrator
VPNs
Add tunnels to VPNs	—	—	—	—	X
Add VPNs to a map	—	—	X	X	X
Create VPNs	—	—	X	X	X
Display VRF egress and ingress adjacents	—	—	—	—	X
Move virtual routers between VPNs	—	X	X	X	X
Remove tunnels from VPNs	—	—	—	—	X
Remove VPNs from a map	—	—	X	X	X
View VPN properties	—	—	—	—	X
View VPNs in Cisco ANA NetworkVision	X	X	X	X	X
View VRF properties	—	—	—	—	X
VPN Overlays
Add VPN overlays	X	X	X	X	X
Display or hide VPN overlays	X	X	X	X	X
Remove VPN overlays	X	X	X	X	X
Routing Entities
View the ARP table	—	—	—	—	X
View the NDP table	—	—	—	—	X
View rate limit information	—	—	—	—	X
Other
View BFD properties	—	—	—	—	X
View cross-VRF routing entries	—	—	—	—	X
View LSE properties	—	—	—	—	X
View MP-BDP information	—	—	—	—	X
View MPLS TE tunnel information	—	—	—	—	X
View port configurations	—	—	—	—	X
View pseudowire end-to-end emulation tunnels	—	—	—	—	X

Viewing VPNs in Cisco ANA NetworkVision

Figure 17-1 shows a VPN displayed in the Cisco ANA NetworkVision map view. In this example, the VPN is selected in the navigation pane, so the VPN details, such as virtual routers and IP interfaces, are not shown in the map view.

Figure 17-1 VPN in Cisco ANA NetworkVision Map View

1	VPN in the navigation tree	4	Network elements
2	Virtual routers	5	VPN in the map view
3	Sites	6	VPN links (IPv4 and IPv6 aware)

Figure 17-2 shows a VPN with details, including virtual routers, IP interfaces, and network elements, displayed in the Cisco ANA NetworkVision map view.

Figure 17-2 VPN in Cisco ANA NetworkVision Map View with VRFs and Sites

1	Virtual router
2	Sites
3	Network elements

The Cisco ANA NetworkVision navigation pane displays the VPN business elements in a tree-and-branch representation. Each business element is represented by an icon in a color that reflects the highest alarm severity. The icon might also have a management state badge or alarm. For more information about icon severity colors and badges, see Network Element Status Indicators, page 2-17.

Table 17-2 shows the VPN icons in the Cisco ANA NetworkVision map view.

Table 17-2 VPN Icons in Cisco ANA NetworkVision Map View 

Icon	Description
	Root (map name) or aggregation
	VPN
	Virtual router
	Site
	Site business element with an actively associated, hidden CE device
	LCA business element
	LCP business element
	LCP business element with an actively assigned tunnel edge for a hidden CE device

The highest level of the navigation pane displays the root or map name. The branches display the VPN and aggregated business elements as well as their names. The Layer 3 VPN sub-branch displays the virtual routers and sites contained in the VPN along with the names of the business elements. In addition, CE devices can also be displayed in the Layer 3 VPN sub-branches. The Layer 2 VPN sub-branches display the LCAs and LCPs contained in the VPN along with the names of the business elements. In addition, CE devices can also be displayed in the Layer 2 VPN sub-branches. If you select an aggregated business element in the navigation pane, the map view displays the business elements contained within the aggregated business element.

The Cisco ANA NetworkVision map view displays the VPN business elements and aggregated business elements loaded in the map view, along with the names of the business elements. In addition, the map view displays the VPN topology (between the virtual routers in the VPNs) and the topology and associations between other business elements. After you select the root in the navigation pane, the map view displays all the VPNs.

Cisco ANA presents tickets related to the map in the ticket area, which allows you to view and manage the VPN tickets.

Viewing Additional VPN Properties

Cisco ANA NetworkVision 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-3 shows the additional properties available for VPN entities.

Table 17-3 Displaying Additional VPN Properties 

Object	Drill-Down Display	For Additional Information
VPN	•Double-clicking a VPN displays the participating VRFs, sites, and network elements in the navigation pane and map view. •Right-clicking a VPN and choosing Properties displays the VPN Properties window.	Viewing VPN Properties
VRF	Double-clicking a VRF displays the VRF properties window	Viewing VRF Properties
Site	Double-clicking a site displays the IP Interface Properties window	Viewing Site Properties
Link	Double-clicking a link displays the link properties window. The properties depend on the link type.	Chapter 5, "Working with Links"

Managing VPNs

The following topics describe:

•Creating a VPN

•Adding a VPN to a Map

•Removing a VPN from a Map

•Moving a Virtual Router Between VPNs

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 Cisco ANA NetworkVision 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-2).

---

•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 VPNs to a map view if the VPNs were previously discovered by Cisco ANA and are not currently displayed in the map.

---

Note Adding VPNs will affect other users if they are working with the same map.

---

To add an existing VPN to a map:

---

Step 1 In Cisco ANA NetworkVision, 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," Cisco ANA displays VPNs that have "net" in their names whether at the beginning of the name, the middle, or the end.

•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 Add.

The VPN is loaded in the map view that is displayed in the Cisco ANA NetworkVision content pane.

Step 6 Click Close.

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

---

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 Cisco ANA 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 will affect 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, sites, LCAs, or LCPs from the map without removing the VPN.

To remove a VPN, in the Cisco ANA NetworkVision 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 the overlay is run, the changes do not appear in the current overlay.

---

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 Cisco ANA NetworkVision 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.

---

Working with VPN Overlays

The following topics describe:

•Adding a VPN Overlay to a Map

•Managing a VPN Overlay Display in the Map View

•Displaying VPN Callouts in a VPN Overlay

Adding a VPN Overlay to a Map

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 create a VPN overlay:

---

Step 1 In Cisco ANA NetworkVision, display the network map for which you want to create 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 either 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," Cisco ANA displays VPNs that have "net" in their names whether net appears at the beginning of the name, the middle, or at the end: for example, Ethernet.

•Choose Show All to display all the VPNs.

Step 4 Select the VPN that you want to add 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 added to a map, you can manage its display using the overlay tools in the main toolbar using any of the following options:

•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 toolbar 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-3) enable you to view the VPN traffic links for a specific link (either bidirectional or unidirectional).

Figure 17-3 Callouts Window

1	Link details and direction. In this example, the link is from P-North to PE-West.	3	Details of sites using the link and interlinks. In this example, the site PE-West is linked to all sites on PE-South.
2	Details of the sites using the link and interlinks. In this example, the site PE-88 is linked to site PE-West.	4	Link details and the direction. In this example, the link is from PE-West to P-North.

To display or hide the callouts:

---

Step 1 In the Cisco ANA NetworkVision 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.

---

Working with CE Devices

---

Note The information in this section applies only to pseudowires that existed before upgrading to Cisco ANA 3.7.1. For information on managing pseudowires that were added after upgrading to Cisco ANA 3.7,1, see Working with Pseudowires and Pseudowire Overlays, page 12-77.

---

The following topics describe:

•Connecting a CE Device

•Disconnecting a CE Device

•Showing or Hiding a CE Device

Connecting a CE Device

---

Note The information in this section applies only to pseudowires that existed before upgrading to Cisco ANA 3.7.1. For information on managing pseudowires that were added after upgrading to Cisco ANA 3.7,1, see Working with Pseudowires and Pseudowire Overlays, page 12-77.

---

The connect CE functionality enables you to create a symbolic link to the overall link between the CE device and the site (IP interface) or Logical Circuit Peers (LCPs). The CE device belongs to the currently displayed map only.

To connect a CE device:

---

Step 1 Do either of the following:

•To add a CE device to a site, choose the VPN in the Cisco ANA NetworkVision navigation pane or map view.

•To add a CE device to an LCP, choose the Logical Circuit Aggregation (LCA).

Step 2 Choose File > Add to Map.

Step 3 From the Add dialog box, choose the device that you want to add.

Step 4 Click OK.

The device is displayed in the navigation pane and the selected map or subnetwork in the Cisco ANA NetworkVision content pane.

---

Note Device alarm tickets do not appear in the ticket area of the Cisco ANA NetworkVision content pane until the device is added to the VPN map view.

---

Step 5 Right-click the site or LCP in the navigation pane or map view and choose Topology > Connect CE Devices.

Step 6 Right-click the device in the navigation pane or map view and choose Topology > Connect to Site/LCP, where Site or LCP displays the details of the site or LCP to be connected.

The site or LCP is connected to the CE device, and the CE device is displayed in the navigation pane and map view. A dashed, dark-gray line indicates the association.

---

Note The Topology > Connect to Site/LCP menu option is not available until after you choose the Topology > Connect CE Device menu option.

---

---

Disconnecting a CE Device

---

Note The information in this section applies only to pseudowires that existed before upgrading to Cisco ANA 3.7.1. For information on managing pseudowires that were added after upgrading to Cisco ANA 3.7,1, see Working with Pseudowires and Pseudowire Overlays, page 12-77.

---

You can disconnect a CE device from its sites or LCPs. To disconnect a CE device, right-click the required CE device or link in the map view and choose Topology > Disconnect CE Device.

The association with the CE device is no longer displayed in the map view.

Showing or Hiding a CE Device

---

Note The information in this section applies only to pseudowires that existed before upgrading to Cisco ANA 3.7.1. For information on managing pseudowires that were added after upgrading to Cisco ANA 3.7,1, see Working with Pseudowires and Pseudowire Overlays, page 12-77.

---

You can show the CE device for a site or LCP in the Cisco ANA NetworkVision navigation pane and map view. You can also display the device associations on the map view after the CE is connected. In addition, you can manually add connected devices (some or all of them) to view them along with the links to sites or LCPs.

To show a connected device, right-click one of the following and choose Show CE Devices:

•A site in the map view displaying the site business element with an actively associated CE device icon (see Table 17-2).

•An LCP in the map view displaying the LCP business element with an actively assigned tunnel edge for the CE device icon.

The connected devices are shown in the navigation pane and map view including the associations.

To hide a connected device, right-click the site or LCP in the Cisco ANA NetworkVision pane or map view connected to the CE device and choose Hide Connected Devices.

The site or LCP with hidden connected devices icon appears. Table 17-4 shows the displayed icons.

Table 17-4 Hidden Device Icons 

Icon	Description
	Site with one or more hidden connected devices.
	LCP with one or more one hidden connected devices.

You can also manually remove some or all of the connected devices in order to hide them along with the links to sites or LCPs.

---

Note Tickets associated with a device are displayed in the ticket pane only when a device or logical part of the device is added to the map view.

---

Working with Tunnels

The following topics describe:

•Adding a Tunnel to a VPN

•Removing a Tunnel

Adding a Tunnel to a VPN

---

Note The information in this section applies only to pseudowires that existed before upgrading to Cisco ANA 3.7.1. For information on managing pseudowires that were added after upgrading to Cisco ANA 3.7,1, see Working with Pseudowires and Pseudowire Overlays, page 12-77.

---

You can add tunnels or partially configured tunnels to a VPN. LCPs with a missing peer are marked with the stranded icon. (For more information about icons, see Table 17-2.) Each tunnel can be associated with only one VPN.

---

Note The topology state between LCPs is a logical link. It does not reflect the actual state of the network.

---

You can do either of the following:

•Add a tunnel (LCP) to an LCA that has been manually created (see Creating an LCA).

•Add a tunnel (LCP) directly to a VPN, in which case the LCA is automatically created beneath the VPN.

To add a tunnel to a VPN:

---

Step 1 In the Cisco ANA NetworkVision navigation pane or a map, right-click an LCA or VPN and choose Topology > Add Tunnel.

The Add Tunnels dialog box (Figure 17-4) displays tunnels not currently attached to a VPN. The Tunnels tab displays the list of pseudowire tunnels (including both tunnel edges). The Stranded Peers tab displays the list of partially configured tunnel edges, so you can add an LCP without its peer, for example, if a tunnel is partially managed, an agent fails to load, or a device is incorrectly configured.

Figure 17-4 Add Tunnels Dialog Box

Step 2 Select the tunnel or stranded peer and click Add.

One of the following occurs:

•If the tunnel or stranded peer is added under an LCA, the link between the peers appears in the map.

•If the tunnel or stranded peer is added under a VPN, Cisco ANA detects the starting point of the PWE3 tunnel edges and groups all of the LCPs that start at the same device into an LCA under the VPN.

---

Note If a tunnel exists between VPNs (for example, an extranet tunnel), add a tunnel to one VPN and then move one LCP to the VPN with which you want to create the extranet tunnel.

---

---

Removing a Tunnel

---

Note The information in this section applies only to pseudowires that existed before upgrading to Cisco ANA 3.7.1. For information on managing pseudowires that were added after upgrading to Cisco ANA 3.7,1, see Working with Pseudowires and Pseudowire Overlays, page 12-77.

---

To remove a tunnel that was added to an LCA or VPN, in the Cisco ANA NetworkVision navigation pane or a map, right-click the LCA or VPN and choose Topology > Remove Tunnel.

Both tunnel sides are removed from the map. You view them in the Add Tunnels dialog box. If the deleted tunnel formed part of an LCA that was created manually, the LCA is still displayed in the navigation or map. If the deleted tunnel formed part of an LCA that was created automatically, the LCA is removed from the navigation and the map, provided no other LCPs exist in the LCA.

---

Note You cannot view MPLS TE tunnels in VPN service view maps; however; you can view the device and topology information. For more information, see Viewing MPLS TE Tunnel Information.

---

Working with LCAs and LCPs

The following topics describe:

•Creating an LCA

•Moving an LCA

•Deleting an LCA

•Moving an LCP

Creating an LCA

You can manually create an LCA and populate it by moving LCPs and tunnels to it. For more information, see Moving an LCP and Adding a Tunnel to a VPN.

To create an LCA:

---

Step 1 In the Cisco ANA NetworkVision window navigation or a map, right-click the VPN and choose Create LCA.

Step 2 In the Create LCA dialog box, enter a unique name for the new LCA.

Step 3 Click OK.

The new LCA is created. It appears in the navigation pane in the Cisco ANA NetworkVision window, beneath the selected VPN, and also appears in the map.

---

Moving an LCA

You can move the LCA to another VPN in the service view map. When you move an LCA, all of the LCPs it contains also move.

To move an LCA:

---

Step 1 In the Cisco ANA NetworkVision navigation or a map, right-click the LCA and choose Edit > Move selected.

Step 2 Right-click the VPN to which you want to move the LCA and choose Edit > Move here.

The LCA moves to the selected VPN and is displayed in the navigation pane and map for the selected VPN.

---

Note All the LCPs move with the LCA.

---

---

Deleting an LCA

You can delete an LCA if it was manually created and either has no LCPs or all the LCPs have reconciliation icons. (To move an LCA to another VPN, see Jumping to an Adjacent LCP.)

To delete the LCA:

---

Step 1 In the Cisco ANA NetworkVision navigation or a map, right-click the required LCA and choose Delete.

Step 2 Click Yes on the confirmation.

The selected LCA is deleted from the database and service view maps of all users.

---

Moving an LCP

You can move an LCP to another VPN or LCA in the service view map.

To move an LCP:

---

Step 1 In the Cisco ANA NetworkVision navigation pane or a map, right-click the LCA and choose Edit > Move selected.

Step 2 Right-click the VPN or LCA to which you want to move the LCP and choose Edit > Move here.

The LCP moves to the VPN or LCA and is displayed in the navigation and map of the selected VPN or LCA.

---

Note If an LCP is moved to a VPN, an LCA is automatically created for it.

---

---

Jumping to an Adjacent LCP

If a service view map displays multiple tunnels, you can quickly access the selected LCP peer appearing in the same map.

To jump to the adjacent LCP, in the Cisco ANA NetworkVision navigation pane or map, right-click the required LCP and choose Jump to Adjacent.

The adjacent LCP is highlighted in the navigation pane and map.

Monitoring MPLS Services

This section provides details for viewing MPLS services and technologies. Topics include:

•Viewing VPN Properties

•Viewing Site Properties

•Viewing VRF Properties

•Displaying VRF Egress and Ingress Adjacents

•Viewing Routing Entities

•Viewing a Label Switched Entity

•Viewing MP-BGP Information

•Viewing BFD Properties

•Viewing a Port Configuration

•Viewing Cross-VRF Routing Entries

•Viewing Pseudowire End-to End Emulation Tunnels

•Viewing MPLS TE Tunnel Information

Viewing VPN Properties

To view the properties of a VPN:

---

Step 1 In the Cisco ANA NetworkVision navigation pane or map view, right-click the VPN and choose Properties.

Step 2 In the VPN Properties window, view the following VPN properties:

•Name—The name of the VPN.

•ID—The unique key automatically assigned to the VPN.

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

---

Viewing Site Properties

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

To view site properties:

---

Step 1 In the Cisco ANA NetworkVision navigation pane or map view, right-click a site and choose Properties.

Step 2 In the Router IP Interface Properties window, view the following site properties:

•Name—The name of the site; for example, ATM4/0.100(10.0.0.1) is a combination of the interface name and IP address used to reach the site.

•Mask—The mask of the specific network.

•Sending Alarms—Whether the alarm for the required port has been enabled (true) or disabled (false).

•IP Address—The IP address of the interface.

•State—The state of the interface, either Up or Down.

•Addresses—A table that displays PE-side IP interface details. Address properties include:

–Subnet—A combination of the IP address and the subnet mask.

---

Note If the site is an IPv6 VPN over MPLS with IPv6 addresses provisioned, the IPv6 addresses are displayed. For more information, see Viewing IPv6 Information, page 16-2.

---

–Type—The address type; for example, Primary, Secondary, or IPv6 Unicast.

–Sending Alarms—Indicates whether the interface is sending alarms.

Step 3 When finished, click Close in the Router IP Interface Properties window.

---

Viewing VRF Properties

Cisco ANA NetworkVision 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:

---

Step 1 Right-click a VRF in the Cisco ANA NetworkVision navigation pane or map view and choose Properties.

The VRF Properties window is displayed (Figure 17-5).

Figure 17-5 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. In addition, the forwarding table also contains MPLS encapsulation information.

Table 17-5 describes the VRF properties that are displayed.

---

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 here.

---

Table 17-5 VRF Properties 

Field	Description
Route Distinguisher	The route distinguisher configured in the VRF.
Name	The name of the VRF.
Description	A description of the VRF, if available.
IPv4 Tab
Export Route Targets	The IPv4 export route targets contained by the VRF.
Import Route Targets	The IPv4 import route targets contained by the VRF.
Route Maps	The route maps for the VRF.
IPv6 Tab
Export Route Targets	The IPv6 export route targets contained by the VRF.
Import Route Targets	The IPv6 import route targets contained by the VRF.
Route Maps	The route maps for the VRF.
IPv4 and IPv6 Route Tables
Destination	The destination of the specific network.
Prefix Length	The length of the network prefix in bits.
Next Hop	The next routing hop.
Outgoing Interface	The name of the outgoing interface; displayed if the Routing Protocol type is local.
Type	The type: Direct (local), Indirect, or Static.
Routing Protocol	The routing protocol used to communicate with the other sites and VRFs: BGP or local.
BGP Next Hop	The Border Gateway Protocol (BGP) next hop. This is the PE address from which to continue to get to a specific address. This field is empty when the routing entry goes to the CE.
Bottom In Label	The innermost label that is expected when MPLS traffic is received.
Bottom Out Label	The innermost label sent with MPLS traffic.
Outer Label	The outermost or top label in the stack used for MPLS traffic.
Sites Tab
Name	The name of the site; for example, ATM4/0.100(10.0.0.1) is a combination of the interface name and IP address used to reach the site.
IP Address	The IP address of the interface.
Mask	The subnet mask.
State	The state of the subinterface: Up or Down.
Associated Entity	Hyperlinked entry to the associated entry in inventory: •For SVI service interfaces, hyperlink to the Carrier Grade NAT entry in logical inventory. •For physical interfaces, hyperlink to the interface in physical inventory. •For link aggregations, hyperlink to the LAG list of interfaces.
Description	A description of the interface.
Input Access List	The access list applied to the inbound traffic of the interface.
Output Access List	The access list applied to the outbound traffic of the interface.
Rate Limits	Measures traffic for the IP interfaces on Cisco devices, including the average rate, normal burst size, excess burst size, conform-action, and exceed action. Note Input access list, output access list, and rate limits parameters apply only to Cisco IOS devices.
IP Sec Map Name	The IP Security (IPsec) map name.
Site Name	The name of the business element to which the interface is attached.
Sending Alarms	Whether or not the interface is configured for sending alarms: True or False.

Step 2 When finished, press Ctrl + F4 to close the VRF Properties window.

---

---

Note You can also open a VRF table by right-clicking the virtual router in the Cisco ANA NetworkVision navigation pane or map view and selecting Open VRF Table. For more information about the columns displayed in the VRF Table window, see Viewing VRF Properties.

---

Displaying VRF Egress and Ingress Adjacents

Cisco ANA enables you to view the exporting and importing neighbors 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:

---

Step 1 Right-click a VRF in the Cisco ANA NetworkVision navigation pane or map view and choose Show VRF Egress Adjacents or Show VRF Ingress Adjacents.

The Adjacents window is displayed.

Step 2 View the ingress and egress adjacent properties:

•Name—The name of the VRF as it appears in the device.

•Route Distinguisher—The route distinguisher configured in the VRF.

•Vrf V6 Table—The IPv6 route distinguisher, if IPv6 is provisioned.

•Sending Alarms—Indicates whether or not the VRF is sending alarms.

---

Note Selecting a specific VRF in the Cisco ANA NetworkVision navigation pane displays the VRF properties. For more information, see Viewing VRF Properties.

---

Step 3 When finished, press Ctrl + F4 to close the Adjacents window.

---

Viewing Routing Entities

To view routing entities, choose Logical Inventory > Routing Entities > Routing Entity. The routing information is displayed as shown in Figure 17-6.

Figure 17-6 Routing Entity Table

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

Table 17-6 Routing Entity Table 

Field	Description
Changes Number	The number of changes to the currently displayed routing entity.
Name	The name of the routing entity.
IP Interfaces Tab
Name	The site name; for example, ATM4/0.100(10.0.0.1) is a combination of the interface name and IP address used to reach the site.
IP Address	The IP address of the interface.
Mask	The details of the dotted decimal mask.
State	The state of the subinterface: Up or Down.
Associated Entity	Interface associated with the routing entity, hyperlinked to its location in physical inventory.
Description	A description of the interface.
Input Access List	If an input access list is assigned to an IP interface, the list is shown as an IP interface property, and a hyperlink highlights the related access list in the Access List table. When an access list is assigned to the inbound traffic on an IP interface, the actions assigned to the packet are performed.
Output Access List	If an output access list is assigned to an IP interface, the list is shown as an IP interface property, and a hyperlink highlights the related access list in the Access List table. When an access list is assigned to the outbound traffic on an IP interface, the actions assigned to the packet are performed.
Rate Limits	If a rate limit is configured on an IP interface, the limit is shown as an IP interface property. This option is checked when a rate limit is defined on the IP interface, meaning the access list is a rate limit access list. IP interface traffic is measured and includes the average rate, normal burst size, excess burst size, conform action, and exceed action. Note Double-clicking a row displays the properties of the IP interface. When a rate limit is configured on the IP interface, the Rate Limits tab is displayed. For more information about rate limits, see Viewing Rate Limit Information. Note The Input Access, Output Access, and Rate Limits parameters apply only to Cisco IOS devices.
IP Sec Map Name	The IP Security (IPsec) crypto map name.
Site Name	The name of the business element to which the interface is attached.
Sending Alarms	Whether or not the interface is configured to send alarms: True or False.
IPv4 and IPv6 Routing Table Tabs
Destination	Destination of the specific network.
Sending Alarms	This option is unavailable.
Outgoing If Name	Name of the outgoing interface; displayed if the Routing Protocol type is local.
Type	Routing type: Direct, Indirect, Static, Other, Invalid, or Unknown.
Next Hop	CE router address from which to continue to get to a specific address. This field is empty when the routing entry goes to a PE router.
Prefix Length	Length of the network prefix in bits.
Route Protocol Type	Routing protocol used to communicate with other routers.

Viewing the ARP Table

Table 17-7 describes the information that is displayed in the ARP table (Logical Inventory > Routing Entities > Routing Entity > ARP).

Table 17-7 ARP Table 

Field	Description
MAC	The interface MAC address.
Interface	The interface name.
IP Address	The interface IP address.
Type	The interface type: •Dynamic—An entry that was learned by the device according to network traffic. •Static—An entry that was learned by a local interface or by configuring a static route. •Other—An entry that was learned by another method not explicitly defined. •Invalid—In SNMP, this type is used to remove an ARP entry from the table.
Sending Alarms	This option is unavailable.

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 neighbor nodes.

NDP functionality includes:

•Router discovery

•Autoconfiguration of addresses (stateless address autoconfiguration [SLAAC])

•IPv6 address resolution (replaces Address Resolution Protocol [ARP])

•Neighbor reachability (neighbor unreachability detection [NUD])

•Duplicate address detection (DAD)

•Redirection

To view the NDP Table, choose Logical Inventory > Routing Entities > Routing Entity > ARP Entity > NDP Table. Figure 17-7 shows an example of the NDP Table tab.

Figure 17-7 NDP Table

Table 17-8 describes the information displayed for NDP.

Table 17-8 NDP Table 

Field	Description
MAC	The interface MAC address.
Interface	The interface name.
IP Address	The interface IPv6 address.
Type	The entry can be one of the following types: •ICMP (Incomplete)—Address resolution is being performed on the entry. A neighbor solicitation (NS) message has been sent to the solicited-node multicast address of the target, but the corresponding neighbor advertisement (NA) message has not yet been received. •REACH (Reachable)—Positive confirmation was received via an NA that the forward path to the neighbor was functioning properly. While in REACH state, the device takes no special action as packets are sent. •STALE—Too much time has elapsed since the last positive confirmation was received that the forward path was functioning properly. While in STALE state, the device takes no action until a packet is sent. •DELAY—Too much time has elapsed since the last positive confirmation was received that the forward path was functioning properly. If no reachability confirmation is received within a specified amount of time, the device sends an NS message and changes the state to PROBE. •PROBE—A reachability confirmation is actively sought by resending neighbor solicitation messages until a reachability confirmation is received. •????—The state is unknown.
Sending Alarms	This option is unavailable.

Viewing Rate Limit Information

Choose Routing Entities  > Routing Entity > IP Interfaces and double-click a specific row in the IP Interfaces tab to display the IP interface properties. If a rate limit is configured on the IP interface, the Rate Limits tab is displayed.

---

Note Rate limit information is relevant only for Cisco IOS devices.

---

The following information is displayed in the Rate Limits tab of the IP Interface Properties dialog box:

Field	Description
Type	The rate limit direction, either Input or Output.
Max Burst	Excess burst size in bytes.
Normal Burst	Normal burst size in bytes.
Bit Per Second	Average rate in bits per second.
Conform Action	The action that can be performed on the packet if it conforms to the specified rate limit (rule), for example, continue, drop, change a bit, or transmit.
Exceed Action	The action that can be performed on the packet if it exceeds the specified rate limit (rule), for example, continue, drop, change a bit, or transmit.
Access List	A hyperlink that highlights the related access list in the Access List table.
Sending Alarms	This option is unavailable.

Viewing a Label Switched Entity

The LSEs logical inventory branch displays incoming and outgoing label information. The Label Switching Properties window includes the following information:

•Local LDP ID—The local Label Distribution Protocol (LDP) identifier.

•LDP Process State—The state of the LDP process, such as Running.

The Label Switching Properties window can contain the following tabs, depending on the configuration:

•MPLS Interfaces Tab

•Label Switching Table Tab

•Traffic Engineering LSPs Tab

•VRF Table Tab

•LDP Neighbors Tab

MPLS Interfaces Tab

The MPLS Interfaces tab provides information about the MPLS interfaces. The following information is displayed:

•ID—The interface identification.

•Distribution Protocol Type—The protocol used to establish the session, which may be LDP or TDP (Tag Distribution Protocol).

•MPLS TE Properties—Indicates whether or not MPLS traffic engineering (TE) properties are included, either checked (included) or unchecked (not included).

•Discovery Protocols—The discovery protocols used on this interface.

•Sending Alarms—Indicates whether or not the interface is sending alarms.

Label Switching Table Tab

The Label Switching Table tab describes the MPLS label switching entries used for traversing the MPLS core networks. Table 17-9 describes the information that is displayed in the Label Switching Table tab.

Table 17-9 Label Switching Table Tab 

Field	Description
Incoming Label	The details of the incoming MPLS label.
Action	The type of action; POP, swap, aggregate, or untagged. If an action is defined as POP, an outgoing label is not required. If an action is defined as untagged, an outgoing label is not present.
Outgoing Label	The details of the outgoing MPLS label.
Out Interface	The name of the outgoing interface, displayed as a hyperlink to the port subinterface in the device physical inventory.
IP Destination	The IP address of the destination network.
Destination Mask	The subnet mask of the destination network.
Next Hop	The IP address of the next MPLS interface in the path. The IP address is used for resolving the MAC address of the next MPLS interface that you want to reach.
Sending Alarms	This option is unavailable.

When a TE tunnel starts, you can view the initial TE tunnel information by choosing Logical Inventory > LSEs > Label Switching > Traffic Engineering LSPs. For more information, see Viewing MPLS TE Tunnel Information.

Traffic Engineering LSPs Tab

The Traffic Engineering LSPs tab 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. Table 17-10 describes the information displayed in the Traffic Engineering LSPs tab.

Table 17-10 Traffic Engineering LSPs Tab 

Field	Description
LSP Name	The LSP name.
LSP Type	The LSP role: Head, Tail, Middle, All, or Remote.
Source Address	The source IP address.
Destination Address	The destination IP address.
In Label	The input label.
In Interface	The input interface.
Out Interface	The output interface.
Out Label	The output label.
Average Bandwidth (Kbps)	The average tunnel bandwidth in Kb/s.
LSP ID	The LSP identifier.
Burst (Kbps)	The tunnel burst rate, in Kb/s.
Peak (Kbps)	The tunnel peak rate, in Kb/s.
FRR TE Tunnel	The Fast Reroute (FRR) TE tunnel name, hyperlinked to the routing entity in logical inventory.
FRR TE Tunnel State	The state of the FRR TE tunnel: Not Configured, Ready, or Active.
Sending Alarms	Indicates whether or not the entity is sending alarms.

VRF Table Tab

The VRF Table tab describes the MPLS paths that terminate locally at a VRF. Table 17-11 describes the information that is displayed in the VRF Table tab.

Table 17-11 VRF Table Tab 

Field	Description
Incoming Label	The details of the incoming VRF label.
Action	The action that will be invoked: push, pop, swap, or untagged.
VRF	The VRF name as a hyperlink; displays the VRF properties.
IP Destination	The destination IP address.
Destination Mask	The destination IP subnet mask.
Next Hop	The next hop.
Out Interface	The out interface.
Sending Alarms	This option is unavailable.

LDP Neighbors Tab

The LDP Neighbors tab provides details of all MPLS interface peers that use the Label Distribution Protocol (LDP). LDP enables neighboring 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 for 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.

---

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

---

The following properties are displayed on the LDP Neighbors tab for each LDP peer:

Field	Description
LDP ID	The LDP identifier of the neighbor (peer) for the session.
Transport IP Address	The IP address advertised by the peer in the hello message or the hello source address.
Session State	The current state of the session, which can be one of the following: •Transient •Initialized •Open Rec •Open Sent •Operational
Protocol Type	The protocol used to establish the session, which may be LDP or TDP (Tag Distribution Protocol).
Label Distribution Method	The method of label distribution. This might be Downstream or Downstream On Demand.
Session Keepalive Interval	The negotiated number of seconds between keepalive messages.
Session Hold Time	The amount of time (in seconds) that an LDP session can be maintained with an LDP peer, without receiving LDP traffic or an LDP keepalive message from the peer.
Discovery Sources	An indication of whether the peer has one or more discovery sources. Note To see the discovery sources in the LDP Neighbor Properties window, double-click the row of the peer in the table.
Sending Alarms	This option is unavailable.

Double-clicking an entry (peer) in the table opens the LDP Neighbor Properties window that displays the basic and targeted discovery sources for the peer. Each peer can have several discovery sources. The following information is displayed:

•Interface Name—The interface on which LDP is configured.

•Source IP Address—The IP address of the peer that sends the targeted hello messages for extended discovery.

•Adjacency Type—The type of LDP adjacency used for discovery, which may be Link (basic) or Targeted (extended).

•Sending Alarms—This option is unavailable.

Viewing MP-BGP Information

The MP-BGP branch displays information about a router's BGP neighbors. Clicking the high-level MP-BGP category displays the MP-BGP peer running on the local router. Right-clicking MP-BGPs and choosing Properties displays the same property in the MPBGPs - FW Component Container Properties window.

Clicking a MP-BGP entity displays a list of the routers used in the MP-BGP network and includes the configuration and status of the links between the router displayed in the inventory and all other BGP members. Right-clicking the MP-BGP entity and choosing Properties displays the same properties in the MPBGP Properties window. The Autonomous System (AS) to which the router belongs is displayed. The BGP Neighbors table contains the following information:

Field	Description
Peer Remote Address	The BGP peer remote IP address used by the BGP peer to exchange routing information with the local BGP peer.
Peer ID	The IP address by which the BGP recognizes and converses with its neighbor.
VRF Name	The remote peer VRF name.
Peer Keep Alive	The time interval, in seconds, between successive keepalive messages. The keepalive time is negotiated with the neighbor after the link is established.
Peer State	The state of the link between the local and remote BGP peers. Valid values are Idle, Connect, Active, Open Set, Open Confirm, and Established.
BGP Neighbor Type	The BGP neighbor type, either client or nonclient. Route reflector advertising is based on the BGP neighbor type. To client peers, a route reflector advertises all routes learned from both client and nonclient peers. To nonclient peers, the route reflector advertises only the routes received from client peers.
Peer Hold Time	The BGP Hold Time value (in seconds) that is used when negotiating with peers. If the router does not receive successive keepalive, update, or notification messages within the period specified in the Hold Time field of the open message, the BGP link to the peer is closed.
Peer Remote AS	The the remote peer AS.
AFI	Address family identifier: IPv4, IPv6, VPNv4, or VPNv6.
AF Peer State	The address family peer state: Established (up), or Idle (down).
Distribute Through Interface	The local interface through which BGP information is distributed to BGP neighbors.
Sending Alarms	This option is unavailable.

Viewing BFD Properties

Bidirectional Forwarding Detection (BFD) is used to expedite detection of communication failures of other protocols, such as BGP and OSPF.

To view BFD properties that are configured on a device:

---

Step 1 In Cisco ANA NetworkVision, double-click the required device.

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

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

Figure 17-8 BFD Properties

Table 17-12 describes the information displayed for BFD.

Table 17-12 BFD Properties 

Field	Description
Process	The process name, such as Bidirectional Forwarding Detection.
Process State	The process state, such as Running.
BFD Sessions Table
Source IP	The source IP address of the session.
Destination IP	The destination IP address of the session.
State	The state of the session, such as Up or Down.
Interface	The interface used for BFD communications, hyperlinked to the routing entity in logical inventory.
Registered Protocols	The routing protocol being monitored for communication failures, such as BGP or OSPF.

---

Viewing a Port Configuration

In addition to viewing logical inventory information from the logical inventory branch, you can also view services provisioned on physical ports by clicking a physical port in the physical inventory branch. Information that is displayed includes:

•Physical layer information.

•Layer 2 information, such as ATM and Ethernet.

•The subinterfaces used by a VRF.

For detailed information on viewing physical inventory information, see Chapter 3, "Viewing Network Element Properties."

Figure 17-9 shows an example of port information (including the subinterfaces) displayed when a port is selected in the physical inventory branch of the inventory window.

Figure 17-9 Port Information in the Inventory Window

The subinterface is a logical interface defined in the device; all of its parameters can be part of its configuration. Table 17-13 describes the information that is displayed in the Subinterfaces table.

Table 17-13 Subinterfaces Table  

Field	Description
Address	The IP address defined in the subinterface.
Mask	The subnet mask.
VLAN Type	The type of VLAN, such as Bridge or IEEE 802.1Q. Double-click the entry to view the Port IP VLAN Properties window containing: •VLAN type •VLAN identifier •Operational status •A brief description of the VLAN
Operational State	The operational state of the subinterface.
VLAN ID	The VLAN identifier.
Inner VLAN	The CE-VLAN identifier.
IP Interface	A hyperlink that displays the VRF properties in the inventory window for the IP interface.
VRF Name	The name of the VRF.
Is MPLS	Whether this is an MPLS interface: True or False.
Sending Alarms	Whether the alarm for the required port has been enabled (true) or disabled (false).
Tunnel Edge	Whether this is a tunnel edge: enabled (true) or disabled (false).
Binding	A hyperlinked entry to the specific bridge in logical inventory.

Viewing Cross-VRF Routing Entries

The Cross-VRF routing entries display routing information learned from the BGP neighbors (BGP knowledge base). The cross-VRF routing entry parameters are displayed in the Cross-VRF Properties window. To display the cross-VRF routing entries, double-click an entry (row) in the Cross-VRFs tab of the MP BGP Properties area. The following information is displayed:

Field	Description
Destination	The destination of the specific network.
Mask	The mask of the specific network.
Next Hop	The PE address from which to continue to get to a specific address.
Out Going VRF	The VRF routing entry that points to the other VRF in the same PE. The outgoing VRF is the VRF that is pointed to by the Cross-VRF entry.
Out Tag	The MPLS label inserted in the MPLS label stack by this PE router to reach the destination address that is connected to the other VRF.
In Tag	The MPLS label used by this router to identify traffic arriving at the destination address, it was advertised by this PE router and is inserted in the MPLS label stack by the PE from which the traffic originated.
Sending Alarms	This option is unavailable.

Viewing Pseudowire End-to End Emulation Tunnels

The Pseudowires branch (Logical Inventory > Pseudowires) displays a list of the Layer 2 tunnel edge properties (per edge), including tunnel status and VC labels. Table 17-14 describes the information that is displayed in the Tunnel Edges table for pseudowires.

Table 17-14 Pseudowires Branch Tunnel Edges Table 

Field	Description
Local Interface	The 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.
ID	The tunnel identifier, hyperlinked to the PTP Layer 2 MPLS Tunnel Properties window.
Peer	The details of the selected LCP peer (edge peer), hyperlinked to the peer pseudowire tunnel in logical inventory.
Tunnel ID	The identifier that, along with the router IP addresses of the two tunnel edges, identifies the PWE3 tunnel.
Tunnel Status	The operational state of the tunnel: Up or Down.
Local Router IP	The IP address of this tunnel edge, which is used as the MPLS router ID.
Peer Router IP	The IP address of the peer tunnel edge, which is used as the MPLS router ID.
Pseudowire Type	Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN Basic, PPP, or SAToP. For a complete list of pseudowire types, see the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide.
Local MTU	The size, in bytes, of the MTU on the local interface.
Remote MTU	The size, in bytes, of the MTU on the remote interface.
Local VC Label	The MPLS label that is used by this router to identify or access the tunnel. It is inserted in the MPLS label stack by the local router.
Peer VC Label	The MPLS label that is used by this router to identify or access the tunnel. It is inserted in the MPLS label stack by the peer router.
Signaling Protocol	The protocol used by MPLS to build the tunnel, for example, LDP or TDP.
Preferred Path Tunnel	The path to be used for MPLS pseudowire traffic.

Viewing MPLS TE Tunnel Information

The Traffic Engineering Tunnels branch displays specific TE tunnel information. The name of the table is displayed at the top of the Properties window in the title bar. Table 17-15 describes the information that is displayed in the Tunnel Edges table.

Table 17-15 Tunnel Edges Table 

Field	Description
Name	The name of the TE tunnel (in Cisco devices it is the interface name).
Tunnel Destination	The IP address of the device in which the tunnel ends.
Administrative Status	The administrative state of the tunnel: Up or Down.
Operational Status	The operational state of the tunnel: Up or Down.
Outgoing Label	The TE tunnel's MPLS label distinguishing the LSP selection in the next device.
Description	A description of the tunnel.
Outgoing Interface	The interface through which the tunnel exits the device.
Bandwidth (Kbps)	Bandwidth specification for this tunnel in Kb/s.
Setup Priority	The tunnel's priority upon path setup.
Hold Priority	The tunnel priority after path setup.
Affinity	The tunnel's preferential bits for specific links.
Affinity Mask	The tunnel affinity bits that should be compared to the link attribute bits.
Auto Route	Whether or not destinations behind the tunnel are routed through the tunnel: Enabled or disabled.
Lockdown	Whether or not the tunnel can be rerouted: •Enabled—The tunnel cannot be rerouted. •Disabled—The tunnel can be rerouted.
Path Option	The tunnel path option: •Dynamic—The tunnel is routed along the ordinary routing decisions after taking into account the tunnel constraints such as attributes, priority, and bandwidth. •Explicit—The route is explicitly mapped with the included and excluded links.
Average Rate (Kbps)	Average bandwidth for this tunnel (in Kb/s).
Burst (Kbps)	Burst flow specification (in Kb/s) for this tunnel.
Peak Rate (Kbps)	Peak flow specification (in Kb/s) for this tunnel.
LSP ID	LSP identification number.
Policy Class	Value of Policy Based Tunnel Selection (PBTS) configured. This value ranges from 1-7.
FRR	The TE Fast Reroute (FRR) status: Enabled or Disabled.
Egress Traffic Descriptor	Name of the VC egress descriptor.
Sending Alarms	This option is unavailable.
Ingress Traffic Descriptor	Name of the VC ingress descriptor.

The Traffic Engineering LSPs Label Switching sub-branch displays the TE tunnel LSP information. Devices that have LSPs running TE tunnels (either as a head end, midpoint, or tail end), display the following information:

Field	Description
LSP Type	The type of LSP: •Head—A tunnel starting at this device. •Midpoint—A tunnel passing through this device. •Tail—A tunnel terminating at this device.
Source Address	IP address of the device where the tunnel begins, that is, the tunnel head.
In Interface and Label	Occupied only for midpoint or tail LSPs, this label is advertised to the previous device on this interface as the LSP's next label.
Out Interface and Label	Occupied only for head or midpoint LSPs, this label is appended to tunnel packets going out through this interface to the next hop along the tunnel's path.
Destination Address	The IP address of the device at the end of the tunnel.
LSP name	A name identifying the tunnel.
LSP ID	LSP identification number.
Average Bandwidth	Average bandwidth for this tunnel (in Kb/s).
Burst	Burst flow specification for this tunnel (in Kb/s).
Peak	Peak flow specification for this tunnel (in Kb/s).
Sending Alarms	This option is unavailable.