Highlighted
Absent Member.
Absent Member.
2617 views

Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool creation

Not sure if anyone has run into this or not, but I figured I would post this for future's sake...

Our Scenario:
We have a few file server clusters in our tree. They are all up-to-date and running OES 2 SP2 Linux. In the past, we have only ever needed NCP and AFP for our clients. Recently we have come across the need to enable CIFS access to these cluster pools as well.

Something that should be simple to do turned into a long and drawn out task.

The procedure sounds pretty simple... Install and configure the CIFS service on the individual cluster nodes, go into iManager, edit the cluster's virtual pool objects, and on the protocols tab check the box to enable CIFS as an advertising protocol.

If only life were that simple... Once I completed that procedure, I offlined the cluster pool resource and attempted to bring it back online (to refresh the configuration of course). That is when I realized this was not such an easy task. The pool resource would go comatose immediately after trying to bring it back online.

The Solution:
After searching these forums and looking for TIDs, I discovered that with OES 2 SP1 Linux, a script called cifsPool.py exists to fix some issues for this exact scenario. Unfortunately, that script does NOT work for SP2. I have tested, re-tested, and triple-tested it to see if it would fix my issue - it did not.

Back at the drawing board, I created a brand new pool; enabling all 3 advertising protocols during creation. Then I did some LDAP searches against the virtual server objects for each pool, comparing the results.

Turns out that the new pool I created added 2 attributes and 1 object class to its virtual server object. These attributes were missing from my production virtual server that I am trying to CIFS enable.

So in order to fix this, go into iManager -> Directory Administration -> Modify Object. Select the virtual server object for your cluster resource. Under General -> Other, select "Object Class", edit it, and add "nfapCIFSConfigInfo" and click OK. Next, add the "nfapCIFSAttach" attribute and set it to the IP address that the virtual pool is bound to (the address you want CIFS to advertise on). Finally, add "nfapCIFSServerName" and enter the server name value from your cluster's CIFS config.

Once this procedure is done the cluster resource came back to life once I performed the online operation. Fully CIFS enabled and ready to service your users.

A "Side" Rant:
Come on now Novell... This is something that should not be that hard for you to fix. Giving out "cifsPool.py" scripts to band-aid an issue is bad enough, but not fixing the problem in the next service release is definitely not a good practice.

Another bug that I stumbled upon while testing in my lab scenario... Where the admin user cannot have a special character in its password or the schema will not extend when installing clustering services.

This bug: ERROR: "NCS install failed to extend schema."

Guess what? This bug was last modified 12/24/2008, in the original OES 2 release. Do you think it has been fixed to date? Of course not! Come on guys... If you are simply passing the GUI data to back-end scripts how hard is it to wrap the admin password in single ticks to allow special characters?

Sorry - my rant for the day... Hope someone finds this useful!
Labels (1)
0 Likes
6 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool crea

I hate to ask but did you open an SR? Unfortunately that'll probably be the only way to confirm that the fix did or did not make it into the channel properly (not for your side rant). Novell doesn't monitor these forums officially so sometimes things get posted here and Novell isn't aware of it. Although I will try to let someone know about your problem and maybe contact you, but I don't guarantee anything.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool crea

No I did not... I was not about to pay lots of money for finding a fix myself, thus my forum post. 🙂
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool creation

tjpatter wrote:

>
> No I did not... I was not about to pay lots of money for finding a fix
> myself, thus my forum post. 🙂
>
>


I feel your pain, especially with the character issue. I have complained
about that all the way back to OES2 and before it shipped. They have said
multiple times it will get fixed.

Great write up there. I was stuck with that one as well. It was a fight to
get it to work.

Thanks for posting
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool crea

tjpatter;2020487 wrote:
No I did not... I was not about to pay lots of money for finding a fix myself, thus my forum post. 🙂

When a call is shown to be due to an unpublished Novell code bug, you don't get charged for the call (or rather, the CC charge gets refunded on closure).

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Highlighted
Micro Focus Contributor
Micro Focus Contributor

Re: Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool crea

See TID 7005192
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Enabling CIFS on OES 2 SP2 Linux cluster AFTER pool crea

This issue had already been found and a fix for the issue is getting released with the OES2SP2 patch for November.The same fix has also been made available with OES2SP3.
Hope this information helps.
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.