Contents
- A through E Commands
- announce config
- clear netconf
- cli (cns)
- cns aaa authentication
- cns config cancel
- cns config connect-intf
- cns config initial
- cns config notify
- cns config partial
- cns config retrieve
- cns connect
- cns dhcp
- cns event
- cns exec
- cns id
- cns image
- cns image password
- cns image retrieve
- cns image retry
- cns inventory
- cns message format notification
- cns mib-access encapsulation
- cns notifications encapsulation
- cns password
- cns template connect
- cns trusted-server
- config-cli
- discover (cns)
A through E Commands
announce config
To specify that an unsolicited configuration inventory is sent out by the CNS inventory agent at bootup, use the announce config command in CNS inventory configuration mode. To disable the sending of the configuration inventory, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2SX |
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use this command to limit inventory requests by the CNS inventory agent. When configured, the routing device details will be announced on the CNS event bus, but the routing device will not respond to any queries from the CNS event bus.
clear netconf
To clear network configuration protocol (NETCONF) statistics counters or NETCONF sessions and to free associated resources and locks, use the clear netconfcommand in privileged EXEC mode.
Command Default
NETCONF statistics counters are incremented and configured NETCONF sessions remain active.
Usage Guidelines
Use this command to clear NETCONF statistics counters to zero, to clear all or specified NETCONF sessions and to disconnect and free associated resources and locks.
Examples
The following example shows how to clear all NETCONF counters:
Router# clear netconf counters
Related Commands
|
Command |
Description |
|---|---|
|
debug netconf |
Enables debugging of NETCONF sessions. |
|
netconf lock-time |
Specifies the maximum time a NETCONF configuration lock is in place without an intermediate operation. |
|
netconf max-sessions |
Specifies the maximum number of concurrent NETCONF sessions allowed. |
|
netconf ssh |
Enables NETCONF over SSHv2. |
|
show netconf |
Displays NETCONF statistics counters and session information. |
cli (cns)
To specify the command lines of a Cisco Networking Services (CNS) connect template, use the cli command in CNS template connect configuration mode. To disable this configuration, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
12.3(2)XF |
This command was introduced. |
|
12.3(8)T |
This command was integrated into Cisco IOS Release 12.3(8)T. |
|
12.3(9) |
This command was integrated into Cisco IOS Release 12.3(9). The CNS connect variable ${dlci} is not supported in this release. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
First use the cns template connect command to enter CNS template connect configuration mode and define the name of the CNS connect template to be configured. Then use the cli command to specify the command lines of the CNS connect template.
 Note | Effective with Cisco IOS Releases 12.3(8)T and 12.3(9), and 12.2(33)SRA the config-cli and line-clicommands are replaced by the cli (cns)command. |
