Changing An Ip Addresses - Netscape MANAGEMENT SYSTEM 6.1 - ADMINISTRATOR Administrator's Manual

If you don't want end-entity interaction with a subsystem, for example, if you
4.
don't want end entities to interact with a Certificate Manager, you can remove
this port too (in addition to the HTTP port).
Save your changes.
5.
Restart CMS.
6.

Changing an IP Addresses

You can configure CMS instances to listen to specific IP addresses. For example,
you can install the Certificate Manager and Data Recovery Manager on a single
host, in separate instances, and then configure the instances so that the Certificate
Manager is served on one IP address and the Data Recovery Manager is served on
another address, if the host is configured with more than one IP address.
To configure a CMS instance to listen to specific IP addresses:
Stop the CMS instance.
1.
Go to the CMS configuration directory:
2.
<server_root>/cert-<instance_id>/config
Open the
3.
addresses:
<VS id="ee-vs" state="on"
urlhosts="<hostname>.<dopmainame>" mime="mime1"
aclids="acl1" connections="eeSSL_default">
file in a text editor. and edit the appropriate IP
server.xml
To change the administration ip address, locate this line and edit the value
of the attribute:
ip
<LS id="admin" ip="0.0.0.0" port="8200" security="on"
acceptorthreads="1" blocking="no">
To change the agent ip address, locate this line and edit the value of the
attribute:
<LS id="agent" ip="0.0.0.0" port="8100" security="on"
acceptorthreads="1" blocking="no">
To change the end-entity HTTP ip address, locate this line and edit the
value of the attribute:
ip
<LS id="ee_nonSSL" ip="0.0.0.0" port="80" security="off"
acceptorthreads="1" blocking="no">
Changing an IP Addresses
Chapter 7 Administrative Basics
ip
289