Control Center

This section describes known issues related to the N1 Provisioning Server Control Center.

Administration Screen Time-out Issue (4849661)

In certain cases, when you navigate from the Administration screen to the Editor screen and the session times out, you might not be able to log into the Control Center.

Workaround: Close the browser, open another browser, and log in again.

If you are in the Administration screen and the session times out, when you log in again, the window might display incorrectly. If this happens, close the browser and log in again.

To vary the session time-out, modify the time-out setting in the /opt/terraspring/gw/war/WEB-INF/web.xml file. Look for the session-timeout tag. The value is specified in minutes.

Find Farm Window Displays in Full After Time-out (4849673)

If you click the Find button in the Find Farm dialog box after the Find Farm session has timed out, the Find Farm window displays in full.

Workaround: Increase the time-out value. To do so, modify the time-out setting in the web.xml file in the /opt/terraspring/gw/war/WEB-INF directory. Look for the session-timeout tag. The value is specified in minutes.

No Rollback After Farm Update Failure (4849688)

When a farm update fails, changes do not always roll back to the last good state of the farm.

Workaround: The workaround for the problem is as follows:

1. To clear the error state, contact the farm using the farm -pf farm-ID command.

2. View the farm in the farm editor.

3. From the farm editor, select the latest farm update request from the Request History panel on the left. The correct farm information will display.

4. Choose Commit from the File menu to resubmit the farm update. A newly updated request is issued.

5. Unblock the new request. The correct farm information will display in the farm editor after the request is completed.

Do Not Bookmark Login Page (4849693)

Do not bookmark any page except the welcome page.

Allow Dialog Pages to Finish Downloading Information (4849697)

In some dialog pages, for example, Select: Disk Image, the application needs to download information from the server. If you click any buttons on the page before that download is complete, a script error occurs.

Workaround: Wait until the page has finished downloading all information from the server before taking any actions.

Snapshot Button Not Disabled for New Disk Created (4849721)

When you create a new disk by flexing a server group, the snapshot button is not disabled as it should be. When you click that button, an error message appears.

Deleting Snapshots or Images From the Control Center (4856854)

When you delete snapshots and images from the Control Center, they are only marked as deleted. They are not yet deleted from the I-Fabric. Until you delete them from the I-Fabric, you will not be able to create snapshots and images with the same names as the ones marked as deleted.

To purge snapshots and images from the I-Fabric, issue the image -lR command from the control plane server to view a list of the images marked as deleted. Then issue the image -d command to delete them from the I-Fabric. See the image command man page for details.

BOM Does Not Show Unmanaged Devices (4856865)

The bill of materials (BOM) dialog box shows information about devices managed by the N1 Provisioning Server and about devices of a known type that are not managed. The BOM dialog box does not include information about unmanaged devices of an unknown type.

Graphics Not Displayed Correctly After Reload Operation (4857740)

Sometimes when you reload a current farm, the graphics in the navigation bar do not display correctly.

Workaround: Refresh the page.

Control Center Client Software Requirements (4857757)

The Control Center requires Microsoft^TM Internet Explorer version 6.0 web browser with a 128-bit security encryption.

Adding Port When Updating a Farm Does Not Switch Devices (4989531)

Initially, a device with only a single connection was requested and allocated. Later a second connection to the device was requested, but the request could not be granted because the allocated device only has one connection. No new device is allocated to fulfill this request.

Workaround 1: Always connect both physical interfaces to subnets even if you do not need the two interfaces. Connecting both interfaces guarantees that a device with two connected interfaces is allocated to the farm. The secondary interface can then be reconfigured at a later time once a purpose has been identified.

Workaround 2: When a farm update fails due to the lack of resources after connecting a secondary interface of a server, bring the farm into active state by changing the farm design back to its previous design and resubmitting a farm update request. When the farm is in active state, snapshot the device to which you would like to add a second interface. Once the snapshot is completed, update the farm by removing the original server to which you would like to add a second interface and replace the deleted server with a new server and initialize its disk from the snapshot image. Connect both physical interfaces of the new device to a subnet and submit the farm update request. A new server will be allocated to the farm with two connected interfaces.

Workaround 3: Add a second switch to the chassis that hosts the device requiring the second connection. Update the device using the shelfsync command. Then resubmit the farm update request.

Workaround 4: Instead of using the secondary interface of the server, update the farm using a virtual interface on the primary interface. This workaround will force the bandwidth of the primary interface to be shared across the eth0 and virtual interfaces.

Imported Farm Can Have Incorrect Number of Ports (4998397)

An imported farm can have appropriate types, however, the implied number of connections might be incorrect.

Workaround: When importing a farm design from a .feml file, make sure that the device types match those in the current I-Fabric. In particular, make sure that the number of ports is correct for each device. If the number of ports for a device is not correct, change the device type within the device configuration dialog box before you submit the new design.

Confusing Error Message When Trying to Unblock a Farm Request With PostgresSQL (5002047)

Rhe following message appears when trying to unblock a farm request from the Pending request page:

Operation failed... may have been caused by ifabric misconfiguration

Workaround: Run the request again. After a few tries, it will succeed.