we using multicast applications in our network and some days ago we encountered this problem which is related with multicast operation.
We have such topology in our network:
| Cat_6506 |
| Cisco_7606 |-------RECEIVER_2
* | g0/2
* | R2
* | Cat_3750 |---RECEIVER_1/SOURCE_1
In this topology SOURCE_1 is sending multicast traffic with multicast group address 188.8.131.52, RECEIVER_1 is requesting this group and receiving multicast traffic from SOURCE_1.
Then if RECEIVER_2 will start requesting multicast traffic for group 184.108.40.206, Cisco_7606 will add the interface g0/1 in output interface list for (*, 220.127.116.11) group, but this change in output interface list will not trigger Cisco_7606 to send pim join with this group to RP. The pim join will be sended after pim Join/Prune-Period [60s] for this group and only then RECEIVER_2 will receive multicast traffic from SOURCE_1. We think that somethink wrong is with multicast operation at this poin in Cisco7606.
In this situation Receiver_2 must wait from 1-60s [depending when the previos pim join message for this group was send to RP] for multicast traffic from SOURCE_1.
Does anybody had this problem and thanks in advance for comments.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...