Downloads |
Table Of Contents
Related Features and Technologies
Supported Standards, MIBs, and RFCs
Configuring the CNS Configuration Agent (required)
Configuring the CNS Event Agent (required)
Configuring the Remote Router (optional)
Verifying CNS Flow-Through Provisioning (optional)
Cisco Configuration Express File Using T1 over HDLC Protocol Example
T1 Configuration Template Example
Voice Configuration Template Example
Serial-Interface Configuration Example
cns notifications encapsulation
CNS Flow-Through Provisioning
Feature History
This document describes the CNS Flow-Through Provisioning feature in Cisco IOS Release 12.2(8)T. It includes the following sections:
•
Supported Standards, MIBs, and RFCs
Feature Overview
Note
Cisco Networking Services (CNS) Flow-Through Provisioning provides the infrastructure for automated configuration of large numbers of network devices. Based on CNS event and config agents, it eliminates the need for an onsite technician to initialize the device. The result is an automated workflow from initial subscriber-order entry through Cisco manufacturing and shipping to final device provisioning and subscriber billing. This focuses on a root problem of today's service-provider and other similar business models: use of human labor in activating service.
To achieve such automation, CNS Flow-Through Provisioning relies on standardized configuration templates that you create. However, the use of such templates requires a known fixed hardware configuration, uniform for all subscribers. There is no way to achieve this without manually prestaging each line card or module within each chassis. While the inventory within a chassis is known at time of manufacture, controlling which line cards or modules are in which slots thereafter is labor-intensive and error-prone.
To overcome these difficulties, CNS Flow-Through Provisioning defines a new set of Cisco IOS commands—the cns commands. When a remote router is first powered on, these commands do the following:
1.
2.
3.
In turn, the configuration engine does the following:
1.
2.
3.
Figure 1 shows the CNS Flow-Through Provisioning architecture.
Figure 1 CNS Flow-Through Provisioning Architecture
Configurations
CNS Flow-Through Provisioning involves three different types of configuration on the remote router:
•
You specify the preset bootstrap configuration on which this solution depends as part of your order from Cisco using Cisco Configuration Express, an existing service integrated with the Cisco.com order-entry tool. You specify a general-subscriber nonspecific bootstrap configuration that provides connectivity to the CNS configuration engine. Cisco then applies this configuration to all the devices of that order in a totally automated manufacturing step. This configuration runs automatically on power-on.
•
The CNS configuration engine downloads an initial configuration, once only, to replace the temporary bootstrap configuration. You can either save or not save it in the router's nonvolatile NVRAM memory:
–
–
•
On subsequent reboot, incremental or partial configurations are performed to update the configuration without the network having to shut down. Such configurations can be delivered either in a push operation that you initiate or a pull operation on request from the router.
Unique IDs
Key to this solution is the capability to associate, with each device, a simple, manageable, and unique ID that is compatible with your systems for order entry, billing, provisioning, and shipping and can also link your order-entry system to the Cisco order-fulfillment system. Such an ID must have the following characteristics:
•
•
•
•
•
To define such an ID, CNS Flow-Through Provisioning equips the CNS agent with a new set of commands—the cns commands—with which you specify how configurations should be done and, in particular, how the system defines unique IDs. You enable the Cisco IOS software to auto-discover the unique ID according to directions that you specify and information that you provide, such as chassis serial number, MAC address, IP address, and several other possibilities. The cns commands are part of the bootstrap configuration of the manufactured device, specified to Cisco Configuration Express at time of order.
Within this scope, Configuration Express and the cns commands also allow you to define custom asset tags to your own specifications, which are serialized during manufacture and automatically substituted into the unit's bootstrap configuration.
Cisco appends tags to the carton for all the various types of IDs supported by the cns commands, so that these values can be bar-code read at shipping time and fed back into your systems. Alternatively, these IDs are also available through a direct XML-software interface between your system and the Cisco order-status engine, eliminating the need for bar-code reading. The CNS agent also provides a feedback mechanism whereby the remote device can receive XML events or commands to modify the device's ID, in turn causing that same device to broadcast an event indicating the old/new IDs.
Management Point
On most networks, a small percentage of individual remote routers get configured locally. This can potentially be a serious problem, not only causing loss of synchronization across your network but also opening your system to the possibility that an automatic reconfiguration might conflict with an existing configuration and cause a router to become unusable or even to lose contact with the network.
To address this problem, you can designate a management point in your network, typically on the Cisco IE2100 CNS configuration engine, and configure it to keep track of the configurations on all remote routers.
To enable this solution, configure the CNS agent to publish an event on the CNS event bus whenever any change occurs to the running configuration. This event indicates exactly what has changed (old/new), eliminating the need for the management point to perform a highly unscalable set of operations such as Telnetting into the device, applying a script, reading back the entire running configuration, and determining the difference between old and new configurations. Additionally, you can arrange for SNMP notification traps of configuration changes occurring through the SNMP MIB set.
Point-to-Point Event Bus
Today's business environment requires that you be able to ensure your customers a level of service not less than what they are actually paying for. Toward this end, you activate service-assurance applications that broadcast small poll/queries to the entire network while expecting large responses from a typically small subset of devices according to the criteria of the query.
For these queries to be scalable, it is necessary for the replying device to bypass the normal broadcast properties of the event bus and instead reply on a direct point-to-point channel. While all devices need the benefit of the broadcasted poll so that they can all be aware of the query to which they may need to reply, the devices do not need to be aware of each others' replies. Massive copying and retransmission of device query replies, as part of the unnecessary reply broadcast, is a serious scalability restriction.
To address this scalability problem, the CNS event bus has a point-to-point connection feature that communicates directly back to the poller station.
Benefits
Automated Configuration
CNS Flow-Through Provisioning simplifies installation by moving configuration requirements to the CNS configuration engine and allowing the Cisco IOS configuration to update automatically. The registrar uses popular industry standards and technologies such as XML, ADSI/Active Directory, HTTP/Web Server, ASP, and Publish-Subscribe Event Bus. The CNS configuration agent enables the CNS configuration engine to configure remote routers in a plug-and-play manner.
Unique IP Addresses and Host Name
CNS Flow-Through Provisioning uses DNS reverse lookup to retrieve the host name by passing the IP address, then assigns the IP address and optionally the host name to the remote router. Both IP address and host name are thus guaranteed to be unique.
Reduced Technical Personnel Requirements
CNS Flow-Through Provisioning permits remote routers to be installed by a person with limited or no technical experience. Because configuration occurs automatically on connection to the network, a network engineer or technician is not required for installation.
Rapid Deployment
Because a person with limited or no technical experience can install a remote router immediately without any knowledge or use of Cisco IOS software, the router can be sent directly to its final premises and be brought up without technician deployment.
Direct Shipping
Routers can be shipped directly to the remote end-user site, eliminating warehousing and manual handling. Configuration occurs automatically on connection to the network.
Remote Updates
CNS Flow-Through Provisioning automatically handles configuration updates, service additions, and deletions. The CNS configuration engine performs a push operation to send the information to the remote router.
Security
Event traffic to and from the remote router is opaque to unauthorized listeners or intruders to your network. CNS agents leverage the latest security features in Cisco IOS software.
Restrictions
Remote Router
•
–
–
•
CNS Configuration Engine
•
•
•
•
Remote Routers
•
Related Features and Technologies
Simple Network-Enabled Auto-Provisioning for Cisco IAD2420 Series IADs
CNS Flow-Through Provisioning expands on Simple Network-Enabled Auto-Provisioning.
Cisco Intelligence Engine 2100 Series
CNS Flow-Through Provisioning requires the CNS IE2100 series product.
Related Documents
CNS Agents
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftcns•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ftcnsCNS Configuration Engine
•
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ie2100/cnfg_reg/IP and ATM Configuration
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan_c/index.htmIAD and Router Hardware and Software
•
http://www.cisco.com/univercd/cc/td/doc/product/access/iad/iad2420/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/hw_inst/index.htm•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis3600/hw_inst/index.htmCisco Configuration Express
•
http://www.cisco.com/warp/public/779/servpro/operate/ce/CNS Flow-Through Provisioning on Cisco IAD2420 Series IADs
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/Cisco IOS Software
•
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/index.htmRouter Platform Documentation
•
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/index.htmSupported Platforms
•
•
•
•
•
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register/.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
http://www.cisco.com/go/fn/Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
Note
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB website on Cisco.com at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtmlRFCs
No new or modified RFCs are supported by this feature.
Prerequisites
Do the following before using CNS Flow-Through Provisioning:
•
•
•
Configuration Tasks
The CNS Flow-Through Provisioning feature allows the remote router to be connected and configured automatically. Cisco Configuration Express loads a minimal set of Cisco IOS configuration commands for the router in the startup-configuration file in the NVRAM, either at the manufacturer or at your premises. The router is ready to be installed on premises with no further configuration.
If you wish to change the configuration or install a custom configuration, see the following sections for configuration tasks. Each task in the list is identified as either required or optional.
•
•
•
•
Configuring the CNS Configuration Agent (required)
The CNS configuration engine uses templates to build a configuration file. Each parameter in the template must have a directory-customized schema attribute associated.
Tip
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/ie2100/cnfg_reg/rel_1_0/crmanual/To create a template in the CNS configuration engine through the Edit Template graphical user interface (GUI), follow these steps:
Configuring the CNS Event Agent (required)
For an event to be initiated between the remote router and the CNS configuration engine, the CNS event agent must configure a connection. To configure the CNS event agent to do so, use the following command in global configuration mode:
Configuring the Remote Router (optional)
Your remote router arrives from the factory with a bootstrap configuration. Upon initial power-on, the router automatically pulls from the CNS configuration engine a full initial configuration, although you can optionally arrange for this manually as well. After initial configuration, you can optionally arrange for periodic incremental (partial) configurations for synchronization purposes.
Initial Configuration
Initial configuration of the remote router occurs automatically when the router is initialized on the network. Optionally, you can perform this configuration manually.
CNS Flow-Through Provisioning assigns the remote router a unique IP address or host name. After resolving the IP address (using SLARP, ATM InARP, or PPP protocols), the system optionally uses DNS reverse lookup to assign a host name to the router and invokes the CNS agent to download the initial configuration from the CNS configuration engine.
To manually perform an initial configuration, use the following commands in global configuration mode:
Configuring the Remote Router with a Full Configuration—Example
The following example shows initial configuration on a remote router. The remote router's host name is the unique ID. The CNS configuration engine IP address is 172.28.129.22.
Router(config)# cns config connect-intf serial ping-interval 1 retries 1Router(config-cns-conn-if)# config-cli ip address negotiatedRouter(config-cns-conn-if)# config-cli encapsulation pppRouter(config-cns-conn-if)# config-cli ip directed-broadcastRouter(config-cns-conn-if)# config-cli no keepaliveRouter(config-cns-conn-if)# config-cli no shutdownRouter(config-cns-conn-if)# exitRouter(config)# hostname RemoteRouterRemoteRouter(config)# ip route 172.28.129.22 255.255.255.0 11.11.11.1RemoteRouter(config)# cns id Ethernet 0 ipaddressRemoteRouter(config)# cns config initial 10.1.1.1 no-persistRemoteRouter(config)# cns mib-access encapsulation xmlRemoteRouter(config)# cns notifications encapsulation xmlRemoteRouter(config)# cns inventory configIncremental Configuration
Incremental or partial configuration allows the remote router to be incrementally configured after its initial configuration. You must perform these configurations manually through the CNS configuration engine. The registrar allows you to change the configuration templates, edit parameters, and submit the new configuration to the router without a software or hardware restart.
To perform an incremental (partial) configuration, configure the CNS event agent—see the "Configuring the CNS Event Agent (required)" section—and then use the following command in global configuration mode:
Configuring the Remote Router with an Incremental Configuration—Example
The following example shows incremental (partial) configuration on a remote router. The CNS configuration engine IP address is 172.28.129.22 and the port number is 80.
Router(config)# cns config partial 172.28.129.22 80Verifying CNS Flow-Through Provisioning (optional)
Troubleshooting Tips
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
Cisco Configuration Express File Using T1 over HDLC Protocol Example
The following example shows use of the Cisco Configuration Express file to configure the remote router before delivery to its final premises. In the example, 172.28.129.22 is the IP address of the CNS configuration engine.
!cns configure and event agentscns config initial 172.28.129.22 no-persistcns event 172.28.129.22!T1 configurationcontroller t1 0framing esflinecode b8zschannel-group 0 timeslots 1-24 speed 64cns id s0:0 ipaddress!Assign IP addr to s0:0interface s0:0ip address slarp retry 2!IP static routeip route 0.0.0.0 0.0.0.0 s0:0endT1 Configuration Template Example
The following example shows use of the T1 configuration template to build the configuration for use on T1.
hostname ${LDAP://this:attrName=IOShostname}enable password ${LDAP://this:attrName=IOSpassword}controller T1 0clock source ${LDAP://this:attrName=IOST1-clocksource}linecode ${LDAP://this:attrName=IOST1-line}framing ${LDAP://this:attrName=IOST1-framing}channel-group ${LDAP://this:attrName=IOST1-channel-group} timeslots ${LDAP://this:attrName=IOST1-timeslots} speed ${LDAP://this:attrName=IOST1-speed}Voice Configuration Template Example
The following example shows use of the voice configuration template to build the configuration for using voice.
voice-port 1/1codec ${LDAP://this:attrName=IOSvoice-port1}dial-peer voice 1 potsapplication ${LDAP://this:attrName=IOSdial-peer1}port 1/1Remote Router Example
The following example shows a remote router configuration.
Current configuration: 1659 bytes!version 12.2no service padservice timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname tira-24V!!network-clock base-rate 64kip subnet-zeroip cef!ip audit notify logip audit po max-events 100!class-map match-any voicematch access-group 100!!policy-map qosclass voicepriority percent 70voice service voiph323!no voice confirmation-tonevoice-card 0!!controller T1 0framing sflinecode ami!controller T1 1mode casframing esflinecode b8zsds0-group 0 timeslots 1 type e&m-immediate-startds0-group 1 timeslots 2 type e&m-immediate-start!!interface Ethernet0ip address 10.1.1.2 255.255.0.0!interface Serial0bandwidth 1536ip address 11.11.11.1 255.255.255.0no ip mroute-cacheload-interval 30clockrate 148000!ip classlessip route 223.255.254.254 255.255.255.0 1.3.0.1!no ip http serverip pim bidir-enable!access-list 100 permit udp any range 16384 32767 anyaccess-list 100 permit tcp any any eq 1720call rsvp-sync!voice-port 1:0timeouts wait-release 3!voice-port 1:1timeouts wait-release 3!!mgcp profile default!dial-peer cor custom!dial-peer voice 1000 potsdestination-pattern 1000port 1:0forward-digits 0!dial-peer voice 1001 potsdestination-pattern 1001no digit-stripport 1:1forward-digits 0!dial-peer voice 2000 voipdestination-pattern 2000session target ipv4:11.11.11.2codec g711ulaw!dial-peer voice 2001 voipdestination-pattern 2001session target ipv4:11.11.11.2signal-type ext-signalcodec g711ulaw!!line con 0line aux 0line 2 3line vty 0 4Serial-Interface Configuration Example
The following example shows configuration of a serial interface to connect to and download a configuration from a Cisco IE2100 CNS configuration engine. The IE2100 IP address is 10.1.1.1. The gateway IP address to reach the 10.1.1.0 network is 11.11.11.1. The CNS default ID is the host name, so that cns id command is not needed. However, the hostname command is key to retrieving the configuration file on the CNS configuration engine.
This configuration auto-tries every serial interface on the remote router in turn, applies the config-cli commands to that interface, and tries to ping the address in the cns config initial cli. When it succeeds, it performs a normal initial configuration.
Initial basic configuration (serial interface) PPPcns config connect-intf serial ping-interval 1 retries 1config-cli ip address negotiatedconfig-cli encapsulation pppconfig-cli ip directed-broadcastconfig-cli no keepaliveconfig-cli no shutdownexithostname 26MLip route 10.1.1.1 255.255.255.0 11.11.11.1cns config initial 10.1.1.1 no-persistcns inventory configInitial basic configuration (serial interface) HDLCcns config connect-intf serial ping-interval 1 retries 1config-cli ip address slarp retry 1config-cli no shutdownexithostname tira-36Vip route 10.1.1.1 255.255.255.0 11.11.11.1cns config initial 10.1.1.1 no-persistcns inventory configIncremental configuration (serial interface)cns config partial 10.1.1.1cns event 10.1.1.1Command Reference
This section documents new and modified commands used with the CNS Flow-Through Provisioning feature. All other commands used with this feature are documented in the Cisco IOS Release 12.2 command reference publications.
New
•
Modified
cns config cancel
To cancel an incremental (partial) Cisco Networking Services (CNS) configuration, use the cns config cancel command in privileged EXEC mode.
cns config cancel queue-id
Syntax Description
queue-id
Queue identifier of the configuration to be cancelled. To display a list of outstanding configurations, use the show cns config outstanding command.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Incremental (partial) configurations take place in two steps:
1.
2.
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 cancels the configuration whose queue-id is 1:
Router# show cns config outstandingThe outstanding configuration information:queue id identifier config-id1 identifierREAD config_idREADRouter# cns config cancel 1Router# show cns config outstandingThe outstanding configuration information:queue id identifier config-idRelated Commands
cns config connect-intf
To specify the interface for connecting to the Cisco Networking Services (CNS) configuration engine, use the cns config connect-intf command in global configuration mode. To disable this interface for the connection, use the no form of this command.
cns config connect-intf interface-prefix [ping-interval seconds] [retries number]
no cns config connect-intf interface-prefix
Syntax Description
Defaults
The ping interval defaults to 10 seconds.
The number of retries defaults to 5.
Command Modes
Global configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
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 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.
Enter this command to enter connect-interface-config (config-cns-conn-if) submode. Then use one of the following bootstrap-configuration commands to connect to the registrar for initial configuration:
•
•
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 command
config-cli ip route 0.0.0.0 0.0.0.0 &
generates the command
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0.Similarly, the command
config-cli cns id & ipaddress
generates the command
cns id FastEthernet0/0 ipaddressExamples
The following example enters config-cns-conn-if submode, connects to a configuration engine using an async interface, and issues a number of commands:
Router(config)# cns config connect-intf AsyncRouter(config-cns-conn-if)# config-cli encapsulation pppRouter(config-cns-conn-if)# config-cli ip unnumbered FastEthernet0/0Router(config-cns-conn-if)# config-cli dialer rotary-group 0Router(config-cns-conn-if)# line-cli modem InOutRouter(config-cns-conn-if)# line-cli ...<other line commands>...Router(config-cns-conn-if)# exitThese commands result in the following configuration being applied:
line 65modem InOut...interface Async65encapsulation pppdialer in-banddialer rotary-group 0Related Commands
cns config initial
To start the Cisco Networking Services (CNS) configuration agent and initiate an initial configuration, use the cns config initial command in global configuration mode. To remove the existing cns config initial command from the router's running configuration, use the no form of this command.
cns config initial {hostname | ip-address} [encrypt] [port-number] [event] [no-persist]
[page page] [source ip-address] [syntax-check]no cns config initial {hostname | ip-address}
Syntax Description
Defaults
The port number defaults to 80 with no encryption and 443 with encryption.
The page defaults to /cns/Config.
Command Modes
Global configuration
Command History
Usage Guidelines
This command must be in the remote router's bootstrap configuration. Use it to pull the initial configuration for a router at its first bootup. The router's bootstrap configuration contains the information necessary to connect to the CNS configuration engine to retrieve the initial configuration.
Examples
The following example shows how to use the CNS configuration engine at 172.28.129.22 to set the initial CNS configuration and to not write the configuration to NVRAM:
Router(config)# cns config initial 172.28.129.22 no-persistRelated Commands
cns config notify
To detect Cisco Networking Services (CNS) configuration changes and send an event containing the previous and current configurations, use the cns config notify command in global configuration mode. To disable event notification, use the no form of this command.
cns config notify {all | diff} [interval minutes] [no-cns-events]
no cns config notify {all | diff}
Syntax Description
Defaults
The interval defaults to 5 minutes.
Command Modes
Global configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example detects configuration changes for all configuration commands:
Router(config)# cns config notify allRelated Commands
cns config partial
To start the Cisco Networking Services (CNS) configuration agent, which provides CNS configuration services to Cisco IOS clients, use the cns config partial command in global configuration mode. To shut down the partial configuration agent, use the no form of this command.
cns config partial {hostname | ip-address} [encrypt] [port-number] [source ip-address]
no cns config partial {hostname | ip-address} [port-number]
Syntax Description
Defaults
The port number defaults to 80 with no encryption and 443 with encryption.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to start the partial configuration agent process. Configuration data can be pushed to the partial configuration agent or pulled from the CNS configuration engine by the partial configuration agent.
•
•
Examples
The following example starts the partial configuration process using the CNS configuration engine at 172.28.129.22 and port number 80:
Router(config)# cns config partial 172.28.129.22 80Related Commands
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.
cns event {hostname | ip-address} [encrypt] [port-number] [backup] [init-retry retry-count] [keepalive seconds retry-count] [source ip-address] [force-fmt1]
no cns event {hostname | ip-address} [port-number]
Syntax Description
Defaults
The event gateway port number default is 11011 with no encryption or 11012 with encryption.
The number of initial retries defaults to 3.
Keepalive defaults to 0 seconds and 0 retries.
The system uses format 2.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to select the IP address of an event and pass it as the unique CNS ID to the CNS configuration agent, which then pulls a new configuration to the router.
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.
Specify format 1 only if you determine that format 2 does not work on your system. This is most likely to occur if your Cisco IE2100 CNS configuration engine is a very early release. Format 2 has a length field of 4 rather than 2 bytes, and can therefore handle events that are larger than 64k bytes.
Examples
The following example shows how to set the address of the primary CNS event gateway to the configuration engine software running on IP address10.1.2.3, port 11011, with a keepalive of 60 seconds and a retry count of 5:
Router(config)# cns event 10.1.2.3 11011 keepalive 60 5Related Commands
cns id
To set the unique event-id or config-id router identifier used by Cisco Networking Services (CNS) services, use the cns id command in global configuration mode. To set the identifier to the router's host name, use the no form of this command.
If ID Choice Is IP Address or MAC Address
cns id interface num {dns-reverse | ipaddress | mac-address} [event]
no cns id interface num {dns-reverse | ipaddress | mac-address} [event]
If ID Choice Is Anything Else
cns id {hardware-serial | hostname | string string} [event]
no cns id {hardware-serial | hostname | string string} [event]
Syntax Description
Defaults
The system defaults to the host name as the unique ID.
Event defaults to set the unique ID to be the config-id value.
Command Modes
Global configuration
Command History
12.2(2)XB
This command was introduced on Cisco IAD2420 series IADs.
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use this command to retrieve if necessary, set, and pass the unique ID to the CNS configuration agent, which then pulls the initial configuration template to the router during bootup.
You can set either or both of two IDs: the config-id value for CNS configuration services and the event-id value for CNS event services. To set both values, use the command twice.
To set the CNS event-id to the router's host name, use the no form of this command with the event keyword. To set the CNS config-id to the router's host name, use the no form of this command without the event keyword.
Examples
The following example shows the host name of the router being passed as the config-id value:
Router(config)# cns id hostnameThe following example shows the hardware serial number of the router being passed as the event-id value.
Router(config)# cns id hardware-serial eventRelated Commands
Configures the CNS event gateway, which provides CNS event services to Cisco IOS clients.
cns inventory
To enable the Cisco Networking Services (CNS) inventory agent—that is, to send an inventory of the router's line cards and modules to the CNS configuration engine—use the cns inventory command in global configuration mode. To disable the CNS inventory agent, use the no form of this command.
cns inventory [config | event]
no cns inventory [config | event [notify oir]]
Syntax Description
Defaults
Enables both inventory-configuration and inventory events
Command Modes
Global configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use this command to notify the CNS configuration engine of changes to the router's port-adaptor and interface inventory.
Use the event keyword to query the inventory from the remote router using the event bus. An event needs to be sent with the subject "cisco.cns.inventory.get" to the cisco router; the payload of the event is ignored. On receiving this query, the inventory agent sends the inventory.
Examples
The following example shows enabling of the CNS inventory agent:
Router(config)# cns inventoryRelated Commands
cns mib-access encapsulation
To specify whether Cisco Networking Services (CNS) should use granular (XML) or nongranular (SNMP) 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 mib-access encapsulation {snmp | xml [size bytes]}
no cns mib-access encapsulation {snmp | xml}
Syntax Description
Defaults
For XML encapsulation, a maximum size of 3072 bytes
Command Modes
Global configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example specifies that XML be used to access MIBs:
Router(config)# cns mib-access encapsulation xmlRelated Commands
Specifies whether CNS notifications should be sent using nongranular (SNMP) or granular (XML) encapsulation.
cns notifications encapsulation
To specify whether Cisco Networking Services (CNS) notifications should be sent using nongranular (SNMP) or granular (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 notifications encapsulation {snmp | xml}
no cns notifications encapsulation {snmp | xml}
Syntax Description
snmp
Uses nongranular (SNMP) encapsulation to send notifications.
xml
Uses granular (XML) encapsulation to send notifications.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example enables notifications:
Router(config)# cns notifications encapsulationRelated Commands
Specifies whether CNS should use granular (XML) or nongranular (SNMP) encapsulation to access MIBs.
config-cli
To connect to the Cisco Networking Services (CNS) configuration engine using a specific type of interface, use the config-cli command in connect-interface-configuration mode.
config-cli
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Connect-interface-configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Begin by using the cns config connect-intf command to enter connect-interface-configuration (config-cns-conn-if) submode. Then use either this or its companion CNS bootstrap-configuration command to connect to the CNS configuration engine for initial configuration:
•
•
Immediately after either of the commands, enter additional configuration commands as appropriate.
Examples
The following example enters config-cns-conn-if submode, connects to a configuration engine using an async interface, and issues a number of commands:
Router(config)# cns config connect-intf AsyncRouter(config-cns-conn-if)# config-cli encapsulation pppRouter(config-cns-conn-if)# config-cli ip unnumbered FastEthernet0/0Router(config-cns-conn-if)# config-cli dialer rotary-group 0Router(config-cns-conn-if)# line-cli modem InOutRouter(config-cns-conn-if)# line-cli ...<other line commands>...Router(config-cns-conn-if)# exitThese commands apply the following configuration:
line 65modem InOut...interface Async65encapsulation pppdialer in-banddialer rotary-group 0Related Commands
Specifies the interface for connecting to the CNS configuration engine.
Connects to the CNS configuration engine using a modem dialup line.
debug cns config
To display information on Cisco Networking Services (CNS) configurations, use the debug cns config command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug cns config {agent | all | connection | notify}
no debug cns config {agent | all | connection | notify}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example displays messages related to the CNS configurations:
Router# debug cns config all00:04:09: config_id_get: entered00:04:09: config_id_get: Invoking cns_id_mode_get()00:04:09: config_id_get: cns_id_mode_get() returned INTERNAL00:04:09: config_id_get: successful exit cns_config_id=minna1,cns_config_id_len=600:04:09: cns_establish_connect_intf(): The device is already connected with the config server00:04:09: cns_initial_config_agent(): connecting with port 8000:04:09: pull_config() entered00:04:09: cns_config_id(): returning config_id=minna100:04:09: Message finished 150 readend00:04:09: %CNS-4-NOTE: SUCCESSFUL_COMPLETION-Process= "CNS Initial Configuration Agent", ipl= 0, pid= 8200:04:10: %SYS-5-CONFIG_I: Configured from console by consoleRelated Commands
Displays information on CNS events.
Displays information on CNS management.
Displays information on the CNS XML parser.
debug cns event
To display information on Cisco Networking Services (CNS) events, use the debug cns event command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug cns event {agent | all | connection | subscriber}
no debug cns event {agent | all | connection | subscriber}
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example displays messages related to CNS events:
Router# debug cns event all00:09:14: %CNS-4-NOTE: SUCCESSFUL_COMPLETION-Process= "CNS Initial Configuration Agent", ipl= 0, pid= 8200:09:14: event_agent():event_agent starting ..00:09:14: event_agent_open_connection(): attempting socket connect to Primary Gateway00:09:14: event_agent_open_connection():cns_socket_connect() succeeded:return_code=000:09:14: event_agent_open_connection():timeout_len=1:ka_total_timeout =0:total_timeout=000:09:14: event_id_get: entered00:09:14: event_id_get: Invoking cns_id_mode_get()00:09:14: event_id_get: cns_id_mode_get() returned INTERNAL00:09:14: event_id_get: successful exit cns_event_id=test1, cns_event_id_len=500:09:14: ea_devid_send(): devid sent DUMP OF DEVID MSG82C920A0: 00120000 00010774 .......t82C920B0: 65737431 00000402 020000 est1.......00:09:14: event_agent_get_input(): cli timeout=0: socket:0x000:09:14: process_all_event_agent_event_items():process_get_wakeup(&major, &minor)=TRUE: major=0test1#x2: minor=0x12D5D:00:09:14: event_id_get: entered00:09:14: event_id_get: Invoking cns_id_mode_get()00:09:14: event_id_get: cns_id_mode_get() returned INTERNAL00:09:14: event_id_get: successful exit cns_event_id=test1, cns_event_id_len=500:09:14: process_event_id_changed(): event_id = 'test1' old_event_id = 'test1'00:09:14: event_id_get: entered00:09:14: event_id_get: Invoking cns_id_mode_get()00:09:14: event_id_get: cns_id_mode_get() returned INTERNAL00:09:14: event_id_get: successful exit cns_event_id=test1, cns_event_id_len=500:09:14: process_event_id_changed(): event_id = 'test1' old_event_id = 'test1'00:09:14: event_agent_get_input fd_isset_boolean = 0x1: sd=0x000:09:14: event_agent_get_input return_code=0x1:(FD_ISSET(sd, &rd_mask)) = TRUE00:09:14: process_2_byte_length_format_msg():read the 2 length fields:bytes_read=0x400:09:14: process_gateway_ctrl_message():Version TLV set protocol_version_gateway=0x10000:09:14: After: set_msg_protocol_format(): protocol_version_gateway=0x100 msg_protocol_format=0x100:09:14: process_gateway_ctrl_message(): protocol_version_gateway=0x10000:09:14: perform_post_msg_protocol_establishment_tasks():restart callback 0x80ACA35C 0x000:09:14: send_boot_event(): Boot Event Sent DUMP OF EVENT MSG82C92A20: 001D0019 53454E44 ....SEND82C92A30: 3A636973 636F2E63 6E732E65 76656E74 :cisco.cns.event82C92A40: 2E626F6F 7400 .boot.00:09:14: validate_subject_name:event_agent=0x80AC4F0C:,subject_name=cisco.cns.config.load, len=2200:09:14: ea_subscribe:subject_name=cisco.cns.config.load00:09:14: validate_subject_name:event_agent=0x80AC4F0C:,subject_name=cisco.cns.exec.cmd, len=1900:09:14: ea_subscribe:subject_name=cisco.cns.exec.cmd00:09:14: validate_subject_name:event_agent=0x80AC4F0C:,subject_name=cisco.cns.config.reboot, len=2400:09:14: ea_subscribe:subject_name=cisco.cns.config.reboot00:09:14: validate_subject_name:event_agent=0x80AC4F0C:,subject_name=cisco.cns.config.load, len=2200:09:14: ea_subscribe:subject_name=cisco.cns.config.load00:09:14: validate_subject_name:event_agent=0x80AC4F0C:,subject_name=cisco.cns.exec.cmd, len=1900:09:14: ea_subscribe:subject_name=cisco.cns.exec.cmd00:09:14: validate_subject_name:event_agent=0x80AC4F0C:,subject_name=cisco.cns.config.reboot, len=2400:09:14: ea_subscribe:subject_name=cisco.cns.config.reboot00:09:14: process_all_event_agent_event_items():process_get_wakeup(&major, &minor)=TRUE: major=0x2: minor=0x12D5C:00:09:14: add_subjectANDhandle_to_subject_table():p_subject_entry=0x82E3E838: p_subject_entry_list=0x82619CD800:09:14: create_user_descriptor():p_user_entry_list=0x829268A8: p_user_entry=0x82C561DC:00:09:14: add_subjectANDhandle_to_subject_table():add 'user_entry' entry succeeded:user entry =0x82C92A28:queue_handle=0x82C913FC00:09:14: process_event_agent_queue_item():socket_send() succeeded:bytes_sent=29:subject name=cisco.cns.config.load message length=2900:09:14: add_subjectANDhandle_to_subject_table():p_subject_entry=0x82E3E888: p_subject_entry_list=0x82619CD800:09:14: create_user_descriptor():p_user_entry_list=0x82926838: p_user_entry=0x82C561DC:00:09:14: add_subjectANDhandle_to_subject_table():add 'user_entry' entry succeeded:user entry =0x82C92A88:queue_handle=0x82C913FC00:09:14: process_event_agent_queue_item():socket_send() succeeded:bytes_sent=26:subject name=cisco.cns.exec.cmd message length=2600:09:14: add_subjectANDhandle_to_subject_table():p_subject_entry=0x82E3EEDC: p_subject_entry_list=0x82619CD800:09:14: create_user_descriptor():p_user_entry_list=0x829267C8: p_user_entry=0x82C561DC:00:09:14: add_subjectANDhandle_to_subject_table():add 'user_entry' entry succeeded:user entry =0x82C92AF4:queue_handle=0x82C913FC00:09:14: process_event_agent_queue_item():socket_send() succeeded:bytes_sent=31:subject name=cisco.cns.config.reboot message length=3100:09:14: add_subjectANDhandle_to_subject_table():p_subject_entry=0x82E3E838: p_subject_entry_list=0x82619CD800:09:14: add_subjectANDhandle_to_subject_table():add 'user_entry' entry succeeded:user entry =0x82C92A28:queue_handle=0x82C913FC00:09:14: add_subjectANDhandle_to_subject_table():p_subject_entry=0x82E3E888: p_subject_entry_list=0x82619CD800:09:14: add_subjectANDhandle_to_subject_table():add 'user_entry' entry succeeded:user entry =0x82C92A88:queue_handle=0x82C913FC00:09:14: add_subjectANDhandle_to_subject_table():p_subject_entry=0x82E3EEDC: p_subject_entry_list=0x82619CD800:09:14: add_subjectANDhandle_to_subject_table():add 'user_entry' entry succeeded:user entry =0x82C92AF4:queue_handle=0x82C913FC00:09:14: %SYS-5-CONFIG_I: Configured from console by consoleRelated Commands
Displays information on CNS configurations.
Displays information on CNS management.
Displays information on the CNS XML parser.
debug cns management
To display information on Cisco Networking Services (CNS) management, use the debug cns management command in privileged EXEC mode. To disable the currently specified debugging, use the no form of this command.
debug cns management {snmp | xml}
no debug cns management {snmp | xml}
Syntax Description
snmp
Displays debug messages related to nongranular (SNMP) encapsulated CNS-management events.
xml
Displays debug messages related to granular (XML) encapsulated CNS-management events.
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example displays information about SNMP- and XML-encapsulated CNS-management events, including both MIB access and trap generation:
Router# debug cns management snmpRouter# debug cns management xmlRouter# show debuggingCNS Management (SNMP Encapsulation) debugging is onCNS Management (Encap XML) debugging is onRouter# show running-config | include cnscns mib-access encapsulation snmpcns mib-access encapsulation xmlcns notifications encapsulation snmpcns notifications encapsulation xmlcns event 10.1.1.1 11011Router#00:12:50: Enqueued a notification in notif_q00:12:50: ea_produce succeeded Subject:cisco.cns.mibaccess:notification Message Length:38500:12:50: Trap sent via CNS Transport Mapping.Router#00:13:31: Response sent via CNS Transport Mapping.Router#00:14:38: Received a request00:14:38: ea_produce succeeded Subject:cisco.cns.mibaccess:response Message Length:241Related Commands
debug cns xml-parser
To display information on the Cisco Networking Services (CNS) XML parser, use the debug cns xml-parser command in privileged EXEC. mode. To disable debugging, use the no form of this command.
debug cns xml-parser
no debug cns xml-parser
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
Examples
The following example displays information on the CNS XML parser:
Router# debug cns xml-parser00:12:05: Registering tag <config-server>00:12:05: Registering tag <server-info>00:12:05: Registering tag <ip-address>00:12:05: Registering tag <web-page>00:12:05: Registering tag <config-event>00:12:05: Registering tag <identifier>00:12:05: Registering tag <config-id>00:12:05: Registering tag <config-data>00:12:05: Registering tag <cli>00:12:05: Registering tag <error-info>00:12:05: Registering tag <error-message>00:12:05: Registering tag <line-number>00:12:05: Registering tag <config-write>00:12:05: Registering tag <exec-cmd-event>00:12:05: Registering tag <identifier-exec>00:12:05: Registering tag <event-response>00:12:05: Registering tag <reply-subject>00:12:05: Registering tag <server-response>00:12:05: Registering tag <ip-address-exec>00:12:05: Registering tag <port-number>00:12:05: Registering tag <url>00:12:05: Registering tag <cli-exec>00:12:05: Registering tag <config-pwd>00:12:06: Pushing tag <config-data> on to stack00:12:06: open tag is <config-data>00:12:06: Pushing tag <config-id> on to stack00:12:06: open tag is <config-id>00:12:06: Popping tag <config-id> off stack00:12:06: close tag is </config-id>00:12:06: Pushing tag <cli> on to stack00:12:06: open tag is <cli>00:12:06: Popping tag <cli> off stack00:12:06: close tag is </cli>00:12:06: Popping tag <config-data> off stack00:12:06: close tag is </config-data>00:12:06: %CNS-4-NOTE: SUCCESSFUL_COMPLETION-Process= "CNS Initial Configuration Agent", ipl= 0, pid= 96Related Commands
Displays information on CNS configurations.
Displays information on CNS events.
Displays information on CNS management.
line-cli
To connect to the Cisco Networking Services (CNS) configuration engine using a modem dialup line, use the line-cli command in connect-interface-configuration mode.
line-cli
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Connect-interface-configuration
Command History
12.2(8)T
This command was introduced on Cisco 2600 series and Cisco 3600 series routers.
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 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.
Enter this command to enter connect-interface-config (config-cns-conn-if) submode. Then use one of the following bootstrap-configuration commands to connect to the registrar for initial configuration:
•
•
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 following is the case:
•
generates the command config ip route 0.0.0.0 0.0.0.0 FastEthernet0/0.•
generates the command cns id FastEthernet0/0 ipaddressExamples
The following example enters config-cns-conn-if submode, connects to a configuration engine using an async interface, and issues a number of commands:
Router(config)# cns config connect-intf AsyncRouter(config-cns-conn-if)# config-cli encapsulation pppRouter(config-cns-conn-if)# config-cli ip unnumbered FastEthernet0/0Router(config-cns-conn-if)# config-cli dialer rotart-group 0Router(config-cns-conn-if)# line-cli modem InOutRouter(config-cns-conn-if)# line-cli ...<other line commands>...Router(config-cns-conn-if)# exitThese commands apply the following configuration:
line 65modem InOut...interface Async65encapsulation pppdialer in-banddialer rotary-group 0Related Commands
Specifies the interface for connecting to the CNS configuration engine.
Connects to the CNS configuration engine using a specific type of interface.
show cns config connections
To display the status of the Cisco Networking Services (CNS) event agent connection, use the show cns config connections command in privileged EXEC mode.
show cns config connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use to determine whether the CNS event agent is connecting to the gateway, connected, or active, and to display the gateway used by the event agent and its IP address and port number.
Examples
The following example displays information about outstanding incremental (partial) configurations:
Router# show cns config connectionsThe partial configuration agent is enabled.Configuration server: 10.1.1.1Port number: 80Encryption: disabledConfig id: test1Connection Status: Connection not active.Related CommandsThe partial configuration agent is enabled.
Related Commands
Related CommandsConfiguration server: 10.1.1.1
Related CommandsPort number: 80
Related CommandsEncryption: disabled
Related CommandsConfig id: test1
Related CommandsConnection Status: Connection not active.
Displays information about incremental CNS configurations that have started but not yet completed.
Displays statistics about the CNS configuration agent.
show cns config outstanding
To display information about incremental (partial) Cisco Networking Services (CNS) configurations that have started but not yet completed, use the show cns config command in privileged EXEC mode.
show cns config outstanding
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use to display information about outstanding incremental (partial) configurations that have started but not yet completed, including the following:
•
•
•
Examples
The following example displays information about outstanding incremental (partial) configurations:
Router# show cns config outstandingThe outstanding configuration information:queue id identifier config-id1 identifierREAD config_idREADRelated Commands
Displays the status of the CNS event agent connection.
Cancels an incremental two-phase synchronization configuration.
Displays statistics about the CNS configuration agent.
show cns config stats
To display statistics about the Cisco Networking Services (CNS) configuration agent, use the show cns config command in privileged EXEC mode.
show cns config stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use to display the following statistics about the configuration agent:
•
•
Examples
The following example displays information about outstanding incremental (partial) configurations:
Router# show cns config stats0 configurations completed.0 configurations failed.Related Commands
Displays the status of the CNS event agent connection.
Displays information about incremental CNS configurations that have started but not yet completed.
show cns event connections
To display the status of the Cisco Networking Services (CNS) event agent connection, use the show cns event command in privileged EXEC mode.
show cns event connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(2)T
This command was introduced.
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use this command to display the status of the event agent connection—such as whether it is connecting to the gateway, connected, or active—and to display the gateway used by the event agent and its IP address and port number.
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event connectionsThe currently configured primary event gateway:hostname is 10.1.1.1.port number is 11011.Event-Id is Internal test1Keepalive setting:none.Connection status:Connection Established.The currently configured backup event gateway:none.The currently connected event gateway:hostname is 10.1.1.1.port number is 11011.Related Commands
Displays statistics about the CNS event agent connection.
Displays a list of subjects about the CNS event agent connection.
show cns event stats
To display statistics about the Cisco Networking Services (CNS) event agent connection, use the show cns event stats command in privileged EXEC mode.
show cns event stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(2)T
This command was introduced.
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use this command to display the following statistics:
•
•
•
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event stats0 events received.4 events sent.0 events not processed.0 events in the queue.The time stamp of the last received event is *Jan 1 1900 00:00:00 UTCThe time stamp of the last sent event is *Mar 1 1993 00:05:42 UTC2 applications are using the event agent.4 subjects subscribed.Related Commands
Displays the status of the CNS event agent connection.
Displays a list of subjects about the CNS event agent connection.
show cns event subject
To display a list of subjects about the Cisco Networking Services (CNS) event agent connection, use the show cns event command in privileged EXEC mode.
show cns event subject [name]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(2)T
This command was introduced.
12.2(8)T
This command was integrated on Cisco 2600 series and Cisco 3600 series routers.
Usage Guidelines
Use this command to display a list of subjects of the the event agent that are subscribed by applications.
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event subjectThe list of subjects subscribed by applications.cisco.cns.mibaccess:requestcisco.cns.config.loadcisco.cns.config.rebootcisco.cns.exec.cmdRelated Commands
Displays the status of the CNS event agent connection.
Displays statistics about the CNS event agent connection.
Glossary
ADSI—Microsoft's Active Directory Services Interface.
ADSL—asymmetric digital subscriber line. Available through several telecommunications carriers to accommodate the need for increased bandwidth for Internet access and telecommuting applications.
ARP—Address Resolution Protocol.
ASP—Microsoft's Active Server Pages technology.
ATM InARP—ATM Inverse Address Resolution Protocol.
CLEC—competitive local-exchange carrier. A company that builds and operates communication networks in metropolitan, urban, and remote areas and provides its customers with an alternative to the local telephone company.
CLI—command-line interface.
CNS—Cisco Networking Services.
CSU—channel service unit.
codec—code/decoder. An algorithm that transforms analog signals into digital signals and digital signals into analog signals.
CPE—customer-premises equipment. Devices such as channel service units (CSUs) and data service units (DSUs), modems, and ISDN terminal adapters, required to provide an electromagnetic termination for wide-area network circuits before connecting to the router or access server. This equipment was historically provided by the telephone company, but is now typically provided by the customer in North American markets.
DNS—Domain Name System.
DSU—data service unit.
HDLC—High-Level Data Link Control.
HTTP—Hypertext Transport Protocol.
IAD—integrated access device. A CPE device used to combine services from various sources onto a common platform for transmission on a common transport span. Typically, an IAD combines various voice and data services such as circuit-based services such as traditional plain old telephone service (POTS) and packet-switched services such as Frame Relay or ATM.
LDAP—Lightweight Directory Access Protocol.
NVRAM—Nonvolatile random-access memory.
PPP/IPCP—Point-to-Point Protocol / IP Control Protocol.
POTS—plain old telephone service.
PVC—permanent virtual circuit.
SLARP—Serial Line ARP.
XML—eXtensible Markup Language.
