Configuring vpls cpu protection – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 508
![background image](/manuals/361646/508/background.png)
484
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
show mpls vpls detail
3
•
CPU protection cannot be enabled for a VPLS instance that has a port configured under two
different VPLS VLANs. Similarly, when CPU protection is enabled for a VPLS instance, the
system does not support a configuration with two different VPLS VLANs as part of the same
VPLS instance.
•
When VPLS FID usage reaches 100%, CPU protection is temporarily disabled until adequate
FID resources are available.
Configuring VPLS CPU protection
VPLS CPU protection can be configured in either of the following two ways:
•
Globally – This enables VPLS CPU protection to affect all VPLS instances on the router
•
Per-VPLS – This enables VPLS CPU protection on one or more specified VPLS instances
Configuring VPLS CPU protection globally
VPLS CPU protection can be enabled for all VPLS instances on a router. To enable VPLS CPU
protection on all VPLS instances, enter the following command.
Brocade(config)# router mpls
Brocade(config-mpls) vpls-cpu-protection
Syntax: [no] vpls-cpu-protection
Configuring VPLS CPU protection per VPLS
VPLS CPU protection can be enabled per VPLS instance. To enable VPLS CPU protection on a
specified VPLS instance, enter the following command.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls test 1
Brocade(config-mpls-vpls-test)# cpu-protection
Syntax: [no] cpu-protection
VPLS Broadcast, multicast, and unknown unicast packet limiting
This feature limits the number of broadcast, multicast, and unknown unicast packet packets that
are flooded into the network. The user can limit the number of broadcast, multicast, and unknown
unicast packet that are flooded by the LP CPU on all VPLS instances.
The user can limit the number of packets that are flooded by the LP CPU on VPLS instances using
the following command.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls-policy
cpu-broadcast-limit 100000
cpu-multicast-limit 200000
cpu-unknown-unicast-limit 300000
Syntax: [no] vpls-policy | [no] cpu-broadcast-limit number |[no] cpu-multicast-limit number| [no]
cpu-unknown-unicast-limit number]