Top
ServerView Resource Orchestrator V3.4.0 Messages
FUJITSU Software

3.1.1 411XX Series

This section explains the 411XX message series.

41105

FJSVrcx:WARNING:41105:failed to get the server information from server_name

Description

Server configuration information and status have not been obtained from the server_name.
One of the following may apply to the server_name.

  1. There is a problem with the network environment between the admin server and the server_name

  2. The server_name is not powered on

  3. The agent service for the server_name has stopped

  4. The server_name, or the server management unit has failed (Related errors are displayed)

  5. The load on the CPU of the server_name is high and information cannot be obtained from the server

  6. When the server_name is "VMwareESXi" and information cannot be obtained from the required software

The name of the server is displayed for server_name.

Corrective Action

For a.

Check the network environment.

For b.

Power on the server server_name.

For c.

When the server_name is a managed server, start the agent service.

For details, refer to the following:

  • For Virtual Edition, refer to "5.2 rcxadm agtctl" in the "Reference Guide (Command) VE".

  • For Cloud Edition, refer to "5.3 rcxadm agtctl" in the "Reference Guide (Command/XML) CE".

In case of d

Recover the failed server or server management unit.

In case of e

After the load on the CPU of the server has become lower, update and obtain new information.
To update the information, right-click the server on the ROR console server resource tree and select [Update] from the displayed menu. It takes several tens of seconds to be updated. Check in the resource details that information for the server has changed.

For f.

Manage the target server using required software and ServerView Operations Manager.

When the cause is not one of the above, collect troubleshooting information, and contact Fujitsu technical staff.


41106

FJSVrcx:WARNING:41106:server:operation failed during switchover, retrying using another Admin LAN interface. detail=detail

Description

As the process operation failed on the server server, the admin LAN interface will be switched to the spare interface and the operation will be executed again.

One of the following is displayed for operation:

  • HBA address rename

  • image restore

Corrective Action

Check the status of the admin LAN and perform corrective action as necessary.

  • When operation is "image restore"

    When not using backup and restore, no corrective action is necessary.


41110

FJSVrcx:WARNING:41110:invalid format for license file filename

Description

The format of the license file filename is incorrect.

Corrective Action

As there is a chance that installation was not completed successfully, perform uninstallation and then perform installation again.
However, if there is no problem with the range of functions that can be used, corrective action is not necessary.


41111

FJSVrcx:WARNING:41111:invalid feature found in license file filename

Description

There is an invalid function described in the license file filename.

Corrective Action

The invalid function cannot be read. No action is necessary.


41115

FJSVrcx:WARNING:41115:server_name:shutdown of the server failed. forced poweroff started

Description

Power off was performed for the managed server server_name, but power off could not be confirmed. The server will be forcibly powered off.
This message may be displayed during server switchover (Auto-recovery or manual switching), failback or when reconfiguring hardware properties after hardware replacement.

The name of the managed server is displayed for server_name.

Corrective Action

The relevant server will undergo forced power off. No action is necessary.


41116

FJSVrcx:WARNING:41116:server_name:rebooting of the server failed. forced reboot started

Description

The managed server server_name was rebooted, but rebooting could not be confirmed. The managed server will undergo forced reboot.
This message may be displayed during Auto-recovery, manual switching or failback.

The name of the managed server is displayed for server_name.

Corrective Action

The relevant server will undergo forced reboot. No action is necessary.


41120

FJSVrcx:WARNING:41120:different type detected. registered=obj1 detected=obj2

Description

Either of the following was detected.

  • There is a server or LAN switch with differing type information in the same slot of the same chassis as a registered server or LAN switch.

  • For the type information, the specified obj1 and obj2 acquired from the network device are not the same.

One of the following is displayed for type:

  • IP address

  • MAC address

  • Product

  • LAN switch model

  • blade type

  • Operation mode in vfabname

The registered value is displayed for obj1.
The newly detected value is displayed for obj2.
The name of the virtual fabric is displayed for vfabname.

Corrective Action

Take corrective action for the content displayed for type.

  • When type is "IP address"

    The IP address of the NIC being used for the admin LAN may have been changed.

    Check the IP address settings of the managed server and change the IP address if necessary.

    For details, refer to the following:

    • For Virtual Edition, refer to "8.1 Changing Admin IP Addresses" in the "User's Guide VE".

    • For Cloud Edition, refer to "6.1 Changing Admin IP Addresses" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  • When type is "MAC address" or "Product"

    When a server has been replaced, or server registration or reconfiguration of hardware properties has been performed, a MAC address that differs from the actual MAC address may have been entered.

    When using the PRIMEQUEST 2000 series, operations from MMBs or addition or deletion of SBs or IOUs using Dynamic Reconfiguration may have been performed.

    Check the status of the server and reconfigure the hardware properties again if necessary.

    However, when VIOM coordination or ISM coordination has been configured, reconfiguration of hardware properties is performed automatically and no action is necessary.

    If this message is displayed when switching over a server using the profile switchover method, no action is necessary.

    For details, refer to the following:

    • For Virtual Edition, refer to "6.2.2 Reconfiguration of Hardware Properties" and "6.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide VE".

    • For Cloud Edition, refer to "9.2.2 Reconfiguration of Hardware Properties" and "9.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide CE".

    With PRIMERGY BX900 chassis, there are cases where this message is displayed directly after a server blade is inserted. This occurs because a short time is necessary for the management blade to recognize the admin LAN NIC, so no action is required.

  • When type is "LAN switch model"

    The LAN switch may have been replaced with a different model.
    To continue using the new model, delete the registered LAN switch and then register the new one.

  • When type is "blade type"

    When multi-slot servers have been registered, a server blade or storage blade may have been mounted in the slave slot. Or, when a server has been registered in the slave slot, a multi-slot server may have been mounted.

    To continue using the new server, delete the registered server blade.

  • When type is "Operation mode in vfabname"

    Review the operational mode of the virtual fabric described in vfabname. If necessary, modify the operational mode of the virtual fabric when modifying the network devices.

