UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Knowledge Partner Knowledge Partner
Knowledge Partner
3038 views

Master IP error in iManager 2.7.7 cluster plugins

I've got a 16-node OES2 SP3 linux cluster

I've got 2 OES11 SP2 64-bit servers with the same iManager version and same plugins on them.

On the one server (not fully patched, so it doesn't have the recently released OES 11 patch), I can go to My Cluster just fine and it finds the Master Node and all is well.

On the OTHER (fully patched) OES11 SP2 server I get this error in iManager:

Failed to retrieve status information about cluster NCS1 via master IP address 10.10.251.49.

Do you want to select a cluster node (preferably the master node) to manage the cluster?

Please note that the selection will be temporary. You need to select again whenever "My Clusters" page loads.

Please use this opportunity to fix the master IP address.


I browse to ANOTHER cluster node and all is well. OF course, I Have to do this every time I use THAT iManager server.

Now the question of course is:

If there truly was a problem with the Master IP stuff, why would one server work and one would not?

Seems to me to be an iManager plugin issue???
Labels (1)
0 Likes
9 Replies
Admiral
Admiral

kjhurni wrote:

>
> I've got a 16-node OES2 SP3 linux cluster
>
> I've got 2 OES11 SP2 64-bit servers with the same iManager version and
> same plugins on them.
>
> On the one server (not fully patched, so it doesn't have the recently
> released OES 11 patch), I can go to My Cluster just fine and it finds
> the Master Node and all is well.
>
>> On the OTHER (fully patched) OES11 SP2 server I get this error in
>> iManager:
>>
>> Failed to retrieve status information about cluster NCS1 via master IP
>> address 10.10.251.49.
>>
>> Do you want to select a cluster node (preferably the master node) to
>> manage the cluster?
>>
>> Please note that the selection will be temporary. You need to select
>> again whenever "My Clusters" page loads.
>>
>> Please use this opportunity to fix the master IP address.

>
> I browse to ANOTHER cluster node and all is well. OF course, I Have to
> do this every time I use THAT iManager server.
>
> Now the question of course is:
>
> If there truly was a problem with the Master IP stuff, why would one
> server work and one would not?
>
> Seems to me to be an iManager plugin issue???
>
>


I just started seeing this for the first time as well a few days ago. Seemed
really strange. Hope someone at Novell can dupe it.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

warper2;2343581 wrote:
kjhurni wrote:

>
> I've got a 16-node OES2 SP3 linux cluster
>
> I've got 2 OES11 SP2 64-bit servers with the same iManager version and
> same plugins on them.
>
> On the one server (not fully patched, so it doesn't have the recently
> released OES 11 patch), I can go to My Cluster just fine and it finds
> the Master Node and all is well.
>
>> On the OTHER (fully patched) OES11 SP2 server I get this error in
>> iManager:
>>
>> Failed to retrieve status information about cluster NCS1 via master IP
>> address 10.10.251.49.
>>
>> Do you want to select a cluster node (preferably the master node) to
>> manage the cluster?
>>
>> Please note that the selection will be temporary. You need to select
>> again whenever "My Clusters" page loads.
>>
>> Please use this opportunity to fix the master IP address.

>
> I browse to ANOTHER cluster node and all is well. OF course, I Have to
> do this every time I use THAT iManager server.
>
> Now the question of course is:
>
> If there truly was a problem with the Master IP stuff, why would one
> server work and one would not?
>
> Seems to me to be an iManager plugin issue???
>
>


I just started seeing this for the first time as well a few days ago. Seemed
really strange. Hope someone at Novell can dupe it.


Guess I'll have to open an SR then.

Glad to see it's not just me though.
0 Likes
Absent Member.
Absent Member.

Hello,

have you tried to restart the sfcb-Daemon with
"rcsfcbd restart" on the cluster node that has the Master_IP_Reource?

Regards

Burkhard Wiegand

Novell-Admin
Debeka-Versicherungen Koblenz
0 Likes
Absent Member.
Absent Member.

I believe this is caused by the patch to fix the POODLE vulnerability.

I also believe an emergency patch with a fix to the problem you experienced has been released to the channel. Please update to the latest patch.


Best regards,

Changju


kjhurni;2343598 wrote:
Guess I'll have to open an SR then.

Glad to see it's not just me though.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

changju;2343687 wrote:
I believe this is caused by the patch to fix the POODLE vulnerability.

I also believe an emergency patch with a fix to the problem you experienced has been released to the channel. Please update to the latest patch.


Best regards,

Changju


Hi Changju,

Which patch for which OS?

Given that a fully patched (as of last week) OES11 SP2 server seems to exhibit the problem, I'm assuming it's a SLES11 SP3 patch you are referring to on the server that's running iManager?

As opposed to the SLES10 SP3/SP4 Cluster Node?

Thanks!
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

wiegandb;2343615 wrote:
Hello,

have you tried to restart the sfcb-Daemon with
"rcsfcbd restart" on the cluster node that has the Master_IP_Reource?

Regards

Burkhard Wiegand

Novell-Admin
Debeka-Versicherungen Koblenz


The cluster is OES2 SP3. I don't believe that uses the sfcb stuff and uses the older CIMOM/Wbem stuff.

And it works fine from iManager OES2 SP3 that doesn't have the newest cluster plugins, and it also works fine on the OES11 SP2 server that's not fully patched either. Thus indicating it's not a problem with the cluster nodes/master node itself.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

changju;2343687 wrote:
I believe this is caused by the patch to fix the POODLE vulnerability.

I also believe an emergency patch with a fix to the problem you experienced has been released to the channel. Please update to the latest patch.


Best regards,

Changju


The OES11 SP2 server in question (that won't connect) is fully patched. I just checked again today and there are no patches to be applied to the system.
0 Likes
Absent Member.
Absent Member.

I am sorry. The fix was ready (before the holidays), but it doesn't appear to be released (likely due to the holidays).

Please contact NTS and ask for the fix for bug 908537. I don't think I can attach the jar file here.

The fix is part of OES, "novell-wbemservices" package.

I am sorry again for the inconvenience here.

Regards,

Changju


kjhurni;2343691 wrote:
Hi Changju,

Which patch for which OS?

Given that a fully patched (as of last week) OES11 SP2 server seems to exhibit the problem, I'm assuming it's a SLES11 SP3 patch you are referring to on the server that's running iManager?

As opposed to the SLES10 SP3/SP4 Cluster Node?

Thanks!
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

changju;2343716 wrote:
I am sorry. The fix was ready (before the holidays), but it doesn't appear to be released (likely due to the holidays).

Please contact NTS and ask for the fix for bug 908537. I don't think I can attach the jar file here.

The fix is part of OES, "novell-wbemservices" package.

I am sorry again for the inconvenience here.

Regards,

Changju


Thanks Changju!

I can certainly request the patch for the defect.

No need to apologize, you've been more than helpful!

--Kevin
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.