wseifert Absent Member.
Absent Member.
1934 views

Volume List incomplete in Kanaka Manager

After completing the config wizzard I found following entries in the Storage Resources - Volume List:

\\IMTESTCLUSTER1\IMGW Unable to read attribute value; Result = 163.
\\IMTESTCLUSTER1\IMHOMETEST Unable to read attribute value; Result = 163.

Both lines without AFP Volume Name and Client Access Protocol listed.

We have followed the post regarding the clustered volumes, no success. in the log we see some error(s):

NWXPLAT: m_pfnNWCCOpenConnByAddr() failed, rc = 0x00008870.

What is going wrong?

Werner
Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: Volume List incomplete in Kanaka Manager

On 30/01/2012 09:36, wseifert wrote:

> After completing the config wizzard I found following entries in the
> Storage Resources - Volume List:
>
> \\IMTESTCLUSTER1\IMGW Unable to read attribute value;
> Result = 163.
> \\IMTESTCLUSTER1\IMHOMETEST Unable to read attribute value; Result =
> 163.
>
> Both lines without AFP Volume Name and Client Access Protocol listed.
>
> We have followed the post regarding the clustered volumes, no success.
> in the log we see some error(s):
>
> NWXPLAT: m_pfnNWCCOpenConnByAddr() failed, rc = 0x00008870.
>
> What is going wrong?


Which version of OES (2 or 11)? SP? Patch level?
--
Simon
Novell/SUSE/NetIQ Knowledge Partner

------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
0 Likes
wseifert Absent Member.
Absent Member.

Re: Volume List incomplete in Kanaka Manager

OES2 SP3 / SLES10 SP4. But that is history. Today I upgraded both clusterservers to OES11 / SLES11.1. Tomorrow I wii reinstall Kanaka.
Let's see tomorrow ..

Werner
0 Likes
matthewdefoor Absent Member.
Absent Member.

Re: Volume List incomplete in Kanaka Manager

I would change the logging level of Storage Resources to Verbose in Log Management and do a rebuild of Storage Resources. Post the results pertaining to the server/volume in question.

-Matt
0 Likes
iuuuuan Absent Member.
Absent Member.

Re: Volume List incomplete in Kanaka Manager

wseifert;2171543 wrote:
After completing the config wizzard I found following entries in the Storage Resources - Volume List:

\\IMTESTCLUSTER1\IMGW Unable to read attribute value; Result = 163.
\\IMTESTCLUSTER1\IMHOMETEST Unable to read attribute value; Result = 163.

Both lines without AFP Volume Name and Client Access Protocol listed.

We have followed the post regarding the clustered volumes, no success. in the log we see some error(s):

NWXPLAT: m_pfnNWCCOpenConnByAddr() failed, rc = 0x00008870.

What is going wrong?

Werner


Hi,

I had same problem. You should check the following :

1.) Check host server of volume with ConsoleOne
If it does not show correct server add correct virtual host server - check TID 1008449

2.) Check NCS:Volumes attribute of cluster resource with ConsoleOne (on other tab)
If cluster resource does not contain NCS:Volumes attribute add it and fill it with correct volume objects

Regards,
Ivan
0 Likes
biketroll Absent Member.
Absent Member.

Re: Volume List incomplete in Kanaka Manager

Along the lines of Ivan, it looks like TID 7010304 might help address it (at least the title looks on target). Looks like a couple of other attributes are referenced -- NCS:Volumes and
NCS:NCP SERVER -- so if you're still having that issue, you might want to check that out.
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.