Vpls cpu protection – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual

Page 111

Advertising
background image

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide

87

53-1003031-02

MPLS over virtual Ethernet interfaces

1

When MPLS is enabled on an interface, the last IP address of a VE cannot be removed. The
command is rejected. The following error message is displayed.

Brocade(config-vif-54)# no ip address 10.40.40.5/24

IP/Port: Error(31) Can not remove IP address as MPLS is configured on the port

VPLS CPU protection

NOTE

VPLS CPU protection is not applicable to Brocade NetIron CES or Brocade NetIron CER devices.

When enabling MPLS on a VE interface with VPLS CPU protection turned on, consider the following.

VPLS CPU protection must be disabled globally, or disabled on all instances of VPLS that has
VE member port as the VPLS endpoint. When VPLS CPU protection is not disabled, then MPLS
cannot be enabled on a VE interface. The following error message is displayed.

Brocade(config-mpls)# mpls-interface ve 1

Error - Port 4/3 belongs to a VPLS instance that has CPU-protection ON

The user cannot configure a VPLS endpoint on a member of a MPLS VE enabled interface
when VPLS CPU protection is configured globally, or for a specified instance. The configuration
is rejected, and the following error message is displayed.

Brocade(config-mpls-vpls-test-vlan-11)# tagged ethernet 4/3

Error - VPLS instance test has CPU protection ON and port 4/3 belongs to a MPLS

VE

When a VPLS endpoint belonging to a VPLS instance (with CPU protection turned on) is on a
port that does not belong to the VE, then the user cannot add a port in an untagged or tagged
mode to a VLAN which has a MPLS VE on it.

Brocade(config-vlan-100)# tagged ethernet 4/7

Error - Port 4/7 belongs to a VPLS instance that has CPU protection ON

On an MPLS VE enabled interface, when a VPLS endpoint is a member of the VE interface, but
VPLS CPU protection is not configured for the VPLS instance, then configuring VPLS CPU
protection globally does not enable CPU protection for that instance. When VPLS CPU
protection is enabled locally on that instance, the configuration is also rejected. The following
error message is displayed.

Brocade(config-mpls)# vpls-cpu-protection

Error - Cannot configure CPU protection for VPLS 111 as end-points share the

same physical port as MPLS VE interfaces.

CPU protection feature is not turned on for VPLS 111

Advertising