The command lines specified using the cli command can include CNS connect variables (see the table below). These variables act as placeholders within the command lines of a CNS connect template. Each variable is defined by an associated discover command. Before a CNS connect template that contains these variables is applied to a routerâs configuration, the variables are replaced by the values defined by their associated discover command. For example, if the discover interface serial command was configured, and you were able to connect to the CNS configuration engine using Serial0/0, then the cli ip route 0.0.0.0 0.0.0.0 ${interface} command would generate the cli ip route 0.0.0.0 0.0.0.0 serial0/0 command.
| Table 1 | Summary of the CNS Connect Variables |
|
Variable |
Description |
|---|---|
|
${line} |
The line type defined by the associated discover line line-type command. |
|
${controller} |
The controller type defined by the associated discover controller controller-type command. |
|
${interface} |
The interface type defined by the associated discover interface command. |
|
${dlci} |
The active DLCI defined by the associated discover dlci command. |
|
${next-hop} |
The next hop interface. This variable is identical to the ${interface}variable unless the discover dlci command has been configured. In this case, the ${next-hop} variable is identical to the ${interface}.{subinterface} variable, where the {subinterface} variable is specified by the discover dlci command. The ${next-hop} variable should only be used in the CNS connect templates after the last discover command has been entered. A typical use of this variable is to allow the default IP route to be configured to send traffic towards the CNS configuration engine. Note that the CNS configuration engine may not be on the same LAN as the router. Therefore, configuring a route to the CNS configuration engine may require deployment-specific knowledge. Common practice is to define a default route to the interface using the ip route command (for example, cli ip route 0.0.0.0 0.0.0.0 ${next-hop}). |
|
$$ |
A literal substitution of the $ symbol. |
Note | Effective with Cisco IOS Releases 12.3(8)T and 12.3(9), the &variable is replaced by the ${interface} variable. |
Examples
The following example shows how to configure a CNS connect template named template1:
Router(config)# cns template connect template-1 Router(config-templ-conn)# cli command-1 Router(config-templ-conn)# cli command-2 Router(config-templ-conn)# cli no command-3 Router(config-templ-conn)# exit Router(config)#
When the template1 template is applied, the following commands are sent to the routerâs parser:
command-1 command-2 no command-3
When the template1 template is removed from the routerâs configuration after an unsuccessful ping attempt to the CNS configuration engine, the following commands are sent to the routerâs parser:
no command-1 no command-2 command-3
Related Commands
|
Command |
Description |
|---|---|
|
cns connect |
Enters CNS connect configuration mode and defines the parameters of a CNS connect profile for connecting to the CNS configuration engine. |
|
cns template connect |
Enters CNS template connect configuration mode and defines the name of a CNS connect template. |
|
discover (cns) |
Defines the interface parameters within a CNS connect profile for connecting to the CNS configuration engine. |
|
template (cns) |
Specifies a list of CNS connect templates within a CNS connect profile to be applied to a routerâs configuration. |
cns aaa authentication
To enable Cisco Networking Services (CNS) Authentication, Authorization, and Accounting (AAA) options, use the cns aaa authenticationcommand in global configuration mode. To explicitly disable CNS AAA options, use the no form of this command.
Usage Guidelines
Use the cns aaa authenticationcommand to enable AAA when using CNS. When the cns aaa authenticationcommand is configured, CNS notification messages sent to the device are rejected if they do not have sender credentials. By default, no authentication is enabled. This command must be enabled to configure AAA authentication for CNS messages. Use the no cns aaa authentication command to explicitly disable AAA support when using CNS.
For more information about AAA authentication methods, see the â AAA Authentication Methods Configuration Task List â section in the â Configuring Authentication â chapter of the Cisco IOS Security Configuration Guide, Release 12.4.
cns config cancel
To remove a partial Cisco Networking Services (CNS) configuration from the list of outstanding partial configurations, use the cns config cancel command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.0(18)ST |
This command was integrated into Cisco IOS Release 12.0(18) ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22) S. |
|
12.2(8)T |
This command was implemented on additional platforms. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Incremental (partial) configurations take place in two steps:
- The configuration agent receives the partial configuration. It checks the configuration commands for syntax, publishes the success or failure of the read and syntax-check operation to the sync-status subject âcisco.cns.config.sync-status,â and stores the configuration.
- The configuration agent receives a second event message directing it to either apply or cancel the stored configuration.
Use the cns config cancel command in error scenarios where the second event message is not received and you need to remove the configuration from the list of outstanding configurations. Currently the maximum number of outstanding configurations is one.
Examples
The following example shows the process of checking the existing outstanding CNS configurations and canceling the configuration with the queue-id of 1:
Router# show cns config outstanding The outstanding configuration information: queue id identifier config-id 1 identifierREAD config_idREAD Router# cns config cancel 1 Router# show cns config outstanding The outstanding configuration information: queue id identifier config-id
Related Commands
|
Command |
Description |
|---|---|
|
cns config partial |
Starts the CNS configuration agent, which provides CNS configuration services to Cisco IOS clients. |
|
cns event |
Configures the CNS event gateway, which provides CNS event services to Cisco IOS clients. |
|
show cns config outstanding |
Displays information about incremental CNS configurations that have started but not yet completed. |
|
show cns event connections |
Displays the status of the CNS event agent connection. |
cns config connect-intf
To specify the interface for connecting to the Cisco Networking Services (CNS) configuration engine, use the cns config connect-intfcommand in global configuration mode. To disable this interface for the connection, use the no form of this command.
Syntax Description
|
type |
Type of connecting interface. |
|
number |
Number of the connecting interface. |
|
ping-interval |
(Optional) Specifies an interval between successive ping attempts. |
|
seconds |
(Optional) Interval between successive ping attempts, in seconds. Values are from 1 to 30. The default is 10. |
|
retries |
(Optional) Indicates that a ping will be retried a specified number of times. |
|
number |
(Optional) Number of times that a ping will be retried, in seconds. Values are from 1 to 30. The default is 5. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(8)T |
This command was introduced. |
|
12.3(8)T |
This command was replaced by the cns connectand cns template connect commands. |
|
12.3(9) |
This command was replaced by the cns connect and cns template connect commands. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
Usage Guidelines
Use this command to connect to the CNS configuration engine using a specific type of interface. You must specify the interface type but need not specify the interface number; the routerâs bootstrap configuration on the router finds the connecting interface, regardless of the slot in which the card resides or the modem dialout line for the connection, by trying different candidate interfaces or lines until it successfully pings the registrar.
Use this command to enter CSN Connect-interface configuration mode (config-cns-conn-if). Then use one of the following bootstrap-configuration commands to connect to the registrar for initial configuration:
- config-cli followed by commands that, used as is, configure the interface.
- line-cli followed by a command to configure modem lines to enable dialout and, after that, commands to configure the modem dialout line.
The config-cli command accepts the special directive character â&,â which acts as a placeholder for the interface name. When the configuration is applied, the & is replaced with the interface name. Thus, for example, if we are able to connect using FastEthernet0/0, the config-cli ip route 0.0.0.0 0.0.0.0 & command generates the ip route 0.0.0.0 0.0.0.0 FastEthernet0/0 command. Similarly, the config-virtual terminal line (vty) cns id & ipaddresscommand generates the cns id FastEthernet0/0 ipaddress command.
Examples
In the following example, the user connects to a configuration engine using the asynch interface and issues several commands:
Router(config)# cns config connect-intf Async Router(config-cns-conn-if)# config-cli encapsulation ppp Router(config-cns-conn-if)# config-cli ip unnumbered FastEthernet0/0 Router(config-cns-conn-if)# config-cli dialer rotary-group 0 Router(config-cns-conn-if)# line-cli modem InOut Router(config-cns-conn-if)# line-cli ...<other line commands>.... Router(config-cns-conn-if)# exit
These commands result in the following configuration being applied:
line 65 modem InOut . . . interface Async65 encapsulation ppp dialer in-band dialer rotary-group 0
Related Commands
|
Command |
Description |
|---|---|
|
cns config cancel |
Cancels an incremental two-phase synchronization configuration. |
|
cns config initial |
Starts the CNS configuration agent and initiates an initial configuration. |
|
cns config notify |
Detects CNS configuration changes and sends an event containing the previous and current configuration. |
|
cns config partial |
Starts the CNS configuration agent, which provides CNS configuration services to Cisco IOS clients. |
cns config initial
To enable the Cisco Networking Services (CNS) configuration agent and initiate a download of the initial configuration, use the cns config initialcommand in global configuration mode. To remove an existing cns config initial command from the running configuration of the routing device, use the no form of this command.
Syntax Description
|
host-name |
Hostname of the configuration server. |
|
ip-address |
IP address of the configuration server. |
|
encrypt |
(Optional) Uses a Secure Sockets Layer (SSL) encrypted link to the event gateway. |
|
port-number |
(Optional) Port number of the configuration service. The value is from 0 to 65535. The default is 80 with no encryption and 443 with encryption. |
|
page |
(Optional) Indicates that the configuration is located on a web page. |
|
page |
(Optional) Web page where the configuration is located. The default is /cns/config.asp. |
|
syntax-check |
(Optional) Turns on syntax checking. |
|
no-persist |
(Optional) Suppresses the default automatic writing to NVRAM of the configuration pulled as a result of issuing the cns config initialcommand. If not present, issuing the cns config initialcommand causes the resultant configuration to be automatically written to NVRAM. |
|
source |
(Optional) Specifies the source of CNS communications. |
|
interface name |
(Optional) Interface name of the source of CNS communications. |
|
status url |
(Optional) Sends an event to the specified URL via HTTP, either notifying successful completion of the configuration or warning that the configuration contained errors. |
|
event |
(Optional) Sends an event to the Event Bus notifying successful completion of the configuration or warning that the configuration contained errors. If the CNS event agent is not configured, the event will be saved until the CNS event agent is enabled. If the event keyword is not specified, a log message is sent to the console of the device after the configuration is complete. |
|
inventory |
(Optional) Sends an inventory of the line cards and modules in the router to the CNS configuration engine as part of the HTTP request. |
Command Default
The port number defaults to 80 with no encryption and 443 with encryption. Default web page of the initial configuration is /cns/config.asp.
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.0(18)ST |
This command was integrated into Cisco IOS Release 12.0(18)ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. |
|
12.2(2)XB |
This command was implemented on Cisco IAD2420 series Integrated Access Devices (IADs). |
|
12.2(8)T |
The sourceand encryptkeywords were added. |
|
12.3(1) |
The inventory keyword was added. |
|
12.3(8)T |
The status urlkeyword/argument pair was added. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use this command when a basic configuration--called a bootstrap configuration--is added to multiple routers before being deployed. When a router is initially powered (or each time a router is reloaded when the no-persistkeyword is used) the cns config initial command will cause a configuration file--called an initial configuration--for the router to be downloaded from the configuration server. The initial configuration can be unique for each router.
When the configuration has been received by the router, each line of the configuration will be applied in the same order as it was received. If the Cisco IOS parser has an error with one of the lines of the configuration, then all the configuration up to this point will be applied to the router, but none of the configuration beyond the error will be applied. If an error occurs, the command will retry until it successfully completes. Once the configuration has successfully completed the cns config initial command will be removed from the running configuration. By default, NVRAM will be updated except when the no-persistkeyword is configured.
When this command is used with the event keyword, a single message will be published on the event bus after the configuration is complete. The event bus will display one of the following status messages:
- cisco.mgmt.cns.config.complete--CNS configuration agent successfully applied the initial configuration.
- cisco.mgmt.cns.config.warning--CNS configuration agent fully applied the initial configuration but encountered possible semantic errors.
When this command is used with the statuskeyword, a single message will be published to the URL specified after the configuration is complete.
Examples
The following example shows how to enable the CNS configuration agent and initiate an initial configuration:
Router(config)# cns config initial 10.19.4.5 page /cns/config/first.asp
Related Commands
|
Command |
Description |
|---|---|
|
cns config connect-intf |
Specifies the interface for connecting to the CNS configuration engine. |
|
cns config notify |
Detects CNS configuration changes and sends an event containing the previous and current configuration. |
|
cns config retrieve |
Enables the CNS configuration agent and initiates a download of the initial configuration. |
|
cns event |
Configures the CNS event gateway, which provides CNS event services to Cisco IOS clients. |
|
show cns config status |
Displays information about the status of the CNS configuration agent. |
cns config notify
Note | Effective with Cisco IOS Release 15.1(1)T1, the cns config notify command is not available in Cisco IOS software. |
To notify Cisco Networking Services (CNS) agents of configuration changes on Cisco IOS devices, use the cns config notify command in global configuration mode. To disable notifications, use the no form of this command.
Cisco IOS Release 12.4(9)T or Later Releases
Syntax Description
Command History
|
Release |
Modification |
|---|---|
|
12.2(8)T |
This command was introduced. |
|
12.2(11)T |
The diff keyword was removed. |
|
12.3(1) |
The diff and old-format keywords were added. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.4(9)T |
The old-format and allkeywords were removed. The qlen number keyword/attribute pair were added. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
|
15.1(1)T1 |
This command was removed. |
Usage Guidelines
When the cns config notify command is enabled, commands entered in configuration mode are detected. If the all keyword is specified, the command is stored for future notification. If the diff keyword is specified, the command is stored for future notification if the software determines that the command will cause a configuration change. The diff keyword also allows the software to store information about the command including previous configuration states, source of the change (for example, a telnet user), and the time of configuration.
The stored information is formatted in XML and sent as part of a CNS config agent change notification event. A CNS configuration agent change notification event is sent to the CNS event bus when configuration mode is exited or no activity from that source has occurred for the configured interval time.
You must enable the CNS event agent using the cns event command before configuring this command. If the CNS event agent is not configured, the notification event will be queued and sent when the CNS event agent is enabled. If the CNS configuration notify queue is full, subsequent events are dropped and a âlostâ CNS configuration change notification is sent when the CNS event agent is enabled.
Use the no_cns_events for applications that already record configuration changes sent to the routing device through the CNS event bus.
Use the old-format keyword to generate XML output--only the entered command and previous configuration state--that is compatible with the versions of this commands when the diff keyword was removed.
Use the qlen number keyword/argument pair to send configuration changes to the CNS agent only after the specified number of changes has occurred.
Examples
The following example shows how to configure the CNS agent to receive configuration change notifications for all configuration commands:
Router(config)# cns config notify all
The following example shows how to configure the CNS agent to receive configuration change notifications only after 50 changes have been made:
Router(config)# cns config notify diff qlen 50
Related Commands
|
Command |
Description |
|---|---|
|
cns config cancel |
Cancels an incremental two-phase synchronization configuration. |
|
cns config connect-intf |
Specifies the interface for connecting to the CNS configuration engine. |
|
cns config initial |
Starts the CNS configuration agent and initiates an initial configuration. |
|
cns config partial |
Starts the CNS configuration agent, which provides CNS configuration services to Cisco IOS clients. |
|
cns event |
Enables and configures CNS event agent services. |
cns config partial
To start the Cisco Networking Services (CNS) configuration agent and accept a partial configuration, use the cns config partialcommand in global configuration mode. To shut down the CNS partial configuration agent, use the no form of this command.
Syntax Description
|
host-name |
Hostname of the configuration server. |
|
ip-address |
IP address of the configuration server. |
|
encrypt |
(Optional) Uses a Secure Sockets Layer (SSL) encrypted link between the router and the web server. |
|
port-number |
(Optional) Port number of the configuration service. The value is from 0 to 65535. The default is 80 with no encryption and 443 with encryption. |
|
source |
(Optional) Specifies the source of this device. |
|
interface name |
(Optional) Interface name to use as the source of this device. |
|
inventory |
(Optional) Sends an inventory of the line cards and modules in the router to the CNS configuration engine as part of the HTTP request. |
Command Default
The CNS configuration agent is not enabled to accept a partial configuration and the router does not request or receive updates.
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.0(18)ST |
This command was integrated into Cisco IOS Release 12.0(18)ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. |
|
12.2(2)XB |
This command was implemented on Cisco IAD2420 series Integrated Access Devices (IADs). |
|
12.2(8)T |
The sourcekeyword and encryptarguments were added. |
|
12.3(1) |
The inventory keyword was added. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.4(4)T |
This command was modified to include enhanced CNS error messages. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use this command to start the CNS partial configuration agent. You must enable the CNS event agent using the cns event command before configuring this command. The CNS event agent sends an event with the subject âcisco.mgmt.cns.config.loadâ to specify whether configuration data can be pushed to the CNS partial configuration agent or pulled from a configuration server by the CNS partial configuration agent.
In the push model, the event message delivers the configuration data to the partial configuration agent.
In the pull model, the event message triggers the partial configuration agent to pull the configuration data from the CNS configuration engine. The event message contains information about the CNS configuration engine, not the actual configuration data. The host name or IP address is the address of the CNS configuration engine from which the configuration is pulled. Use the cns trusted-server command to specify which CNS configuration engines can be used by the CNS partial configuration agent.
When the configuration has been received by the router, each line of the configuration will be applied in the same order as it was received. If the Cisco IOS parser has an error with one of the lines of the configuration, then all the configuration up to this point will be applied to the router, but none of the configuration beyond the error will be applied. If an error occurs, the command will retry until the configuration successfully completes. In the pull mode, the command will not retry after an error. By default, NVRAM will be updated except when the no-persistkeyword is configured.
A message will be published on the CNS event bus after the partial configuration is complete. The CNS event bus will display one of the following status messages:
- cisco.mgmt.cns.config.complete--CNS configuration agent successfully applied the partial configuration.
- cisco.mgmt.cns.config.warning--CNS configuration agent fully applied the partial configuration, but encountered possible semantic errors.
- cisco.mgmt.cns.config.failure(CLI syntax)--CNS configuration agent encountered a command line interface (CLI) syntax error and was not able to apply the partial configuration.
- cisco.mgmt.cns.config.failure(CLI semantic)--CNS configuration agent encountered a CLI semantic error and was not able to apply the partial configuration.
In Cisco IOS Releases 12.4(4)T, 12.2 (33)SRA, and later releases, a second message is sent to the subject âcisco.cns.config.resultsâ in addition to the appropriate message above. The second message contains both overall and line-by-line information about the configuration that was sent and the result of the action requested in the original message. If the action requested was to apply the configuration, then the information in the results message is semantic in nature. If the action requested was to check syntax only, then the information in the results message is syntactical in nature.
Examples
The following example shows how to configure the CNS partial configuration agent to accept events from the event gateway at 172.28.129.22. The CNS partial configuration agent will connect to the CNS configuration server at 172.28.129.22, port number 80. The CNS partial configuration agent requests are redirected to a configuration server at 172.28.129.40, port number 80.
Router(config)# cns event 172.28.129.22 Router(config)# cns trusted-server config 172.28.129.40 Router(config)# cns config partial 172.28.129.22
The following example shows an enhanced error message sent to the subject âcisco.mgmt.cns.config.resultsâ:
[2005-09-08 14:30:44]: subject=cisco.mgmt.cns.config.results.dvlpr-7200-6, message= <?xml version="1.0" encoding="UTF-8"?> <SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope"> <SOAP:Header> <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext" SOAP:mustUnderstand="true"> <wsse:UsernameToken> <wsse:Username>user1</wsse:Username> <wsse:Password>password1</wsse:Password> </wsse:UsernameToken> </wsse:Security> <CNS:cnsHeader Version="2.0" xmlns:CNS="http://www.cisco.com/management/cns/envelope"> <CNS:Agent>CNS_CONFIG</CNS:Agent> <CNS:Response> <CNS:correlationID>SOAP_IDENTIFIER</CNS:correlationID> </CNS:Response> <CNS:Time>2005-09-13T08:34:36.523Z</CNS:Time> </CNS:cnsHeader> </SOAP:Header> <SOAP:Body xmlns="http://www.cisco.com/management/cns/config"> <configResults version="2.0" overall="Success"> <configId>AAA</configId> </configResults> </SOAP:Body> </SOAP:Envelope>
Related Commands
|
Command |
Description |
|---|---|
|
cns config initial |
Starts the CNS configuration agent and initiates an initial configuration. |
|
cns event |
Enables and configures CNS event agent services. |
|
cns trusted-server |
Specifies a trusted server for CNS agents. |
|
show cns config outstanding |
Displays information about incremental CNS configurations that have started but are not yet completed. |
cns config retrieve
To enable the Cisco Networking Services (CNS) configuration agent and initiate a download of the initial configuration, use the cns config retrieve command in privileged EXEC mode.
Syntax Description
|
host-name |
Hostname of the configuration server. |
|
ip-address |
IP address of the configuration server. |
|
encrypt |
(Optional) Uses a Secure Sockets Layer (SSL) encrypted link to the event gateway. |
|
port-number |
(Optional) Port number of the configuration service. The value is from 0 to 65535. The default is 80 with no encryption and 443 with encryption. |
|
page |
(Optional) Indicates that the configuration is located on a web page. |
|
page |
(Optional) Web page where the configuration is located. The default is /cns/config.asp. |
|
overwrite-startup |
(Optional) Replaces the startup configuration file. Does not apply to the running configuration file. |
|
retry retries |
(Optional) Specifies the retry interval. The range is 0 to 100. The default is 0. |
|
interval seconds |
(Optional) Specifies the time in seconds, before the next attempt to request the configuration of a device from a configuration server. The range is 1 to 3600. |
|
syntax-check |
(Optional) Turns on syntax checking. |
|
no-persist |
(Optional) Suppresses the default automatic writing to NVRAM of the configuration pulled as a result of issuing the cns config retrievecommand. If not present, issuing the cns config retrievecommand causes the resultant configuration to be automatically written to NVRAM. |
|
source |
(Optional) Specifies the source of CNS communications. |
|
interface name |
(Optional) Interface name of the source of the configuration. |
|
status url |
(Optional) Sends the configuration the specified URL via HTTP, either notifying successful completion of the configuration or warning that the configuration contained errors. |
|
event |
(Optional) Sends an event to the CNS Event Bus stating successful completion of the configuration, a warning that the configuration contained errors, or a message noting that the configuration failed. If the CNS event agent is not configured, the event will be saved until the CNS event agent is enabled. If the event keyword is not specified, a log message is sent to the console of the device after the configuration is complete. |
|
inventory |
(Optional) Sends an inventory of the line cards and modules in the router to the CNS configuration engine as part of the HTTP request. |
Command Default
The port number defaults to 80 with no encryption and 443 with encryption. Default web page of the initial configuration is /cns/config.asp.
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.0(18)ST |
This command was integrated into Cisco IOS Release 12.0(18)ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. |
|
12.3(1) |
The inventory keyword was added. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.4(15)T |
The retry retries and interval seconds keywords and arguments were added. |
|
12.2(33)SRC |
This command was integrated into Cisco IOS Release 12.2(33)SRC. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use this command to request the configuration of a device from a configuration server. Use the cns trusted-server command to specify which configuration server can be used (trusted).
When the configuration has been received by the router, each line of the configuration will be applied in the same order as it was received. If the Cisco IOS parser has an error with one of the lines of the configuration, then all the configuration up to this point will be applied to the router, but none of the configuration beyond the error will be applied. If an error occurs, the command will not retry.
A single message will be published on the event bus after the partial configuration is complete. The event bus will display one of the following status messages:
- cisco.mgmt.cns.config.complete--CNS configuration agent successfully applied the configuration.
- cisco.mgmt.cns.config.warning--CNS configuration agent fully applied the configuration, but encountered possible semantic errors.
- cisco.mgmt.cns.config.failure--CNS configuration agent encountered an error and was not able to apply the configuration.
The cns config retrieve command can be used with Command Scheduler commands (for example, kron policy-list and cli commands) in environments where it is not practical to use the CNS event agent and the cns config partial command. Configured within the clicommand, the cns config retrieve command can be used to poll the configuration server to detect configuration changes.
You can use the optional retry and interval keywords to specify an amount of time in seconds to wait before attempting to retrieve a configuration from a trusted server. The number of retries is restricted to 100 to prevent the configuration agent from indefinitely attempting to reach an unreachable server. Use the keyboard combination Ctrl-Shift-6 to abort this command.
Examples
The following example shows how to request a configuration from a trusted server at 10.1.1.1:
Router(config)# cns trusted-server all 10.1.1.1 Router(config)# exit Router# cns config retrieve 10.1.1.1
The following example shows how to request a configuration from a trusted server at 10.1.1.1 and to configure a CNS configuration retrieve interval:
Router(config)# cns trusted-server all 10.1.1.1 Router(config)# exit Router# cns config retrieve 10.1.1.1 retry 50 interval 1500 CNS Config Retrieve Attempt 1 out of 50 is in progress Next cns config retrieve retry is in 1499 seconds (Ctrl-Shft-6 to abort this command). .. 00:26:40: %CNS-3-TRANSPORT: CNS_HTTP_CONNECTION_FAILED:10.1.1.1 -Process= "CNS config retv", ipl= 0, pid= 43 00:26:40: %CNS-3-TRANSPORT: CNS_HTTP_CONNECTION_FAILED -Process= "CNS config retv", ipl= 0, pid= 43......
Related Commands
|
Command |
Description |
|---|---|
|
cli |
Specifies EXEC CLI commands within a Command Scheduler policy list. |
|
cns config initial |
Starts the CNS configuration agent and initiates an initial configuration. |
|
cns trusted-server |
Specifies a trusted server for CNS agents. |
|
kron policy-list |
Specifies a name for a Command Scheduler policy and enters kron-policy configuration mode. |
|
show cns config status |
Displays information about the status of the CNS configuration agent. |
cns connect
To enter Cisco Networking Services (CNS) connect configuration mode and define the parameters of a CNS connect profile for connecting to the CNS configuration engine, use the cns connect command in global configuration mode. To disable the CNS connect profile, use the no form of this command.
Syntax Description
|
name |
Name of the CNS connect profile to be configured. |
|
retry-interval interval-seconds |
(Optional) Sets the interval (in seconds) between each successive attempt to ping the CNS configuration engine. The default value is 10 seconds. The valid range is 8 to 40 seconds. |
|
retries number-retries |
(Optional) Sets the number of times the CNS connect function will try to ping the CNS configuration engine. The default value is 3. |
|
timeout timeout-seconds |
(Optional) Sets the amount of time (in seconds) after which an interface is no longer used for ping attempts. The default value is 120 seconds. |
|
sleep sleep-seconds |
(Optional) Sets the amount of time (in seconds) before the first ping is attempted for each interface. This option provides time for the far end of a link to stabilize. The default value is 0 seconds. |
Command History
|
Release |
Modification |
|---|---|
|
12.3(2)XF |
This command was introduced. |
|
12.3(8)T |
This command was integrated into Cisco IOS Release 12.3(8)T. |
|
12.3(9) |
This command was integrated into Cisco IOS Release 12.3(9). |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. The ping-interval keyword was replaced by the retry-interval keyword. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
|
12.2(33)SRD |
This command was modified to allow users to reenter CNS connect configuration mode after configuring the CNS connect profile. |
Usage Guidelines
Use the cns connect command to enter CNS connect configuration mode and define the parameters of a CNS connect profile for connecting to the CNS configuration engine. Then use the following CNS connect commands to create a CNS connect profile:
- discover
- template
A CNS connect profile specifies the discover commands and associated template commands that are to be applied to a routerâs configuration. Multiple discover and templatecommands configured in a CNS connect profile are processed in the order in which they are entered.
Note | Effective with Cisco IOS Releases 12.3(8)T, 12.3(9), and 12.2(33)SRA the cns config connect-intfcommand is replaced by the cns connectand cns template connectcommands. |
Examples
The following example shows how to create a CNS connect profile named profile-1:
Router(config)# cns connect profile-1 Router(config-cns-conn)# discover interface Serial Router(config-cns-conn)# template template-1 Router(config-cns-conn)# exit
In this example, the following sequence of events occurs for each serial interface when the cns connect profile-1command is processed:
- Enter interface configuration mode and apply all commands in the template-1 template to the routerâs configuration.
- Try to ping the CNS configuration engine.
- If the ping is successful, then download pertinent configuration information from the CNS configuration engine and exit. The cns connect profile-1 command has completed its process.
- If the ping is unsuccessful, enter interface configuration mode and remove all commands in the template-1 template from the routerâs configuration. The cns connect profile-1command has failed to retrieve any configuration information from the CNS configuration engine.
Related Commands
|
Command |
Description |
|---|---|
|
cli (cns) |
Specifies the command lines of a CNS connect template. |
|
cns template connect |
Enters CNS template connect configuration mode and defines the name of a CNS connect template. |
|
discover (cns) |
Defines the interface parameters within a CNS connect profile for connecting to the CNS configuration engine. |
|
template (cns) |
Specifies a list of CNS connect templates within a CNS connect profile to be applied to a routerâs configuration. |
cns dhcp
To enable a Cisco Networking Service (CNS) with permission to process the incoming DHCP Option 43 message, use the cns dhcp command in global configuration mode. To disable this permission, use the no form of this command.
Usage Guidelines
If you need to pass CNS configuration commands to the router via the DHCP option 43 message, the cns dhcpcommand enables the DHCP option 43 message that the CNS processes. For more information, see the â Configuring Cisco Networking Services â module in the Cisco IOS Network Management Configuration Guide .
cns event
To configure the Cisco Networking Services (CNS) event gateway, which provides CNS event services to Cisco IOS clients, use the cns event command in global configuration mode. To remove the specified event gateway from the gateway list, use the no form of this command.
Syntax Description
|
hostname |
Hostname of the event gateway. |
||
|
ip-address |
IP address of the event gateway. |
||
|
encrypt |
(Optional) Uses a Secure Sockets Layer (SSL) encrypted link to the event gateway.
|
||
|
port-number |
(Optional) Port number for the event gateway.
|
||
|
backup |
(Optional) Indicates a backup gateway.
|
||
|
failover-time seconds |
(Optional) Specifies a time interval, in seconds, to wait for the primary gateway route after the route to the backup gateway is established.
|
||
|
keepalive seconds retry-count |
(Optional) Specifies a keepalive timeout, in seconds, and retry count. |
||
|
source interface-name |
(Optional) Indicates the interface name or IP address of the source for CNS communications. |
||
|
ipv4-address |
(Optional) IPv4 address of the source device. |
||
|
ipv6-address |
(Optional) IPv6 address of the source device. |
||
|
interface-name |
(Optional) Interface name of the source. |
||
|
clock-timeout time |
(Optional) Specifies the maximum time, in minutes, that the CNS event agent will wait for the clock to be set for transports (such as SSL) that require an accurate clock. The default is 10. |
||
|
reconnect-time time |
(Optional) Specifies the configurable upper limit of the maximum retry timeout, in seconds.
|
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)T |
This command was introduced. |
|
12.0(18)ST |
This command was integrated into Cisco IOS Release 12.0(18)ST. |
|
12.0(22)S |
This command was integrated into Cisco IOS Release 12.0(22)S. |
|
12.2(2)XB |
This command was integrated into Cisco IOS Release 12.2(2)XB and implemented on Cisco IAD2420 series Integrated Access Devices (IADs). |
|
12.2(8)T |
This command was modified. The encrypt, init-retry, source, and force-fmt1 keywords were added. |
|
12.3 |
This command was modified. The reconnect-timekeyword was added. |
|
12.3(1) |
This command was modified. The init-retry keyword was replaced with the failover-time keyword. The force-fmt1 keyword was removed. The clock-timeout keyword was added. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
|
15.0(1)M |
This command was modified in a release earlier than Cisco IOS Release 15.0(1)M. The ipv4-address and ipv6-address arguments were added. |
Usage Guidelines
The CNS event agent must be enabled before any of the other CNS agents are configured because the CNS event agent provides a transport connection to the CNS event bus for all other CNS agents. The other CNS agents use the connection to the CNS event bus to send and receive messages. The CNS event agent does not read or modify the messages.
The failover-time keyword is useful if you have a backup CNS event gateway configured. If the CNS event agent is trying to connect to the gateway and it discovers that the route to the backup is available before the route to the primary gateway, the seconds argument specifies how long the CNS event agent will continue to search for a route to the primary gateway before attempting to link to the backup gateway.
Unless you are using a bandwidth-constrained link, you should set a keepalive timeout and retry count. Doing so allows the management network to recover gracefully should a Cisco IE2100 configuration engine ever fail. Without the keepalive data, such a failure requires manual intervention on every device. The value of the seconds argument multiplied by the value of the retry-count argument determines the length of the idle time before the CNS event agent will disconnect and attempt to reconnect to the gateway. We recommend a minimum retry-count of two.
If the optional source keyword is used, the source IP address might be a secondary IP address of a specific interface to allow a management network to run on top of a production network.
If network connectivity between the Cisco IOS router running the CNS event agent and the gateway is absent, the event agent goes into an exponential backoff retry mode and gets stuck at the maximum limit (which may be hours). The reconnect-time keyword allows a configurable upper limit of the maximum retry timeout.
If you configure CNS passwords using the cns password command, existing event connections will be closed and reopened.
cns exec
To enable and configure the Cisco Networking Services (CNS) exec agent, which provides CNS exec agent services to Cisco IOS clients, use the cns exec command in global configuration mode. To disable the use of CNS exec agent services, use the no form of this command.
Syntax Description
|
encrypt |
(Optional) Uses a Secure Sockets Layer (SSL) encrypted link to the exec agent server.
|
||
|
port-number |
(Optional) Port number for the exec server. The default is 80. |
||
|
source |
(Optional) Specifies the use of an IP address defined by the ip-address argument as the source for CNS exec agent communications. |
||
|
ipv4-address |
(Optional) IPv4 address of the source device. |
||
|
ipv6-address |
(Optional) IPv6 address of the source device. |
||
|
interface-type |
(Optional) Interface type. For more information, use the question mark (?) online help function. |
||
|
number |
(Optional) Interface or subinterface number. For more information about the numbering syntax for your networking device, use the question mark (?) online help function. |
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
|
15.0(1)M |
This command was modified in a release earlier than Cisco IOS Release 15.0(1)M. The ipv4-address and ipv6-address arguments were added. |
Usage Guidelines
The CNS exec agent allows a remote application to execute an EXEC mode command-line interface (CLI) command on a Cisco IOS device by sending an event message containing the command. A restricted set of EXEC CLI commands--show commands--is supported.
In previous Cisco IOS releases, the CNS exec agent was enabled when the CNS configuration agent was enabled through the cns config partial command.
cns id
To set the unique event ID, config ID, or image ID used by Cisco Networking Services (CNS), use the cns id command in global configuration mode. To set the identifier to the hostname of the Cisco IOS device, use the no form of this command.
Syntax Description
|
type number |
Type of interface (for example, ethernet, group-async, loopback, or virtual-template) and the interface number.
|
|
ipaddress |
Uses the IP address specified in the type numberarguments as the unique ID. |
|
mac-address |
Uses the MAC address specified in the type numberarguments as the unique ID. |
|
hardware-serial |
Uses the hardware serial number as the unique ID. |
|
hostname |
Uses the hostname as the unique ID. This is the system default. |
|
string string |
Uses an arbitrary text string--typically the hostname--as the unique ID. |
|
udi |
Uses the product Unique Device Identifier (UDI) as the unique ID. |
|
event |
(Optional) Sets this ID to be the event ID value, which is used to identify the Cisco IOS device for CNS event services.
|
|
image |
(Optional) Sets this ID to be the image ID value, which is used to identify the Cisco IOS device for CNS image agent services.
|
Command History
|
Release |
Modification |
|---|---|
|
12.2(2)XB |
This command was introduced on Cisco IAD2420 series IADs. |
|
12.2(8)T |
This command was integrated into Cisco IOS Release 12.2(8)T. The dns-reverse keyword was removed. |
|
12.3(1) |
The optional image keyword was added to set an image ID. |
|
12.3(14)T |
The udi keyword was added to use the product UDI as the unique ID. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use this command to set the unique ID for the CNS configuration agent, which then pulls the initial configuration template to the Cisco IOS device during bootup.
You can set one or all three IDs: the config ID value for CNS configuration services, the event ID value for CNS event services, and the image ID value for CNS image agent services. To set all values, use the command three times.
An IP address can be assigned to an interface, and cns id global configuration command can use this IP address as the CNS ID string.
When CNS ID configuration fails, the system defaults to the hostname of the Cisco IOS device as the unique ID.
To set the CNS event ID to the hostname of the Cisco IOS device, use the no form of this command with the event keyword. To set the CNS config ID to the hostname of the Cisco IOS device, use the no form of this command without the event keyword. To set the CNS image ID to the hostname of the Cisco IOS device, use the no form of this command with the image keyword.
Unique Device Identifier
Each identifiable Cisco product is an entity, as defined by the Entity MIB (RFC 2737) and its supporting documents. Some entities, such as a chassis, will have subentities like slots. An Ethernet switch might be a member of a superentity, such as a stack. Most Cisco entities that are orderable products will leave the factory with an assigned UDI. The UDI information is printed on a label that is affixed to the physical hardware device, and it is also stored electronically on the device in order to facilitate remote retrieval. To use UDI retrieval, the Cisco product in use must be UDI-enabled.
A UDI consists of the following elements:
- Product identifier (PID)
- Version identifier (VID)
- Serial number (SN)
The PID is the name by which a product can be ordered; historically, it has been called the âProduct Nameâ or âPart Number.â This identifier is the one to use to order an exact replacement part.
The VID is the version of the product. When a product is revised, the VID is incremented according to a rigorous process derived from Telcordia GR-209-CORE, an industry guideline that governs product change notices.
The SN is the vendor-unique serialization of the product. Each manufactured product carries a unique serial number assigned at the factory, which cannot be changed in the field. The serial number is used to identify an individual, specific instance of a product.
Note | The udi keyword will create an ID consisting of the PID, VID, and SN values. Any spaces in PID, VID, and SN values will be removed. To view the UDI for this product, use the show inventory command. |
Examples
The following example shows how to pass the hostname of the Cisco IOS device as the config ID value:
Router(config)# cns id hostname
The following example shows how to pass the hardware serial number of the Cisco IOS device as the event ID value:
Router(config)# cns id hardware-serial event
The following example shows how to pass the UDI as the event ID value:
Router(config)# cns id udi event
The following example shows how to pass the IP address of Ethernet interface 0/1 as the image ID value:
Router(config)# cns id ethernet 0/1 ipaddress image
cns image
To configure the CNS image agent services, use the cns imagecommand in global configuration mode. To disable the use of CNS image agent services, use the no form of this command.
Syntax Description
|
server |
(Optional) Specifies an image distribution server to contact for information about an updated image to be downloaded. |
|
server-url |
(Optional) URL used to contact an image distribution server. An IP address or domain name can be used. |
|
status |
(Optional) Specifies that any status messages generated by CNS image agent operations will be sent to the URL specified by the status-url argument. |
|
status-url |
(Optional) URL of a web server to which status messages are written. |
Command Default
When configured, the CNS image agent always listens for image events on the CNS Event Bus server.
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(31)SB2 |
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
|
12.2(33)SRB |
This command was integrated into Cisco IOS Release 12.2(33)SRB. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use the cns image command to start the CNS image agent process and to listen for image-related events on the CNS Event Bus.
If the optional server details are specified, the CNS image agent uses the server URL to contact the image management server. If no server details are specified, the URL for the image server must be supplied using one of the following three methods. The first method is to specify the image server using the server options on the cns image retrieve command. The second method is to use the server configured by the CNS event agent and stored as an image server event that can be received from the CNS Event Bus. The third method does not require a server URL because it uses CNS Event Bus mode.
If the optional status details are not specified, the status messages are sent as events on the CNS Event Bus.
cns image password
To configure a password to use with the Cisco Networking Services (CNS) image agent services, use the cns image password command in global configuration mode. To disable the use of a password, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(31)SB2 |
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
|
12.2(33)SRB |
This command was integrated into Cisco IOS Release 12.2(33)SRB. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use this command to create a password that is sent with the image ID in all CNS image agent messages. The recipient of these messages can use this information to authenticate the sending device. This password may be different from the username and password used for HTTP basic authentication configured with other CNS image agent commands.
cns image retrieve
To contact a Cisco Networking Services (CNS) image distribution server and download a new image if a new image exists, use the cns image retrievecommand in privileged EXEC mode.
Syntax Description
|
server |
(Optional) Specifies an image distribution server to contact for information about an updated image to be downloaded. |
|
server-url |
(Optional) URL used to contact an image distribution server. |
|
status |
(Optional) Specifies that any status messages generated by this command will be sent to the URL specified by the status-url argument. |
|
status-url |
(Optional) URL of a web server to which status messages are written. |
Command Default
An error occurs when a cns image server has not previously been configured in global configuration mode.
Usage Guidelines
When the cns image retrieve command is issued in privileged EXEC mode without the server keyword and server-url argument, an error occurs.
When a cns image server has been configured and the cns image retrieve command is issued with no server keyword and server-url argument, the server path configured in the cns image command is used.
When the cns imagecommand is issued in global configuration mode with the optional server keyword, no keywords are required and no error occurs when you issue the cns image retrieve command in privileged EXEC mode.
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(31)SB2 |
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
|
12.2(33)SRB |
This command was integrated into Cisco IOS Release 12.2(33)SRB. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
You must enable the CNS image agent services using the cns image command before configuring this command.
Use this command to poll an image distribution server and download a new image to the Cisco IOS device if a new image exists.
Examples
The following example shows how to configure the CNS image agent to access the image distribution server at 10.19.2.3 and download a new image if a new image exists:
Router# cns image retrieve server https://10.20.2.3:8080/cns/imageserver/ status https://10.20.2.3:8080/cns/imageserver/messages /
cns image retry
To set the Cisco Networking Services (CNS) image upgrade retry interval, use the cns image retrycommand in global configuration mode. To restore the default value, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(31)SB2 |
This command was integrated into Cisco IOS Release 12.2(31)SB2. |
|
12.2(33)SRB |
This command was integrated into Cisco IOS Release 12.2(33)SRB. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use this command to set an interval after which the CNS image agent will retry an image upgrade operation if the original upgrade attempt failed.
cns inventory
To enable the CNS inventory agent--that is, to send an inventory of the routerâs line cards and modules to the CNS configuration engine--and enter CNS inventory mode, use the cns inventory command in global configuration mode. To disable the CNS inventory agent, use the no form of this command.
Usage Guidelines
Use this command with the announce config and transport event CNS inventory configuration mode commands to specify when to notify the CNS configuration engine of changes to the routerâs port-adaptor and interface inventory. A transport must be specified in CNS inventory configuration mode before any of the CNS inventory commands are executed.
Examples
The following example shows how to enable the CNS inventory agent and enter CNS inventory configuration mode:
Router(config)# cns inventory
Router(cns_inv)#
Related Commands
|
Command |
Description |
|---|---|
|
announce config |
Species that an unsolicited configuration inventory is sent out by the CNS inventory agent at bootup. |
|
cns config initial |
Starts the CNS configuration agent and initiates an initial configuration. |
|
transport event |
Species that inventory events are sent out by the CNS inventory agent. |
cns message format notification
To configure the message format for notification messages from a Cisco Networking Services (CNS) device, use the cns message format notificationcommand in global configuration mode. To unconfigure a configured message format for notification messages from a CNS device, use the no form of this command.
Usage Guidelines
Use this command to configure a CNS agent to use the SOAP format for CNS notification messages. SOAP message formats are supported by default. If the Cisco IOS device receives a request in the non-SOAP message format, the response will be sent in the non-SOAP format. If the Cisco IOS device receives a request in the SOAP format, the response will be sent in the SOAP format. By default, notification messages that are sent without any corresponding request messages will be sent in both SOAP and non-SOAP formats.
When this command is configured, received CNS notification messages that do not conform to the configured message format are rejected.
If the cns aaa authentication notificationcommand is already configured, then the senderâs credentials will be authenticated. If the cns message format notificationcommand is configured, then the notification messages will be sent as per the configured version number. The default configuration is the legacy non-SOAP format.
cns mib-access encapsulation
To specify whether Cisco Networking Services (CNS) should use nongranular (Simple Network Management Protocol [SNMP]) or granular (Extensible Markup Language [XML]) encapsulation to access MIBs, use the cns mib-access encapsulation command in global configuration mode. To disable the currently specified encapsulation, use the no form of this command.
cns notifications encapsulation
To specify whether Cisco Networking Services (CNS) notifications should be sent using nongranular (Simple Network Management Protocol [SNMP]) or granular (Extensible Markup Language [XML]) encapsulation, use the cns notifications encapsulation command in global configuration mode. To disable the currently specified encapsulation, use the no form of this command.
cns password
To configure a Cisco Networking Services (CNS) password, use the cns password command in global configuration mode. To disable the CNS password, use the no form of this command.
Usage Guidelines
You must configure the CNS password the first time a router is deployed, and the CNS password must be the same as the bootstrap password set on the Configuration Engine (CE). If both the router and the CE bootstrap password use their default settings, a newly deployed router will be able to connect to the CE.
Once connected, the CE will change the CNS password from the bootstrap password to a random password. Network administrators must ensure not to change the CNS password. If the CNS password is changed, connectivity to the CE will be lost.
cns template connect
To enter Cisco Networking Services (CNS) template connect configuration mode and define the name of a CNS connect template, use the cns template connect command in global configuration mode. To disable the CNS connect template, use the no form of this command.
Command History
|
Release |
Modification |
|---|---|
|
12.3(2)XF |
This command was introduced. |
|
12.3(8)T |
This command was integrated into Cisco IOS Release 12.3(8)T. |
|
12.3(9) |
This command was integrated into Cisco IOS Release 12.3(9). |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
|
12.2(33)SRD |
This command was modified to allow users to reenter the CNS connect configuration mode after configuring the CNS connect profile. |
Usage Guidelines
Use the cns template connect command to enter CNS template connect configuration mode and define the name of the CNS connect template to be configured. Then use the cli command to specify the command lines of the CNS connect template.
Note | When you create a CNS connect template, you must enter the exit command to complete the configuration of the template and exit from CNS template connect configuration mode. This requirement was implemented to prevent accidentally entering a command without the cli command. |
Note | Effective with Cisco IOS Releases 12.3(8)T, 12.3(9), and 12.2(33)SRA the cns config connect-intfcommand is replaced by the cns connectand cns template connect commands. |
Examples
The following example shows how to configure a CNS connect template named template1:
Router(config)# cns template connect template1 Router(config-templ-conn)# cli command-1 Router(config-templ-conn)# cli command-2 Router(config-templ-conn)# cli no command-3 Router(config-templ-conn)# exit
When the template1 template is applied, the following commands are sent to the routerâs parser:
command-1 command-2 no command-3
When the template1 template is removed from the routerâs configuration after an unsuccessful ping attempt to the CNS configuration engine, the following commands are sent to the routerâs parser:
no command-1 no command-2 command-3
Related Commands
|
Command |
Description |
|---|---|
|
cli (cns) |
Specifies the command lines of a CNS connect template. |
|
cns connect |
Enters CNS connect configuration mode and defines the parameters of a CNS connect profile for connecting to the CNS configuration engine. |
|
discover (cns) |
Defines the interface parameters within a CNS connect profile for connecting to the CNS configuration engine. |
|
template (cns) |
Specifies a list of CNS connect templates within a CNS connect profile to be applied to a routerâs configuration. |
cns trusted-server
To specify a trusted server for Cisco Networking Services (CNS) agents, use the cns trusted-server command in global configuration mode. To disable the use of a trusted server for a CNS agent, use the no form of this command.
Syntax Description
|
all-agents |
Specifies a trusted server for all CNS agents. |
|
config |
Specifies a trusted server for CNS config agent. |
|
event |
Specifies a trusted server for CNS event agent. |
|
exec |
Specifies a trusted server for CNS exec agent. |
|
image |
Specifies a trusted server for CNS image agent. |
|
name |
A string that specifies the hostname or IP address of the trusted server. |
Command Default
By default, only the implicit server strings are trusted.
The configuration of the CNS event agentâs server string through the command-line interface (CLI) results in an implicit trust by all CNS agents. For the other CNS agents, the configuration of a server string using the CLI results in an implicit trust of the server for the specified agent. For example, cns exec 10.2.1.2 implies the string 10.2.1.2 is implicitly trusted by the exec agent, and specifying cns event 10.4.2.2 implies the string 10.4.2.2 is implicitly trusted by all the CNS agents.
Command History
|
Release |
Modification |
|---|---|
|
12.3(1) |
This command was introduced. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
|
12.2(33)SB |
This command was integrated into Cisco IOS Release 12.2(33)SB. |
|
12.2(33)SXI |
This command was integrated into Cisco IOS Release 12.2(33)SXI. |
Usage Guidelines
Use the cns trusted-server command to specify a trusted server for an individual CNS agent or all the CNS agents. In previous Cisco IOS Releases, CNS agents could connect to any server and this could expose the system to security violations. An attempt to connect to a server not on the list results in an error message being displayed and an authentication failure reply extensible markup language (XML). For backwards compatibility the configuration of a server address using the configuration CLI for a CNS agent results in an implicit trust of the server for the specified agent.
Use this command when a CNS agent will redirect its response to a server address that is not explicitly configured on the command line for the specific CNS agent. For example, the CNS exec agent may have one server configured but receive a message from the CNS Event Bus that overrides the configured server. The new server address string has not been explicitly configured so the new server address is not a trusted server. An error will be generated when the CNS exec agent tries to respond to this new server address unless the cns trusted-server command has been configured for the new server address string.
The cns trusted-server command does not use Domain Name System (DNS). Instead a string comparison is done between the configured and implicit trusted servers and requested redirected server address.
Examples
The following example shows how to configure server 10.19.2.5 as a trusted server for the CNS event agent:
Router# cns trusted-server event 10.19.2.5
The following example shows how to configure server 10.2.2.8, which maps though DNS to host.somedomain.com as a trusted server for all CNS agents:
Router# cns trusted-server all-agents 10.2.2.8 Router# cns trusted-server all-agents host Router# cns trusted-server all-agents host.somedomain.com
The following example shows how to configure the string 10.2.2.8 as an implicit trusted server for the CNS image agent:
Router# cns image server 10.2.2.8 status 10.2.2.8
config-cli
Note | Effective with Cisco IOS Releases 12.3(8)T and 12.3(9), the config-clicommand is replaced by the cli (cns)command. See the cli (cns) command for more information. |
To connect to the Cisco Networking Services (CNS) configuration engine using a specific type of interface, use the config-clicommand in CNS Connect-interface configuration mode.
Syntax Description
|
type |
Type of interface. Indicates from which interface the IP or MAC address should be retrieved in order to define the unique ID. |
|
number |
(Optional) Interface number. Indicates from which interface the IP or MAC address should be retrieved in order to define the unique ID. |
|
interface-config-cmd |
Command that configures the interface. The type argument must be configured before other interface configuration commands. |
Command History
|
Release |
Modification |
|---|---|
|
12.2(8)T |
This command was introduced on Cisco 2600 series and Cisco 3600 series routers. |
|
12.3(8)T |
This command was replaced by the cli (cns)command. |
|
12.3(9) |
This command was replaced by the cli (cns)command. |
|
12.2(25)S |
This command was integrated into Cisco IOS Release 12.2(25)S. |
|
12.2(33)SRA |
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
Begin by using the cns config connect-intf command to enter CNS Connect-interface configuration (config-cns-conn-if) mode. Then use either this or its companion CNS bootstrap-configuration command to connect to the CNS configuration engine for initial configuration:
- config-cli connects to the registrar using a specific type of interface. You must specify the interface type but need not specify the interface number; the routerâs bootstrap configuration finds the connecting interface, regardless of the slot in which the card resides, by trying different candidate interfaces until it can ping the configuration engine.
- line-cli connects to the registrar using modem dialup lines.
Immediately after either of the commands, enter additional configuration commands as appropriate.
Examples
The following example enters CNS Connect-interface configuration mode, connects to a configuration engine using an asynchronous interface, and issues a number of commands:
Router(config)# cns config connect-intf Async Router(config-cns-conn-if)# config-cli encapsulation ppp Router(config-cns-conn-if)# config-cli ip unnumbered FastEthernet0/0 Router(config-cns-conn-if)# config-cli dialer rotary-group 0 Router(config-cns-conn-if)# line-cli modem InOut Router(config-cns-conn-if)# line-cli ...<other line commands>.... Router(config-cns-conn-if)# exit
These commands apply the following configuration:
line 65 modem InOut . . . interface Async65 encapsulation ppp dialer in-band dialer rotary-group 0
discover (cns)
To define the interface parameters within a Cisco Networking Services (CNS) connect profile for connecting to the CNS configuration engine, use the discover command in CNS connect configuration mode. To disable this functionality, use the no form of this command.
Syntax Description
|
line |
Indicates that a line is used to connect to the CNS configuration engine. When the line line-typekeyword and argument are specified, all the lines that create an interface that match the specified line-type argument are discovered. The CNS connect templates associated with the discover line line-type command are applied in line configuration mode. |
||
|
line-type |
Type of line used to connect to the CNS configuration engine. |
||
|
controller |
Indicates that a controller is used to connect to the CNS configuration engine. When the controller controller-typekeyword and argument are specified, all the controllers that create an interface that match the specified controller-type argument are discovered. The CNS connect templates associated with the discover controller controller-type command are applied in controller configuration mode. |
||
|
controller-type |
Type of controller used to connect to the CNS configuration engine. |
||
|
interface |
Indicates that an interface is used to connect to the CNS configuration engine. If the discover interface interface-typecommand is the first discover command configured in a CNS connect profile, the interfaces that match the specified interface-type argument are discovered. If the discover interface interface-typecommand is configured after the discover line line-type or discover controller controller-type commands in a CNS connect profile, the specified interface-typeargument is ignored. Instead, the CNS connect templates associated with the discover interface command are applied to all the interfaces associated with the preceding discover line line-type or discover controller controller-type commands. The CNS connect templates associated with the discover interface interface-typecommand are applied in interface configuration mode. |
||
|
interface-type |
(Optional) Type of interface used to connect to the CNS configuration engine. |
||
|
dlci |
Active DLCIs to be used for connecting to the CNS configuration engine. When this keyword is defined, all the active DLCIs are discovered on the interface specified by the preceding discover interface interface-type command. A Frame Relay LMI message will return a list of active DLCIs. Active DLCIs can only be discovered on interfaces configured with Frame Relay. Therefore, the location of the discover dlci command in a CNS connect profile is important. It must be entered after the interfaces have been configured with Frame Relay. The CNS connect templates associated with the discover dlci command are applied in subinterface (point-to-point) configuration mode. Defines the CNS connect variable ${dlci} and ${next-hop}.
|
||
|
subinterface |
(Optional) Indicates that a point-to-point subinterface is used to perform a search for active DLCIs. If a number is not specified, the default value is 9999. |
||
|
subinterface-number |
(Optional) Number of the point-to-point subinterface used to perform a search for active DLCIs. |
Command History
|
Release |
Modification |
|---|---|
|
12.3(2)XF |
This command was introduced. |
|
12.3(8)T |
This command was integrated into Cisco IOS Release 12.3(8)T. |
|
12.3(9) |
This command was integrated into Cisco IOS Release 12.3(9). The dlci subinterface subinterface-number keywords and argument and the CNS connect variable ${dlci} are not supported in this release. |
Usage Guidelines
First use the cns connect command to enter CNS connect configuration mode and define the parameters of a CNS connect profile for connecting to the CNS configuration engine. Then use the following CNS connect commands to create a CNS connect profile:
A CNS connect profile specifies the discover commands and associated template commands to apply to a routerâs configuration. The first discover command in a CNS connect profile defines the scope of interfaces to be searched and used to perform the ping iterations for connecting to the CNS configuration engine. Subsequent discover commands limit this scope.
The search is based on discovering all the interfaces that match the specified line, controller, or interface type. The search is case-insensitive and allows for abbreviations. For example, the discover interface Serial, discover interface Ser, discover interface serial, and discover interface ser commands all match the serial interface.
Each discover command must have at least one unique CNS connect template associated with it. Specifically, the template command must be configured after configuring the discover command. The discover command specifies the configuration mode in which the CNS connect templates (specified by the template command that is associated with the discover command) are to be applied. When multiple discover and templatecommands are configured in a CNS connect profile, they are processed in the order in which they are entered.
The table below provides a summary of the interface parameters that can be defined using the discover command.
| Table 2 | Summary of the discover Commands |
|
discover Command |
Description |
Associated CNS Connect Variable |
Configuration Mode in Which CNS Connect Templates Are Applied |
Prerequisite discover Command |
Required Subsequent discover Command |
|---|---|---|---|---|---|
|
discover line line-type |
Discovers all the lines that create an interface that match the specified line-type argument. |
${line} |
Line |
-- |
discover interface interface-type |
|
discover controller controller-type |
Discovers all the controllers that create an interface that match the specified controller-type argument. |
${controller} |
Controller |
-- |
discover interface interface-type |
|
discover interface [interface-type] |
${interface} ${next-hop} |
Interface |
-- |
-- |
|
|
discover dlci [subinterface subinterface-number] |
Discovers all active DLCIs on the interface specified by the preceding discover interface command. |
${dlci} ${next-hop} |
Subinterface (point-to-point) |
discover interface interface-type |
-- |
CNS connect variables can be used as placeholders within a CNS connect template configuration. Each variable is defined by an associated discover command (see the table above and the table below). Before a CNS connect template that contains these variables is applied to a routerâs configuration, the variables are replaced by the values defined by their associated discover command. For example, if the discover interface serial command was configured, and you were able to connect to the CNS configuration engine using Serial0/0, the cli ip route 0.0.0.0 0.0.0.0 ${interface} command would generate the cli ip route 0.0.0.0 0.0.0.0 serial0/0 command.
| Table 3 | Summary of the CNS Connect Variables |
|
Variable |
Description |
|---|---|
|
${line} |
The line type defined by the associated discover line line-type command. |
|
${controller} |
The controller type defined by the associated discover controller controller-type command. |
|
${interface} |
The interface type defined by the associated discover interface command. |
|
${dlci} |
The active DLCI defined by the associated discover dlci command. |
|
${next-hop} |
The next hop interface. This variable is identical to the ${interface}variable unless the discover dlci command has been configured. In this case, the ${next-hop} variable is identical to the ${interface}.{subinterface} variable, where the {subinterface} variable is specified by the discover dlci command. The ${next-hop} variable should only be used in the CNS connect templates after the last discover command has been entered. A typical use of this variable is to allow the default IP route to be configured to send traffic towards the CNS configuration engine. Note that the CNS configuration engine may not be on the same LAN as the router. Therefore, configuring a route to the CNS configuration engine may require deployment-specific knowledge. Common practice is to define a default route to the interface using the ip route command (for example, cli ip route 0.0.0.0 0.0.0.0 ${next-hop}). |
|
$$ |
A literal substitution of the $ symbol. |
Note | Effective with Cisco IOS Releases 12.3(8)T and 12.3(9), the &variable is replaced by the ${interface} variable. |
Examples
The following example shows how to create a CNS connect profile named EG:
Router (config)# cns connect EG Router (config-cns-conn)# discover controller T1 Router (config-cns-conn)# template timeslot-1 Router (config-cns-conn)# discover interface Router (config-cns-conn)# template frame Router (config-cns-conn)# exit Router (config)#
In this example, the following sequence of events occur for each T1 controller when the cns connect EGcommand is processed:
- Enter controller configuration mode and apply all commands in the timeslot-1 template to the routerâs configuration.
- For each interface associated with each T1 controller:
- Enter interface configuration mode and apply all commands in the frame template to the routerâs configuration.
- Try to ping the CNS configuration engine.
- If the ping is successful, then download pertinent configuration information from the CNS configuration engine and exit. The cns connect EGcommand has completed its process.
- If the ping is unsuccessful, enter interface configuration mode and remove all commands in the frame template from the routerâs configuration.
- Enter controller configuration mode and remove all commands in the timeslot-1 template from the routerâs configuration. The cns connect EGcommand has failed to retrieve any configuration information from the CNS configuration engine.
Related Commands
|
Command |
Description |
|---|---|
|
cli (cns) |
Specifies the command lines of a CNS connect template. |
|
cns connect |
Enters CNS connect configuration mode and defines the parameters of a CNS connect profile for connecting to the CNS configuration engine. |
|
cns template connect |
Enters CNS template connect configuration mode and defines the name of a CNS connect template. |
|
template (cns) |
Specifies a list of CNS connect templates within a CNS connect profile to be applied to a routerâs configuration. |