N1 Provisioning Server 3.1, Blades Edition, System Administration Guide

Troubleshooting Image Problems

The following table contains descriptions of troubleshooting scenarios involving images. This list is not inclusive. The message log file indicates whether your problem relates to images.

Table 7–3 Troubleshooting Image Problems


Problem	Possible Cause	Solution
While allocating the resources for a farm, the N1 Provisioning Server generates a message indicating that it cannot find the named image.	The image ID in the FML file is incorrect.	Contact http://sun.com/service/contacting/index.html for assistance. Synchronize the Control Center. Also check the images list on the CPDB by running the command `image -ls`, and ensure that this list matches what displays in the Control Center.
A farm update request failed after making a snapshot.	The server was not completely backed up and running yet when the update request was made.	When you issue a farm update request after taking a snapshot, make sure that the server is completely up and running before issuing a farm update request. Otherwise, the farm update will fail. To ensure that the server is up and running, run the command `ping server IP-address`.
Farm activation fails after image creation.	Not enough external subnets.	The farm that is automatically created by the image creation process includes an external subnet. Define a new external subnet using the command `subnet -cx -m netmask-size network-IP`.
Farm standby request failed.	Not enough space on the image server for storing the image.	Go to the directory where all images are stored and issue the command `df -k` to determine how much space is available for storing image. If the capacity is above 85 percent, add more storage space for images.

Troubleshooting the Image Server

The image server manages images. The image server can be either a stand-alone network file server (NFS) or it can run on a control plane server. See Chapter 3, Managing Software Images for details.

Gigabit Ethernet Support

If your image requires Gigabit Ethernet support for the Solaris operating environment, ensure that the appropriate drivers are loaded each time the system boots. You can initialize the list of managed interfaces by running the following commands:

devfsadm
ifconfig -a plumb
ifconfig -a | grep flags | cut -d: -f1 | grep -v lo0> /etc/opt/terraspring/managed_interfaces

Now edit the contents of /etc/opt/terraspring/managed_interfaces by commenting out any interfaces that should not be managed by N1 Provisioning Server software.

Note –

The instance assigned to any gigabit Ethernet card must always be 0. For example, ce0, skge 0, alt0.