Anonymous_User Absent Member.
Absent Member.
898 views

Slow Failover NCS 1.7/NW6.5SP2orSP3

Hi

We have a four node cluster and find that when manually migrating resources
we can see unload times of 45secs to 1 minute resulting in users losing
connections to documents on network drives and causing a lot of problems.
We think that also when a node fails the reload time might be better but
the problems of lost connections as we say below is still there.

We hear that an NSS should unload in under 5 seconds and then reload to
avoid the loss of connection?

What can we check to improve performance - are there settings at the
cluster and/or on the client. At the moment it's not really helping much as
when a user loses connection MS Word seems to be reluctant to allow the
user to save the work elsewhere and often it's a case of them rebooting
their PC and us having to try and find temp files on their PC or using
salvage on the server.

Thanx

Jay
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Slow Failover NCS 1.7/NW6.5SP2orSP3

Has this always happened since installation, or only since what change
or update?

Is it identical on all resources and nodes? Identical ever time with any
given resource?

What exact part of the migration process takes so long?

What client32 version? When you say SP2orSP3 do you mean you have mixed
SP versions in the same cluster? Any patches apart from the SPs?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Slow Failover NCS 1.7/NW6.5SP2orSP3

> Hi
>
> We have a four node cluster and find that when manually migrating

resources
> we can see unload times of 45secs to 1 minute resulting in users losing
> connections to documents on network drives and causing a lot of

problems.
> We think that also when a node fails the reload time might be better but
> the problems of lost connections as we say below is still there.
>
> We hear that an NSS should unload in under 5 seconds and then reload to
> avoid the loss of connection?
>
> What can we check to improve performance - are there settings at the
> cluster and/or on the client. At the moment it's not really helping much

as
> when a user loses connection MS Word seems to be reluctant to allow the
> user to save the work elsewhere and often it's a case of them rebooting
> their PC and us having to try and find temp files on their PC or using
> salvage on the server.
>
> Thanx
>
> Jay



Hi

By design I think I'm right in saying that a cluster resource will take
longer to migrate than failover. This is because the NUDP command in the
resource unload script will wait for each connection to signal it has
closed. (See TID10086057) You could as this says use the NUDP ODEL
statement but I think this would be unwise in a real world situation

Even under failure conditions, by default, it will take at least 8 seconds
before the cluster is aware that a resource is down before it tries to
start it on another node (cluster heartbeat tolerance).

Also be aware that Windows 2000 and XP do not support file level reconnect
like W95/98, they will reconnect the drive mappings but not the file
connections. Under Word this will manifest as the SaveAs dialog being
envoked when the user saves after a migration or failover

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.