Sun Management Center Change Manager 1.0 Administration Guide

- Previous: Panic: unable to mount file systems Message Appears While Booting From the Network
- Next: Appendix C Security (Reference)

## Interactive Installation Program Launched When Files For Non-Existent Managed Hosts Not Cleaned Up (4721489)

Description:

  When the last reference to a managed host is removed from the Change Manager topology, the custom JumpStart data is not deleted.

  The `/etc/bootparams` file still contains entries corresponding to the managed hosts.

  The `/var/opt/ichange/jsdata/hostname` directories still contain boot environment information and custom JumpStart configuration files.

  Extraneous `/etc/bootparams` entries for a managed host can cause problems. For example, if more than one Change Manager server has the same managed host registered, each server answers the call from that managed host. This situation produces excess traffic and unknown results on the managed host.

Solution:

  Manually clean up the following files on the Change Manager server:

  - Find a Solaris miniroot, which might be located in the Change Manager repository under `/var/opt/ichange/root`. Change directory to the Tools subdirectory, for example, `/var/opt/ichange/root/s9.miniroot/Solaris_9/Tools`. Then, as superuser, type:

        # ./rm_install_client hostname

  - Delete the host-specific directories from the `/var/opt/ichange/jsdata` directory.

- Previous: Panic: unable to mount file systems Message Appears While Booting From the Network
- Next: Appendix C Security (Reference)

- © 2010, Oracle Corporation and/or its affiliates