Chapter 2 N1 Provisioning Server 3.1, Blades Edition Installation Issues

This chapter describes known issues related to installing the N1 Provisioning Server 3.1, Blades Edition product.

Installation Bugs

This section describes known issues related to N1 Provisioning Server installations.

Different Usernames and Passwords Not Allowed for Multiple Shelves and Switches (4849704)

At the initial installation of the shelves and switches, you must use a common username and password for all shelves and switches during the installation. After completion of the installation, you can modify the username and password on any shelf or switch and update the database to reflect the changes using the device command. All other discovery commands permit the use of multiple username and password combinations.

System Controller and Switch Login (4856821)

Presently, the installer utility accepts only one username and password for all chassis switches and system controllers.

Workaround: Assign the same username and password for all system controllers and chassis switches.

Segment Manager Cannot Instantiate Farm Manager (4856825)

After installing the N1 Provisioning Server software, the segment manager sometimes is unable to instantiate the Farm Manager.

Workaround: To resolve this issue, stop and restart the segment manager by executing the commands /etc/rc3.d/S97sm stop, then /etc/rc3.d/S97sm start from the control plane server.

Disk Copying Failure (4856862)

After installing the N1 Provisioning Server software, you must add properties to the file /etc/opt/terraspring/tspr.properties before activating any farms.

Workaround: Add the following lines to the /etc/opt/terraspring/tspr.properties file:

com.terraspring.stm.client.ScriptCopyImpl.pingInterval=60
com.terraspring.stm.client.ScriptCopyImpl.pingTimeout=300

System Controller Responds to Old and New IP Address (4857745)

When you change the Internet protocol (IP) address of a system controller using the command setupsc, the system controller begins to respond to the new IP address and also continues to respond to the previous IP address. If the previous IP address is in use by another device, connectivity issues to the other device can develop.

Workaround: To resolve this issue, issue the resetsc command on the offending system controller. After the system controller successfully boots, it only responds to the newly assigned IP address.

As a precaution, always issue the resetsc command after changing an IP address.

Image Subnet Mask Length for N1 Provisioning Server Installation (4891850)

The image subnet mask length for the N1 Provisioning Server installation must be 24.

During Installation Failure, Retry Does Not Accept Changed Parameters (4989031)

Whenever the installer fails during an installation, it provides an option to change the install parameters and retry installation. However, depending upon the where the installer failed, some of the changed parameters might not take effect.

Workaround: Uninstall the software, then reinstall the software.

Installation Fails with "PES did not become active in 120 seconds" Error (4951122)

At the end of installation, the N1 Provisioning Server installer verifies all the blades in the system. Occasionally, some blades may fail this verification step with the following error:

50100:test FAILED: Reason was:- PES 50100 did not become active in 120 seconds 

Workaround: When you see this message, choose option 4 in the installer menu to skip the verification step and continue. When the installation completes, run the pestest command manually to verify the failed blades.

Discovery Fails During Installation or Post-Installation Due to XML Errors (5001590)

Discovery of a shelf fails during installation or post-installation while running the discoversfb1600 command.

Workaround: Use the command setupsc on the system controller to verify the prompt and prompt generation settings in the SC of the corresponding shelf. The prompt generation string should be set to none. The prompt must have a > symbol at the end.

Farm Activation Fails with Error 51 After Completion of Fresh Installation (4998383)

After a fresh installation, farm activations fail, leaving farms in error 51 and state NEW.

Workaround: To resolve this issue, stop and restart the segment manager by executing the commands /etc/rc3.d/S97sm stop, then /etc/rc3.d/S97sm start from the control plane server.

Installation Fails Because of Network Misconfiguration (5004515)

An attempt to install the N1 Provisioning Server 3.1, Blades Edition software fails. The following message is displayed:

'/etc/init.d/bootspdns start' failed with exit status 256

Workaround: Make sure that the /etc/nsswitch.conf file includes dns in the hosts line.