Cisco ASR 5000 Series Administration Manual page 437

StarOS Tasks
Task Description
hwctrl Hardware Controller
hwmgr Hardware Manager
inetd InterNET Service Daemon
ipsecctrl IPSec Controller
ipsecmgr IPSec Manager
kvctrl Key Value Controller
lagmgr Link Aggregation Group
Manager
[ASR 5500 only]
msgd Messenger Daemon
msgproxy Message Proxy
Function
The hwctrl task has several timers that manage polling loops for hardware
sensor readings, sensor threshold monitoring, and fan tray monitoring.
The hwmgr task runs on all cards in the chassis to read local accessible
hardware sensors and report them back to the hwctrl.
The subsystem responsible for starting most of the network services.
Listens for requests from connecting clients, such as FTP, SFTP, and telnet.
When a TCP packet or UDP packet arrives with a particular destination
port number, inetd launches the appropriate server program to handle the
connection.
Note: In release 20.0 and higher Trusted StarOS builds, FTP and Telnet
are not supported.
Started by SIT on system startup regardless of configuration.
Starts ipsecmgr tasks based on configuration and maintains its list for task
recovery.
Receives and maintains user configuration for IPSec.
Manages the configured IPSec crypto maps and its assignment to ipsecmgrs.
Interfaces with the vpnmgr task for required IPSec configuration parameters
such as IP Access Lists, IP pools, interface addresses, and interface state
notifications.
Created by the Session Controller, establishes and manages secure IKEv1,
IKEv2 and IPSec data tunnels.
Central key value store (kvstore) function that runs on the management
card. Its primary function is to support recovery and distribution functions.
Started by npuctrl on the demux card's primary MIO (ASR 5500) with a
facility level between CSP and npumgr to receive configuration/status
notification from npumgr and build global LAG database.
Exchanges control packets (LACP and Marker) over configured physical
ports with peers to reach agreement on an aggregation of links.
Implements the Name Service and related functions for the internal message
passing system.
The Messenger Proxy process handles broadcast messages send from any
single application (referred to as a client) to any facility which has one
instance per thread (referred to as the Target Facility).
One msgproxy task runs on each CPU complex on the DPCs (ASR 5500)
and SF Virtual Machine (VPC-DI).
Processes incoming broadcast messages from the Client processes, such
as sessctrl, distributes them to the correct Target Facility, such as sessmgr,
creates the correct responses and sends them back to the correct Client.
ASR 5500 System Administration Guide, StarOS Release 21.4
Platform Processes
405