OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Recommendations

Info

DHCP Client Auto-Configuration Process Managing Automatic Remote Configuration Download DHCP Client Auto-Configuration Process The automatic remote configuration download feature supports the following client configuration methods to obtain an initial dynamic IP address from the DHCP server: • Static DHCP client on untagged VLAN 1 • Dynamic DHCP client on tagged VLAN 127 • Dynamic DHCP client on LLDP tagged Management VLAN • Auto Link Aggregate Detection OmniSwitch creates a DHCP Client interface on: • the default untagged VLAN 1 and then on tagged VLAN 127 alternating between each, or • the Management VLAN being advertised in the LLDP PDUs sent by the Management Switch configured in Nearest-Edge Mode. If OmniSwitch receives LLDP PDUs with VLAN and port information from a Management switch in nearest edge mode, then the DHCP client interface is moved to user defined LLDP management VLAN on the network. See the “” on page 12-16 for additional information. The detailed process of DHCP client auto-configuration on an OmniSwitch is as follows: 1 At boot-up, the initial DHCP client starts with untagged VLAN 1.The DHCP client waits for 30 seconds for a DHCP lease. 2 If the lease is not obtained even after 30 seconds, the DHCP client is stopped on the untagged VLAN 1 and DHCP client is started on tagged VLAN 127. The DHCP client on tagged VLAN 127 waits for 30 seconds for a DHCP lease. 3 If the DHCP client does not get the lease in 30 seconds, DHCP client moves back to untagged VLAN 1 and this process continues until it gets the DHCP lease on any one of the two VLANs. 4 If during this process the switch receives an LLDP PDU advertising the management VLAN, the DHCP process will stop on VLANs 1 and 127 and begin on the management VLAN. Note. DHCP client is automatically stopped once a user logs in the switch through console port before getting the DHCP lease. Once the DHCP client gets the lease, the Remote Config process does not stop even if the user logs on to the switch through console port. page 12-16 OmniSwitch AOS Release 8 Switch Management Guide May 2014
Managing Automatic Remote Configuration Download Nearest-Edge Mode Operation Nearest-Edge Mode Operation In order for the network to propagate Nearest-Edge mode LLDP PDUs a Management Switch must be configured to send the LLDP PDUs with the Management VLAN information. Additionally, the peer switches are automatically configured to process the Nearest-Edge Mode LLDP PDU frames by the Automatic Configuration Download feature. An OmniSwitch running the Automatic Remote Configuration feature is automatically enabled to process LLDP PDUs with the unique Nearest-Edge destination MAC address. In Nearest-Edge mode the Management OmniSwitch uses a unique MAC address when sending LLDP PDUs. The network OmniSwitch also looks for these unique packets to determine a Management VLAN. It then creates a DHCP client interface on that tagged VLAN. LLDP Transmission from Management Switch • The Management Switch is configured to use the Nearest-Edge Mode MAC address and is connected to the network using an untagged interface. • LLDP is configured on the untagged port of the Management Switch so that the LLDP PDUs are sent with the Management VLAN information. • The LLDP interval must not be set higher than 30 seconds (default). • The Management Switch sends LLDP PDUs on the untagged interface with the MAC address of 01:20:DA:02:01:73. LLDP Propagation through Network These LLDP PDUs are propagated throughout the network as normal L2 multicast frames, eventually reaching the Access Switch. LLDP Reception by Access Switch The Automatic Configuration Download feature enables the processing of the Nearest-edge LLDP PDUs by default. Nearest-Edge Mode Configuration Example LLDP Nearest Edge Configuration Automatic Remote Configuration feature requires learning Management VLAN ID from a centralized management switch. This VLAN ID information is distributed through LLDP message. On the management switch, LLDP sends Port VLAN ID TLV to the special MAC address [01:20: DA: 02:01:73]. The CLI command for this functionality is as follows: -> lldp nearest-edge mode {enable | disable} This functionality also depends on the nearest bridge agent LLDPDU transmit mode. So LLDP sends a Port VLAN ID TLV when both of the below commands are executed: -> lldp nearest-bridge chassis lldpdu tx-and-rx -> lldp nearest-edge mode enable The LLDPDUs are sent on the untagged interface with the Nearest-edge MAC address and propagated throughout the network eventually reaching the Access Switch. OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 12-17
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 157 and 158:
Web Services, CLI Scripting, and Op
Page 159 and 160: 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 209: 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 261 and 262:
SNMP Traps Table No. Trap Name Obje
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?