Хвостат Хвостатыч (hvostat_hvostat) wrote,
Хвостат Хвостатыч
hvostat_hvostat

Interface Naming in JunOS



• 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.
• 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.
• at— ATM1 or ATM2 intelligent queuing (IQ) interface or a virtual ATM interface on a circuit emulation (CE) interface.
• bcm— The bcm0 internal Ethernet process is supported on specific Routing engines for various M series and T series routers. For more information please refer the link titled Supported Routing Engines by Chassis under Related Documentation section.
• br— Integrated Services Digital Network (ISDN) interface (configured on a 1-port or 4-port ISDN 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.
• 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 M Series routers, MX Series routers, T Series routers, and TX Series routers, you can use the show chassis hardware command to display hardware information about the router, including its Routing Engine model. To determine which management interface is supported on your router and Routing Engine combination, see Understanding Management Ethernet Interfaces and Supported Routing Engines by Router.
• es— Encryption interface.
• et— 100-Gigabit Ethernet interfaces (10, 40, and 100-Gigabit Ethernet interface for PTX Series Packet Transport Routers only).
• fe— Fast Ethernet interface.
• fxp— Management and internal Ethernet interfaces. For M Series routers, MX Series routers, T Series routers, and TX Series routers, you can use the show chassis hardware command to display hardware information about the router, including its Routing Engine model. To determine which management interface is supported on your router and Routing Engine combination, see Understanding Management Ethernet Interfaces and Supported Routing Engines by Router.
• ge— Gigabit Ethernet interface. Some older 10-Gigabit Ethernet interfaces use the ge media type to identify the physical part of the network device, but newer 10-Gigabit Ethernet interfaces use the xe media type.
• gr— Generic routing encapsulation (GRE) tunnel interface.
• gre— Internally generated interface that is configurable only as the control channel for Generalized MPLS (GMPLS). For more information about GMPLS, see the Junos OS MPLS Applications Library for Routing Devices and the Junos OS, Release 14.2.
• ip— IP-over-IP encapsulation tunnel interface.
• ipip— Internally generated interface that is not configurable.
• irb- Integrated bridging and routing (IRB) interface.
• ixgbe— The internal Ethernet process ixgbe0 and ixgbe1 are used by the RE-DUO-C2600-16G Routing Engine, which is supported on TX Matrix Plus and PTX5000.
• iw— Logical interfaces associated with the endpoints of Layer 2 circuit and Layer 2 VPN connections (pseudowire stitching Layer 2 VPNs). For more information about VPNs, see the Junos OS VPNs Library for Routing Devices.
• lc— Internally generated interface that is not configurable.
• lo— Loopback interface. The Junos OS automatically configures one loopback interface (lo0). The logical interface lo0.16383 is a nonconfigurable interface for router control traffic.
• ls— Link services interface.
• lsi— Internally generated interface that is not configurable.
• lt- Logical tunnel. On SRX Series Services Gateways, the logical tunnel interface is used to interconnect logical systems.
• ml— Multilink interface (including Multilink Frame Relay and MLPPP).
• mo— Monitoring services interface (including monitoring services and monitoring services II). The logical interface mo-fpc/pic/port.16383 is an internally generated, nonconfigurable interface for router control traffic.
• ms— Multiservices interface.
• mt— Multicast tunnel interface (internal router interface for VPNs). If your router has a Tunnel PIC, the Junos OS automatically configures one multicast tunnel interface (mt) for each virtual private network (VPN) you configure. Although it is not necessary to configure multicast interfaces, you can use the multicast-only statement to configure the unit and family so that the tunnel can transmit and receive multicast traffic only. For more information, see multicast-only.
• mtun— Internally generated interface that is not configurable.
• oc3— OC3 IQ interface (configured on the Channelized OC12 IQ and IQE PICs or Channelized OC3 IQ and IQE PICs).
• pd— Interface on the rendezvous point (RP) that de-encapsulates packets.
• pe— Interface on the first-hop PIM router that encapsulates packets destined for the RP router.
• pimd— Internally generated interface that is not configurable.
• pime— Internally generated interface that is not configurable.
• rlsq— Container interface, numbered from 0 through 127, used to tie the primary and secondary LSQ PICs together in high availability configurations. Any failure of the primary PIC results in a switch to the secondary PIC and vice versa.
• rms— Redundant interface for two multiservices interfaces.
• rsp— Redundant virtual interface for the adaptive services interface.
• se— Serial interface (including EIA-530, V.35, and X.21 interfaces).
• si— Services-inline interface, which is hosted on a Trio-based line card.
• so— SONET/SDH interface.
• sp— Adaptive services interface. The logical interface sp-fpc/pic/port.16383 is an internally generated, nonconfigurable interface for router control traffic.
• st- Secure tunnel interfaces are used in the creation of route-based VPNs.
• stm1— STM1 interface (configured on the OC3/STM1 interfaces).
• stm4— STM4 interface (configured on the OC12/STM4 interfaces).
• stm16— STM16 interface (configured on the OC48/STM16 interfaces).
• t1— T1 interface (including channelized DS3-to-DS1 interfaces).
• t3— T3 interface (including channelized OC12-to-DS3 interfaces).
• tap— Internally generated interface that is not configurable.
• umd— USB modem interface.
• vsp— Voice services interface.
• vc4— Virtually concatenated interface.
• vt— Virtual loopback tunnel interface.
• xe— 10-Gigabit Ethernet interface. Some older 10-Gigabit Ethernet interfaces use the ge media type (rather than xe) to identify the physical part of the network device.
• xt— Logical interface for Protected System Domains to establish a Layer 2 tunnel connection.
Tags: juniper, железо
Subscribe

  • "Firefox: TCP Fast Open"

    В Firefox версии 60 появилась поддержка быстрого открытия TCP-соединений. Управляется параметром: network.tcp.tcp_fastopen_enable Для включения…

  • О фирменных знаках.

    Кто не обновил Огнелиса - напоминаю, что вышла 23-я версия. Да, и зачем они побрили/уложили шерсть на спине лисицы на фирменном знаке, кто-нибудь…

  • "IPsec в Windows"

    Вопрос: Какой набор шифров и хэш-функций предлагает по дефолту встроенный в Windows 8.1 Pro IPsec клиент? Ответ: Вот такой:…

  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 4 comments