vsphere 4.1 u2 - vmkernel error

[cemdur]

we are getting the following error in vmkernel log  , i didn't find any kb in vmware support.

any  suggestion ?

ps: esx version is vsphere 4.1  U2  

Dec 10 17:50:51 esx01 vmkernel: 0:00:20:51.553 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311
Dec 10 17:51:07 esx01 vmkernel: 0:00:21:08.053 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311
Dec 10 17:51:11 esx01 vmkernel: 0:00:21:12.155 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311
Dec 10 17:51:11 esx01 vmkernel: 0:00:21:12.164 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311
Dec 10 17:51:13 esx01 vmkernel: 0:00:21:13.663 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311
Dec 10 17:51:14 esx01 vmkernel: 0:00:21:15.163 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311
Dec 10 17:51:16 esx01 vmkernel: 0:00:21:16.663 cpu4:4100)NetDiscover: 732: Too many vlans for srcPort 0x1000002; won't track vlan 311

thanks

[beckham007fifa]

how many Vlans do you have configured? also is your server a blade or standalone?

[peetz]

Hi,

we are also seeing this on our HP BL620c G7 blades after upgrading to Update 2. We have quite a lot VLANs (20 or 30) on these ports.

I believe "NetDiscover" is just the function that tries to track what IP address ranges are used on each port or VLAN (which is then displayed e.g. in the vSphere client). That's useful information, but it is not necessary for correct handling of the VLAN traffic.

I consider this only a warning (not an error), and I haven't seen any related network problems since Update 2.

- Andreas

[cemdur]

we have 60-70 VLANs . it is not a blade server  ,  it is a  standalone server.

i think that issue releated with update 2  , we did not get any eror  on vsphere 4.1 u1 .

[cemdur]

is it possible that disable  NetDiscover  function in vsphere ? do we need it ?

thanks

[peetz]

I don't think so.

I believe it is safe to ignore this message. The "problem" of NetDiscover not being able to track so many VLANs probably existed before Update 2, but with Update 2 it is just reported in the logs for the first time.

If you are still worried you should open a support case with VMware to have this clarified.

- Andreas

[TZiegler]

Agree to peetz. Just researched, Message can safely be ignored it has only to do with the neighbour discovery and the log Message is a new one with 4.1 U2.

[peetz]

Yes, I opened a SR with VMware myself in the meantime, and a support engineer confirmed that the message can safely be ignored.

- Andreas

[beckham007fifa]

there is a limitation in passing vlan to a esx hosts, i think its 128 that can be passed to a trunked a trunked port. but you have vlan's well in limit and this won't be a problem I think so. Could you check with network team and confirm whether they havn't played around with this. and one thing was it was working before and recently you have got issue? also could you confirm for the no of port you have defined per switch?