- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- How does Virtual Connect (VC) handle multicast pac...
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
03-10-2014 11:32 AM
03-10-2014 11:32 AM
How does Virtual Connect (VC) handle multicast packets?
Hilt had a question regarding multicast packets:
**************
Need help with some networking that's a little out of my wheelhouse. A customer has asked the following :
Something else that we need to factor in is how we manage multicast (MC) traffic between the App servers. This will be between blades in an enclosure so we need to understand how we contain the MC traffic within the Virtual connect domain preventing it reaching the core network. And within the domain we need to separate Unicast and MC traffic ie: some E/W traffic will be Unicast and some MC, we need to protect the servers functioning with Unicast from being flooded by MC traffic.
If we enable IGMP snooping along with IGMP NoFlood, will that do the job ? Or am I way off here ?
*************
Comment from Dan:
I think that's the right direction and possibly add IGMP security that came in one of the 4.x releases.
Reply from Mark:
You have to include an mrouter or igmp querier inside the domain in your design else you will timeout.
No flood would make sense. Internal network possibly with 0 uplinks would keep inside.
***************
Any other comments?