Juniper按口类型汇总.doc

Juniper按口类型汇总juniper中的接口命名规则：type-fpc/pic/port（大槽号/小槽号/端口号.子接口）Juniper接口类型： aeAggregated Ethernet interface. This is a virtual aggregated link and has a differentnaming format from most PICs; for more information, see “Aggregated EthernetInterfaces Overview” on page 661. asAggregated SONET/SDH interface. This is a virtual aggregated link and has adifferent naming format from most PICs; for more information, see “ConfiguringAggregated SONET/SDH Interfaces” on page 997. atATM1 or ATM2 intelligent queuing (IQ) interface or a virtual ATM interface on aCircuit Emulation (CE) interface. bcmGigabit Ethernet internal interface brIntegrated Services Digital Network (ISDN) interface (configured on a 1-port or4-port Basic Rate Interface (BRI) card). This interface has a different naming formatfrom most PICs: br-pim/0/port. The second number is always 0. For more information,see “Configuring ISDN Physical Interface Properties” on page 937. cau4Channelized AU-4 IQ interface (configured on the Channelized STM1 IQ or IQEPIC or Channelized OC12 IQ and IQE PICs). ce1Channelized E1 IQ interface (configured on the Channelized E1 IQ PIC or ChannelizedSTM1 IQ or IQE PIC). ciContainer interface. coc1Channelized OC1 IQ interface (configured on the Channelized OC12 IQ and IQEor Channelized OC3 IQ and IQE PICs). coc3Channelized OC3 IQ interface (configured on the Channelized OC3 IQ and IQEPICs) coc12Channelized OC12 IQ interface (configured on the Channelized OC12 IQ and IQEPICs). coc48Channelized OC48 interface (configured on the Channelized OC48 andChannelized OC48 IQE PICs). cpCollector interface (configured on the Monitoring Services II PIC). cstm1Channelized STM1 IQ interface (configured on the Channelized STM1 IQ or IQEPIC). cstm4Channelized STM4 IQ interface (configured on the Channelized OC12 IQ andIQE PICs). cstm16Channelized STM16 IQ interface (configured on the Channelized OC48/STM16and Channelized OC48/STM16 IQE PICs). ct1Channelized 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 ChannelizedT1 IQ PIC). ct3Channelized 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). demuxInterface that supports logical IP interfaces that use the IP source or destinationaddress to demultiplex received packets. Only one demux interface (demux0) existsper chassis. All demux logical interfaces must be associated with an underlying logicalinterface. dfcInterface that supports dynamic flow capture processing on T Series or M320routers containing one or more Monitoring Services III PICs. Dynamic flow captureenables you to capture packet flows on the basis of dynamic filtering criteria.Specifically, you can use this feature to forward passively monitored packet flows thatmatch a particular filter list to one or more destinations using an on-demand controlprotocol. dsDS0 interface (configured on the Multichannel DS3 PIC, Channelized E1 PIC,Channelized OC3 IQ and IQE PICs, Channelized OC12 IQ and IQE PICs, ChannelizedDS3 IQ and IQE PICs, Channelized E1 IQ PIC, Channelized STM1 IQ or IQE PIC, orChannelized T1 IQ). dscDiscard interface. e1E1 interface (including channelized STM1-to-E1 interfaces). e3E3 interface (including E3 IQ interfaces). emManagement and internal Ethernet interfaces for RE2600 and RE1800 RoutingEngines. The Junos OS automatically configures the routers management interface,em0, which is an out-of-band management interface, and the internal Ethernet interfaceem1, which connects the Routing Engine with the routers packet-forwardingcomponents. If the router has redundant Routing Engines, the Junos OS configuresanother internal Ethernet interface, em2, on each Routing Engine (re0 and re1) in orderto support fault tolerance. Two physical links between re0 and re1 connect theindependent control planes. If one of the links fails, both Routing Engines can use theother link for IP communication.esEncryption interface. et100-Gigabit Ethernet interface. feFast Ethernet interface. fxpManagement and internal Ethernet interfaces for all Routing Engines exceptRE2600 and RE1800 Routing Engines. The Junos OS automatically configures therouters management Ethernet interface, fxp0, which is an out-of-band managementinterface, and the internal Ethernet interface, fxp1, which connects the Routing Enginewith the routers packet-forwarding components. If the router has redundant RoutingEngines, another internal Ethernet interface, fxp2, is created on each Routing Engine(re0 and re1) in order to support fault tolerance. Two physical links between re0 andre1 connect the independent control planes. If one of the links fails, both Routing Enginescan use the other link for IP communication. geGigabit Ethernet interface. Some older 10-Gigabit Ethernet interfaces use the gemedia type to identify the physical part of the network device, but newer 10-GigabitEthernet interfaces use the xe media type. grGeneric routing encapsulation (GRE) tunnel interface. greInternally generated interface that is configurable only as the control channel forGeneralized MPLS (GMPLS). For more information about GMPLS, see the Junos OSMPLS Applications Configuration Guide and the Junos OS Feature Guide. ipIP-over-IP encapsulation tunnel interface. ipipInternally generated interface that is not configurable. ixgbe10-Gigabit Ethernet internal interface iwLogical interfaces associated with the endpoints of Layer 2 circuit and Layer 2 VPNconnections (pseudowire stitching for Layer 2 VPNs). For more information aboutVPNs, see the Junos OS VPNs Configuration Guide. lcInternally generated interface that is not configurable. loLoopback interface. The Junos OS automatically configures one loopback interface(lo0). The logical interface lo0.16383 is a nonconfigurable interface for router controltraffic. lsLink services interface. lsiInternally generated interface that is not configurable. mlMultilink interface (including Multilink Frame Relay and MLPPP). moMonitoring services interface (including monitoring services and monitoring servicesII). The logical interface mo-fpc/pic/port.16383 is an internally generated,nonconfigurable interface for router control traffic. msMultiServices interface. mtMulticast tunnel interface (internal router interface for VPNs). If your router hasa Tunnel PIC, the Junos OS automatically configures one multicast tunnel interface(mt) for each virtual private network (VPN) you configure. Although it is not necessaryto configure multicast interfaces, you can use the multicast-only statement to configurethe unit and family so that the tunnel can transmit and receive multicast traffic only.For more information, see multicast-only. mtunInternally generated interface that is not configurable. oc3OC3 IQ interface (configured on the Channelized OC12 IQ and IQE PICs orChannelized OC3 IQ and IQE PICs). pdInterface on the rendezvous point (RP) that de-encapsulates packets. peInterface on the first-hop RP that encapsulates packets destined for the RP router. pimdInternally generated interface that is not configurable. pimeInternally generated interface that is not configurable. rlsqContainer interface, numbered from 0 through 127, used to tie the primary andsecondary LSQ PICs together in high availability configurations. Any failure of theprimary PIC results in a switch to the secondary PIC and vice versa. rmsRedudant interface for two MultiServices interfaces. rspRedundant virtual interface for the adaptive services interface. seSerial interface (including EIA-530, V.35, and X.21 interfaces). soSONET/SDH interface. spAdaptive services interface. The logical interfac