DCE Installation, Configuration, and Management Guide
Managing a DCE Cell
HP NonStop DCE Installation, Configuration, and Management Guide—429552-005
7-9
DCE Serviceability Messages
4. In the file /opt/dcelocal.<hostname>/etc/security/pe_site, replace
the current IP address with the new IP address.
5. Stop the DCE host.
6. Export the environment variable BIND_PE_SITE to 1.
7. Restart the DCE host. During the restart, the error rpc_ns_binding_export is
reported (this error will be fixed later).
8. Attempt to login to the cell using dce_login. This login attempt will fail to consult
CDSD because the BIND_PE_SITE environment variable is set.
9. Unset the BIND_PE_SITE environment variable.
10. Try dce_login again. If this login attempt is successful, CDSD is working
properly.
11. Through cdsp, enter a show cell command. This command displays fields
similar to the following, showing the IP address for the tower:
Replica Type = Master
Tower = ncacn_ip_tcp:<ip address>[]
Tower = ncadg_ip_udp:<ip address>[]
The display shows the current (unchanged) IP address because the update has
not yet taken affect.
12. Through cdsp, enter this command:
create clearinghouse /.:/<clearinghouse name>
13. Enter a show cell command and, again, check the Tower entry. It should now
contain the new IP address, indicating that the update has completed.
DCE Serviceability Messages
Problems encountered by NonStop DCE 1.1 components are recorded with a standard
serviceability mechanism, which is described in the introduction of the OSF DCE
Problem Determination Guide. This mechanism can also be used by DCE application
programs. For more information, see the dce_svc_intro(3) reference page online.
Serviceability messages can be recorded in many ways under user control, as
described in the section on routing serviceability messages in the OSF DCE
Administration Guide Core Components. The file /dce/local/var/svc/routing is
the default location for controlling message routing.
The severity levels for serviceability messages are listed in Table 7-1.