Cisco Prime Nerk 43 User Guide

							  
18-47
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Monitoring PBB-based Support Service Discovery
Monitoring PBB-based Support Service Discovery
The Cisco Prime Network delivers PBB-based discovery for various support services over VLAN, 
VPLS, EVC, and pseudowires. 
The Cisco Prime Network supports the following service discoveries:
VLAN Discovery—Discovers bridges domains such as I-Bridges, B-Bridges, and regular bridges 
that are unassociated. 
VPLS Discovery—Discovers VFIs and their associations between I-Bridges and B-Bridges.
Pseudowire Discovery—Discovers pseudowires and their associations between I-Bridges and 
B-Bridges.
EVC Discovery—Creates an end-to-end complex circuit representing the network associations in 
the core network of the above discovered elements.
The PBB specified by IEEE 802.1ah-2008, provides 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. The PBB network interconnects multiple 
provider bridge networks without losing each customer’s individual VLANs.
The Prime Network PBB-based support service discovery recognizes service entities in the network. 
Service discovery are either network data discovered by Prime Network VNEs or other underlying 
services discovered by other service discoveries. The network data is stored and cached (in memory) in 
Snapshots on the Prime Network gateway machine. After which, the data is transformed into service 
data, and then stored in the Prime Network database.
The Prime Network PBB-based support services can be discovered either by using a full discovery mode 
or a notification-based discovery mode.
The Prime Network supports the following PBB-based support services:
PBB-based VLAN Discovery, page 18-47
PBB-based EVC Discovery, page 18-48
Discovering PBB-links Between I-Bridge and B-Bridge, page 18-49
PBB-based Pseudowire Discovery, page 18-49
PBB-based VPLS Discovery, page 18-50
PBB-based VLAN Discovery
Prime Network discovers and allows you to display maps with a network-level view of VLANs.
A VLAN entity consists of one or more bridges and the corresponding EFP elements. When the VLAN 
discovery is initiated, it identifies VLANs that are considered as part of a switching entity. 
Associated and Unassociated Bridges
Generally, all the bridges are categorized as associated or unassociated based on their association with 
the type of switching entities such as pseudowire and VPLS. In the Provider Backbone configuration, 
the VLANs identified by VLAN discovery are considered as a part of associated bridges and the VLANs 
that are not identified are considered as a part of unassociated bridges. For example, if a regular bridge  
						

							  
18-48
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Monitoring PBB-based Support Service Discovery
is associated with a pseudowire or a VPLS, then it is classified as an associated bridge. Otherwise, it is 
classified as an unassociated bridge. However, the I-Bridges and B-Bridges are always considered as a 
part of unassociated bridges irrespective of their association with the switching entities.
Discovering Unassociated Domains
To discover the VLAN service configured in a network, a component called VLAN data plug-in collects 
information related to VLAN from various devices. The data plug-in holds all the data related to the 
bridges in a centralized location. To discover an unassociated bridge, for example, an I-bridge or a 
B-bridge, it is essential to verify whether the plug-in has information related to the I-bridge or the 
B-bridge, or any other additional I-bridge PBB information. To verify, see Verifying Bridge domains, 
page 18-48. Based on the information collected, a discovery plug-in is created, and the plug-in receives 
the necessary data from the VLAN plug-in to create the VLAN instances. 
Verifying Bridge domains
To verify the bridge domains, follow the steps provided below:
Step 1Create a new map in the Vision client. For example, VLAN. 
Step 2Add bridges to the map.
Step 3Right-click one of the bridges and choose Inventory. 
Step 4Verify the bridge type in the Inventory window.
Step 5Open the Add Bridge Domain dialog box in one of the following ways:
Choose File Add to Map > Bridge Domain.
In the toolbar, click Add to Map and choose Bridge Domain.
Step 6In the Add Bridge Domain dialog box, select Show All to display the list of bridge domains. 
Step 7Verify whether the bridge that you identified in the Inventory window is listed in the Bridge Domain list.
NoteThe bridges of type I-Bridges or B-Bridges are considered as the bridge domains. These I-Bridges or 
B-Bridges are added in the Bridge Domain list.
PBB-based EVC Discovery
PBB-based EVC discovery is dependent on the following discovery processes:
VPLS Discovery
Network VLAN Discovery
Network Pseudowire Discovery
Bridge Domain Discovery
EVC discovery plug-in is responsible for handling Carrier Ethernet technologies such as VPLS, VLAN, 
bridge domains, cross connect, and pseudowires. This plug-in connects all the domains together in a map 
from the Vision client.
For more information on the Ethernet services, refer to Working with Ethernet Services in the Cisco 
Prime Network 4.3.2 User Guide. 
						

							  
18-49
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Monitoring PBB-based Support Service Discovery
PBB-based EVC Multiplexing
Every EVC should be created with the following rules:
Every network element, for example, I-Bridge, B-Bridge, pseudowire, or VPLS that is discovered 
in the inventory should definitely be part of at least one EVC.
If a network element is associated with the I-Bridge, EVC is created for each I-SID (I-Bridge unique 
identifier).
If no I-Bridges are associated, then the EVC is created based on the association between the 
B-Bridge and VPLS.
EVC creation for regular bridges works in the same way as that of Prime Network 4.3.2.
Prime Network supports EVC multiplexing to create an EVC. EVC creation involves the following 
processes:
Discovers all dependent discoveries such as VLAN, VPLS, or pseudowires.
Notifications for each discovery are received by related processors and the Information Model 
Objects (IMOs) are processed to loaders for creating building blocks based on the associations 
between the network elements.
Segmenter collects building blocks from all the above mentioned discoveries and creates segments 
based on the associations.
Every segment created is processed based on the rules specified above and creates a complex virtual 
circuit.
Discovering PBB-links Between I-Bridge and B-Bridge
The PBB I-Bridge interfaces with the customer edge and the B-bridge interfaces with the core network. 
To discover the link between the I-Bridge and the B-Bridge, follow the steps provided below:
Step 1Create a new map in the Vision client. For example, VLAN. 
Step 2Open the Add Bridge Domain dialog box in one of the following ways:
Choose File Add to Map > Bridge Domain.
In the toolbar, click Add to Map and choose Bridge Domain.
Step 3In the Add Bridge Domain dialog box, select Show All to display the list of bridge domains. 
Step 4From the bridge domains, select an I-Bridge and a B-Bridge and click OK.
Step 5Add the selected bridges to the map. The map displays the PBB links between the newly added bridges.
PBB-based Pseudowire Discovery
A pseudowire is a point-to-point connection between pairs of provider edge (PE) routers. 
Discovering PBB-links Between Pseudowire and I-Bridge/B-Bridge
To discover the link between the pseudowire and the I-Bridge or B-Bridge, follow the steps provided 
below: 
						

							  
18-50
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Monitoring PBB-based Support Service Discovery
Step 1Create a new map in the Vision client. For example, Pseudowire. 
Step 2Open the Add Bridge Domain to domain dialog box in one of the following ways:
Choose File Add to Map > Bridge Domain.
In the toolbar, click Add to Map and choose Bridge Domain.
Step 3In the Add Bridge Domain dialog box, select Show All to display the list of bridge domains. 
Step 4From the bridge domains, select an I-Bridge and a B-Bridge and click OK to add the selected bridges to 
the map.
Step 5Choose Add to Map > Pseudowire to open the Add Pseudowire to map dialog box.
Step 6In the Add Pseudowire to map dialog box, select Show All to display the list of pseudowires.
Step 7Add any pseudowire from the list to the map.
Step 8The map displays the link between the pseudowires and the bridge domains.
PBB-based VPLS Discovery
Prime Network provides Virtual Private LAN Service (VPLS) plug-in to gather VPLS relevant 
information in a network.
The VPLS plug-in gathers VPLS relevant information from all the VNEs, including the VFIs or VSIs, 
to create a VPLS service. A VPLS instance representing the VPLS configuration is created on the 
network. The VPLS snapshot finds out VNEs that are running to retrieve potential VFIs and VSIs. The 
bridge domains that are connected to the VSIs are attached to VPLS instances to create connection 
between the VPLS and the Network VLANs.
Based on data gathered, the VPLS discovery constructs the VPLS instances. This discovery can be 
viewed from the client GUI. A map in the GUI represents VPLS instances in addition to regular VNEs. 
Thereby, the bridges connected to VSI or VFI are discovered and connected. The VPLS container sends 
notifications when an VPLS instance is added, modified, or deleted.
Discovering PBB-links Between VPLS and I-Bridge/B-Bridge
To discover the link between the VPLS and the I-Bridge or B-Bridge, follow the steps provided below:
Step 1Create a new map in the Vision client. For example, VPLS. 
Step 2Open the Add Bridge Domain to domain dialog box in one of the following ways:
Choose File Add to Map > Bridge Domain.
In the toolbar, click Add to Map and choose Bridge Domain.
Step 3In the Add Bridge Domain dialog box, select Show All to display the list of bridge domains. 
Step 4From the bridge domains, select an I-Bridge and a B-Bridge and click OK to add the selected bridges to 
the map.
Step 5Choose Add to Map > VPLS to open the Add Vpls Instance to map dialog box.
Step 6In the Add Vpls Instance to map dialog box, select Show All to display the list of VPLS instances.
Step 7Add a VPLS instance from the VPLS instances list.
The map displays the link between the VPLS instance and bridge domains. 
						

							  
18-51
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Viewing EFP Properties
Viewing EFP Properties
The Vision client provides information about EFPs in a number of ways. For example:
EFP names displayed in Vision client 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 the Vision client 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 1In the Vision client 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.
Figure 18-13 shows an example of the EFP Properties window.
Figure 18-13 EFP Properties Window 
						

							  
18-52
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Viewing EFP Properties
Table 18-26 describes the information displayed in the EFP Properties window. 
Step 2Click the hyperlink entry in the Binding field to view the related properties in logical inventory. 
In this example, clicking the hyperlink displays the relevant bridge in logical inventory, as shown in 
Figure 18-14. 
Figure 18-14 Bridge Associated with EFP in Logical Inventory  Table 18-26 EFP Properties Window
Field Description
EFP ID Identifier for the EFP.
VLAN Match Criteria Match criteria configured on the EFP for forwarding decisions. 
Split Horizon GroupSplit horizon group to which the EFP is associated. 
If no split horizon group is defined, the value is null. 
If only one split horizon group exists and it is enabled for the EFP, the 
value is the default group 0. 
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.  
						

							  
18-53
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Viewing EFP Properties
Table 18-27 describes the information displayed for an EFP associated with a bridge. 
Step 3To view EFP properties in physical inventory, navigate to the required interface in one of the following 
ways: 
In the bridge entry in logical inventory, click the hyperlinked entry in the Binding field. 
Use the procedure described in Viewing and Renaming Ethernet Flow Domains, page 18-60 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 18-15. 
Table 18-27 EFP Associated with a Bridge in Logical Inventory
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.
VSI VSI information, hyperlinked to the VSI entry 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 interface and EFP entry in physical 
inventory. 
Description Description for the EFP. 
						

							  
18-54
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Connecting a Network Element to an EFP
Figure 18-15 EFPs Tab in Physical Inventory
Table 18-28 describes the information displayed in the EFPs tab.
Connecting a Network Element to an EFP
You can add and connect network elements to an EFP under an existing aggregation for VLAN, VPLS, 
Pseudowire, and Ethernet Service. 
To connect network elements to an EFP:
Table 18-28 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.  
						

							  
18-55
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Understanding EFP Severity and Ticket Badges
Step 1Select an EFP node under the VLAN/VPLS/Pseudowire/Ethernet Service aggregation node and choose 
File > Add to Map > Network Element.
Step 2In the Add Network Element dialog box, search for the desired network elements and choose the network 
element that you want to add.
The selected network element appears under the aggregation node in the navigation pane. 
Step 3Right-click the EFP node and choose Topology > Connect CE Device.
Step 4Right-click the network element that you added and choose Topology > Connect to EFP.
The map view displays a link between the EFP and the added network element. If required, you can 
remove the link, by right-clicking the link and choosing Remove Link.
Step 5To hide or show the connected network elements, right-click the EFP node and choose Hide Connected 
Devices or Show CE device.
Understanding EFP Severity and Ticket Badges
Severity and ticket badges are displayed on EFP icons as follows:
If the VLAN EFP element represents a 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 service instance or enhanced port configuration. 
Figure 18-16 shows an example of a ticket badge based on a service instance.
Figure 18-16 EFP Severity and Ticket Badges Based on Underlying Service Instance

If the Ethernet flow point element represents a VLAN interface for a regular switch port, the severity 
and ticket badges are based on the corresponding port, as shown in Figure 18-17.  
						

							  
18-56
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Viewing EVC Service Properties
Figure 18-17 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. For 
information on the devices for which Prime Network discovers and models these key EVC service 
properties, refer to Cisco Prime Network 4.1 Supported VNEs.
Shared Switching Entities and EVC Service View
Some switching entities that the Vision client discovers are concurrently part of a network VLAN and 
VPLS/EoMPLS instance. These switching entities are referred to as shared switching entities. 
The Vision client displays the switching entity information for shared switching entities only under the 
VPLS instances in the EVC service view. 
To view EVC port-related properties for the supported devices and software versions: 
Step 1In the Vision client, double-click the required device. 
Step 2In the Inventory window, choose Physical Inventory > Chassis >module>port. 
Figure 18-18 shows an example of a port in physical inventory configured with these EVC properties.