To suppress this message when performing maintenance work, place the device into maintenance mode.
Note that this message cannot be suppressed for "LAN switch model" or "blade type".


41121

FJSVrcx:WARNING:41121:no type detected

Description

type indicates either of the following:

  • When type is "NIC for admin LAN"

    type information was not detected for a server blade.

  • When type is "VFAB(ID=vfabid)"

    A VFAB could not be detected from the Ethernet Fabric switch.

    In vfabid, "default" or VFAB ID (1-3000) is displayed.

Corrective Action

Take corrective action depending on the type displayed in type.

  • When type is "NIC for admin LAN"

    There is a chance that the server blade has no NIC to use for the admin LAN or the management blade cannot correctly recognize the server blade's NIC.
    Check the admin window of the management blade to see if the server blade's NIC is being recognized correctly.
    If it is not being recognized correctly, remount the server blade and power it on.

    If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.

  • When type is "VFAB(ID=vfabid)"

    The virtual fabric registered with Resource Orchestrator is not defined in the Ethernet Fabric switch.
    If necessary, define the virtual fabric for the Ethernet Fabric switch.


41122

FJSVrcx:WARNING:41122:data collection could not complete within the polling interval. (detail)

Description

Data collection could not be completed within the polling interval.
Detailed information is displayed for detail.

Corrective Action

Either change the polling interval to one longer than the current interval, or reduce the number of devices that are the target of data collection.


41123

FJSVrcx:WARNING:41123:obj:function was aborted. detail=detail

Description

The processing of the function for obj has not been performed.
One of the following is displayed for obj:

  • The HBA WWPN value configured in the [WWN Settings]

  • The L-Server name

The reason the processing of function was not performed is displayed for detail.

  • When detail is "obj is busy"

    function could not be performed as obj was performing another operation.

  • When detail is "failed to get wwpn's hostrsp_no value, set default value 0"

    As the host response value configured using ETERNUS for HBA of the switchover source or failback source server could not be acquired, the takeover operation of the host response value stops. Configure 0(Default) as the host response value.

  • When "message notifying of disconnect" is displayed for function.

    A message was not sent to the user even though an action was performed targeting the L-Server when it was infected with malware.

  • When "email notifying of disconnect" is displayed for function.

    An e-mail was not sent to the tenant administrator even though an action was performed targeting the L-Server when it was infected with malware.

Corrective Action

  • When function is "auto-recovery", Auto-Recovery has not been performed.
    Perform server switchover manually as necessary.

  • When function is "using own hostrsp_no", the host response value was not taken over during server switchback or failback operations.
    As 0(Default) is configured as the host response value configured in ETERNUS that can be used for the HBA of the switchover destination or failback destination server, reconfigure it when necessary.

  • When "message notifying of disconnect" is displayed for function.

    Processing of a VDI management server remote command failed. There are the following possibilities:

    • There is no connection information configured for the VDI management server, or there is a mistake in the connection information

    • The VDI management server is not operating correctly

    • The network settings of the VDI management server are incorrect

    Check the connection information, operating status, and network settings of the VDI management server.

  • When "email notifying of disconnect" is displayed for function.

    Processing of an SMTP server remote command failed.
    Check the connection information, operating status, and network settings of the SMTP server.

    When the cause is not one of the above, collect troubleshooting information, and contact Fujitsu technical staff.

When the cause is not one of the above, collect troubleshooting information, and contact Fujitsu technical staff.


41126

FJSVrcx:WARNING:41126:obj:spare server contains setting

Description

The setting for the spare server has been configured.
The name of the spare server is displayed for obj.
One of the following is displayed for setting:

  • HBA address rename

  • VIOM server profile

  • agent

Corrective Action

If an unexpected server has been configured for the spare server, release the settings of the spare server.

41127

FJSVrcx:WARNING:41127:vmhost saving of vm guest(s) configuration failed. code=code, message=message

Description

Saving of VM guest configurations failed in the VM Host displayed for vmhost.

Corrective Action

Check a displayed message and remove the cause of an error.
After removing the cause of an error, please save the vm guest(s) configuration.

[OVM for SPARC]
Check following items, and, execute the "Recovery Procedure".

  • Check if the number of configurations saved on the service processor have reached the maximum.

    If it has, remove any unnecessary configurations to secure availability.

  • Check if a configuration named "config_tmp" exists in configurations saved on the service processor.

    If it does, delete "config_tmp".

  • Check if the state of "factory-default" saved on the service processor is [current] or [next poweron].

    If it is, set the configuration state of other configuration information to [current] or [next poweron].

  • Check if a single quotation exists in name of configuration information saved on the service processor.

    If it does, delete the configuration information including the single quotation.

  • Check if Vm Host is powered on.

  • Check if service of ldmd is online.

  • Check if communication with the VM Host is possible.

Recovery Procedure

On the host where saving of VM guest configurations failed, execute the following steps.

  1. Set the value in the definition file (sparc_vm.rcxprop) to "false" to disable the function for saving VM guest configurations automatically.

  2. Execute the following command to create new configuration.

    # ldm add-spconfig config_name <RETURN>

    Specify an arbitrary configuration information name for config_name.

  3. Execute the following command to remove unnecessary configurations.

    # ldm remove-spconfig config_name <RETURN>