Re: Cluster SAN disk timeout value
- From: "Edwin vMierlo [MVP]" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Jun 2007 09:11:32 +0100
There are a couple of things to consider here
First of all your storage vendor will determine what value this should be
for your configuration. So if your storage admin is giving you that value,
than yes, it should be 60.
Second, in Windows 2003-RTM (no SP), if you have configured 60 second time
out prior to installing cluster service, then yes, your storage admin is
right, the non-Service-Pack installer of cluster service will change the
value back to 20 (hex 0x14) and will not retain a previous configured value,
this is a bug in W2K3-RTM and was corrected in SP1. So, in short, it is wise
to install SP1 (or SP2) prior to clustering. Further more; develop a best
practice checklist, which you can check after fully installing your cluster,
and ensure this value is on your checklist to be checked.
Thirdly, certain installers of HBA-drivers will be "OEM installers" and are
capable of setting this value while installing or upgrading your drivers. In
regards to EMC storage, you should download the EMC driver package to ensure
you have the correct (approved) driver. However a driver installer will
change it to the right value, so you just need to check afterwards.
A checklist as mentioned above should cover cluster functionality and custom
settings for your cluster, and should be checked everytime you make a change
to your cluster which can influence functionality and or settings.
Obviously, hotfixes, patches, service packs and driver upgrades all fall
into that catagory of being able to influence functionality or capable of
changing settings, so when any of those are installed on your cluster, you
should run through your checklist.
HTH,
Edwin.
"Bazooka-Joe" <bazooka-joe@xxxxxxxxxxx> wrote in message
news:1183056233.063096.325750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
SAN admins in my company are telling me that to do online firmware
updates of the SAN all the nodes connected have to have the following
registry value:
HKLM\System\CurrentControlSet\Services\Disk\TimeOutValue = 60
By default all systems have a value of 60. According our SAN admin
when you install clustering, it changes the nodes of the cluster to a
value of 20. There asking about changing it back to 60. What would
that do to me? Any negative impacts? Should I change it back when
the firmware code update is done?
Thoughts? Opinions? Couldn't find anything in TechNet specificall
about this except a KB article relating to EMC storage, non-clustered,
and NT4/2000 (KB #248191).
Thanks in Advance.
:Bazooka-Joe
.
- References:
- Cluster SAN disk timeout value
- From: Bazooka-Joe
- Cluster SAN disk timeout value
- Prev by Date: Re: Using diskpart on clustered file server with shadow copy enabled
- Next by Date: Re: Cluster server fails over when replistor service is stopped
- Previous by thread: Re: Cluster SAN disk timeout value
- Next by thread: Re: view cluster log
- Index(es):
Relevant Pages
|
