OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Managing Automatic Remote Configuration Download<br />
Automatic Remote Configuration Download Process<br />
Automatic Remote Configuration Download<br />
Process<br />
The automatic remote configuration process is initialized when an Omni<strong>Switch</strong> is integrated in to the<br />
network as a new device or when a firmware and configuration upgrade is required.<br />
If the automatic configuration download process is not performed completely on the switch, manual<br />
intervention is required. For details on troubleshooting techniques under such instances, see<br />
“Nearest-Edge Mode Operation” on page 12-17<br />
The detailed process of Automatic Remote Configuration Download performed on the Omni<strong>Switch</strong> is as<br />
follows:<br />
1 When the switch is integrated in to the network as a new device with no vcboot.cfg file, then Automatic<br />
Remote Configuration is performed on the switch.<br />
2 The Remote Configuration Manager on Omni<strong>Switch</strong> configures a link aggregate automatically when a<br />
LACP PDU is detected on the uplink ports on the switch during Automatic Remote Configuration. For<br />
details, see the following section “LACP Auto Detection and Automatic Link Aggregate Association” on<br />
page 12-19.<br />
3 A DHCP client is automatically configured on VLAN 1, <strong>Management</strong> VLAN, and VLAN 127 at<br />
switch boot up. Omni<strong>Switch</strong> then uses different methods of DHCP client configuration until connection to<br />
a DHCP Server is obtained. For details, see the following section “DHCP Client Auto-Configuration<br />
Process” on page 12-16<br />
4 The DHCP client obtains the switch IP address information from the DHCP server.<br />
5 The DHCP client obtains the TFTP server IP address from the DHCP server using Option (66).<br />
6 The DHCP client obtains the instruction file name and location from the DHCP server using Option<br />
(67).<br />
7 SSH access is automatically enabled to allow remote access in case the automatic configuration<br />
process fails.<br />
8 The instruction file with the .alu extension is downloaded from the TFTP server to the /flash/working<br />
directory of the Omni<strong>Switch</strong>.<br />
9 If available, the configuration, script, and images files are downloaded from the FTP or SFTP servers.<br />
The password used to connect to the FTP/SFTP servers is same as the username.<br />
10 If available, the switch compares the firmware version available on the switch with the firmware<br />
version in the instruction file. If the firmware versions are different, then the new firmware is downloaded<br />
in to the /flash/working directory.<br />
11 If available, the downloaded configuration file is saved as the vcboot.cfg file in the /flash/working<br />
directory and the switch is rebooted completing the auto configuration process (a reboot occurs only if no<br />
script file is downloaded).<br />
12 If available, commands in the script file are run and the DHCP client configuration is automatically<br />
removed.<br />
Omni<strong>Switch</strong> <strong>AOS</strong> Release 8 <strong>Switch</strong> <strong>Management</strong> <strong>Guide</strong> May 2014 page 12-9