Configure Media Stream Parameters

Configure the global multicast parameters by the following steps:

1. Switch to Expert View by clicking the bidirectional arrow icon on the top right of the home screen in the Web-UI of the Primary AP.

   A message is displayed to confirm if you want to switch to the expert view.

2. Click Ok.

3. Navigate to Services > Media Stream.

4. Enable Global Multicast to support multicast traffic on Primary AP. The default value is Disabled.

   Important

   Global multicast cannot be enabled without configuring IPv4 multicast address in WLAN page.

5. Enable Multicast Direct to enhance the video streaming for wireless clients. The default value is Disabled.

   Note	The wireless clients must re-join the multicast stream after enabling the multicast direct feature on the Primary AP.

6. Select Session Announcement State toggle button to enable the session announcement mechanism. If the session announcement state is enabled, clients are informed each time a Primary AP is not able to serve the multicast direct data to the client. The following parameters need to be filled only if Session Announcement State is enabled.

   1. Session Announcement URL— Enter the URL where the client can find more information when an error occurs during the multicast media stream transmission.

   2. Session Announcement E-mail— Enter the e-mail address of the person who can be contacted.

   3. Session Announcement Phone— Enter the phone number of the person who can be contacted.

   4. Session Announcement Note— Enter a reason as to why a particular client cannot be served with a multicast media.

7. Click Apply.

Configuring a New Media Stream

To add a new Media stream switch to Expert View and navigate to Services > Media Stream.

1. Click Add New Stream to configure a new media stream.

2. Enter the media stream name in the Stream Name text box. The stream name can be up to 64 characters.

3. Enter the starting IPv4 address of the multicast media stream in the Multicast Start IP Address text box.

4. Enter the ending IPv4 address of the multicast media stream in the Multicast End IP Address text box.

5. Enter the maximum expected bandwidth that you want to assign to the media stream into the Maximum Expected Bandwidth (Kbps) text box. The range is 1 to 35000 kbps.

   Note	We recommend that you use a template to add a media stream to the Primary AP.

6. From the Select from Predefined Templates drop-down list under Resource Reservation Control (RRC) Parameters, choose one of the following options to specify the details about the resource reservation control:

   • Very Coarse (below 300 kbps)

   • Coarse (below 500 kbps)

   • Ordinary (below 750 kbps)

   • Low (below 1 Mbps)

   • Medium (below 3 Mbps)

   • High (below 5 Mbps)

   Note	When you select a predefined template from the drop-down list, the following text boxes under the Resource Reservation Control (RRC) Parameters list their default values that are assigned with the template.

7. Specify the average packet size in the Average Packet Size field. The value can be in the range of 100 to 1500 bytes. The default value is 1200.

8. Enable the RRC (Resource Reservation Control Check) Periodic update in the RRC Periodic update field. By default, this option is enabled.

   RRC periodically updates the admission decision on the admitted stream according to the correct channel load. As a result, it may deny certain low priority admitted stream requests.

9. Specify the priority bit set in the media stream in the RRC Priority field. The priority can be any number between 1 and 8.

   The larger the value means the priority is higher. For example, a priority of 1 is the lowest value and a value of 8 is the highest value. The default priority is 4. The low priority stream may be denied in the RRC periodic update.

10. Specify the action to perform in case of a violation after a re-RRC in the Traffic Profile Violation field. Choose an action from the drop-down list. The possible values are as follows:

    • Best Effort— Specifies that a stream is set to Best Effort class on periodic revaluation. This is the default value.

    • Drop— Specifies that a stream is dropped on periodic revaluation.

11. Click Apply.

    The newly created Media stream is displayed in the table along with details of Stream Name, Start/End IP Address, and Operation Status.

Viewing Media Stream Clients

Media stream clients will be displayed under this section with the following details:

• Client MAC—Displays the MAC address of the client.

• Stream Name—Shows the Media stream name. If the Multicast Direct toggle disabled, the Stream Name will be null for clients that are connected to the WLAN.

• Multicast IP—Displays the Multicast Group Address configured in the WLAN page.

• AP Name—Displays the AP Name connected to the client.

• VLAN—Displays the Client VLAN.

• Type—Displays Multicast Only or Multicast Direct based on which toggle was configured in the WLAN.

Multicast Domain Name System (mDNS)

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.

Bonjour Advertisements for CBW device discovery

The Cisco Business Wireless Access Point sends Bonjour Advertisements to the local network to support CBW device discovery in the Cisco Business Dashboard probe. Using these advertisements, CBD probe obtains details of individual AP and the Primary AP.

Note	During the initial setup phase, if there is more than one Primary Capable AP in the network, only one AP will get DHCP IP, and sends VRRP and Bonjour Advertisements. The rest of the APs will wait for the AP to be configured and then join the Primary AP.

Location Specific Services

The processing of mDNS service advertisements and mDNS query packets support Location Specific Services (LSS). All the valid mDNS service advertisements received by the Primary AP 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, such as Apple TV database.

The response to the client query filters the wireless entries in the SP-DB using the MAC address of the AP associated with the querying client. 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 entries. There is no location awareness for wired service provider devices. The status of LSS cannot be enabled for services with the ORIGIN set to wired.

mDNS Policy

This section explains how you can define a policy to access a specific service provider. The access policy explains the client attributes, the constructs, and the rule components that make up the policy, and how rules and policies are evaluated. This helps in deciding whether the given service provider should be included in the mDNS response for the client (that made the mDNS query).

When LSS is enabled, it provides the information only about nearby service providers. mDNS Policy enables you to define a policy that is even more granular.

mDNS policies can be framed based on:

• User

• Role

• AP Name

• AP Location

• AP Group

mDNS Policy Limitations

The limitations of the mDNS policy are as follows:

• LSS cannot be applied in conjunction with the mDNS policy.

• If the keyword Any is used as a role parameter value, then that check is bypassed.

• mDNS Policy will be active only when mDNS Snooping is enabled.

• The maximum number of policies that can be configured per MAC address is five.

Client Attributes in an mDNS Policy

Any client initiating an mDNS query is associated with a set of attributes that describe the context of the client. The list of attributes can be based on Role, User-id, associated AP Name, associated AP Location, and associated AP Group.

mDNS AP

The mDNS AP feature allows the Primary AP to have visibility of the wired service providers. This is in-built in the Primary AP.

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 non-priority 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 wired or wireless origin. All the services that are learned from an mDNS AP are treated as wired. When the 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 devices. If you change the origin between wired and wireless, the service provider database entries with the prior origin type are cleared.

Cisco Umbrella Support for the Primary AP

• Up to 10 different Cisco Umbrella profiles are supported, each with a unique device ID.

• In the context of mapping Cisco Umbrella profiles or device IDs to wireless entities, only WLAN level mapping is supported.

• In the context of provisioning device IDs to APs, AP snoops the DNS packets and applies EDNS tags.

• Forced or Ignore Open modes are supported.

Limitations

This feature does not work with the following:

• Local-auth

• IPv6 addresses

Other limitations include:

• If an application or host uses an IP address directly, instead of using DNS to query domain names.

• If a client is connected to a web proxy and does not send a DNS query to resolve the server address.

• The application of wireless Cisco Umbrella profiles on wireless entities, like WLAN, through configuration, is dependent on the success of the registration of the device.

• The Cisco Umbrella Cloud provides two IPv4 addresses. The AP uses the first server address that is configured. It does not load balance across servers.