- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: va7400 Warning State
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
тАО07-01-2003 01:15 PM
тАО07-01-2003 01:15 PM
va7400 Warning State
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2003 06:29 PM
тАО07-01-2003 06:29 PM
Re: va7400 Warning State
However, we continued to have periodic synchronous flashing of all the disks amber LED's. CV reported a lot of scrubbing going on, and Warning "non redundant disk access". This turned out that C1 had a "Link Up" state on J1 port trying to link to a phantom JBOD array which did not exist. Reseating the loopback plug on J1 (next to the FC port on the back)fixed that problem with phantom link up state.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2003 10:59 PM
тАО07-01-2003 10:59 PM
Re: va7400 Warning State
first of all log call with HP. Then check if you have data backup (this does NOT mean that something wrong to occur, but just good practice to be on the safe track).
Your VA has HP15 firmware, HP engineers will upgrade it to HP18, and upgrade commandView to 1.06.
From what you're saying I suspect that something is wrong at the backend of M/C2 controller. What - should be checked by HP - if this is really controller, disk or backend FC cable causing these symptoms.
You can use LUNs now. This warning is about redundancy loss (NOT data loss). It's very good that you noticed it.
What CV says when you're trying 'armdsp -i' and 'armdsp -a va1'?
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2003 11:04 PM
тАО07-01-2003 11:04 PM
Re: va7400 Warning State
As I said - if you see something wrong with VA please DO NOT run commands you do not know. Call HP!
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2003 02:27 AM
тАО07-02-2003 02:27 AM
Re: va7400 Warning State
As long as a suspicious fru is M/C2 is it worth to pull it out for troubleshooting? About recover. As I remember, healthy array replies to recover command as 'nothing to recover' (or smth like that). Am I wrong?
And last question. What is Volume Set and its serial number?
Thanks a lot in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2003 02:51 AM
тАО07-02-2003 02:51 AM
Re: va7400 Warning State
About recover: I did not try it by myself from VFP. From CV, yes, it says 'nothing to recover' or 'no need to recover'. Not sure about VFP command which may be able to force VA to reconstruct maps.
Volume set s/n is an identifier of current VA volume set. This value is written to all the disks within VA and allows any VA to which disk may be installed to recognize if this disks belongs to its volume set or not.
About 'armdsp -i': I do not know which OS you use, you need to stop host agent (HA_trigger in hpux), then stop opendial (dial_trigger in hpux), then find and move DeviceDBFile in anoter location, and then start these 2 services in reverse order. Then issue 'armdiscover' (new DeviceDBFile database file will be created). If armdiscover will discover VA, then run 'armdsp -i' and then 'armdsp -a', but if not.... then you may need HP CE onsite
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2003 03:26 AM
тАО07-02-2003 03:26 AM
Re: va7400 Warning State
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-02-2003 04:26 AM
тАО07-02-2003 04:26 AM
Re: va7400 Warning State
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-03-2003 11:43 AM
тАО07-03-2003 11:43 AM
Re: va7400 Warning State
When we had our problem with Warning: "Non redundant disk access", it was explained to me by the support center that the warning was referring to the disks on your JBOD, not the disks in the main enclosure. The disks in the M enclosure should be fine.
Again, I think your controller MC2 is losing its connection to your JBOD for some reason. Our VA7400 does not have a JBOD attached. However, each conroller has a loopback plug in the external port which keeps M/C1.J1 = M/C2.J1 = Link Up. When C2 was generating "Non redundant disk access" errors we were seeing M/C2.J1 = Link Down. I was looking for these port states in your attachment and could not find anything.