This section explains the 691XX message series.
[Description]
An error occurred during communication with the target target.
[Corrective Action]
When target is the admin IP address of the admin server, take the following corrective actions depending on the content of detail.
"configuration error"
For the correction method, refer to the corrective action of "Message number 67350".
"SSL certification error"
For the correction method, refer to the corrective action of "Message number 67351".
"connection timeout"
For the correction method, refer to the corrective action of "Message number 67352".
"read timeout"
For the correction method, refer to the corrective action of "Message number 67353".
"write timeout"
For the correction method, refer to the corrective action of "Message number 67354".
"connection error"
For the correction method, refer to the corrective action of "Message number 67355".
"no route to host"
For the correction method, refer to the corrective action of "Message number 67356".
"IO error"
For the correction method, refer to the corrective action of "Message number 67357".
"internal error"
For the correction method, refer to the corrective action of "Message number 67358".
When target is the IP address of a server management unit, take the following corrective actions depending on the content of detail.
"snmp communication error"
Use the following methods to check if SNMP communication with the server management unit is possible.
Use the ping command or another method to check if there is a problem with the network environment between the admin server and the server management unit.
If a cable is disconnected from the LAN connector, connect it.
Check whether connection to the admin UI of the server management unit (In the case of the PRIMERGY BX series, the Web UI or telnet) is possible.
Check that the SNMP community name set in the management blade has not been changed from the value specified in chassis registration.
Check that the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values.
Check that Write (reference and updating) authority is possessed for the SNMP setting of the management blade.
Check the SNMP community name set from the RC console.
If it was omitted, "public" will be specified.
Check that the server management unit of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
For details of checks and the setup method, refer to the manual of the server being used.
When target is the IP address of a power monitoring device, take the following corrective actions depending on the content of detail.
"snmp communication error"
Use the following methods to check if SNMP communication with the power monitoring device is possible.
Check if there is a problem with the network environment between the admin server and the power monitoring device using the ping command or another method.
If a cable is disconnected from the LAN connector, connect it.
Check that connection to the power monitoring device is possible using Web UI or telnet.
Check that the SNMP community name set in the power monitoring device has not been changed from the value specified during registration.
Check that Read (reference) authority is possessed for the SNMP setting of the power monitoring device.
Check the SNMP community name set from the RC console.
If it was omitted, "public" will be specified.
For details of checks and the setup method, refer to the manual of the power monitoring device.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
SNMP communication with target failed.
If the basic information of the chassis or managed server has been changed, the specified value may differ from the value set on the device.
In cases other than the above, there are the following possibilities:
The SNMP community name settings are incorrect
The server is not powered on
The ServerView Agent has not been started
[Corrective Action]
If the basic information of the chassis or managed server has been changed, check the following and take corrective action.
When the IP address of the chassis has been changed
Check that the specified IP address matches the one set on the management blade.
When the SNMP community name of the chassis has been changed
Check that the SNMP community name specified matches the one set for the management blade and managed servers.
When the IP address of a managed server has been changed
Check that the specified IP address matches the one set on the managed server.
In cases other than the above, check the following and take corrective action.
Check the power status of the managed server.
If the status is OFF, power on the managed server.
Check that the ServerView Agent of the managed server has been started.
If it has not been started, refer to the ServerView Agent manual and start it.
Check that the SNMP service of managed server has been started.
If it has not been started, start SNMP service.
[Windows/Hyper-V]
Log in to the managed server using OS administrator authority.
Open "Services" from "Administrative Tools" on the Windows Control Panel, and check that the status of the SNMP Service is "Started" on the [Services] window.
When the service is stopped, start the service.
[Linux/VMware/Xen]
Log in to the admin server using OS administrator authority.
Execute the following command, and check that the SNMP daemon is operating.
# /etc/init.d/snmpd status <RETURN> |
When SNMP daemon is stopped, execute the following command and start the daemon.
# /etc/init.d/snmpd start <RETURN> |
Check that the SNMP community name set for the ServerView Agent matches the one set in a management blade.
Check that the SNMP community name specified during server registration matches the one set for the ServerView Agent.
Check that the admin LAN IP address specified during server registration matches the one that has been set on the managed server.
Check that Write (reference and updating) authority is possessed for the SNMP setting of the management blade.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The managed server is a model for which LED operation cannot be performed.
[Corrective Action]
Refer to "1.2 Hardware Environment" of the "ServerView Resource Coordinator VE Installation Guide", and check that the server meets the requirements.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
A blade has not been mounted in slot slot_number.
[Corrective Action]
Mount a blade in the slot.
When a blade has been mounted in the slot, check if the MAC address of the blade is recognized correctly on the management blade Web UI.
If the MAC address of the blade is not recognized correctly, mount the blade again, and power it on.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Obtaining the information from the server management unit failed.
[Corrective Action]
Check whether communication with the server management unit is possible.
Use the ping command or another method to check if there is a problem with the network environment between the admin server and the server management unit.
If a cable is disconnected from the LAN connector, connect it.
Use the Web UI or telnet to check that connection to the server management unit is possible.
Check that the SNMP community name set in the management blade has not been changed from the value specified in chassis registration.
Check that the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values.
Also, check that the user of the Remote Management Controller has administrator authority.
If this message is displayed during execution of any of the following operations, check that the specified IP address matches that of the server management unit.
Chassis registration
Changing of a chassis admin IP address
Managed server registration
Changing of a managed server's Remote Management Controller information
If no problems are found, a temporary loss of communication may have occurred due to rebooting of the server management unit, etc.
Wait for 2 or 3 minutes and then repeat the failed operation.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The server may not exist or an incorrect name might have been specified.
[Corrective Action]
Update the information of the RC console, and check if the relevant server exists.
To update the information, right-click the chassis on the 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.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The server is a model which does not support forced power off.
[Corrective Action]
Refer to "1.2 Hardware Environment" of the "ServerView Resource Coordinator VE Installation Guide", and check that the server meets the requirements.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The server is a model which does not support power operations.
[Corrective Action]
Refer to "1.2 Hardware Environment" of the "ServerView Resource Coordinator VE Installation Guide", and check that the server meets the requirements.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Timeout has occurred during the execution of the internal command command.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Power operation has been executed normally, but timeout has occurred during obtaining the information for the status of post-power off.
[Corrective Action]
The server may have not been powered off.
Check the power status of the server.
[Description]
Timeout has occurred during the execution of the power control module.
[Corrective Action]
Power operation may have been performed directly on the hardware of the managed server or the chassis while it was being started or stopped.
In that case, perform the operation again.
If power operation has not been performed directly, take the following corrective actions.
When deploying cloning images
There may be a mistake in the SNMP community name settings.
When this occurs on PRIMERGY BX series servers
When the blade server the cloning image was collected from is mounted in a different chassis from the blade server the cloning image is being deployed to, check that the SNMP community names of the chassis are the same.
When this occurs on rack-mount servers or tower servers
Check that the SNMP community names of the server the cloning image was collected from and the server the cloning image was deployed to are the same.
When a managed server with an agent registered has been powered on
The settings of the OS may be incorrect.
Log in, check the following and take corrective action.
If the settings of the admin network interface are correct
Whether the network settings are valid, and if the admin server and managed server can communicate correctly.
Whether an agent has been started
Refer to "15.3 "unknown" Server Status" of the "ServerView Resource Coordinator VE Operation Guide", and take the relevant corrective action.
When a managed server using HBA address rename does not start
Refer to "15.2 OS Startup Issues (with I/O Virtualization)" of the "ServerView Resource Coordinator VE Operation Guide", and take the relevant corrective action.
When Auto-Recovery, server switchover or failback has been performed
Check the resource name of the event log, determine whether the primary server or spare server has been affected and then take the following corrective action.
When the primary server has been affected (the spare server in the case of failback)
Check if the active server has been powered off. If it has not been powered off, directly (physically) power off the server hardware and then perform the operation again.
When the spare server has been affected (the primary server in the case of failback)
Whether the BIOS settings are correct
Check if the BIOS settings of the spare server correspond with those of the operational environment. After changing any necessary settings, perform the operation again.
For details of BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
Whether an HBA has been mounted
When using HBA address rename, check if the server has an HBA mounted, and if there is no HBA mounted, mount one. Then perform the operation again.
Whether communication is possible using the admin LAN
Check that the settings of network devices (LAN switches, ports, etc.) enable communication using the admin LAN.
If communication is not possible using the admin LAN, either replace the devices or change the settings, and the repeat the operation.
Alternatively, in an environment with a redundant admin LAN, for managed servers other than PRIMERGY BX series servers, check that the admin LAN MAC address set during managed server registration is correct. If there is an error in the settings, reconfigure the hardware information and specify the correct MAC address.
The MAC address can be checked in the resource details of the physical server.
For how to check, refer to "2.5.2 [Resource Details] tab" of the "ServerView Resource Coordinator VE Setup Guide".
For reconfiguration of hardware properties, refer to "9.3 Re-configuring Hardware Properties" of the "ServerView Resource Coordinator VE Operation Guide".
In cases other than the above, manually perform server switchover or failback again, and check the console of the spare server.
If the OS of the spare server boots, the settings of the OS may be incorrect. Log in, check the following and take corrective action. If the status of the agent is not normal after a given length of time, it will automatically return to its previous state. After it does, perform the operation again.
Whether the SNMP community name settings of the chassis are correct
When the primary server and spare server are mounted in different chassis, ensure that the SNMP community names of both chassis are the same.
Whether the SNMP community name settings of the server are correct
When this occurs on rack-mount servers or tower servers, check that the SNMP community name settings of the primary server and the spare server are the same.
Whether an agent has been started
Refer to "15.3 "unknown" Server Status" of the "ServerView Resource Coordinator VE Operation Guide", and take the relevant corrective action.
If the settings of the admin network interface are correct
When the settings to bind admin network interfaces to MAC addresses have been performed, change the settings so as not to bind them.
When chassis power operations have been performed
There may be a mistake in the SNMP settings. Check that the SNMP community name set in the management blade has not been changed from the value specified in chassis registration.
If an operation to stop the chassis is performed while the OS of the server blade is starting, the server blade will not shut down and stopping of the chassis will fail. In such cases, perform the operation to stop the chassis again.
When managed servers are PRIMERGY BX series servers
There is a chance that the correct settings have not been configured for the SNMP agent on the management blade. For details of the settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An internal command for obtaining server information may be being executed in another process.
[Corrective Action]
Wait a couple of minutes and then perform the operation again.
[Description]
The operation of the server management unit failed.
[Corrective Action]
Check the following and take corrective action.
Whether communication with the management blade is possible
Check if there is a problem with the network environment between the admin server and the management blade using the ping command or another method.
If a cable is disconnected from the LAN connector, connect it.
Whether Write (reference and updating) authority is possessed for the SNMP setting of the management blade
Check the SNMP community name set from the RC console.
If it was omitted, "public" will be specified.
Check that the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
For details of checks and the setup method, refer to the management blade manual.
Whether the hardware status is correct
When the server blade has not been inserted into chassis correctly, re-insert it and perform the operation again.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Powering on of the maintenance LED failed because of the error displayed in the detailed information error_number.
[Corrective Action]
Check the error number displayed in the detailed information error_number and take the corrective action indicated for that message.
[Description]
Powering off of the maintenance LED failed because of the error displayed in the detailed information error_number.
[Corrective Action]
Check the error number displayed in the detailed information error_number and take the corrective action indicated for that message.
[Description]
Powering off of the managed server failed because of the error displayed in the detailed information error_number.
[Corrective Action]
Check the error number displayed in the detailed information error_number and take the corrective action indicated for that message.
[Description]
The managed server is not in the maintenance mode.
[Corrective Action]
Set the server to the maintenance mode.
[Description]
Power control failed because the power status is OFF.
[Corrective Action]
This message is displayed when the server for power control operation is powered OFF. Check that the correct server is the target of the operation.
When the server for operation is correct, turn ON the power and perform the operation again.
When this message is displayed during the setting of HBA address rename, restarting the server enables HBA address rename setup.
[Description]
Chassis power control failed.
When detail is rc manager found in chassis
As there is a manager installed on a server blade mounted in the chassis that is the target of power operation, it is not possible to stop the chassis.
[Corrective Action]
Take corrective action for the content displayed for detail.
When detail is rc manager found in chassis
When stopping the chassis, please do so without using Resource Coordinator VE.
[Description]
An internal error has occurred.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
