Get started
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
A newer release of this product is available.
Service processor events
Contributors
Suggest changes
-
PDF of this doc site
-
Online help
-
Monitor and manage cluster performance
-
Monitor and manage cluster health
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
Service processor events provide you with information about the status of your processor so that you can monitor for potential problems. Events are grouped by impact area and include the event and trap name, impact level, source type, and severity.
Impact area: availability
| Event name(Trap name) |
|---|
Impact level |
Source type |
Severity |
Service Processor Not Configured(ocumEvtServiceProcessorNotConfigured) |
Risk |
Node |
Warning |
Service Processor Offline(ocumEvtServiceProcessorOffline) |
Risk |
Node |
Error |
