Comware

 View Only
  • 1.  IPTV igmp-snooping

    Posted Nov 11, 2018 05:38 AM

    Hello Dears,

    i am having iptv service on a server connected directly to the core switch 10508 on vlan 60, and edge switches connected to the core, and the config as follows:

    Core Config:

    vlan 60
    name IPTV
    description IPTV
    igmp-snooping enable
    igmp-snooping drop-unknown
    igmp-snooping version 3
    igmp-snooping querier

     

    interface Vlan-interface60
    description IPTV
    ip address 10.6.60.1 255.255.0.0
    pim dm
    igmp enable
    igmp version 3

     

    edges config:

    vlan 60
    name IPTV
    description IPTV
    igmp-snooping enable
    igmp-snooping drop-unknown
    igmp-snooping version 3

    the issue is that sometimes when we turn the tv on it takes to much time to get us the welcome page for the iptv service, (3 mins), which is too much but the streaming is good and stable, and even when i try to ping from the core to the iptv server the ping is continuous with success rate 100%.

     

    so do you have any recommecndation for a better config?

    thanks in advance



  • 2.  RE: IPTV igmp-snooping

    Posted Nov 12, 2018 08:37 AM

    Hello

    Try to use pim sm instead of pim dm. 

    • PIM-SM is based on a "join protocol", where traffic is not forwarded on a segment unless an explicit request originates (typically through IGMP) from the network segment.
    • PIM-DM is based on a "flood and prune" mechanism, where everyone receives traffic until they explicitly inform (through the PIM-DM prune mechanism) that they do not want that particular stream. Thus, PIM-DM is typically deployed in topologies where listeners are densely populated. And PIM-SM is typically deployed where the receivers are sparsely populated over the network, so that most of the network segments’ bandwidth is conserved. You can configure dense mode or sparse mode on a per-interface basis. After they are enabled, some interfaces can run dense mode, while others run sparse mode. (reference)

    for configuration details see following configuration guide.