Cisco Prime Nerk 43 User Guide

							  
18-27
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Monitoring Provider Backbone Bridges
Monitoring Provider Backbone Bridges
The Provider Backbone Bridge (PBB) 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.
The PBB network comprises of a set of architecture and protocols for routing over a provider’s network. 
The PBB network interconnects multiple provider bridge networks without losing each customer’s 
individual VLANs. The PBB network encapsulates and decapsulates end-user traffic on a Backbone 
Edge Bridge (BEB) at the edge of the Provider Backbone Bridged Network (PBBN). A Backbone Core 
Bridge (BCB)-based network provides internal transport of the IEEE 802.1ah encapsulated frames 
within the PBBN.
Figure 18-12 shows a typical provider backbone network topology.
Figure 18-12 Provider Backbone Network Topology
BFD Templates Support
BFD (Bidirectional Forwarding Detection Templates) are the new features added in CPT devices. Prime 
Network uses Telnet Command to get the BFD templates in existing CPT devices. 
Telnet /CLI Command for listing the BFD template
Ethernet link carrying backbone frames
comprising backbone SA and DA, B-VLAN
tag, I-tag and customer frame
Ethernet link carrying customer frames
comprising optional service VLAN tag and
original octets of data
BEB internal link between
edge BD and backbone BD278091
Backbone
BD
BEB BEB
CECEBackbone
BDEdge
BDBackbone
BDEdge
BD
Backbone
BD
BCB BCB
Provider
Network
Por tProvider
Network
Por t Provider
Network
Por t
Provider
Network
Por tCustomer
Network
Por t Customer
Network
Por tPBBN 
						

							  
18-28
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Monitoring Provider Backbone Bridges
Show running-config|section bfd-template
Cerent Trap Support
Cerent trap alarms are supported for CPT devices. There are 170 traps supported.
Change Settings in CTC (Cisco Transport Controller)
Any configurations settings made in CPT should be done through CTC. To receive traps in a particular 
server, that server IP needs to be entered in the device through CTC.  Most of the traps are on device 
dependencies.
Link and Port Parameters
Configuration of Ethernet loopback is used to add and remove loopback. Link and Port parameters have 
been used for Prime Network configuration scripts in both TLI and Telnet. The link and port parameters 
are supported for the following: Ethernet Parameter Configuration
MTU
Link State
Expected Speed
Expected Duplex
Operating Flow Control
Carrier Delays
Auto Negotiation
Port Parameter Configuration
Port Name
Admin State
AINS Soak
Reach
Wavelength
L2 Parameter Configuration
CDP
DOTIX
DTP
LACP
PA G P
VTP
STP 
						

							  
18-29
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
The following are the configuration scripts supported,
Add Loopback
Remove Loopback
Configure CDP
Configure Ethernet
Configure L2 Control Protocol
Configure Port Parameters
Show Ethernet Parameters
Show L2 Control Parameters
Show Port Parameters
This chapter describes the following topics:
Working with PBB-EVPN, page 18-29
Working with PBB-VPLS, page 18-40
Working with PBB-MMRP, page 18-44
Working with PBB-EVPN
Ethernet Virtual Private Network (EVPN) is a solution for secure and private connectivity of multiple 
sites within an organization. The EVPN service extends the benefits of Ethernet technology to the WAN. 
This service is delivered over Multiprotocol Label Switching (MPLS) networks.
EVPN allows you to manage routing over a virtual private network, providing complete control and 
security. EVPN introduces a solution for multipoint L2VPN services with advanced multi-homing 
capabilities, using BGP for distributing customer or client MAC address reachability information over 
the MPLS/IP network. EVPN advertises each customer MAC address as BGP routes, therefore allowing 
BGP policy control over MAC addresses.
The PBB-EVPN solution combines Ethernet Provider Backbone Bridging (PBB - IEEE 802.1ah) with 
Ethernet VPN, where provider edges (PEs) perform as PBB Backbone Edge Bridge (BEB). The PEs 
receive 802.1Q Ethernet frames from their attachment circuits. These frames are encapsulated in the 
PBB header and forwarded over the Internet Protocol / Multi-protocol label switching (IP/MPLS) core. 
On the egress side (EVPN PE), the PBB header is removed after MPLS disposition, and the original 
802.1Q Ethernet frame is delivered to the customer equipment.
The PE routers perform these functions:
Learns customer or client MAC addresses (C-MACs) over the attachment circuits in the data-plane, 
per normal bridge operation.
Learns remote C-MAC to backbone MAC (B-MAC) bindings in the data-plane from traffic ingress 
from the core.
Advertises local B-MAC address reachability information in BGP to all other PE nodes in the same 
set of service instances. Note that every PE has a set of local B-MAC addresses that uniquely 
identify the device. 
						

							  
18-30
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
Builds a forwarding table from the received remote BGP advertisements, associating remote 
B-MAC addresses with remote PE IP addresses.
PBB-EVPN scales well for large network with millions of customer MAC addresses by constraining 
customer MAC address in access. Only B-MAC addresses are advertised in core, making the number of 
BGP routes exchanged manageable. 
This section describes the following topics:
EVPN Instance, page 18-30
Ethernet Segment, page 18-30
EVPN Instance
E-VPN Instance (EVI) identifies a VPN in the MPLS/IP network. There can only be one EVI per core 
bridge. 
Ethernet Segment
Ethernet Segment is a site connected to one or more PEs. The Ethernet Segment can be a single device 
like a Customer Edge (CE) or an entire network, such as:
Single-Homed Device (SHD)
Multi-Homed Device (MHD) using Ethernet Multi-chassis Link Aggregation Group
Single-Homed Network (SHN)
Multi-Homed Network (MHN)
The Ethernet segment is uniquely identified by a 10-byte global Ethernet Segment Identifier (ESI). 
You can view the following properties in the PBB-EVPN network:
Viewing PBB-EVPN Core Bridge Properties, page 18-30
Viewing EVPN Container Properties, page 18-34
Viewing EVPN Properties, page 18-35
Viewing Ethernet Segment Container Properties, page 18-36
Viewing Ethernet Segment Properties, page 18-38
Viewing PBB-EVPN Core Bridge Properties
To view the PBB-EVPN core bridge properties:
Step 1Double-click the required device in the Vision client.
Step 2In the Inventory window, choose Logical Inventory > Bridges to view the list of bridges.
Step 3Select a PBB-EVPN bridge to view the properties.
Table 18-16 describes the information displayed for PBB-EVPN bridge properties. 
						

							  
18-31
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
Table 18-16 PBB-EVPN Core Bridge Properties
Field Description
Name PBB bridge name.
Type Specifies the type of bridge. There can be two types of bridges:
I-Bridge—Interfaces with the customer edge. 
B-bridge—Interfaces with the core network.
The PBB-EVPN core bridge is a B-bridge
VLAN ID VLAN identifier configured for the subscriber.
VSI VSI information, hyperlinked to the VSI entry in logical inventory.
Evi Specifies an unique route distinguisher per customer. There can only be 
one Evi per core bridge.
MMRP Enabled Denotes Multiple MAC Registration Protocol (MMRP). It allows 
multicast traffic in bridged LANs. 
NoteThe MMRP is disabled by default in the EVPN network.
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.
SAII Specifies the Source Access Individual Identifier (SAII) of the tunnel.
NoteThe SAII attribute can be configured only if the Pseudowire type 
is FEC129 TYPE II.
Tunnel Status Operational state of the tunnel: Up or Down.
TAII Specifies the Target Attachment Individual Identifier (TAII) of the 
tunnel.
NoteThe TAII can be configured only if the Pseudowire type is 
FEC129 TYPE II.
Peer Router IP IP Address of the peer router for this pseudowire.
Pseudowire  Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN Basic, 
PPP, SAToP or FEC129 TYPE II. 
Pseudowire Role If the pseudowire is in a redundancy configuration, then the pseudowire 
role indicates whether its a primary pseudowire or a secondary 
pseudowire in the configuration.
If the pseudowire is not configured for redundancy, the field is blank.
Preferred Path Tunnel Specifies the path that has to be used for MPLS pseudowire traffic. 
						

							  
18-32
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
Viewing PBB-EVPN Customer Bridge Properties
To view the PBB-EVPN customer bridge properties:
Step 1Double-click the required device in the Vision client.
Step 2In the Inventory window, choose Logical Inventory > Bridges to view the list of bridges.
Step 3Select a PBB-EVPN customer bridge to view the properties.
Table 18-17 describes the information displayed for PBB-EVPN customer bridge properties. Local Router IP Specifies the IP address of the tunnel edge, which is used as the router 
identifier.
Local MTU Specifies the byte size of the MTU on the local interface. 
Remote MTU Specifies the byte size of the MTU on the remote interface. 
Local VC Label Specifies the MPLS label that is used by the local router to identify or 
access the tunnel. It is inserted in the MPLS label stack by the local 
router.
Peer VC Label Specifies the MPLS label that is used by the peer router to identify or 
access the tunnel. It is inserted in the MPLS label stack by the peer 
router.
Signaling Protocol Specifies the protocol that is used to build the tunnel, such as the LDP or 
TDP.
Peer Status Specifies the status of the peer link.
Associated EVC Name Specifies the name of the associated Ethernet Virtual Circuits (EVC). 
I-Bridge Associations Tab
I-SID Specifies a 24-bit identifier that represents the backbone service 
instance.
I-Bridge Specifies the exchange identification (XID) in the I-Bridge component. 
The XID is hyperlinked to the relevant bridge in the logical inventory.
Table 18-16 PBB-EVPN Core Bridge Properties (continued)
Field Description
Table 18-17 PBB-EVPN Customer Bridge Properties
Field Description
Name PBB bridge name.
Type Specifies the type of bridge. The PBB-EVPN customer bridge is an 
I-bridge
VLAN ID VLAN identifier configured for the subscriber. 
						

							  
18-33
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
I-SID Specifies a 24-bit identifier that represents the backbone service 
instance.
B-Bridge Specifies the XID of the B-Bridge component. The XID is hyperlinked 
to the relevant bridge in logical inventory.
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.
SAII Specifies the Source Access Individual Identifier (SAII) of the tunnel.
NoteThe SAII attribute can be configured only if the Pseudowire type 
is FEC129 TYPE II.
Tunnel Status Operational state of the tunnel: Up or Down.
TAII Specifies the Target Attachment Individual Identifier (TAII) of the 
tunnel.
NoteThe TAII can be configured only if the Pseudowire type is 
FEC129 TYPE II.
Peer Router IP IP address of the peer router for this pseudowire.
Pseudowire  Type Type of pseudowire, such as Ethernet, Ethernet Tagged, CESoPSN Basic, 
PPP, SAToP or FEC129 TYPE II. 
Pseudowire Role If the pseudowire is in a redundancy configuration, then the pseudowire 
role indicates whether its a primary pseudowire or a secondary 
pseudowire in the configuration.
If the pseudowire is not configured for redundancy, the field is blank.
Preferred Path Tunnel Specifies the path that has to be used for MPLS pseudowire traffic.
Local Router IP Specifies the IP address of the tunnel edge, which is used as the router 
identifier.
Local MTU Specifies the byte size of the MTU on the local interface. 
Remote MTU Specifies the byte size of the MTU on the remote interface. 
Local VC Label Specifies the MPLS label that is used by the local router to identify or 
access the tunnel. It is inserted in the MPLS label stack by the local 
router.
Peer VC Label Specifies the MPLS label that is used by the peer router to identify or 
access the tunnel. It is inserted in the MPLS label stack by the peer 
router.
Signaling Protocol Specifies the protocol that is used to build the tunnel, such as the LDP or 
TDP.
Peer Status Specifies the status of the peer link.
Table 18-17 PBB-EVPN Customer Bridge Properties (continued)
Field Description 
						

							  
18-34
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
Viewing EVPN Container Properties
To view the EVPN container properties:
Step 1Right-click the required device in the Vision client and choose Inventory.
Step 2In the Inventory window, choose Logical Inventory > EVPN to view the EVPN container properties.
Table 18-18 describes the information displayed for the EVPN container properties. Associated EVC Name Specifies the name of the associated EVC. 
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.
Ingress Policy The name of the ingress service policy associated with the subscriber 
template. This field is applicable only for IP Subscriber and Service 
templates.
Egress Policy The name of the egress service policy associated with the subscriber 
template. This field is applicable only for IP Subscriber and Service 
templates.
Service Control Policy Specifies the policy for a port or operation.
MMRP Participants
Associated MMRP 
ParticipantSpecifies an entry that is hyperlinked to an associated MMRP service for 
that bridge.
Table 18-17 PBB-EVPN Customer Bridge Properties (continued)
Field Description
Table 18-18 EVPN Container Properties
Field Description
EVI The EVI identifies a VPN (Virtual Private Network) in the MPLS/IP 
network. There can only be one EVI per core bridge.
Bridge Domain Maintains a forwarding database of MAC addresses from packets 
received from its interfaces. The bridge domain is hyperlinked to the 
relevant core bridge in the logical inventory. 
						

							  
18-35
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
Viewing EVPN Properties
To view the EVPN properties:
Step 1Right-click the required device in the Vision client and choose Inventory.
Step 2In the Inventory window, choose Logical Inventory > EVPN to display the EVPN container properties.
Step 3Double-click an EVI to view its EVPN properties.
Table 18-19 describes the information displayed for EVPN properties. EVPN Type Specifies the type of bridges.There can be two types of bridges:
PBB-EVPN
BD
Route Distinguisher Creates a unique 96-bit VPNv4 address to distinguish routes within a 
single internet service providers (ISP) MPLS network.
Multicast Label Specifies a 20-bit multicast label in the MPLS packet to make 
forwarding decisions and to pre-establish a path for switch-labeled 
packets at the Layer 2. 
Unicast Label Specifies a 20-bit unicast label in MPLS packet to make forwarding 
decisions and to pre-establish a path for switch-labeled packets at the 
Layer 2.
Route Distinguisher 
(Auto)The Route Distinguisher (Auto) is generated by default as a combination 
of Loopback IP Address and EVI.
Route Target (Auto) Communicates the VPN route to the PE routers.
Table 18-18 EVPN Container Properties (continued)
Field Description
Table 18-19 EVPN Properties
Field Description
EVI The EVI identifies a VPN in the MPLS/IP network. There can only be 
one EVI per core bridge.
Bridge Domain Maintains a forwarding database of MAC addresses from packets 
received from its interfaces. The bridge domain is hyperlinked to the 
relevant core bridge in the logical inventory.
EVPN Type Specifies the type of bridges. There can be two types of bridges:
PBB-EVPN
BD
Route Distinguisher Creates a unique 96-bit VPNv4 address to distinguish routes within a 
single ISP-MPLS network.  
						

							  
18-36
Cisco Prime Network 4.3.2 User Guide
Chapter 18      Managing Carrier Ethernet Configurations
  Working with PBB-EVPN
