This section explains the 411XX message series.
[Description]
Server configuration information and status have not been obtained from the server_name.
One of the following may apply to the server_name.
There is a problem with the network environment between the admin server and the server_name
The server_name is not powered on
The agent service for the server_name has stopped
The server_name, or the server management unit has failed (Related errors are displayed)
The load on the CPU of the server_name is high and information cannot be obtained from the server
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]
Check the network environment.
Power on the server_name.
When the server_name is a managed server, start the agent service.
For how to start the agent service, refer to "5.1 rcxadm agtctl" of the "ServerView Resource Coordinator VE Command Reference".
Recover the failed server or server management unit.
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 RC console server resource tree and select [Update] from the displayed menu. Updating of the information may take around 30 seconds. Check in the resource details that information for the server has changed.
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.
[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.
[Corrective Action]
Check the status of the admin LAN and perform corrective action as necessary.
[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.
[Description]
There is an invalid function described in the license file filename.
[Corrective Action]
The invalid function cannot be read. No action is required.
[Description]
Power off was performed for the managed server server_name, but power off could not be confirmed. The managed server will undergo forced power off.
This message may be displayed during 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 required.
[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 required.
[Description]
A server or LAN switch with differing type information was detected in the same slot of the same chassis as a registered server or LAN switch.
One of the following is displayed for type:
IP address
MAC address
Product
LAN switch model
blade type
The registered value is displayed for obj1.
The newly detected value is displayed for obj2.
[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 changing IP addresses, refer to "6.3.2.3 Changing Admin IP Addresses" of the "ServerView Resource Coordinator VE Setup Guide".
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.
Check the status of the server and reconfigure the hardware properties again if necessary.
However, when VIOM coordination settings have been performed, reconfiguration of hardware properties is performed automatically so no action is necessary.
For reconfiguration of hardware properties, refer to "9.3 Re-configuring Hardware Properties" of the "ServerView Resource Coordinator VE Operation Guide".
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.
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".
[Description]
type information was not detected for a server blade.
"NIC for admin LAN" is displayed for type.
[Corrective Action]
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.
[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.
[Description]
The processing of the function for obj has not been performed.
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.
[Corrective Action]
When function is "auto-recovery", Auto-Recovery has not been performed.
Perform server switchover manually as necessary.
[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.
