Quality of Service (QoS) for multicast equipment in UDP

[cadumep12]

Hello experts, good morning!
I would like some assistance or ideas for a scenario I'm facing. I'm new to dealing with networks, especially CISCO. Here's the lab setup I have:
I have a Cisco switch (WS-C3560X-48) to be used with TV equipment, which will communicate via Multicast. A VLAN was configured in access mode on the ports and communication was validated, but with some freezing issues. To fix this, the idea of configuring QoS, IGMP-Carrier, and IGMP Snooping was suggested. Once I adjust the IP targeting via the modulator (connected equipment), it's advisable to link the SWITCH PORT, mapping the MODULATOR by Mbits and IPs, setting up filters per port on the SWITCH, for example: MODULATOR 1 - IPs XXXXXXXXXXXXXXX - 20 Mbits flow connected to port 1 of CISCO SWITCH, remembering the QoS application for UDP, which by default is in TCP, focusing on filtering by MODULATOR with attention to the IPs configured on them and also the transport MEGABITS that will be connected to the SWITCH ports to prevent the total flow from overwhelming all SWITCH ports.
Example: port 2 - 192.168.2.11 - Modulator 2 will communicate with port 5 - 192.168.2.12 - GATEWAY LAND 1.
Has anyone seen a similar scenario or have an idea of how to perform these configurations?

[Joseph W. Doherty]

I confess I'm a bit confused by your posting, but can say QoS can be used to insure your multicast video obtains the network resources it needs.

For non-realtime video you need to guarantee it somewhat more (perhaps +10%) than its average bandwidth usage and try to preclude any drops.  You might accomplish the forgoing using a dedicated egress queue.  (How it's specifically done depends on device and/or IOS version.)

BTW, I recall (?) igmp snooping might be on by default but you need an igmp querier for it to work.  (Normally provided by the multicast routing gateway.)

Unknown, to me, what an igmp-carrier is.

[cadumep12]

Sure, and using only QoS to ensure prioritization of UDP traffic and guaranteeing that bandwidth on:

Model: WS-C3560X-48

SW Version: 12.2(55)SE3

SW Image: C3560E-UNIVERSALK9-M

[Joseph W. Doherty]

BTW the 3560x uses, the much  confusing, MLS QoS.  It also supports 4 egress queues, when QoS is enabled.  It also, like other Catalyst 2k and 3k switches are a bit light in queuing resources.  Lastly. your IOS version is considered one of the best for those switches but yours is at a very early patch level.

[cadumep12]

Eu entendo, vou continuar tentando ajustar as filas com MLS QoS, para priorização UDP, como devo proceder?

[Joseph W. Doherty]

Enable QoS.

Tag video traffic, upon ingress, with a DSCP marking.

Direct that traffic to a dedicated, to it, egress queue.

Adjust bandwidth or buffer allocations, if needed.

Do not use the first egress queue (as it's the only queue which supports PQ).

[cadumep12]

Ok, vou tentar aqui, obrigado pelo apoio

[cadumep12]

Good morning, I ran a test here, but the multicast traffic from the devices didn't work. This was the configuration applied:
conf t
mls qos
ip access-list extended VIDEO-TRAFFIC
permit udp any any eq 5000
class-map match-all VIDEO-CLASS
match access-group name VIDEO-TRAFFIC
policy-map VIDEO-POLICY
class VIDEO-CLASS
set dscp af41
bandwidth percent 30
class class-default
set dscp default
interface gigabitEthernet0/1 (example interface)
srr-queue bandwidth share 1 30 35 5
srr-queue bandwidth shape 10 0 0 0
service-policy input VIDEO-POLICY
if anyone has any ideas, it would be very helpful

[cadumep12]

The end devices are still experiencing many errors; this is the configuration:

[Joseph W. Doherty]

Looking at your attachment, it's unclear, to me, whether your ingress policy in on the correct ports.  It needs to be on the port(s) that receive the multicast for redistribution.

Once you enable MLS QoS, you have a default QoS egress policy, which you may not need to immediately modify until we clarify your video traffic is being correctly tagged and egressing as we desire.

For your egress interfaces, especially ones you believe are having issues (try):

sh int sum
show mls qos interface {interface} statistics
show platform port-asic stats drop {interface}

[cadumep12]

follow drop outputs from interfaces.

[Joseph W. Doherty]

Try

int g0/11
no srr-queue bandwidth share 1 50 30 20
no srr-queue bandwidth shape 10 0 0 0
priority-queue out

[cadumep12]

Ok, I will try with this configuration, just with mls qos enabled globally, right?

[Joseph W. Doherty]

Correct.

[Joseph W. Doherty]

Oh, also do a stats capture, before and after (so we can assess impact of changes).