Wired Intelligent Edge

 View Only

HP E5406zl PIM Sparse Mode no longer adding addresses to multicast routing table.

This thread has been viewed 0 times
  • 1.  HP E5406zl PIM Sparse Mode no longer adding addresses to multicast routing table.

    Posted Jul 30, 2012 09:43 AM

    Hi All,

     

    Stuck on a really anoying problem.  We have configured Multicast routing for the first time 2 weeks ago using PIM-SM on a stand alone E5406zl configured with static routing between approx 10 vlans.  We had the configuration working but as of this morning the sh ip mroute command is not showing any learning multicast routes at all. Here is the relevant configuration commands:

     

    ip multicast routing 
    router pim 
        enable 
        bsr-candidate 
        bsr-candidate source-ip-vlan 11 
        rp-candidate 
        rp-candidate source-ip-vlan 11 
        rp-candidate group-prefix 224.0.0.0 240.0.0.0 
        rp-candidate hold-time 150 
        state-refresh 45 
    exit
    vlan 10-200
        ip pim-sparse 
            ip-addr any 
        exit 
    exit

     

    The output from sh ip igmp groups shows the following:

     IGMP Group Address Information
    
      VLAN ID Group Address   Expires       UpTime        Last Reporter   | Type
      ------- --------------- ------------- ------------- --------------- + ------
      1       239.255.255.250 0h 3m 24s     31d 19h 18... 10.31.224.7     | Filter
      10      224.0.1.1       0h 3m 12s     24d 20h 32... 192.168.10.51   | Filter
      10      232.44.44.233   0h 3m 7s      6d 5h 13m 35s 192.168.10.21   | Filter
      10      239.255.255.250 0h 3m 7s      6d 5h 8m 4s   192.168.10.23   | Filter
      10      239.255.255.254 0h 3m 9s      7d 5h 48m 33s 192.168.10.2    | Filter
      12      224.0.1.60      0h 3m 22s     31d 19h 19... 192.168.12.24   | Filter
      20      224.0.1.43      0h 3m 30s     6d 3h 7m 13s  192.168.20.13   | Filter
      100     224.0.1.43      0h 3m 36s     6d 4h 42m 50s 10.31.176.156   | Filter
      100     239.0.208.0     0h 3m 31s     6h 51m 53s    192.168.100.5   | Filter
      100     239.255.255.250 0h 3m 38s     6h 52m 34s    192.168.100.6   | Filter
      101     239.0.208.0     0h 2m 19s     5h 53m 47s    192.168.101.57  | Filter
      101     239.0.208.4     0h 2m 20s     0h 2m 17s     192.168.101.57  | Filter
      101     239.0.208.99    0h 2m 16s     0h 5m 22s     192.168.101.20  | Filter
      101     239.255.255.250 0h 2m 24s     6d 4h 29m 19s 192.168.101.20  | Filter
      105     239.0.208.0     0h 3m 47s     0h 0m 47s     192.168.105.28  | Filter
      105     239.0.208.16    0h 3m 51s     0h 0m 47s     192.168.105.28  | Filter
      105     239.255.255.250 0h 3m 51s     7d 3h 18m 27s 192.168.105.14  | Filter

     I can see that the address we are interested in (239.0.208.0) is in the igmp list accross multiple vlans but for some reason the switch is not adding it to the multicast routing table. 

     

    I have tried all the obvious commands to try and find the problem but am completely stuck now.  The switch is the E-BSR.

     

    Any suggestions on how to find out what process the switch is going through to decide when/why to add an address to the multicast routing table? 

     

    Thanks