Unsolved
This post is more than 5 years old
92 Posts
0
2154
March 7th, 2011 12:00
Errors on recovery side
Hey I was performing an SRM test as well as a SQL access test today and I noticed the following errors in the RecoverPoint management program:
WARNING: 19 timeouts occurred during the past 60 minutes from hba_0 to 0x500601603ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: 10 timeouts occurred during the past 60 minutes from hba_1 to 0x500601603ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_2 to 0x500601613ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: 13 timeouts occurred during the past 60 minutes from hba_3 to 0x500601613ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_2 to 0x500601683ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_3 to 0x500601683ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_0 to 0x500601693ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_1 to 0x500601693ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: Degradation of outgoing RPA I/O speed occurred during the past 60 minutes. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 1 in Springfield
WARNING: 9 timeouts occurred during the past 60 minutes from hba_0 to 0x500601603ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: 10 timeouts occurred during the past 60 minutes from hba_1 to 0x500601603ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_2 to 0x500601613ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: 5 timeouts occurred during the past 60 minutes from hba_3 to 0x500601613ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_2 to 0x500601683ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_3 to 0x500601683ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: More than 20 timeouts occurred during the past 60 minutes from hba_0 to 0x500601693ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
WARNING: 15 timeouts occurred during the past 60 minutes from hba_1 to 0x500601693ce008a4. Possible causes: slow storage, bad Fibre Channel cable, or other connectivity issue. ; Springfield ; RPA 2 in Springfield
I know that all my cables are connected and i dont see any particular errors on the fiber channel switches. Any idea what would cause this?
RickBrunner1
117 Posts
0
March 7th, 2011 13:00
A number of issues could cause this as the messages indicate. I would check the IO service times on the array and determine if they are acceptable.
If you do not see an issue with the array service times, open a service request and have it root caused by emc.
-rick
forshr
2 Intern
•
1.1K Posts
0
March 7th, 2011 14:00
In addition to Rick and Pat's replies, as the events are for different RPAs and storage ports it is very likely that the storage is slow to respond or the tests you ran created a very high load. If these errors have since disappeared then this adds further support in favour of this probability. To be on the safe side, raise and SR and capture the run the RecoverPoint system log collection for the period that the errors appeared.
Swanson1
1 Rookie
•
116 Posts
0
March 7th, 2011 14:00
I'm going to move this discussion to the Support Forum.
Mabro1
2 Intern
•
666 Posts
0
March 8th, 2011 03:00
I have moved this question to the Replication support Forum to ensure it gets to the right audience.
Regards,
Mark