Cisco Wireless LAN Controller Configuration Guide, Release 7.5
Configuring Multicast
Downloads: This chapterpdf (PDF - 1.35MB) The complete bookPDF (PDF - 17.88MB) | The complete bookePub (ePub - 4.41MB) | Feedback

Configuring Multicast

Configuring Multicast

Configuring Multicast Mode

Information About Multicast Mode

If your network supports packet multicasting, you can configure the multicast method that the controller uses. The controller performs multicasting in two modes:

  • Unicast mode—In this mode, the controller unicasts every multicast packet to every access point associated to the controller. This mode is inefficient but might be required on networks that do not support multicasting.
  • Multicast mode—In this mode, the controller sends multicast packets to a CAPWAP multicast group. This method reduces overhead on the controller processor and shifts the work of packet replication to your network, which is much more efficient than the unicast method.

When you enable multicast mode and the controller receives a multicast packet from the wired LAN, the controller encapsulates the packet using CAPWAP and forwards the packet to the CAPWAP multicast group address. The controller always uses the management interface for sending multicast packets. Access points in the multicast group receive the packet and forward it to all the BSSIDs mapped to the interface on which clients receive multicast traffic. From the access point perspective, the multicast appears to be a broadcast to all SSIDs.

The controller supports Multicast Listener Discovery (MLD) v1 snooping for IPv6 multicast. This feature keeps track of and delivers IPv6 multicast flows to the clients that request them. To support IPv6 multicast, you must enable Global Multicast Mode.


Note


When you disable the Global Multicast Mode, the controller still forwards the IPv6 ICMP multicast messages, such as router announcements and DHCPv6 solicits, as these are required for IPv6 to work. As a result, enabling the Global Multicast Mode on the controller does not impact the ICMPv6 and the DHCPv6 messages. These messages will always be forwarded irrespective of whether or not the Global Multicast Mode is enabled.


In controller software 4.2 or later releases, Internet Group Management Protocol (IGMP) snooping is introduced to better direct multicast packets. When this feature is enabled, the controller gathers IGMP reports from the clients, processes them, creates unique multicast group IDs (MGIDs) from the IGMP reports after selecting the Layer 3 multicast address and the VLAN number, and sends the IGMP reports to the infrastructure switch. The controller sends these reports with the source address as the interface address on which it received the reports from the clients. The controller then updates the access point MGID table on the access point with the client MAC address. When the controller receives multicast traffic for a particular multicast group, it forwards it to all the access points, but only those access points that have active clients listening or subscribed to that multicast group send multicast traffic on that particular WLAN. IP packets are forwarded with an MGID that is unique for an ingress VLAN and the destination multicast group. Layer 2 multicast packets are forwarded with an MGID that is unique for the ingress interface.

When IGMP snooping is disabled, the following is true:

  • The controller always uses Layer 2 MGID when it sends multicast data to the access point. Every interface created is assigned one Layer 2 MGID. For example, the management interface has an MGID of 0, and the first dynamic interface created is assigned an MGID of 8, which increments as each dynamic interface is created.
  • The IGMP packets from clients are forwarded to the router. As a result, the router IGMP table is updated with the IP address of the clients as the last reporter.

When IGMP snooping is enabled, the following is true:

  • The controller always uses Layer 3 MGID for all Layer 3 multicast traffic sent to the access point. For all Layer 2 multicast traffic, it continues to use Layer 2 MGID.
  • IGMP report packets from wireless clients are consumed or absorbed by the controller, which generates a query for the clients. After the router sends the IGMP query, the controller sends the IGMP reports with its interface IP address as the listener IP address for the multicast group. As a result, the router IGMP table is updated with the controller IP address as the multicast listener.
  • When the client that is listening to the multicast groups roams from one controller to another, the first controller transmits all the multicast group information for the listening client to the second controller. As a result, the second controller can immediately create the multicast group information for the client. The second controller sends the IGMP reports to the network for all multicast groups to which the client was listening. This process aids in the seamless transfer of multicast data to the client.
  • If the listening client roams to a controller in a different subnet, the multicast packets are tunneled to the anchor controller of the client to avoid the reverse path filtering (RPF) check. The anchor then forwards the multicast packets to the infrastructure switch.

    Note


    The MGIDs are controller specific. The same multicast group packets coming from the same VLAN in two different controllers may be mapped to two different MGIDs.



    Note


    If Layer 2 multicast is enabled, a single MGID is assigned to all the multicast addresses coming from an interface.



    Note


    The number of multicast addresses supported per VLAN for a Cisco WLC is 100.

