error ipv4 multicast entry
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-28-2015 06:52 PM
I open a GTAC case, I just put in this x440 stack (today first day of production) and I got the ipv4 multicast entry error any suggestions?
27 REPLIES 27
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-06-2016 12:22 AM
Thanks.. No reboot I check
Slot-1 MDF-U-st.2 # sh config "mcmgr"
#
# Module mcmgr configuration.
#
configure igmp snooping filters per-vlan
configure forwarding ipmc lookup-key group-vlan
Slot-1 MDF-U-st.2 # sh config "mcmgr"
#
# Module mcmgr configuration.
#
configure igmp snooping filters per-vlan
configure forwarding ipmc lookup-key group-vlan
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-06-2016 12:22 AM
You can check to make sure that the configuration is there by doing the command, "show config mcmgr" - It should show you the configuration that you are using assuming it is there.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-05-2016 10:46 PM
The error appear again,
Slot-1 MDF-U-st.1 # sh log sev war
01/05/2016 14:14:07.07 Slot-1: IPv4 multicast entry not added. Hardware Group Table full.
01/05/2016 08:17:16.70 Slot-1: Previous message repeated 3 additional times in the last 9511 second(s)
maybe last resort will be to put only L2, will this impact current traffic? do I need a maintenance window?
Slot-1 MDF-U-st.1 # sh log sev war
01/05/2016 14:14:07.07
01/05/2016 08:17:16.70
maybe last resort will be to put only L2, will this impact current traffic? do I need a maintenance window?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎01-05-2016 10:46 PM
Hi,
do you have any requirement or protocol needing L3 IPMC? This include PIM, MVR IGMPv3 and Private VLAN. If so, you'll need to turn on mixed-mode instead of mac-vlan as they cannot work in L2 mode. You should have a message saying that from the CLI.
The User Guide is a helpful resource for the details.
do you have any requirement or protocol needing L3 IPMC? This include PIM, MVR IGMPv3 and Private VLAN. If so, you'll need to turn on mixed-mode instead of mac-vlan as they cannot work in L2 mode. You should have a message saying that from the CLI.
The User Guide is a helpful resource for the details.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-30-2015 04:43 PM
Sort of related to this,
I am working on new configs for a network refresh for one of our customers.
Code version: 15.7.2.9
Our current default multicast config for mixed networks (440/460) is:
enable igmp snooping forward-mcrouter-only vr VR-Default
configure igmp snooping filters per-vlan
configure forwarding ipmc lookup-key group-vlan
The customer has distributed routing from the the building MDF closets I started working on some of the IDFs and the above config worked fine.
When I got to the MDF I found the current gear has:
enable ipmcforwarding vlan "ADDAMSD100"
enable ipmcforwarding vlan "RO_AES_HS_link"
enable ipmcforwarding vlan "RO_AES_SVR"
enable ipmcforwarding vlan "RO_AES_USR"
This does not work with in conjunction with our current default config. So I am trying to determine how to proceed. The MDF stacks are all 460s so they should be fine with the modifications to the table entries.
My concern is will things work with modified entries in the IDF and default entries in the MDF? Or should we use the default multicast table entry method everywhere and just deal with the error messages in the IDFs?
Thanks,
I am working on new configs for a network refresh for one of our customers.
Code version: 15.7.2.9
Our current default multicast config for mixed networks (440/460) is:
enable igmp snooping forward-mcrouter-only vr VR-Default
configure igmp snooping filters per-vlan
configure forwarding ipmc lookup-key group-vlan
The customer has distributed routing from the the building MDF closets I started working on some of the IDFs and the above config worked fine.
When I got to the MDF I found the current gear has:
enable ipmcforwarding vlan "ADDAMSD100"
enable ipmcforwarding vlan "RO_AES_HS_link"
enable ipmcforwarding vlan "RO_AES_SVR"
enable ipmcforwarding vlan "RO_AES_USR"
This does not work with in conjunction with our current default config. So I am trying to determine how to proceed. The MDF stacks are all 460s so they should be fine with the modifications to the table entries.
My concern is will things work with modified entries in the IDF and default entries in the MDF? Or should we use the default multicast table entry method everywhere and just deal with the error messages in the IDFs?
Thanks,
