Thursday
Hi There!
We are implementing a service called Digital Video Signage. For this, the corresponding ports were configured and VLAN ID 1807 was assigned. Initially, I thought it would be for cameras (based on the VLAN name displayed on the 5520-24X switch), but they later clarified that the service is for displaying information on these televisions.
In Buildings 1A and 1H, the televisions are connected to VLAN 1807. In Building 1G, there is a server with an application that, according to the IT administrator at the Faculty, has the following characteristics: it uses SADP (Search Active Device Protocol), a Hikvision utility that uses the multicast address 239.255.255.230 and UDP port 37020.
From the server, we can ping the televisions, but the application that performs the device discovery cannot detect them (we also tested with the server's firewall disabled). The IT administrator at the Faculty has asked us to review the multicast and IGMP snooping settings on this VLAN. Could you please assist us with this request, either by reviewing these settings or any other parameters you deem necessary given the nature of the service we are trying to implement?
I attached a picture showing the involved switchs: 5520-24x (voss) and 3 exos .
The Video server is at port 4:36 of the 128.94 exos switch.
The TV01 is at port 34 of the 128.232 exos switch
The TV02 is at port 23 of the 128.111 Switch Engine 5320-24P-8X
Best regards!
Solved! Go to Solution.
Friday
First i think you need to disable the IP igmp upnp-filter on this vlan, as the MC address you mention falls into this range.
if it still does not work, it could be related to the fact, that even in this scenario VOSS decrements the TTL of the packet, so if the application uses MC with TTL=1, it will get dropped.
The only choice (so far until we change this behavior, which is planned for next 9.4. release) would be to remove the IP MC config from the vlan and just flood the MC traffic from/to the EXOS switches.
Friday
First i think you need to disable the IP igmp upnp-filter on this vlan, as the MC address you mention falls into this range.
if it still does not work, it could be related to the fact, that even in this scenario VOSS decrements the TTL of the packet, so if the application uses MC with TTL=1, it will get dropped.
The only choice (so far until we change this behavior, which is planned for next 9.4. release) would be to remove the IP MC config from the vlan and just flood the MC traffic from/to the EXOS switches.
Friday
Hi Gfriedl
That solution worked as a charm!
Thank you for the support!
My best regards!
Friday
Hi Gfriedl!
Thank you for answering!
I will do the first step and will reply what happened.
"The only choice (so far until we change this behavior, which is planned for next 9.4. release) would be to remove the IP MC config from the vlan and just flood the MC traffic from/to the EXOS switches."
What is the CLI for this? If it would be the case.
Best regards!
Thursday