HP StorageWorks Clustered Gateway 3.6.0 Windows Storage Server Edition Event Notification Guide (5697-7151, January 2008)

Chapter 3: Event Messages 29
4628 Probe failed: <monitor> feature is unlicensed.
The monitor feature is unlicensed on the specified server. The server may no
longer be suitable for the virtual host(s) associated with the monitor. If the
virtual host(s) were active on the affected server, they may have failed over
to another server. (Whether failover occurs is dependent on the
configuration of the monitor and the virtual host(s).)
Action: Verify that the product license is installed correctly.
4629 Probe license feature is resolved.
Action. None. Alert 2628 is resolved.
4630 Probe failed: <IP address> feature license is unavailable.
The monitor feature license is unavailable. The server may no longer be
suitable for the virtual host associated with the monitor. If the virtual host
was active on the affected server, it may have failed over to another server.
(Whether failover occurs is dependent on the configuration of the monitor
and the virtual host.)
Action. Verify that the product license is configured correctly.
4631 Probe feature license availability is resolved.
Action. None. Alert 4630 is resolved.
4632 Probe failed: <monitor> feature license is unavailable.
The monitor feature license is unavailable. The server may no longer be
suitable for the virtual host associated with the monitor. If the virtual host
was active on the affected server, it may have failed over to another server.
(Whether failover occurs is dependent on the configuration of the monitor
and the virtual host.)
Action: Verify that the product license is configured correctly.
4633 Probe feature license availability is resolved.
Action. None. Alert 4632 is resolved.
13901 <server> should be rebooted ASAP as it stopped network communication
<date-time> and was excluded from the SAN to protect filesystem integrity.
Action. The server was excluded from the cluster because it could no longer
communicate over the network. The server should be rebooted at the first
opportunity. Also check the network and make sure that the server is not
experiencing a resource shortage.
ID Message and Corrective Action