Related Documentation
- J, M, MX, PTX, T Series
- Types of Interfaces Overview
- Permanent Interfaces Overview
- Understanding Internal Ethernet Interfaces
- Interface Encapsulations Overview
- Interface Descriptors Overview
- Interface Naming Overview
- Displaying Interface Configurations Overview
- J, M, MX, T Series
- Understanding Services Interfaces
- Container Interfaces Overview
- M, MX, PTX, T Series
- Supported Routing Engines by Chassis
- M, MX, T Series
- Understanding Transient Interfaces
- PTX Series
- PTX Series Packet Transport Switch Management Ethernet Interfaces
Understanding Management Ethernet Interfaces
The management Ethernet interface provides an out-of-band method for connecting to the router using utilities such as ssh and telnet to monitor or configure the router, or the Simple Network Management Protocol (SNMP) to gather statistics from the router. The Junos OS automatically configures the router’s management Ethernet interface, as either em0 or fxp0, and the internal Ethernet interface, em1 or fxp1, which connects the Routing Engine with the router’s packet-forwarding components.
You can use the show chassis hardware command to display hardware information about the router, including its Routing Engine model. The specific Routing Engine model installed in the routers determines which of the two management Ethernet interface types is supported, em0 or fxp0. To determine which management interface type is supported on a router, locate the router and Routing Engine combination in Supported Routing Engines by Chassis and note its management Ethernet interface type, either em0 or fxp0.
To use a type em0 management Ethernet interface as a management port, you must configure its logical port, em0.0, with a valid IP address.
To use a type fxp0 management Ethernet interface as a management port, you must configure its logical port, fxp0.0, with a valid IP address.
For the 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.” |
| Note: 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. |
| Note: Restricted load-sharing next hops with fxp0—On M Series routers and T Series 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. |
| Note: CoS not supported on fxp0—The fxp0 interface does not support CoS. |
For information about configuring the speed of management Ethernet interfaces on M Series and T Series routers, see Configuring the Interface Speed
For information about establishing basic connectivity and configuring a management port, see the Getting Started guide for your router.
Related Documentation
- J, M, MX, PTX, T Series
- Types of Interfaces Overview
- Permanent Interfaces Overview
- Understanding Internal Ethernet Interfaces
- Interface Encapsulations Overview
- Interface Descriptors Overview
- Interface Naming Overview
- Displaying Interface Configurations Overview
- J, M, MX, T Series
- Understanding Services Interfaces
- Container Interfaces Overview
- M, MX, PTX, T Series
- Supported Routing Engines by Chassis
- M, MX, T Series
- Understanding Transient Interfaces
- PTX Series
- PTX Series Packet Transport Switch Management Ethernet Interfaces
Published: 2013-02-13
Related Documentation
- J, M, MX, PTX, T Series
- Types of Interfaces Overview
- Permanent Interfaces Overview
- Understanding Internal Ethernet Interfaces
- Interface Encapsulations Overview
- Interface Descriptors Overview
- Interface Naming Overview
- Displaying Interface Configurations Overview
- J, M, MX, T Series
- Understanding Services Interfaces
- Container Interfaces Overview
- M, MX, PTX, T Series
- Supported Routing Engines by Chassis
- M, MX, T Series
- Understanding Transient Interfaces
- PTX Series
- PTX Series Packet Transport Switch Management Ethernet Interfaces
