Table Of Contents

Monitoring Carrier Ethernet Services

User Roles Required to Work with Carrier Ethernet Services

Viewing CDP Properties

Viewing Link Layer Discovery Protocol Properties

Viewing Spanning Tree Properties

Viewing Resilient Ethernet Protocol Properties

Working with Ethernet Link Aggregation Groups

Viewing Ethernet LAG Properties

Viewing Provider Backbone Bridge Properties

Viewing EFP Properties

Understanding EFP Severity and Ticket Badges

Viewing EVC Service Properties

Viewing Virtual Switching Instance Properties

Viewing VPLS Core or Access Pseudowire Endpoint Properties

Viewing VPLS Access Ethernet Flow Point Properties

Viewing and Renaming Ethernet Flow Domains

Working with VLANs and VLAN Overlays

VLAN and EFD Discovery

VLAN Elements

Switching Entities Containing Termination Points

Adding VLANs to a Map

Removing VLANs from a Map

Viewing VLAN Mappings

Working with Associated VLANs

Adding an Associated VLAN

Viewing Associated Network VLAN Service Links and VLAN Mapping Properties

Viewing VLAN Links Between VLAN Elements and Devices

Adding a VLAN Overlay to a Map View

Displaying or Hiding VLAN Overlays

Removing a VLAN Overlay

Viewing VLAN Service Link Properties

Viewing REP Information in VLAN Domain Views and VLAN Overlays

Viewing REP Properties for VLAN Service Links

Viewing STP Information in VLAN Domain Views and VLAN Overlays

Viewing STP Properties for VLAN Service Links

Viewing VLAN Trunk Group Properties

Viewing VLAN Bridge Properties

Understanding Unassociated Bridges

Adding Unassociated Bridges

Working with Ethernet Flow Point Cross-Connects

Adding EFP Cross-Connects

Viewing EFP Cross-Connect Properties

Working with VPLS and H-VPLS Instances

Adding VPLS Instances to a Map

Using VPLS Instance Overlays

Viewing Pseudowire Tunnel Links in VPLS Overlays

Viewing VPLS-Related Properties

Viewing VPLS Instance Properties

Working with Pseudowires and Pseudowire Overlays

Adding Pseudowires to a Map

Pinging a Pseudowire

Displaying Pseudowire Information

Applying Pseudowire Overlays

Viewing Pseudowire Properties

Working with Ethernet Services

Adding Ethernet Services to a Map

Using Ethernet Service Overlays

Viewing Ethernet Service Properties

Viewing IP SLA Responder Service Properties

Viewing IS-IS Properties

Viewing OSPF Properties

Monitoring Carrier Ethernet Services

---

The following topics describe how you can use Cisco ANA to monitor Carrier Ethernet services:

•User Roles Required to Work with Carrier Ethernet Services

•Viewing CDP Properties

•Viewing Link Layer Discovery Protocol Properties

•Viewing Spanning Tree Properties

•Viewing Resilient Ethernet Protocol Properties

•Working with Ethernet Link Aggregation Groups

•Viewing Provider Backbone Bridge Properties

•Viewing EFP Properties

•Understanding EFP Severity and Ticket Badges

•Viewing EVC Service Properties

•Viewing Virtual Switching Instance Properties

•Viewing and Renaming Ethernet Flow Domains

•Working with VLANs and VLAN Overlays

•Understanding Unassociated Bridges

•Working with Ethernet Flow Point Cross-Connects

•Working with VPLS and H-VPLS Instances

•Working with Pseudowires and Pseudowire Overlays

•Working with Ethernet Services

•Viewing IP SLA Responder Service Properties

•Viewing IS-IS Properties

•Viewing OSPF Properties

User Roles Required to Work with Carrier Ethernet Services

Table 12-1 identifies the roles that are required to work with to Carrier Ethernet services in Cisco ANA NetworkVision. 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 12-1 Default Permission/Security Level Required for Working with Carrier Ethernet Services  

Task	Viewer	Operator	OperatorPlus	Configurator	Administrator
Bridges and Bridge Domains
Add unassociated bridges	—	—	X	X	X
EFP Cross-Connects
Add EFP cross-connects	—	—	X	X	X
View EFP cross-connect properties	Partial1	Partial1	Partial1	Partial1	X
Ethernet Flow Domains
Rename Ethernet flow domains	X	X	X	X	X
View EFD properties	—	—	—	—	X
View EFP properties	—	—	—	—	X
View Ethernet flow domains	X	X	X	X	X
View Ethernet LAG properties	—	—	—	—	X
View LAG link discovery information	—	—	—	—	X
Ethernet Services
Add Ethernet services to a map	—	—	X	X	X
Add Ethernet service overlays	X	X	X	X	X
View Ethernet service properties	X	X	X	X	X
Pseudowires and Pseudowire Overlays
Add pseudowires to a map	—	—	X	X	X
Apply pseudowire overlays	X	X	X	X	X
View EVC service properties	—	—	—	—	X
View pseudowire properties	Partial2	Partial2	Partial2	Partial2	X
Resilient Ethernet Protocol (REP)
View REP information in VLAN domain views and VLAN overlays	—	—	—	—	X
View REP properties	—	—	—	—	X
View REP properties for VLAN service links	—	—	—	—	X
Spanning Tree Protocol (STP)
View STP information in VLAN domain views and VLAN overlays	—	—	—	—	X
View STP properties	—	—	—	—	X
View STP properties for VLAN service links	—	—	—	—	X
VLANs
Add VLANs to a map	—	—	X	X	X
Remove VLANs from a map	—	—	X	X	X
View associated VLAN network VLAN service links and VLAN mapping properties	—	—	—	—	X
View VLAN bridge properties	—	—	—	—	X
View VLAN mappings	—	—	—	—	X
View VLAN trunk group properties	—	—	—	—	X
VLAN Overlays
Add VLAN overlays to a map	X	X	X	X	X
Display or hide VLAN overlays	X	X	X	X	X
Remove VLAN overlays	X	X	X	X	X
VPLS / H-VPLS
Add VPLS instances to a map	—	—	X	X	X
Use VPLS instance overlays	X	X	X	X	X
View VPLS access EFP properties	—	—	—	—	X
View VPLS core or access pseudowire endpoint properties	—	—	—	—	X
View VPLS instance properties	X	X	X	X	X
View VSI properties	—	—	—	—	X
Other Tasks
View CDP properties	—	—	—	—	X
View IP SLA responder service properties	—	—	—	—	X
View IS-IS properties	—	—	—	—	X
View Link Layer Discovery Protocol (LLDP) properties	—	—	—	—	X
View OSPF properties	—	—	—	—	X
View Provider Backbone Bridge (PBB) properties	—	—	—	—	X

1 The user with this role can view EFP cross-connect properties, but not local switching properties configured on an element unless the element is in the user's scope. 2 The user with this role can view properties for individual pseudowires added to a map, but not for pseudowire endpoint properties configured on an element unless the element is in the user's scope.

Viewing CDP Properties

Cisco Discovery Protocol (CDP) is primarily used to obtain protocol addresses of neighboring devices and discover the platform of those devices.

To view CDP properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the device whose CDP properties you want to view.

Step 2 In the inventory window, click Logical Inventory > Cisco Discovery Protocol.

The CDP properties are displayed in logical inventory as shown in Figure 12-1.

Figure 12-1 CDP in Logical Inventory

Table 12-2 describes the CDP instance properties that are displayed.

Table 12-2 CDP Properties in Logical Inventory 

Field	Description
Process	Process name; in this case, Cisco Discovery Protocol
Process Status	Process status: Running or Disabled.
CDP Holdtime	Specifies the amount of time a receiving device should hold the information sent by a device before discarding it.
CDP Message Interval	Interval between CDP advertisement transmissions.
CDP Local Device ID	Local device identifier.
CDP Version	CDP version: 1 or 2.
CDP Neighbors Table
Local Port	Local port name.
Local Port ID	Local port identifier.
Remote Device ID	Remote device identifier.
Remote Port ID	Remote port identifier.
Remote IP Address	Remote IP address.

Step 3 When finished, press Ctrl + F4 to close each CDP properties window.

---

Viewing Link Layer Discovery Protocol Properties

LLDP stores and maintains the local device information, including a list of devices directly connected to the device.

In Logical Inventory

To view LLDP properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the device with the LLDP information you want to view.

Step 2 In the inventory window, choose Logical Inventory > Link Layer Discovery Protocol.

The LLDP properties are displayed in logical inventory as shown in Figure 12-2.

Figure 12-2 LLLD in Logical Inventory

Table 12-3 describes the properties that are displayed for LLDP.

Table 12-3 Link Layer Discovery Protocol Properties 

Field	Description
Process	Process; in this case, Link Layer Discovery Protocol
Process Status	Process status: Running or Disabled.
LLDP Hold Time	LLDP advertised hold time in seconds.
LLDP Reinitialization Delay	LLDP interface reinitialization delay in seconds
LLDP Advertisements Interval	LLDP advertisements interval in seconds.
Local System Name	Local system name.
Local Chassis ID	Local chassis identifier.
LLDP Neighbors Table
Local Port	Local port.
Local Port ID	Local port identifier.
Local Port Name	Local port name.
Remote System Name	Remote system name.
Remote Chassis ID	Remote chassis identifier.
Remote Port ID	Remote port identifier.
Remote Port Name	Remote port name.
Remote Management IP	Remote management IP address.

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

---

In Physical Inventory

To view LLDP on a Layer 2 port:

---

Step 1 In Cisco ANA NetworkVision, double-click the device with the Layer 2 port with LLDP information you want to view.

Step 2 In the inventory window, select the required port under Physical Inventory.

The LLDP information is displayed in the Discovery Protocols area in the Cisco ANA NetworkVision content pane:

•Discovery Protocol Type—LLDP

•Info—Tx (Enabled or Disabled), Rx (Enabled or Disabled).

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

---

Viewing Spanning Tree Properties

STP is a link management protocol that provides path redundancy while preventing undesirable loops in the network.

To view Spanning Tree properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the element whose STP properties you want to view.

Step 2 In the inventory window, choose Logical Inventory > Spanning Tree Protocol Service.

Step 3 STP properties are displayed in logical inventory as shown in Figure 12-3.

Figure 12-3 STP in Logical Inventory

Table 12-4 describes the properties that are displayed for STP.

Table 12-4 STP Properties 

Field	Description
Process	Process; in this case, Spanning Tree Protocol.
Process Status	Process status: Running or Disabled.
Bridge Hello Time	Hello message keepalive interval (in hundredths of seconds) when the port is the root.
Hello Time	Current hello time (in hundredths of seconds).
Bridge Forward Delay	When the port is the root and in listening or learning state, amount of time to wait (in hundredths of seconds) before proceeding to the forwarding state.
Forward Delay	Current bridge forward delay (in hundredths of seconds).
Bridge Max Age	When the port is the root, maximum age of learned Spanning Tree Protocol port information (in hundredths of seconds).
Max Age	Current maximum age (in hundredths of seconds).
STP Protocol	STP version: RSTP, PVSTP, MSTP, or RPVST.
UplinkFast	PVSTP Uplink Fast function status: Up or Down.
BackboneFast	PVSTP BackboneFast function status: Up or Down.
STP Instance Info Table
STP Instance ID	STP instance name.
VLAN Id	VLAN identifier.
Bridge Priority	Bridge priority.
STP Root Port	Hyperlinked entry to the STP port in physical inventory.
Root Cost	Root cost value for this bridge.
Designated Root	MAC address of the designated root.
Bridge ID	Bridge identifier (MAC address).
Bridge Hello Time	Hello message keepalive interval (in hundredths of seconds) when the port is the root.
Hello Time	Current hello time (in hundredths of seconds).
Bridge Forward Delay	When the port is the root and in the listening or learning state, amount of time to wait (in hundredths of seconds) before proceeding to the forwarding state.
Forward Delay	Current bridge forward delay (in hundredths of seconds).
Bridge Max Age	When the port is the root, maximum age of learned Spanning Tree Protocol port information (in hundredths of seconds).
Max Age	Current maximum age (in hundredths of seconds).
Sending Alarms	Whether or not the STP instance is sending alarms.

Step 4 To view the properties of an STP instance, double-click it.

Table 12-5 describes the information that is displayed in the STP Instance Information Properties window.

Table 12-5 STP Instance Information Properties 

Field	Description
STP Instance ID	STP instance identifier.
VLAN ID	VLAN identifier.
Bridge Priority	Bridge priority.
Bridge ID	Bridge identifier (MAC address).
Root Cost	Root cost value for this bridge.
Designated Root	MAC address of the designated root.
Bridge Hello Time	Hello message keepalive interval (in hundredths of seconds) when the port is the root.
Hello Time	Current hello time (in hundredths of seconds).
Bridge Forward Delay	When the port is the root and in listening or learning state, amount of time to wait (in hundredths of seconds) before proceeding to the forwarding state.
Forward Delay	Current bridge forward delay (in hundredths of seconds).
Bridge Max Age	When the port is the root, the maximum age of learned Spanning Tree Protocol port information (in hundredths of seconds).
Max Age	Current maximum age (in hundredths of seconds).
STP Protocol Specification	STP version, such as PVSTP or RSTP.
Is Root	Whether or not the port is the root: True or False.
Ports Info Table
STP Port	Hyperlinked entry to the STP port in physical inventory.
Port State	STP port state: Disabled, Blocking, Listening, Learning, or Forwarding,
Port Role	Port role: Unknown, Backup, Alternative, Designated, Root, or Boundary.
Port Priority	Default 802.1p priority assigned to untagged packets arriving at the port.
Port Path Cost	Port path cost, which represents the media speed for this port.
Point To Point Port	Whether or not the port is linked to a point-to-point link: True or False.
Edge Port	Whether or not the port is an edge port; that is, whether it is connected to a nonbridging device: True or False.
Port Identifier	STP port identifier.
Portfast	STP PortFast status: Up or Down.
Designated Port Identifier	Designated STP port identifier.
Designated Bridge	STP designated bridge.
BPDU Filter	BPDU Filter status: Up or Down.
BPDU Guard	BPDU Guard status: Up or Down.
Sending Alarms	Whether or not the port is configured for sending alarms: True or False.

