[Contents] [Prev] [Next] [Index] [Report an Error]

Interface Naming Conventions Used in JUNOS Operational Commands

This topic explains the interface naming conventions used in JUNOS operational commands, and contains the following sections:

Physical Part of an Interface Name

The M-series and T-series routing platforms use one convention for interface naming, whereas the J-series routing platform uses another.

Note: Exceptions to the type-fpc/pic/port physical description include the aggregated Ethernet and aggregated SONET/SDH interfaces, which use the syntax aenumber and asnumber, respectively.

Note: An exception to the type-pim/0/port physical description is the Integrated Services Digital Network (ISDN) dialer interface, which uses the syntax dlnumber.

Logical Part of an Interface Name

The logical unit part of the interface name corresponds to the logical unit number, which can be a number from 0 through 16,384. In the virtual part of the name, a period (.) separates the port and logical unit numbers:

Channel Identifier Part of an Interface Name

The channel identifier part of the interface name is required only on channelized interfaces. For channelized interfaces, channel 0 identifies the first channelized interface. For channelized intelligent queuing (IQ) interfaces, channel 1 identifies the first channelized interface.

Note: Depending on the type of channelized interface, up to three levels of channelization can be specified. For more information, see the JUNOS Network Interfaces Configuration Guide.

A colon (:) separates the physical and virtual parts of the interface name:


[Contents] [Prev] [Next] [Index] [Report an Error]