Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Understanding Management Ethernet Interfaces

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. Through a management interface you can access the device over the network using utilities such as ssh and telnet and configure the device from anywhere, regardless of its physical location. SNMP can use the management interface to gather statistics from the device.

A management interface lets authorized users and management systems 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. This interface can be dedicated to management or shared with other traffic. Before users can access the management interface, you must configure it. Information required to set up the management interface includes its IP address and prefix. In many types of Junos OS devices (or recommended configurations), 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).

For devices with dedicated management ports, Junos OS automatically configures the router’s management Ethernet interface, as either em0 or fxp0. You can use the show interfaces terse | match fxp0 or show interfaces terse | match em0 command to display management interface information.

To use the management Ethernet interface as a management port, you must configure its logical port, em0.0 or fxp0.0, with a valid IP address.

For some SRX Series Services Gateways and J Series Services Routers, you can use any of the built-in Ethernet ports as a management interface. To use a built-in interface as a management Ethernet interface, configure it with a valid IP address. The factory configuration for the J4350 and J6350 Services Routers automatically enables the J-Web user interface on the ge-0/0/0, ge-0/0/1, ge-0/0/2, and ge-0/0/3 interfaces. To manually configure J-Web access, include the interface interface-name statement at the [edit system services web-management http] hierarchy level.

Note: Routing Engine upgrade considerations—When upgrading to a Routing Engine that supports em0 from a Routing Engine that supports fxp0, you must convert existing management Ethernet interface references in the router configuration files from fxp0, fxp1, or fxp2 interfaces to em0 interfaces. Whether you use an automated script or edit the configuration files manually, you must revise any command lines that reference the fxp0 management Ethernet interface by replacing “fxp0” with “em0.”

Reusing scripts for standalone T1600 routers on T1600 routers in a routing matrix—Automated scripts that you have developed for standalone T1600 routers (T1600 routers that are not in a routing matrix) might contain references to the fxp0 management Ethernet interface. Before reusing the scripts on T1600 routers in a routing matrix, edit the command lines that reference the fxp0 management Ethernet interface so that the commands reference the em0 management Ethernet interface instead.

Restricted load-sharing next hops with fxp0—On M Series Multiservices Edge Routers and T Series Core Routers running Junos OS later than Release 7.0R2.7 or Release 7.1R2.2, the fxp0 interface does not support load-sharing next hops. This restriction only affects fxp0 routes.

CoS not supported on fxp0—The fxp0 interface does not support class of service (CoS).

 

Related Documentation

 

Published: 2013-10-28

Previous Page Next Page