Restrictions for Configuring Multicast Mode

  • The Cisco Unified Wireless Network solution uses some IP address ranges for specific purposes, and you should keep these ranges in mind when configuring a multicast group:
    • 224.0.0.0 through 224.0.0.255—Reserved link local addresses
    • 224.0.1.0 through 238.255.255.255—Globally scoped addresses
    • 239.0.0.0 through 239.255.x.y /16—Limited scope addresses
  • When you enable multicast mode on the controller, you also must configure a CAPWAP multicast group address. Access points subscribe to the CAPWAP multicast group using IGMP.
  • Cisco 1100, 1130, 1200, 1230, and 1240 access points use IGMP versions 1, 2, and 3.
  • Access points in monitor mode, sniffer mode, or rogue detector mode do not join the CAPWAP multicast group address.
  • The CAPWAP multicast group configured on the controllers should be different for different controllers.
  • Access points running recent Cisco IOS versions transmit multicast frames at the highest configured basic rate and management frames at the lowest basic mandatory rates, can cause reliability problems. Access points running LWAPP or autonomous Cisco IOS should transmit multicast and management frames at the lowest configured basic rate. Such behavior is necessary to provide good coverage at the cell's edge, especially for unacknowledged multicast transmissions where multicast wireless transmissions might fail to be received. Because multicast frames are not retransmitted at the MAC layer, clients at the edge of the cell might fail to receive them successfully. If reliable reception is a goal, multicast frames should be transmitted at a low data rate. If support for high data rate multicast frames is required, it might be useful to shrink the cell size and disable all lower data rates.
    Depending on your requirements, you can take the following actions:
    • If you need to transmit multicast data with the greatest reliability and if there is no need for great multicast bandwidth, then configure a single basic rate, that is low enough to reach the edges of the wireless cells.
    • If you need to transmit multicast data at a certain data rate in order to achieve a certain throughput, you can configure that rate as the highest basic rate. You can also set a lower basic rate for coverage of nonmulticast clients.
  • Multicast mode does not operate across intersubnet mobility events such as guest tunneling. It does, however, operate with interface overrides using RADIUS (but only when IGMP snooping is enabled) and with site-specific VLANs (access point group VLANs).
  • For LWAPP, the controller drops multicast packets sent to UDP control port 12223. For CAPWAP, the controller drops multicast packets sent to UDP control and data ports 5246 and 5247, respectively. Therefore, you may want to consider not using these port numbers with the multicast applications on your network.
  • We recommend that any multicast applications on your network not use the multicast address configured as the CAPWAP multicast group address on the controller.
  • For multicast to work on 2500 series controller, you have to configure the multicast IP address.
  • Multicast mode is not supported on Cisco Flex 7500 Series Controllers.

