NNM Architecture

ca.com
Basic Components of NNM
NNM Local System Remote System
NNM Processes
and Applications

NNM
Databases
NNM User
Interfaces

Web Web
Launcher Browser

Slide I - 2 ca.com
How NNM Works
Processes associated with a
user’s ovw session

Foreground
Processes
Post-processing Processes
storage accessible started by
through SQL and ovstart,
web reports which monitor
the network

Data Background
Network
Warehouse Processes

NNM
Contain data stored
Databases
and used
by foreground &
background processes

Slide I - 3 ca.com
NNM Directory Structure
OV_BIN install_dir\bin Executable files for NNM

OV_WWW install_dir\www Web-related files

OV_MAN install_dir\help Reference pages

OV_CONTRIB install_dir\contrib Contributed software

OV_DB install_dir\databases Map, object, topology and data collection

databases
OV_LOG install_dir\log Log files

OV_SNMP_MIBS install_dir\snmp_mibs MIB definitions

OV_REGISTRATI install_dir\registration Files that modify the operation of user interfaces

ON

OV_WWW_REG install_dir\www\registration Files that modify the operation of web interfaces

OV_CONF install_dir\conf Configuration and security files

OV_LRF Install_dir\lrf Files that modify the operation of processes

Slide I - 4 ca.com
NNM Background Services
ovspmd Starts and monitors NNM background processes
netmon Discovers and polls network nodes
ovtopmd,ovwdb Maintain the topology and object database
ovtrapd Receives and buffers SNMP traps
ovactiond Runs event-triggered commands

snmpCollect Collects MIB data and monitors thresholds

ovdbcheck Validates the connection to the data warehouse
ovrepld Replicates remote topology on local system
ovcapsd Checks for DMI and web capabilities
pmd Receives and forwards OpenView events
ovuispmd, Keep track of all the ovw and web sessions running
ovsessionmgr
ovalarmsrv Maintains the alarm service
ovrequestd Schedules requests for the web reporting interface
ovas Serves the Dynamic Views java applets
NNM Services - Relationships

Map ovw
Database
ovactiond
xnmevents
ipmap

Object Binary
ovwdb
Database Event
pmd
Store

Topology ovtrapd
ovtopmd
Database
netmon
SNMP v1
OpenView SNMP v2
Events via traps, inform
SNMP v1 TCP requests
ICMP SNMP v1
(ping) SNMP v2

Managed nodes and collection stations on the network

Slide I - 6 ca.com
NNM Databases

pmd ovtopmd snmpCollect ovw

Map
Binary Event Topology Trend Database
Store Database Database

ovwdb
Data
Warehouse
Object
Database

Slide I - 7 ca.com
Object Database

 Semantic information that spans maps like

object’s Selection Name
 Maintained by ovwdb service
 Object capabilities (isRouter, isHub)
 Object attributes (sysObjectID, system
description)
 Interface Count (number of IP interfaces)

Slide I - 8 ca.com
Topology Database

 Information critical to discovery, monitoring

and displaying of IP nodes
 Maintained by ovtopmd service
– IP information
– netmon information
– Information to track relationships between objects
– Timestamps to help ipmap synchronize

Slide I - 9 ca.com
Map Database

 Information related to visual presentation

 Specific to each map (each map has its own
set of database files)

– Symbol placement on submaps

– Symbol labels

Slide I - 10 ca.com
Event Database (Binary Event Store)

 Events that pass through pmd are logged in

Binary Event Store
 From this database, alarm browser displayes
the configured category of events as alarms

Slide I - 11 ca.com
Trend Database

 Data that is configured for collection for trend

and threshold analysis is stored in Trend
database

Slide I - 12 ca.com
Data Warehouse

 ODBC database that holds data collected by

NNM components
 Central location from which reports are
generated
 Commands to put data into Data Warehouse
– ovdwevent exports event data
– ovdwtopo exports the current topology data
– ovdwtrend exports SNMP collected data and
builds summary of that data

Slide I - 13 ca.com
NNM Database Commands
ovobjprint Prints information from object database
ovobjprint –S Retrieve object database summary information
ovobjprint –s <nodename> Retrieves all object information of a node
ovtopodump Prints information from topology database
ovtopodump –l Displays number of managed nodes and total nodes
ovtopodump –v <nodename> Displays all topology database information of a node
snmpColDump Translates Data Collector data into ASCII format
snmpColDump ASCII format of binary data file If%util.4
\nnm\snmpCollect\If%util.4
ovtopofix Corrects inconsistencies between topology and object
databases
ovtopofix –a Performs all checks and updates
ovtopofix –s Verifies managed and removed state of all objects
ovtopofix –U Update the creation time of objects in topology
database
ovdumpevents Prints information from the Binary Event Store

Slide I - 14 ca.com
NNM Foreground Processes
ovw provides map drawing, editing and menu management

ipmap Invoked by ovw

Draws and maintains submap topology
ovwnavigator Invoked by ovw
Manages the Quick Navigator
ovwsmaphelp Invoked by ovw
Manages the help subsystem
xnmevents Invoked by ovw
Displays the Alarm Browser categories
xnmtrap Invoked by menu bar item
Event Configuration
xnmsnmpconf Invoked by menu bar item
SNMP polling configuration
xnmbrowser Invoked by menu bar item
SNMP MIB browser

Slide I - 15 ca.com
Objects and Symbols
 Object
– Internal representation of an entity
– Objects and their attributes are stored in object database
– Exist only once in the object database
 Symbol
– Graphical representation of an object
– Multiple symbols can exist for the same object
– Eg: LAN card represented by LAN card symbol in Node
submap and connection symbol (line) in segment submap
 Object is deleted from the database only if all the
symbols in all the maps representing that object is
deleted

Slide I - 16 ca.com
NNM Installation Steps

 Install Windows 2003 server

 Install SNMP service
 Check IP configuration – static IP, correct
subnet mask and default gateway
 Ensure DNS specified – else configure hosts
file
 Ensure that Primary DNS suffix name is
configured
 Default gateway should be SNMP enabled

Slide I - 17 ca.com