ABach Respected Contributor.
Respected Contributor.
1855 views

New OES2 SP3 cluster on new hw setup issues

I'm building a brand new SAN (IBM DS family storage) with QLogic HBA's and are using the RDAC and qlaxxx storage drivers. So far so good. (after a bunch of fiddling).

Carved up the SAN and made the LUNS and see them in nssmu.

Problem is when we go to set up the NCS. We have a 20 mb LUN for the SBD but cannot Initialize it (nssmu only puts down a 16 kb partition), nor mark is Shareable for Clustering.

Now we are dead stopped!

Any ideas or help on how to move this cluster ahead so we can get it into production?
Thanks!
Andreas
Labels (2)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: New OES2 SP3 cluster on new hw setup issues

Hi.

On 06.04.2011 00:06, abach wrote:
>
> I'm building a brand new SAN (IBM DS family storage) with QLogic HBA's
> and are using the RDAC and qlaxxx storage drivers. So far so good.
> (after a bunch of fiddling).
>
> Carved up the SAN and made the LUNS and see them in nssmu.
>
> Problem is when we go to set up the NCS. We have a 20 mb LUN for the
> SBD but cannot


Define "cannot". Error message? BTW, 20MB *might* just be too small.

> Initialize it (nssmu only puts down a 16 kb partition),


Sounds like completely normal behaviour, that's what "initialize" does,
so this sounds like it worked fine.

> nor mark is Shareable for Clustering.


Again, error message?

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
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
ABach Respected Contributor.
Respected Contributor.

Re: New OES2 SP3 cluster on new hw setup issues

Thanks for the input Massimo.
When looking at Devices, the drives read as follows before and after pressing the Init (F3) button in Nssmu:
-- Before--
Capacity: 300 Gb
Partitioned space: 0
Unpartitioned space: 300 Gb

-- After --
Capacity: 300 Gb
Partitioned space: 16 Kb
Unpartitioned space: 299.99 Gb

When I press Share (F6), nothing happens and the shareable for clustering doesn't change. No error messages visible in NSSMU.
I also tried F3 and F6 in iManager.

THEN, if I use the SUSE partitioner (forget it's official name), any drive I did INIT on now says something like: "Partioner cannot work with drive /dev/sdf, you can use it if you like, but I cannot touch it"

When we go to install NCS it doesn't like the SBD since it's not yet shared.
Also, 10-20 Mb for SBD was in the docs. 🙂

Andreas
0 Likes
Knowledge Partner
Knowledge Partner

Re: New OES2 SP3 cluster on new hw setup issues

On 06.04.2011 16:06, abach wrote:
>
> Thanks for the input Massimo.
> When looking at Devices, the drives read as follows before and after
> pressing the Init (F3) button in Nssmu:
> -- Before--
> Capacity: 300 Gb
> Partitioned space: 0
> Unpartitioned space: 300 Gb
>
> -- After --
> Capacity: 300 Gb
> Partitioned space: 16 Kb
> Unpartitioned space: 299.99 Gb


So far, so normal.

> When I press Share (F6), nothing happens and the shareable for
> clustering doesn't change.


*That* however isn't normal. Are you using NSSMU from the server
console, or via SSH/putty? There are some oddities with the function
keys when using it remote.

> No error messages visible in NSSMU.
> I also tried F3 and F6 in iManager.


And no error in iManager either?

> THEN, if I use the SUSE partitioner (forget it's official name), any
> drive I did INIT on now says something like: "Partioner cannot work with
> drive /dev/sdf, you can use it if you like, but I cannot touch it"


That's correct. What do you try to do? You're not supposed to touch NSS
drives with partitioner.

> When we go to install NCS it doesn't like the SBD since it's not yet
> shared.


You mean it doesn't like the device to *create* the SBD to start with.
Yes, the problem is that you're unable to set the device shareable.

> Also, 10-20 Mb for SBD was in the docs. 🙂


That's the size of the partition it creates (and which you have no
influence on), not the supposed size of the underlying device (which in
your case is way too huge BTW. I would strongly suggest to create a
seperate LUN exclusively used for the SBD and nothing else. The smallest
possible LUN +100MB should do). Do not share data and SBD partition on
the same device (LUN). But the core issue is your inability to set the
device shareable. You need to conncentrate on that. Check
/var/log/messages to start.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
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
ABach Respected Contributor.
Respected Contributor.

Re: New OES2 SP3 cluster on new hw setup issues

It was NSSMU on server we tried. But when we rebooted everything in sight it fixed itself and we were able to proceed. (phew!)
We will NOT be using SUSE partitioner any more.
The SBD partition was created successfully (9 mb is what I believe it made for itself from the 20 Mb separate LUN we gave it) so we have been able to create all the cluster resources and move forward.
Thanks for your help!
0 Likes
warper2 Outstanding Contributor.
Outstanding Contributor.

Re: New OES2 SP3 cluster on new hw setup issues

abach wrote:

>
> It was NSSMU on server we tried. But when we rebooted everything in
> sight it fixed itself and we were able to proceed. (phew!)
> We will NOT be using SUSE partitioner any more.
> The SBD partition was created successfully (9 mb is what I believe it
> made for itself from the 20 Mb separate LUN we gave it) so we have been
> able to create all the cluster resources and move forward.
> Thanks for your help!
>
>


Were the servers running when you configured the san? If they were it is
always recommended to reboot the servers. I have seen this myself adding new
luns to the san. That is the only thing that comes to mind here.

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.