UNSOLVED
CX3-80 strange performance metrics and disk access issues
I have a new CX3-80 installed which is replacing my CX500. I have moved over one 400GB parition using a backup/restore method and have had a number of strange problems since. I don't know if the NaviAnalyzer stuff is much different on the 80, but here is what I am seeing:
Collected Data = SPB, LUN1100, watching Service Time and Write Cache Hit Ratio. Approximately every 4 minutes, all of these metrics go from their average value down to 0. Sometimes it goes a little longer than 4 minutes, but generally it almost looks like some type of flush event.
If I monitor a disk in LUN1100, the service time does not drop to 0. During that same time, the SP Queue length stays normal (.3), but the disk queue length drops to 0 with the service time on the LUN.
The problem that we are having is that a Windows2003E host reports "Not enough server storage is available to process the command" during large file transfer operations (100+mb generally). After it happens once for the day, we generally need to fail the resource over to a new server (MS Clustering).
We have identical traffic on our CX500. We even built a new cluster node using the same (older) server hardware vs. the new stuff we put in to use with the new SAN. Same drivers, same HBA's, same PP, etc.
The new SAN is connected to a new Cisco MDS, while the CX500 is using older 32 port Brocades.
Any ideas? Has anyone seen any performance metrics like that and if so, is that considered normal?
Collected Data = SPB, LUN1100, watching Service Time and Write Cache Hit Ratio. Approximately every 4 minutes, all of these metrics go from their average value down to 0. Sometimes it goes a little longer than 4 minutes, but generally it almost looks like some type of flush event.
If I monitor a disk in LUN1100, the service time does not drop to 0. During that same time, the SP Queue length stays normal (.3), but the disk queue length drops to 0 with the service time on the LUN.
The problem that we are having is that a Windows2003E host reports "Not enough server storage is available to process the command" during large file transfer operations (100+mb generally). After it happens once for the day, we generally need to fail the resource over to a new server (MS Clustering).
We have identical traffic on our CX500. We even built a new cluster node using the same (older) server hardware vs. the new stuff we put in to use with the new SAN. Same drivers, same HBA's, same PP, etc.
The new SAN is connected to a new Cisco MDS, while the CX500 is using older 32 port Brocades.
Any ideas? Has anyone seen any performance metrics like that and if so, is that considered normal?
