-

2021年2月11日发(作者：naivete)

Junipe

r

按口类型汇总

< br>

juniper

中的接口命名规则：

< br>type-fpc/pic/port

（

大槽号

/

小槽号

/

端口号

.

子接口）

Juniper

接口类型：

●

ae

—

Aggregated

Ethernet

interface.

This

is

a

virtual

aggregated

link

and

has

a

different

naming format from most PICs; for more information, see

“

Aggregated Ethernet

Interfaces Overview

”

on page 661.

●

as

—

Aggregated SONET/SDH interface. This is a virtual aggregated link and has a

different naming format from most PICs; for more information, see

“

Configuring

Aggregated SONET/SDH Interfaces

”

on page 997.

●

at

—

ATM1 or ATM2 intelligent queuing (IQ) interface or a virtual ATM interface on a

Circuit Emulation (CE) interface.

●

bcm

—

Gigabit Ethernet internal interface

●

br

—

Integrated Services Digital Network (ISDN) interface (configured on a 1-port

or

4-port Basic Rate Interface (BRI) card). This interface has a different naming format

from

most

PICs:

br-pim/0/port.

The

second

number

is

always

0.

For

more

information,

see

“

Configuring ISDN Physical Interface Properties

”

on page 937.

●

cau4

—

Channelized AU-4 IQ interface (configured on the Channelized STM1 IQ or

IQE

PIC or Channelized OC12 IQ and IQE PICs).

●

ce1

—

Channelized E1 IQ interface (configured on the Channelized E1 IQ PIC or

Channelized

STM1 IQ or IQE PIC).

●

ci

—

Container interface.

●

coc1

—

Channelized OC1 IQ interface (configured on the Channelized OC12 IQ and

IQE

or Channelized OC3 IQ and IQE PICs).

●

coc3

—

Channelized OC3 IQ interface (configured on the Channelized OC3 IQ and

IQE

PICs)

●

coc12

—

Channelized OC12 IQ interface (configured on the Channelized OC12 IQ

and IQE

PICs).

●

coc48

—

Channelized OC48 interface (configured on the Channelized OC48 and

Channelized OC48 IQE PICs).

●

cp

—

Collector interface (configured on the Monitoring Services II PIC).

●

cstm1

—

Channelized STM1 IQ interface (configured on the Channelized STM1 IQ

or IQE

PIC).

●

cstm4

—

Channelized STM4 IQ interface (configured on the Channelized OC12 IQ

and

IQE PICs).

●

cstm16

—

Channelized

STM16

IQ

interface

(configured

on

the

Channelized

OC48/STM16

and Channelized OC48/STM16 IQE PICs).

●

ct1

—

Channelized T1 IQ interface (configured on the Channelized DS3 IQ and IQE

PICs,

Channelized

OC3

IQ

and

IQE

PICs,

Channelized

OC12

IQ

and

IQE

PICs,

or

Channelized

T1 IQ PIC).

●

ct3

—

Channelized T3 IQ interface (configured on the Channelized DS3 IQ and IQE

PICs,

Channelized OC3 IQ and IQE PICs, or Channelized OC12 IQ and IQE PICs).

●

demux

—

Interface

that

supports

logical

IP

interfaces

that

use

the

IP

source

or

destination

address to demultiplex received packets. Only one demux interface (demux0) exists

per

chassis.

All

demux

logical

interfaces

must

be

associated

with

an

underlying

logical

interface.

●

dfc

—

Interface that supports dynamic flow capture processing on T Series or M320

routers containing one or more Monitoring Services III PICs. Dynamic flow capture

enables you to capture packet flows on the basis of dynamic filtering criteria.

Specifically, you can use this feature to forward passively monitored packet flows that

match a particular filter list to one or more destinations using an on-demand control

protocol.

●

ds

—

DS0 interface (configured on the Multichannel DS3 PIC, Channelized E1 PIC,

Channelized OC3 IQ and IQE PICs, Channelized OC12 IQ and IQE PICs, Channelized

DS3 IQ and IQE PICs, Channelized E1 IQ PIC, Channelized STM1 IQ or IQE PIC, or

Channelized T1 IQ).

●

dsc

—

Discard interface.

●

e1

—

E1 interface (including channelized STM1-to-E1 interfaces).

●

e3

—

E3 interface (including E3 IQ interfaces).

●

em

—

Management

and

internal

Ethernet

interfaces

for

RE2600

and

RE1800

Routing

Engines. The Junos OS automatically configures the router

’

s management interface,

em0,

which

is

an

out-of-band

management

interface,

and

the

internal

Ethernet

interface

em1, which connects the Routing Engine with the router

’

s packet- forwarding

components. If the router has redundant Routing Engines, the Junos OS configures

another

internal

Ethernet

interface,

em2,

on each Routing Engine

(re0 and

re1)

in

order

to support fault tolerance. Two physical links between re0 and re1 connect the

independent control planes. If one of the links fails, both Routing Engines can use the

other link for IP communication.

-

-

-

-

-

-

-

-