Skip to Content
0
Apr 17, 2009 at 05:23 PM

Having a problem with NetWeaver systems on VMware when VMotion happens

169 Views

We have started to migrate systems to VMware as we migrate to 64-bit. But we are running into issues with network disconnects and short dumps that occur at the same time VMotions happen. Oddly, we don't see issues with every VMotion, just some of them.

We are running VMware ESX 3.5x. The guests are all Windows Server 2003 64-bit. We have BW 3.5 and Solution Manager 7 landscapes. The database servers are MS SQL Server 2005 64-bit on separate physical hardware (distributed SAP install). The BW install consists of a CI with 6 additional application servers. The Solution Manager systems are all single application/CI servers systems.

The type of errors we see are

>SYSBATCH R49 Communication error, CPIC return code 020, SAP return code 223

>SYSBATCH R5A > Conversation ID: 20680799

>SYSBATCH R64 > CPI-C function: CMRCV

> Q0I Operating system call recv failed (error no. 10054)

> Q0U Client <appserver>_PRD_00 is not known to the message server

> Q0I Operating system call SiPeekPendConn failed (error no. 10061)

and

> Unable to reach central lock handler

We've also seen short dumps if the database is being accessed during VMotion.

From the errors everything appears to be related to a network disconnect. But the disconnect in VMotion is supposed to only last a few milliseconds. Would that be enough to cause these types of issues?

Any help or advise is appreciated. I would also like to hear if anyone else has similar experiences.

Thanks,

Brian Fitzgerald