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
Applying VPN Overlays
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
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 Label Switched Entity Properties
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
•Monitoring MPLS Services
For more information about MPLS and Cisco ANA, see the Cisco Active Network Abstraction 3.7.2 Theory of Operations Guide.
User Roles Required to Work with MPLS Networks
This topic 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 elements), authorization is based on the default permission that is assigned to your user account.
•For element-based tasks (tasks that do affect elements), authorization is based on the default permission that is assigned to your account. That is, whether the element 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.2 Administrator Guide.
The following tables identify the tasks that you can perform:
•Table 17-1 identifies the tasks that you can perform if a selected element is not in one of your assigned scopes.
•Table 17-2 identifies the tasks that you can perform if a selected element is in one of your assigned scopes.
Users with the Administrator role have access to all managed elements.
Table 17-1 Default Permission/Security Level Required for Working with MPLS Networks - Element Not in User's Scope
Task
|
Viewer
|
Operator
|
OperatorPlus
|
Configurator
|
Administrator
|
VPNs and VRFs
|
Add tunnels to VPNs
|
—
|
X
|
X
|
X
|
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
|
X
|
X
|
X
|
X
|
Remove VPNs from a map
|
—
|
—
|
X
|
X
|
X
|
View VPN properties
|
X
|
X
|
X
|
X
|
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-BGP information
|
—
|
—
|
—
|
—
|
X
|
View MPLS TE tunnel information
|
—
|
—
|
—
|
—
|
X
|
View port configurations
|
—
|
—
|
—
|
—
|
X
|
View pseudowire end-to-end emulation tunnels
|
—
|
—
|
—
|
—
|
X
|
Table 17-2 Default Permission/Security Level Required for Working with MPLS Networks - Element in User's Scope
Task
|
Viewer
|
Operator
|
OperatorPlus
|
Configurator
|
Administrator
|
VPNs and VRFs
|
Add tunnels to VPNs
|
—
|
X
|
X
|
X
|
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
|
X
|
X
|
X
|
X
|
Remove VPNs from a map
|
—
|
—
|
X
|
X
|
X
|
View VPN properties
|
X
|
X
|
X
|
X
|
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
|
X
|
X
|
X
|
X
|
View the NDP table
|
X
|
X
|
X
|
X
|
X
|
View rate limit information
|
X
|
X
|
X
|
X
|
X
|
Other
|
View BFD properties
|
X
|
X
|
X
|
X
|
X
|
View cross-VRF routing entries
|
X
|
X
|
X
|
X
|
X
|
View LSE properties
|
X
|
X
|
X
|
X
|
X
|
View MP-BGP information
|
X
|
X
|
X
|
X
|
X
|
View MPLS TE tunnel information
|
X
|
X
|
X
|
X
|
X
|
View port configurations
|
X
|
X
|
X
|
X
|
X
|
View pseudowire end-to-end emulation tunnels
|
X
|
X
|
X
|
X
|
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
|
Sites
|
5
|
VPN in the map view
|
3
|
Virtual routers
|
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
|
Network elements
|
2
|
Virtual routers
|
3
|
Sites
|
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.
Table 17-3 shows the VPN icons in the Cisco ANA NetworkVision map view.
Table 17-3 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-4 shows the additional properties available for VPN entities.
Table 17-4 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-3).
•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 Cisco ANA 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 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 OK.
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 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, 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 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 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:
•Applying VPN Overlays
•Managing a VPN Overlay Display in the Map View
•Displaying VPN Callouts in a VPN Overlay
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 Cisco ANA NetworkVision, 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," 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 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 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).
Note The link must be displayed in the VPN overlay and not dimmed for you to display the link callouts.
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 topic 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.
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 topic 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.
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 one 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 topic 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.
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 topic 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.
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-3).
•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-5 shows the displayed icons.
Table 17-5 Hidden Device Icons
Icon
|
Description
|
|
Site with one or more hidden connected devices.
|
|
LCP with one or more 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 topic 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.
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-3.) 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 created manually.
•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 topic 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.
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.
Monitoring MPLS Services
The following topics provide details for viewing MPLS services and technologies:
•Viewing VPN Properties
•Viewing Site Properties
•Viewing VRF Properties
•Displaying VRF Egress and Ingress Adjacents
•Viewing Routing Entities
•Viewing Label Switched Entity Properties
•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.
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
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 the required site and choose Properties.
Step 2 Table 17-6 describes the information that is displayed in the Router IP Interface Properties window:
Table 17-6 Router IP Interface Properties Window for Sites
Field
|
Description
|
Name
|
Name of the site, such as FastEthernet4/1.252.
|
State
|
Interface state, either Up or Down.
|
IP Address
|
IP address of the interface.
|
Mask
|
Network mask.
|
Interface Description
|
Description applied to the interface.
|
Associated Entity
|
Element and interface associated with the site, hyperlinked to its entry in physical inventory.
|
Addresses Table
|
Subnet
|
IP address and 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.
|
Type
|
Address type, such as Primary, Secondary, or IPv6 Unicast.
|
Step 3 Click Close to close 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 Open the VRF Properties window in either of the following ways:
•Right-click a VRF in the Cisco ANA NetworkVision navigation pane or map view and choose Properties.
•Right-click the required virtual router in the Cisco ANA NetworkVision navigation pane or map view and select Open VRF Table.
The VRF Properties window is displayed as shown in 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. The forwarding table also contains MPLS encapsulation information.
Table 17-7 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-7.
Table 17-7 VRF Properties
Field
|
Description
|
Route Distinguisher
|
Route distinguisher configured in the VRF.
|
Name
|
VRF name.
|
Description
|
Description of the VRF.
|
IPv4 Tab
|
Export Route Targets
|
IPv4 export route targets contained by the VRF.
|
Import Route Targets
|
IPv4 import route targets contained by the VRF.
|
Route Maps
|
Route maps for the VRF.
|
IPv6 Tab
|
Export Route Targets
|
IPv6 export route targets contained by the VRF.
|
Import Route Targets
|
IPv6 import route targets contained by the VRF.
|
Route Maps
|
Route maps for the VRF.
|
Routing Tables
|
Destination
|
Destination of the specific network.
|
Prefix Length
|
Length of the network prefix in bits.
|
Next Hop
|
Next routing hop.
|
Outgoing Interface
|
Name of the outgoing interface; displayed if the Routing Protocol type is local.
|
Type
|
Route type: Direct (local), Indirect, or Static.
|
Routing Protocol
|
Routing protocol used to communicate with the other sites and VRFs: BGP or local.
|
BGP Next Hop
|
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
|
Innermost label that is expected when MPLS traffic is received.
|
Bottom Out Label
|
Innermost label sent with MPLS traffic.
|
Outer Label
|
Outermost or top label in the stack used for MPLS traffic.
|
Sites Tab
|
Name
|
Site name.
|
IP Address
|
IP address of the interface.
|
Mask
|
Subnet mask.
|
State
|
State of the subinterface: Up or Down.
|
Associated Entity
|
Element and interface associated with the site, hyperlinked to its entry in physical inventory.
|
Description
|
Interface description.
|
Input Access List
|
Access list applied to the inbound traffic.
|
Output Access List
|
Access list applied to the outbound traffic.
|
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
|
IP Security (IPsec) map name.
|
Site Name
|
Name of the business element to which the interface is attached.
|
Step 2 Press Ctrl + F4 to close the VRF Properties window.
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.
Table 17-8 describes the information displayed in the Adjacents window.
Table 17-8 VRF Adjacents Properties Window
Field
|
Description
|
Name
|
VRF name.
|
Route Distinguisher
|
Route distinguisher configured in the VRF.
|
VRF V6 Table
|
IPv6 rout distinguisher if IPv6 is configured.
|
Step 2 When finished, press Ctrl + F4 to close the Adjacents window.
Viewing Routing Entities
To view routing entities:
Step 1 Right-click the required device in Cisco ANA NetworkVision 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-6.
Figure 17-6 Routing Entity Table
Table 17-9 describes the information that is displayed in the Routing Entity table.
Table 17-9 Routing Entity Table
Field
|
Description
|
Name
|
Name of the routing entity.
|
IP Interfaces Tab
|
Name
|
Site name.
|
IP Address
|
IP address of the interface.
|
Mask
|
Network mask.
|
State
|
State of the subinterface: Up or Down.
|
Associated Entity
|
Interface associated with the routing entity, hyperlinked to its location in physical inventory.
|
Description
|
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
|
IP Security (IPsec) crypto map name.
|
Site Name
|
Name of the business element to which the interface is attached.
|
IPv4 and IPv6 Routing Table Tabs
|
Destination
|
Destination of the specific network.
|
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
|
IP 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
To view the ARP table:
Step 1 Right-click the required device in Cisco ANA NetworkVision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Routing Entities > Routing Entity > ARP.
Table 17-10 describes the information that is displayed in the ARP table.
Table 17-10 ARP Table
Field
|
Description
|
MAC
|
Interface MAC address.
|
Interface
|
Interface name.
|
IP Address
|
Interface IP address.
|
State
|
Interface state:
•Dynamic—The entry was learned by the device according to network traffic.
•Static—The entry was learned by a local interface or from a user configuring a static route.
•Other—The entry was learned by another method not explicitly defined.
•Invalid—In SNMP, this type is used to remove an ARP entry from the 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 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:
Step 1 Right-click the required device in Cisco ANA NetworkVision 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.
Table 17-11 describes the information displayed for NDP.
Table 17-11 NDP Table
Field
|
Description
|
MAC
|
Interface MAC address.
|
Interface
|
Interface name.
|
IP Address
|
Interface IPv6 address.
|
Type
|
Entry type:
•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.
|
Viewing Rate Limit Information
To view rate limit information:
Step 1 Right-click the required element in Cisco ANA NetworkVision 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 is relevant only for Cisco IOS devices.
The following information is displayed in the Rate Limits tab of the IP Interface Properties dialog box:
Table 17-12 Rate Limits Information
Field
|
Description
|
Type
|
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
|
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
|
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
|
Hyperlink that highlights the related access list in the Access List table.
|
Viewing Label Switched Entity Properties
The LSEs branch in logical inventory displays the following tabs for label switched entities:
•MPLS Interfaces Tab—Contains information on MPLS interfaces and whether traffic engineering tunnels are configured on an interface.
•Label Switching Table Tab—Describes the MPLS label switching entries used for traversing MPLS core networks.
•VRF Table Tab—Describes MPLS paths that terminate locally at a VRF.
•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.
•LDP Neighbors Tab—Details 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 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.
To view information for label switched entities:
Step 1 Right-click the required device in Cisco ANA NetworkVision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > LSEs > Label Switching.
Table 17-13 describes the information that is displayed for label switched entities.
Table 17-13 Label Switching Properties in Logical Inventory
Field
|
Description
|
Local LDP ID
|
Local Label Distribution Protocol (LDP) identifier.
|
LDP Process State
|
State of the LDP process, such as Running, Down, or Unknown.
|
MPLS Interfaces Tab
|
ID
|
Identifier for MPLS interface, as a combination of IP address and interface name.
|
Distribution Protocol Type
|
Distribution protocol used: Null, LDP, TDP (Tag Distribution Protocol), RSVP, or TDP and LDP.
|
MPLS TE Properties
|
Whether or not traffic engineering (TE) properties are configured on the interface:
•Checked—MPLS TE properties are configured on the interface.
•Unchecked—MPLS TE properties are not configured on the interface.
|
Discovery Protocols
|
Discovery protocols used on the interface.
|
Label Switching Table Tab
|
Incoming Label
|
Incoming MPLS label identifier.
|
Action
|
Type of switching action: Null, Pop, Swap, Aggregate, Untagged, or Act. 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
|
Outgoing label.
|
Out Interface
|
Name of the outgoing interface, displayed as a hyperlink to the port subinterface in physical inventory.
|
IP Destination
|
Destination IP address.
|
Destination Mask
|
Subnet mask of the destination.
|
Next Hop
|
IP address of the next hop in the path. The IP address is used for resolving the MAC address of the next MPLS interface that you want to reach.
|
VRF Table Tab
|
Incoming Label
|
Incoming VRF label identifier.
|
Action
|
Type of switching action: Null, Pop, Swap, Aggregate, Untagged, or Act.
|
VRF
|
VRF name, hyperlinked to its location in logical inventory.
|
IP Destination
|
Destination IP address.
|
Destination Mask
|
Subnet mask of the destination.
|
Next Hop
|
IP address of the next hop in the path. The IP address is used for resolving the MAC address of the next MPLS interface that you want to reach.
|
Out Interface
|
Name of the outgoing interface, displayed as a hyperlink to the port subinterface in physical inventory.
|
Traffic Engineering LSPs Tab
|
LSP Name
|
Label switched path (LSP) name.
|
LSP Type
|
Segment type: Head, Midpoint, or Tail.
|
Source Address
|
Source IP address.
|
Destination Address
|
Destination IP address.
|
In Label
|
Incoming label, if not a head segment.
|
In Interface
|
Incoming interface, if not a head segment.
|
Out Interface
|
Outgoing interface, if not a tail segment.
|
Out Label
|
Outgoing label, if not a tail segment.
|
Average Bandwidth (Kbps)
|
Current bandwidth (in Kb/s) used to automatically allocate the tunnel's bandwidth.
|
LSP ID
|
LSP identifier.
|
Burst (Kbps)
|
Tunnel bandwidth burst rate, in Kb/s.
|
Peak (Kbps)
|
Tunnel bandwidth peak rate, in Kb/s.
|
FRR TE Tunnel
|
Fast Reroute (FRR) TE tunnel name, hyperlinked to the routing entity in logical inventory.
|
FRR TE Tunnel State
|
State of the FRR TE tunnel:
•Active—A failure exists in the primary tunnel and the backup is in use.
•Not Configured—The primary tunnel has no designated backup tunnel.
•Ready—The primary tunnel is in working condition.
|
LDP Neighbors Tab
|
LDP ID
|
Identifier of the LDP peer.
|
Transport IP Address
|
IP address advertised by the peer in the hello message or the hello source address.
|
Session State
|
Current state of the session: Transient, Initialized, Open Rec, Open Sent, or Operational.
|
Protocol Type
|
Protocol used by the peer to establish the session: LDP, TDP, or Unknown.
|
Label Distribution Method
|
Method of label distribution: Downstream, Downstream On Demand, Downstream Unsolicited, or Unknown.
|
Session Keepalive Interval
|
Length of time (in milliseconds) between keepalive messages.
|
Session Hold Time
|
The amount of time (in milliseconds) 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
|
Whether the peer has one or more discovery sources:
•Checked—Has one or more discovery sources.
•Unchecked—Has no discovery sources.
Note To see the discovery sources in the LDP Neighbor Properties window, double-click the row of the peer in the table.
|
Step 3 Double-click an entry in any of the tables to view additional properties for that entry.
Table 17-14 Additional Properties Available from Label Switching in Logical Inventory
Double-click an entry in this tab...
|
To display this window...
|
MPLS Interfaces tab
|
MPLS Link Information - MPLS Properties
|
Label Switching Table tab
|
Label Switching Properties
|
VRF Table tab
|
MPLS Aggregate Entry Properties
|
Traffic Engineering LSPs tab
|
Tunnel Properties
|
LDP Neighbors tab
|
LDP Peer Properties
|
Viewing MP-BGP Information
The MP-BGP branch displays information about a router's BGP neighbors and cross-connect VRFs.
To view MP-BGP information:
Step 1 Right-click the required device in Cisco ANA NetworkVision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > MPBGPs > MPBGP.
Table 17-15 describes the information that is displayed for MP-BGP.
Table 17-15 MP-BGP Information in Logical Inventory
Field
|
Description
|
Local AS
|
Identifier of the autonomous system (AS) to which the router belongs.
|
BGP Identifier
|
BGP identifier, represented as an IP address.
|
Cross VRFs Tab
|
VRF Name
|
Name of the VRF.
|
Cross VRF Routing Entries
|
Group of cross VRFs that share a single destination.
|
BGP Neighbors Tab
|
Peer AS
|
Identifier of the AS to which the remote peer belongs.
|
Peer State
|
State of the remote peer: Active, Connect, Established, Open Confirm, Open Sent, or Null.
|
Peer Address
|
Remote peer IP address.
|
AFI
|
Address family identifier: IPv4, IPv6, L2VPN, VPNv4, or VPNv6.
|
AF Peer State
|
Address family peer state: Established or Idle.
|
Peer BGP ID
|
Identifier of the remote peer, represented as an IP address.
|
Local BGP ID
|
Local peer IP address.
|
VRF Name
|
Remote peer VRF name.
|
BGP Neighbor Type
|
Neighbor type: Null, Client, or Non Client.
|
Hold Time (secs)
|
Established hold time in seconds.
|
Keepalive (secs)
|
Established keepalive time in seconds.
|
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 an element:
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-7.
Figure 17-7 BFD Properties
Table 17-16 describes the information displayed for BFD.
Table 17-16 BFD Properties
Field
|
Description
|
Process
|
Process name, such as Bidirectional Forwarding Detection.
|
Process State
|
Process state, such as Running.
|
BFD Sessions Table
|
Source IP
|
Source IP address of the session.
|
Destination IP
|
Destination IP address of the session.
|
State
|
Session state, such as Up or Down.
|
Interface
|
Interface used for BFD communications, hyperlinked to the routing entity in logical inventory.
|
Registered Protocols
|
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 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.
•Subinterfaces used by a VRF.
For detailed information on viewing physical inventory information, see Chapter 3 "Viewing Network Element Properties."
To view a port's configuration:
Step 1 In Cisco ANA NetworkVision, double-click the required device.
Step 2 In the inventory window, choose Physical Inventory > Chassis > Slot > Subslot > Port.
Figure 17-8 shows an example of the information (including the subinterfaces) displayed when a port is selected in the physical inventory branch of the inventory window.
Figure 17-8 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-17 describes the information that can be displayed in the Subinterfaces table. Not all fields appear in all Subinterfaces tables.
Table 17-17 Subinterfaces Table
Field
|
Description
|
Address
|
IP address defined in the subinterface.
|
Mask
|
Subnet mask.
|
VLAN Type
|
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
|
Operational state of the subinterface.
|
VLAN ID
|
VLAN identifier.
|
Inner VLAN
|
CE-VLAN identifier.
|
IP Interface
|
IP interface, hyperlinked to the VRF properties in the inventory window.
|
VRF Name
|
Name of the VRF.
|
Is MPLS
|
Whether this is an MPLS interface: True or False.
|
VC
|
Virtual connection (VC) configured on the interface, hyperlinked to the VC Table window.
For more information about VC properties, see Viewing ATM Virtual Connection Cross-Connects.
|
Tunnel Edge
|
Hyperlinked entry to the specific tunnel edge in logical inventory.
|
Binding
|
Hyperlinked entry to the specific bridge or pseudowire in logical inventory.
|
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 Cisco ANA NetworkVision 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-18.
Table 17-18 Cross-VRF Properties Window
Field
|
Description
|
Name
|
Cross-VRF name.
|
Cross VRF Routing Entries Table
|
Destination
|
IP address of the destination network.
|
Prefix
|
Length of the network prefix in bits.
|
Next Hop
|
IP address of the next hop in the path.
|
Out Going VRF
|
Outgoing VRF identifier, hyperlinked to its entry in logical inventory.
|
Out Tag
|
Outgoing virtual router tag, such as 50 or no tag.
|
In Tag
|
Incoming virtual router tag, such as 97 or no tag.
|
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 Cisco ANA NetworkVision 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-19.
Table 17-19 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.
|
|
|
ID
|
Tunnel identifier, hyperlinked to the PTP Layer 2 MPLS Tunnel Properties window.
|
Peer
|
Details of the selected LCP peer (edge peer), hyperlinked to the peer pseudowire tunnel in logical inventory.
|
Tunnel ID
|
Identifier that, along with the router IP addresses of the two tunnel edges, identifies the PWE3 tunnel.
|
Tunnel Status
|
Operational state of the tunnel: Up or Down.
|
Local Router IP
|
IP address of this tunnel edge, which is used as the MPLS router ID.
|
Peer Router IP
|
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.2 Theory of Operations Guide.
|
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.
|
Preferred Path Tunnel
|
Path to be used for MPLS pseudowire traffic.
|
Viewing MPLS TE Tunnel Information
The Traffic Engineering Tunnels branch displays specific TE tunnel information.
To view MPLS TE tunnel information:
Step 1 Right-click the required device in Cisco ANA NetworkVision and choose Inventory.
Step 2 In the logical inventory window, choose Logical Inventory > Traffic Engineering Tunnels.
Table 17-20 describes the information that is displayed in the Tunnel Edges table.
Table 17-20 Tunnel Edges Table
Field
|
Description
|
Name
|
Name of the TE tunnel; for Cisco devices it is the interface name.
|
Tunnel Destination
|
IP address of the device in which the tunnel ends.
|
Administrative Status
|
Administrative state of the tunnel: Up or Down.
|
Operational Status
|
Operational state of the tunnel: Up or Down.
|
Outgoing Label
|
TE tunnel's MPLS label distinguishing the LSP selection in the next device.
|
Description
|
Description of the tunnel.
|
Outgoing Interface
|
Interface through which the tunnel exits the device.
|
Bandwidth (KBps)
|
Bandwidth specification for this tunnel in Kb/s.
|
Setup Priority
|
Tunnel priority upon path setup.
|
Hold Priority
|
Tunnel priority after path setup.
|
Affinity
|
Tunnel preferential bits for specific links.
|
Affinity Mask
|
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
|
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 identifier.
|
Policy Class
|
Value of Policy Based Tunnel Selection (PBTS) configured. Values range from 1-7.
|
FRR
|
TE Fast Reroute (FRR) status: Enabled or Disabled.
|
Egress Traffic Descriptor
|
Name of the VC egress descriptor.
|
Ingress Traffic Descriptor
|
Name of the VC ingress descriptor.
|
The Traffic Engineering LSPs tab in the LSEs branch in logical inventory displays TE tunnel LSP information.
Step 3 For details about the information displayed for TE tunnel LSPs, see Traffic Engineering LSPs Tab.
Feedback
