Chapter 1
| Initial Switch Configuration
Configuring Automatic Installation of Operation Code and Configuration Settings
– 53 –
The general framework for this DHCP option is set out in RFC 2132 (Option 60). This
information is used to convey configuration settings or other identification
information about a client, but the specific string to use should be supplied by your
service provider or network administrator. Options 60 (vendor-class-identifier), 66
(tftp-server-name) and 67 (bootfile-name) statements can be added to the server
daemon’s configuration file as described in the following section.
If the DHCP server has an index entry for a switch requesting service, it should reply
with the TFTP server name and boot file name. Note that the vendor class identifier
can be formatted in either text or hexadecimal, but the format used by both the
client and server must be the same.
Console(config)#interface vlan 2
Console(config-if)#ip dhcp client class-id hex 0000e8666572
Console(config-if)#
Downloading a
Configuration File
Referenced by a
DHCP Server
Information passed on to the switch from a DHCP server may also include a
configuration file to be downloaded and the TFTP servers where that file can be
accessed. If the Factory Default Configuration file is used to provision the switch at
startup, in addition to requesting IP configuration settings from the DHCP server, it
will also ask for the name of a bootup configuration file and TFTP servers where
that file is stored.
If the switch receives information that allows it to download the remote bootup file,
it will save this file to a local buffer, and then restart the provision process.
Note the following DHCP client behavior:
◆
The bootup configuration file received from a TFTP server is stored on the
switch with the original file name. If this file name already exists in the switch,
the file is overwritten.
◆
If the name of the bootup configuration file is the same as the Factory Default
Configuration file, the download procedure will be terminated, and the switch
will not send any further DHCP client requests.
◆
If the switch fails to download the bootup configuration file based on
information passed by the DHCP server, it will not send any further DHCP client
requests.
◆
If the switch does not receive a DHCP response prior to completing the bootup
process, it will continue to send a DHCP client request once a minute. These
requests will only be terminated if the switch’s address is manually configured,
but will resume if the address mode is set back to DHCP.
Summary of Contents for EX-3524
Page 2: ......
Page 28: ...Figures 28 ...
Page 34: ...Section I Getting Started 34 ...
Page 58: ...Chapter 1 Initial Switch Configuration Setting the System Clock 58 ...
Page 72: ...Chapter 2 Using the Command Line Interface CLI Command Groups 72 ...
Page 156: ...Chapter 5 SNMP Commands Notification Log Commands 156 ...
Page 164: ...Chapter 6 Remote Monitoring Commands 164 ...
Page 218: ...Chapter 7 Authentication Commands Management IP Filter 218 ...
Page 268: ...Chapter 8 General Security Measures Port based Traffic Segmentation 268 ...
Page 292: ...Chapter 9 Access Control Lists ACL Information 292 ...
Page 312: ...Chapter 10 Interface Commands Power Savings 312 ...
Page 324: ...Chapter 11 Link Aggregation Commands Trunk Status Display Commands 324 ...
Page 366: ...Chapter 15 Address Table Commands 366 ...
Page 428: ...Chapter 17 VLAN Commands Configuring Voice VLANs 428 ...
Page 572: ...Chapter 25 IP Interface Commands IPv6 Interface 572 ...
Page 578: ...Section I Appendices 578 ...