Enabling Multicast Mode (GUI)


    Step 1   Choose Controller > Multicast to open the Multicast page.
    Step 2   Select the Enable Global Multicast Mode check box to configure sending multicast packets. The default value is disabled.
    Note   

    FlexConnect supports unicast mode only.

    Step 3   If you want to enable IGMP snooping, select the Enable IGMP Snooping check box. If you want to disable IGMP snooping, leave the check box unselected. The default value is disabled.
    Step 4   To set the IGMP timeout, enter a value between 30 and 7200 seconds in the IGMP Timeout text box. The controller sends three queries in one timeout value at an interval of timeout/ 3 to see if any clients exist for a particular multicast group. If the controller does not receive a response through an IGMP report from the client, the controller times out the client entry from the MGID table. When no clients are left for a particular multicast group, the controller waits for the IGMP timeout value to expire and then deletes the MGID entry from the controller. The controller always generates a general IGMP query (that is, to destination address 224.0.0.1) and sends it on all WLANs with an MGID value of 1.
    Step 5   Enter the IGMP Query Interval (seconds).
    Step 6   Select the Enable MLD Snooping check box to support IPv6 forwarding decisions.
    Note   

    To enable MLD Snooping, you must enable Global Multicast Mode of the controller.

    Step 7   In the MLD Timeout text box, enter a value between 30 and 7200 seconds to set the MLD timeout.
    Step 8   Enter the MLD Query Interval (seconds). The valid range is between 15 and 2400 seconds.
    Step 9   Click Apply to commit your changes.
    Step 10   Click Save Configuration to save your changes.

    Enabling Multicast Mode (CLI)


      Step 1   Enable or disable multicasting on the controller by entering this command:

      config network multicast global {enable | disable}

      The default value is disabled.

      Note   

      The config network broadcast {enable | disable} command allows you to enable or disable broadcasting without enabling or disabling multicasting as well. This command uses the multicast mode currently on the controller to operate.

      Step 2   Perform either of the following:
      1. Configure the controller to use the unicast method to send multicast packets by entering this command:

        config network multicast mode unicast

      2. Configure the controller to use the multicast method to send multicast packets to a CAPWAP multicast group by entering this command:

        config network multicast mode multicast multicast_group_ip_address

      Step 3   Enable or disable IGMP snooping by entering this command:

      config network multicast igmp snooping {enable | disable}

      The default value is disabled.

      Step 4   Set the IGMP timeout value by entering this command:

      config network multicast igmp timeout timeout

      You can enter a timeout value between 30 and 7200 seconds. The controller sends three queries in one timeout value at an interval of timeout/3 to see if any clients exist for a particular multicast group. If the controller does not receive a response through an IGMP report from the client, the controller times out the client entry from the MGID table. When no clients are left for a particular multicast group, the controller waits for the IGMP timeout value to expire and then deletes the MGID entry from the controller. The controller always generates a general IGMP query (that is, to destination address 224.0.0.1) and sends it on all WLANs with an MGID value of 1.

      Step 5   Enable or disable MLD snooping by entering this command:

      config network multicast mld snooping {enable | disable}

      The default value is disabled.

      Note   

      To enable MLD snooping, you must enable global multicast mode of the controller.

      Step 6   Set the MLD timeout value by entering this command:

      config network multicast mld timeout timeout

      Enter the MLD Query Interval (seconds). The valid range is between 15 and 2400 seconds.

      Step 7   Save your changes by entering this command: save config

      Viewing Multicast Groups (GUI)


        Step 1   Choose Monitor > Multicast. The Multicast Groups page appears.

        This page shows all the multicast groups and their corresponding MGIDs.

        Step 2   Click the link for a specific MGID (such as MGID 550) to see a list of all the clients joined to the multicast group in that particular MGID.

        Viewing Multicast Groups (CLI)

        Before You Begin
        • See all the multicast groups and their corresponding MGIDs by entering this command: show network multicast mgid summary Information similar to the following appears:
          
          Layer2 MGID Mapping:
          -------------------
          InterfaceName                    vlanId   MGID
          -------------------------------- ------   ----
          management                       0        0
          test                             0        9
          wired                            20       8
          
          Layer3 MGID Mapping:
          -------------------
          Number of Layer3 MGIDs........................... 1
          
           Group address    Vlan  MGID
           ---------------  ----  ----
           239.255.255.250  0     550

          
        • See all the clients joined to the multicast group in a specific MGID by entering this command: show network multicast mgid detail mgid_value where the mgid_value parameter is a number between 550 and 4095. Information similar to the following appears:
          
          Mgid........................................ 550
          Multicast Group Address..................... 239.255.255.250
          Vlan........................................ 0
          Rx Packet Count............................. 807399588
          No of clients............................... 1
          Client List.................................
                  Client MAC             Expire Time (mm:ss)
                  00:13:02:23:82:ad      0:20
          

        Viewing an Access Point’s Multicast Client Table (CLI)

        To help troubleshoot roaming events, you can view an access point’s multicast client table from the controller by performing a remote debug of the access point.


          Step 1   Initiate a remote debug of the access point by entering this command:

          debug ap enable Cisco_AP

          Step 2   See all of the MGIDs on the access point and the number of clients per WLAN by entering this command:

          debug ap command “show capwap mcast mgid all” Cisco_AP

          Step 3   See all of the clients per MGID on the access point and the number of clients per WLAN by entering this command:

          debug ap command “show capwap mcast mgid id mgid_value Cisco_AP


          Configuring Multicast Domain Name System

          Information About Multicast Domain Name System

          Multicast Domain Name System (mDNS) service discovery provides a way to announce and discover the services on the local network. The mDNS service discovery enables wireless clients to access Apple services such as Apple Printer and Apple TV advertised in a different Layer 3 network. mDNS performs DNS queries over IP multicast. mDNS supports zero-configuration IP networking. As a standard, mDNS uses multicast IP address 224.0.0.251 as the destination address and 5353 as the UDP destination port.

          Location Specific Services

          The processing of mDNS service advertisements and mDNS query packets support Location-Specific Services (LSS). All the valid mDNS service advertisements that are received by the controller are tagged with the MAC address of the AP that is associated with the service advertisement from the service provider while inserting the new entry into the service provider database. The response formulation to the client query filters the wireless entries in the SP-DB using the MAC address of the AP associated with the querying client. The wireless service provider database entries are filtered based on the AP-NEIGHBOR-LIST if LSS is enabled for the service. If LSS is disabled for any service, the wireless service provider database entries are not filtered when they respond to any query from a wireless client for the service.

          LSS applies only to wireless service provider database entries. There is no location awareness for wired service provider devices.

          The status of LSS cannot be enabled for services with ORIGIN set to wired and vice-versa.

          mDNS AP

          The mDNS AP feature allows the controller to have visibility of wired service providers that are on VLANs that are not visible to the controller. You can configure any AP as an mDNS AP and enable the AP to forward mDNS packets to the controller. VLAN visibility on the controller is achieved by APs that forward the mDNS advertisements to the controller. The mDNS packets between the AP and the controller are forwarded in Control and Provisioning of Wireless Access Points (CAPWAP) data tunnel that is similar to the mDNS packets from a wireless client. Only CAPWAP v4 tunnels are supported. APs can be in either the access port or the trunk port to learn the mDNS packets from the wired side and forward them to the controller.

          You can use the configurable knob that is provided on the controller to start or stop mDNS packet forwarding from a specific AP. You can also use this configuration to specify the VLANs from which the AP should snoop the mDNS advertisements from the wired side. The maximum number of VLANs that an AP can snoop is 10.

          If the AP is in the access port, you should not configure any VLANs on the AP to snoop. The AP sends untagged packets when a query is to be sent. When an mDNS advertisement is received by the mDNS AP, the VLAN information is not passed on to the controller. The service provider's VLAN that is learned through the mDNS AP's access VLAN is maintained as 0 in the controller.

          By default, the mDNS AP snoops in native VLAN. When an mDNS AP is enabled, native VLAN snooping is enabled by default and the VLAN information is passed as 0 for advertisements received on the native VLAN.

          The mDNS AP feature is supported only on local mode and monitor mode APs.

          The mDNS AP configuration is retained on those mDNS APs even if global mDNs snooping is disabled.


          Note


          There is no check to ensure that no two mDNS APs are duplicating the same traffic for the same service. But, for the same VLAN, there is such a check.


          If an mDNS AP is reset or associated with the same controller or another controller, one of the following occurs:
          • If the global snooping is disabled on the controller, a payload is sent to the AP to disable mDNS snooping.
          • If the global snooping is enabled on the controller, the configuration of the AP before the reset or the association procedure is retained.
          The process flow for the mDNS AP feature is as follows:
          • Uplink (Wired infrastructure to AP to Controller):
            1. Receives the 802.3 mDNS packet on configured VLANs.
            2. Forwards the received mDNS packet over CAPWAP.
            3. Populates multicast group ID (MGID) based on the received VLAN.
          • Downlink (Controller to AP to Wired Infrastructure):
            1. Receives an mDNS query over CAPWAP from the controller.
            2. Forwards the query as 802.3 packet to wired infrastructure.
            3. The VLAN is identified from dedicated MGIDs.

          Per-Service SP Count Limit

          The following list shows the global service provider limit per controller model:
          • Cisco 8500 Series Wireless LAN Controller—16000
          • Cisco Flex 7500 Series Wireless LAN Controller—16000
          • Cisco 5500 Series Wireless LAN Controller—6400
          • Cisco 2500 Series Wireless LAN Controller—6400

          If the total number of service providers for all services is within the specified limit, any service is free to learn or discover as many other services. There is no per service reservation or restriction, which allows flexibility to accommodate more service providers for any service with respect to other services.

          Priority MAC Support

          You can configure up to 50 MAC addresses per service; these MAC addresses are the service provider MAC addresses that require priority. This guarantees that any service advertisements originating from these MAC addresses for the configured services are learned even if the service provider database is full by deleting the last nonpriority service provider from the service that has the highest number of service providers. When you configure the priority MAC address for a service, there is an optional parameter called ap-group, which is applicable only to wired service providers to associate a sense of location to the wired service provider devices. When a client mDNS query originates from this ap-group, the wired entries with priority MAC and ap-group are looked up and the wired entries are listed first in the aggregated response.

          Origin-Based Service Discovery

          You can configure a service to filter inbound traffic that is based on its origin, that is either wired or wireless. All the services that are learned from an mDNS AP are treated as wired. When the learn origin is wired, the LSS cannot be enabled for the service because LSS applies only to wireless services.

          A service that has its origin set to wireless cannot be changed to wired if the LSS status is enabled for the service because LSS is applicable only to wireless service provider database. If you change the origin between wired and wireless, the service provider database entries with the prior origin type is cleared.

          Restrictions for Configuring Multicast DNS

          • mDNS over IPv6 is not supported.
          • mDNS is not supported on access points in FlexConnect mode in a locally switched WLAN and mesh access points.
          • mDNS is not supported on remote LANs.
          • mDNS is not supported on Cisco AP1240 and Cisco AP1130.
          • Third-party mDNS servers or applications are not supported on the Cisco WLC using the mDNS feature. Devices that are advertised by the third-party servers or applications are not populated on the mDNS service or device table correctly on the Cisco WLC.
          • Video is not supported on Apple iOS 6 with WMM in enabled state.
          • mDNS APs cannot duplicate the same traffic for the same service or VLAN.
          • LSS filtering is restricted to only wireless services.
          • The LSS, mDNS AP, Priority MAC address, and origin-based discovery features cannot be configured using the controller GUI.

          Configuring Multicast DNS (GUI)


            Step 1   Configure the global mDNS parameters and the Master Services Database by following these steps:
            1. Choose Controller > mDNS > General.
            2. Select or unselect the mDNS Global Snooping check box to enable or disable snooping of mDNS packets, respectively.
            3. Enter the mDNS query interval in minutes. The query interval is the frequency at which the controller queries for a service.
            4. Choose a service from the Select Service drop-down list.
              Note   

              To add a new mDNS-supported service to the list, choose Other. Specify the service name and the service string. The controller snoops and learns about the mDNS service advertisements only if the service is available in the Master Services Database. The controller can snoop and learn a maximum of 64 services.

            5. Select or unselect the Query Status check box to enable or disable an mDNS query for a service, respectively.
            6. Click Add.
            7. Click Apply.
            8. To view the details of an mDNS service, hover your cursor over the blue drop-down arrow of a service, and choose Details.
            Step 2   Configure an mDNS profile by following these steps:
            1. Choose Controller > mDNS > Profiles.

              The controller has a default mDNS profile, which is default-mdns-profile. It is not possible to delete the default profile.

            2. To create a new profile, click New, enter a profile name, and click Apply.
            3. To edit a profile, click a profile name on the mDNS Profiles page; from the Service Name drop-down list, choose a service to be associated with the profile, and click Apply.

              You can add multiple services to a profile.

            Step 3   Click Save Configuration.

            What to Do Next

            After creating a new profile, you must map the profile to an interface group, an interface, or a WLAN. Clients receive service advertisements only for the services associated with the profile. The highest priority is given to the profiles associated with interface groups, followed by the interface profiles, and then the WLAN profiles. Each client is mapped to a profile based on the order of priority.

            • Map an mDNS profile to an interface group by following these steps:
              1. Choose Controller > Interface Groups.
              2. Click the corresponding interface group name. The Interface Groups > Edit page is displayed.
              3. From the mDNS Profile drop-down list, choose a profile.
            • Map an mDNS profile to an interface by following these steps:
              1. Choose Controller > Interfaces.
              2. Click the corresponding interface name. The Interfaces > Edit page is displayed.
              3. From the mDNS Profile drop-down list, choose a profile.
            • Map an mDNS profile to a WLAN by following these steps:
              1. Choose WLANs. click the WLAN ID to open the WLANs > Edit page.
              2. Click the corresponding WLAN ID. The WLANs > Edit page is displayed.
              3. Click the Advanced tab.
              4. Select the mDNS Snooping check box.
              5. From the mDNS Profile drop-down list, choose a profile.

            Configuring Multicast DNS (CLI)

            • Configure mDNS snooping by entering this command: config mdns snooping {enable | disable}
            • Configure mDNS services by entering this command: config mdns service {{create service-name service-string origin {wireless | wired | all} lss {enable | disable} [query] [enable | disable]} | delete service-name}
            • Configure a query for an mDNS service by entering this command: config mdns service query {enable | disable} service-name
            • Configure a query interval for mDNS services by entering this command: config mdns query interval value-in-minutes
            • Configure an mDNS profile by entering this command:
              config mdns profile {create | delete} profile-name

              Note


              If you try to delete an mDNS profile that is already associated with an interface group, an interface, or a WLAN, an error message is displayed.


            • Configure mDNS services to a profile by entering this command: config mdns profile service {add | delete} profile-name service-name
            • Map an mDNS profile to an interface group by entering this command:
              config interface group mdns-profile {interface-group-name | all} {mdns-profile-name | none}

              Note


              If the mDNS profile name is none, no profiles are attached to the interface group. Any existing profile that is attached is removed.


            • View information about an mDNS profile that is associated with an interface group by entering this command: show interface group detailed interface-group-name
            • Map an mDNS profile to an interface by entering this command: config interface mdns-profile {management | {interface-name | all}} {mdns-profile-name | none}
            • View information about the mDNS profile that is associated with an interface by entering this command: show interface detailed interface-name
            • Configure mDNS for a WLAN by entering this command: config wlan mdns {enable | disable} {wlan-id | all}
            • Map an mDNS profile to a WLAN by entering this command: config wlan mdns profile {wlan-id | all} {mdns-profile-name | none}
            • View information about an mDNS profile that is associated with a WLAN by entering this command: show wlan wlan-id
            • View information about all mDNS profiles or a particular mDNS profile by entering this command: show mdns profile {summary | detailed mdns-profile-name}
            • View information about all mDNS services or a particular mDNS service by entering this command: show mdns service {summary | detailed mdns-service-name}
            • View information about the mDNS domain names that are learned by entering this command: show mdns domain-name-ip summary
            • View the mDNS profile for a client by entering this command: show client detail client-mac-address
            • View the mDNS details for a network by entering this command: show network summary
            • Clear the mDNS service database by entering this command: clear mdns service-database {all | service-name}
            • View events related to mDNS by entering this command: debug mdns message {enable | disable}
            • View mDNS details of the events by entering this command: debug mdns detail {enable | disable}
            • View errors related to mDNS processing by entering this command: debug mdns error {enable | disable}
            • Configure debugging of all mDNS details by entering this command: debug mdns all {enable | disable}
            • Location Specific Service-related commands:

              • Enable or disable location specific service on a specific mDNS service or all mDNS services by entering this command:

                config mdns service lss {enable | disable} {service-name | all}


                Note


                By default, LSS is in disabled state.

                Impact on High Availability: Requires to be synchronized with the standby controller.


              • View the status of LSS by entering these commands:

                Summary—show mdns service summary

                Detailed—show mdns service detailed service-name

              • Configure troubleshooting HA-related mDNS by entering this command:

                debug mdns ha {enable | disable}

            • Origin-based service discovery-related commands:

              • Configure learning of services from wired, wireless, or both by entering this command:

                config mdns service origin {Wireless | Wired | All} {service-name | all}

                It is not possible to configure wired services if LSS is enabled and vice versa. It is not possible to enable LSS for wired-only service learn origin.

                Impact on High Availability: Requires to be synchronized with the standby controller.

              • View the status of origin-based service discovery by entering this command:

                Summary—show mdns service summary

                Detailed—show mdns service detailed service-name

              • View all the service advertisements that are present in the controller, but not discovered because of restrictions on learning those services, by entering this command:

                show mdns service not-learnt

                Service advertisements across all VLANs and origin types that are not learned are displayed.

            • Priority MAC address-related commands:

              • Configure per-service MAC addresses of service-providing devices to ensure that they are snooped and discovered even if the service provider database is full, by entering this command:

                config mdns service priority-mac {add | delete} priority-mac-addr service-name ap-group ap-group-name

                The optional AP group is applicable only to wired service provider devices to give them a sense of location; these service providers are placed higher in the order than the other wired devices.

              • View the status of Priority MAC address by entering this command:

                Detailed—show mdns service detailed service-name

            • mDNS AP-related commands:

              • Enable or disable mDNS forwarding on an AP that is associated with the controller by entering this command:

                config mdns ap {enable | disable} {ap-name | all} vlan vlan-id

                There is no default mDNS AP. VLAN ID is an optional node.

                Impact on High Availability: The static configuration is synchronized to the standby controller.

              • Configure the VLAN on which the AP should snoop, and forward the mDNS packets by entering this command:

                config mdns ap vlan {add | delete} vlan-id ap-name

              • View all the APs for which mDNS forwarding is enabled by entering this command:

                show mdns ap summary