Identifying Problems

Gathering the following information might help you to identify the cause of a problem more easily:

• Identify the exact version numbers of the operating system and N1 Provisioning Server software.

  For information about software requirements, see Chapter 2, Hardware and Software Requirements in N1 Provisioning Server 3.1, Blades Edition, Installation Guide.

• Check whether any patches have been applied. If so, specify product and operating system patch numbers.

  For information about patch requirements, see Installing Required Patches in N1 Provisioning Server 3.1, Blades Edition, Installation Guide.

• Identify the system resources, such as memory, disk space , and swap space.

  For information about configuration requirements, see Chapter 2, Hardware and Software Requirements in N1 Provisioning Server 3.1, Blades Edition, Installation Guide.

• Verify that the appropriate services are running on the N1 Provisioning Server system.

  The expected N1–related services are as follows:

  • Monitoring protocol ports

  • https/ssl/http

  • Name server (named)

  • DHCP

  • SNMP

  • Oracle listener

  • NFS

  • tftp

  • Syslog

  • RPC

  The following services can be disabled without affecting functionality:

  • telnetd

  • r-tools

• For information about installation failures, check the messages in the installation log file /var/opt/terraspring/install/run/install.log.

• If a farm fails to activate or update, check the messages in the debug log file on the Provisioning Server machine /var/adm/tspr.debug.

• If a problem occurs during daily operations, check the messages in the following log files:

  • Monitoring log file /var/opt/terraspring/mon.log located on the provisioning server machine

  • Sun Java System Application Server log file /opt/terraspring/sunone/domain_gw/server_gw/logs located on the provisioning server machine

  • Monitoring agent log file /opt/terraspring/log/tspr.log located on a provisioned server