- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Comware Based
- >
- 7500 Switch - Routing issue with NLB multicast ser...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
07-21-2017 03:12 AM
07-21-2017 03:12 AM
7500 Switch - Routing issue with NLB multicast servers
Hi all,
in our network we have this situation: we are using a cluster of 2 virtual NLB servers hosted each on a ESX server and configured in multicast mode. To limit broadcast traffic, we would like to configure static multicast MAC address entry along the path toward servers.
In our case, servers are connected to a switch HP 7506 (switch "B"), which is directly connected to the core switch (another HP 7506, switch "A") using bridge-aggregation 2 of switch B to bridge-aggregation 1 of switch A.
We have configured static multicast MAC, fixing the VIP multicast mac-address both on the interfaces of switch B where two servers are connected (3+3 interfaces) and on the bridge-aggregation 1 (uplink of switch A to B):
mac-address multicast "mac-address" interface "interface-list" vlan "vlan-id"
We have also disabled the ARP entry check function on the switches (undo arp check enable).
After this configuration, we can reach servers from clients on the same vlan of the servers but not from clients on other vlans (routing is on the switch A); however we can ping the cluster virtual IP from switch A also using other vlans as ping source (so not only form server vlan).
We also tried to configure static ARP entry on the switch A (described as option on the reference guide) but nothing changed.
Whats' wrong with this configuration? Or are there some known issues witch L3/routing using multicast?
Thanks in advance to all.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP