Managing Automatic Remote Configuration Download DHCP Client Preference to OXO DHCP Server
OmniSwitch 6250/6450 Switch Management Guide June 2013 page 8-19
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.
The detailed process of DHCP client auto-configuration on 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 a LLDP that is advertising the management VLAN ID is received on any of the switch ports, the
initial DHCP client on untagged VLAN and tagged VLAN 127 is stopped and a new DHCP client is
started on this tagged management VLAN.
5
Now, the DHCP Client created on tagged management VLAN waits infinitely to get a lease.
Note.
If the initial DHCP clients (untagged or VLAN 127) obtains an IP lease, the LLDP detection mechanism is
disabled to prevent the switch from starting a new DHCP client.
DHCP client is automatically stopped once a user logs in the switch through console port before getting
the DHCP lease. This condition applies for any type of DHCP client (untagged, tagged 127 or tagged with
LLDP associated management VLAN).
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.
DHCP Client Preference to OXO DHCP Server
When the RCL is running and the DHCP client is created, the following steps are followed in order to
provide preference to the desired OXO DHCP server:
•
If DHCPACK from Non-OXO DHCP server is received and DHCP client is created on default
VLAN 1, DHCP client stores this response if it is the first response otherwise response gets declined.
This stored response is applied only if the desired OXO DHCP response is not found within 30 secs
window. The desired OXO DHCP response is the response having the VSI: "alcatel.a4400.0".
•
If DHCPACK from desired OXO DHCP server is received it gets applied immediately.
•
If DHCPACK from undesired OXO DHCP server is received and DHCP client is created on default
VLAN 1, DHCP client stores this response if it is the first response otherwise response gets declined.
This stored response is applied only if the desired OXO DHCP response is not found within 30 secs
window.
•
If no DHCPACK is received in 30 secs window, RCL will continue its process. The DHCP client on
VLAN 1 is deleted and that on VLAN 127 gets created, this continues until the desired OXO DHCP
response is received.
To Next Page
Loading...
