Administration: File Management
DHCP Auto Configuration/Image Update
Cisco 350, 350X and 550X Series Managed Switches, Firmware Release 2.4, ver 0.4 111
7
Auto Configuration/Image Update via DHCPv6 is triggered when the following conditions are
fulfilled:
• When a DHCPv6 server sends information to the device. This occurs in the following
cases:
- When an IPv6-enabled interface is defined as a DHCPv6 stateless configuration
client.
- When DHCPv6 messages are received from the server (for example, when you
press the Restart button on IPv6 Interfaces page,
- When DHCPv6 information is refreshed by the device.
- After rebooting the device when stateless DHCPv6 client is enabled.
• When the DHCPv6 server packets contain the configuration filename option.
• The Auto Image Update process is triggered when an indirect image file name is
provided by the DHCP server or a backup indirect image file name has been
configured. Indirect means that this is not the image itself, but rather a file that holds
the path name to the image.
Auto Configuration Image Update in a Stack
The current master of a stack is responsible for the Auto Configuration/Image Update of the
whole stack.
For auto configuration, the new configuration file is downloaded to the master unit and
synchronized to backup before reload.
For auto image update, the new image is copied and saved to the inactive-image of the master
unit. As the part of the copy process the master unit synchronizes the image to all the units in
the stack before the reload.
A configuration file that is placed on the TFTP/SCP server must match the form and format
requirements of the supported configuration file. The form and format of the file are checked,
but the validity of the configuration parameters is not checked prior to loading it to the Startup
Configuration.
To Next Page
Loading...
Need help?
General
