Catalyst 2960 - Cap2

CHAPTER 2
Assigning the Switch IP Address and Default

Gateway
• Information About Performing Switch Setup Configuration, page 15
Information About Performing Switch Setup Configuration
Review the sections in this module before performing your initial switch configuration tasks that include IP
address assignments and DHCP autoconfiguration.
Understanding the Boot Process
To start your switch, you need to follow the procedures in the Getting Started Guide or the hardware installation
guide for installing and powering on the switch and for setting up the initial switch configuration (IP address,
subnet mask, default gateway, secret and Telnet passwords, and so forth).
The normal boot process involves the operation of the boot loader software, which performs these activities:
• Performs low-level CPU initialization. It initializes the CPU registers, which control where physical
memory is mapped, its quantity, its speed, and so forth.
• Performs power-on self-test (POST) for the CPU subsystem. It tests the CPU DRAM and the portion
of the flash device that makes up the flash file system.
• Loads a default operating system software image into memory and boots up the switch.
The boot loader provides access to the flash file system before the operating system is loaded. Normally, the
boot loader is used only to load, uncompress, and launch the operating system. After the boot loader gives
the operating system control of the CPU, the boot loader is not active until the next system reset or power-on.
The boot loader also provides trap-door access into the system if the operating system has problems serious
enough that it cannot be used. The trap-door mechanism provides enough access to the system so that if it is
necessary, you can format the flash file system, reinstall the operating system software image by using the
Xmodem Protocol, recover from a lost or forgotten password, and finally restart the operating system. For
more information, see the "Recovering from a Software Failure" section and the "Recovering from a Lost or
Forgotten Password" section.
Software Configuration Guide, Cisco IOS Release 15.2(2)E (Catalyst 2960, 2960-S, 2960-SF and 2960-Plus Switches)
OL-32521-01 15
Note You can disable password recovery. Formore information, see the "Disabling Password Recovery" section.
Before you can assign switch information, make sure you have connected a PC or terminal to the console
port, and configured the PC or terminal-emulation software baud rate and character format to match these of
the switch console port:
• Baud rate default is 9600.
• Data bits default is 8.
Note If the data bits option is set to 8, set the parity option to none.
• Stop bits default is 1.
• Parity settings default is none.
Switches Information Assignment
You can assign IP information through the switch setup program, through a DHCP server, or manually.
Use the switch setup program if you want to be prompted for specific IP information. With this program, you
can also configure a hostname and an enable secret password.
It gives you the option of assigning a Telnet password (to provide security during remote management) and
configuring your switch as a command or member switch of a cluster or as a standalone switch.
The switch stack is managed through a single IP address. The IP address is a system-level setting and is not
specific to the stack master or to any other stack member. You can still manage the stack through the same
IP address even if you remove the stack master or any other stack member from the stack, provided there is
IP connectivity.
Stack members retain their IP address when you remove them from a switch stack. To avoid a conflict by
having two devices with the same IP address in your network, change the IP address of the switch that
you removed from the switch stack.
Note
Use a DHCP server for centralized control and automatic assignment of IP information after the server is
configured.
If you are using DHCP, do not respond to any of the questions in the setup program until the switch
receives the dynamically assigned IP address and reads the configuration file.
Note
If you are an experienced user familiar with the switch configuration steps, manually configure the switch.
Otherwise, use the setup program described in the Boot Process section.
Software Configuration Guide, Cisco IOS Release 15.2(2)E (Catalyst 2960, 2960-S, 2960-SF and 2960-Plus
Switches)
16 OL-32521-01
Default Switch Information
Table 4: Default Switch Information
Feature Default Setting
IP address and subnet mask No IP address or subnet mask are defined.
Default gateway No default gateway is defined.
Enable secret password No password is defined.
Hostname The factory-assigned default hostname is Switch.
Telnet password No password is defined.
Cluster command switch functionality Disabled.
Cluster name No cluster name is defined.
DHCP-Based Autoconfiguration Overview
DHCP provides configuration information to Internet hosts and internetworking devices. This protocol consists
of two components: one for delivering configuration parameters from a DHCP server to a device and an
operation for allocating network addresses to devices. DHCP is built on a client-server model, in which
designated DHCP servers allocate network addresses and deliver configuration parameters to dynamically
configured devices. The switch can act as both a DHCP client and a DHCP server.
During DHCP-based autoconfiguration, your switch (DHCP client) is automatically configured at startup
with IP address information and a configuration file.
With DHCP-based autoconfiguration, no DHCP client-side configuration is needed on your switch. However,
you need to configure the DHCP server for various lease options associated with IP addresses.
If you want to use DHCP to relay the configuration file location on the network, you might also need to
configure a Trivial File Transfer Protocol (TFTP) server and a Domain Name System (DNS) server.
The DHCP server for your switch can be on the same LAN or on a different LAN than the switch. If the
DHCP server is running on a different LAN, you should configure a DHCP relay device between your switch
and the DHCP server. A relay device forwards broadcast traffic between two directly connected LANs. A
router does not forward broadcast packets, but it forwards packets based on the destination IP address in the
received packet.
DHCP-based autoconfiguration replaces the BOOTP client functionality on your switch.
DHCP Client Request Process
When you boot up your switch, the DHCP client is invoked and requests configuration information from a
DHCP server when the configuration file is not present on the switch. If the configuration file is present and
the configuration includes the ip address dhcp interface configuration command on specific routed interfaces,
the DHCP client is invoked and requests the IP address information for those interfaces.
OL-32521-01 17
This is the sequence of messages that are exchanged between the DHCP client and the DHCP server.
Figure 1: DHCP Client and Server Message Exchange
The client, Switch A, broadcasts a DHCPDISCOVER message to locate a DHCP server. The DHCP server
offers configuration parameters (such as an IP address, subnet mask, gateway IP address, DNS IP address, a
lease for the IP address, and so forth) to the client in a DHCPOFFER unicast message.
In a DHCPREQUEST broadcast message, the client returns a formal request for the offered configuration
information to the DHCP server. The formal request is broadcast so that all other DHCP servers that received
the DHCPDISCOVER broadcast message from the client can reclaim the IP addresses that they offered to
the client.
The DHCP server confirms that the IP address has been allocated to the client by returning a DHCPACK
unicast message to the client. With this message, the client and server are bound, and the client uses
configuration information received from the server. The amount of information the switch receives depends
on how you configure the DHCP server.
If the configuration parameters sent to the client in the DHCPOFFER unicast message are invalid (a
configuration error exists), the client returns a DHCPDECLINE broadcast message to the DHCP server.
The DHCP server sends the client a DHCPNAK denial broadcast message, which means that the offered
configuration parameters have not been assigned, that an error has occurred during the negotiation of the
parameters, or that the client has been slow in responding to the DHCPOFFER message (the DHCP server
assigned the parameters to another client).
A DHCP client might receive offers from multiple DHCP or BOOTP servers and can accept any of the offers;
however, the client usually accepts the first offer it receives. The offer from the DHCP server is not a guarantee
that the IP address is allocated to the client; however, the server usually reserves the address until the client
has had a chance to formally request the address. If the switch accepts replies from a BOOTP server and
configures itself, the switch broadcasts, instead of unicasts, TFTP requests to obtain the switch configuration
file.
The DHCP hostname option allows a group of switches to obtain hostnames and a standard configuration
from the central management DHCP server. A client (switch) includes in its DCHPDISCOVER message an
option 12 field used to request a hostname and other configuration parameters from the DHCP server. The
configuration files on all clients are identical except for their DHCP-obtained hostnames.
If a client has a default hostname (the hostname name global configuration command is not configured or
the no hostname global configuration command is entered to remove the hostname), the DHCP hostname
option is not included in the packet when you enter the ip address dhcp interface configuration command.
In this case, if the client receives the DCHP hostname option from the DHCP interaction while acquiring an
IP address for an interface, the client accepts the DHCP hostname option and sets the flag to show that the
system now has a hostname configured.
Switches)
18 OL-32521-01
DHCP-based Autoconfiguration and Image Update
You can use the DHCP image upgrade features to configure a DHCP server to download both a new image
and a new configuration file to one or more switches in a network. Simultaneous image and configuration
upgrade for all switches in the network helps ensure that each new switch added to a network receives the
same image and configuration.
There are two types of DHCP image upgrades: DHCP autoconfiguration and DHCP auto-image update.
Restrictions for DHCP-based Autoconfiguration
• The DHCP-based autoconfiguration with a saved configuration process stops if there is not at least one
Layer 3 interface in an up state without an assigned IP address in the network.
• Unless you configure a timeout, the DHCP-based autoconfiguration with a saved configuration feature
tries indefinitely to download an IP address.
• The auto-install process stops if a configuration file cannot be downloaded or if the configuration file
is corrupted.
• The configuration file that is downloaded from TFTP is merged with the existing configuration in the
running configuration but is not saved in the NVRAM unless you enter the write memory or
copy running-configuration startup-configuration privileged EXEC command. If the downloaded
configuration is saved to the startup configuration, the feature is not triggered during subsequent system
restarts.
DHCP Autoconfiguration
DHCP autoconfiguration downloads a configuration file to one or more switches in your network from a
DHCP server. The downloaded configuration file becomes the running configuration of the switch. It does
not over write the bootup configuration saved in the flash, until you reload the switch.
DHCP Auto-Image Update
You can use DHCP auto-image upgrade with DHCP autoconfiguration to download both a configuration and
a new image to one or more switches in your network. The switch (or switches) downloading the new
configuration and the new image can be blank (or only have a default factory configuration loaded).
If the new configuration is downloaded to a switch that already has a configuration, the downloaded
configuration is appended to the configuration file stored on the switch. (Any existing configuration is not
overwritten by the downloaded one.)
To enable a DHCP auto-image update on the switch, the TFTP server where the image and configuration files
are located must be configured with the correct option 67 (the configuration filename), option 66 (the DHCP
server hostname) option 150 (the TFTP server address), and option 125 (description of the Cisco IOS image
file) settings.
After you install the switch in your network, the auto-image update feature starts. The downloaded configuration
file is saved in the running configuration of the switch, and the new image is downloaded and installed on the
switch. When you reboot the switch, the configuration is stored in the saved configuration on the switch.
OL-32521-01 19
DHCP Server Configuration Guidelines
Follow these guidelines if you are configuring a device as a DHCP server:
• You should configure the DHCP server with reserved leases that are bound to each switch by the switch
hardware address.
• If you want the switch to receive IP address information, you must configure the DHCP server with
these lease options:
◦IP address of the client (required)
◦Subnet mask of the client (required)
◦DNS server IP address (optional)
◦Router IP address (default gateway address to be used by the switch) (required)
• If you want the switch to receive the configuration file from a TFTP server, you must configure the
DHCP server with these lease options:
◦TFTP server name (required)
◦Boot filename (the name of the configuration file that the client needs) (recommended)
◦Hostname (optional)
• Depending on the settings of the DHCP server, the switch can receive IP address information, the
configuration file, or both.
• If you do not configure the DHCP server with the lease options described previously, it replies to client
requests with only those parameters that are configured. If the IP address and the subnet mask are not
in the reply, the switch is not configured. If the router IP address or the TFTP server name are not found,
the switch might send broadcast, instead of unicast, TFTP requests. Unavailability of other lease options
does not affect autoconfiguration.
• The switch can act as a DHCP server. By default, the Cisco IOS DHCP server and relay agent features
are enabled on your switch but are not configured. (These features are not operational.)
Purpose of the TFTP Server
Based on the DHCP server configuration, the switch attempts to download one or more configuration files
from the TFTP server. If you configured the DHCP server to respond to the switch with all the options required
for IP connectivity to the TFTP server, and if you configured the DHCP server with a TFTP server name,
address, and configuration filename, the switch attempts to download the specified configuration file from
the specified TFTP server.
If you did not specify the configuration filename, the TFTP server, or if the configuration file could not be
downloaded, the switch attempts to download a configuration file by using various combinations of filenames
and TFTP server addresses. The files include the specified configuration filename (if any) and these files:
network-config, cisconet.cfg, hostname.config, or hostname.cfg, where hostname is the switch’s current
hostname. The TFTP server addresses used include the specified TFTP server address (if any) and the broadcast
address (255.255.255.255).
For the switch to successfully download a configuration file, the TFTP server must contain one or more
configuration files in its base directory. The files can include these files:
Switches)
20 OL-32521-01
• The configuration file named in the DHCP reply (the actual switch configuration file).
• The network-confg or the cisconet.cfg file (known as the default configuration files).
• The router-confg or the ciscortr.cfg file (These files contain commands common to all switches. Normally,
if the DHCP and TFTP servers are properly configured, these files are not accessed.)
If you specify the TFTP server name in the DHCP server-lease database, you must also configure the TFTP
server name-to-IP-address mapping in the DNS-server database.
If the TFTP server to be used is on a different LAN from the switch, or if it is to be accessed by the switch
through the broadcast address (which occurs if the DHCP server response does not contain all the required
information described previously), a relay must be configured to forward the TFTP packets to the TFTP server.
The preferred solution is to configure the DHCP server with all the required information.
Purpose of the DNS Server
The DHCP server uses the DNS server to resolve the TFTP server name to an IP address. You must configure
the TFTP server name-to-IP address map on the DNS server. The TFTP server contains the configuration
files for the switch.
You can configure the IP addresses of the DNS servers in the lease database of the DHCP server from where
the DHCP replies will retrieve them. You can enter up to two DNS server IP addresses in the lease database.
The DNS server can be on the same LAN or on a different LAN from the switch. If it is on a different LAN,
the switch must be able to access it through a router.
Purpose of the Relay Device
You must configure a relay device, also referred to as a relay agent, when a switch sends broadcast packets
that require a response from a host on a different LAN. Examples of broadcast packets that the switch might
send are DHCP, DNS, and in some cases, TFTP packets. You must configure this relay device to forward
received broadcast packets on an interface to the destination host.
If the relay device is a Cisco router, enable IP routing (ip routing global configuration command), and
configure helper addresses by using the ip helper-address interface configuration command.
Examples of Configuring the Relay Device
Configure the router interfaces as follows:
On interface 10.0.0.2:
router(config-if)# ip helper-address 20.0.0.2
On interface 20.0.0.1
OL-32521-01 21
Note If the switch is acting as the relay device, configure the interface as a routed port.
Figure 2: Relay Device Used in Autoconfiguration
How to Obtain Configuration Files
Depending on the availability of the IP address and the configuration filename in the DHCP reserved lease,
the switch obtains its configuration information in these ways:
• The IP address and the configuration filename is reserved for the switch and provided in the DHCP reply
(one-file read method).
The switch receives its IP address, subnet mask, TFTP server address, and the configuration filename
from the DHCP server. The switch sends a unicast message to the TFTP server to retrieve the named
configuration file from the base directory of the server and upon receipt, it completes its boot up process.
• The IP address and the configuration filename is reserved for the switch, but the TFTP server address
is not provided in the DHCP reply (one-file read method).
The switch receives its IP address, subnet mask, and the configuration filename from the DHCP server.
The switch sends a broadcast message to a TFTP server to retrieve the named configuration file from
the base directory of the server, and upon receipt, it completes its boot-up process.
• Only the IP address is reserved for the switch and provided in the DHCP reply. The configuration
filename is not provided (two-file read method).
The switch receives its IP address, subnet mask, and the TFTP server address from the DHCP server.
The switch sends a unicast message to the TFTP server to retrieve the network-confg or cisconet.cfg
default configuration file. (If the network-confg file cannot be read, the switch reads the cisconet.cfg
file.)
The default configuration file contains the hostnames-to-IP-address mapping for the switch. The switch
fills its host table with the information in the file and obtains its hostname. If the hostname is not found
in the file, the switch uses the hostname in the DHCP reply. If the hostname is not specified in the DHCP
reply, the switch uses the default Switch as its hostname.
After obtaining its hostname from the default configuration file or the DHCP reply, the switch reads the
configuration file that has the same name as its hostname (hostname-confg or hostname.cfg, depending
Switches)
22 OL-32521-01
on whether network-confg or cisconet.cfg was read earlier) from the TFTP server. If the cisconet.cfg
file is read, the filename of the host is truncated to eight characters.
If the switch cannot read the network-confg, cisconet.cfg, or the hostname file, it reads the router-confg
file. If the switch cannot read the router-confg file, it reads the ciscortr.cfg file.
The switch broadcasts TFTP server requests if the TFTP server is not obtained from the DHCP replies,
if all attempts to read the configuration file through unicast transmissions fail, or if the TFTP server name
cannot be resolved to an IP address.
Note
Example of DHCP-Based Autoconfiguration Network
A sample network for retrieving IP information using DHCP-based autoconfiguration.
Figure 3: DHCP-Based Autoconfiguration Network
Table 5: DHCP Server Configuration
Switch A Switch B Switch C Switch D
Binding key 00e0.9f1e.2001 00e0.9f1e.2002 00e0.9f1e.2003 00e0.9f1e.2004
(hardware address)
IP address 10.0.0.21 10.0.0.22 10.0.0.23 10.0.0.24
Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
Router address 10.0.0.10 10.0.0.10 10.0.0.10 10.0.0.10
DNS server address 10.0.0.2 10.0.0.2 10.0.0.2 10.0.0.2
tftpserver or
10.0.0.3
tftpserver or
10.0.0.3
tftpserver or
10.0.0.3
tftpserver or
10.0.0.3
TFTP server name
OL-32521-01 23
Switch A Switch B Switch C Switch D
Boot filename switcha-confg switchb-confg switchc-confg switchd-confg
(configuration file)
(optional)
Hostname (optional) switcha switchb switchc switchd
Switch A reads its configuration file as follows:
• It obtains its IP address 10.0.0.21 from the DHCP server.
• If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg file
from the base directory of the TFTP server.
• It adds the contents of the network-confg file to its host table.
• It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha).
• It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg from
the TFTP server.
Switches B through D retrieve their configuration files and IP addresses in the same way.
DNS Server Configuration
The DNS server maps the TFTP server name tftpserver to IP address 10.0.0.3.
TFTP Server Configuration (on UNIX)
The TFTP server base directory is set to /tftpserver/work/. This directory contains the network-confg file used
in the two-file read method. This file contains the hostname to be assigned to the switch based on its IP address.
The base directory also contains a configuration file for each switch (switcha-confg, switchb-confg, and so
forth) as shown in this display:
prompt> cd /tftpserver/work/
prompt> 1s
network-confg
switcha-confg
switchb-confg
switchc-confg
switchd-confg
prompt> cat network-confg
ip host switcha 10.0.0.21
ip host switchb 10.0.0.22
ip host switchc 10.0.0.23
ip host switchd 10.0.0.24
DHCP Client Configuration
No configuration file is present on Switch A through Switch D.
Configuration Explanation
In the figure, DHCP-based autoconfiguration network, the Switch A reads its configuration file as follows:
• It obtains its IP address 10.0.0.21 from the DHCP server.
Switches)
24 OL-32521-01
• If no configuration filename is given in the DHCP server reply, Switch A reads the network-confg file
from the base directory of the TFTP server.
• It adds the contents of the network-confg file to its host table.
• It reads its host table by indexing its IP address 10.0.0.21 to its hostname (switcha).
• It reads the configuration file that corresponds to its hostname; for example, it reads switch1-confg from
the TFTP server.
Switches B through D retrieve their configuration files and IP addresses in the same way.
Configuring the DHCP Auto Configuration and Image Update Features
Using DHCP to download a new image and a new configuration to a switch requires that you configure at
least two switches: One switch acts as a DHCP and TFTP server. The client switch is configured to download
either a new configuration file or a new configuration file and a new image file.
Configuring DHCP Autoconfiguration (Only Configuration File)
This task describes how to configure DHCP autoconfiguration of the TFTP and DHCP settings on an existing
switch in the network so that it can support the autoconfiguration of a new switch.
SUMMARY STEPS
1. configure terminal
2. ip dhcp pool poolname
3. boot filename
4. network network-number mask prefix-length
5. default-router address
6. option 150 address
7. exit
8. tftp-server flash:filename.text
9. interface interface-id
10. no switchport
11. ip address address mask
12. end
DETAILED STEPS
Command or Action Purpose
configure terminal Enters global configuration mode.
Example:
Switch# configure terminal
Step 1
OL-32521-01 25
Creates a name for the DHCP server address pool, and
enters DHCP pool configuration mode.
ip dhcp pool poolname
Example:
Switch(config)# ip dhcp pool pool
Step 2
Specifies the name of the configuration file that is used as
a boot image.
boot filename
Example:
Switch(dhcp-config)# boot config-boot.text
Step 3
Specifies the subnet network number and mask of the DHCP
address pool.
network network-number mask prefix-length
Example:
Switch(dhcp-config)# network 10.10.10.0
Step 4
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 (/).
Note
255.255.255.0
Specifies the IP address of the default router for a DHCP
client.
default-router address
Example:
Switch(dhcp-config)# default-router 10.10.10.1
Step 5
option 150 address Specifies the IP address of the TFTP server.
Example:
Switch(dhcp-config)# option 150 10.10.10.1
Step 6
exit Returns to global configuration mode.
Example:
Switch(dhcp-config)# exit
Step 7
tftp-server flash:filename.text Specifies the configuration file on the TFTP server.
Example:
Switch(config)# tftp-server
Step 8
flash:config-boot.text
Switches)
26 OL-32521-01
Specifies the address of the client that will receive the
configuration file.
interface interface-id
Example:
Switch(config)# interface gigabitethernet1/0/4
Step 9
no switchport Puts the interface into Layer 3 mode.
Example:
Switch(config-if)# no switchport
Step 10
ip address address mask Specifies the IP address and mask for the interface.
Example:
Switch(config-if)# ip address 10.10.10.1
Step 11
255.255.255.0
end Returns to privileged EXEC mode.
Example:
Switch(config-if)# end
Step 12
Configuring DHCP Auto-Image Update (Configuration File and Image)
This task describes DHCP autoconfiguration to configure TFTP and DHCP settings on an existing switch to
support the installation of a new switch.
Before You Begin
You must first create a text file (for example, autoinstall_dhcp) that will be uploaded to the switch. In the text
file, put the name of the image that you want to download (forexample,
c3750e-ipservices-mz.122-44.3.SE.tarc3750x-ipservices-mz.122-53.3.SE2.tar). This image must be a tar and
not a bin file.
OL-32521-01 27
SUMMARY STEPS
2. ip dhcp pool poolname
3. boot filename
4. network network-number mask prefix-length
5. default-router address
6. option 150 address
7. option 125 hex
8. copy tftp flash filename.txt
9. copy tftp flash imagename.bin
10. exit
11. tftp-server flash: config.text
12. tftp-server flash: imagename.bin
13. tftp-server flash: filename.txt
14. interface interface-id
15. no switchport
16. ip address address mask
17. end
18. copy running-config startup-config
DETAILED STEPS
Example:
Step 1
Creates a name for the DHCP server address
pool and enter DHCP pool configuration mode.
ip dhcp pool poolname
Example:
Switch(config)# ip dhcp pool pool1
Step 2
Specifies the name of the file that is used as a
boot image.
boot filename
Example:
Switch(dhcp-config)# boot config-boot.text
Step 3
Switches)
28 OL-32521-01
Specifies the subnet network number and mask
of the DHCP address pool.
network network-number mask prefix-length
Example:
Switch(dhcp-config)# network 10.10.10.0 255.255.255.0
Step 4
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 (/).
Note
Specifies the IP address of the default router for
a DHCP client.
default-router address
Example:
Switch(dhcp-config)# default-router 10.10.10.1
Step 5
option 150 address Specifies the IP address of the TFTP server.
Example:
Switch(dhcp-config)# option 150 10.10.10.1
Step 6
Specifies the path to the text file that describes
the path to the image file.
option 125 hex
Example:
Switch(dhcp-config)# option 125 hex
Step 7
0000.0009.0a05.08661.7574.6f69.6e73.7461.6c6c.5f64.686370
copy tftp flash filename.txt Uploads the text file to the switch.
Example:
Switch(config)# copy tftp flash image.bin
Step 8
Uploads the tar file for the new image to the
switch.
copy tftp flash imagename.bin
Example:
Switch(config)# copy tftp flash image.bin
Step 9
Example:
Switch(dhcp-config)# exit
Step 10
OL-32521-01 29
Specifies the Cisco IOS configuration file on
the TFTP server.
tftp-server flash: config.text
Example:
Switch(config)# tftp-server flash:config-boot.text
Step 11
tftp-server flash: imagename.bin Specifies the image name on the TFTP server.
Example:
Switch(config)# tftp-server flash:image.bin
Step 12
Specifies the text file that contains the name of
the image file to download
tftp-server flash: filename.txt
Example:
Switch(config)# tftp-server flash:boot-config.text
Step 13
Specifies the address of the client that will
receive the configuration file.
interface interface-id
Example:
Switch(config)# interface gigabitEthernet1/0/4
Step 14
no switchport Puts the interface into Layer 3 mode.
Example:
Switch(config-if)# no switchport
Step 15
Specifies the IP address and mask for the
interface.
ip address address mask
Example:
Switch(config-if)# ip address 10.10.10.1 255.255.255.0
Step 16
Example:
Step 17
(Optional) Saves your entries in the
configuration file.
copy running-config startup-config
Example:
Step 18
Switches)
30 OL-32521-01
Configuring the Client to Download Files from DHCP Server
You should only configure and enable the Layer 3 interface. Do not assign an IP address or DHCP-based
autoconfiguration with a saved configuration.
Note
SUMMARY STEPS
2. boot host dhcp
3. boot host retry timeout timeout-value
4. banner config-save ^C warning-message ^C
5. end
6. show boot
DETAILED STEPS
Example:
Step 1
boot host dhcp Enables autoconfiguration with a saved configuration.
Example:
Switch(conf)# boot host dhcp
Step 2
(Optional) Sets the amount of time the system tries to
download a configuration file.
boot host retry timeout timeout-value
Example:
Switch(conf)# boot host retry timeout 300
Step 3
If you do not set a timeout, the system will try
indefinitely to obtain an IP address from the
DHCP server.
Note
(Optional) Creates warning messages to be displayed when
you try to save the configuration file to NVRAM.
banner config-save ^C warning-message ^C
Example:
Switch(conf)# banner config-save ^C Caution -
Step 4
Saving Configuration File
to NVRAM May Cause You to No longer Automatically
Download Configuration Files at Reboot^C
OL-32521-01 31
Example:
Step 5
show boot Verifies the configuration.
Example:
Switch# show boot
Step 6
Manually Assigning IP Information to Multiple SVIs
This task describes how to manually assign IP information to multiple switched virtual interfaces (SVIs):
SUMMARY STEPS
2. interface vlan vlan-id
3. ip address ip-address subnet-mask
4. exit
5. ip default-gateway ip-address
6. end
7. show interfaces vlan vlan-id
8. show ip redirects
DETAILED STEPS
Example:
Step 1
Enters interface configuration mode, and enters the VLAN to which
the IP information is assigned. The range is 1 to 4094.
interface vlan vlan-id
Example:
Switch(config)# interface vlan 99
Step 2
Switches)
32 OL-32521-01
ip address ip-address subnet-mask Enters the IP address and subnet mask.
Example:
Switch(config-vlan)# ip address
Step 3
10.10.10.2 255.255.255.0
Example:
Switch(config-vlan)# exit
Step 4
Enters the IP address of the next-hop router interface that is directly
connected to the switch where a default gateway is being configured.
ip default-gateway ip-address
Example:
Switch(config)# ip default-gateway
Step 5
The default gateway receives IP packets with unresolved destination
IP addresses from the switch.
Once the default gateway is configured, the switch has connectivity
to the remote networks with which a host needs to communicate.
10.10.10.1
When your switch is configured to route with IP, it does
not need to have a default gateway set.
Note
The switch capwap relays on default-gateway configuration
to support routed access point join the switch.
Note
Example:
Switch(config)# end
Step 6
show interfaces vlan vlan-id Verifies the configured IP address.
Example:
Switch# show interfaces vlan 99
Step 7
show ip redirects Verifies the configured default gateway.
Example:
Switch# show ip redirects
Step 8
OL-32521-01 33
Checking and Saving the Running Configuration
You can check the configuration settings that you entered or changes that you made by entering this privileged
EXEC command:
Switch# show running-config
Building configuration...
Current configuration: 1363 bytes
!
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname
!
enable secret 5 $1$ej9.$DMUvAUnZOAmvmgqBEzIxE0
!.
<output truncated>
.
ip address 172.20.137.50 255.255.255.0
!
mvr type source
<output truncated>
...!
interface VLAN1
ip address 172.20.137.50 255.255.255.0
no ip directed-broadcast
!
ip default-gateway 172.20.137.1 !
!
snmp-server community private RW
snmp-server community public RO
snmp-server community private@es0 RW
snmp-server community public@es0 RO
snmp-server chassis-id 0x12
!
end
To store the configuration or changes you have made to your startup configuration in flash memory, enter
this privileged EXEC command:
Switch# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
This command saves the configuration settings that you made. If you fail to do this, your configuration will
be lost the next time you reload the system. To display information stored in the NVRAM section of flash
memory, use the show startup-config or more startup-config privileged EXEC command.
For more information about alternative locations from which to copy the configuration file, see "Working
with the Cisco IOS File System, Configuration Files, and Software Images."
Configuring the NVRAM Buffer Size
The default NVRAM buffer size is 512 KB. In some cases, the configuration file might be too large to save
to NVRAM. Typically, this occurs when you have many switches in a switch stack. You can configure the
size of the NVRAM buffer to support larger configuration files. The new NVRAM buffer size is synced to
all current and new member switches.
Switches)
34 OL-32521-01
After you configure the NVRAM buffer size, reload the switch or switch stack.
When you add a switch to a stack and the NVRAM size differs, the new switch syncs with the stack and
reloads automatically.
Note
Beginning in privileged EXEC mode, follow these steps to configure the NVRAM buffer size:
SUMMARY STEPS
2. boot buffersizesize
3. end
4. show boot
DETAILED STEPS
Step 1 configure terminal Enter global configuration mode.
Configure the NVRAM buffersize in KB. The valid range for size is from 4096 to
1048576 .
Step 2 boot buffersizesize
Step 3 end Return to privileged EXEC mode.
Verify the configuration.
This example shows how to configure the NVRAM buffer size:
Enter configuration commands, one per line. End with CNTL/Z.
Step 4 show boot
Switch(config)# boot buffersize 524288
Switch(config)# end
Switch# show boot
BOOT path-list :
Config file : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break : no
Manual Boot : no
HELPER path-list :
Auto upgrade : yes
Auto upgrade path :
NVRAM/Config file
buffer size: 524288
Timeout for Config
Download: 300 seconds
Config Download
via DHCP: enabled (next boot: enabled)
Switch#
OL-32521-01 35
Modifying the Switch Startup Configuration
Default Boot Configuration
Feature Default Setting
The switch attempts to automatically boot up the system using information
in the BOOT environment variable. If the variable is not set, the switch
attempts to load and execute the first executable image it can by performing
a recursive, depth-first search throughout the flash file system.
The Cisco IOS image is stored in a directory that has the same name as the
image file (excluding the .bin extension).
In a depth-first search of a directory, each encountered subdirectory is
completely searched before continuing the search in the original directory.
Operating system software
image
Configured switches use the config.text file stored on the system board in
flash memory.
A new switch has no configuration file.
Configuration file
Automatically Downloading a Configuration File
You can automatically download a configuration file to your switch by using the DHCP-based autoconfiguration
feature. For more information, see the "Understanding DHCP-Based Autoconfiguration" section.
Specifying the Filename to Read and Write the System Configuration
By default, the Cisco IOS software uses the config.text file to read and write a nonvolatile copy of the system
configuration. However, you can specify a different filename, which will be loaded during the next boot cycle.
Before You Begin
Use a standalone switch for this task.
SUMMARY STEPS
2. boot flash:/file-url
3. end
4. show boot
Switches)
36 OL-32521-01
DETAILED STEPS
Example:
Step 1
Specifies the configuration file to load during the next boot
cycle.
boot flash:/file-url
Example:
Switch(config)# boot flash:config.text
Step 2
file-url—The path (directory) and the configuration filename.
Filenames and directory names are case-sensitive.
Example:
Switch(config)# end
Step 3
Step 4 show boot Verifies your entries.
Example:
Switch# show boot
The boot global configuration command changes the setting of
the CONFIG_FILE environment variable.
copy running-config startup-config (Optional) Saves your entries in the configuration file.
Example:
Step 5
Manually Booting the Switch
By default, the switch automatically boots up; however, you can configure it to manually boot up.
Before You Begin
Use a standalone switch for this task.
OL-32521-01 37
SUMMARY STEPS
2. boot manual
3. end
4. show boot
DETAILED STEPS
Example:
Step 1
boot manual Enables the switch to manually boot up during the next boot cycle.
Example:
Switch(config)# boot manual
Step 2
Example:
Switch(config)# end
Step 3
Step 4 show boot Verifies your entries.
Example:
Switch# show boot
The boot manual global command changes the setting of the
MANUAL_BOOT environment variable.
The next time you reboot the system, the switch is in boot loader mode,
shown by the switch: prompt. To boot up the system, use the boot
filesystem:/file-url boot loader command.
• filesystem:—Uses flash: for the system board flash device.
switch: boot flash:
• For file-url—Specifies the path (directory) and the name of the
bootable image.
Filenames and directory names are case-sensitive.
copy running-config startup-config (Optional) Saves your entries in the configuration file.
Example:
Switch# copy running-config
Step 5
Switches)
38 OL-32521-01
startup-config
Booting a Specific Software Image On a Switch Stack
By default, the switch attempts to automatically boot up the system using information in the BOOT environment
variable. If this variable is not set, the switch attempts to load and execute the first executable image it can
by performing a recursive, depth-first search throughout the flash file system. In a depth-first search of a
directory, each encountered subdirectory is completely searched before continuing the search in the original
directory. However, you can specify a specific image to boot up.
SUMMARY STEPS
2. boot system switch {number | all}
3. end
4. show boot system
DETAILED STEPS
Example:
Step 1
(Optional) For switches in a stack, specifies the
switch members on which the system image is
loaded during the next boot cycle:
boot system switch {number | all}
Example:
Switch(config)# boot system switch 2
Step 2
• Use number to specify a stack member.
flash:cat3850-universalk9.SSA.03.08.83.EMD.150-8.83.EMD.bin (Specify only one stack member.)
• Use all to specify all stack members.
If you enter on a Catalyst 3750-X stack master or
member, you can only specify the switch image for
other Catalyst 3750-X stack members.
If you enter on a Catalyst 3750-E stack master or
member, you can only specify the switch image for
other Catalyst 3750-E stack members.
OL-32521-01 39
If you want to specify the image for a Catalyst 3750
switch, enter this command on the Catalyst 3750
stack member.
Example:
Switch(config)# end
Step 3
Step 4 show boot system Verifies your entries.
Example:
Switch# show boot system
The boot system global command changes the
setting of the BOOT environment variable.
During the next boot cycle, the switch attempts to
automatically boot up the system using information
in the BOOT environment variable.
(Optional) Saves your entries in the configuration
file.
copy running-config startup-config
Example:
Step 5
Controlling Environment Variables
With a normally operating switch, you enter the boot loader mode only through a switch console connection
configured for 9600 b/s. Unplug the switch power cord, and press the switch Mode button while reconnecting
the power cord. You can release the Mode button a second or two after the LED above port 1 turns off. Then
the boot loader switch: prompt appears.
The switch boot loader software provides support for nonvolatile environment variables, which can be used
to control how the boot loader, or any other software running on the system, behaves. Boot loader environment
variables are similar to environment variables that can be set on UNIX or DOS systems.
Environment variables that have values are stored in flash memory outside of the flash file system.
Each line in these files contains an environment variable name and an equal sign followed by the value of the
variable. A variable has no value if it is not listed in this file; it has a value if it is listed in the file even if the
value is a null string. A variable that is set to a null string (for example, " ") is a variable with a value. Many
environment variables are predefined and have default values.
Environment variables store two kinds of data:
• Data that controls code, which does not read the Cisco IOS configuration file. For example, the name
of a boot loader helper file, which extends or patches the functionality of the boot loader can be stored
as an environment variable.
• Data that controls code, which is responsible for reading the Cisco IOS configuration file. For example,
the name of the Cisco IOS configuration file can be stored as an environment variable.
Switches)
40 OL-32521-01
You can change the settings of the environment variables by accessing the boot loader or by using Cisco IOS
commands. Under normal circumstances, it is not necessary to alter the setting of the environment variables.
For complete syntax and usage information for the boot loader commands and environment variables, see
the command reference for this release.
Note
Table 6: Environment Variables
Cisco IOS Global Configuration
Command
Variable Boot Loader Command
boot systemfilesystem:/file-url ...
Specifies the Cisco IOS image to
load during the next boot cycle.
This command changes the setting
of the BOOT environment variable
set BOOT filesystem :/ file-url
...
A semicolon-separated list of
executable files to try to load and
execute when automatically
booting. If the BOOT
environment variable is not set,
the system attempts to load and
execute the first executable image
it can find by using a recursive,
depth-first search through the
flash file system. If the BOOT
variable is set but the specified
images cannot be loaded, the
system attempts to boot the first
bootable file that it can find in the
flash file system.
BOOT
boot manual
Enables manually booting up the
switch during the next boot cycle
and changes the setting of the
MANUAL_BOOT environment
variable.
The next time you reboot the
system, the switch is in boot loader
mode. To boot up the system, use
the boot flash: filesystem :/ file-url
boot loader command, and specify
the name of the bootable image.
set MANUAL_BOOT yes
Decides whether the switch
automatically or manually boots
up.
Valid values are 1, yes, 0, and no.
If it is set to no or 0, the boot
loader attempts to automatically
boot up the system. If it is set to
anything else, you must manually
boot up the switch from the boot
loader mode.
MANUAL_BOOT
OL-32521-01 41
Cisco IOS Global Configuration
Command
Variable Boot Loader Command
boot config-file flash:/ file-url
Specifies the filename that Cisco
IOS uses to read and write a
nonvolatile copy of the system
configuration. This command
changes the CONFIG_FILE
environment variable.
set CONFIG_FILE flash: /
file-url
CONFIG_FILE
Scheduling a Reload of the Software Image
You can schedule a reload of the software image to occur on the switch at a later time (for example, late at
night or during the weekend when the switch is used less), or you can synchronize a reload network-wide (for
example, to perform a software upgrade on all switches in the network).
Note A scheduled reload must take place within approximately 24 days.
Configuring a Scheduled Reload
To configure your switch to reload the software image at a later time, use one of these commands in privileged
EXEC mode:
• reload in [hh :]mm [text]
This command schedules a reload of the software to take affect in the specified minutes or hours and
minutes. The reload must take place within approximately 24 days. You can specify the reason for the
reload in a string up to 255 characters in length.
• reload at hh:mm [month dayIday month [text]
This command schedules a reload of the software to take place at the specified time (using a 24-hour
clock). If you specify the month and day, the reload is scheduled to take place at the specified time and
date. If you do not specify the month and day, the reload takes place at the specified time on the current
day (if the specified time is later than the current time) or on the next day (if the specified time is earlier
than the current time). Specifying 00:00 schedules the reload for midnight.
Use the at keyword only if the switch system clock has been set (through Network Time
Protocol (NTP), the hardware calendar, or manually). The time is relative to the
configured time zone on the switch. To schedule reloads across several switches to occur
simultaneously, the time on each switch must be synchronized with NTP.
Note
The reload command halts the system. If the system is not set to manually boot up, it reboots itself. Use
the reload command after you save the switch configuration information to the startup configuration
(copy running-config startup-config).
Switches)
42 OL-32521-01
If your switch is configured for manual booting, do not reload it from a virtual terminal. This restriction
prevents the switch from entering the boot loader mode and thereby taking it from the remote user's
control.
If you modify your configuration file, the switch prompts you to save the configuration before reloading.
During the save operation, the system requests whether you want to proceed with the save if the CONFIG_FILE
environment variable points to a startup configuration file that no longer exists. If you proceed in this situation,
the system enters setup mode upon reload.
This example shows how to reload the software on the switch on the current day at 7:30 p.m:
Switch# reload at 19:30
Reload scheduled for 19:30:00 UTC Wed Jun 5 1996 (in 2 hours and 25 minutes)
Proceed with reload? [confirm]
This example shows how to reload the software on the switch at a future time:
Switch# reload at 02:00 jun 20
Reload scheduled for 02:00:00 UTC Thu Jun 20 1996 (in 344 hours and 53 minutes)
Proceed with reload? [confirm]
To cancel a previously scheduled reload, use the reload cancel privileged EXEC command
Displaying Scheduled Reload Information
To display information about a previously scheduled reload or to find out if a reload has been scheduled on
the switch, use the show reload privileged EXEC command.
It displays reload information including the time the reload is scheduled to occur and the reason for the reload
(if it was specified when the reload was scheduled).
Boot Loader Upgrade and Image Verification for the FIPS Mode of Operation
To operate in the FIPS mode, complete these steps:
• Enable the FIPS mode on the switch.To enable the FIPS mode, enter the fips authorization-key
authorization-key global configuration command. To disable the FIPS mode, use the no version of the
command.
• Use signed and validated images. Cisco IOS Release 15.2(1)E supports an updated boot loader that can
validate the Cisco IOS image signature only in the FIPS mode of operation.
Ensure that the power is not turned off while updating the boot loader. If the power is turned off during
the update, you will have to replace the switch by using a Return Merchandise Authorization (RMA)
license.
Note
Table 4-6 describes upgrade and downgrade scenarios using different images and using the FIPS mode or
non-FIPS mode:
OL-32521-01 43
Table 7: Upgrade and Downgrade Scenarios Relating to FIPS Certified Images
Upgrade/ Downgrade Scenario Action Status or Result
• The boot loader is upgraded.
• The image signature is
verified.
• The following message
appears in the boot sequence:
“Image passed digital
signature verification.”
If you upload a corrupt or
unsigned image, the
following message
appears during boot up:
“Image verification
failed.”
Note
Boot with the Cisco IOS Release
15.2(1)E image.
Upgrade from an image that is in
the FIPS mode to a Cisco IOS
Release 15.2(1)E image in the FIPS
mode.
• The boot loader is upgraded.
• The image signature is
verified.
unsigned image, the
following message
appears during boot up:
“Image verification failed.
Note
• Configure the fips
authorization- key
authorization-key global
configuration command
• Reload the switch for the
FIPS key to be operational.
By default, the switch
automatically boots up;
however, if you have
configured it to boot up
manually, you have to initiate
the reboot.
• After the boot loader is
upgraded, boot with the Cisco
IOS Release 15.2(1)E image.
Upgrade from a switch that is in
the non-FIPS mode to a Cisco IOS
Release 15.2(1)E image in the FIPS
mode
• The boot loader is not
updated.
• The image signature is not
verified
• The switch works normally.
Boot with the Cisco IOS Release
15.2(1)E image.
Upgrade to Cisco IOS Release
15.2(1)E in the non-FIPS mode
Switches)
44 OL-32521-01
Upgrade/ Downgrade Scenario Action Status or Result
updated.
• The switch works normally
and the FIPS commands are
no longer available.
“Image passed digital
signature verification”.
unsigned image, the
following message appears
during boot up:
“WARNING: Unable to
determine image
authentication. Image is
either unsigned or is
signed but corrupted.”
Note
• Configure the no fips
authorization- key
configuration command.
configuration to take effect.
the reboot.
Configure an existing FIPS
complaint switch running Cisco
IOS Release 15.2(1)E to work in a
non-FIPS mode.
downgraded
• The switch work normally
and the FIPS commands are
no longer available.
“WARNING: Unable to
determine image
authentication. Image is
either unsigned or is signed
but corrupted.”
• Configure the no fips
authorization- key
configuration command
configuration to take effect.
reboot.
• Upload and boot the older
image.
Downgrade from a Cisco IOS
Release 15.2(1)E image in FIPS
mode to an older release.
OL-32521-01 45
Switches)
46 OL-32521-01
PA R T II
Configuring Cisco IOS Configuration Engine
• Configuring Cisco IOS Configuration Engine, page 49

Catalyst 2960 - Cap2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Catalyst 2960 - Cap2

Uploaded by

Copyright:

Available Formats

CHAPTER 2

Assigning the Switch IP Address and Default

You might also like