Step 5 When finished, press Ctrl + F4 to close each STP properties window.

---

The following topics describe how to view STP properties related to:

•VLAN domain views and overlays—See Viewing STP Information in VLAN Domain Views and VLAN Overlays.

•VLAN service link properties—See Viewing STP Properties for VLAN Service Links.

Viewing Resilient Ethernet Protocol Properties

Cisco Resilient Ethernet Protocol (REP) technology is implemented on Cisco Carrier Ethernet switches and intelligent service edge routers. REP is a segment protocol, and a REP segment is a chain of ports connected to each other and configured with the same segment identifier. Each end of a segment terminates on an edge switch. The port where the segment terminates is called the edge port.

To view REP properties in logical inventory:

---

Step 1 In Cisco ANA NetworkVision, double-click the device configured for REP.

Step 2 In the inventory window, choose Logical Inventory > Resilient Ethernet Protocol.

Figure 12-4 shows an example of REP in logical inventory.

Figure 12-4 REP in Logical Inventory

Table 12-6 describes the information that is displayed for REP.

Table 12-6 REP Properties 

Field	Description
Process	Process name; in this case, Resilient Ethernet Protocol.
Process Status	State of the REP process, such as Running or Down.
Administrative VLAN	Administrative VLAN used by REP to transmit its hardware flooding layer messages. Values range from 1 to 4094.
Notification Enabled	Whether or not notification is enabled: True or False.
REP Version	Version of REP being used.
REP Segments Table
Segment ID	Segment identifier.
Segment Complete	Indicates whether the segment is complete; that is, that no port in the segment is in a failed state: True or False.
Segment Ports	This column is empty.
Sending Alarms	Whether or not the segment is configured for sending alarms: True or False.

Step 3 To view REP segment properties, double-click the required entry in the REP Segments table.

Figure 12-5 shows an example of REP segment properties in logical inventory.

Figure 12-5 REP Segment Properties

Table 12-7 describes the information that is displayed for REP segments.

Table 12-7 REP Segment Properties 

Field	Description
Segment ID	Segment identifier.
Segment Complete	Indicates whether the segment is complete; that is, that no port in the segment is in a failed state: True or False.
Segment Ports Table
Port	Hyperlinked entry to the port in physical inventory.
Port State	Current operational link state of the REP port: None, Init Down, No Neighbor, One Way, Two Way, Flapping, Wait, or Unknown.
Port Type	Port type: Primary Edge, Secondary Edge, or Intermediate.
Port Role	Role or state of the REP port depending on its link status and whether it is forwarding or blocking traffic: Failed, Alternate, or Open.
Remote Device Name	Name of the neighbor device that this port is connected to on this segment. This value can be null.
Remote Port Name	Name of the neighbor port on the neighbor bridge that this port is connected to on this segment. This value can be null.
Blocked VLANs	List of VLANs configured to be blocked at this port. This value is effective only on ports with a type of Alternate.
Preemptive Timer	Amount of time, in seconds, that REP waits before triggering preemption after the segment is complete. The entry can range from 0 to 300, or be Disabled. The value Disabled indicates that no time delay is configured, and that the preemption occurs manually. This property applies only to REP primary edge ports.
LSL Ageout Timer	Using the Link Status Layer (LSL) age-out timer, the amount of time, in milliseconds, that the REP interface remains up without receiving a hello from a neighbor.
Remote Device MAC	MAC address of the neighbor bridge that this port is connected to on this segment. This value can be null.

Step 4 When finished, press Ctrl + F4 to close each window.

---

The following topics describe how to view REP properties related to VLANs:

•VLAN domain views and overlays—See Viewing REP Information in VLAN Domain Views and VLAN Overlays.

•VLAN service link properties—See Viewing REP Properties for VLAN Service Links.

Working with Ethernet Link Aggregation Groups

Ethernet link aggregation groups (LAGs) provide the ability to treat multiple switch ports as one switch port. The port groups act as a single logical port for high-bandwidth connections between two network elements. A single link aggregation group balances the traffic load across the links in the channel.

Beginning with Cisco ANA 3.7.1:

•LAG links are discovered automatically for devices that support LAG technology and use VNEs that model Link Aggregation Control Protocol (LACP) attributes.

•You can create static links between Ethernet LAGs by choosing a LAG and the desired port channel for the A or Z side as described in Adding Static Links, page 5-12.

If a physical link within the link aggregation group fails, the following actions occur:

•Traffic that was previously carried over the failed link is moved to the remaining links.

Most protocols operate over single ports or aggregated switch ports and do not recognize the physical ports within the port group.

•An aggregation service alarm is generated.

The aggregation service alarm indicates the percentage of links within the aggregation that have failed. For example, if an Ethernet link aggregation group contains four Ethernet links and one fails, the aggregation service alarm indicates that 25% of the links are down.

---

Viewing Ethernet LAG Properties

To view properties for Ethernet link aggregation groups:

---

Step 1 In Cisco ANA NetworkVision, double-click the device with the link aggregation group you want to view.

Step 2 In the inventory window, choose Logical Inventory > Ethernet Link Aggregation.

The link aggregation properties are displayed as shown in Figure 12-6.

Figure 12-6 Ethernet Link Aggregation in Logical Inventory

Table 12-8 describes the aggregation group properties that are displayed in the Data Link Aggregations table.

Table 12-8 Data Link Aggregations Table 

Field	Description
ID	Aggregation identifier. Double-click the entry to view the properties for that aggregation.
Type	Aggregation group type: Ethernet Channel or IEEE 8023 AD LAG.
Group Number	Aggregation group number.
Bandwidth	Aggregation bandwidth.
Aggregation Control Protocol	Aggregation control protocol: Manual, Link Aggregation Control Protocol (LACP), or Port Aggregation Protocol (PagP).
Status	Aggregation status: Up or Down.
MAC Address	Aggregation MAC address.

Step 3 To view properties for a specific aggregation, double-click the group identifier.

The information that is displayed depends on the type of aggregation:

•For Ethernet Channel aggregations, see Table 12-9.

•For IEEE 802.3 AD aggregations, see Table 12-10.

Table 12-9 LAG Ethernet Channel Properties 

Field	Description
Group Number	Aggregation group number.
Bandwidth	Aggregation bandwidth in b/s.
Control Protocol	Aggregation control protocol: Manual, Link Aggregation Control Protocol (LACP), or Port Aggregation Protocol (PagP).
MAC Address	Aggregation MAC address.
Administrative State	Aggregation administrative status: Up or Down.
Operational State	Aggregation operational status: Up or Down.
Adjacent	Adjacent group, hyperlinked to the group in logical inventory.
Aggregated Ports Table
ID	Aggregated port identifier, hyperlinked to the interface in physical inventory.
Type	Aggregation type, such as Layer 2 VLAN.
Mode	VLAN mode, such as Trunk.
Native VLAN ID	VLAN identifier (VID) associated with this VLAN. The range of VLANs is 1 to 4067.
VLAN Encapsulation Type	Type of encapsulation configured on the VLAN, such as IEEE 802.1Q.
Allowed VLANs	List of VLANs allowed on this interface.
VLAN Encapsulation Admin Type	VLAN administration encapsulation type, such as IEEE 802.1Q.
Subinterfaces Table
Address	IP address of the subinterface.
Mask	Subnet mask applied to the IP address.
VLAN Type	Type of VLAN, such as Bridge or IEEE 802.1Q.
Operational State	Operational state of the subinterface: Up or Down.
VLAN ID	VLAN identifier.
Inner VLAN	CE-VLAN identifier.
IP Interface	IP interface configured as part of the subinterface, hyperlinked to the routing entity or VRF in logical inventory.
VRF Name	VRF associated with the subinterface.
Is MPLS	Whether the subinterface is enabled for MPLS: True or False. This column is displayed when at least one interface is MPLS-enabled.
Sending Alarms	Whether the interface is configured for alarms: True or False.
Tunnel Edge	Whether this is a tunnel edge: True or False.
VC	Virtual circuit identifier, hyperlinked to the VC Table when the subinterface is configured for ATM VC.
Binding	Hyperlinked entry to the specific bridge in logical inventory.
EFPs Table
EFP ID	EFP identifier.
Operational State	EFP operational state: Up or Down.
VLAN	VLAN associated with this EFP.
Inner VLAN	CE-VLAN identifier.
Translated VLAN	Translated, or mapped, VLAN identifier.
Translated Inner VLAN	Translated, or mapped, inner VLAN identifier.
Binding	Hyperlinked entry to the specific bridge in logical inventory.
Description	Description for the EFP.

Table 12-10 LAG IEEE 802.3 AD Properties 

Field	Description
Group Number	Aggregation group number.
Bandwidth	Aggregation bandwidth.
Control Protocol	Aggregation control protocol: Manual, Link Aggregation Control Protocol (LACP), or Port Aggregation Protocol (PagP).
MAC Address	Aggregation MAC address.
Administrative State	Aggregation administrative status: Up or Down.
Operational State	Aggregation operational status: Up or Down.
Dot3ad Agg Partner System Priority	Priority of the partner system.
Dot3ad Agg MAC Address	Aggregation MAC address.
Dot3ad Agg Actor Admin Key	Actor administrative key.
Dot3ad Agg Actor System Priority	Actor system priority.
Dot3ad Agg Partner Oper Key	Partner operational key.
Dot3ad Agg Actor Oper Key	Actor operational key.
Dot3ad Agg Collector Max Delay	Maximum delay (in microseconds) for either delivering or discarding a received frame by the frame collector.
Dot3ad Agg Actor System ID	Actor system identifier, in the form of a MAC address.
Dot3ad Agg Partner System ID	Partner system identifier, in the form of a MAC address.
Aggregated Ports Table
ID	Port identifier, hyperlinked to the interface in physical inventory.
Type	Type of VLAN, such as Layer 2 VLAN.
Sending Alarms	Whether or not the interface is configured for sending alarms: True or False.
Discovery Protocols	Discovery protocols used on this port.
Subinterfaces Table
Address	IP address of the subinterface.
Mask	Subnet mask applied to the IP address.
VLAN Type	Type of VLAN, such as Bridge or IEEE 802.1Q.
Operational State	Operational state of the subinterface: Up or Down.
VLAN ID	VLAN identifier.
Inner VLAN	CE-VLAN identifier.
IP Interface	IP interface configured as part of the subinterface, hyperlinked to the routing entity or VRF in logical inventory.
VRF Name	VRF associated with the subinterface.
VC	Virtual circuit identifier, hyperlinked to the VC Table when the subinterface is configured for ATM VC.
Binding	Hyperlinked entry to the specific bridge in logical inventory.
EFPs Table
EFP ID	EFP identifier.
Operational State	EFP operational state: Up or Down.
VLAN	VLAN associated with this EFP.
Inner VLAN	CE-VLAN identifier.
Translated VLAN	Translated, or mapped, VLAN identifier.
Translated Inner VLAN	Translated, or mapped, inner VLAN identifier.
Binding	Hyperlinked entry to the specific bridge in logical inventory.
Description	Description for the EFP.
LACP Port Entries
Dot3ad Agg Port Partner Admin Key	Administrative key for the partner port.
Dot3ad Agg Port Partner Admin Port Priority	Administrative port priority for the partner.
Dot3ad Agg Port Partner Oper Port Priority	Priority assigned to the aggregation port by the partner.
Dot3ad Agg Port Actor Admin State	Local administrative state as transmitted by the local system in LACP data units (LACPDUs).
Dot3ad Agg Port Actor Oper State	Local operational state for the port.
Dot3ad Agg Port Partner Oper Key	Operational key for the partner port.
Dot3ad Agg Port Selected Agg ID	Selected identifier for the aggregation port.
Dot3ad Agg Port Partner Admin State	Partner administrative state.
Dot3ad Agg Port Actor Port Priority	Priority assigned to the local aggregation port.
Dot3ad Agg Port Attached Agg ID	Identifier of the aggregator that the port is attached to.
Dot3ad Agg Port Partner Oper State	Partner administrative state as transmitted by the partner in the most recently transmitted LAPCDU.
Dot3ad Agg Port Actor Admin Key	Administrative key for the local port.
Dot3ad Agg Port Actor Port	Number assigned to the local aggregation port.
Dot3ad Agg Port Partner Oper Port	Number assigned to the aggregation port by the partner.
Dot3ad Agg Port Actor Oper Key	Operational for the local port.
Dot3ad Agg Port Partner Admin Port	Administrative value of the port for the partner.

Step 4 When finished, press Ctrl + F4 to close each open window.

---

Viewing Provider Backbone Bridge Properties

Provider backbone bridges (PBBs), specified by IEEE 802.1ah-2008, provide a way to increase the number of service provider supported Layer 2 service instances beyond the number supported by QinQ and VPLS. PBB adds a backbone VLAN tag and backbone destination and source MAC addresses to encapsulate customer Ethernet frames and create a MAC tunnel across core switches.

