[
Contents]
[
Prev]
[
Next]
[
Index]
[
Report an Error]
Naming Services Interfaces
Each interface has an interface name, which specifies
the media type, the slot the FPC is located in, the location on the
FPC that the PIC is installed in, and the PIC port. The interface
name uniquely identifies an individual network connector in the system.
You use the interface name when configuring interfaces and when enabling
various functions and properties, such as routing protocols, on individual
interfaces. The system uses the interface name when displaying information
about the interface, for example, in the show interfaces command.
The interface name is represented by a physical
part, a logical part, and a channel part in the following format:
- physical<:channel>.logical
The channel part of the name is optional for all
interfaces except channelized DS3, E1, OC12, and STM1 interfaces.
The physical part of an interface name identifies
the physical device, which corresponds to a single physical network
connector. This part of the interface name has the following format:
-
type-fpc/pic/port
type is the media
type, which identifies the network device. For service interfaces,
it can be one of the following:
-
cp—Flow collector interface.
-
es—Encryption interface.
-
gr—Generic routing encapsulation tunnel
interface.
-
gre—This interface is internally generated
and not configurable.
-
ip—IP-over-IP encapsulation tunnel interface.
-
ipip—This interface is internally generated
and not configurable.
-
ls—Link services interface.
-
lsq—Link services intelligent queuing (IQ)
interface; also used for voice services.
-
ml—Multilink interface.
-
mo—Monitoring services interface. The logical
interface mo-fpc/pic/port.16383 is an internally generated,
nonconfigurable interface for routing platform control traffic.
-
mt—Multicast tunnel interface. This interface
is automatically generated, but you can configure properties on it
if needed.
-
mtun—This interface is internally generated
and not configurable.
-
rlsq—Redundancy LSQ interface.
-
rsp—Redundancy adaptive services interface.
-
sp—Adaptive services interface. The logical
interface sp-fpc/pic/port.16383 is an internally generated,
nonconfigurable interface for routing platform control traffic.
-
tap—This interface is internally generated
and not configurable.
-
vp—Voice over IP (VoIP) interface, configured
on J-series Services Routers only.
-
vt—Virtual loopback tunnel interface.
[
Contents]
[
Prev]
[
Next]
[
Index]
[
Report an Error]