I reached out to a few friends and nobody has been forced to use IPv6 so I'm reaching out here to see if anybody could test something for me. I'm sure it's either a bug or something stupid that is not jumping out at me.
Long story short: In a environment I'm working on currently, any vSS can't have more than one vmk with IPv6 on it. The address can be applied without warning from esxcli or the gui; however, the interface will never have connectivity unless it is brought on it's own vSwitch or all other vmk's are deleted off the vSwitch.
Pretty much what I would like somebody to try is to either confirm that they have a vSS with two IPv6 vmk's on it OR setup an new one and try it out. The only error I get in vmkernel.log is
Tcpip_Vmk: 97: nd6_rs_timer: no routers on 'vmk4'. Giving up
And this only comes after assigning an IPv6 address to a second adapter on the vSwitch, and no alerts in the GUI at all. Seeing that it is a Neighbor Discovery issue it could be a issue with the switch config? Networking isn't exactly my strong suit but I could give details on the 3750 config if needed.
Long story short: In a environment I'm working on currently, any vSS can't have more than one vmk with IPv6 on it. The address can be applied without warning from esxcli or the gui; however, the interface will never have connectivity unless it is brought on it's own vSwitch or all other vmk's are deleted off the vSwitch.
Pretty much what I would like somebody to try is to either confirm that they have a vSS with two IPv6 vmk's on it OR setup an new one and try it out. The only error I get in vmkernel.log is
Tcpip_Vmk: 97: nd6_rs_timer: no routers on 'vmk4'. Giving up
And this only comes after assigning an IPv6 address to a second adapter on the vSwitch, and no alerts in the GUI at all. Seeing that it is a Neighbor Discovery issue it could be a issue with the switch config? Networking isn't exactly my strong suit but I could give details on the 3750 config if needed.