Environment
Situation
Resolution
Here is a list of references that you will need to change when you modify the servers IP address(es).
Only products that ship with the Enterprise version of NetWare 6.0 are taken into consideration, please contact technical support for any other product concerned including products that ship with Small Business Server (SBS).
It should be understood that a CNE6 or equivalent level of knowledge is desirable for the implementation of these changes - this TID makes no effort to detail the steps required, it's just a list of references that may require changing.
INETCFG:
Bindings and Subnet Mask
Default Route and possibly some other static network routes
Static NAT tables
DNS Resolvers
O/S FILES:
SYS:etc\hosts
SYS:etc\hostname
SYS:etc\resolv.cfg (if you didn't use INETCFG)
SYS:NI\UPDATE\DATA\PortResolverInstalled.properties
SYS:ETC\TRAPTARG.CFG (If applicable)
SYS:SYSTEM\TIMESYNC.CFG (If applicable)
AUTOEXEC.NCF:
Bindings/Mask (if you didn't use INETCFG)
Default Route
Secondary IP address(s)
FTP:
SYS:ETC\FTPSERV.CFG
SYS:ETC\FTPREST.TXT (You probably won't need to change this)
DNS/DHCP:
Delete the ranges serviced by DHCP if they can no longer be
serviced by the new IP address and no other server can service the
range. There is no edit option for DHCP in NetWare. If DHCP
has been configured for clustering check the DHCP service load and
unload scripts for references to the old server IP address.
WEB MANAGER:
SYS:webapps\WebAdmin\servers.xml (If you Didn't use DNS)
NOVELL SEARCH:
SYS:NSEARCH\SiteList.properties
APACHE:
SYS:apache\conf\adminserv.conf (There are up to 7 places that need
changing - 'listen', 'securelisten' and 'redirect') (NOTE: In
NetWare 6.5, Apache is now in SYS:\Apache2 ).
SYS:apache\nwdocs\nav.html - This is the default Apache "Welcome" page and could require changes in multiple places.
iFOLDER:
If running 2.0 Standard edit the
SYS:apache\iFolder\Server\httpd.conf (2 places - 'listen' and'securelisten')
For both 2.0 Standard and Professional edit the
SYS:apache\iFolder\Server\httpd_additions_nw.conf
If running 2.0 Standard the FIXUP.NLM needs to be run to change the
IP Address of the installed iFolder Client - see KB 10068551 for
details.
If running 2.0 Professional the iFolder Server Object needs the iFolderLDAPDNSorIP under the"Other" tab.
SYS:Apache\iFolder\DocumentRoot\html\iFolder_nav.html (If you didn't use DNS)
NetStorage - Verify that old
and new IP address are listed, with "CDBE Edit on" at the server
console at the following location:
NETSCAPE ENTERPRISE SERVER:
This procedure is detailed in
TID 1067790
WEB ACCESS:
SYS:webapps\WebAccess\WEB-INF\PortalServlet.properties (If you didn't use DNS)
NOVELL CLUSTER SERVICES:
There are no configuration files assocaited with cluster serivces. All configuration information is stored in NDS. Therefore, the modifications will need to be made through ConsoleOne.
Each node will require that
the IP address field be changed via ConsoleOne under the properties
page of the node object that resides inside the cluster
container.
Once the node IP addresses are changed, each resource associated
with an IP address change will need to be modufied. This can be
done in ConsoleOne by going to the properties page of the
respective resource under the cluster container object.
Once the node and resource IP addresses are changed, the Master IP address resource will need to be changed. This is modified on the cluster container object under the Management tab.
If there are hard-coded DNS references
you must ensure that they still resolve to the correct
address.
For the changes to take effect, the 'Cluster Down' command must be
issued and type 'ULDNCS' on each node before starting the cluster
with 'LDNCS'.
Note: if you are changing to a different subnet all cluster
resources IP address will have to be changed to be within the new
subnet. If client mappings are done using the virtual server's IP
address then the login scripts will have to be changed
accordingly.
LDAP/SSL:
ConsoleOne: The ldap server object will have to be recreated and
reassociated to the ldap group object. A new SSL KMO object will
have to be reassociated to the ldap server object.
As the names of the servers have changed you will need to recreate
the following certificates:
1. SSL CertificateIP (Regardless)
2. SSL CertificateDNS (Only if the DNS Name changes)
https://support.novell.com
NDS:
set dstace=*L
Execute a Repair Server Address from DSRepair.
Then do the normal DS health
check. dsrepair | report sync and timesync. (see knowledge base for
more details).
SLP:
If you are running a SLP DA you can remove objects from the SLP
Scope that reference services on the server to ensure this happens
instantly.
Once this is done, execute a 'SET SLP RESET = ON' on the
DA(s).
Server SET parameters (also accessible via MONITOR.NLM):
set SLP include, exclude addresses if you have changed them from default settings.
set NCP include, exclude
addresses if you have changed them from default settings.
External References (not DS):
Change any DNS records pointing to services (for example the iPrint
NDPS Manager DNS record) to point at the correct ip address.
IP-Based Restriction files on other servers (such as FTPREST.TXT
for FTP on NetWare).
Static Routes on other servers or devices pointing to the old
address.
SLP.CFG files on other servers that may have pointed to this server
by IP address.
CLIENT: directory agent list
Other servers may point to this server for Timesync information, if
that is the case you will need to change the
SYS:SYSTEM\TIMESYNC.CFG information.
NAAS:
If you are running Novell
Advanced Audit Service, see KB 10080358 for
details.
ZEN for Desktops:
On the database object, confirm the IP address or DNS name of the database object in two places:
1. "Zenworks Database†tab |"Server IP address or DNS nameâ€
2. "Jdbc driver information†tab | Database Service name.
NOTE: If you don’t have the Database Service name under the JDBC driver information tab, it means that you don’t have the ZFD4 SNAPIN correctly installed and you’ll need to download the "4.0.1 Snap-in for ConsoleOne†from download.novell.com
OTHER:
SCMD has a prefered IP address, this may need to be changed if it
is hard-coded.
NOTE: This process is not needed for NetWare 6.5. NetWare 6.5 includes a new feature known as "IP Address Management" that allows you to schedule IP Address changes in the NRM (NetWare Remote Manager). This process will also update the necessary configuration files/setting for any product that IAM is enabled for. More information about IAM is available in the online documentationNetWare 6.5 IP Address Management Administration Guide.
For NetWare 6.5 you will need to make a couple changes for eGuide and iFolder
You will need to Manually change the iFolder_ldap01 edirectory object with the changed IPAddress in the iFolderLDAPDNS or IP field
For eGuide you need to
manually change the directories.properties and the
new_data_source_dir_scheme.xml. These 2 files are listed under
/SYS/tomcat/4/webapps/eGuide/WEB-INF/properties
Additional Information
Formerly known as TID# 10067853