Configuring Access Guardian Bring Your Own Devices (BYOD) Overview
OmniSwitch AOS Release 8 Network Configuration Guide December 2017 page 28-136
Backward Compatibility
mDNS and SSDP with Aruba mode is backward compatible. The configurations made using the older CLI
commands will continue to work provided the Loopback0 IP address is configured as the source endpoint
address. Responder IP will be set to destination IP of the legacy tunnel IP interface configuration. Any
further changes to the existing configuration can be made only after saving the configuration in the new
format using the write memory command.
Configuration Guidelines
• The mDNS or SSDP packet handling across Layer 3 supports different modes of operation, such as
Tunnel (relay to Aruba), Gateway, Tunnel Standard (relay to OmniSwitch responder), and Responder
mode. At any given point of time, the switch can operate in only one mode.
• The operational status of mDNS and SSDP on the edge switch will be down if the responder IP address
is not configured. The responder IP address configured must be reachable.
• The Loopback0 IP address must be configured on the edge switch and reachable from the controller.
• When the OmniSwitch is running as a responder (Responder mode), the query packets are flooded
through only those VLANs that are configured in the access VLAN list on the edge switch.
• When mDNS relay or SSDP relay status is disabled, the mDNS or SSDP packets are dropped.
• The responder triggers a service request query in the event of takeover, VC takeover, reload, and
responder initiated query requests. Configuring the known service list is recommended. The responder
queries only those services that are configured in the service list.
Note. Refer to “Quick Steps for Zero Configuration mDNS and SSDP” on page 28-137 for procedures on
how to configure each mode.
To Next Page
Loading...
Need help?
General
