- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: EVA5000 VCS 4.x - 3.x Downgrade?
Disk Enclosures
1752590
Members
3797
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-09-2009 12:06 PM
тАО06-09-2009 12:06 PM
EVA5000 VCS 4.x - 3.x Downgrade?
Have a trash-and-burn EVA-5000 that I am using for testing VCS Upgrades and OS patching that is required as part of it. I cannot seem to downgrade the VCS from 4.100 to 3.110, even after de-initialising the Array.
Also, when I did upgrade the VCS and recable the SAN, only half the device paths were visible in "ioscan -fn"; the rest were "UNKNOWN". Even using the Fibre-Channel-00 driver install did not bring them back. Eventually I had to re-install SecurePath (Active/ Active instead of Active / Passive) then de-install it to get the devices recognised.
Has anyone seen these before and know how to work around them?
Share and Enjoy! Ian
Also, when I did upgrade the VCS and recable the SAN, only half the device paths were visible in "ioscan -fn"; the rest were "UNKNOWN". Even using the Fibre-Channel-00 driver install did not bring them back. Eventually I had to re-install SecurePath (Active/ Active instead of Active / Passive) then de-install it to get the devices recognised.
Has anyone seen these before and know how to work around them?
Share and Enjoy! Ian
Building a dumber user
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2009 12:40 AM
тАО06-10-2009 12:40 AM
Re: EVA5000 VCS 4.x - 3.x Downgrade?
Hmmmm, got it working. You can't use the GUI, you have to un-initialise the Array, use SSSU to select the un-initialised Array and then perform a "codeload [path to SSS file]". Once this is complete (wait for the codeload on the trays and disks to complete), you can initialise the Array.
10 points to Hufflepuff there. Share and Enjoy. Ian
10 points to Hufflepuff there. Share and Enjoy. Ian
Building a dumber user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-10-2009 04:01 AM
тАО06-10-2009 04:01 AM
Re: EVA5000 VCS 4.x - 3.x Downgrade?
Hi Ian,
To go from VCS v4.x to v3.x you must uninitialise the array before the codeload. I have done this many times no problem from CV. I have also done the un-init from CV or the OCP - no problem. Alos the versions you specified = all OK. The key thing is to un-init first or it will fail.
Are you using HP-UX as the OS? If so what version as this is where you can have fun with SP or MPIO as most people call it!
Assuming HP-UX for VCS VCS V3.xxx (A/P) you need SP V3.0c for VCS V4.xxx (A/A)you need SP V3.0f. Both versions can co-exist on the same platform and you would need both if you are using both versions of VCS. If you do not use them you can still use pvlinks.
I believe that this is correct up to HP-UX 11.23. For 11.31 the it is native.
Type in "spmgr" for V3.0c and "autopath" for 3.0f and you will see what params/qualifiers you have available for each cmd.
Alternatively put in "swlist" and look for the products.
Mark...
To go from VCS v4.x to v3.x you must uninitialise the array before the codeload. I have done this many times no problem from CV. I have also done the un-init from CV or the OCP - no problem. Alos the versions you specified = all OK. The key thing is to un-init first or it will fail.
Are you using HP-UX as the OS? If so what version as this is where you can have fun with SP or MPIO as most people call it!
Assuming HP-UX for VCS VCS V3.xxx (A/P) you need SP V3.0c for VCS V4.xxx (A/A)you need SP V3.0f. Both versions can co-exist on the same platform and you would need both if you are using both versions of VCS. If you do not use them you can still use pvlinks.
I believe that this is correct up to HP-UX 11.23. For 11.31 the it is native.
Type in "spmgr" for V3.0c and "autopath" for 3.0f and you will see what params/qualifiers you have available for each cmd.
Alternatively put in "swlist" and look for the products.
Mark...
if you have nothing useful to say, say nothing...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP