User guide

Managing Automatic Remote Configuration Download Interaction With Other Features
OmniSwitch AOS Release 7 Switch Management Guide March 2015 page 13-9
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 13-16
802.1Q
802.1Q tagging is applied on VLAN 127 for all ports or the Management VLAN.
LLDP
In Nearest-Edge mode operation LLDP packets carry and provide the advertised VLAN ID to the
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.
Automatic Virtual Chassis and Automatic Fabric
• Automatic Remote Configuration will run after a Master is chosen and the VC is established.
• Automatic Remote Configuration will run before any automatic fabric protocols (LACP, SPB, MVRP,
Loopback, IP).