HP OneView for Microsoft System Center User Manual
Page 41
Health Explorer does not display Knowledge Information for computers and certain
Windows components
Knowledge bases are components of Microsoft Management Pack and can display limited or no
information.
HP Custom Data Manager cannot be used in the HP Virtual Connect Management
Pack
Although CDM is accessible from the HP Virtual Connect Group Diagram view, it only supports
servers for custom data management.
Health rollup to VC Domain does not bring the worst case health status from underlying
health components
The worst case health rollup in the HP Virtual Connect Management Pack stops at the level of
Physical and Logical components. The Virtual Connect Domain health is designed to be unaffected
by the underlying health components, but to periodically match the health status of the underlying
Virtual Connect Domain.
To observe the health status of the Virtual Connect Domain, launch the Virtual Connect Manager
web console. Virtual Connect Domain health will be rolled up to the HP Virtual Connect Domain
Group.
If a VC FC Uplink becomes unpopulated its health status is set to “Warning” instead
of “Healthy”, irrespective of Flex-Fabric and Ethernet uplinks
If an FC uplink connecting to an external switch is removed, it is expected that the health status of
the FC uplink will change to “Warning”. Now, from the same FC uplink, if the SFP transceiver (a
connector between a Fibre Channel cable and the interconnect bay
is removed, the health status does not change to “Healthy” but remains
as “Warning”.
This is expected behavior from the underlying VC implementation. Virtual Connect Management
Pack only receives the status as defined internally and surfaces the same in the FC Uplink Ports
State View.
When an uplink status restores from Error to Normal, Event ID 7500 or 7800 is
raised in VC Active Alerts view
When an uplink connection is removed, Event ID 7500 or 7800 is raised in the Active Alerts view
under HP Virtual Connect. But if the same uplink is restored the same Event ID 7500 or 7800 will
be raised, resulting in the increment of the Repeat Count property.
This is an expected behavior triggered from the internal Virtual Connect domain. During the restoring
of the uplink status the internal implementation causes an “Error” alert to be raised, followed by
informational alerts. Due to this, the Active Alerts view increments the Repeat Count for the event
ID 7500 as it was triggered to “Error”, but it cannot show informational alerts.
Alerts show the IP of the module rather than the overall Primary IP, or statically
configured domain IP
This is expected behavior. Virtual Connect domain throws alerts on behalf of problems raised in
the individual modules. This helps to determine more easily the source of the problem in complex
domain configurations. Launch the Virtual Connect Manager web console to diagnose the module
which raised the alert.
Operational and usage issues
41