This section explains how to troubleshoot a registered managed server whose status is "unknown" even though the managed server is still running.
When errors or warning messages are displayed in the event log, take the appropriate action by referring to the "ServerView Resource Coordinator VE Messages". Check the following points and correct the cause of any problems:
Communication between the Admin Server and the server management device is not possible.
Check if it is possible to connect to either the Web or telnet interface of the server management device (management blade or remote management controller).
Communication between the Admin Server and the managed server is not possible.
Check that the same VLAN ID is set for the LAN switch blade port used by the Admin LAN so that communication between the managed server and Admin Server is possible.
When changing VLAN IDs on the Admin LAN, change the VLAN ID for the LAN switch blade's port connected to the Admin Server as well as the VLAN ID of the Admin IP address in order to enable communication from the Admin Server to the LAN switch blade. Then change the VLAN ID for the Admin LAN to the managed server.
Refer to "3.2.1 Network Configuration" and "6.3.2.8 Changing the VLAN Settings of a LAN Switch" of the "ServerView Resource Coordinator VE Setup Guide" for the overview and the setup of VLAN for the managed server.
Communication is not allowed for the ports used by Resource Coordinator VE
Allow communication for the ports described in "Appendix C Port List" of the "ServerView Resource Coordinator VE Setup Guide".
The Resource Coordinator VE Agent is not running
Make sure that the Agent is running on the managed server.
The ServerView Agent is not running.
For PRIMERGY servers, check whether the ServerView Agent is running properly on the managed server.
[Windows/Hyper-V]
From the Windows Control Panel, open "Administrative Tools" and then open the [Services] window. Check that the status of the Server Control Service and SNMP Service is shown as "started".
[Linux/VMware]
Execute the following commands to check if the ServerView Agent daemon is running.
# /etc/init.d/srvmagt status <RETURN> |
The above commands are not available if the ServerView Agent is not installed. In this case install the ServerView Agent on the managed server.
If the above commands indicate that the ServerView Agent is not running, refer to the ServerView Agent manual to start the ServerView Agent.
SNMP community settings are incorrect
Make sure that the SNMP community settings on the management blade and managed server match those set in Resource Coordinator VE during chassis and server registration.
Hardware properties were not re-configured after replacing the server.
Identify the MAC address of the replacement server, and check if it is the same address as that set for the Admin LAN (MAC address) in the [Resource Details] tab of the RC console.
If the MAC address is different, re-configure the hardware properties from the RC console.
No information could be obtained from the virtualization software running on the managed server.
In environments where no VM management software was registered, or for VM hosts that are not managed by a VM management software, the status of a VM guest is displayed as "unknown" if its information could not be obtained from the server virtualization software used to run that VM guest. Check whether the virtualization software is operating correctly.
If it is operating correctly, its account information (user account name and password) may have changed. As a result, the settings no longer correspond to those registered in Resource Coordinator VE. In that case, change the virtualization software's account settings registered in Resource Coordinator VE.
Refer to "6.3.2.7 Changing VM Host Login Account Information" of the "ServerView Resource Coordinator VE Setup Guide" for details.
No information could be obtained from VM management software
In environments where a VM management software was registered, the status of a VM guest (on a VM host managed by this VM management software) is displayed as "unknown" if its information could not be obtained from the VM management software. Check whether the VM management software is operating correctly.
If it is operating correctly, its account information (user account name and password) may have changed. As a result, the settings no longer correspond to those registered in Resource Coordinator VE. In that case, change the VM management software's account settings registered in Resource Coordinator VE.
Refer to "6.3.5 Changing VM Management Software Settings" of the "ServerView Resource Coordinator VE Setup Guide" for details.
The remote management controller's IP address, user name, or password was changed after server registration
Change the IP address, user name and password settings registered for this remote management controller in Resource Coordinator VE.
Refer to "6.3.2.5 Changing Remote Management Controller Settings" in the "ServerView Resource Coordinator VE Setup Guide" for details.
High load on the Admin Server, server management unit or managed server
Resource statuses may be temporally shown as "unknown".
