Management Ethernet Interfaces Overview
Management interfaces are the primary interfaces for accessing the device remotely.
Typically, a management interface is not connected to the in-band network but is connected
instead to the device's internal network. You (the system administrator) can use the
management interface to access the device over the network using utilities such as
ssh
and telnet
. You can configure the device from
anywhere, regardless of its physical location. SNMP can use the management interface to gather
statistics from the device.
Authorized users and management systems use a management interface to connect to the device over the network. Some Juniper Networks devices have a dedicated management port on the front panel. For other types of platforms, you can configure a management interface on one of the network interfaces. You can dedicate this interface to management or share it with other traffic.
You must configure the management interface before users can access it. To set up the management interface, you need information such as its IP address, prefix, and next hop. We recommend configuring your devices so that traffic is not routed between the management interface and the other ports. In Junos OS Evolved, it is not possible to route traffic between the management interface and the other ports. Therefore, you should select an IP address in a separate (logical) network with a separate prefix (netmask).
The name of the management interface depends on the platform. For devices running Junos OS, the management Ethernet interface is usually named fxp0, em0, or me0. For Junos OS Evolved, use re0:mgmt-* for Routing Engine 0 and re1:mgmt-* for Routing Engine 1 management interfaces, where the * is the index of the management interface. If there is only one management interface, the index is 0.
Table 1 summarizes the management interfaces typically used on Junos and Junos Evolved platforms. It's always a good idea to refer to the specific documentation for your platform to confirm details about its management interface.
Refer to the Product Documentation page for details on your platform.
Alternatively, refer to the Day One + quick start guide for your platform at: Day One + Guides.
Platform |
Interface Name | Description |
---|---|---|
MX Series routers |
fxp0 |
The |
EX Series switches |
me0 , vme |
The vme interface is used when the device is part of a
Virtual Chassis (VC), and is accessed via the me0 port. For
consistency you can configure and use the vme interface on a stand
alone switch. |
QFX Series switches |
em0 , vme |
The vme interface is used when the device is part of a
Virtual Chassis (VC), and is accessed via the em0 port. For
consistency you can configure and use the vme interface on a stand
alone switch. |
SRX Security Gateways |
fxp0 , ge-0/0/0 |
The |
Platforms running Junos Evolved, for example, PTX10001-36MR, PTX10003, PTX10004, PTX10008, QFX5130, QFX5220, etc. |
re0:mgmt-* and re1:mgmt-* |
Junos Evolved platforms typically support two management interfaces per Routing
Engine. The two Routing Engines are identified as re0 and
re1 . The RJ-45 copper port on each Routing Engine is indexed as 0,
while the SFP fiber port is indexed as 1. For example, the RJ-45 management
Ethernet port on Routing Engine 0 is typically named
|