- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: FibreChannel TOV
Disk Enclosures
1753451
Members
6105
Online
108794
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
Go to solution
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-24-2008 07:46 AM
тАО06-24-2008 07:46 AM
Hi,
what's the recommended Time out value for a cache centric arrays, I was requested to set up as 60 sec, it is recommended .
If we are running under a clustered env , it is going to affect us ?
Regards,
Marc'0
what's the recommended Time out value for a cache centric arrays, I was requested to set up as 60 sec, it is recommended .
If we are running under a clustered env , it is going to affect us ?
Regards,
Marc'0
Just unplug and plug in again ....
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2008 06:25 AM
тАО06-29-2008 06:25 AM
Solution
Hi,
there are special recommendations to change the TOV especially when we have the EVA connected to the XP (e.g. EVA 8100 to XP 24000) as an external storage - for the online EVA 8100 firmware upgrade procedure
both IO_TOV and PBWT should be set to 180 seconds prior to the EVA controller firmware upgrade with the reset to the defaults after the procedure (the defaults are the following:
IO_TOV=15 adn PBWT=10 seconds.
Can you provide the cluster/application specification and the reason for the 60s IO_TOV recommendation pls?
there are special recommendations to change the TOV especially when we have the EVA connected to the XP (e.g. EVA 8100 to XP 24000) as an external storage - for the online EVA 8100 firmware upgrade procedure
both IO_TOV and PBWT should be set to 180 seconds prior to the EVA controller firmware upgrade with the reset to the defaults after the procedure (the defaults are the following:
IO_TOV=15 adn PBWT=10 seconds.
Can you provide the cluster/application specification and the reason for the 60s IO_TOV recommendation pls?
the pain is one part of the reality
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-30-2008 02:10 AM
тАО06-30-2008 02:10 AM
Re: FibreChannel TOV
Marco,
In general HP recommend that the SAN hosts uses a >SCSI< command timeout of 60 when e.g. connected to an XP. Depending on the size of the SAN environment and the configuration sometimes 120 seconds is more appropriate.
If you are running in a clustered environment this means that the cluster node will have to wait for this timeout period before it can take corrective measures. Usually this will force a path failover to the alternate path. If even that fails the cluster could decide to failover the package to the alternate clusternode.
60 seconds a normal value and is recommended in various XP Configuration guides.
hope this helps.
-Eric
In general HP recommend that the SAN hosts uses a >SCSI< command timeout of 60 when e.g. connected to an XP. Depending on the size of the SAN environment and the configuration sometimes 120 seconds is more appropriate.
If you are running in a clustered environment this means that the cluster node will have to wait for this timeout period before it can take corrective measures. Usually this will force a path failover to the alternate path. If even that fails the cluster could decide to failover the package to the alternate clusternode.
60 seconds a normal value and is recommended in various XP Configuration guides.
hope this helps.
-Eric
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