Cisco Prime Nerk 43 User Guide

							  
18-87
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with VLANs
Step 4When 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 Vision client 
inventory window and choosing Bridges in logical inventory. 
To view VLAN bridge properties:
Step 1In the Vision client, double-click the device containing the VLAN bridges you want to view.
Step 2In the Inventory window, choose Logical Inventory > Bridges >bridge.
VLAN bridge properties are displayed as shown in Figure 18-39.
Figure 18-39 VLAN Bridge Properties in Logical Inventory 
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.
Table 18-40 VTP Properties in Inventory (continued)
Field Description 
						

							  
18-88
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with VLANs
Table 18-41 describes the information that is displayed. Depending on the bridge configuration, any of 
the tabs might be displayed for the selected bridge.
Table 18-41 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.
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 
Ty p eType of encapsulation configured on the VLAN, such as IEEE 802.1Q. 
						

							  
18-89
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with VLANs
Step 3When finished, press Ctrl + F4 to close each VLAN Bridge properties window.
Using Commands to Work With VLANs
The following commands can be launched from the physical inventory by right-clicking an Ethernet slot 
and choosing Commands > Configuration. Your permissions determine whether you can run these 
commands (see Permissions for Managing Carrier Ethernet, page B-12). To find out if a device supports 
these commands, see the Cisco Prime Network 4.3.2 Supported Cisco VNEs.  Allowed VLANs List of the VLANs allowed on this VLAN interface.
VLAN Encapsulation 
Admin TypeVLAN 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.
Sub Interfaces Tab
BER VLAN bit error rate. 
Interface Name Interface on which the VLAN is configured. 
VLAN Type Type of VLAN, such as Bridge or IEEE 802.1Q. 
Operational State Subinterface operational state.
VLAN ID VLAN identifier. 
Inner VLAN CE-VLAN identifier. 
Table 18-41 VLAN Bridge Properties (continued)
Field Description 
						

							  
18-90
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Understanding Unassociated Bridges
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 in the Vision client map. 
Adding Unassociated Bridges
The Vision client enables you to add unassociated bridges to maps and to view their properties. 
To add an unassociated bridge to a map: 
Step 1In the Vision client, select the required map or domain. 
Step 2Open 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 18-40 shows an example of the Add Unassociated Bridge dialog box. 
Table 18-42 VLAN Commands
Command Inputs Required and Notes
Create VLANVLAN ID, VLAN Context Name, Bind Interface Name, Status
Modify VLANVLAN ID, Delete Bind Interface, Context Name, Bind Interface 
Name, Status
Delete VLANVLAN ID 
						

							  
18-91
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Understanding Unassociated Bridges
Figure 18-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 18-41.  
						

							  
18-92
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with Ethernet Flow Point Cross-Connects
Figure 18-41 Unassociated Bridge in the Vision Window
Working with Ethernet Flow Point Cross-Connects
Prime Network automatically discovers Ethernet flow point (EFP) cross-connects, also known as locally 
switched EFPs. Prime Network 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.
Prime Network 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, the Vision client displays the links between them and the cross-connect as well.
The Vision client 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, page 18-92
Viewing EFP Cross-Connect Properties, page 18-93
Adding EFP Cross-Connects
To add an EFP cross-connect to a map:
Step 1In the Vision client, select the map to which you wish to add the cross-connect. 
Step 2Open the Add EFP Cross-Connect dialog box in one of the following ways: 
						

							  
18-93
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with Ethernet Flow Point Cross-Connects
Choose File Add to Map > Cross Connect.
In the toolbar, click Add to Map and choose Cross Connect. 
Step 3In 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. 
Viewing EFP Cross-Connect Properties
To view EFP cross-connect properties in the Vision client, do either of the following: 
Select the EFP cross-connect with the properties you want to view, and choose Node > Properties. 
Double-click the device configured with an EFP cross-connect and, in the inventory window, choose 
Logical Inventory > Local Switching > Local Switching Entity. 
The information that is displayed for EFP cross-connects is the same in both the Local Switching Entry 
Properties window and in the Local Switching Table in logical inventory (as shown in Figure 18-42). 
Figure 18-42 Local Switching Table in Logical Inventory 
Table 18-43 describes the information displayed for the EFP cross-connects in the Local Switching 
Ta b l e .
Table 18-43  EFP Cross-Connect Properties in Local Switching Table
Field Description
Key Entry key for the cross-connect group.
Entry Status Status of the cross-connect: Down, Unresolved, or Up.  
						

							  
18-94
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with VPLS and H-VPLS Instances
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.
Prime Network discovers the following VPLS-related information from the network and constructs 
VPLS instances: 
VSIs
Pseudowires
EFPs
Switching entities
The Vision client enables you to: 
Add VPLS instances to a map—See Adding VPLS Instances to a Map, page 18-95.
Apply VPLS overlays—See Applying VPLS Instance Overlays, page 18-96.
View link details in VPLS overlays—See Viewing Pseudowire Tunnel Links in VPLS Overlays, 
page 18-97.
View VPLS-related properties—See the following topics:
–Viewing VPLS Instance Properties, page 18-99
–Viewing Virtual Switching Instance Properties, page 18-100 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. 
Table 18-43  EFP Cross-Connect Properties in Local Switching Table (continued)
Field Description 
						

							  
18-95
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with VPLS and H-VPLS Instances
–Viewing VPLS Core or Access Pseudowire Endpoint Properties, page 18-102
–Viewing VPLS Access Ethernet Flow Point Properties, page 18-104
Configure VFI Autodiscovery and Signaling—Configuring VFI Autodiscovery and Signaling, 
page 18-105
You can delete a VPLS forward from the Vision client if it is displayed with the reconciliation icon. 
Adding VPLS Instances to a Map
You can add the VPLS instances that Prime Network discovers to maps as required. 
To add a VPLS instance to a map: 
Step 1In the Vision client, select the required map or domain. 
Step 2Open 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 3In 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.
NoteIf 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 Viewing a Table of NEs and Their 
Properties (List View), page 7-7.
Step 4In 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 5Click 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.
The VPLS instance information is saved with the map in the Prime Network database.  
						

							  
18-96
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with VPLS and H-VPLS Instances
Applying 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 1In the Vision client, choose the map in which you want to apply an overlay.
Step 2From the toolbar, choose Choose Overlay Type > VPLS. 
Figure 18-43 shows an example of the Select VPLS Instance Overlay for map dialog box. 
Figure 18-43 Select VPLS Instance Overlay Dialog Box 
Step 3
Select the required VPLS instance for the overlay.
Step 4Click 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 18-44.