Top
ServerView Resource Orchestrator V3.1.0 Messages
ServerView

4.5.2 655XX Series

This section explains the 655XX message series.

65509

65509: An unrecoverable error occurred.

Description

An I/O error has occurred, or command execution failed.

Corrective Action

Check that there is enough free disk space on the server used for the HBA address rename setup service, and the network is correctly connected.
After checking the amount of free disk space and the network connection, perform the operation again.
If the same error occurs again, collect troubleshooting information and contact Fujitsu technical staff.


65510

65510: Failed in registration due to internal contradiction.

Description

An I/O error has occurred, or command execution failed.

Corrective Action

Check that there is enough free disk space on the server used for the HBA address rename setup service, and the network is correctly connected.
After checking the amount of free disk space and the network connection, perform the operation again.
If the same error occurs again, collect troubleshooting information and contact Fujitsu technical staff.


65516

65516: Failed to show help due to failure of starting web browser.

Description

The web browser for displaying HELP has not been started.

Corrective Action

Perform setting of the web browser.
Start Internet Explorer, select [Tools]-[Internet Options] then select the [Programs] tab and click <Make default>.
After checking the amount of free disk space and the network connection, perform the operation again.
If the same error occurs again, collect troubleshooting information and contact Fujitsu technical staff.


65529

65529:establishing connection with admin server failed
FJSVrcx:ERROR:65529:establishing connection with admin server failed

Description

This message is displayed in the following situations:

  1. When connection to the admin server fails

    There are the following possibilities:

    • The admin server has stopped

    • The manager on the admin server has stopped

    • Another user has deleted the logged in user

    • Cluster switching has occurred on an admin server

    If this message is displayed after settings are made or operations performed there is a chance that the settings were not reflected or the operations failed.

  2. When a user logged in using another window or tab (the same process) of the same web browser on the same admin server logs out

Corrective Action

For a.

Check the following, resolve the problem, and log in again.
When cluster switching has occurred, wait until the manager starts on the standby side, and log in again.
If this message is displayed after settings are made or operations performed, log in again and then perform the settings or operation again.
When logging in to the same process again, login is performed automatically and the login window will not be displayed.

  • When the manager is stopped, start the manager.

    Startup status of the manager can be checked using the following methods.

    [Windows Manager]
    Open "Services" from "Administrative Tools" on the Control Panel, and check that the status of the "Manager Services" explained in "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" is "Started" on the [Services] window.

    [Linux Manager]
    Use the service command, and check the startup status of the services listed under "Manager Services" in "2.1 Starting and Stopping the Manager" in the "Operation Guide VE".

  • Check if there is a problem with the network environment between the server used for the HBA address rename setup service and the admin server.

    If a cable is disconnected from the LAN connector, connect it.

  • Check with an administrator of Resource Orchestrator if the user who was logged in was a registered user.
    If a user was not registered, request the administrator to take corrective action.

For b.

Log in again. Login will be performed automatically and the login window will not be displayed.


65530

65530:Failed to start services.

Description

Starting of services failed because ServerView Deployment Manager, other DHCP services, or PXE services are installed, or a memory shortage occurred.
The service has not been started.

Corrective Action

[Windows Manager]
Open "Event Viewer" from "Administrative Tools" on the Control Panel to check if "Message number 61506" is displayed on the event log of displayed window, and then take the following corrective actions:

  • When "Message number 61506" is displayed

    Uninstall ServerView Deployment Manager, other DHCP services, and PXE services, and then perform the operation again.

  • When "Message number 61506" is not displayed

    Exit open applications that are not being used or increase the amount of memory, and then perform the operation again.

[Linux Manager]
Check whether "Message number 61506" is displayed in the system log and then take the following corrective actions:

  • When "Message number 61506" is displayed

    Uninstall ServerView Deployment Manager, other DHCP services, and PXE services, and then perform the operation again.

  • When "Message number 61506" is not displayed

    Exit open applications that are not being used or increase the amount of memory, and then perform the operation again.

If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.


65531

FJSVrcx:ERROR:65531:obj: Two or more partition servers were detected on the partition chassis.

Description

There are two or more partition servers on the chassis.

Corrective Action

After reducing the number of servers on the chassis, take the corrective action again.


65532

FJSVrcx:ERROR:65532:spare_server_name: The spare server should have the same WWPN for the target CA as the primary server, but a different AffinityGroup.

Description

The WWPN value of the target CA configured in spare server should be the same value as that of the primary server, and the value of AffinityGroup should be different from that of the primary server.

Corrective Action

After modifying the value of the target CA configured on the spare server and the AffinityGroup, take the corrective action again.