Cisco OL-21636-01 - Manual (Page 249)

10-13
Cisco IP Solution Center L2VPN and Carrier Ethernet User Guide, 6.0
OL-21636-01
Chapter 10 Managing a VPLS Service Request
Using the Bridge Domain ID Attribute
Using the Bridge Domain ID Attribute
The Bridge Domain ID attribute appears in the Link Attributes window of some VPLS service request
scenarios, as shown in
Figure 10-15 .
Figure 10-15 Bridge Domain ID Attribute
To use the Bridge Domain ID attribute, enter an ID number in the Bridge Domain ID text field to enable
bridge domain functionality for the VPLS service request.
Acceptable values are 1 to 4294967295.
Usage notes:
• The Bridge Domain ID attribute is only available for the following service request scenarios:
– Ethernet/ERMS (EVP-LAN) with a CE
– Ethernet/ERMS (EVP-LAN) without a CE
– Ethernet/EMS (EP-LAN) with a CE
– Ethernet/EMS (EP-LAN) without a CE
• The Bridge Domain ID attribute is only supported for the Cisco GSR 12406 running
IOS 12.0(32)SY6 and functioning in an N-PE role. This attribute will show up in a service request
only for this platform; otherwise, the attribute will be filtered from the Link Attributes window of
the service request.
• The following points apply to service requests based on this policy:
– When an N-PE (GSR platform) is used as a UNI device, the standard UNI attributes are not
displayed in the Link Attributes window of the service request workflow.
– When a U-PE (non-GSR platform) is used as a UNI device, all standard UNI attributes are
displayed in the Link Attributes window of the service request workflow.
– For VPLS EMS services, a U-PE (non-GSR platform) should be used in the same circuit which
is terminating on a GSR device (N-PE). In other words, an NPC circuit should be used to
provision VPLS EMS on GSR devices.