OPERATIONAL DEFECT DATABASE
...
...
One (or more) of these error messages are seen: 2015 May 5 20:20:29 F340.09.22-7009-1-NAM-634630999-Recreate %L2MCAST-SLOT3-3-L2MCAST_HW_INSTALL_FAIL: Hw install failed for vlan 2 (22, 239.1.1.1, *) entry! 2015 May 5 20:20:29 F340.09.22-7009-1-NAM-634630999-Recreate %L2MCAST-SLOT4-2-L2MCAST_MAC_FULL_LC: Failed to insert entry in MAC table for FE 0 swidx 1 (0x1) with err (mac table full). To avoid possible multicast traffic loss, disable OMF. Use the configuration CLI: "no ip igmp snooping optimise-multicast-flood"
This happens when the NAM module interfaces are allocated to a VDC that contains an M-series linecard with more than 11-12000 mac addresses learned.
The best workaround is to implement the NAM module in a dedicated VDC. It is highly recommended that the NAM-NX1 module be placed in an isolated VDC with 4 or more interfaces. At that point, the interfaces can be physically cabled into the M-series VDC so that tables sizes are not impacted. The other workaround is to unallocate the NAM interfaces from the VDC.
The NAM Module is based on an F2E linecard. When we try to use the NAM module in a VDC with an M-Series linecard that has more than 11-12000 MAC addresses learned, error messages are seen. This is because the NAM module immediately starts learning any MAC addresses in the VDC in its own mac table as soon as the NAM interfaces are moved to the VDC. The first is an error message that is seen immediately when allocating the NAM module interfaces to the VDC: 2015 May 5 20:20:29 F340.09.22-7009-1-NAM-634630999-Recreate %L2MCAST-SLOT3-3-L2MCAST_HW_INSTALL_FAIL: Hw install failed for vlan 2 (22, 239.1.1.1, *) entry! The second we see when a multicast membership report (join) message is sent after the NAM interfaces have been allocated to the VDC: 2015 May 5 20:20:29 F340.09.22-7009-1-NAM-634630999-Recreate %L2MCAST-SLOT4-2-L2MCAST_MAC_FULL_LC: Failed to insert entry in MAC table for FE 0 swidx 1 (0x1) with err (mac table full). To avoid possible multicast traffic loss, disable OMF. Use the configuration CLI: "no ip igmp snooping optimise-multicast-flood"
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
