bridgeasebo.blogg.se

1. #MULTICAST TRAFFIC GENERATOR REGISTRATION#
2. #MULTICAST TRAFFIC GENERATOR SOFTWARE#
3. #MULTICAST TRAFFIC GENERATOR WINDOWS 7#
4. #MULTICAST TRAFFIC GENERATOR SERIES#

#MULTICAST TRAFFIC GENERATOR SERIES#

To create the examples in this document, the following devices were used in a lab environment:Ĭatalyst 4908G-元 switch-router running Cisco IOS 12.0(7)W5(15d)Ĭatalyst 4003 switch running Catalyst OS 5.5(2)Ĭatalyst 6009 switch running Catalyst OS 5.5(2)Ĭatalyst 5509 switch running Catalyst OS 5.5(2)įor the IGMP Snooping Querier feature, two catalyst 6500/6000 series switches running 8.1(3) and 7.6(2a) Understanding and Configuring IGMP Snooping on Catalyst 4000Ĭonfiguring IGMP Snooping on Catalyst 6500/6000

#MULTICAST TRAFFIC GENERATOR SOFTWARE#

Refer to the following documents to constrain multicast traffic on Catalyst 40 switches running Cisco IOS® system software (Native Mode): This document explains constraining multicast traffic on Catalyst switches running CatOS. Note: You do not have to enable multicast routing (using the ip multicast-routing global configuration command) on the router if you just want to constrain multicasts on a single VLAN and you do not intend for multicast traffic to be forwarded to other interfaces or subnets (the router will complain that you must enable multicast routing when you enable PIM on the router interface but this warning can be safely ignored in this application). If you are using CGMP, the router must have CGMP enabled on the interface connected in the VLAN where the source and receivers are located. The router must have Protocol-Independent Multicast (PIM) enabled on the interface connected in the VLAN where the source and receivers are located.

#MULTICAST TRAFFIC GENERATOR REGISTRATION#

GARP Multicast Registration Protocol (GMRP), another mechanism for constraining multicast on Layer 2 devices, is not considered here. The switch must have Cisco Group Management Protocol (CGMP) or Internet Group Management Protocol (IGMP) snooping enabled. The basic requirements for constraining multicast traffic on a switch when the multicast source and all receivers are in the same VLAN are as follows: Readers of this document should be knowledgeable of the following: The IGMP snooping querier enables IGMP snooping within a VLAN where Protocol Independent Multicast (PIM) and IGMP are not configured because the multicast traffic does not need to be routed. With this feature, a router is no longer required to constrain multicast traffic when the multicast source and all receivers are in the same VLAN. Note: Starting from CatOS 7.1 and later versions on the Catalyst 6500/6000 series switches, a new feature is available called the Internet Group Management Protocol (IGMP) snooping querier. The answer is yes it is possible, and in most cases a router is required. We have tried to bridge to the two NICS on the Test Server.Network managers frequently ask whether it is possible to constrain multicast traffic on a switch when the multicast source and the multicast receivers are all on the same VLAN, and what the requirements are for accomplishing this goal-in particular, whether a router is required. On the Test Server we have enabled IP routing and set up the following static route “Route IP AS –p 224.0.0.0 mask 240.0.0.0 192.168.200.1”. Computers on the Test LAN need to be able to send Unicast and Multicast messages to the Production Server.Ĭurrently PC’s on the Test LAN can send ping requests to the production server but are unable to send Multicast requests. The Test Server has two NICs installed, one connecting to the Production Server and oneĬonnecting to a switch that connects to the Test LAN. I will refer to the PCs as Test server and Production Server. The two PCs are both connected together Via a switch.

#MULTICAST TRAFFIC GENERATOR WINDOWS 7#

We have two windows 7 PCs acting as routers.