Cisco ANA supports PBB inventory discovery and modeling for the following devices:

•Cisco 7600-series devices running Cisco IOS version 12.2(33)SRE1

•Cisco ASR 9000-series devices running Cisco IOS XR version 3.9.1

Cisco ANA models the IB type of Backbone edge bridges which includes both I-type and B-type components.

To view PBB properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the element configured for PBB.

Step 2 In the inventory window, choose Logical Inventory > BridgeILans > PBB-bridge.

Figure 12-7 shows an example of PBB properties in logical inventory.

Figure 12-7 PBB Properties in Logical Inventory

Table 12-11 describes the information displayed for PBB.

Table 12-11 PBB Properties in Logical Inventory 

Field	Description
Name	Identifier of the bridge as follows: •For Cisco 7600 devices, the identifier of the MAC tunnel created. •For Cisco ASR 9000-series devices, the identifier is a combination of the bridge group and the bridge domain on the B-Bridge component.
IB Bridge Mapping Table
ISID	24-bit entry representing the Backbone service instance.
I-Bridge	XID of the I-Bridge component, hyperlinked to the relevant bridge in logical inventory.
B-Bridge	XID of the B-Bridge component, hyperlinked to the relevant bridge in logical inventory.

---

Viewing EFP Properties

Cisco ANA provides information about EFPs in a number of ways. For example:

•EFP names displayed in Cisco ANA NetworkVision maps add EFP and the managed element name to the interface name, such as GigabitEthernet4/0/1 EFP: 123@c4-npe5-67.

•If you select an EFP in the navigation pane in Cisco ANA NetworkVision and then click Show List View, an Ethernet Flow Points table lists the network element, port, and network VLAN associated with the EFP.

To view additional EFP properties:

---

Step 1 In the Cisco ANA NetworkVision map view, select the required EFP in the navigation pane or in the map pane and then do either of the following:

•Right-click the EFP and choose Properties.

•Choose Node > Properties.

The EFP Properties window displays the information described in Table 12-12.

Table 12-12 EFP Properties Window 

Field	Description
EFP ID	Identifier for the EFP.
VLAN Match Criteria	Match criteria configured on the EFP for forwarding decisions.
Operational State	Operational status of the EFP: Up or Down.
Administrative State	Administrative status of the EFP: Up or Down.
Binding	Hyperlinked entry to the relevant item in logical inventory, such as a pseudowire or bridge.
Rewrite Definition	Rewrite command configured on the EFP: pop, push, or translate.

Step 2 To view EFP properties in physical inventory, navigate to the required interface in either of the following ways:

•Use the procedure described in Viewing and Renaming Ethernet Flow Domains to navigate to the individual interface.

•In physical inventory, navigate to and then select the required interface.

The EFPs tab is displayed in the content pane next to the Subinterfaces tab as shown in Figure 12-8.

Figure 12-8 EFPs Tab in Physical Inventory

Table 12-13 describes the information displayed in the EFPs tab.

Table 12-13 EFPs Tab 

Field	Description
EFP ID	EFP identifier.
Operational State	EFP operational state.
VLAN	VLAN identifier.
Inner VLAN	CE-VLAN identifier.
Translated VLAN	Translated VLAN identifier.
Translated Inner VLAN	Translated CE-VLAN identifier.
Binding	Hyperlinked entry to the specific bridge or pseudowire in logical inventory.
Description	Configured description for the EFP.

---

Understanding EFP Severity and Ticket Badges

Severity and ticket badges are displayed on EFP icons as follows:

•If the EFP element represents an EFP configuration, such as a service instance on a Cisco 7600 device or an enhanced port on a Cisco ASR 9000 device and is associated directly with a network VLAN or a bridge domain switching entity, the severity and ticket badges are based on the underlying VNE EFP configuration service instance. See Figure 12-9.

Figure 12-9 EFP Severity and Ticket Badges Based on Underlying Service Instance

•If the EFP element represents a VLAN interface for a regular switch port, the severity and ticket badges are based on the corresponding port. See Figure 12-10.

Figure 12-10 EFP Severity and Ticket Badges Based on Corresponding Port

Viewing EVC Service Properties

Certain EVC service properties are configured as port attributes. These attributes determine the degree of service transparency and protect the service provider's network from protocol control traffic. Cisco ANA discovers these key EVC service properties and displays this information in physical inventory for the following devices:

•Cisco ME3400- and Cisco ME3400E-series devices running Cisco IOS versions 12.2(52)SE to 12.2(54)SE.

•Cisco 3750 Metro devices running Cisco IOS versions 12.2(52)SE to 12.2(54)SE.

To view EVC port-related properties for the supported devices and software versions:

---

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

Step 2 In the inventory window, choose Physical Inventory > Chassis > module > port.

Figure 12-11 shows an example of a port in physical inventory configured with these EVC properties.

Figure 12-11 EVC Port Properties in Physical Inventory

Table 12-14 describes the information displayed for these properties.

Table 12-14 EVC Port Properties in Physical Inventory 

Field	Description
Storm Control and Monitoring Properties Area
Port Monitoring Interval	Keepalive interval in seconds. The default value is ten seconds.
Storm Control	Status of storm control on the port: Enabled or Disabled.
Storm Control Type	Type of storm the port is configured for protection from: Broadcast, Multicast, or Unicast.
Port Monitoring Status	Status of port monitoring: •Enabled—The switch sends keepalive messages on user network interfaces (UNIs) and enhanced network interfaces (ENIs) and does not send keep alive messages on network node interfaces (NNIs). •Disabled—The switch does not send keepalive messages.
Storm Control Level	Representing a percentage of the total available bandwidth of the port, the threshold at which additional traffic of the specified type is suppressed until the incoming traffic falls below the threshold.
Security Properties Areas
Port Security	Status of security on the port: Enabled or Disabled.
Aging Type	Type of aging used for automatically learned addresses on a secure port: •Absolute—Times out the MAC address after the specified age-time has been exceeded, regardless of the traffic pattern. This is the default for any secured port, and the age-time value is set to 0. •Inactivity—Times out the MAC address only after the specified age-time of inactivity from the corresponding host has been exceeded.
Violation Mode	Action that occurs when a new device connects to a port or when a new device connects to a port after the maximum number of devices are connected: •Protect—Drops packets with unknown source addresses until a sufficient number of secure MAC addresses are removed to drop below the maximum value •Restrict—Drops packets with unknown source addresses until a sufficient number of secure MAC addresses are removed to drop below the maximum value and causes the Security Violation counter to increment. •Shutdown—Puts the interface into the error-disabled state immediately and sends an SNMP trap notification.
Aging Time	Length of time, in minutes, that a MAC address can remain on the port security table.
MAC Address Limit	Maximum number of MAC addresses allowed on the interface.

---

Viewing Virtual Switching Instance Properties

To view VSI properties in Cisco ANA NetworkVision, open the VSI properties window in either of the following ways:

•Double-click the required device and, in the inventory window, choose Logical Inventory > VSIs > vsi.

•In the navigation pane, expand the VPLS instance, right-click the required VPLS forward, and choose Properties. (See Figure 12-12.)

Figure 12-12 VPLS Forward in Cisco ANA NetworkVision Navigation Pane

The first option opens the inventory window, while the second option opens a standalone VSI Properties window. The information that is displayed is the same for both options.

VSI properties are displayed as shown in Figure 12-13.

Figure 12-13 VSI Properties in Logical Inventory

Table 12-15 describes the information that is displayed for the selected VSI.

Table 12-15 VSI Properties in Logical Inventory 

Field	Description
VSI Name	VSI name.
VPN ID	VPN identifier used in an MPLS network to distinguish between different VPLS traffic.
VSI Mode	VSI mode: Point-to-Point (default) or Multipoint.
Discovery Mode	VSI discovery mode: Manual, BGP, LDP, RADIUS, DNS, MSS/OSS, or Unknown.
Operational State	VSI operational status: Up or Down.
Administrative State	VSI administrative status: Up or Down.
Local Bridge	Local bridge, hyperlinked to the bridge in logical inventory.
Pseudowires Table
Pseudowire ID	Pseudowire identifier, hyperlinked to the Tunnel Edges table under Pseudowires in logical inventory.
Autodiscovery	Whether the pseudowire was automatically discovered: True or False.
Split Horizon	SSH pseudowire policy that indicates whether or not packets are forwarded to the MPLS core: True or False.
Pseudowire Peer IP	IP address of the pseudowire peer.
Pseudowire VC ID	Pseudowire virtual circuit identifier.

Viewing VPLS Core or Access Pseudowire Endpoint Properties

Pseudowire endpoints are displayed under VPLS Instance (Access) or VPLS Forward (Core) in the Cisco ANA NetworkVision navigation pane.

To view pseudowire endpoint properties for a VPLS instance, right-click the required pseudowire endpoint in the navigation pane, and choose Properties. (See Figure 12-14.)

Figure 12-14 VPLS Pseudowire in Cisco ANA NetworkVision Navigation Pane

Figure 12-15 shows an example of the Tunnel Properties window that is displayed.

Figure 12-15 VPLS Tunnel Properties Window

Table 12-16 describes the information that is displayed for pseudowire endpoint properties.

Table 12-16 Tunnel Properties Window 

Field	Description
Port	VSI on which the pseudowire is configured, hyperlinked to the VSI in logical inventory.
Peer	Hyperlinked entry to the pseudowire endpoint peer pseudowires in logical inventory.
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.
Tunnel Status	Operational state of the tunnel: Up or Down.
Local VC Label	MPLS label that is used to identify or access the tunnel. It is inserted into the MPLS label stack by the local router.
Local Router IP	IP address of this tunnel edge, which is used as the MPLS router identifier.
Tunnel ID	Identifier that, along with the router IP addresses of the two pseudowire endpoints, identifies the PWE3 tunnel.
Peer Router IP	IP address of the peer tunnel edge, which is used as the MPLS router identifier.
Local MTU	Size, in bytes, of the MTU on the local interface.
Remote MTU	Size, in bytes, of the MTU on the remote interface.
Signaling Protocol	Protocol used by MPLS to build the tunnel, such as LDP or TDP.
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.

Viewing VPLS Access Ethernet Flow Point Properties

The ports that represent the attachment circuits to VPLS instances are displayed under VPLS instances in the Cisco ANA NetworkVision navigation pane.

To view the properties for the Access Ethernet Flow Points configured for a VPLS instance, right-click the required interface in the navigation pane, and choose Properties. (See Figure 12-16.)

Figure 12-16 VPLS Interface in Cisco ANA NetworkVision Navigation Pane

Figure 12-17 shows an example of the Port Connector Properties window.

Figure 12-17 Port Connector Properties Window

The information displayed in this window is the same as that displayed when the interface is selected in physical inventory.

The following information is displayed, depending on the interface and its configuration:

•Location and interface details.

•Technology-related information, such as Ethernet CSMA/CD or ATM IMA properties.

•VLAN configuration details.

•List of the configured subinterfaces on the port. For more information on the Subinterfaces table, see Viewing a Port Configuration, page 17-33.

•List of the configured EFPs on the port. For more information on the EFPs table, see Viewing EFP Properties.

•List of VLAN mappings configured on the port. For more information about the VLAN Mappings table, see Viewing VLAN Mappings.

Viewing and Renaming Ethernet Flow Domains

An Ethernet flow domain represents an Ethernet access domain. The Ethernet flow domain holds all network elements between the CE (inclusive, if managed by the SP), up to the SP core (exclusive). This includes CE, access, aggregation, and distribution network elements.

An Ethernet flow domain can have no N-PEs (flat VLAN) or one or more N-PEs (N-PE redundancy configuration). The Ethernet flow domain is defined using physical connectivity at the port level, and not at the NE level. STP is used to mark the root bridge, root or blocked ports, and blocked VLAN links.

To view Ethernet flow domains:

---

Step 1 In Cisco ANA NetworkVision, choose Network Inventory > Ethernet Flow Domains.

The Ethernet Flow Domain List window is displayed with the name and a brief description for each Ethernet flow domain as shown in Figure 12-18.

Figure 12-18 Ethernet Flow Domains in Logical Inventory

Step 2 To rename an Ethernet flow domain:

a. Right-click the required domain, then choose Rename.

b. In the Rename Node dialog box, enter a new name for the domain.

c. Click OK.

The window is refreshed, and the new name is displayed.

Step 3 To view Ethernet flow domain properties, do either of the following:

•Right-click the required domain, then choose Properties.

•Double-click the required domain.

The Ethernet Flow Domain Properties window is displayed as shown in Figure 12-19.

Figure 12-19 Ethernet Flow Domain Properties Window

Table 12-17 describes the information displayed in the Ethernet Flow Domain Properties window.

---

Note Not all fields are available in all tables. The table contents depend on the domain type, such as FastEthernet.

---

Table 12-17 Ethernet Flow Domain Properties Window 

Field	Description
Domain Name	Name of the selected domain.
System Defined Name	Domain name as identified by the most dominant device and its lowest port name lexicographically.
Elements Table
ID	Interface identifier, hyperlinked to the interface in physical inventory.
Type	Aggregation group type: Ethernet Channel (EtherChannel), or IEEE 8023 AD LAG (IEEE 802.3 link aggregation group).
Discovery Protocol	Discovery protocol used on the interface.
Sending Alarms	Whether the interface is configured for sending alarms: True or False.

Step 4 To navigate to the individual interface or link aggregation group, click an interface ID or group.