Viewing Ethernet Segment Container Properties
The Ethernet segment is a site that is connected to one or more Provider Edge Switches (PEs). The 
Ethernet segment can be a single device such as a customer edge or an entire network. The Ethernet 
segment in a network can be of the following types:
Single-homed device (SHD) 
Multi-homed device (MHD) 
Single-homed network (SHN)
Multi-homed network (MHN)
The Ethernet segment is unique and identified by a 10-byte global Ethernet Segment Identifier (ESI).
To view the Ethernet segment container properties:
Step 1Right-click the required device in the Vision client and choose Inventory.
Step 2In the Inventory window, choose Logical Inventory > Ethernet Segments to view the Ethernet 
segment container properties.Multicast Label Specifies a 20-bit multicast label in MPLS packet to make forwarding 
decisions and to pre-establish a path for switch-labeled packets at the 
Layer 2. 
Unicast Label Specifies a 20-bit unicast label in MPLS packet to make forwarding 
decisions and to pre-establish a path for switch-labeled packets at the 
Layer 2.
Route Distinguisher 
(Auto)The Route Distinguisher (Auto) is generated by default as a combination 
of Loopback IP Address and EVI.
Route Target (Auto) Communicates the VPN route to the PE routers.
EVPN BMAC Address Entries Tab
MAC Address It is an unique identifier of the bridge clients in a PE router for an EVPN 
instance.
Next HOP Specifies the peer router associated to each EVPN instance.
MPLS Label Enables the MPLS network data packets to make packet forwarding 
decisions. This allows the data packets to create end-to-end circuits 
across any type of transport medium, using any protocol.
Import Route Targets Tab
Route Target The PE imports routes with specific prefixes or subnet masks based on 
the Route Target.
Export Route Targets Tab
Route Target The Route Target attribute defines the prefixes that are exported on the 
PE routers.
Table 18-19 EVPN Properties
Field Description