dbgallo1 Absent Member.
Absent Member.
868 views

Slow Cluster Migrations OES2015SP1

Sitrep. Upgraded cluster to OES2015SP1, mostly NSS32 drives, san attached. We are currently transitioning from NCP to CIFS based auth for our shares.

Since the upgrade, volumes with large amount of connections will go comatose instead of migrating. The cifs log shows a message of
"ERROR: VERB: SMB2_TreeConnect: No Share exists with name: $VOLNAME$" , this is listed as one of the nuisance messages in
https://www.novell.com/support/kb/doc.php?id=7017883 but seems related to this....

Once the volumes go comatose, you still need to remove the secondary IP address to migrate the volume.


there used to be nssstart.cfg configuration options for tearing down connections quickly it was /Dirtysomethingsomething I think, but I can't fnd it?
Can someone point me to these switches?


Thanks in advance!
Labels (2)
0 Likes
2 Replies
AutomaticReply Absent Member.
Absent Member.

Re: Slow Cluster Migrations OES2015SP1

dbgallo,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.
https://www.partnernetprogram.com/partnerfinder/find.html

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.microfocus.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team
http://forums.microfocus.com



0 Likes
Knowledge Partner
Knowledge Partner

Re: Slow Cluster Migrations OES2015SP1

Am 25.09.2017 um 16:14 schrieb dbgallo:
>
> Sitrep. Upgraded cluster to OES2015SP1, mostly NSS32 drives, san
> attached. We are currently transitioning from NCP to CIFS based auth for
> our shares.
>
> Since the upgrade, volumes with large amount of connections will go
> comatose instead of migrating. The cifs log shows a message of
> "ERROR: VERB: SMB2_TreeConnect: No Share exists with name: $VOLNAME$" ,
> this is listed as one of the nuisance messages in
> https://www.novell.com/support/kb/doc.php?id=7017883 but seems related
> to this....
>
> Once the volumes go comatose, you still need to remove the secondary IP
> address to migrate the volume.
>
>
> there used to be nssstart.cfg configuration options for tearing down
> connections quickly it was /Dirtysomethingsomething I think, but I can't
> fnd it?
> Can someone point me to these switches?


My guess is that your unload script hangs at ncpcon unbind command,
which is a known issue. All the rest are likely follow-up problems. Open
a SR if you can, there is a ftf available.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
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.