The interface or link aggregation group properties are displayed in the inventory window.

---

Working with VLANs and VLAN Overlays

The following topics provide information and procedures for working with VLANs and VLAN overlays:

•VLAN and EFD Discovery

•VLAN Elements

•Switching Entities Containing Termination Points

•Adding VLANs to a Map

•Removing VLANs from a Map

•Viewing VLAN Mappings

•Working with Associated VLANs

•Viewing VLAN Links Between VLAN Elements and Devices

•Adding a VLAN Overlay to a Map View

•Displaying or Hiding VLAN Overlays

•Removing a VLAN Overlay

•Viewing VLAN Service Link Properties

•Viewing REP Information in VLAN Domain Views and VLAN Overlays

•Viewing REP Properties for VLAN Service Links

•Viewing STP Information in VLAN Domain Views and VLAN Overlays

•Viewing STP Properties for VLAN Service Links

•Viewing VLAN Trunk Group Properties

•Viewing VLAN Bridge Properties

VLAN and EFD Discovery

When you start the Cisco ANA gateway the first time, Cisco ANA waits for two topology cycles to complete before discovering new VLANs, VLAN associations, and EFDs. The default configured time for two topology cycles to complete is one hour, but might be configured for longer periods of time on large setups. This delay allows the system to stabilize, and provides the time needed to model devices and discover links.

Similarly, when you restart the gateway, Cisco ANA uses this stabilization period to add existing information on VLANs, VLAN associations, and EFDs to maps and logical inventory. EFDs that were previously stored in the database can be viewed in inventory, and VLANs can be viewed in maps.

During this delay, Cisco ANA does not add VNEs or apply updates to existing VLANs or EFDs.

After the initial delay has passed, Cisco ANA discovers new VLANs, VLAN associations, and EFDs, applies updates to existing VLANs, VLAN associations, and EFDs, and updates the database accordingly.

VLAN Elements

The following concepts are important to understand when working with the representation of edge EFPs inside VLANs:

•VLAN Elements in Cisco ANA NetworkVision

•VLANs

•Switching Entities

•Ethernet Flow Points

VLAN Elements in Cisco ANA NetworkVision

Table 12-18 describes the icons that Cisco ANA uses to represent VLAN elements.

Table 12-18 VLAN Elements and Icons in Cisco ANA NetworkVision 

Element	Associated Network Element	Icon
Network VLAN	None
Switching entity	Bridge
Ethernet Flow Point (EFP)	Ethernet port

VLANs

As described in the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide, Cisco ANA discovers and allows you to display maps with a network-level view of VLANs.

In Cisco ANA, a VLAN entity consists of one or more switching entities and the corresponding EFP elements.

A network VLAN represents the virtual LAN. The network VLAN holds its contained switching entities and can be associated to a customer. The network VLAN also holds the Ethernet flow points that are part of the network VLAN but not part of any switching entity. For example, a port that tags ingress flows after which the flow moves to a different VLAN.

Switching Entities

A switching entity represents a device-level Layer 2 forwarding entity (such as a VLAN or bridge domain) that participates in a network VLAN. A switching entity is associated to a network VLAN according to its relationship to the same Ethernet Flow Domain (EFD) and the VLAN identifier.

If you right-click a switching entity in Cisco ANA NetworkVision and then choose Inventory, the inventory window is displayed with the corresponding bridge selected in Logical Inventory.

A switching entity typically contains EFP elements.

Ethernet Flow Points

An Ethernet flow point (EFP) can represent a port that is configured for participation in a specific VLAN.

If you right-click an EFP in Cisco ANA NetworkVision and then choose Inventory, the inventory window is displayed with the corresponding port selected in Physical Inventory.

EFPs that are located in a switching entity represent Ethernet ports that are configured as switch ports (in either Access, Trunk, or Dot1Q tunnel mode).

Figure 12-20 shows an example of EFPs configured as switch ports in Cisco ANA NetworkVision.

Figure 12-20 EFPs in a Cisco ANA NetworkVision Map

EFPs that are located directly inside a VLAN represent one of the following:

•Termination point EFPs—Ethernet ports that are at the edge of a Layer 2 domain flow, such as a VLAN, on which traffic enters a Layer 3 domain or a different Layer 2 domain, such as EoMPLS. These ports are found on such devices as the Cisco 7600 series, Cisco GSR, and Cisco ASR 9000 series devices.

These EFPs are typically connected to a switching entity inside the VLAN by a VLAN link, as shown in Figure 12-21.

Figure 12-21 Termination Point EFP Inside a VLAN

•Edge EFPs—A subset of EFPs that exist inside a switching entity but that are not connected to other EFPs and that represent edge EFPs in the context of the VLAN.

In Cisco ANA, edge EFPs are displayed directly under the VLAN at the same level as their switching entities and are connected to their corresponding switching entities by a dotted link, as shown in Figure 12-22.

Figure 12-22 Edge EFP Inside a VLAN

Expanding the switching entity VLAN-400@c7-sw4 in Figure 12-22 allows us to see in Figure 12-23 that the highlighted EFP (GigabitEthernet1/0/2@c7-sw4) is:

–Not connected to any other EFP by a VLAN link (as opposed to EFP GigabitEthernet1/0/1@c7-sw4).

–Displayed both inside and outside its switching entity.

Figure 12-23 Edge EFP Displayed Inside and Outside of Switching Entity

You can delete EFPs and switching entities that have a reconciliation icon by right-clicking them and choosing Delete. After all switching entities and EFPs are deleted from a network VLAN, the empty network VLAN is automatically deleted from Cisco ANA NetworkVision after a few minutes.

Switching Entities Containing Termination Points

For some devices, such as Cisco 7600 series, Cisco GSR, and Cisco ASR 9000 series devices, the related switching entities can contain Ethernet flow point elements that serve as termination points on different network VLANs. If a single map contains both the switching entities and the network VLANs, a link is displayed between them.

Adding VLANs to a Map

You can add VLANs to a map if the VLANs were previously discovered by Cisco ANA and are not currently displayed in the map. For more information about VLANs, see the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide.

---

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

---

To add VLANs to a map:

---

Step 1 In Cisco ANA NetworkVision, display the map to which you want to add the VLANs.

Step 2 Choose File > Add to Map > VLAN. The Add VLAN dialog box is displayed as shown in Figure 12-24.

Figure 12-24 Add VLAN Dialog Box

Step 3 In the Add VLAN dialog box, do either of the following:

•Choose a search category, enter a search string, then click Go to narrow the VLAN display to a range of VLANs or a specific VLAN.

The search condition is "contains." Search strings are case-insensitive. For example, if you choose the Name category and enter "net," Cisco ANA displays VLANs that have "net" anywhere in their names. The string "net" can be at the beginning, the middle, or end of the name, such as Ethernet.

•Choose Show All to display all the VLANs.

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

---

Tip Press Shift or Ctrl to choose multiple adjoining or nonconsecutive VLANs.

---

Step 5 Click OK.

The VLANs are displayed in the Cisco ANA NetworkVision content pane as shown in Figure 12-25.

Any tickets that apply to the VLANs are displayed in the ticket pane.

Figure 12-25 Network VLAN in Cisco ANA NetworkVision Map View

---

After you add a VLAN to a map, you can use Cisco ANA NetworkVision to view its switching entities and Ethernet flow points. For more information, see:

•Viewing and Renaming Ethernet Flow Domains

•Viewing EFP Properties

You can view additional information about REP and STP in logical inventory, VLAN domain views, and VLAN overlays.

For REP, see:

•Viewing Resilient Ethernet Protocol Properties

•Viewing REP Information in VLAN Domain Views and VLAN Overlays

•Viewing REP Properties for VLAN Service Links

For STP, see:

•Viewing Spanning Tree Properties

•Viewing STP Information in VLAN Domain Views and VLAN Overlays

•Viewing STP Properties for VLAN Service Links

Removing VLANs from a Map

You can remove one or more VLANs from the current map. This change does not affect other maps. Removing a VLAN from a map does not remove it from the Cisco ANA database. You can add the VLAN to the map at any time.

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

•Removing a VLAN affects other users who 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 VLAN.

To remove a VLAN, in the Cisco ANA NetworkVision navigation pane or map view, right-click the VLAN and choose Remove from Map.

The VLAN is removed from the navigation pane and map view along with all VLAN elements such as connected CE devices. Remote VLANs (extranets) are not removed.

Viewing VLAN Mappings

VLAN mapping, or VLAN ID translation, is used to map customer VLANs to service provider VLANs. VLAN mapping is configured on the ports that are connected to the service provider network. VLAN mapping acts as a filter on these ports without affecting the internal operation of the switch or the customer VLANs.

If a customer wants to use a VLAN number in a reserved range, VLAN mapping can be used to overlap customer VLANs by encapsulating the customer traffic in IEEE 802.1Q tunnels.

To view VLAN mappings:

---

Step 1 In Cisco ANA NetworkVision, double-click the device with VLAN mappings configured.

Step 2 In the inventory window, choose Physical Inventory > Chassis > slot > port.

Step 3 Click VLAN Mappings next to the Subinterfaces tab in the lower portion of the content pane.

The VLAN Mappings tab is displayed as shown in Figure 12-26.

Figure 12-26 VLAN Mappings Tab in Physical Inventory

Table 12-19 describes the information that is displayed in the VLAN Mappings table.

Table 12-19 VLAN Mappings Table 

Field	Description
Direction	Whether the VLAN mapping is defined in the incoming or outgoing direction: In or Out.
VLAN	Customer-side VLAN identifier.
Inner VLAN	Used for two-to-one mappings, the customer-side inner VLAN identifier.
Translated VLAN	Translated, or mapped, service-provider side VLAN identifier.
Translated Inner VLAN	Translated, or mapped, service-provider side inner VLAN identifier.
Action	Action taken if the VLAN traffic meets the specified mapping: Translate or Drop.

---

Working with Associated VLANs

Cisco ANA discovers associations between network VLANs and displays the information in Cisco ANA NetworkVision. Network VLAN associations are represented by VLAN service links, and can be any of the tag manipulation types described in Table 12-20.

Table 12-20 Types of Tag Manipulations in VLAN Associations 

VLAN Tag Manipulation	Description	Example
One-to-one	One VLAN tag is translated to another VLAN tag.	VLAN tag 100 > VLAN tag 200
Two-to-two	•Two VLAN tags exist and both are translated to other tags. •Two VLAN tags exist, but tag manipulation is applied only to the outer tag.	Inner tag 100, Outer tag 101 > Inner tag 200, Outer tag 201 Inner tag 100, Outer tag 101 > Inner tag 100, Outer tag 201
One-to-two	One VLAN tag exists and an additional tag is inserted into the packet.	VLAN tag 100 > Inner tag 100, Outer tag 101

When working with VLANs, you can:

•Add an associated VLAN—See Adding an Associated VLAN.

•View properties for associated VLANs—See Viewing Associated Network VLAN Service Links and VLAN Mapping Properties.

Adding an Associated VLAN

To add an associated VLAN to an existing VLAN in a map:

---

Step 1 In Cisco ANA NetworkVision, select the required VLAN in the map view.

Step 2 Right-click the VLAN and choose Add Associated VLAN.

The Add Associated VLAN table is displayed as shown in Figure 12-27.

Figure 12-27 Add Associated VLAN Window

In this example, the selected network VLAN has two associated VLANs: VLAN-141 and VLAN-600.

Table 12-21 describes the information displayed in the Add Associated VLAN table.

Table 12-21 Add Associated VLAN Table 

Field	Description
Name	Name of the VLAN.
ID	VLAN identifier.
Ethernet Flow Domain	Name of the Ethernet flow domain.
Description	Brief description of the VLAN.

Step 3 Select the required VLAN in the Add Associated VLAN table, then click OK.

The associated network VLAN is added to the map in Cisco ANA NetworkVision.

---

Viewing Associated Network VLAN Service Links and VLAN Mapping Properties

After you add an associated network VLAN, you can:

•View the associated network VLAN service links in Cisco ANA NetworkVision in the thumbnail view.

•View VLAN mapping properties in the Link Properties window.

To view associated network VLAN service links and VLAN mapping properties:

---

Step 1 Select the required network VLAN in the map view.

Step 2 Right-click the VLAN, then choose Show Thumbnail.

Figure 12-28 shows an example of a network VLAN in the thumbnail view.

The VLAN service links are displayed as lines between the associated network VLANs. The links represent the connections between the Ethernet flow points that are part of each network VLAN.

Figure 12-28 VLAN Service Links Between Associated Network VLANs

Step 3 To view additional information, right-click a link, and choose Properties.

The Link Properties window is displayed as shown in Figure 12-29.

If VLAN tag manipulation is configured on the link, the VLAN Mapping Properties area in the Link Properties window displays the relevant information. For example, in Figure 12-29, the VLAN Mapping Properties area shows that a one-to-one VLAN mapping for VLAN tag 142 to VLAN tag 141 is configured on port GigabitEthernet1/1/1 on c7-sw10 on the egress direction.

Figure 12-29 VLAN Mapping Properties in Link Properties Window

---

For additional information about viewing network VLAN service link properties, see:

•Viewing REP Properties for VLAN Service Links

•Viewing STP Properties for VLAN Service Links

Viewing VLAN Links Between VLAN Elements and Devices

If a Cisco ANA NetworkVision map contains a VLAN and the network element on which the VLAN is configured, along with EFPs, switching entities, or network VLANs, you might see what appear to be multiple associations between the logical and physical entities. Actually, however, you are seeing other views of the original VLAN link.

