Cisco ASR1002 - ASR 1002 Router Software Configuration Manual page 27

Software Packaging and Architecture
Table 2
Process
Forwarding Manager
Pluggable Services
Shell Manager
SPA driver process
CPP driver process
CPP HA process
CPP SP process
IOS as a Process
In almost all previous Cisco router platforms, an overwhelming majority of the internal software
processes are run using Cisco IOS memory.
The Cisco ASR 1000 Series Routers introduce a distributed software architecture that moves many
operating system responsibilities out of the IOS process. In this architecture, IOS, which previously was
responsible for almost all of the internal software processes, now runs as one of many Linux processes
while allowing other Linux processes to share responsibility for running the router.
This architecture allows for better allocation of memory so the router can run more efficiently.
Furthermore, the Cisco ASR 1000 Series Routers has a command-line interface in diagnostic mode that
can be accessed in certain scenarios even if the IOS process fails. See the
Mode" section on page 7
Individual Processes (continued)
Purpose
Manages the downloading of
configuration to each of the
ESPs and the communication
of forwarding plane
information, such as statistics,
to the IOS process.
The integration point between
platform policy application,
such as authentication and the
IOS process.
Provides all user interface
features and handling related
to features in the nonIOS
image of the consolidated
package, which are also the
features available in diagnostic
mode when the IOS process
fails.
Provides an isolated process
driver for a specific SPA.
Manages the CPP hardware
forwarding engine on the ESP.
Manages HA state for the CPP
hardware forwarding engine.
Performs high-latency tasks
for the CPP-facing
functionality in the ESP
instance of the Forwarding
Manager process.
for information on diagnostic mode.
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
SubPackage
Affected FRUs Mapping
RP (one per software RPControl
redundancy instance per
RP). Maximum of two
instances per RP.
ESPBase
ESP (one per ESP)
RP (one per software RPControl
redundancy instance per
RP). Maximum of two
instances per RP.
RP (one instance per RPControl
RP)
SPA (one instance per SIPSPA
SPA per SIP)
ESP (one instance per ESPBase
ESP)
ESP (one instance per ESPBase
ESP)
ESP (one instance per ESPBase
ESP)
"Understanding the Diagnostic
Processes Overview
7