Chapter 8 N1 System Manager Problems

This chapter describes the most common N1 System Manager problems, their causes, and the solution for each problem. The following topics are discussed:

• N1 System Manager Services Do Not Start After Reboot or Restart

• Management Features Unavailable on Managed Servers After Rebooting

• Job IDs are Missing After Power Cycling the Management Server

• Solaris OS Management Server Unable To Start Jobs

N1 System Manager Services Do Not Start After Reboot or Restart

If you reboot the management server, or if you stop and restart the N1 System Manager, and the services do not start, you must regenerate security keys as described in Regenerating Security Keys.

Management Features Unavailable on Managed Servers After Rebooting

When the load server or load group command is used to install software on the managed server, the managed server's networktype attribute could be set to dhcp. This setting means that the server uses DHCP to get its provisioning network IP address.

If the system reboots and obtains a different IP address than the one that was used for the agentip parameter during the load command or add server command, then the following features might not work:

• The OS Monitoring content of the show server command (no OS monitoring)

• The load server update and load group update commands

• The start server command command

• The set server threshold command

• The set server refresh command

In this case, use the set server agentip command to correct the server's agent IP address. See To Modify the Agent IP for a Server in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.

Job IDs are Missing After Power Cycling the Management Server

If the N1 System Manager management server is rebooted or power cycled while jobs are running, the show jobs command will not list the jobs that were running when the management server was power cycled. Subsequent jobs will start at a higher job number, and the list of jobs produced by the show jobs command will display a gap in the job numbers. This gap can occur due to a power loss, or if the management server was manually power cycled.

To avoid this problem, wait until all jobs have completed. Stop the N1 System Manager and wait for all processes to stop before rebooting or powering off the management server.

Solaris OS Management Server Unable To Start Jobs

If IPv6 is enabled on a Solaris OS Management Server, N1 System Manager jobs will not start, and the n1sh user interface is not available. IPv6 must be disabled for N1 System Manager to function correctly. Perform the following procedure to ensure that IPv6 is disabled.

To Disable IPv6 on a Solaris OS Management Server

1. Log in to the management server as root (su - root).

2. Type ifconfig -a6 to determine whether IPv6 is enabled.

   The IPv6 status is displayed. If IPv6 is enabled, the status contains the text UP and RUNNING. For example:

   # ipconfig -a6 lo0: flags=2000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6> mtu 8252 index 1 inet6 ::1/128 eri0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2

3. Disable IPv6

   To disable IPv6, you must rename the IPv6 interface files in the /etc directory and then reboot the system as follows.

   1. Type ls /etc/hostname6.* to list the IPv6 interfaces. For example:

      # ls /etc/hostname6.* /etc/hostname6.eri0 /etc/hostname6.eri1 /etc/hostname6.eri2

   2. For each file listed in Step a, rename the file as follows:

      # mv /etc/hostname6.interface disabled./etc/hostname6.interface

      where interface is the interface used such as eri0, lo0, bge0 and so on.

4. Reboot the management server.