Configuring Enhanced LAN Mode for a Virtual Chassis
Configuring network-services lan
assumes the
system is running in network-services enhanced-ip
mode.
Be sure to delete any unsupported configurations before
changing to enhanced-ip
mode.
To configure MX-LAN Mode for an existing Virtual Chassis:
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 Using the Enhanced Layer 2 Software CLI.