king daddy
asked on
symmpi 9 error on VMs
Greetings,
a few of my VMs (including Veeam and Exchange) are reporting this error:
Source: symmpi
Category: None
Event ID: 9
Description:
The device, \Device\Scsi\symmpi1, did not respond within the timeout period.
It has happened 8 times since Feb 10 2012, with the most recent at 5:30 am this morning on both Veeam and Exchange.
the VMs are all on one host (ESX 4), VMs on the other host (ESXi 5) do not show this error. I read some stuff about SCSI problems but am still a little confused.
any help appreciated - thanks
a few of my VMs (including Veeam and Exchange) are reporting this error:
Source: symmpi
Category: None
Event ID: 9
Description:
The device, \Device\Scsi\symmpi1, did not respond within the timeout period.
It has happened 8 times since Feb 10 2012, with the most recent at 5:30 am this morning on both Veeam and Exchange.
the VMs are all on one host (ESX 4), VMs on the other host (ESXi 5) do not show this error. I read some stuff about SCSI problems but am still a little confused.
any help appreciated - thanks
ASKER
not really sure what I am looking for but performance in vCenter looks normal - no obvious spikes in network, CPU, memory except around 5:30 am this morning. This was on the Veeam and Exchange servers, not the host performance monitor. All datastores are attached and appear normal. Networking looks fine as well.
I've read about updating SCSI drivers, but is that on the host or the individual VMs? I've also read about shrinking the VM - but not sure what that would do.
thx
I've read about updating SCSI drivers, but is that on the host or the individual VMs? I've also read about shrinking the VM - but not sure what that would do.
thx
VM storage drivers, is the random, or at particular times, eg. backup times?
single server pr all servers, other servers on same lun affected?
ASKER
random, error this morning was 2 hours after backup ended. Previous days show 9:30 - 10:30 am and 3 - 3:30 PM. definitely wouldn't be messing with storage during production hours.
looking now for directions on updating storage drivers unless you have info. the servers are windows 2003, veeam is 64-bit on an HP DL360 G6
looking now for directions on updating storage drivers unless you have info. the servers are windows 2003, veeam is 64-bit on an HP DL360 G6
is this just 2003? single vm or multiple?
ASKER
Veeam on local disks - affected.
Exchange on LUN with 2 other VMs - only exchange affected. no other servers have error.
Exchange on LUN with 2 other VMs - only exchange affected. no other servers have error.
battery on iPad getting low 9% just in case go radio silent on you....
both 2003?
both 2003?
before I go dark.....have a read of this
http://www.happysysadm.com/2010/09/vmware-guests-and-iscsisan-storage.html
http://www.happysysadm.com/2010/09/vmware-guests-and-iscsisan-storage.html
ASKER
yes, both 2003 Veeam 64-bit
ASKER
Thanks for the link
ASKER
so I see where to change the registry and will do so but should I be concerned that this happened 8 times over the last month? I guess if it doesn't register again I'm good but I'd like to figure out what happened, if possible. I guess I'll also look for updated storage drivers just in case.
thx
thx
ASKER
is it weird that the vmnics going to my SAN don't show an observed IP range? They show a speed of 1000 full and they are definitely connected as I have VMs running on SAN datastores and there are no alarms. The vmnics for the LAN do show an observed IP range.
The observed IP range, is discovered if there is lots of LAN traffic, from clients and servers.
Sometimes, you may not see a detected IP range on a Storage Network, with just end to end points.
Sometimes, you may not see a detected IP range on a Storage Network, with just end to end points.
ASKER
happened again. only Veeam. last night 8:00, then Plug and Play error 12 at 10 pm and 4:30 am, then symmpi at 4:47, 5:32, 5:33 am, then Plug and Play error 12 again at 6:47 am. I am going to tweak the reg setting after my failed backup runs again but I need some insight into what is causing this - and I guess troubleshooting steps because I have no idea why this would start happening all of a sudden.
thx
thx
ASKER
just noticed Veeam registered the symmpi error 9 at 7:50 am. backup started at 7:48 according to veeam.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So Veeam is on internal disks so it must be something to do with the San connections. I have 3 nics on Veeam - one LAN and two on San subnets (.50 and .100). I have ms iscsi initiator configured to an EMC ax4 and EMC power path as well. No obvious performance issues on any servers and the only other server to show this error is my exchange server which is on the ax4.
Any ideas on how I can troubleshoot this? Don't want this to be something that'll essentially shut down or at least stop communications with the ax4.
Thanks a lot
Any ideas on how I can troubleshoot this? Don't want this to be something that'll essentially shut down or at least stop communications with the ax4.
Thanks a lot
Interesting it was the Microsoft iSCSI initiator that caused us issues
ASKER
I'll look for any logs for it. Wonder if I should look for an updated version. Still, it's not on exchange and that server showed the error. Is the initiator necessary since I have power path configured?
ASKER
so I filtered the event viewer for just symmpi and there were 64,000 entries. event viewer only showed the first 23,000 with the last entry of those 23,000 dated 09/13/2010. so this must have been occurring since the Veeam server was installed but I never noticed because up until a couple of weeks ago it didn't cause an issue with the backup of a VM nor did it cause the Veeam server to crash and reboot. I edited the registry but it happened again last night around 8 PM and again this morning around 5 AM. After filtering, I am definitely seeing a pattern. My first backup starts around 8 PM and I have two other backups scheduled for 4:20 and 4:45 AM. Another backup is scheduled for 5:30. the specific times are 4:48 AM, 5:39 AM, and 8:03 PM. This is everyday but some days have entries at other, sporadic times. I am not as concerned as this has been happening for years without major issue, but would still like to figure out what is causing this. I was thinking of either re-configuring the MS iSCSI initiator and / or building a new Veeam server.
thx
thx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you may need to change registry parameters