1.

The Junos OS
-

Robust, Modular operating System

Compartmentalized into multiple software process
Each process runs in its own protected memory space.
One process can't directly interfere another
Entire system never fall down due to failure of single process
new features can be added with less likehood of breaking current functionality
Jonus kernel is based on the FreeBSD Unix operating system.

2. Single Software Train

- All platforms running the Jun OS use the same source code
- Core features work in a consistent manner across all platforms
- Features and services are configured and managed the same way
- Less setup task and ongoing ONM
- Use a code base that is updated at a slower packe. e.g. 12.1 in the code base
of Junos security devices
- New features introduced at a faster cadence within that code base . e.g. 12.1X
44, 12.1X45
3. Separation of Control and Forwarding
- Clean separation of control and forwarding functions
- So, can support many different platforms from a common code base
- Can deliver superior performance and highly reliable operation. e.g. Graceful
Routing Engine (GRES), nonstop active routing (NSR), unified in-service software
upgrades
- Control plane contain the RE - Routing Engine
- RE maintains the routing table, bridging table, and primary forwarding table
- RE performs protocol updates and system managemet that reside insie a protecte
d memory management
- RE is based on X86 or PowerPC architecture
- RE is connected to PFE through an internal link
- PFE is responsible for forwarding transit traffic through the Junos device
- PFE is built on ASIC ( Application specefic integrated circuits )
4. Routing Engine
- Handles all protocol processes.
- Handles all software processes
- That control interfaces, chasis components, system management, user access
- All protocol traffics are directed to the RE
- Controls the PFE by providing accurate, up-to-date layer 2 and layer 3 forward
ing table
- Receives hardware and env status messages from PFE and acts on this.
5. PFE
- Use a local copy of forwarding table to forward traffic.
- implements a number of advanced services - policing, stateless firewall, class
of service
- Provides other services through special interface cards
6. Transit Traffic
- Transit traffic is forwarded through the local system
- PFE uses the forwarding table provided by the RE to forward the transit traffi

c
- Transit traffic can be unicast or multicast
7. Exception Traffic
- Exception traffic is processed by the local system. Examples of Exception traf
fic
- Packets addressed to the chasis
- Such as routing protocol updates, Telnet sessions, ping and traceroute and rep
lies to traffic source from RE
- IP Packets with IP Options field
- Traffic that requires the generation of internet control message (ICMP)
- Exception traffic is rate limited on the internal link to protect the RE from
DoS attacks
- Control traffic is given preference when congestion exists
- Traffic requiring ICMP err messages responses is typically dealt by the PFE
8. Junos Platforms
-

ACX Series
LN Series
M Series
MX Series
PTX Series
T Series
EX Series
QFX Series
SRX Series