Interface Process; Snmp And Mib Ii Processes; Management Process; Routing Engine Kernel - Juniper G10 CMTS Hardware Manual

JUNOSg Internet Software Overview
•

Interface Process

•
•
•
•
•
•
•
•
•
•
•
•
•
•

SNMP and MIB II Processes

•
•
•
•
•
•
•
•

Management Process

•
•
•
•
•
•
•
•
•

Routing Engine Kernel

•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
60 JUNOSg 3.0 G10 CMTS Hardware Guide
The JUNOSg interface process allows you to configure and control the physical interface
devices and logical interfaces in the CMTS. You configure various interface properties such as
the interface location (the slot in which the module is installed and the port on the module),
the interface family (Layer 2 or Layer 3), and interface-specific properties. You can configure
the interfaces that are currently present in the CMTS, as well as interfaces that you might be
adding.
The JUNOSg interface process communicates with the interface process in the Packet
Forwarding Engine through the JUNOSg kernel, enabling the JUNOSg software to track the
status and condition of the CMTS's interfaces.
The JUNOSg Internet software supports the Simple Network Management Protocol (SNMP),
Versions 1, 2, and 3, which provides a mechanism for monitoring the state of the CMTS. This
software is controlled by the JUNOSg SNMP and MIB II processes, which consist of an SNMP
master agent and a MIB II agent.
Within the JUNOSg software, a management process starts and monitors all the other
software processes, as well as the command-line interface (CLI), which is the primary tool
you use to control and monitor the JUNOSg software. The management process starts all the
software processes and the CLI when the CMTS boots. If a software process terminates for
some reason, the management process makes all reasonable attempts to restart it.
The Routing Engine kernel provides the underlying infrastructure for all the JUNOSg software
processes. It also provides the link among the routing protocol process' routing table and the
Routing Engine's forwarding table. Additionally, it conducts communication with the Packet
Forwarding Engine, including keeping the Packet Forwarding Engine's copy of the forwarding
table synchronized with the master copy in the Routing Engine.