For example, assume that you have the following situation, as shown in Figure 12-30 and described in the following paragraphs.

Figure 12-30 VLAN Elements and Devices in Cisco ANA NetworkVision

The elements are configured as follows:

•Port GigaEthernet1/0/1 on element C4-CE9 is connected to port FastEthernet0/4 on element C4-UPE7 by an Ethernet topology link.

•Port GigaEthernet1/0/1 on element C4-CE9 is a trunk port associated with VLAN-1410 which is configured on element C4-CE9.

•Port FastEthernet0/4 on element C4-UPE7 is a trunk port associated with VLAN-140 which is configured on element C4-UPE7.

•Port FastEthernet0/4 on element C4-UPE7 has a VLAN mapping to tunnel VLAN-1410 (C-VLAN) in VLAN-140 (SP-VLAN).

In this example, VLAN discovery identified two network VLANs: VLAN-1410 and VLAN-140. Each of these network VLANs contains a switching entity and an EFP that represent the connected ports, GigaEthernet1/0/1 and FastEthernet0/4, respectively.

The four links in the map are identified in Figure 12-31 and described in the following table.

Figure 12-31 Links Between VLAN Elements and Devices

1	The Ethernet topological link between port GigaEthernet1/0/1 on VNE C4-CE9 and portFastEthernet0/4 on VNE C4-UPE7.
2	The VLAN link between GigaEthernet1/0/1@C4-CE9 EFP and FastEthernet0/4@C4-UPE7 EFP.
3	Another view of the VLAN link (link 2), shown as a link between VNE C4-CE9 and FastEthernet0/4@C4-UPE7 EFP.
4	Another view of the VLAN link (link 2), shown as a link between VNE C4-UPE7 and GigaEthernet1/0/1@C4-CE9 EFP.

The key point is that a link between a VNE and EFP, switching entity, or network VLAN does not represent an association between the VNE and the logical element. Such a link is simply another view of the VLAN link.

If the thumbnail view is closed, instead of a link between the VNE and EFP, you will see a link between the VNE and the switching entity or network VLAN.

Adding a VLAN Overlay to a Map View

You can create an overlay of a specific VLAN on top of the physical network elements displayed in a map view. The overlay highlights the network elements and links that the selected VLAN and its associated VLANs traverse. Network elements and links that are not part of the VLAN are dimmed in the map view.

The VLAN overlay is a snapshot of the network to help you visualize the network elements and links connected to a VLAN. The overlay displays STP and REP link and port information.

If you select a network VLAN that is associated with other VLANs, the associated VLANs are included in the overlay.

The VLAN 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 site interconnections use the same link. For more information about VLAN overlays, see the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide.

To add a VLAN overlay:

---

Step 1 Display the network map for which you want to create an overlay in Cisco ANA NetworkVision.

Step 2 In the toolbar, choose Choose Overlay Type > VLAN.

Step 3 In the Select VLAN Overlay dialog box, do either of the following:

•Choose a search category, enter a search string, then click Go to narrow the selection to a set of overlays or a specific overlay.

The search condition is "contains." Search strings are case-insensitive. For example, if you choose the Name category and enter "net," Cisco ANA displays overlays that have "net" in their names. The string "net" can be at the beginning, middle, or end of the name, such as Ethernet.

•Choose Show All to view all overlays.

Step 4 Select an overlay, then click OK.

The network elements and physical links used by the selected VLAN overlay are highlighted in the network map. All other network elements and links are dimmed. The VLAN name is displayed in the title of the window. See Figure 12-32.

Figure 12-32 VLAN Overlay Example

Figure 12-33 shows an example of a VLAN with associated VLANs. In this example:

•VLAN 142 is configured on devices in the San Francisco South aggregation.

•VLAN 141 is configured on devices in the San Francisco Center aggregation and on c7-npe1-76.

Figure 12-33 VLAN Overlay with VLAN Associations

---

---

Note The overlay is a snapshot taken at a specific point in time. As a result, the information in the overlay might become stale. To update the overlay, click Refresh the Last Selected Overlay in the toolbar.

---

Displaying or Hiding VLAN Overlays

After you create a VLAN overlay, you can hide it by clicking Hide Overlay in the toolbar. All previously dimmed network elements and links are displayed. To display the overlay, click Show Overlay.

---

Note The Overlay icon toggles between Show Overlay and Hide Overlay. When selected, the VLAN overlay is displayed and the Hide Overlay tool is active. When deselected, the VLAN overlay is hidden and the Show Overlay tool is active.

---

Removing a VLAN Overlay

To remove a VLAN overlay from a map, choose Choose Overlay Type > None in the toolbar. The overlay is removed from the map, and the Show Overlay/Hide Overlay icon is dimmed.

Viewing VLAN Service Link Properties

See the following topics for information on viewing VLAN service link properties:

•Viewing REP Properties for VLAN Service Links

•Viewing STP Properties for VLAN Service Links

•Viewing Associated Network VLAN Service Links and VLAN Mapping Properties

Viewing REP Information in VLAN Domain Views and VLAN Overlays

You can view REP segment and port information in Cisco ANA NetworkVision in the map view. The icons displayed depend on whether you view the REP information in the VLAN domain view or in a VLAN overlay. Table 12-22 describes the icons and badges used to represent REP segment and port information.

Table 12-22 REP Icons and Badges in VLAN Domain Views and Overlays 

Item	Description	VLAN Domain View	VLAN Overlay
	REP identifier—Uses the format REP-id where id represents the REP segment identifier, such as REP-255.	The REP identifier is displayed in the domain view if the visual link represents only one link. f the visual link represents more than one link, no REP identifier is displayed.	The REP identifier is displayed in a VLAN overlay view if all the links represented by the visual link are from the same source to the same destination.
	REP identifier for incorrect configuration—Indicates that the two sides of the link are configured differently or incorrectly.
	Multiple links icon—Indicates that multiple links or badges are represented by a single visual link.	The multiple links icon is displayed in the domain view if more than one link is represented by the visual link and at least one of the links has a REP identifier or badge.	The multiple links icon is displayed in a VLAN overlay view if either of the following is true: •More than one link is represented by the visual link and the links have different sources or destinations. •A badge or REP identifier exists on a sublink.
	REP primary badge—Indicates a REP primary port.
	Blocking badge—Indicates a REP alternate port.
	Primary and blocking badge—Indicates a REP primary port that is also blocking.

Viewing REP Properties for VLAN Service Links

To view REP properties for a VLAN service link, open the Link Properties window in either of the following ways:

•Double-click the VLAN service link.

•Right-click the VLAN service link, and choose Properties.

Figure 12-34 shows an example of the Link Properties window with REP information.

Figure 12-34 VLAN Service Link Properties Window with REP Information

Table 12-23 describes the information that is displayed for REP for each end of the link.

Table 12-23 REP Properties in VLAN Service Link Properties Window 

Field	Description
Segment ID	REP segment identifier.
Port Type	Port type: Primary Edge, Secondary Edge, or Intermediate.
Port Role	Role or state of the REP port depending on its link status and whether it is forwarding or blocking traffic: Failed, Alternate, or Open.
Port Status	Operational link state of the REP port: None, Init Down, No Neighbor, One Way, Two Way, Flapping, Wait, or Unknown.

Viewing STP Information in VLAN Domain Views and VLAN Overlays

You can view STP segment and port information in Cisco ANA NetworkVision in the map view. The icons displayed depend on whether you view the STP information in the VLAN domain view or in a VLAN overlay. Table 12-22 describes the icons and badges used to represent STP link and port information.

Table 12-24 STP Information in VLAN Domain Views and Overlays 

Description	VLAN Domain View	VLAN Overlay
The STP root bridge, or root of the STP tree, is indicated by an uppercase R.
An STP root port is the port at the root of the STP tree. Each switching entity in the network VLAN should have a port designated as the root port. The STP root port is indicated by an uppercase R on the Ethernet flow point that is designated the root port.
STP blocks some VLAN ports to ensure a loop-free topology. The blocked port is marked with a red deny badge on the side on which traffic is denied.

To view additional STP information in a VLAN overlay, right-click an STP link and choose Show Callouts. The following STP port information is displayed as shown in Figure 12-35:

•Port name

•Port role

•Port state

Figure 12-35 STP Link Information in a VLAN Overlay

•Viewing VLAN Trunk Group Properties

•Viewing VLAN Bridge Properties

Viewing STP Properties for VLAN Service Links

To view STP properties for a VLAN service link, open the Link Properties window in either of the following ways:

•Double-click the VLAN service link.

•Right-click the VLAN service link, and choose Properties.

Figure 12-36 shows an example of the Link Properties window with STP information.

Figure 12-36 STP Properties in VLAN Service Link Properties Window

Table 12-25 describes the information that is displayed for STP for the VLAN service link.

Table 12-25 STP Properties in VLAN Service Link Properties Window 

Field	Description
Port State	STP port state: Disabled, Blocking, Listening, Learning, or Forwarding,
Port Role	STP port role: Unknown, Backup, Alternative, Designated, Root, or Boundary.

Viewing VLAN Trunk Group Properties

VTP is a Layer 2 multicast messaging protocol that manages the addition, deletion, and renaming of VLANs on a switched network-wide basis.

Cisco ANA displays VTP information in the Cisco ANA NetworkVision logical inventory. VTP information is shown only for Cisco devices that support VTP, and support is provided only for VTP Version 1 and 2. Support for Version 3 is limited to the additional attributes that are supported by the version, such as primary and secondary server. No support is provided for the display of VTP information at the port (trunk) level.

Cisco ANA shows all VTP modes: Server, Client, Transparent, and Off. For each mode, Cisco ANA displays the relevant mode information such as VTP domain, VTP mode, VTP version, VLAN trunks, and the trunk encapsulation. Cisco ANA also displays VTP domain information in a view that includes a list of all switches that are related to these domains, their roles (server, client, and so on), and their VTP properties.

For additional information about VTP, see the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide.

To view VTP properties:

---

Step 1 In Cisco ANA NetworkVision, choose Network Inventory > VTP Domains.

Step 2 Double-click the VTP domain you want to view.

The VTP Domain Properties window is displayed as shown in Figure 12-37.

Figure 12-37 VTP Domain Properties Window in Logical Inventory

Table 12-26 describes the information that is displayed in the VTP Domain Properties window.

Table 12-26 VTP Domain Properties Window 

Field	Description
Managed Element	Managed element name, hyperlinked to VTP in logical inventory.
Operating Mode	VTP operating mode: •Server—Allows VLAN creation, modification, and deletion, and specification of other configuration parameters for the entire VTP domain. Server is the default mode. •Client—Same behavior as VTP server, except VLANs cannot be created, changed, or deleted. •Transparent—The device does not participate in the VTP. The device does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements. However, the device forwards received VTP advertisements out of their trunk ports in VTP Version 2. •Off—The device does not participate in VTP and does not forward VTP advertisements.
Process Status	Status of the VTP process: Running or Disabled.
Authentication Enabled	Whether or not VTP authentication is enabled: True or False. Authentication ensures authentication and integrity of switch-to-switch VTP messages. VTP Version 3 introduces an additional mechanism to authenticate the primary VTP server as the only device allowed to change the VLAN configuration on a network-wide basis.
Configuration Revision	32-bit number that indicates the level of revision for a VTP packet. Each VTP device tracks the VTP configuration revision number that is assigned to it. Most VTP packets contain the VTP configuration revision number of the sender.
Version	VTP version: 1, 2, or 3.

Step 3 To view the VTP properties at the device, double-click the VTP domain.

Table 12-27 describes the VTP information that is displayed in the inventory window content pane.

Table 12-27 VTP Properties in Inventory 

Field	Description
Operating Mode	VTP operating mode: Server, Client, Transparent, or Off.
Domain Name	VTP domain name.
Version	VTP version: 1, 2, or 3.
Pruning	Whether or not VTP pruning is enabled: True or False. VTP pruning increases available bandwidth by restricting flooded traffic to those trunk links that the traffic must use to access the appropriate network devices.
Configuration Revision	32-bit number that indicates the level of revision for a VTP packet.
Authentication	Whether or not VTP authentication is enabled: True or False.

Step 4 When finished, press Ctrl + F4 to close each VTP properties window.

---

Viewing VLAN Bridge Properties

You can view VLAN bridges provisioned on a device by displaying the device in the Cisco ANA NetworkVision inventory window and choosing Bridges in the Logical Inventory tree. To view VLAN bridge properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the device containing the VLAN bridges you want to view.

Step 2 In the inventory window, choose Logical Inventory > Bridges > bridge.

VLAN bridge properties are displayed as shown in Figure 12-38.

Figure 12-38 VLAN Bridge Properties in Logical Inventory

Table 12-28 describes the information that is displayed. Depending on the bridge configuration, any of the tabs might be displayed for the selected bridge.

Table 12-28 VLAN Bridge Properties 

