[c-nsp] cisco 3560 & Multicast

[Sergey Velikanov [Intelsoft]]

Sergey Velikanov [Intelsoft] wrote:
> the problem was that my routers did not know path to source of multicast
> (ip was out of my network) I've discovered that problem solved when I do smth. like
> 
> interface Vlan151
>   description digitaltv
>   ip address 10.0.0.5 255.255.255.252 secondary
>   ip address 218.19.182.225 255.255.255.252
>   ip pim sparse-mode
> end
> 
> or
> 
> interface Vlan151
>   description digitaltv
>   ip address 218.19.182.225 255.255.255.252
>   ip pim sparse-mode
> end
> 
> ip route 10.0.0.5 255.255.255.255 218.19.182.226
> 
> 
> What method is better?

some people advise me use
ip mroute 10.0.0.4 255.255.255.252 218.19.182.226 instead of
ip route 10.0.0.5 255.255.255.255 218.19.182.226

but it works strange, it work only 3 minute

#sh ip mroute 224.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
        L - Local, P - Pruned, R - RP-bit set, F - Register flag,
        T - SPT-bit set, J - Join SPT, M - MSDP created entry,
        X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
        U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel
        Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
  Timers: Uptime/Expires
  Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.1.1.1), 00:01:29/00:03:10, RP 192.168.9.1, flags: SJCL
   Incoming interface: Null, RPF nbr 0.0.0.0
   Outgoing interface list:
     Vlan151, Forward/Sparse, 00:01:27/00:02:46
     Vlan999, Forward/Sparse, 00:01:18/00:03:10

(10.0.0.6, 224.1.1.1), 00:00:59/00:02:59, flags: LJT
   Incoming interface: Vlan151, RPF nbr 217.15.180.226, Mroute
   Outgoing interface list:
     Vlan999, Forward/Sparse, 00:00:59/00:02:00


but after about 3 minuts it is become like



#sh ip mroute 224.1.1.1
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
        L - Local, P - Pruned, R - RP-bit set, F - Register flag,
        T - SPT-bit set, J - Join SPT, M - MSDP created entry,
        X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
        U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel
        Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
  Timers: Uptime/Expires
  Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.1.1.1), 00:20:01/00:02:37, RP 192.168.9.1, flags: SJC
   Incoming interface: Null, RPF nbr 0.0.0.0
   Outgoing interface list:
     Vlan151, Forward/Sparse, 00:14:50/00:00:52
     Vlan999, Forward/Sparse, 00:19:50/00:02:37

(10.0.0.6, 224.1.1.1), 00:19:31/00:02:55, flags: PJTX
   Incoming interface: Vlan151, RPF nbr 217.15.180.226, Mroute
   Outgoing interface list: Null


why timer is expired ( it looks like Vlan999, Forward/Sparse, 00:03:20/00:00:00 and then disappers)?

if i use "ip route" instead of "ip mroute" timer periodically updates.

Could anybody comment this?