Enabling vpls auto-discovery, To disable load balancing, refer to, Disabling load balancing – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 793
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
769
53-1003031-02
Configuring BGP-based auto-discovery for VPLS
8
The above commands disable VPLS auto-discovery for VPLS instance “c1”, then re-enable VPLS
auto-discovery with the load-balance option.
Syntax: [no] auto-discovery
Syntax: [no] auto-discovery load-balance
Disabling load balancing
To disable load balancing when VPLS auto-discovery is enabled on the device, first disable VPLS
auto-discovery, then re-enable it without the load-balancing option.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls c1 10
Brocade(config-mpls-vpls-c1)# no auto-discovery load-balance
Brocade(config-mpls-vpls-c1)# auto-discovery
Syntax: [no] auto discovery load-balance
Syntax: [no] auto-discovery
Viewing the load balancing configuration
Use the show mpls vpls name command to view when VPLS traffic to the peer is load balanced
across tunnel LSPs, and to the tunnel LSPs used to reach the peer. Refer to
about VPLS auto-discovery and load balancing”
Enabling VPLS auto-discovery
NOTE
Before enabling VPLS auto-discovery, make sure the user has completed the configuration tasks
listed in
762.
To enable auto-discovery for a VPLS instance, enter commands such as the following.
Brocade(config)# router mpls
Brocade(config-mpls)# vpls c1
Brocade(config-mpls-vpls-c1)# auto-discovery
These commands enable MPLS, then change the CLI configuration level from the global MPLS level
to the configuration level for the VPLS instance “c1”. The auto-discovery command enables
auto-discovery for this VPLS instance.
Syntax: [no] auto-discovery
Use the [no] form of the command to disable VPLS auto-discovery.
Configuration notes
Consider the following configuration notes while enabling VPLS auto-discovery:
•
When the user attempts to enable VPLS auto-discovery without first adding a loopback
interface, the following error message displays on the console.