interfacefees or linearcards Juniper Networks (line card, interface module) allow you to expand your router or switch (modular platform, chassis) Required functional, including the necessary access ports at speeds 1GbE, 10GbE, 40GbEor 100GbE, control boards (switch control board) etc..
Interface boards Juniper represented by various modules that are compatible with a particular series (for example. interface module MS-MIC-16G compatible with the entire range Juniper MX, and the module MPC-3D-16XGE-SFPP series compatible MX240, MX480 andMX960).
interface board MIC (Modular Interface Cards) is a small-sized module that provides physical connection to various types of network devices. MIC the board can support various physical interfaces in one module. module Juniper MICs also support hot swapping and plugging. For example, in routers MX series, interface module MIC installed in the module MPC (Modular Port Concentrator), and in series from MX5 before MX104 module MPC already built in chassis.
interface module Juniper MPC (Modular Port Concentrator) provides transfer services Lkand packages. module MPC encapsulates packets and passes them through the module's outgoing interfaces MIC. everyone MPC module equipped with up to four chipsets Junos Trio, which performs the functions of management. For example, a router Juniper MX960 supports installation of up to 12 modules MPCs, and the platform MX480 before 3 MPCs. For proper operation module Juniper MPC You need to use high-performance cooling modules. Online Juniper http://www.juniper.net there is a calculator for calculating the recommended power and cooling power, for a specific series and used MPC modules.
Interface modules DPC (Dense Port Concentrators) Provides several physical interfaces and pass systems Lkand packages on a single board that fits into a slot in a router or modular chassis. module DPC accepts incoming packets and sends outgoing packets to the network.
module Juniper PIC (Physical Interface Card) installed in FPC (Flexible PIC Concentrators), similar to how they work MIC andMPC modules. PICs modules provide physical interfaces, and FPCs boards provide transfers Lkfor packets on the network. everyone FPCthe module is equipped with a microchip ASIC, which performs the functions of management, and FPC supports installation of 2 modules PIC.
Technical characteristics of the interface module Juniper MIC-3D-8OC3-2OC12-ATM:
|
Software release
|
|
|
Description
|
- Rate-selectable using one of the following rates:
- 8-port OC3
- 2-port OC12
- Power requirement: 0.73 A @ 48 V (35 W)
- Weight: 1.2 lb (0.54 kg)
- Model number: MIC-3D-8OC3-2OC12-ATM
- Name in the CLI: 3D 80C3 20C12 ATM
|
|
Hardware features
|
- High-performance parsing of SONET/SDH frames
- Packet segmentation and reassembly (SAR) management and output port queuing
- Packet buffering, Layer 2 parsing
- Line rate throughput for each port
|
|
Software features
|
- Circuit cross-connect (CCC) for leveraging ATM access networks
- User-configurable virtual circuit (VC) and virtual path (VP) support
- Support for idle cell or unassigned cell transmission
- OAM fault management processes alarm indication signal (AIS), remote defect indication (RDI) cells, and loop cells
- Point-to-point and point-to-multipoint mode Layer 2 counters per VC and per VP
- Local and remote loopback
- Simple Network Management Protocol (SNMP):
- Management Information Base (MIB) 2 (RFC 1213)
- ATM MIB (RFC 1695)
- SONET MIB
- PWE3 MIB (RFC 5603)
- PW-ATM-MIB (RFC 5605)
- PW-FRAME-MIB (RFC 5601)
- MIB for CoS
- Unspecified bit rate (UBR), non-real-time variable bit rate (VBR), and constant bit rate (CBR) traffic shaping
- Per-VC or per-VP traffic shaping
- Support for F4 OAM cells (AIS, RDI, Loopback, and Continuity Check)
- Support for F5 OAM cells (AIS, RDI, Loopback, and Continuity Check)
- Support for 16 bit VCI range
- Encapsulations:
- atm-ccc-cell-relay (Junos 12.1 and later)
- atm-ccc-vc-mux (Junos 12.1 and later)
- atm-snap (Junos 12.2 and later)
- atm-vc-mux (Junos 12.2 and later)
- atm-tcc-snap (Junos 13.3 and later)
- atm-tcc-vc-mux (Junos 13.3 and later)
- vlan-vci-ccc (Junos 16.1 and later)
- ether-over-atm-llc
- ppp-over-ether-over-atm-llc
- atm-ppp-llc
- atm-ppp-vc-mux
Note: Inline MLPPP is not supported on this MIC.
|
|
Cables and connectors
|
Tip: You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on your Juniper Networks device.
The list of supported transceivers for the MX Series is located at https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series.
|
|
LEDs
|
OK/FAIL LED, one bicolor:
- Green—MIC is functioning normally.
- Red—MIC has failed.
Link LED, one green per port:
- Off—No link.
- On steadily—Link is up.
- Blinking—Online with alarms for remote failures
- Blinking rapidly—Active with a local alarm; router has detected a failure
|
|
Alarms, errors, and events
|
- Alarm indication signal—line (AIS-L)
- Alarm indication signal—path (AIS-P)
- Bit error rate—signal degrade (BERR-SD)
- Bit error rate—signal fail (BERR-SF)
- Loss of cell delineation (LOC)
- Loss of frame (LOF)
- Loss of pointer (LOP-P)
- Loss of signal (LOS)
- Payload mismatch (PLM-P)
- Payload unequipped (unequipped STS at path level) (UNEQ-P)
- Remote defect indication—line (RDI-L)
- Remote defect indication—path (RDI-P)
- Error detection:
- Bit interleaved parity errors B1, B2, B3
- Errored seconds (ES-S, ES-L, ES-P)
- Far-end bit errors, remote error indication—line (REI-L), far-end line coding violations (CV-LFE)
- Far-end bit errors, remote error indication—path (REI-P), far-end path coding violations (CV-PFE)
- Far-end errored seconds (ES-LFE, ES-PFE)
- Far-end severely errored seconds (SES-LFE, SES-PFE)
- Far-end unavailable seconds (UAS-LFE, UAS-PFE)
- Severely errored framing (SEF)
- Severely errored framing seconds (SEFS-S)
- Severely errored seconds (SES-S, SES-L, SES-P)
- Unavailable seconds (UAS-L, UAS-P)
|
table tr:nth-child(2n) {background: #f5f5f5;}
-->
Log In