- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- "IpAddrMgr: Failed to allocate new HW IP multicast...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2015 10:38 AM
02-28-2015 10:38 AM
"IpAddrMgr: Failed to allocate new HW IP multicast [...] table full FIB entry" on a L2-only switch
Hello,
we have three switches: (a) 5412zl, (b) 5406zl anc (c) 2910al. The 5412zl is acting as our core switch, is connected to our carrier and L3 routing is enabled (IPv4 and IPv6). The other both switches 5406zl and 2019al only work in L2 mode.
Both L2-only switches send the SNMP trap
IpAddrMgr: Failed to allocate new HW IP multicast [...] table full FIB entry
First question: Why? Is there any reasonable explanation? Why should a L2-only switch be aware of IP addresses at all?
Second question, if there is a reasonable explanation: Why do we not see a similar message from our core L3-switch? This switch has much more traffic/packets to handle.
Last question, if there is still a reasonable explanation: What can we do against it?
Thanks, Matthias