Hello @Fernandomunoz81
The issue you're describing seems to be related to multicast traffic forwarding between VLANs on your IE-5000 switch. Let's break this down and troubleshoot step by step:
1. Multicast Forwarding Basics
Multicast traffic requires specific configurations to ensure it is forwarded correctly between VLANs. In your case:
- Multicast traffic is coming in on VLAN 14 (interface GigabitEthernet1/13).
- It needs to be forwarded to VLAN 420 (interface TenGigabitEthernet1/27).
You have configured ip pim dense-mode on both VLAN interfaces, which is correct for enabling multicast routing. However, there are additional considerations to ensure multicast traffic flows properly.
2. Check IGMP Membership
Multicast traffic forwarding depends on IGMP (Internet Group Management Protocol) to determine which interfaces are interested in receiving specific multicast groups. If there are no IGMP joins on VLAN 420, the multicast traffic will not be forwarded.
Verify IGMP Membership: Use the following command to check IGMP group memberships on the switch:
show ip igmp groups
Ensure that the multicast group(s) from VLAN 14 are being joined on VLAN 420.
Enable IGMP Snooping: If IGMP snooping is not enabled, the switch may not properly forward multicast traffic. Enable IGMP snooping globally and on the VLANs:
ip igmp snooping
ip igmp snooping vlan 14
ip igmp snooping vlan 420
3. Multicast Routing Configuration
Your configuration includes ip pim dense-mode on both VLAN interfaces, which is required for multicast routing. However, ensure the following:
Multicast Routing is Enabled Globally: Verify that multicast routing is enabled on the switch:
ip multicast-routing
If it is not enabled, add this command to the global configuration.
Check PIM Neighbors: Use the following command to verify PIM neighbors:
show ip pim neighbor
Ensure that the IE-5000 and the 3750 are PIM neighbors on VLAN 420. If they are not, multicast traffic will not be forwarded.
4. Check HSRP Configuration
You are using HSRP (Hot Standby Router Protocol) on both VLANs. Ensure that the HSRP virtual IP addresses are not interfering with multicast traffic. HSRP itself uses multicast (224.0.0.2), so there could be conflicts if multicast routing is not properly configured.
- Verify HSRP Status: Use the following command to check HSRP status:
show standby brief
Ensure that the HSRP configuration is correct and that the switch is the active router for both VLANs.
5. Check Multicast Traffic Flow
Use the following commands to verify multicast traffic flow:
Check Multicast Routes:
show ip mroute
This will display the multicast routing table. Look for the multicast group(s) being sent by the public address server. Ensure that there is an outgoing interface (OIL) for VLAN 420.
Debug Multicast Traffic: Use the following debug commands to troubleshoot multicast traffic:
debug ip pim
debug ip igmp
debug ip mpacket
These commands will provide detailed information about multicast traffic and PIM/IGMP activity.
6. Verify VLAN and Port Configuration
Ensure that the VLAN and port configurations are correct:
- VLAN 14:
- GigabitEthernet1/13 is correctly configured as an access port in VLAN 14.
- VLAN 420:
- TenGigabitEthernet1/27 is correctly configured as an access port in VLAN 420.
However, if the 3750 switch is connected via a trunk port, you may need to configure TenGigabitEthernet1/27 as a trunk port instead:
interface TenGigabitEthernet1/27
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 420
7. Check the 3750 Configuration
Ensure that the 3750 switch is properly configured to receive and forward multicast traffic:
- Verify that ip pim dense-mode is configured on the corresponding VLAN interface on the 3750.
- Check IGMP group memberships on the 3750:
show ip igmp groups
- Verify PIM neighbors on the 3750:
show ip pim neighbor
8. Test Multicast Traffic
To test multicast traffic, you can use tools like iperf or a multicast traffic generator. Alternatively, you can use the following commands to monitor multicast traffic:
- On the IE-5000:
show ip mroute
- On the 3750:
show ip mroute
Ensure that the multicast group(s) are present in the routing table and that the outgoing interface is correct.
Summary of Key Steps:
- Enable ip multicast-routing globally.
- Verify IGMP group memberships on VLAN 420.
- Check PIM neighbors and multicast routes.
- Ensure VLAN and port configurations are correct.
- Verify the 3750 configuration for multicast routing.
By following these steps, you should be able to identify and resolve the issue with multicast traffic not being forwarded from VLAN 14 to VLAN 420. Let me know if you need further assistance!
Hope This Helps!!!
AshSe
Forum Tips:
- Insert photos/images inline - don't attach.
- Always mark helpful and correct answers, it helps others find what they need.
- For a prompt reply, kindly tag @name. An email will be automatically sent to the member.