Field	Description
Name	VLAN bridge name.
Type	VLAN bridge type.
MAC Address	VLAN bridge MAC address.
VLAN ID	VLAN bridge VLAN identifier.
STP Instance	STP instance information, hyperlinked to the STP entry in logical inventory.
Bridge Table Tab
MAC Address	Bridge MAC address.
Port	Port associated with the bridge, hyperlinked to the interface in physical inventory.
Sending Alarms	Whether or not the port is configured for sending alarms: True or False.
Interfaces Tab
ID	VLAN interface identifier, hyperlinked to the interface in physical inventory.
Type	VLAN interface type, such as Layer 2 VLAN.
Mode	VLAN interface configuration mode: •Unknown—The interface is not VLAN aware. •Access—Puts the interface into permanent nontrunking mode and negotiates to convert the link into a nontrunk link. The interface becomes nontrunking. •Dynamic Auto—The interface can convert the link to a trunk link. The interface becomes a trunk if the neighbor interface is set to Trunk or Dynamic Desirable mode. •Dynamic Desirable—The interface actively attempts to convert the link to a trunk link. The interface becomes a trunk if the neighboring interface is set to Trunk, Dynamic Desirable, or Dynamic Auto mode. Dynamic Desirable is the default mode for all Ethernet interfaces. •Trunk—Puts the interface into permanent trunking mode and negotiates to convert the link into a trunk link. The interface becomes a trunk interface even if the neighbor interface is not a trunk interface. •Dot1Q Tunnel—Configures the interface as a tunnel (nontrunking) port to be connected in an asymmetric link with an 802.1Q trunk port. 802.1Q tunneling is used to maintain customer VLAN integrity across a service provider network.
Native VLAN ID	VLAN Identifier (VID) associated with this VLAN. The range of the VLAN ID is (1 to 4067).
VLAN Encapsulation Type	Type of encapsulation configured on the VLAN, such as IEEE 802.1Q.
Allowed VLANs	List of the VLANs allowed on this VLAN interface.
VLAN Encapsulation Admin Type	VLAN administration encapsulation type, such as IEEE 802.1Q.
EFPs Tab
EFP ID	EFP identifier.
Operational State	EFP operational state.
VLAN	VLAN identifier.
Inner VLAN	CE-VLAN identifier.
Translated VLAN	Translated VLAN identifier.
Translated Inner VLAN	Translated CE-VLAN identifier.
Binding Port	Hyperlinked entry to the port in physical inventory.
Description	Brief description of the EFP.
Pseudowires Tab
ID	Pseudowire identifier, hyperlinked to the VLAN entry in Bridges in logical inventory.
Peer	Identifier of the pseudowire peer, hyperlinked to the entry in the Pseudowire Tunnel Edges table in logical inventory.
Tunnel ID	Tunnel identifier.
Tunnel Status	Status of the tunnel: Up or Down.
Peer Router IP	IP address of the peer router for this pseudowire.

Step 3 When finished, press Ctrl + F4 to close each VLAN Bridge properties window.

---

Understanding Unassociated Bridges

Some switching entities might not belong to a flow domain, such as a network VLAN, a VPLS instance, or a network pseudowire. These switching entities are referred to as unassociated bridges.

In addition, a switching entity that belongs to a network VLAN is considered an unassociated bridge if it meets both of the following criteria:

•The network VLAN contains a null Ethernet flow domain (EFD).

•The switching entity contains no switch ports.

Unassociated bridge switching entities can hold Ethernet flow points that serve as termination points on different network VLANs. If these switching entities are added to a map with the relevant VLANs, the links are displayed as shown in Figure 12-39.

Figure 12-39 Switching Entity with EFPs on Different Network VLANs

Adding Unassociated Bridges

Cisco ANA enables you to add unassociated bridges to maps and to view their properties in Cisco ANA NetworkVision.

To add an unassociated bridge to a map:

---

Step 1 In Cisco ANA NetworkVision, select the required map or domain.

Step 2 Open the Add Unassociated Bridge dialog box in one of the following ways:

•Choose File Add to Map > Unassociated Bridge.

•In the toolbar, click Add to Map and choose Unassociated Bridge.

Figure 12-40 shows an example of the Add Unassociated Bridge dialog box.

Figure 12-40 Add Unassociated Bridge Dialog Box

Step 3 In the Add Unassigned Bridge to domain dialog box, select the required bridge and click OK.

The map is refreshed and displays the newly added bridge as shown in Figure 12-41.

Figure 12-41 Unassociated Bridge in Cisco ANA NetworkVision

---

Working with Ethernet Flow Point Cross-Connects

Cisco ANA automatically discovers Ethernet flow point (EFP) cross-connects, also known as locally switched EFPs. Cisco ANA also identifies changes in already identified EFP cross-connects, such as cross-connect deletions or changes. Cross-connect changes can occur when one side of the cross-connect is removed or replaced.

Cisco ANA also associates the VLANs that contain the EFPs that are part of the cross-connects. If the cross-connect contains a range EFP, which represents a range of VLANs, and you add the related VLANs to a map, Cisco ANA displays the links between them and the cross-connect as well. Figure 12-42 shows an example of a cross-connect, two related VLANs, and the links between the cross-connect and the VLANs.

Figure 12-42 EFP Cross-Connect Linked to VLANs in Cisco ANA NetworkVision

Cisco ANA enables you to add EFP cross-connects to maps and to view their properties in inventory, as described in the following topics:

•Adding EFP Cross-Connects

•Viewing EFP Cross-Connect Properties

Adding EFP Cross-Connects

To add an EFP cross-connect to a map:

---

Step 1 In Cisco ANA NetworkVision, select the map to which you wish to add the cross-connect.

Step 2 Open the Add EFP Cross-Connect dialog box in one of the following ways:

•Choose File Add to Map > Cross Connect.

•In the toolbar, click Add to Map and choose Cross Connect.

Step 3 In the Add EFP Cross Connect to domain dialog box, select the required EFP cross-connect and click OK.

The map is refreshed and displays the newly added EFP cross-connect as shown in Figure 12-43.

Figure 12-43 EFP Cross-Connect in Cisco ANA NetworkVision

---

Viewing EFP Cross-Connect Properties

To view EFP cross-connect properties:

---

Step 1 In Cisco ANA NetworkVision, select the EFP cross-connect with the properties you want to view.

Step 2 To open the EFP Cross-Connect Properties window, choose Node > Properties.

Figure 12-44 shows an example of the EFP Cross-Connect Properties window.

Figure 12-44 EFP Cross-Connect Properties Window

Table 12-29 describes the information displayed in the EFP Cross-Connect Properties window.

Table 12-29 EFP Cross-Connect Properties  

Field	Description
Name	EFP cross-connect name.
Segment 1	Identifier of the first cross-connect segment, hyperlinked to its entry in physical inventory.
Segment 2	Identifier of the second cross-connect segment, hyperlinked to its entry in physical inventory.
System Name	Name of system on which the EFP cross-connect is configured.
Local Switching Entry	Hyperlink to the relevant entry in the Local Switching table in logical inventory.

Step 3 To view the Local Switching Entry Properties window, right-click the required EFP cross-connect in Cisco ANA NetworkVision and then choose Properties.

Figure 12-45 shows an example of the Local Switching Entry Properties window.

Figure 12-45 Local Switching Entry Properties Window

Table 12-30 describes the information displayed for the EFP cross-connect in the Local Switching Entry Properties window.

Table 12-30 Local Switching Entry Properties 

Field	Description
Key	Entry key for the cross-connect group.
Entry Status	Status of the cross-connect: Down, Unresolved, or Up.
Segment 1	Identifier of the first cross-connect segment, hyperlinked to the relevant entry in physical inventory.
Segment 1 Port Name	Identifier of the first cross-connect segment port.
Segment 1 Status	Status of the first cross-connect segment, such as Admin Up, Admin Down, Oper Down, or Up.
Segment 2	Identifier of the second cross-connect segment, hyperlinked to the relevant entry in physical inventory.
Segment 2 Port Name	Identifier of the second cross-connect segment port.
Segment 2 Status	Status of the second cross-connect segment, such as Admin Up, Admin Down, Oper Down, or Up.

Step 4 To view the EFP cross-connect properties in logical inventory, double-click the required element in Cisco ANA NetworkVision, then choose Logical Inventory > Local Switching > Local Switching Entity.

Figure 12-46 shows an example of the Local Switching Table.

Figure 12-46 Local Switching Table in Logical Inventory

Table 12-31 describes the information displayed in the Local Switching Table.

Table 12-31 Local Switching Table in Logical Inventory 

Field	Description
Local Switching Table
Key	Entry key for the cross-connect group.
Entry Status	Status of the cross-connect: Down, Unresolved, or Up.
Segment 1	Identifier of the first cross-connect segment, hyperlinked to the relevant entry in physical inventory.
Segment 1 Port Name	Identifier of the first cross-connect segment port.
Segment 1 Status	Status of the first cross-connect segment, such as Admin Up, Admin Down, Oper Down, or Up.
Segment 2	Identifier of the second cross-connect segment, hyperlinked to the relevant entry in physical inventory.
Segment 2 Port Name	Identifier of the second cross-connect segment port.
Segment 2 Status	Status of the second cross-connect segment, such as Admin Up, Admin Down, Oper Down, or Up.
PW Switching Table
Key	Entry key for the pseudowire.
Entry Status	Status of the pseudowire: Down, Unresolved, or Up.
Segment 1	Identifier of the first segment, hyperlinked to the relevant entry in the Pseudowires Tunnel Edges table in logical inventory.
Segment 1 Port Name	Identifier of the first segment port.
Segment 1 Status	Status of the first segment, such as Admin Up, Admin Down, Oper Down, or Up.
Segment 2	Identifier of the second segment, hyperlinked to the relevant entry in the Pseudowires Tunnel Edges table in logical inventory.
Segment 2 Port Name	Identifier of the second segment port.
Segment 2 Status	Status of the second segment, such as Admin Up, Admin Down, Oper Down, or Up.

---

Working with VPLS and H-VPLS Instances

Virtual Private LAN Service (VPLS) is a Layer 2 VPN technology that provides Ethernet-based multipoint-to-multipoint communication over MPLS networks. VPLS allows geographically dispersed sites to share an Ethernet broadcast domain by connecting sites through pseudowires. The network emulates a LAN switch or bridge by connecting customer LAN segments to create a single bridged Ethernet LAN.

Hierarchical VPLS (H-VPLS) partitions the network into several edge domains that are interconnected using an MPLS core. The edge devices learn only of their local n-PE devices and therefore do not need large routing table support. The H-VPLS architecture provides a flexible architectural model that enables Ethernet multipoint and point-to-point Layer 2 VPN services, as well as Ethernet access to Layer 3 VPN services, enabling service providers to offer multiple services across a single high-speed architecture.

Cisco ANA discovers the following VPLS-related information from the network and constructs VPLS instances:

•VSIs

•Pseudowires

•Switching entities

•EFPs

By using the identified VPLS instances, you can:

•Add VPLS instances to a map—See Adding VPLS Instances to a Map.

•Apply VPLS overlays—See Using VPLS Instance Overlays.

•View link details in VPLS overlays—See Viewing Pseudowire Tunnel Links in VPLS Overlays.

•View VPLS-related properties—See Viewing VPLS-Related Properties.

•View VPLS instance properties—See Viewing VPLS Instance Properties.

You can delete a VPLS forward from Cisco ANA if it is displayed with the reconciliation icon.

Adding VPLS Instances to a Map

You can add the VPLS instances that Cisco ANA discovers to maps as required.

To add a VPLS instance to a map:

---

Step 1 In Cisco ANA NetworkVision, select the required map or domain.

Step 2 Open the Add VPLS Instance to map dialog box in either of the following ways:

•In the toolbar, choose Add to Map > VPLS.

•In the menu bar, choose File > Add to Map > VPLS.

Step 3 In the Add VPLS Instance dialog box, do either of the following:

•To search for specific elements:

a. Choose Search.

b. To narrow the display to a range of VPLS instances or a group of VPLS instances, enter a search string in the search field.

c. Click Go.

For example, if you enter VPLS1, the VPLS instances that have names containing the string VPLS1 are displayed.

•To view all available VPLS instances, choose Show All and click Go.

The VPLS instances that meet the specified search criteria are displayed in the Add VPLS Instance dialog box in table format. The dialog box also displays the date and time at which the list was generated. To update the list, click Refresh.

---

Note If an element is not included in your scope, it is displayed with the locked device icon.

---

For information about sorting and filtering the table contents, see Working with Cisco ANA Tables, page 2-40.

Step 4 In the Add VPLS Instance dialog box, select the instances that you want to add. You can select and add multiple instances by pressing Ctrl while selecting individual instances or by pressing Ctrl +Shift to select a group of instances.

Step 5 Click OK.

The VPLS instance is displayed in the navigation pane and in the content area. In addition, any associated tickets are displayed in the ticket pane. See Figure 12-47.

Figure 12-47 VPLS Instance in Cisco ANA NetworkVision Map

---

The VPLS instance information is saved with the map in the Cisco ANA database.

Using VPLS Instance Overlays

An VPLS instance overlay allows you to isolate the parts of a network that are being used by a specific VPLS instance.

To apply a VPLS instance overlay:

---

Step 1 In Cisco ANA NetworkVision, choose the map in which you want to apply an overlay.

Step 2 From the toolbar, choose Choose Overlay Type > VPLS.

Figure 12-48 shows an example of the Select VPLS Instance Overlay for map dialog box.

Figure 12-48 Select VPLS Instance Overlay Dialog Box

Step 3 Select the required VPLS instance for the overlay.

Step 4 Click OK.

The elements being used by the selected VPLS instance are highlighted in the map while the other elements are dimmed, as shown in Figure 12-49.

Figure 12-49 VPLS Instance Overlay in Cisco ANA NetworkVision

Step 5 To hide and view the overlay, click Hide Overlay/Show Overlay in the toolbar. The button toggles depending on whether the overlay is currently displayed or hidden.

Step 6 To remove the overlay, choose Choose Overlay Type > None.

---

Viewing Pseudowire Tunnel Links in VPLS Overlays

