Table Of Contents
Configuring Cisco Smart Install Devices
Configuration Guidelines
DHCP Configuration Guidelines
Configuring the DHCP Server
Configuring the Director as the DHCP Server
Configuring Another Device as DHCP Server
Configuring the TFTP Server
Establishing a Remote Client Session
Configuring a Network with Single or Mixed Switch Types
Configuring a Network That Includes a Single Switch Type
Using Built-In Groups to Configure a Mixed Network with Two Switch Types
On-Demand Update to a New Image or Configuration
Custom Group Based on Connectivity
Custom Group Based on MAC Address
Custom Group Based on Stack Number
Custom Group Based on Product ID
Managing Client Configuration Files
Backing Up Files after Loss of Connection
Extracting and Displaying Tar Files
Other Configuration Options
Disabling Smart Install on a Device
Managing File Downloads on Clients
Download Management for Non-Smart Install Clients
Download Management for Smart Install Clients
Configuring a Client Hostname Prefix
Configuring Additional Smart Install Management VLANs
Smart Install Configuration Examples
Director as the TFTP Server
Before Configuring the Director
Configure a Director
Third-Party, Non-Cisco IOS Device as the TFTP Server
Before Configuring the Director
Configure the Director
Configuring Cisco Smart Install Devices
This section includes some basic scenarios and tasks that you might configure in a Smart Install network.
•
Configuration Guidelines
•Configuring the DHCP Server
•Configuring the TFTP Server
•Establishing a Remote Client Session
•Configuring a Network with Single or Mixed Switch Types
•On-Demand Update to a New Image or Configuration
•Using Custom Groups to Configure Groups Based on Connectivity, MAC Address, Stack Number, or Product ID
•Managing Client Configuration Files
•Other Configuration Options
•Smart Install Configuration Examples
Configuration Guidelines
•A Smart Install zero-touch update refers to an out-of-box switch that is shipped to a customer with no configuration file. The customer can connect it to the network, and after it has booted up, it automatically downloads the appropriate image and configuration. Zero-touch updates also take place on preconfigured switches after you have entered the write erase and reload privileged EXEC commands to clear the configuration.
Caution If you touch the console keyboard during a zero-touch installation and attempt to enter a command or a return on the switch before the client has obtained an IP address, the auto install and Smart Install processes stop. To recover and restart the process, at the system prompt, enter the
write erase and
reload commands on the client and restart the process.
•If, for some reason, the startup configuration fails to download, the client can go into an infinite loop because there is no startup configuration to update. The only way to recover from the loop is to press Enter when the client is coming up after a reload so that the update process stops.
•When performing a zero-touch update, you should always update both the image and the startup configuration files. To update only the image or only the configuration file, use the vstack download-image or vstack download-config privileged EXEC commands for an on-demand download instead.
•Client switches with static IP addresses cannot get zero-touch downloads but can receive on-demand downloads.
•If the director temporarily loses communication with the client switches, there is no impact to the Smart Install feature unless the client is in the middle of installing Cisco IOS images or downloading the configuration. If this happens, manual intervention might be required to restart the process.
•We recommend that configuration files do not include boot host dhcp. If a configuration file does include this configuration, do not apply the configuration file to switches with interfaces that do not have a configured IP address.
•When a director is configured and a client joins the Smart Install network, Smart Install is automatically enabled on these devices. Beginning with Cisco IOS Release 12.2(58)SE, 15.1(1)SY, 15.0(2)SE, or 3.2(0)SE, you can disable Smart Install on a device and also shut down its Smart Install TCP ports by entering the no vstack global configuration command on the client or director.
–When Smart Install is disabled on a device, any Smart Install configuration on the device remains in the running configuration but does not take effect while Smart Install is disabled.
–When Smart Install is disabled on a device, the vstack director ip_ address and vstack basic global configuration commands are not allowed.
–If you disable Smart Install on the director and there were Smart Install DHCP IP addresses configured, you need to manually unconfigure them.
–To reenable Smart Install on the device, enter the vstack global configuration command.
Most configuration commands are visible and can be entered on the director or on a client, but only the ones configured on the director take effect. If you enter commands on a client switch, they do not take effect now, but if the client later becomes the director, the commands are then valid.
DHCP Configuration Guidelines
•Although we recommend that the director be configured to act as DHCP server for the clients, Smart Install can also use an external DHCP server. If you use an external device as DHCP server, you could configure the DHCP server to send option 125/suboption 16 for the director IP address to avoid the possibility of fake DHCP servers.
•We recommend configuring a Cisco IOS DHCP server to remember IP bindings to ensure that devices in the Smart Install network retain the same IP address in the event of a network or device reload.
•In networks that do not use DHCP to assign IP addresses to the clients, you must configure the IP address of the director on each client switch.
Configuring the DHCP Server
To perform zero-touch updates, the Smart Install network must be running DHCP. The DHCP server could be the director, another Cisco device running Cisco IOS, or a non-Cisco third-party server. You can also have the director act as the Smart Install DHCP server and have another device perform all other DHCP server functions.
Either way, use one of the following procedures to set up a Cisco device as DHCP server, or if you choose to configure a non-Cisco third-party device as DHCP server, follow the instructions in the product documentation for configuring a network address and a TFTP server.
Note You should not configure any client switches participating in Smart Install as the DHCP server.
•Configuring the Director as the DHCP Server
•Configuring Another Device as DHCP Server
Note If the DHCP server is the director or another Cisco IOS device and the network reloads, it is possible that DHCP could assign new IP addresses to the devices. This is an unlikely occurrence, but if it does happen, you might need to reassociate the director and client switches by manually entering the director IP address on the director or the client switches. To prevent this occurrence, configure the DHCP server to remember the IP bindings by entering the ip dhcp remember global configuration command or the remember DHCP pool configuration command.
Configuring the Director as the DHCP Server
You can configure the director as DHCP server and create DHCP server pools directly from the Smart Install director.
Beginning in privileged EXEC mode, follow these steps on the director to configure it as the DHCP server:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as the Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack dhcp-localserver poolname
|
Creates a name for the Smart Install DHCP server address pool, and enter vstack DHCP pool configuration mode.
|
Step 6
|
address-pool network-number mask prefix-length
|
Specifies the subnet network number and mask of the DHCP address pool.
Note The prefix length specifies the number of bits that comprise the address prefix. The prefix is an alternative way of specifying the network mask of the client. The prefix length must be preceded by a forward slash (/).
|
Step 7
|
default-router ip_address
|
Specifies the IP address of the DHCP default router for the pool.
Note You can use the vstack startup-vlan global configuration command to specify another VLAN that should be used for Smart Install management.
|
Step 8
|
file-server address
|
Specifies the IP address of the TFTP server.
Note If the director is also the TFTP server, you must enable it. See the "Configuring the TFTP Server" section.
|
Step 9
|
exit
|
Returns to global configuration mode.
|
Step 10
|
ip dhcp remember
|
(Optional) Configures the DHCP server to remember the IP bindings of a device. If the network or device reloads, the DHCP server issues the same IP address to a client that it had before the reload. This command is supported in Cisco IOS Release 12.2(53) or later on switches and in Cisco IOS Release 15.1(3)T or later on routers.
|
Step 11
|
end
|
Returns to privileged EXEC mode.
|
Step 12
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 13
|
show dhcp server
|
Verifies the configuration by displaying the DHCP servers recognized by the device.
|
This example shows how to configure the Smart Install director as the DHCP server:
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack dhcp-localserver pool1
Director(config-vstack-dhcp)# address-pool 1.1.1.0 255.255.255.0
Director(config-vstack-dhcp)# default-router 1.1.1.30
Director(config-vstack-dhcp)# file-server 1.1.1.40
Director(config-vstack-dhcp)# exit
Director(config)# ip dhcp remember
DHCP snooping is automatically enabled on the director. Therefore, you do not need to enable it when the director is the DHCP server.
Configuring Another Device as DHCP Server
If the Smart Install director is not the DHCP server, you can use the traditional Cisco IOS DHCP commands to configure a server pool outside the Smart Install network. The director must have connectivity to the DHCP server. For procedures to configure other DHCP server options, see the "Configuring DHCP" section of the "IP Addressing Services" section of the Cisco IOS IP Configuration Guide, Release 12.2 or the "IP Addressing Services" section of the Cisco IOS IP Configuration Guide, Release 15.1 from Cisco.com. This procedure shows the minimum steps that you need to perform to configure a DHCP server.
Note Do not configure a client switch as DHCP server. Configuring DHCP server commands on a client switch would cause the switch to assign IP addresses, which would make it unable to participate in Smart Install.
Beginning in privileged EXEC mode, follow these steps:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
ip dhcp pool poolname
|
Creates a name for the DHCP server address pool, and enter DHCP pool configuration mode.
|
Step 3
|
bootfile filename
|
Specifies the name of the configuration file to be used.
|
Step 4
|
network network-number mask prefix-length
|
Specifies the subnet network number and mask of the DHCP address pool.
Note The prefix length specifies the number of bits that comprise the address prefix. The prefix is an alternative way of specifying the network mask of the client. The prefix length must be preceded by a forward slash (/).
|
Step 5
|
option 150 address
|
Specifies the IP address of the TFTP server.
|
Step 6
|
remember
|
(Optional) Configures the DHCP pool to remember the IP bindings of a device. If the network or device reloads, the DHCP server issues the same IP address to a client that it had before the reload.
|
Step 7
|
end
|
Returns to privileged EXEC mode.
|
This example shows how to configure another device as a DHCP server:
Switch # configure terminal
Switch(config)# ip dhcp pool pool1
Switch(dhcp-config)# network 10.10.10.0 255.255.255.0
Switch(dhcp-config)# bootfile config-boot.text
Switch(dhcp-config)# option 150 10.10.10.1
Switch(dhcp-config)# remember
When the director is a Layer 3 switch, DHCP snooping is automatically enabled on it. When there is a relay agent between the DHCP server and the director, you must enable DHCP snooping on the relay agent.
To enable DHCP snooping on a Cisco DHCP relay device, enter these global configuration commands:
•ip dhcp snooping
•ip dhcp snooping vlan vlan-id for other configured Smart Install VLANs
•no ip dhcp snooping information option (if the DHCP server is running Cisco IOS)
You must also enter the ip dhcp snooping trust interface configuration command on the director interface that is connected to the server.
If the director and the DHCP server are on different VLANs, you must enable IP routing on the VLAN interface connected to the client switches, and enter this command:
•ip helper address (IP address of the DHCP server)
Configuring the TFTP Server
Smart Install stores image and configuration files on a TFTP server. The director can function as the TFTP server, eliminating the need for an external TFTP-serving device. If the director is the TFTP server, image and configuration files are stored in the director flash memory. If the director does not have available memory storage space, you can store the files on a third-party server and point to that location.
•If the TFTP server is a third-party (non-Cisco) device, you should disable the server option to change the name of a file if another file is created with the same name. Otherwise, duplicate imagelist files might be created.
In Catalyst 6500 Supervisor Engine 2T switches, flash size supports onboard and external disk to download the image and the configuration file.
Guidelines when selecting the director to be the TFTP server:
•The total flash memory space (used and free) on the director must be large enough to contain the director image and configuration file and the image and configuration files required for client switches.
•There must be enough available flash memory on the director to hold the client Cisco IOS images and configuration files. The Cisco IOS image files vary in size, depending on the client product IDs and size of the images being installed.
•When the director is the TFTP server, a copy of the configuration file for each client is stored in the root directory of the flash file system on the director. There must be enough space for each planned client.
•Most director devices have enough flash memory to hold one client Cisco IOS image and a small number of client configuration files. For example, the Catalyst 3750 switch can have a maximum flash size of 64 MB, which accommodates only 4 or 5 images, based on the image size.
•If the director is a switch and the Smart Install network includes client switches with more than one product ID, you should use an external TFTP server.
Beginning with this release, you do not need to configure the director as TFTP server. The director automatically gets the required image and configuration files and acts as the TFTP server when you specify flash: as the location from which to retrieve the files.
For example, for zero-touch updates of a default image and a configuration file, entering these commands on the director automatically configures the director as the TFTP server and enables the director DHCP server to provide these files to the clients.
vstack config flash:new_configuration_file
vstack image flash:image_name.tar
Establishing a Remote Client Session
You can perform configuration tasks on the client through a remote connection from the director. From the director, enter the vstack attach {client - index} | {client IP address} command in EXEC mode to attach to a client interface and temporarily enable it as director. Select a client by either choosing from a list that shows the active clients that are available within the Smart Install network or by entering the client IP address.
The client index list is dynamically generated in the Cisco IOS help text. If the director device is not rebooted, then the client-index is retained and it can be used in future configurations.
Configuring a Network with Single or Mixed Switch Types
•Configuring a Network That Includes a Single Switch Type
•Using Built-In Groups to Configure a Mixed Network with Two Switch Types
Configuring a Network That Includes a Single Switch Type
When all client switches in the Smart Install network are the same switch product ID and are performing the same functions, all clients would use the same image and the same seed (base) configuration file. In this case, you can configure a default image and a seed configuration file for all clients in the network.
Beginning in privileged EXEC mode, follow these steps on the director to set the default image and configuration file for all clients in the network.
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack image {flash:image_name.tar | tftp://location image_name.tar}
|
Enters the location and image.
Note Although visible in the command-line help, these options are not supported: ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•flash:image_name.tar—Enter if the director is the TFTP server and the image is in the director flash memory.
Note Instead of flash:, you can also enter flash0:, flash1:, or usb:
•tftp://location image_name.tar
•image_name.tar: Enter the name of the default image tar file for clients in the network.
|
Step 6
|
vstack config {flash: config.txt | tftp://location config.txt}
|
Enters the location and the default configuration file name. The configuration file is a text file that contains the configuration file to be downloaded to the client.
Note Although visible in the command-line help, these options are not supported: ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•For location, enter flash: if the TFTP server is the director and the configuration file is in the director flash memory.
Note Instead of flash:, you can also enter flash0:, flash1:, or usb:.
•For location, enter tftp: if the TFTP server is not the director or if the file is not in the director flash memory. In this case enter tftp://director ip_address.
•config_filename—Enter the filename of the default seed configuration file for clients in the network.
|
Step 7
|
end
|
Returns to privileged EXEC mode.
|
Step 8
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 9
|
show vstack config
|
Verifies the configuration.
|
A client switch sends an error message if it is unable to download an image or a configuration file due to miscommunication, if the image or configuration file is not available, or if a join window is configured and the DHCP acknowledgement occurs outside the configured time frame. If a Cisco device is being used as the TFTP server, you should configure it as described in the "Configuring the TFTP Server" section.
This example shows how to configure a default image and configuration file for a Smart Install network if the director is the TFTP server and the default image and configuration file are in the director flash memory:
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack image flash:c2960-lanbase-tar.122-52SE.tar
Director(config)# vstack config flash:2960lanbase_config.txt
This example shows how to configure a default image and configuration file when the TFTP server is not the director:
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack image tftp://101.122.33.10/c2960-lanbase-tar.122-52SE.tar
Director(config)# vstack config tftp://101.122.33.10/2960LANBase_config.txt
Using Built-In Groups to Configure a Mixed Network with Two Switch Types
You can use built-in groups in a Smart Install network to configure a group of switches that have one product ID with an image and configuration file and to configure a second group of switches that have another product ID with another image file and configuration. You could also have other clients in the network that do not belong to either of these groups that could use the default image and configuration if they match the default product ID.
Beginning in privileged EXEC mode, follow these steps on the director to configure the image and configuration file for two different product IDs in the Smart Install network:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack group built-in product_family1 port_config
|
Identifies the first built-in group product ID, and enters Smart Install group configuration mode for the group.
|
Step 6
|
image location image_name.tar
|
Enters the location and image name for group 1.
•For location, enter flash: (if the TFTP server is the director and the file is stored in the director flash memory).
Note Instead of flash:, you can also enter flash0:, flash1:, or usb:.
•For location, enter tftp: and the location of the configuration file for group 1 if the file is not stored in the director flash memory.
Note Although visible in the command-line help, these options are not supported: ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•image_name.tar: Enter the name of the image tar file for clients in group 1.
|
Step 7
|
config location config_filename
|
Enters the location and configuration file for group 1.
•For location, enter flash: (if the TFTP server is the director and the file is stored in the director flash memory).
Note Instead of flash:, you can also enter flash0:, flash1:, or usb:.
•For location, enter tftp: and the location of the configuration file for group 1 if the file is not stored in the director flash memory.
Note Although visible in the command-line help, these options are not supported: ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•config_filename—Enter the filename of the configuration file for group 1.
|
Step 8
|
exit
|
Returns to global configuration mode.
|
Step 9
|
vstack group built-in product_family2 port_config
|
Identifies the second built-in group product ID, and enter Smart Install group configuration mode for the group.
|
Step 10
|
image location image_name.tar
|
Enters the location and image name for group 2.
•For location, enter flash: (if the TFTP server is the director and the file is stored in the director flash memory).
Note Instead of flash:, you can also enter flash0:, flash1:, or usb:.
•For location, enter tftp: and the location of the configuration file for group 2 if the file is not stored in the director flash memory.
Note Although visible in the command-line help, these options are not supported: ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•image_name.tar—Enter the name of the image tar file for clients in group 2.
|
Step 11
|
config location config_filename
|
Enters the location and configuration file for group 2.
•For location, enter flash: (if the TFTP server is the director and the file is stored in the director flash memory).
Note Instead of flash:, you can also enter flash0:, flash1:, or usb:.
•For location, enter tftp: and the location of the configuration file for group 2 if the file is not stored in the director flash memory.
Note Although visible in the command-line help, these options are not supported: ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•config_filename—Enter the filename of the configuration file for group 2.
|
Step 12
|
end
|
Returns to privileged EXEC mode.
|
Step 13
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 14
|
show vstack group built-in detail
|
Verifies the configurations.
|
A client switch sends an error message if it cannot download an image or a configuration file due to misconfiguration, if the image or configuration file is not available, or if a join window is configured and the DHCP acknowledgement occurs outside of the configured time frame.
This example uses built-in groups to configure all 3560 24-port switches in the network with one image and configuration file and to configure all 2960 24-port switches in the network with another image file and configuration.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack group built-in 3560 24
Director(config-vstack-group)# image tftp://101.122.33.10/c3560-ipbaselmk9-tar.122-52.SE.tar
Director(config-vstack-group)# config tftp://101.122.33.10/3560-24-ipbase_config.txt
Director(config)# vstack group built-in 2960 24
Director(config-vstack-group)# image tftp://101.122.33.10/c2960-lanbasek9-tar.122-52.SE.tar
Director(config-vstack-group)# config tftp://101.122.33.10/2960-24-LANbase_config.txt
On-Demand Update to a New Image or Configuration
When a director is established and default or group images and configuration files are defined and there is connectivity between the director and a client switch, you can perform on-demand image and configuration updates. You can use this capability on a new client switch to make it Smart Install capable or on existing clients to update the image or configuration.
You can initiate an on-demand download if the switch has a valid IP interface. For on-demand download on a switch that is not Smart Install capable, the switch must also have an enable password configured.
Note In Catalyst 3850 switch, the client should be in installed mode to update the image.
Beginning with Cisco IOS Release 12.2(58)SE ,15.1(1)SY, 15.0(2)SE, and 3.2(0)SE, you can perform on-demand updates to multiple clients at the same time.
Beginning in privileged EXEC mode, follow these steps on the director to perform an on-demand update on a client switch.
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as the Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
end
|
Returns to privileged EXEC mode.
|
Step 6
|
vstack download-image tar image_URL {ip_address | index name} remote_switch_password [override] reload [in time]
or
vstack download-image built-in product_family port_config remote_switch_password [override] reload [in time]
or
vstack download-image {imagelist_file _URL {ip_address | index name} | built-in product_family port_config} remote_switch_password [override] reload [in time]
|
Starts an on-demand tar image download on a Smart Install client switch:
•Enter the image_name.tar filename and location and the IP address of the client.
or
Enter the image_list filename and location and the IP address of the client (for releases earlier than 12.2(55)SE).
•ip_address—Enter the IP address of the client switch.
•index name—Enter the index name from the director database for multiple clients or a range of clients (for example, 1-3, 4). This feature was added in Cisco IOS Release 12.2(58)SE, 15.1(1)SY, 15.0(2)SE, or15.0(3) SE.
•Enter built-in, and select the product family and port configuration from the command-line help.
Note Use this option if you have identified the image for the specified built-in group by entering the image location image_name.tar Smart Install group configuration command.
•remote_switch_password —Enter the password for the client switch.
Note A password is needed only if the switch is running a Cisco IOS image earlier than 12.2(52)SE. It is not required for switches already in the Smart Install network. If you are upgrading the image for multiple clients, all clients must have the same password or must have no password (None).
•(Optional) override—Overrides the existing image on the client switch.
•reload—Reloads the client switch.
•(Optional) in time—Specifies the time to reload the switch by using the format hh:mm. The range is from 00:00 to 23:59. If no time is specified, the reload occurs when you exit the CLI.
|
Step 7
|
vstack download-config {config_URL ip_address | built-in product_family port_config} remote_switch_password startup [reload] [in time]
|
Starts an on-demand configuration download on a Smart Install client switch:
•Enter the configuration filename and location and the IP address of the client
•Enter built-in and select the product family and port configuration from the command-line help.
Note Use this option if you have identified the configuration for the specified built-in group by entering the config location config_filename Smart Install group configuration command.
The remaining keywords have these meanings:
•remote_switch_password —Enter the password for the client switch.
Note A password is required only for switches that are not Smart Install capable. It is not required for switches already in the Smart Install network.
•startup—Apply the configuration to the switch startup configuration.
•(Optional) reload—Reload the switch.
•(Optional) in time—Specifies the time to reload the switch using the format hh:mm. The range is from 00:00 to 23:59. If no time is specified, the reload occurs when you exit the CLI.
|
Step 8
|
show vstack download-status
|
Checks status of the download.
|
This example shows how to configure a Smart Install director to schedule an on-demand download of an image and configuration file to the client switch with the IP address 1.1.1.30 and password of mypassword. The download takes place in 6 hours and 30 minutes.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director# vstack download-image tar tftp://101.122.33.10/c2960-lanbasek9-tar.122-52.SE.tar
1.1.1.30 mypassword reload in 06:30
Director# vstack download-config tftp://101.122.33.10/2960LANBase_config.txt 1.1.1.30 my
password reload in 06:30
This example shows the same configuration for a built-in group.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director# vstack download-image built-in 3750 24 mypassword override reload in 6:30
Director# vstack download-config built-in 3750 24 mypassword reload in 06:30
Using Custom Groups to Configure Groups Based on Connectivity, MAC Address, Stack Number,
or Product ID
You can configure a custom group to set up the image and configuration file for all client switches that match connectivity, MAC address, stack number, or product IDs for switches in a stack.
A client switch sends an error message if it cannot download an image or configuration file due to misconfiguration, if the image or configuration file is not available, or if a join window is configured and the DHCP acknowledgement occurs outside of the configured time frame.
Custom Group Based on Connectivity
You can configure a custom group based on the connectivity or topology of switches in a Smart Install network. For example, you would use a connectivity match to configure a group of switches that are connected to the director through a single interface or switches that are connected to the director through a specific intermediate switch. A connectivity match takes priority over product ID or stack number custom groups and over built-in groups, but not over groups based on MAC addresses. The switches that do not match the connectivity configuration would get the configuration and image in a built-in group or the default configuration.
Beginning in privileged EXEC mode, follow these steps on the director to configure a custom group based on connectivity:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as the Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack group custom group_name connectivity
|
Identifies a custom group based on a connectivity match, and enter Smart Install group configuration mode for the group.
|
Step 6
|
match host ip_address interface interface-id
|
Identifies the client switches for the custom group:
•host ip_address—The IP address of the upstream neighbor of the client (this could be the director or an intermediate device).
•interface interface-id—The interface on the upstream neighbor to which the clients is connected. The interface ID must be the full identifier for the interface, such as GigabitEthernet 2/0/1.
|
Step 7
|
image location image_name.tar
|
Enters the location and image file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory, or enter tftp: and the location of the imagefile: Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•image_name.tar is the image tar file that you want to download. For a switch stack, there could be multiple images for members of the stack.
|
Step 8
|
config location config_filename.
|
Enters the location and configuration file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory, or enter tftp: and the location of the configuration file. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•config_filename—The filename of the configuration file for the group.
|
Step 9
|
end
|
Returns to privileged EXEC mode.
|
Step 10
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 11
|
show vstack group custom detail
|
Verifies the configuration.
|
This example creates a custom group named testgroup2 for all switches that are connected to the specified host and interface and configures the group to use the specified image file and configuration.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack group custom textgroup2 connectivity
Director(config-vstack-group)# match host 1.1.1.10 interface GigabitEthernet 1/0/3
Director(config-vstack-group)# image tftp://101.122.33.10/c3750-ipbase-tar.122-52.SE.tar
Director(config-vstack-group)# config tftp://101.122.33.10/3750-24-ipbase_config.txt
Director(config-vstack-group)# exit
Custom Group Based on MAC Address
You can configure a custom group based on the MAC addresses of switches in a Smart Install network. A MAC address match takes priority over any other matches. The switches that do not match the MAC addresses in the group would get the configuration and image for another group or the default configuration.
Beginning in privileged EXEC mode, follow these steps on the director to configure a custom group based on connectivity:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as the Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack group custom group_name mac
|
Identifies a custom group based on a MAC address match, and enter Smart Install group configuration mode for the group.
|
Step 6
|
match mac_address
|
Enters the MAC address of the client switch to be added to the custom group. Repeat the command for each MAC address to be added.
Note To see MAC addresses of switches in the Smart Install network, enter the show vstack neighbors all privileged EXEC command. Switches added to the group must be able to use the same image and configuration file.
|
Step 7
|
image location image_name.tar
|
Enters the location and image file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory, or enter tftp: and the location of the image. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•image_name.tar is the image tar file that you want to download. For a switch stack, there could be multiple images for members of the stack.
|
Step 8
|
config location config_filename.
|
Enterss the location and configuration file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory, or enter tftp: and the location of the configuration file. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•config_filename—The filename of the configuration file for the group.
|
Step 9
|
end
|
Returns to privileged EXEC mode.
|
Step 10
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 11
|
show vstack group custom detail
|
Verifies the configuration.
|
This example creates a custom group named testgroup3 that includes the three switches identified by MAC address, and configures the group to use the specified image file and configuration.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack group custom textgroup3 mac
Director(config-vstack-group)# match mac 0023.34ca.c180
Director(config-vstack-group)# match mac 001a.a1b4.ee00
Director(config-vstack-group)# match mac 00:1B:54:44:C6:00
Director(config-vstack-group)# image tftp://101.122.33.10/c3750-ipbase-tar.122-52.SE.tar
Director(config-vstack-group)# config tftp://101.122.33.10/3750-24-ipbase_config.txt
Director(config-vstack-group)# exit
Custom Group Based on Stack Number
You can configure a custom group based on the number of the switch in the stack. Any switch in a stack that matches the stack number and product ID gets the same configuration.
Note A client switch in a stack can be updated only when it belongs to a custom stack group. It cannot belong to the default group.
Beginning in privileged EXEC mode, follow these steps on the director to configure a custom group based on the stack number:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as Smart Install director be entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart -Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack group custom group_name stack
|
Identifies a custom group based on matching the stack number and enter Smart Install group configuration mode for the group.
|
Step 6
|
match switch_number stack product_family port_config
|
Identifies the client switches for the custom group:
•switch_number—Number of the switch in the stack. The range is from 1 to 9.
•product_family—Select the stack product family from the command-line help.
•port_config—Switch port configuration. To see the available port configurations, enter a ? after the product family.
|
Step 7
|
image location image_name.tar
|
Enters the location and image file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory or enter tftp: and the location of the imagefile. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•image_name.tar is the image tar file that you want to download.
|
Step 8
|
config location config_filename.
|
Enters the location and configuration file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory or enter tftp: and the location of the configuration file for the group. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•config_filename—The filename of the configuration file for the group.
|
Step 9
|
end
|
Returns to privileged EXEC mode.
|
Step 10
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 11
|
show vstack group custom detail
|
Verifies the configuration.
|
This example creates a custom group named testgroup for all switches that are identified as switch member 2 in a Catalyst 3750 24-port stack to use the specified image file and configuration.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack group custom testgroup stack
Director(config-vstack-group)# image tftp://101.122.33.10/c3750-ipbase-tar.122-52.SE.tar
Director(config-vstack-group)# config tftp://101.122.33.10/3750stack_config.txt
Director(config-vstack-group)# match 1 3750 24poe
Director(config-vstack-group)# match 2 3750 24poe
Director(config-vstack-group)# match 3 3750 24poe
Director(config-vstack-group)# exit
Custom Group Based on Product ID
You can configure a custom group based on the product ID of switches in a Smart Install network. The switches that do not match the product ID in the group can have the configuration and image for another group or the default configuration.
Beginning in privileged EXEC mode, follow these steps on the director to configure a custom group based on connectivity:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as the Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack startup-vlan vlan_value
|
Specifies the default VLAN that the director should use for Smart Install management.
|
Step 5
|
vstack group custom group_name product-id
|
Identifies a custom group based on a product-ID match, and enter Smart Install group configuration mode for the group.
|
Step 6
|
match product-id
|
Enters the product ID of the client switches in the custom group.
Note The product ID can be the same as that of a built-in group. If a client matches a built-in group and a custom group, the custom group takes precedence.
|
Step 7
|
image location image_name.tar
|
Enters the location and image file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory, or enter tftp: and the location of the image. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•image_name.tar is the image tar file that you want to download. For a switch stack, there could be multiple images for members of the stack.
|
Step 8
|
config location config_filename.
|
Enters the location and configuration file for the custom group.
•location—Enter flash: if the TFTP server is the director and the file is stored in the director flash memory, or enter tftp: and the location of the configuration file. Instead of flash:, you can also enter flash0:, flash1:, or usb:.
Note Although visible in the command-line help, these options are not supported: flash1:, ftp:, http:, https:, null:, nvram:, rcp:, scp:, system:, tmpsys:.
•config_filename—The filename of the configuration file for the group.
|
Step 9
|
end
|
Returns to privileged EXEC mode.
|
Step 10
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 11
|
show vstack group custom detail
|
Verifies the configuration.
|
This example creates a custom group named testgroup4 that includes switches that match the product ID WS-C2960-48TC-L, and configures the group to use the specified image file and configuration.
Director# configure terminal
Director(config)# vstack director 1.1.1.20
Director(config)# vstack basic
Director(config)# vstack group custom textgroup4 product-id
Director(config-vstack-group)# match WS-C2960-48TC-L
Director(config-vstack-group)# image tftp://101.122.33.10/c2960-lanbase-tar.122-52.SE.tar
Director(config-vstack-group)# config tftp://101.122.33.10/c2960-lanbase_config.txt
Director(config-vstack-group)# exit
Managing Client Configuration Files
You can manage the client configuration files through the director that is set up as TFTP server, or through a third-party TFTP server. Only supported devices that are Smart Install capable can perform the role of director and save client configuration files to a repository. See "Supported Devices for Smart Install" to see a list of devices that can be a Smart Install network director.
The backup feature does not need to be enabled; it is on by default. However, if you have disabled it and want to save the configuration files to a repository, use the vstack backup global configuration command to enable the feature. After enabling the backup feature, use the vstack backup file-server global configuration command to specify a repository on the TFTP server to save the configurations files. The repository will define where the files are saved.
Every time the write memory privileged EXEC command is issued on the client, its configuration files are saved to the director-TFTP server or third-party TFTP server.
These names are assigned to the client backup files:
•HostnameMAC address.rev1
•HostnameMAC address.rev2 (most recent version)
When the client undergoes a hostname change, the configuration files are not backed up until you enter the write memory command. When a new mapping is created between the client with a new hostname and the two configuration files, the existing mapping is removed. On a third-party TFTP server, after a new mapping is created between the client with a new hostname and the two configuration files, the files are not removed.
Note Do not remove the backed-up client files from the third-party TFTP server repository. Otherwise, the backup feature does not work properly.
Backing Up Files after Loss of Connection
If the client-to-director connection is lost after issuing the write memory command, the back-up process fails. You must reestablish the connection so that the client file is backed up on the director. If you entered the write memory command more than once, the files associated with the last write memory command event are backed up on the director. If the client reloads or fails before receiving feedback that the backup was successful, any changes made to the client startup do not take effect until you reload the client.
Extracting and Displaying Tar Files
When the client sends a tar file to the director, you can use the vstack untar source-url [destination-url] command in EXEC mode to extract and display the files in a specified location. However, when the client sends a tar file to a third-party TFTP server, you cannot use the director to extract and display the files.
The tar files are placed into the preconfigured directory within the repository. If the directory is not configured, the files are extracted and displayed in the director root directory flash memory.
Other Configuration Options
•Disabling Smart Install on a Device
•Managing File Downloads on Clients
•Configuring a Client Hostname Prefix
•Configuring Additional Smart Install Management VLANs
Disabling Smart Install on a Device
When a director is configured and a client joins the Smart Install network, Smart Install is automatically enabled on these devices. Beginning with Cisco IOS Release 12.2(58)SE, 15.1(1)SY, 15.0(2)SE, or 3.2(0)SE, you can disable Smart Install on a device and also shut down its Smart Install TCP ports by entering the no vstack global configuration command on the client or director. When Smart Install is disabled on a device, any Smart Install configuration on it remains in the running configuration but does not take effect while Smart Install is disabled.
When Smart Install is disabled on a device, the vstack director ip_ address and vstack basic global configuration commands are not allowed on the device. To reenable Smart Install on a device, enter the vstack global configuration command.
Managing File Downloads on Clients
You can use download management to download image and configuration files to a client. For non-Smart Install clients, an HTTP emulation process manages file downloads. For Smart Install capable clients, file downloads are performed when a request is received from the director.
Download Management for Non-Smart Install Clients
For non-Smart Install capable clients, you can initiate downloads from the director through HTTP emulation. The client initiates a new connection to the director, and the director initiates a new HTTP connection to the non-Smart Install client on port 80. The image file name and configuration file name from the group database is gathered, and a download is issued on the non-Smart Install client through HTTP emulation. After the download is complete, a reload is issued on the client.
Note Stackable switches must have the correct configuration present because they do not have a default image and configuration.
Download Management for Smart Install Clients
For Smart Install-capable clients to receive image and configuration files, the client performs a write erase and reload. The client establishes connectivity with the director and gathers information about the image and the configuration files. When this information is gathered, the client begins the update. When the update is complete, the Smart Install-capable client reboots.
Configuring a Client Hostname Prefix
When configuring switches out of the box, to help identify the switches and their locations in the network, you can enter this global configuration command on the director:
vstack hostname-prefix prefix
You can then enter a prefix to the hostname for clients in the Smart Install network. The last part of the switch hostname for a switch that had a DCHP request snooped through the director contains the last 3 bytes of the switch MAC address.
This example shows how to configure the hostname Cisco for a client that has been DHCP-snooped. The second display shows the resulting switch hostname assignment:
Director(config)# vstack hostname-prefix Cisco
If you then telnet to that switch from the director, the hostname is shown:
Director#
*Mar 1 17:21:43.281: %SYS-5-CONFIG_I: Configured from console by console
*Mar 1 17:21:52.399: %DHCP-6-ADDRESS_ASSIGN: Interface Vlan1 assigned DHCP address 172.16.0.17, mask 255.255.0.0, hostname
CISCO-bf.97c0#
Configuring Additional Smart Install Management VLANs
Client switches can be on any VLANs if you configure the director to snoop on the VLAN by entering the vstack vlan vlan-id global configuration command and if traffic from the VLAN flows through the director. The director can snoop on multiple VLANs extending to clients on different Layer 2 subnets.
By default, when the director is an Ethernet switch, VLAN 1 is the Smart Install management VLAN and the only VLAN that DHCP snoops on. You can, however, use the vstack startup-vlan global configuration command to specify another default VLAN.
You can add additional Smart Install management VLANs or a range of VLANs to participate in DHCP snooping. You can configure any number of Smart Install management VLANs.
vstack vlan vlan-id
This command is not supported when the director is a router. On a router, after you enable Smart Install with the vstack basic command, clients connected to any Layer 3 interface on the router will continue to communicate with Smart Install. Clients must have a default route to reach the director as specified in its DHCP pool.
Beginning in privileged EXEC mode, follow these steps on the director to configure a startup VLAN:
| |
Command
|
Purpose
|
Step 1
|
config terminal
|
Enters global configuration mode.
|
Step 2
|
vstack director ip_ address
|
Configures the device as the Smart Install director by entering the IP address of an interface on the device.
|
Step 3
|
vstack basic
|
Enables the device as the Smart Install director.
|
Step 4
|
vstack vlan vlan-id
|
Specifies the VLAN for Smart Install management.
|
Step 5
|
vstack startup-vlan vlan_value
|
Specifies the startup VLAN that the director should use for Smart Install management.
Note Ensure that this VLAN is already present in the system as a VLAN for Smart Install management.
|
Step 6
|
no vstack startup-vlan
|
Removes the VLAN as the startup VLAN so that VLAN 1 now becomes the startup VLAN for Smart Install management.
|
Step 7
|
end
|
Returns to privileged EXEC mode.
|
Step 8
|
no vstack vlan
|
(Optional) Removes the earlier vlan-id VLAN from the Smart Install management VLAN list.
|
Step 9
|
copy running-config startup config
|
(Optional) Saves your entries in the configuration file.
|
Step 10
|
show vstack group custom detail
|
Verifies the configuration.
|
Smart Install Configuration Examples
These are examples of how to configure a client default configuration on the director. The director should have Layer 3 enabled with multiple Layer 3 interfaces. The director has an IP address on the VLAN that is used for Smart Install management, and configures an IP address on the client VLAN interface. All clients are the same model type and use the default configuration. Clients added to the network are out-of the box switches with no configuration, or switches that have had a write erase and reload.
Note VLANs are not required when the director is a router.
These examples show how to configure a default configuration with the director as TFTP server and with a third-party server.
•Director as the TFTP Server
•Third-Party, Non-Cisco IOS Device as the TFTP Server
Director as the TFTP Server
In this example, the director is the TFTP server and the image and configuration file are stored in the director flash memory.
Before Configuring the Director
Define the Configuration File and Cisco IOS Image
Step 1 You must transfer files to the director. TFTP is the preferred method of transferring files to and from the director. Locate a TFTP server that is IP-reachable by the director and put all files to be transferred on that server.
Step 2 Using a text editor, create a file with the configuration commands for your default switch. In this example, the file name is default_configuration.txt.
Step 3 Save the default_configuration.txt to the TFTP server.
Step 4 Identify the Cisco IOS image you want loaded as the default image on the switches, for example, c2960-lanbase-tar.122-53.SE.tar. Put that file in the TFTP server.
You should have two files on the TFTP server: the configuration file and the Cisco IOS image.
Note After the director is enabled and configured with the default image name, it creates a tailored configuration file for boot up and an imagelist file with the default image and puts them in flash memory.
Transfer These Files to the Director
Step 1 Before you start, make sure that you have room in the flash memory for the Cisco IOS image. The output of the dir command shows the available space near the end of the output. If you do not have enough space for the image, do one of these:
•Remove files to free up some space.
•Consider using an external TFTP server for the Smart Install. (That is a different scenario that is not described here.)
Step 2 To transfer files to the director, you must copy from the director, not to the director. The director must initiate the transfer. From the Cisco IOS console, enter these commands:
Director# copy tftp://tftp ip address/default_configuration.txt flash:
Director# copy tftp://tftp ip address/IOS_image_file.tar flash:
Note This normally takes several minutes.
Configure a Director
By default, new Ethernet switches shipped from Cisco (for example, Catalyst 2960 switches) boot up without a configuration file. These switches issue a DHCP request on the default VLAN that is configured for the Smart Install director. The director recognizes the DHCP request on the VLAN and responds.
In this example, the director is both the TFTP server and the DHCP server, and it serves IP addresses on VLAN 1.
Note If the director is a router, all clients connected to Layer 3 interfaces on the router will be recognized.
Step 1 Assign an IP address to the director on the VLAN 1 interface. If the director is a router, assign an IP address on any Layer 3 interface. You can also use a loopback interface on the director. In this example, the director_ip_address is 192.168.1.1.
Director(config)# interface vlan 1
Director(config)# ip address 192.168.1.1 255.255.255.0
Step 2 Configure the director for the default image and configuration file.
Director(config)# vstack config flash:default_configuration.txt
Director(config)# vstack image flash:IOS_image_file_name.tar
Step 3 Configure the director to serve as the DHCP server for clients.
Director(config)# vstack dhcp-localserver smart_install_pool
Director(config-vstack-dhcp)# address-pool network_ip_address 255.255.255.0
Director(config-vstack-dhcp)# file-server network_ip_address
Director(config-vstack-dhcp)# default-router network_ip_address
Director(config-vstack-dhcp)# exit
Director(config)# ip dhcp remember
Step 4 Enable Smart Install on the director.
Director(config)# vstack director director_ip_address
Director(config)# vstack basic
Any switch that boots up without a configuration file on the default Smart Install VLAN or on an Layer 3 interface on the router becomes a Smart Install client of the director. As clients are powered up and discovered by the director, they are updated and given the configuration defined in default_configuration.txt.
Note If the configuration file is not present when the smart install client boots up, the client attempts to retrieve the DHCP address from VLAN 1. If VLAN 1 is not allowed in the network, then the smart install client attempts to identify the startup VLAN from the CDP packets that it receives from the upstream data (that is, data received either from a smart install client that is already part of the network, or from the director that the client is connected to).
Use these commands to see the Smart Install network.
To see the update of new clients in progress: Director(config)# show vstack download
To see the clients and information about them: Director(config)# show vstack status
Third-Party, Non-Cisco IOS Device as the TFTP Server
In this example, the customer stores all client image and configuration files on an external, third-party server reachable by the director and client switches.
Before Configuring the Director
Define the Configuration File and Cisco IOS Image
Step 1 You must transfer files to the director and TFTP is the preferred method. Locate a TFTP server that is IP-reachable by the director, and put all files to be transferred on the TFTP server.
Step 2 Using a text editor, create a file with the configuration commands that you want for the default switch. In this example, the file name is default_configuration.txt.
Step 3 Save the default_configuration.txt to the TFTP server.
Step 4 Identify the Cisco IOS image you want loaded as the default image on the switches, for example c2960-lanbase-tar.122-53.SE.tar. Put that file in the TFTP server.
You should have two files on the TFTP server: the configuration file and the Cisco IOS image.
Note After the director is enabled and configured with the default image name, it automatically creates a tailored configuration file and an imagelist file for boot up and stores the files in the TFTP server.
Configure the Director
By default, new Ethernet switches shipped from Cisco (for example, Catalyst 2960 switches) boot up without a configuration file. These switches send a DHCP request on the default Smart Install VLAN. The director recognizes the DHCP request and responds.
Note If the director is a router, all clients connected to Layer 3 interfaces on the router are recognized.
In this example, the director is not acting as the TFTP server. It is acting as the DHCP server, and it serves IP addresses on VLAN 1.
Step 1 Assign an IP address to the director on the VLAN 1 interface on a switch or any Layer 3 interface on a router. In this example, the director_ip_address is 192.168.1.1.
Director(config)# interface vlan 1
Director(config)# ip address 192.168.1.1 255.255.255.0
Step 2 Configure the director for the default configuration file and image.
Director(config)# vstack config tftp://server-ip-address/default_configuration.txt
Director(config)# vstack image tftp://server-ip-address/default_image_file.tar
Step 3 Configure the director as the DHCP server for clients.
Director(config)# vstack dhcp-localserver smart_install_pool
Director(config-vstack-dhcp)# address-pool network_ip_address 255.255.255.0
Director(config-vstack-dhcp)# file-server network_ip_address
Director(config-vstack-dhcp)# default-router network_ip_address
Director(config-vstack-dhcp)# exit
Director(config)# ip dhcp remember
Step 4 Enable Smart Install on the director.
Director(config)# vstack director director_ip_address
Director(config)# vstack basic
Any switch that boots up without a configuration file on the default Smart Install VLAN or on a Layer 3 interface on the router, becomes a Smart Install client of the director. As clients power up and are discovered by the director, they are updated and given the configuration defined in default_configuration.txt.
Note If the configuration file is not present when the smart install client boots up, the client attempts to retrieve the DHCP address from VLAN 1. If VLAN 1 is not allowed in the network, then the smart install client attempts to identify the startup VLAN from the CDP packets that it receives from the upstream data (that is, data received either from a smart install client that is already part of the network, or from the director that the client is connected to).
Use these commands to see the Smart Install network.
To see the update of new clients in progress: Director# show vstack download status
To see the clients and information about them: Director# show vstack status
Feedback
