- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: PV and LV timeout values for rolling SAN Firmw...
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
тАО11-03-2009 09:50 AM
тАО11-03-2009 09:50 AM
We are planning updating our SAN environment to the latest firmware. We have been advised to we can do rolling updates, but must set timeout values greater than 60 seconds on the applications, and OS. We are running wndows and HPUX in our environment.
With regards to the HPUX OS, would recommend changing the timeout on the PV or both PV and LV?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 10:06 AM
тАО11-03-2009 10:06 AM
Re: PV and LV timeout values for rolling SAN Firmware update
I assume you are talking about a fibre channel disk array.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 10:13 AM
тАО11-03-2009 10:13 AM
Re: PV and LV timeout values for rolling SAN Firmware update
Intro
1. Selecting a period of low I/O activity is essential
2. checking the MPIO/native MPIO/PVlinks/Autopaths both path activity and accessibility to the array
3.For all your platforms
you should go to 60 (HP-UX/Windows standalone) or more seconds of 90-120 (HP-UX SG/MSCS clusters) seconds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 10:18 AM
тАО11-03-2009 10:18 AM
Re: PV and LV timeout values for rolling SAN Firmware update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 11:11 AM
тАО11-03-2009 11:11 AM
Re: PV and LV timeout values for rolling SAN Firmware update
http://h20272.www2.hp.com/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 11:20 AM
тАО11-03-2009 11:20 AM
Re: PV and LV timeout values for rolling SAN Firmware update
Yes, I am referring to EVA's. EVA 8100 and 8000. The HPUX servers hba's are up to date with firmware. I am just trying to figure out if I need to set just the PV timeout or both PV and LV timeouts on the servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 11:28 AM
тАО11-03-2009 11:28 AM
Re: PV and LV timeout values for rolling SAN Firmware update
pvdisplay = 30s.
So the PV timeout value should be changed to 60s
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 11:31 AM
тАО11-03-2009 11:31 AM
Re: PV and LV timeout values for rolling SAN Firmware update
Now it depends - what version of hp-ux, and multipathing software in use?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 11:32 AM
тАО11-03-2009 11:32 AM
Re: PV and LV timeout values for rolling SAN Firmware update
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00795548/c00795548.pdf
HPStorageWorksEnterpriseVirtualArray
online ├п┬м rmwareupgradebestpractices
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-03-2009 11:39 AM
тАО11-03-2009 11:39 AM
Re: PV and LV timeout values for rolling SAN Firmware update
c01815339 - HP StorageWorks Enterprise Virtual Array (EVA) - Online Firmware Upgrades May Take Longer Than Expected
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01815339
(the support people who are pressing the "GO!" button do know why they want to do offline upgrades...)