When a VPLS overlay is applied to a map in Cisco ANA NetworkVision, you can view the details of the pseudowires that are interconnected through selected links.

To view unidirectional or bidirectional pseudowire traffic links when a VPLS overlay is applied to a map:

---

Step 1 Right-click the required link in the overlay, and choose Show Callouts. The link must be visible (not dimmed) in the map.

Link information is displayed as shown in Figure 12-50.

Figure 12-50 Link Callout Window for a VPLS Overlay

The callout window displays the following information for each link represented by the selected link:

•Link details and direction.

•Details of the sites using the link and the interlinks.

Step 2 To view the pseudowire link details, double-click the yellow callout window.

The details about the link are displayed in the Link Details window as shown in Figure 12-51.

Figure 12-51 Link Details Window for a VPLS Overlay

The Link Details window provides the following information:

1	Link details and direction. In this example, the link is from p3 to c7-npe1-76.
3	Link details and direction. In this example, the link is from c7-npe1-76 to p3.
2 and 4	Details of the pseudowire tunnel traversing this link.

Step 3 Click OK to close the Link Details window.

Step 4 To close the link callout window, right-click the selected link, then choose Hide Callouts.

---

Viewing VPLS-Related Properties

Cisco ANA NetworkVision enables you to view the properties of the following VPLS-related elements:

•VPLS instances—See Viewing VPLS Instance Properties.

•Tunnels—See Viewing VPLS Core or Access Pseudowire Endpoint Properties.

•Port connectors—See Viewing VPLS Access Ethernet Flow Point Properties.

Viewing VPLS Instance Properties

To view the properties of a VPLS instance in Cisco ANA NetworkVision, open the VPLS Instance Properties window in either of the following ways:

•In the navigation pane or the map pane, right-click the VPLS instance and choose Properties.

•In the navigation pane or the map pane, select the VPLS instance and choose Node > Properties.

Figure 12-52 shows an example of the VPLS Instance Properties window.

Figure 12-52 VPLS Instance Properties Window

Table 12-32 describes the information that is displayed for VPLS instance properties.

The tabs that appear in the window depend on the VPLS instance and its configuration.

Table 12-32 VPLS Instance Properties 

Field	Description
System Name	Name that Cisco ANA assigns to the VPLS instance.
Name	User-defined name of the VPLS instance. When the VPLS instance is created, the system name and this name are the same. If you change the name of the VPLS instance (right-click, then choose Rename), the changed name appears in this field whereas the system name retains the original name.
VPN ID	VPN identifier used in an MPLS network to distinguish between different VPLS traffic.
VPLS Forwards Tab
Name	User-defined name of the VPLS forward.
System Name	Name that Cisco ANA assigns to the VPLS forward.
Bridge	Bridge that the VSI is configured to use, hyperlinked to the bridge table in logical inventory.
VSI	VSI hyperlinked to the relevant entry in logical inventory.
VPN ID	VPN identifier for the VSI.
Access Pseudowires Tab
Name	Pseudowire name.
Port	VSI on which the pseudowire is configured, hyperlinked to the entry in logical inventory.
Local Router IP	Local router IP address on which the pseudowire is configured.
Tunnel ID	Virtual circuit identifier of the pseudowire.
PTP Tunnel	Hyperlinked entry to the pseudowire properties in logical inventory.
Peer Router IP	Peer router IP address on which the pseudowire is configured.
Peer OID	Hyperlinked entry to the pseudowire properties of the peer.
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.
Pseudowire Edge Binding Type	Pseudowire endpoint association: •0—Unknown •1—Connection termination point •2—Ethernet flow point •3—Switching entity •4—Pseudowire switching entity •5—VPLS forward
Access Flow Points Tab
Name	Access flow point name. Double-click to view port connector properties.
Port	Interface configured as a flow point, hyperlinked to the interface in physical inventory.

Working with Pseudowires and Pseudowire Overlays

Cisco ANA supports the discovery and modeling of Any Transport over MPLS (AToM) and Ethernet over MPLS (EoMPLS) domains that span multisegment pseudowires. This support enables you to:

•Add discovered pseudowires to a map—See Adding Pseudowires to a Map.

•Ping a pseudowire—See Pinging a Pseudowire.

•View information about pseudowires—See Displaying Pseudowire Information.

•Apply pseudowire overlays—See Applying Pseudowire Overlays.

•View multisegment pseudowire properties—See Viewing Pseudowire Properties.

Adding Pseudowires to a Map

You can add a pseudowire that Cisco ANA discovers to maps as required.

To add a pseudowire to a map:

---

Step 1 In Cisco ANA NetworkVision, select the required map or domain.

Step 2 Open the Add Pseudowire to map dialog box in either of the following ways:

•In the toolbar, choose Add to Map > Pseudowire.

•In the menu bar, choose File > Add to Map > Pseudowire.

Figure 12-53 shows an example of the Add Pseudowire dialog box.

Figure 12-53 Add Pseudowire Dialog Box

Step 3 In the Add Pseudowire dialog box, do either of the following:

•To search for specific elements:

a. Choose Search.

b. To narrow the display to a range of pseudowire or a group of pseudowires, enter a search string in the search field.

c. Click Go.

For example, if you enter pseudo1, the pseudowires that have names containing the string "pseudo1" are displayed.

•To view all available pseudowires, choose Show All and click Go.

The pseudowires that meet the specified search criteria are displayed in the Add Pseudowire dialog box in table format. The dialog box also displays the date and time at which the list was generated. To update the list, click Refresh.

---

Note If an element is not included in your scope, it is displayed with the locked device icon.

---

For information about sorting and filtering the table contents, see Working with Cisco ANA Tables, page 2-40.

Step 4 In the Add Pseudowire dialog box, select the pseudowires that you want to add. You can select and add multiple pseudowires by pressing Ctrl while selecting individual pseudowires or by pressing Ctrl +Shift to select a group of pseudowires.

Step 5 Click OK.

The pseudowire is displayed in the navigation pane and in the content area. In addition, any associated tickets are displayed in the ticket pane. See Figure 12-54.

Figure 12-54 Pseudowire in Cisco ANA NetworkVision Map

Step 6 Click the pseudowire in the navigation pane or double-click the pseudowire in the map pane to view the pseudowire components, such as pseudowire endpoints, pseudowire switching entities, and terminating interfaces.

Figure 12-55 shows an example of an expanded pseudowire in Cisco ANA NetworkVision.

Figure 12-55 Pseudowire Components in Cisco ANA NetworkVision Maps

---

The pseudowire information is saved with the map in the Cisco ANA database.

Pinging a Pseudowire

Cisco ANA enables you to ping a peer router to ensure that the pseudowire tunnel is available.

To ping a pseudowire peer router:

---

Step 1 In the require map, double-click the required device configured for pseudowire.

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

Step 3 In the Tunnel Edges table, select the interface with the peer edge that you want to ping, and make sure that the tunnel status is up.

Step 4 Right-click the interface and choose Commands > Configure > Ping Pseudowire as shown in Figure 12-56.

Figure 12-56 Ping Pseudowire Command

The Ping Pseudowire dialog box is displayed with the General tab as shown in Figure 12-57.

Figure 12-57 Ping Pseudowire Dialog Box - General Tab

Step 5 In the General tab, specify the destination as follows:

•Ping with default Destination IP and VC-ID—Check this check box to ping the selected peer pseudowire endpoint using the default destination IP address and VC identifier. You do not need to enter a destination IP address or tunnel identifier if you choose this option.

•Destination IP Address—Enter the required destination IP address if you do not want to use the default destination IP address. If you enter a destination IP address, you must enter the tunnel identifier in the VC-ID field.

•VC-ID—Enter the required tunnel identifier if you do not want to use the default VC identifier. If you enter a tunnel identifier, you must enter the destination IP address in the Destination IP Address field.

Step 6 To preview the command to ensure it is right, click Preview.

The command is displayed in the Result tab for your review.

Step 7 To execute the command, click Execute.

The result of the command is displayed in the Result tab, as shown in Figure 12-58.

Figure 12-58 Ping Pseudowire Dialog Box - Result Tab

Step 8 Click Close to close the Ping Pseudowire dialog box.

---

Displaying Pseudowire Information

To view Virtual Circuit Connectivity Verification (VCCV) and Control Channel (CC) information for a pseudowire endpoint:

---

Step 1 In the require map, double-click the required device configured for pseudowire.

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

Step 3 In the Tunnel Edges table, right-click the required interface and choose Commands > Show > Display Pseudowire.

Step 4 In the Display Pseudowire dialog box, do either of the following:

•To view the command before running it, click Preview.

•To run the command, click Execute.

When you click Execute, the results are displayed in the dialog box as shown in Figure 12-59.

Figure 12-59 Display Pseudowire Dialog Box

Step 5 The following information is displayed:

•The element name.

•The command issued.

•The results, including:

–VCCV: CC Type—The types of CC processing that are supported. The number indicates the position of the bit that was set in the received octet. The available values are:

- CW [1]—Control Word

- RA [2]—Router Alert

- TTL [3]—Time to Live

- Unkn [x]—Unknown

–Elapsed time—The elapsed time, in seconds.

Step 6 Click Close to close the Display Pseudowire dialog box.

---

Applying Pseudowire Overlays

A pseudowire overlay allows you to isolate the parts of a network that are being used by a specific pseudowire.

To apply a pseudowire overlay:

---

Step 1 In Cisco ANA NetworkVision, choose the map in which you want to apply an overlay.

Step 2 From the toolbar, choose Choose Overlay Type > Pseudowire.

Figure 12-60 shows an example of the Select Pseudowire Overlay for map dialog box.

Figure 12-60 Select Pseudowire Overlay Dialog Box

Step 3 Select the required pseudowire for the overlay.

Step 4 Click OK.

The elements being used by the selected pseudowire are highlighted in the map while the other elements are dimmed, as shown in Figure 12-61.

Figure 12-61 Pseudowire Overlay in Cisco ANA NetworkVision

Step 5 To hide and view the overlay, click Hide Overlay/Show Overlay in the toolbar. The button toggles depending on whether the overlay is currently displayed or hidden.

Step 6 To remove the overlay, choose Choose Overlay Type > None.

---

Viewing Pseudowire Properties

To view pseudowire properties:

---

Step 1 In Cisco ANA NetworkVision, select the required map or domain.

Step 2 To view pseudowire endpoint properties configured on an element:

a. In the navigation or map pane, right-click the required element and then choose Inventory.

b. In the inventory window, choose Logical Inventory > Pseudowires.

The Tunnel Edges table is displayed, listing the pseudowire endpoints configured on the selected element. For a description of the information contained in the Tunnel Edges table, see Table 17-15 on page 17-36.

Step 3 To view the properties of a pseudowire that you added to a map, right-click the element, and then choose Properties.

The Pseudowire Properties window is displayed as shown in Figure 12-62.

Figure 12-62 Pseudowire Properties Window

Table 12-33 describes the information presented in the Pseudowire Properties window.

Table 12-33 Pseudowire Properties Window 

Field	Description
Name	Name of the pseudowire.
Multisegment Pseudowire	Whether or not the pseudowire is multisegment: True or False.
System Name	Internal or system-generated name of the pseudowire.
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.

Step 4 To view the properties of a pseudowire endpoint associated with a pseudowire, right-click the required pseudowire endpoint, and then choose Properties.

The Tunnel Properties window containing the pseudowire endpoint properties is displayed as shown in Figure 12-15 and described in Table 12-16.

Step 5 To view the properties of a pseudowire switching entity associated with the pseudowire, select the switching entity, and then choose Node > Inventory.

The PW Switching table is displayed as shown in Figure 12-63.

Figure 12-63 PW Switching Table in Logical Inventory

Table 12-34 describes the information displayed in the PW Switching table.

Table 12-34 PW Switching Table in Logical Inventory 

Field	Description
Key	Entry key for the pseudowire.
Entry Status	Status of the pseudowire: Down, Unresolved, or Up.
Segment 1	Identifier of the first segment, hyperlinked to the relevant entry in the Pseudowires Tunnel Edges table in logical inventory.
Segment 1 Port Name	Identifier of the first segment port.
Segment 1 Status	Status of the first segment, such as Admin Up, Admin Down, Oper Down, or Up.
Segment 2	Identifier of the second segment, hyperlinked to the relevant entry in the Pseudowires Tunnel Edges table in logical inventory.
Segment 2 Port Name	Identifier of the second segment port.
Segment 2 Status	Status of the second segment, such as Admin Up, Admin Down, Oper Down, or Up.

Step 6 To view the properties of the pseudowire endpoint that terminates on the subinterface, right-click the required interface, and then choose Properties.

The Contained Current CTPs table is displayed as shown in Figure 12-64.

---

Note The selected port must be an Ethernet subinterface for the Contained Current CTPs table to be displayed.

---

Figure 12-64 Contained Current CTPs Table

Table 12-35 describes the information displayed in the Contained Current CTPs table.

Table 12-35 Contained Current CTPs Table 

Field	Description
Local Interface	The name of the subinterface or port, hyperlinked to the interface in physical inventory.
ID	The tunnel identifier, hyperlinked to Pseudowires Tunnel Edges table in logical inventory.
Peer	The peer tunnel identifier, 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 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 router identifier.
Peer Router IP	The IP address of the peer tunnel edge, which is used as the router identifier.
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 to build the tunnel, such as LDP or TDP.
Preferred Path Tunnel	The path to be used for pseudowire traffic.

Step 7 To view the properties of an Ethernet flow point associated with the pseudowire, right-click the EFP and then choose Properties.

See Viewing EFP Properties for the information that is displayed for EFPs.

---

Working with Ethernet Services

Ethernet services are created when the following business elements are linked to one another:

•Network VLAN and bridge domain are linked through a shared EFP.

•Network VLAN and VPLS instance are linked through either of the following:

–A shared, standalone EFP.

–A shared switching entity.

•Network VLAN and network pseudowire (either single or multi-segment) are linked through either of the following:

–A shared, standalone EFP.

–A shared switching entity.

•VPLS-EoMPLS connected via a shared Access pseudowire endpoint.

•Network VLAN and cross-connect connected by a shared EFP.

•Network VLAN and service link connected by a shared EFP.

If a VPLS, network pseudowire, cross-connect, or network VLAN object is not connected to another business element, it resides alone in an Ethernet service.

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

Cisco ANA discovers Ethernet services and enables you to add them to maps, apply overlays, and view their properties. See the following topics for more information:

•Adding Ethernet Services to a Map

•Using Ethernet Service Overlays

•Viewing Ethernet Service Properties

Adding Ethernet Services to a Map

You can add the Ethernet services that Cisco ANA discovers to maps as required.

To add an Ethernet service to a map:

---

Step 1 In Cisco ANA NetworkVision, select the required map or domain.

Step 2 Open the Add Ethernet Service to map dialog box in either of the following ways:

•In the toolbar, choose Add to Map > Ethernet Service.

•In the menu bar, choose File > Add to Map > Ethernet Service.

Step 3 In the Add Ethernet Service dialog box, do either of the following:

•To search for specific elements:

a. Choose Search, and then choose a search category: EVC Terminating EFPs, Name, or System Name.

b. To narrow the display to a range of Ethernet services or a group of Ethernet services, enter a search string in the search field.

c. Click Go.

For example, if you choose Name and enter EFP1, the network elements that have names beginning with EFP1 are displayed.

•To view all available Ethernet services, choose Show All and click Go.

The available elements that meet the specified search criteria are displayed in the Add Ethernet Service dialog box in table format. The dialog box also displays the date and time at which the list was generated. To update the list, click Refresh.

---

Note If an element is not included in your scope, it is displayed with the locked device icon.

---

For information about sorting and filtering the table contents, see Working with Cisco ANA Tables, page 2-40.

Step 4 In the Add Ethernet Service dialog box, select the elements that you want to add. You can select and add multiple elements by pressing Ctrl while selecting individual elements or by pressing Ctrl +Shift to select a group of elements.

Step 5 Click OK.

The Ethernet service is displayed in the navigation pane and in the content area. In addition, any associated tickets are displayed in the ticket pane. See Figure 12-65.

Figure 12-65 Ethernet Service in Cisco ANA NetworkVision Map

---

The Ethernet service information is saved with the map in the Cisco ANA database.

Using Ethernet Service Overlays

An Ethernet service overlay allows you to isolate the parts of a network that are being used by a specific Ethernet service.

To apply an Ethernet service overlay:

---

Step 1 In Cisco ANA NetworkVision, choose the map in which you want to apply an overlay.

Step 2 From the toolbar, choose Choose Overlay Type > Ethernet Service.

Figure 12-66 shows an example of the Select Ethernet Service Overlay for map dialog box.

Figure 12-66 Select Ethernet Service Overlay Dialog Box

Step 3 Select the required Ethernet Service for the overlay.

Step 4 Click OK.

The elements being used by the selected Ethernet service are highlighted in the map while the other elements are dimmed, as shown in Figure 12-67.

Figure 12-67 Ethernet Service Overlay in Cisco ANA NetworkVision

Step 5 To hide and view the overlay, click Hide Overlay/Show Overlay in the toolbar. The button toggles depending on whether the overlay is currently displayed or hidden.

Step 6 To remove the overlay, choose Choose Overlay Type > None.

---

Viewing Ethernet Service Properties

To view Ethernet service properties:

---

Step 1 In Cisco ANA NetworkVision, select the map containing the required Ethernet service.

Step 2 In the navigation or map pane, right-click the Ethernet service and choose Properties.

Figure 12-68 shows an example of an Ethernet Service Properties window.

Figure 12-68 Ethernet Service Properties Window

Table 12-36 describes the information that is displayed for an Ethernet service.

Table 12-36 Ethernet Service Properties Window 

Field	Description
Name	Ethernet service name.
System Name	Name of the system associated with the Ethernet service.
EVC	Name of the EVC associated with the Ethernet service, hyperlinked to the EVC Properties window.
EVC Terminating Table
Name	EVC name, represented by the interface name, EFP, and the EFP name.
Network Element	Hyperlinked entry to the specific interface and EFP in physical inventory.
Port	Hyperlinked entry to the specific interface in physical inventory.

Step 3 To view the EVC Properties window, click the hyperlink in the EVC field.

Figure 12-69 shows an example of the EVC Properties window.

Figure 12-69 EVC Properties Window

Table 12-37 describes the information that is displayed in the EVC Properties window. The tabs that are displayed in the window depend on the EVC links.

Table 12-37 EVC Properties Window 

Field	Description
System Name	Name of the system on which the EVC is configured.
Name	EVC name.
Network VLANs Tab
Name	VLAN name.
ID	VLAN identifier.
Ethernet Flow Domain	Name of the Ethernet flow domain.
System Name	VLAN system name.
Description	Brief description of the VLAN.
Network Pseudowires Tab
Name	Pseudowire name.
System Name	System on which the pseudowire is configured.
Description	Brief description of the pseudowire.
Pseudowire Type	Type of pseudowire. For a complete list of pseudowire types, see the Cisco Active Network Abstraction 3.7.1 Theory of Operations Guide.
Is Multisegment Pseudowire	Whether or not the pseudowire is multisegment: True or False.
VPLS Instances Tab
Name	VPLS name.
System Defined Name	VPLS system name.
VPN ID	Identifier of associated VPN.

---

Viewing IP SLA Responder Service Properties

Cisco IOS Service Level Agreements (SLAs) software allows you to analyze IP service levels for IP applications and services by using active traffic monitoring to measure network performance.

The IP SLA responder is a component embedded in the destination Cisco device that allows the system to anticipate and respond to IP SLAs request packets. The responder provides accurate measurements without requiring dedicated probes. The responder uses the Cisco IOS IP SLAs Control Protocol to provide a mechanism through which it can be notified on which port it should listen and respond.

Two-Way Active Measurement Protocol (TWAMP) defines a standard for measuring round-trip network performance between any two devices that support the protocol.

In Cisco ANA 3.7.1, IP SLA Responder service is supported on the following devices:

•Cisco 3400ME and 3750ME devices running Cisco IOS 12.2(52)SE.

•Cisco MWR2941 devices running Cisco CSR 3.2.

To view IP SLA Responder service properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the device configured for IP SLA Responder service.

Step 2 In the inventory window, choose Logical Inventory > IP SLA Responder.

IP SLA Responder properties are displayed as shown in Figure 12-70.

Figure 12-70 IP SLA Responder in Logical Inventory

Table 12-38 describes the properties displayed for IP SLA Responder service.

Table 12-38 IP SLA Responder Properties in Logical Inventory 

Field	Description
IP SLA Responder Status	Status of the IP SLA Responder: Up or Down.
IP SLA TWAMP Responder Status	Status of the IP SLA TWAMP responder: Up or Down.
UDP Echo Tab
IP Address	Destination IP address used for the UDP echo operation.
Port Number	Destination port number used for the UDP echo operation.
TCP Connect Tab
IP Address	Destination IP address used for the TCP connect operation.
Port Number	Destination port number used for the TCP connect operation.

---

Viewing IS-IS Properties

Intermediate System-to-Intermediate System (IS-IS) protocol is a routing protocol developed by the ISO. It is a link-state protocol where IS routers exchange routing information based on a single metric to determine network topology. It behaves in a manner similar to OSPF in the TCP/IP network.

IS-IS networks contain end systems, intermediate systems, areas, and domains. End systems are user devices. Intermediate systems are routers. Routers are organized into local groups called areas, and areas are grouped into a domain.

To view IS-IS properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the device configured for IS-IS.

Step 2 In the inventory window, choose Logical Inventory > IS-IS > System.

Figure 12-71 shows an example of the ISIS window with the Process table in logical inventory.

Figure 12-71 ISIS Window in Logical Inventory

Table 12-39 describes the information that is displayed in this window and the Processes table.

Table 12-39 IS-IS Properties in Logical Inventory - Processes Table 

Field	Description
Version	Version of IS-IS that is implemented.
Processes Table
Process ID	Identifier for the IS-IS process.
System ID	Identifier for this Intermediate System.
IS Type	Level at which the Intermediate System is running: Level 1, Level 2, or Level 1-2.
Manual Area Address	Address assigned to the area.

Step 3 To view IS-IS process information, choose Logical Inventory > IS-IS > Process nnn.

Figure 12-72 shows an example of the information that is displayed for the IS-IS process.

Figure 12-72 IS-IS Process Properties in Logical Inventory

Table 12-40 describes the information that is displayed for the selected IS-IS process.

Table 12-40 IS-IS Process Properties in Logical Inventory 

Field	Description
Process	Unique identifier for the IS-IS process.
System ID	Identifier for this Intermediate System.
IS Type	Level at which the Intermediate System process is running: Level 1, Level 2, or Level 1-2.
Manual Area Address	Address assigned to the area.
Metrics Tab
IS Type	Level at which the Intermediate System is running: Level 1, Level 2, or Level 1-2.
Metric Style	Metric style used: Narrow, Transient, or Wide.
Metric Value	Metric value assigned to the link. This value is used to calculate the path cost via the links to destinations. This value is available for Level 1 or Level 2 routing only. If the metric style is Wide, the value can range from 1 to 16777214. If the metric style is Narrow, the value can range from 1 to 63. The default value for active IS-IS interfaces is 10, and the default value for inactive IS-IS interfaces is 0.
Address Family	IP address type used: IPv4 or IPv6.
Interfaces Tab
Interface Name	Interface name.
Neighbors Tab
System ID	Identifier for the neighbor system.
Interface	Neighbor interface name.
IP Address	Neighbor IP address.
Type	IS type for the neighbor: Level 1, Level 2, or Level 1-2.
SNPA	Subnetwork point of attachment (SNPA) for the neighbor.
Hold Time	Holding time, in seconds, for this adjacency. The value is based on received IS-to-IS Hello (IIH) PDUs and the elapsed time since receipt.
State	Administrative status of the neighbor system: Up or Down.
Address Family	IP address type used by the neighbor: IPv4 or IPv6.

---

Viewing OSPF Properties

Cisco ANA supports the following versions of OSPF:

•OSPFv1

•OSPFv2

•OSPFv3

Using Cisco ANA NetworkVision you can view OSPF properties for:

•OSPF processes, including the process ID and OSPF version.

•OSPF network interfaces, such as the area ID, network type, and status.

•OSPF neighbors, including the neighbor ID, neighbor interface address, and status.

To view OSPF properties:

---

Step 1 In Cisco ANA NetworkVision, double-click the device configured for OSPF.

Step 2 To view OSPF processes, choose Logical Inventory > OSPF Processes > OSPF Process (vn) ID where vn represents the OSPF version and ID is the OSPF process identifier.

For example, in Figure 12-73, the entry in the navigation tree is OSPF Process (v2) 1.

Figure 12-73 OSPF Processes in Logical Inventory

Table 12-41 describes the information that is displayed for OSPF processes.

Table 12-41 OSPF Processes in Logical Inventory 

Field	Description
OSPF Process Details
Process ID	Unique process identifier.
Router ID	Router IP address.
OSPF Version	OSPF version: v1, v2, or v3.
SPF Timers
Schedule Delay	Number of milliseconds to wait after a change before performing the shortest path first (SPF) calculation.
Min Hold Time	Minimum number of milliseconds to wait between two consecutive SPF calculations.
Max Wait Time	Maximum number of milliseconds to wait between two consecutive SPF calculations.
OSPF Neighbors Table
Neighbor ID	OSPF neighbor IP address
Area	OSPF area identifier.
Interface Address	IP address of the interface on the neighbor configured for OSPF.
State	State of the communication with the neighbor: Down, Attempt, Init, 2-Way, Exstart, Exchange, Loading, and Full.
OSPF Interface	Hyperlinked entry to the OSPF Interface Properties window. The OSPF Interfaces window displays the same information as in the OSPF Interfaces Table below.
Sending Alarms	Status of sending alarms on the interface: True or False.
OSPF Interfaces Table
IP Interface	OSPF interface, hyperlinked to relevant entry in the routing entity IP Interfaces table in logical inventory. For more information about the IP Interfaces table, see Table 17-6.
Internet Address	OSPF interface IP address.
Area ID	OSPF area identifier.
Priority	Eight-bit unsigned integer that specifies the priority of the interface. Values range from 0 to 255. Of two routers, the one with the higher priority takes precedence.
Cost	Specified cost of sending a packet on the interface, expressed as a metric. Values range from 1 to 65535.
Status	State of the interface: Up or Down.
State	OSPF state: BDR, DR, DR-Other, Waiting, Point-to-Point, or Point-to-Multipoint.
Network Type	Type of OSPF network: Broadcast, Nonbroadcast Multiple Access (NBMA), Point-to-Multipoint, Point-to-Point, or Loopback.
DR Address	Designated router IP address.
BDR Address	Backup designated router IP address.
Sending Alarms	Status of sending alarms on the interface: True or False.

---