Identifying service-affected events

Use the SAEs in the Event Viewer to quickly identify network service-affecting events.

Network Manager uses the discovered topology and event data to create SAEs. An SAE is generated on a service when a severity 5 (Critical) event occurs on a device or interface that is essential to that service. The SAEs themselves have a severity of 4 (Major) and are colored orange in the Event Viewer. The Summary field contains text indicating that the event is an SAE.

Click on the color-coded severity indicator box corresponding to severity 5 (Major).
The severity indicator boxes are located at the bottom of the Event Viewer and the corresponding color is orange.
Examine the Summary field of the Major severity events to determine whether any of the events is an SAE.

Network Manager models MPLS Layer 3 VPNs and identifies the Provider-Edge to Customer-Edge facing interfaces for each discovered VPN. When an event is raised against one of these interfaces, Network Manager calculates that a specific VPN instance could be affected by the event. Network Manager raises an SAE on the VPN and does not delete the original event.

You can perform any of the following actions on this event:

Display network events that contributed to a service-affected event.
Display related topology views
Drill into the affected device to investigate the health of device components
Browse the MIB associated with the affected device