During a deployment, a customer has identified location data that they would like added to both
chassis and interface events from active (IBM Tivoli Network Manager IP Edition V3.9 (ITNM)) and
passive (traps, syslog etc.) event sources.
This data has been successfully imported into the Discovery process using supported stitching
techniques and appears in the topology as three custom Extralnfo fields (see below). ncpjnodel has
been configured to transfer this location data to a custom extended NCIM database table named
locations (see exhibit below). This data is only held on EntityType 1 (chassis entities) to reduce the

NCIM load. The customer has identified three ObjectServer fields that they would like this data:o be
added to for all suitable events -NmosGeography, NmosCountry, and NmosSite

Example record in Model
Description of the ncim.locations table

The ModelNcimDb configuration has been modified to map:

Based on the scenario, the location data is held in NCIM at the chassis (EntityType 1) but not against
each interface entity.
If an SNMP linkDown trap was received by the ObjectServer, could it be enriched with the location
data held on the chassis?

A.
No. An interface event cannot be related to the parent chassis by the gateway

B.
Yes. Interface events can be enriched with chassis level data by the EventGateway

C.
No. The data would need to be held at both the interface and chassis level to allow this
enrichment

D.
Yes. But only if the event is sent across the gateway for further root cause analysis and entity
identification