Manualshelf

User guide

ManualsBrandsAlcatel ManualsComputer equipmentOmniSwitch AOS Release 7
241242243244245246247248249250
DHCP Client Auto-Configuration Process Managing Automatic Remote Configuration Download
page 13-16 OmniSwitch AOS Release 7 Switch Management Guide March 2015
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:
• DHCP client on untagged VLAN 1
• DHCP client on tagged VLAN 127
• DHCP client on LLDP tagged Management VLAN
• Auto Link Aggregate Detection
The 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 “Nearest-Edge Mode Operation” on page 13-17 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.
5 If during this process the switch receives an LACP PDUs it will attempt to automatically create a link
aggregate with the peer device. The link aggregate will become part of VLAN 1 (untagged) and VLAN
127 (tagged).