- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: HSV300 is resetting on EVA4400
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2010 08:54 PM
тАО02-02-2010 08:54 PM
HSV300 is resetting on EVA4400
I have been checking the so many reported issues on EVA4400 on this forum.
not sure if any of you had encountered such issue with EVA4400.
We have EVA4400 with 2 HSV300 09501200, attached to 2 borcade SWs with no zoning configured managed through mgt server CV v9.1. From time to time the HSV300 reboots by itself. I have attched the log.
the alarms are mainly about Back-end Fibre Channel Port transitions. and battary state change.
Do you think it has to do with the XCS version should I consider upgrading to 09522000?? is there any cons to be considered regarding the upgrade?
Many Thanks
Aladdin
EVA-logs.txt
----------------------------------
20:07:30:125
11-Jan-2010
Controller 2 031a000a #100296
An HSV300 controller has completed discovering devices on the backend loops.
Corrective action code: 00 More details
20:07:24:610
11-Jan-2010
Controller 2 066a0028 #100295
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:609
11-Jan-2010
Controller 2 066a0028 #100294
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:561
11-Jan-2010
Controller 2 066a0028 #100293
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:561
11-Jan-2010
Controller 2 066a0028 #100292
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:560
11-Jan-2010
Controller 2 062d0012 #100291
An HSV300 controller issued a directed LIP to an arbitrated loop physical address.
Corrective action code: 00 More details
20:07:20:560
11-Jan-2010
Controller 2 060b4709 #100290
A non-data exchange sent to a physical disk drive has timed out.
Corrective action code: 47 More details
20:07:12:964
11-Jan-2010
Controller 2 0319000a #100289
An HSV300 controller has begun discovering devices on the backend loops.
Corrective action code: 00 More details
20:07:12:964
11-Jan-2010
Controller 2 066a0028 #100288
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:964
11-Jan-2010
Controller 2 066a0028 #100287
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:930
11-Jan-2010
Controller 2 066a0028 #100286
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:30:108
11-Jan-2010
Controller 1 031a000a #100285
An HSV300 controller has completed discovering devices on the backend loops.
Corrective action code: 00 More details
20:07:24:609
11-Jan-2010
Controller 1 066a0028 #100284
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:609
11-Jan-2010
Controller 1 066a0028 #100283
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:561
11-Jan-2010
Controller 1 066a0028 #100282
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:24:561
11-Jan-2010
Controller 1 066a0028 #100281
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:20:929
11-Jan-2010
Controller 1 060b4709 #100280
A non-data exchange sent to a physical disk drive has timed out.
Corrective action code: 47 More details
20:07:12:964
11-Jan-2010
Controller 1 0319000a #100279
An HSV300 controller has begun discovering devices on the backend loops.
Corrective action code: 00 More details
20:07:12:964
11-Jan-2010
Controller 1 066a0028 #100278
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:964
11-Jan-2010
Controller 1 066a0028 #100277
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:929
11-Jan-2010
Controller 2 066a0028 #100276
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:930
11-Jan-2010
Controller 1 066a0028 #100275
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:930
11-Jan-2010
Controller 1 066a0028 #100274
A Back-end Fibre Channel Port transitioned to link up or link down.
Corrective action code: 00 More details
20:07:12:929
11-Jan-2010
Controller 1 062d0012 #100273
An HSV300 controller issued a directed LIP to an arbitrated loop physical address.
Corrective action code: 00 More details
20:07:08:929
11-Jan-2010
Controller 1 060b4709 #100272
A non-data exchange sent to a physical disk drive has timed out.
Corrective action code: 47 More details
20:07:04:060
11-Jan-2010
Controller 2 0102000d #100271
A time change occurred.
Corrective action code: 00 More details
20:07:04:060
11-Jan-2010
Controller 2 0102000d #100270
A time change occurred.
Corrective action code: 00 More details
20:07:04:060
11-Jan-2010
Controller 1 0966000f #100269
Time was set on a Storage System.
Corrective action code: 00 More details
20:07:04:060
11-Jan-2010
Controller 1 0102000d #100268
A time change occurred.
Corrective action code: 00 More details
20:07:04:059
11-Jan-2010
Controller 1 0102000d #100267
A time change occurred.
Corrective action code: 00 More details
20:07:04:059
11-Jan-2010
Controller 1 0102000d #100266
A time change occurred.
Corrective action code: 00 More details
20:05:36:000
11-Jan-2010
Controller 1 03260027 #100265
An HSV300 controller has changed Battery Cache policy
Corrective action code: 00 More details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2010 03:36 AM
тАО02-03-2010 03:36 AM
Re: HSV300 is resetting on EVA4400
If you do not have XCS 09522000, ugrade to it. It's not bug-free but at least has less bugs than previous versions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-03-2010 06:05 PM
тАО02-03-2010 06:05 PM
Re: HSV300 is resetting on EVA4400
I have attached the whole output.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2010 03:30 AM
тАО02-04-2010 03:30 AM
Re: HSV300 is resetting on EVA4400
The event log is full of
03260027; An HSV300 controller has changed Battery Cache policy
on controller 1d25 M
Because it's battery is transitioning to failed state and back
Also timeouts to the I/O modules and DP-1A failing
Reseat the battery and see if it keeps transitioning from good to bad state. If it does, replace it.
Update to 0952200 to avoid the timeouts to the I/O modules and loop resets. Or disable time synchronization on Command View. The timeouts happen after CV tries to update the time on the I/O modules. This is a known bug.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2010 08:39 PM
тАО02-08-2010 08:39 PM
Re: HSV300 is resetting on EVA4400
I have reseated the battery which I have replaced recently for the second time, but still same issue. I will upgrade the FW and see.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2010 05:31 PM
тАО04-25-2010 05:31 PM
Re: HSV300 is resetting on EVA4400
I am having trouble viewing the log files since its file extension is .idi. Can you give me some assistance since i can see that you were able to view the detailed log file.
Thanks and Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2010 04:43 AM
тАО04-26-2010 04:43 AM
Re: HSV300 is resetting on EVA4400
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2010 01:22 AM
тАО08-03-2010 01:22 AM
Re: HSV300 is resetting on EVA4400
I have 2 EVA on DC and DR, controller1 on DC reboot after log in 1 DR group is full, in my opinion log full should not be the cause of controller reboot.