When a routing device first comes up, it connects to the configuration server component of the Cisco Networking Services configuration
agent by establishing a TCP connection through the use of the cns config initial command, a standard CLI command. The device issues a request and identifies itself by providing a unique configuration ID
to the configuration server.
When the Cisco Networking Services web server receives a request for a configuration file, it invokes the Java servlet and
executes the corresponding embedded code. The embedded code directs the Cisco Networking Services web server to access the
directory server and file system to read the configuration reference for this device (configuration ID) and template. The
Configuration Agent prepares an instantiated configuration file by substituting all the parameter values specified in the
template with valid values for this device. The configuration server forwards the configuration file to the Cisco Networking
Services web server for transmission to the routing device.
The Cisco Networking Services configuration agent accepts the configuration file from the Cisco Networking Services web server,
performs XML parsing, checks syntax (optional), and loads the configuration file. The routing device reports the status of
the configuration load as an event to which a network monitoring or workflow application can subscribe.
For more details on using the Cisco Cisco Networking Services configuration engine to automatically install the initial Cisco
Networking Services configuration, see the Cisco Networking Services Configuration Engine Administrator’s Guide