Resource Coordinator VE can centrally monitor the configuration and status of servers or other managed resources directly from the RC console. This enables the identification of resources experiencing problems, which reduces time spent on system maintenance. Moreover, Resource Coordinator VE can easily launch external management software to precisely locate faulty parts within a managed resource.
Monitoring is based on the following three components:
Resources
The resource tree displays chassis, servers, LAN switches, physical OS's, VM hosts, VM guests, power monitoring device relationships or statuses (either PDU or UPS). When a hardware problem occurs on a server, affected guest operating systems can easily be detected.
Note
Power monitoring devices are not subject to monitoring.
Events
Resource Coordinator VE displays events such as hardware failures, server switchovers triggered by hardware failures, and the results of every performed operation.
Recent Operations
Resource Coordinator VE displays the progress status of the various operations performed on resources.
The following table shows the level of monitoring performed for each resource monitored in Resource Coordinator VE.
Resource | Status monitoring | Event monitoring |
|---|---|---|
Chassis | Yes | Yes |
Server | Yes | Yes |
Physical OS | Yes | No |
VM host | Yes | No |
VM guest | Yes | No |
VM management software | Yes | No |
LAN switch | Yes | Yes |
Power monitoring device | No | No |
Yes: Supported
No: Not supported
Regular update of resource data
The Resource Coordinator VE Manager regularly updates resource data with information gathered from the following resources.
Resources subject to regular update | Related resources | Data source |
|---|---|---|
Chassis | Chassis | Server Management Unit |
Server | Server | ServerView Agent (*2) |
LAN switch | LAN switch | LAN switch |
VM management software | VM management software | VM management software |
*1: When no VM management software is registered, the status of VM hosts and VM guests is updated during a regular update of their physical server. When a VM management software is registered, their status is updated during a regular update of the VM management software.
*2: only for PRIMERGY servers.
*3: only for LAN switch blades mounted in a PRIMERGY BX chassis.
The time required to update all resources depends on the number of registered resources. For one chassis that contains 10 servers and 4 LAN switches, the update takes about 2 minutes. For 5 chassis that have identical configurations, the update should take about 10 minutes.
VM management software updates are independent from other resource updates, and takes approximately 2 minutes.
In the following cases, resource data is refreshed without waiting for the regular update.
When a resource's state is changed as the result of an operation performed by Resource Coordinator VE
When a failure-triggered SNMP Trap is received from a resource
If a resource was operated externally to Resource Coordinator VE, there may be a slight delay before its state is updated in the RC console. To force an update of a resource's data, right-click the resource and select [Update] from the displayed menu. The time required to update resource data depends on the device. Generally, update should take no more than 40 seconds.
In order to restrain device and network load, resource data is not refreshed for 7 seconds following the last update time. However, when a failure-triggered SNMP Trap is received, resource data is refreshed unconditionally. When manually updating a resource from the menu right after performing an operation on that resource, if its data is not refreshed within 40 seconds, try updating it from the menu again.
