VMware Cloud Community
wayne7215
Contributor
Contributor

5.1 - VIM Performance warnings

Hi

I've seen in the syslogd those warnings every few seconds:

[FFF42D20 warning 'vim.PerformanceManager'] Calculated write I/O size 1036756 for scsi0:1 is out of range -- 1036756,prevBytes = 33479446016 curBytes = 33515732480 prevCommands = 38971curCommands = 39006
[FFF42D20 warning 'vim.PerformanceManager'] Calculated write I/O size 887291 for scsi0:2 is out of range -- 887291,prevBytes = 178116214272 curBytes = 178454272512 prevCommands = 352017curCommands = 352398
[290E2B90 warning 'vim.PerformanceManager'] Calculated write I/O size 683478 for scsi0:2 is out of range -- 683478,prevBytes = 178454272512 curBytes = 178479561216 prevCommands = 352398curCommands = 352435
[29A3EB90 warning 'Default'] Can't convert IP Address of type 0
[29AE0B90 warning 'Default'] Can't convert IP Address of type 0
[FFB82B90 error 'EnvironmentManager'] Unable to obtain the default HW version

Can someone explain me the vim.PerformanceManager warnings?

Another question is about the "Can't convert IP Address of type 0

I know the KB article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103879... but I can't belive that we really have to migrate each guest to figure out which guest's are generating those warnings. Can we figure out the guest in any other way?

Thx for any suggestions

Wayne

Reply
0 Kudos
5 Replies
Sreejesh_D
Virtuoso
Virtuoso

Another question is about the "Can't convert IP Address of type 0

I know the KB article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=103879... but I can't belive that we really have to migrate each guest to figure out which guest's are generating those warnings. Can we figure out the guest in any other way?

This powrcli script will help you to get the IPv4 details of the windows VMs. by doing this we can find out which VM has incorrect IP settings.

http://pingforinfo.com/powercli-to-see-the-windows-guest-ipv4-network-details/

wayne7215
Contributor
Contributor

You made my day Yezdi, thx Smiley Wink

But after we got all the IPv4 information's, we can't find any "not properly configured" nic's. The only thing we have are some Loopback Pseudo-interface 1 adapter with a 127.0.0.1 configuration. Could it be a IPv6 problem what is generating the "Can't convert IP Address of type 0" warnings? We don't use IPv6 at all and that's why we disabled just the protocol on all the guest. So do we have to disable all IPv6 components on our 2008R2 and 2012 servers with netsh although Microsoft strongly advise against?

How you guys handle the IPv6 in your vSphere enivronment?

Reply
0 Kudos
wayne7215
Contributor
Contributor

Ok, shame on me, the second WINS server should still be available in the network of course! We had a few guest with an old second WINS server and after changed those settings we don't have any further "Can't convert IP Address of type 0" warnings anymore.

Reply
0 Kudos
Sreejesh_D
Virtuoso
Virtuoso

[FFF42D20 warning 'vim.PerformanceManager'] Calculated write I/O size 1036756 for scsi0:1 is out of range -- 1036756,prevBytes = 33479446016 curBytes = 33515732480 prevCommands = 38971curCommands = 39006

Regarding this warning, Are you confgiured Storage DRS or Storage IO Control?

If so have a look at this KB and make necessary changes in collection level. Hope it will stop unnecessary events.

http://kb.vmware.com/kb/2009532

Reply
0 Kudos
wayne7215
Contributor
Contributor

It couldn't be the DRS at all. I disabled DRS for the last few days and we still have those warnings in the log.

Any other suggestions?

Reply
0 Kudos