OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Recommendations

Info

Interaction With Other Features Managing Automatic Remote Configuration Download Interaction With Other Features This section contains important information about how other OmniSwitch features interact with Automatic Remote Configuration. Refer to the specific sections if required, to get detailed information about the feature interaction process. UDP/DHCP Relay Interaction with UDP/DHCP Relay is required for the following processes, to support Automatic Remote Configuration: • All the DHCP responses from the DHCP server are processed. The IP address, mask, and gateway details are processed • To acquire Option (66) and Option(67) information - the TFTP Server name and Boot file name are retrieved. For details on DHCP interaction see the section “DHCP Client Auto-Configuration Process” on page 12-16 802.1Q LLDP 802.1Q tagging is applied on VLAN 127 or the Management VLAN. In Nearest-Edge mode operation LLDP packets carry and provide the advertised VLAN ID to the Access OmniSwitches running in Auto Remote Configuration mode. Dynamic Link Aggregation (LACP) Interaction with LACP is required for the following processes, to support Automatic Remote Configuration: • To detect LACP PDU from the peer device on uplink ports • To enable the auto link aggregate creation after receiving LACP message • The link aggregate is associated as a tagged member of VLAN 127 and VLAN 1. On completion of the Automatic Download and configuration process, the automatic link aggregate is disabled and all port associations are deleted. page 12-8 OmniSwitch AOS Release 8 Switch Management Guide May 2014
Managing Automatic Remote Configuration Download Automatic Remote Configuration Download Process Automatic Remote Configuration Download Process The automatic remote configuration process is initialized when an OmniSwitch is integrated in to the network as a new device or when a firmware and configuration upgrade is required. If the automatic configuration download process is not performed completely on the switch, manual intervention is required. For details on troubleshooting techniques under such instances, see “Nearest-Edge Mode Operation” on page 12-17 The detailed process of Automatic Remote Configuration Download performed on the OmniSwitch is as follows: 1 When the switch is integrated in to the network as a new device with no vcboot.cfg file, then Automatic Remote Configuration is performed on the switch. 2 The Remote Configuration Manager on OmniSwitch configures a link aggregate automatically when a LACP PDU is detected on the uplink ports on the switch during Automatic Remote Configuration. For details, see the following section “LACP Auto Detection and Automatic Link Aggregate Association” on page 12-19. 3 A DHCP client is automatically configured on VLAN 1, Management VLAN, and VLAN 127 at switch boot up. OmniSwitch then uses different methods of DHCP client configuration until connection to a DHCP Server is obtained. For details, see the following section “DHCP Client Auto-Configuration Process” on page 12-16 4 The DHCP client obtains the switch IP address information from the DHCP server. 5 The DHCP client obtains the TFTP server IP address from the DHCP server using Option (66). 6 The DHCP client obtains the instruction file name and location from the DHCP server using Option (67). 7 SSH access is automatically enabled to allow remote access in case the automatic configuration process fails. 8 The instruction file with the .alu extension is downloaded from the TFTP server to the /flash/working directory of the OmniSwitch. 9 If available, the configuration, script, and images files are downloaded from the FTP or SFTP servers. The password used to connect to the FTP/SFTP servers is same as the username. 10 If available, the switch compares the firmware version available on the switch with the firmware version in the instruction file. If the firmware versions are different, then the new firmware is downloaded in to the /flash/working directory. 11 If available, the downloaded configuration file is saved as the vcboot.cfg file in the /flash/working directory and the switch is rebooted completing the auto configuration process (a reboot occurs only if no script file is downloaded). 12 If available, commands in the script file are run and the DHCP client configuration is automatically removed. OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 12-9
Page 1 and 2:
Part No. 060391-10, Rev. A May 2014
Page 3 and 4:
Contents About This Guide .........
Page 5 and 6:
Contents Using the Switch as an FTP
Page 7 and 8:
Contents Account and Password Polic
Page 9 and 10:
Contents Authentication Trap ......
Page 11 and 12:
Contents Firmware Upgrade Files ...
Page 13 and 14:
About This Guide This OmniSwitch AO
Page 15 and 16:
About This Guide Documentation Road
Page 17 and 18:
About This Guide Related Documentat
Page 19 and 20:
1 Logging Into the Switch Logging i
Page 21 and 22:
Logging Into the Switch Quick Steps
Page 23 and 24:
Logging Into the Switch Overview of
Page 25 and 26:
Logging Into the Switch Accessing t
Page 27 and 28:
Logging Into the Switch Setting the
Page 29 and 30:
Logging Into the Switch Using Secur
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Logging Into the Switch Modifying t
Page 37 and 38:
Logging Into the Switch Enabling th
Page 39 and 40:
Logging Into the Switch Enabling th
Page 41 and 42:
2 Managing System Files This chapte
Page 43 and 44:
Managing System Files Switch Admini
Page 45 and 46:
Managing System Files File and Dire
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Managing System Files Loading Softw
Page 55 and 56:
Managing System Files Loading Softw
Page 57 and 58:
Managing System Files Setting the S
Page 59 and 60:
Managing System Files Setting the S
Page 61 and 62:
3 Managing CMM Directory Content Th
Page 63 and 64:
Managing CMM Directory Content CMM
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Managing CMM Directory Content Mana
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Managing CMM Directory Content Usin
Page 77 and 78:
4 Using the CLI Alcatel-Lucent’s
Page 79 and 80:
Using the CLI Command Entry Rules a
Page 81 and 82:
Using the CLI Command Help -> sh vl
Page 83 and 84:
Using the CLI Logging CLI Commands
Page 85 and 86:
Using the CLI Customizing the Scree
Page 87 and 88:
5 Working With Configuration Files
Page 89 and 90:
Working With Configuration Files Tu
Page 91 and 92:
Working With Configuration Files Qu
Page 93 and 94:
Working With Configuration Files Co
Page 95 and 96:
Working With Configuration Files Cr
Page 97 and 98:
Working With Configuration Files Cr
Page 99 and 100:
6 Managing Switch User Accounts Swi
Page 101 and 102:
Managing Switch User Accounts User
Page 103 and 104:
Managing Switch User Accounts Overv
Page 105 and 106:
Managing Switch User Accounts Overv
Page 107 and 108:
Managing Switch User Accounts Creat
Page 109 and 110:
Managing Switch User Accounts Confi
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Managing Switch User Accounts Setti
Page 117 and 118:
Managing Switch User Accounts Multi
Page 119 and 120:
7 Managing Switch Security Switch s
Page 121 and 122:
Managing Switch Security Switch Sec
Page 123 and 124:
Managing Switch Security Authentica
Page 125 and 126:
Managing Switch Security Quick Step
Page 127 and 128:
Managing Switch Security Setting Up
Page 129 and 130:
Managing Switch Security Configurin
Page 131 and 132:
8 Using WebView The switch can be m
Page 133 and 134:
Using WebView WebView CLI Commands
Page 135 and 136:
Using WebView WebView Overview Conf
Page 137 and 138:
9 Using SNMP The Simple Network Man
Page 139 and 140:
Using SNMP Quick Steps for Setting
Page 141 and 142:
Using SNMP Quick Steps for Setting
Page 143 and 144:
Using SNMP SNMP Overview Using SNMP
Page 145 and 146:
Using SNMP Using SNMP For Switch Se
Page 147 and 148:
Using SNMP Using SNMP For Switch Se
Page 149 and 150:
Using SNMP Working with SNMP Traps
Page 151 and 152: Using SNMP Verifying the SNMP Confi
Page 153 and 154: 10 Web Services, CLI Scripting, and
Page 155 and 156: Web Services, CLI Scripting, and Op
Page 181 and 182: 11 Configuring Network Time Protoco
Page 183 and 184: Configuring Network Time Protocol (
Page 195 and 196: 12 Managing Automatic Remote Config
Page 197 and 198: Managing Automatic Remote Configura
Page 201: Managing Automatic Remote Configura
Page 219 and 220: 13 Configuring Virtual Chassis A Vi
Page 221 and 222: Configuring Virtual Chassis Virtual
Page 223 and 224: Configuring Virtual Chassis Quick S
Page 227 and 228: Configuring Virtual Chassis Managin
Page 229 and 230: Configuring Virtual Chassis Managin
Page 235 and 236: Configuring Virtual Chassis Interac
Page 237 and 238: Configuring Virtual Chassis Configu
Page 239 and 240: Configuring Virtual Chassis Configu
Page 241 and 242: Configuring Virtual Chassis Display
Page 243 and 244: A Software License and Copyright St
Page 245 and 246: Alcatel-Lucent License Agreement Al
Page 247 and 248: B SNMP Trap Information This append
Page 249 and 250: SNMP Traps Table No. Trap Name Obje
Page 251 and 252: SNMP Traps Table No. Trap Name Obje
Page 253 and 254:
SNMP Traps Table No. Trap Name Obje
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Index Symbols !! command 4-6 A aaa
Page 295 and 296:
Index Network Time Protocol see NTP
show all

OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Create successful ePaper yourself

Delete template?

Save as template?