Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring MX Enhanced LAN Mode

    Configuring network-services assumes that the system is running in network-services enhanced-ip mode.

    Note: Be sure to delete any unsupported configurations before changing to enhanced-ip mode.

    To configure MX-LAN Mode for an existing Virtual Chassis:

    1. Log into the console for the master Routing Engine in the Virtual Chassis master router (member0-re0 in this procedure).
    2. Access the chassis hierarchy.
      {master:member0-re0}[edit]
      user@host# edit chassis
    3. Configuring MX-LAN Mode on member 0.
      {master:member0-re0}[edit chassis]
      user@host# set network-services
    4. Commit the configuration.
    5. When prompted to do so, reboot all Routing Engines in the Virtual Chassis.
      {master:member0-re0}

      The request system reboot command reboots both Routing Engines in each member router forming the Virtual Chassis.

      Warning: After the chassis configuration for network services has been changed, a system reboot is mandatory. Please reboot the system now. Continuing without a reboot might result in unexpected system behavior.

    6. (Optional) Verify that enhanced IP network services has been properly configured for the Virtual Chassis.

      Verify that MX-LAN Mode is configured on the master Routing Engine in the Virtual Chassis master router (member0-re0).

      {master:member0-re0}
      Network Services Mode: MX-LAN

    You must reboot the router when you configure or delete the enhanced LAN mode on the router. Configuring the network-services lan option implies that the system is running in the enhanced IP mode. When you configure a device to function in MX-LAN mode, only the supported configuration statements and operational show commands that are available for enabling or viewing in this mode are displayed in the CLI interface. If your system contains parameters that are not supported in MX-LAN mode in a configuration file, you cannot commit those unsupported attributes. You must remove the settings that are not supported and then commit the configuration. After the successful CLI commit, a system reboot is required for the attributes to be come effective. Similarly, if you remove the network-services lan statement, the system does not run in MX-LAN mode. Therefore, all of the settings that are supported outside of the MX-LAN mode are displayed and are available for definition in the CLI interface. If your configuration file contains settings that are supported only in MX-LAN mode, you must remove those attributes before you commit the configuration. After the successful CLI commit, a system reboot will be required for the CLI settings to take effect. The Layer 2 Next-Generation CLI configuration settings are supported in MX-LAN mode. As a result, the typical MX Series-format of CLI configurations might differ in MX-LAN mode.

    For more information about the Layer 2 Next-Generation (L2NG) mode, also called Enhanced Layer 2 software (ELS), and the hierarchy levels at which the different configuration statements and commands are available for various parameters, see Getting Started with Enhanced Layer 2 Software.

    Modified: 2017-10-28