Las plataformas o dispositivos juniper correr sobre un sistema operativo propio

de la empresa denominado junos, este es similar a un mtodo de programacin

Hardware y Tarjetas
 fpcSlot in which the DPC is installed. On the MX960 router, the DPCs
are represented in the CLI as FPC 0 through FPC 11.

type-fpc/pic/port

type which identifies the network device. For example:

geGigabit Ethernet interface

soSONET/SDH interface

xe10-Gigabit Ethernet interface

picLogical PIC on the DPC.

The number of logical PICs varies depending on the type of DPC. For example,

20-port Gigabit Ethernet DPC has two logical PICs, numbered 0 through 1.

40-port Gigabit Ethernet DPC has four logical PICs, numbered 0 through 3.

2-port 10-Gigabit Ethernet DPC has two logical PICs, numbered 0 through 1.

4-port 10-Gigabit Ethernet DPC has four logical PICs, numbered 0 through 3.
acarmoni@mde-ame-mx960_re0> show chassis hardware
Tarjetas MIC.
Field Name Field Description

PEM slotstatu
s Number of the PEM slot.

State Status of the PEM.

Temperature Temperature of the air flowing past the PEM.

AC Input Status of the AC input for the specified component

AC Output Status of the AC output for the specified component.

DC input Status of the DC input for the specified component.

DC output Status of the DC output for the specified component.

(Not available on M40e or M160 routers) Information about the load on supply, in percentage
Load of rated current being used.

(M120, M160, M320, T640, T1600, TX Matrix, and TX Matrix Plus routers only) Information
about voltage supplied to the PEM.
Voltage (MX104 routers only) Information about voltage supplied by the PEM to the system.

Current (T640, T1600, TX Matrix, and TX Matrix Plus routers only) Information about the PEM current.

Power (T640, T1600, TX Matrix, and TX Matrix Plus routers only) Information about the PEM power.

(T640, T1600, TX Matrix, and TX Matrix Plus routers only) SONET Clock Generator/Control
SCG/CB/SIB Board/Switch Interface Board.

(T640, T1600, and T4000 routers with six-input DC power supply only) Information about the
FAN DC output to the fan.
Routing Engine (El cerebro de la Plataforma)

Routing Engine Function

The Routing Engine runs the Junos OS. Software processes that run on the
Routing Engine maintain the routing tables, manage the routing protocols used
on the router, control the router interfaces, control some chassis components,
and provide the interface for system management and user access to the
router.

Routing Engine Slots

You can install one or two Routing Engines in the router. Each Routing Engine
must be installed directly into an SCB. A USB port on the Routing Engine
accepts a USB memory device that allows you to load Junos OS. The Routing
Engines install into the front of the chassis in vertical slots directly into the
SCBs labeled 0 and 1. If two Routing Engines are installed, one functions as the
master and the other acts as the backup.

Routing Engine Interface Ports

Three ports, located on the right side of the routing engine, connect the
Routing Engine to one or more external devices on which system
administrators can issue Junos OS command-line interface (CLI) commands to
manage the router.
The ports with the indicated labels function as follows:

AUXConnects the Routing Engine to a laptop, modem, or other auxiliary

device through a serial cable with an RJ-45 connector.

CONSOLEConnects the Routing Engine to a system console through a serial

cable with an RJ-45 connector.

ETHERNET or MGMTConnects the Routing Engine through an Ethernet

connection to a management LAN (or any other device that plugs into an
Ethernet connection) for out-of-band management. The port uses an
autosensing RJ-45 connector to support 10-Mbps or 100-Mbps connections. Two
small LEDs on the bottom of the port indicate the connection in use: the LED
flashes yellow or green for a 10-Mbps or 100-Mbps connection, and the LED is
light green when traffic is passing through the port.

Otro aspecto de la modularidad de Junos es la separacin del plano de control y

el plano de forwarding o datos.

Los procesos que controlan los protocolos de enrutamiento y conmutacin

estn separados de los procesos que envan frames, paquetes o ambos a
travs del dispositivo que ejecuta el sistema operativo Junos. Este diseo le
permite afinar cada proceso para obtener el mximo rendimiento y fiabilidad.

El RE es el cerebro de la plataforma; Es responsable de realizar las

actualizaciones del protocolo y la administracin del sistema.

El RE mantiene las tablas de enrutamiento, bridging table (capa 2 y capa 3) y

la tabla principal de forwarding y se conecta al Packet Forwarding Engine (PFE)
a travs de un enlace interno.

El PFE es el componente de procesamiento central del plano de forwarding. El

PFE enva sistemticamente el trfico basado en su copia local de la tabla de
forwarding.

La tabla de reenvo de PFE es una copia sincronizada de la informacin creada

y proporcionada por el RE.

Plano de Control (control Plane) y Plano de Datos (Data plane)

Los conceptos de Plano de Control (control Plane) y Plano de Datos (Data
plane) se refieren a la separacin lgica, y en algunos escenarios fsica, del
trafico destinado a los Servicios (Data plane) y el trfico que ocupan los
Equipos de Red para gestionar, mantener y modificar el estado de la misma
(Control Plane).

Otro aspecto de la modularidad de Junos es la separacin del plano de control y

el plano de reenvo o datos.

Los procesos que controlan los protocolos de enrutamiento y conmutacin

estn separados de los procesos que envan cuadros, paquetes o ambos a
travs del dispositivo que ejecuta el sistema operativo Junos. Este diseo le
permite afinar cada proceso para obtener el mximo rendimiento y fiabilidad.

Resumen.