Accessing the Virtual Chassis Through the Management Interface
The management Ethernet interface (fxp0) on an MX Series router or EX9200 switch is an out-of-band management interface, also referred to as a management port, that enables you to use Telnet or SSH to access and manage the device remotely. You typically configure the management interface with an IP address and prefix length when you first install Junos OS.
You can configure a management Ethernet interface in one of two ways to access a Virtual Chassis:
To access the Virtual Chassis as a whole, configure a consistent IP address for the management interface using the master-only option. You can use this management IP address to consistently access the primary (primary) Routing Engine in the primary router or switch (protocol primary) for the Virtual Chassis.
To access a specific Routing Engine in an individual member router or switch of the Virtual Chassis, configure an IP address for one of the following configuration groups:
member0-re0
member0-re1
member1-re0
member1-re1
For most management tasks, we recommend that you access the Virtual Chassis as a whole through a consistent management IP address. For troubleshooting purposes, however, accessing a specific Routing Engine in an individual member router or switch may be useful.
To access a Virtual Chassis through the management Ethernet interface, do one of the following:
Configure a consistent management IP address that accesses the entire Virtual Chassis through the primary Routing Engine in the Virtual Chassis primary router or switch.
{master:member0-re0}[edit] user@host# set interfaces fxp0 unit 0 family inet address ip-address/prefix-length primary-only
For example, to access the entire Virtual Chassis via management IP address 10.4.5.33/16:
{master:member0-re0}[edit] user@host# set interfaces fxp0 unit 0 family inet address 10.4.5.33/16 primary-only
Configure a management IP address that accesses a specified Routing Engine in an individual member router or switch in the Virtual Chassis.
{master:member0-re0}[edit groups] user@host# set membern-ren interfaces fxp0 unit 0 family inet address ip-address/prefix-length
For example, to access the Routing Engine installed in slot 1 of member router 1 (member1-re1) in the Virtual Chassis:
{master:member0-re0}[edit groups] user@host# set member1-re1 interfaces fxp0 unit 0 family inet address 10.4.3.145/32