Interaction With Other Features
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
QoS
Interaction with QoS is required for the following processes, to support Auto Remote Configuration:
• Policy control lists (PCLs) are created to trap LLDP packets.
• PCLs are deleted after the required processing for Nearest-Edge Mode operation.
802.1Q
For 802.1Q tagging is applied interaction is required for Nearest Edge Mode operation
LLDP
In Nearest-Edge Mode operation LLDP packets carry and provide the advertised VLAN ID to the Access
OmniSwitches running Auto Remote Configuration download.
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 combo/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 8-8
Managing Automatic Remote Configuration Download
"DHCP Client Auto-Configuration Process" on page 8-18
OmniSwitch 6250/6450 Switch Management Guide
June 2013