IBM Tivoli Network Manager IP Edition

© 2014 IBM Corporation

What are

SAE

s -

S

ervice

A

ffected

E

vents?

- v3.9 & higher versions!

Presenter:

Agenda:



SAE Overview



SAE Architecture



SAE Functional walk through

–

How to enable/disable SAE plug-ins

–

Demo



Reference Material

–

SAE implementation in multi-tiered OS architecture

Presenter: Krishna M Kodali

SAE Overview

 Service-Affected Events (SAEs)

– Introduced in ITNM v3.7 and is a cross-product ITNM/OMNIbus feature.

– Automation generates an event when a member of a pre-defined service fails.

– SAE feature is ON by default in v3.9 and higher versions.

– A Service Affected Event alert warns operators that a critical customer service has been affected by one or more network events.

– An SAE is produced when one or more events occur on a Provider Edge (PE) or Customer Edge (CE) interface in a Virtual Private Network (VPN) or Virtual Private LAN Service (VPLS). The underlying network events are on an interface of a PE router or a CE router, or on the link between them. One should configure the MPLS discovery to infer the existence of CE routers so all possible SAEs are generated for your customer VPNs.

– Allows dynamic Discovery and Modelling of a Network Services

• Out-of-the-box for MPLS VPNs (MPLS VPNs, MPLS TE Paths & On demand IPv4 Paths)

• Customizable to any collection of discovered entities

 SAE is a plug-in for EventGateway (ncp_g_event).

– SAE plug-in extracts MPLS VPN information from the discovered topology and uploads it into the OMNIbus ObjectServer for use by the SAE automation

– Configurable via $NCHOME/etc/precision/SAESchema.cfg

 OMNIbus SAE automation

– The SAE automation & schemas can be added to an existing v7 Object Server via the script : $NCHOME/precision/scripts/create_sae_automation.sql

SAE -Architecture

SAE IP Path

SAE MPLS VPN

➔

Each time the topology is updated due to Discovery cycles, the updates are sent by Event Gateway via SAE plug-ins to

the ObjectServer either by inserting, updating or deleting a record.

Presenter: Krishna M Kodali

SAE -Functional walk through

 What's an SAE event and how does it work?

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

– In above example, the red event is a linkDown event of an interface that has an MPLS VPN running over it. This is called as an underlying event.

– The ObjectServer SAE automation sees that (runs every 60 seconds), this linkDown event is of an entity known to support a VPN named VC_77 and creates ‘synthetic’ event to represent that a given MPLS VPN service has been affected named VC_77.

– Only ONE SAE will get generated per service, no matter how many events appear on interfaces running this particular VPN service.

– SAE events are always Severity 4 Major (orange).

– When all underlying events (on all entities) that pertain to a given VPN are cleared, the SAE automatically clears itself.

 Advantages:

SAE -Verifying SAE plug-in status

 Validating if ITNM & Omnibus are SAE ready:

– Two fold check i.e. ITNM & Omnibus:

•

ITNM

– Verify the plug-ins are enabled for a given domain (Out-of-the-box they are ON).

•

Omnibus

– Are necessary schemas & SAE automation installed in ObjectServer and enabled?

> You can drop and re-install using below scripts (if need be):

Presenter: Krishna M Kodali

SAEs for Network IPv4 Paths

SAEs - Event navigation

 Use right-click tools to navigate between Underlying and Synthetic Events. :

– Click on underlying event – select Show SAE Related Services, i.e. see SAE(s)

Presenter: Krishna M Kodali