Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
744 views

Re: change NCP SERVER NAME

So now that I have seen your other half of your thread...

As you say, you cannot create a Linux host name with an Underscore
within it. And thay applied to an OES box as much as any Linux box.

You have a cluster with virtual servers that corespond to different
resources, and you want to move that volume/resource to a VMWare guest
(keeping the same LUN) but you also want to maintain the same Virtual
Server host name.

There are two solutions to this, one is to ensure that your clients
use DNS as the highest priority on their NW Client name resolution and
then set up your DNS with A-Records for the new Servername with a
Cname of the old resource virtual server name. This will resolve UNC
paths and keep them working.

If you want to create a virtual server that has the original name, do
what I saidn create the new server in paralel, move the volume, and
bring it into eDirectory (you will need to remove the shared volume
flag) and then create a ONE NODE cluster - create a simple IP resource
that has the old Virtual server name and the old IP number.

HTH

T
Labels (2)
0 Likes
1 Reply
Absent Member.
Absent Member.

Ok this should be an option.
But the general question why editing the ncpserv.conf file does not work
is still open.

The problem of usage underscores in ncp server names is part of all OES2
docs :

http://www.novell.com/documentation/oes2/file_ncp_lx/?page=/documentation/oes2/file_ncp_lx/data/bc2k13y.html



On 20.06.2011 13:02, TimScotland (NKP) wrote:
> So now that I have seen your other half of your thread...
>
> As you say, you cannot create a Linux host name with an Underscore
> within it. And thay applied to an OES box as much as any Linux box.
>
> You have a cluster with virtual servers that corespond to different
> resources, and you want to move that volume/resource to a VMWare guest
> (keeping the same LUN) but you also want to maintain the same Virtual
> Server host name.
>
> There are two solutions to this, one is to ensure that your clients
> use DNS as the highest priority on their NW Client name resolution and
> then set up your DNS with A-Records for the new Servername with a
> Cname of the old resource virtual server name. This will resolve UNC
> paths and keep them working.
>
> If you want to create a virtual server that has the original name, do
> what I saidn create the new server in paralel, move the volume, and
> bring it into eDirectory (you will need to remove the shared volume
> flag) and then create a ONE NODE cluster - create a simple IP resource
> that has the old Virtual server name and the old IP number.
>
> HTH
>
> T


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.