HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem - General
cancel
Showing results for 
Search instead for 
Did you mean: 

HP c3000 w/ Virtual Connect fail multicast NLB vm

 
HowardLEE
Occasional Visitor

HP c3000 w/ Virtual Connect fail multicast NLB vm

ESX VM with virtual IP created by multicast NLB cannot be ping in network.
ESX 3.5 installed in HP c3000 with Virtual Connect. Configued 2 active and 2 standby netowrk port for this vlan.

How does VC work with multicast NLB?
3 REPLIES
HEM_2
Honored Contributor

Re: HP c3000 w/ Virtual Connect fail multicast NLB vm

VC by default should just flood multicast traffic on a vnet.

If the multicast traffic is IGMP-enabled and you enable IGMP snooping in VC then VC will only send the multicast traffic to ports who have joined that multicast group.

Are you pinging from the same network? I believe multicast NLB uses a multicast IP that resolves to a Unicast MAC... some routers don't like that and a static ARP entry would need to be added.
HowardLEE
Occasional Visitor

Re: HP c3000 w/ Virtual Connect fail multicast NLB vm

Hi HEM,

I only use std Microsoft multicast NLB in VM.(without enable IGMP). The cisco router and sw are configured with static ARP and ethernet channel LACP.

I cannot get response from multicast Virtual IP when pinging from any network. But when I change all configure to unicast NLB, it works.

Does you memtion some option need to enable in VC?
HEM_2
Honored Contributor

Re: HP c3000 w/ Virtual Connect fail multicast NLB vm

no, there is no option that needs to be configured in VC...

can you ping from the Cisco router? That is where you specified a static ARP entry right? so it should be able to ping at least from there.

Can you ping the unicast IP addresses of the NLB cluster nodes?

Not sure what's up, you might try disabling all but 1 uplink from VC to simplify the troubleshooting.