HP OpenView Process & Files

1. HP OpenViewProcess & Files CS720H May, 24, 2000

2. At startup

3. ovstart, ovspmd • ovstart • Start the various processes (daemon) • At first, check if ovspmd is running, if ovspmd is not running, starts ovspmd • When you reboot the system, boot script automatically execute ovstart • Ex) Solaris 2.X /etc/init.d/netmgt • ovspmd • Maintains a communication channel for request from ovstart • Send status responses to ovstart • Starts background processes, pmd, ovwdb, ovactiond, snmpCollect, ovtopmd, ovrepld, ovlmd, ovtrapd and netmon according to the start-up configuration file ovsuf • Each process is a child of ovspmd and must run under the control of ovspmd • The ovspmd process maintains a communication channel with each process • The ovspmd uses this channel to send commands to the processes and to receive status responses from them

4. $OV_CONF/ovsuf • Contains the configuration information for ovspmd • Each entry in ovsuf is created by ovaddobj from informaton in the LRF (Local Registration File). • There is at least one LRF for each of the background processes • ovsuf example • 1:ovwdb:ovwdb:OVs_YES_START::-O:OVs_WELL_BEHAVED:15:PAUSE:: • 0:pmd:pmd:OVs_YES_START:::OVs_WELL_BEHAVED:15:PAUSE:: • LRF example • # @(#)netmon.lrf • netmon:netmon: • OVs_YES_START:ovtopmd,pmd,ovwdb:-P -k segRedux=true:OVs_WELL_BEHAVED:15:PAUSE::

5. During operation (Part 1)

6. During operation (Part 2)

7. Background Processes (1) • netmon • Polls SNMP agents to initially discover network topology • Detects topology, configuration and status changes in the network • Uses a “seed file” containing a list of nodes to define the initial management region • Uses the oid_to_type and HPoid2type file to determine correct IP topology behavior and correct vendor and SNMP agent value • oid_to_type example • 1.3.6.1.4.1.4.1.1:Micro Technology:MT LANCE/NMS agent • HPoid2type • 1.3.6.1.4.1.11.2.3.4.1:Hewlett-Packard:HP 3000/XL:6

8. Background Processes (2) • ovtopmd • Maintains the network topology database • The topology database is a set of files in the $OV_DB/openview/topo • Initially reads it, if non exist, create and populate it • Controls and updates the topology database on information from netmon indicating that changes have occurred • Database files: binary file format • Ininfo.dir, ininfo.pag, netinfo.dir, netinfo.pag, nodeinfo.dir, nodeinfo.pag • Seginfo.dir, seginfo.pag, stationinfo.dir, stationinfo.pag, • topoinfo.dir, topoinfo.pag

9. Background Processes (3) • ovwdb • Controls the object database • The object database stores information about the object that NNM uses for describe operations • ovwdbmust be running for NM to work • pmd • Receives and forwards events • Logs events to the files $OV_LOG/trapd.log and $OV_LOG/trapd.log.old • Forwards events from the network on to other applications that have connected to pmd using the SNMP API • ovtrapd • Receives SNMP traps and forwards them to pmd • Responds to SNMPv2 inform requests

10. Background Processes (4) • ovactiond • Receives events from pmd • Executes commands by trapd.conf • trapd.conf Ex) • CATEGORY 0 "IGNORE" "IGNORE“ • ACTION 60 "Print Alarms" printEvents SDESC • OID_ALIAS snmpTraps .1.3.6.1.6.3.1.1.5 • ….. • snmpCollect • Collects MIB data and store the data in the $OV_DB/snmpCollect directory • Perform threshold monitoring and sends threshold events to pmd • Ovlmd • Coordinates communication between the license server and the NNM • Ovrepld • Responsible for object replication

11. Foreground Processes (1) • ovw • Provides map drawing, map editing and menu management • ipmap • Runs under ovw to automatically draw IP topology maps representing network • xnmevents • Display events that are being received by pmd • xnmtrap • The process is invoked by the Option:Event Configuration menu • Define enterprise-specific events (traps) • You can customize the message displayed when a particular event arrives • You can specify a command or a script that should be executed when a particular event arrive

12. Foreground Processes (2) • xnmsnmpconf • The process is invoked by the Option:SNMP Configuration menu • You can add,delete and modify SNMP configuration parameter (community name, number of retries, etc. ) • You can change the netmon status polling interval • xnmloadminb • The process is invoked by the Option:Load/Unload MINs:SNMP menu • Load new Internet-standard or enterprise-specific MIBs into the loaded MIB database • xnmbrowser • The process is invoked by the Misc:SNMP MIB Browser menu • Get and set MIB values for MIB objects • xnmcollect • The process is invoked by the Options:Data Collection & Thresholds: SNMP menu • Configure the manager to collect MIB data from network object at regular intervals

13. Foreground Processes (3) • xnmbuilder • The process is invoked by the Options:MIB Application Builder:SNMP menu • Build custom screens to manage multi-vendor MIB objects • xnmgraph • Graph the results of monitoring operations for managed SNMP objects • xnmappmon • Displays textual results of monitoring operations for managed SNMP objects • xnmpolling • The process is invoked by the Options:Network Polling Configuration: IP menu • Updates the polling configuration • mibform, mibtable, rnetstat,findroute,rdbf,rping • Monitor and diagnose problems in TCP/IP network

14. Databases • The Map Database • Presentation information per map • Exact symbol placement, symbol association with each object and symbol labels • The Object Database • Global object information • sysObjectId, vendor and SNMP Agent • The Topology Database • Topology information and layout • Much of information of object database is duplicated in the toplology database

15. Implementation Issues • Implementation Platform • OS • Language • … • What can we reuse from previous work? • Job assignment • Schedule

16. PosView Level-0 Design

17. Level-1 Use case diagram: Set data

18. Level-1 Use case diagram: Discover agent

19. Level-1 Use case diagram: Notify alarm

20. Level-1 Use case diagram: Collect data