Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring Improved VPLS MAC Address Learning on T4000 Routers with Type 5 FPCs

Junos OS Release 12.3 enables improved virtual private LAN service (VPLS) MAC address learning on T4000 routers with Type 5 FPCs by supporting up to 262,143 MAC addresses per VPLS routing instance. In Junos OS releases before Release 12.3, T4000 routers with Type 5 FPCs support only 65,535 MAC addresses per VPLS routing instance.

Before you begin, configure VPLS. See Configuring VPLS Routing Instances.

To enable improved VPLS MAC address learning on T4000 routers with Type 5 FPCs:

  1. Enable the network services mode by including the enhanced-mode statement at the [edit chassis network-services] hierarchy level.
    Note:

    After you configure the enhanced-mode statement and commit your configuration, a warning message prompts you to reboot the router.

  2. Perform a system reboot in operational mode.

    After the router reboots, only the T4000 Type 5 FPCs are online while the remaining FPCs are offline. You can verify the status of the FPCs by using the show chassis fpc operational mode command.

  3. Modify the size of the VPLS MAC address table at the [edit routing-instance instance-name protocols vpls] hierarchy level.

    For example, to set the MAC address learning limit to 262,143 addresses for each vpls routing instance:

    Note:

    The enhanced-mode statement supports up to 262,143 MAC addresses per VPLS routing instance. However, the MAC address learning limit for each interface remains the same (that is, 65,535 MAC addresses).

  4. In configuration mode, verify the configuration.

To disable the improved VPLS MAC address learning feature on T4000 routers with Type 5 FPCs, include the delete chassis network-services enhanced-mode statement at the [edit] hierarchy level.

Note:

After you disable network services mode and commit your configuration, a warning message prompts you to reboot the router. You must reboot the router. Continuing without a reboot might result in unexpected system behavior.