Cisco Cisco Configuration Engine 1.4 Guía De Información
Data Sheet
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 3 of 7
It is important to note that the bootstrap configuration can be the same across all your remote devices. This
feature makes staging, if needed, much easier because you do not have to match the device with the right
configuration.
feature makes staging, if needed, much easier because you do not have to match the device with the right
configuration.
Q.
What are the different identification methods for the CNS agents?
A.
Any unique string will work, as long as there is no overlap within the Cisco Configuration Engine. It is
recommended you use identification methods that come with the devices, including hardware serial number and
the Cisco product UDI. In some solutions such as Cisco Virtual Office, you can even use the end-user’s
username as the device identifier. It is important to note that the device identifier must be registered to the Cisco
Configuration Engine so that it knows this device will be connecting.
Q.
Is there more than one way to put the bootstrap configuration into the devices?
A.
There are several ways of loading the bootstrap configuration into the devices:
●
AutoInstall: AutoInstall is a Cisco IOS Software feature. A device having no configuration goes through a
series of initial tasks, including sending out a Dynamic Host Configuration Protocol (DHCP) discover request.
If the request reaches a DHCP server, the server can reply with an offer. Through DHCP option 150, the
DHCP server can return a Trivial File Transfer Protocol (TFTP) address. The Cisco IOS Software device then
requests the bootstrap configuration from the TFTP address. Because the bootstrap configuration is the
same across all devices, for the configuration engine this option provides a true ZTD solution. The critical
limitation is that the initial DHCP discover request must be able to reach the intended DHCP server—in many
cases over a WAN.
●
Cisco IOS Software Secure Device Provisioning (SDP) in the Cisco Virtual Office solution: The Cisco
Virtual Office solution uses the Cisco IOS Software SDP feature along with Cisco Secure Access Control
Server (ACS) to provide secure authentication of the device, and uses SDP to deliver the bootstrap
configuration to the device. Please visit www.cisco.com/go/cvo for more details. The critical limitation is that
this approach assumes that IP connectivity is already in place.
●
Cisco Configuration Express: Cisco Configuration Express is an ordering option of selected hardware
platforms. Using Cisco Configuration Express, you can specify the bootstrap configuration to be loaded into
the devices before they are shipped. Because the bootstrap configuration is already loaded into the devices,
the devices already have enough information to initiate connection to the Cisco Configuration Engine, thereby
achieving ZTD. Please contact your Cisco account representative for more details and the models that are
supported.
●
Aladdin eToken: You can use the secure eToken USB key on the USB port for selected integrated services
routers (ISRs). You can configure the ISRs to get bootstrap configuration from the secure eToken. For more
information about Aladdin eToken, please contact your local Cisco account representative.
●
Staging: You can also stage the devices using your existing staging service to put the bootstrap configuration
onto the devices. Because the bootstrap configuration is the same for all devices, the staging process can be
significantly simpler.
Q.
I want to use the AutoInstall option. Do I need to order the device with a certain option?
A.
Yes. In order for AutoInstall to be activated, the device must not have any configuration. For Cisco ISR and
Cisco Integrated Services Routers Generation 2 (ISR G2) routers, please use the ISR-CCP-EXP-NOCONF or
ISR-CCP-CD-NOCONF option when ordering Cisco 1900, 2900, and 3900 routers, and the CCP-EXPRESS-
NOCF or CCP-CD-NOCF option when ordering Cisco 800, 1800, 2800, and 3800 routers