Controller Based WLANs

Is the Firewall shape multicast feature supports in which forward mode (Tunnel, Split Tunnel or Bridge)

Environment         Standalone controller which handles multicast traffic

 

 

 

Once this feature is enabled, the controller shapes all the incoming multicast data traffic. This is ingress functionality and it won't care how and in which mode the traffic is transmitted to end client.

By enabling this feature the controller buffers the data per second shape and sent in next second.  In general buffer exhaustion won't happen. 100 streams each 5Meg is tested internally.


To Enable this feature:

(config) #firewall shape-mcast

 Automatically shape bursty multicast traffic

To Disable this feature:

(config) #no firewall shape-mcast
 
 
Once this feature is enabled, the controller shapes all the incoming multicast data traffic. This is ingress functionality and it won't care how and in which mode the traffic is transmitted to end client.

By enabling this feature the controller buffers the data per second shape and sent in next second. In general buffer exhaustion won't happen. 100 streams each 5Meg is tested internally.


To Enable this feature:

(config) #firewall shape-mcast

Automatically shape bursty multicast traffic

To Disable this feature:

(config) #no firewall shape-mcast

 

Version History
Revision #:
1 of 1
Last update:
‎11-13-2014 04:50 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.