Home > Cisco > Network Hardware > Cisco Prime Nerk 43 User Guide

Cisco Prime Nerk 43 User Guide

Here you can view all the pages of manual Cisco Prime Nerk 43 User Guide. The Cisco manuals for Network Hardware are available online for free. You can easily download all the documents as PDF.

Page 221

CH A P T E R
  
10-1
Cisco Prime Network 4.3.2 User Guide
10
How Prime Network Handles Incoming Events
These topics explain how Prime Network handles incoming events and provides information about 
events and tickets in the GUI clients:
How Events Flow Through Prime Network Components, page 10-1
Standard and Upgraded Events, page 10-4
How Prime Network Correlates Incoming Events, page 10-4
How Prime Network Calculates and Reports Affected Parties (Impact Analysis), page 10-11
Clearing, Archiving, and...

Page 222

  
10-2
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Events Flow Through Prime Network Components
Figure 10-1 Logical Flow of Incoming Events Received By Prime Network
External OSS Apps (SNMP)
Fault Agent
(AVM 25)Fault
Manager
Even
repo
Gateway
VNEVNE Units
- New tickets and related events
- Updates to existing tickets
- Upgraded events with correlation 
- System internal events
- E-mail notifications
- Standard events
- Events from specified...

Page 223

  
10-3
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Events Flow Through Prime Network Components
The main components involved in fault processing are described in the following table.
Component Located on: Description
Event Collector
(AVM 100)Gateway or 
unit(s)1
1. By default, the Event Collector is installed on the gateway. All supported configurations are described in the event monitoring 
topics in the Cisco Prime Network 4.3.2 Administrator...

Page 224

  
10-4
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  Standard and Upgraded Events
For more details about what each component does, see How Prime Network Correlates Incoming Events, 
page 10-4.
Standard and Upgraded Events
If the VNE cannot extract adequate information about an event, it performs some basic parsing and saves 
the event in the database. These events are called standard events. A standard event is an event that Prime 
Network cannot match...

Page 225

  
10-5
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Prime Network Correlates Incoming Events
Figure 10-2 Event Processing—Events With Correlation Enabled
 
AVM 100
VNE
Event
from managed
device?
(If saving events from unmanaged devices is enabled)
Standard events
Upgraded
events
Ye s
Ye sNo
Can
identify and
associate?No
Ye s
Flapping?
SuppressNo
Local Network
Ye s
Correlate?
Local or
Network?
Cause
found?
Suspend for
2 minutes
Ye s
NoNo
Ye s...

Page 226

  
10-6
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Prime Network Correlates Incoming Events
Figure 10-3 Event Processing—Events With No Correlation
Parse the Event To Identify It, Associate It With a Source, And Determine If It Is a Standard or Upgraded Event
The VNE begins the event identification process by extracting and parsing the following information 
from the raw event:
Event Functionality Type—Trap, syslog, or Service event
Event Type and...

Page 227

  
10-7
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Prime Network Correlates Incoming Events
Event description strings—Content of the notification message content and a short description
Event Severity—Event’s importance, derived from the setting for the event’s severity registry key): 
–Flagging—Indicates a fault: Critical (red), Major (orange), Minor (yellow), or Warning (sky 
blue)
–Clearing—Indicates a fault that is resolved: Cleared (green)...

Page 228

  
10-8
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Prime Network Correlates Incoming Events
Note‘true’ enables the expedite optimization and ‘false’ disables the expedite optimization.
You can also override the window-length of the time span by using the following runRegTool command 
and then restart the VNEs:
runRegTool.sh -gs 127.0.0.1 set 0.0.0.0 
agentdefaults/da/optimized-expedite/window-length 
NoteThe time-value should be in milli seconds....

Page 229

  
10-9
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Prime Network Correlates Incoming Events
An example of an event with a correlate=false registry setting is a Link Down Due To Oper Down event, 
where the event is its own cause. An example of an event with a is-correlation-allowed=false registry 
setting is a syslog that does not cause other events.
The VNE attempts to identify an event sequence (see Identify Event Sequences and Hierarchies, 
page...

Page 230

  
10-10
Cisco Prime Network 4.3.2 User Guide
Chapter 10      How Prime Network Handles Incoming Events
  How Prime Network Correlates Incoming Events
The correlation is based on a flow that runs across the Prime Network model and topology. Network 
correlation is most successful if the event holds forwarding information, such as the IP address of a 
Border Gateway Protocol (BGP) neighbor, or a Frame Relay virtual connection. Network correlation is 
well suited for the following scenarios: 
The event...
Start reading Cisco Prime Nerk 43 User Guide

Related Manuals for Cisco Prime Nerk 43 User Guide

All Cisco manuals