Test 901: IBM Tivoli Netcool/OMNIbus V7.1 Implementation

Section 1 - Planning

1. Given the customer requirements in the Statement of Work, review the solution details in order to confirm the architecture

With emphasis on performing the following steps:
1. Review proposed architecture.
2. Determine tier level or architecture.
3. Determine customer advanced configuration. Requirements
4. Determine hardware and OS.
5. Determine contacts at the customer.
6. Determine political considerations.
7. Gather Users, Roles, Security and Physical location.
8. Evaluate security requirements.
9. Evaluate port availability (firewall and ACLs)
10. Determine correct interfaces to existing customer network management systems.


2. Given the architecture document determine the design details in order to develop a design document

With emphasis on performing the following steps:
1. Verify all software needed.
2. Verify licensing.
3. Determine product integration probes.
4. Define components and locations.
5. Determine connectivity between components.
6. Determine media type (CDs, ftp, etc)
7. Determine naming conventions.
8. Determine directory for install.
9. Review customer compliance requirements. (Acceptance testing.)


3. Given a design document obtain the required components so that you are ready to install Netcool/OMNIbus.

With emphasis on performing the following steps:
1. Determine appropriate installer (console vs. GUI).
2. Obtain network availability.
3. Obtain access to systems and servers.
4. Obtain authorization for network.
5. Obtain install media.
6. Obtain license keys.

Section 2 - Installing

1. Given environment variables have been set on a support UNIX or Linux server, install the Netcool License Server using the console, so that the Netcool License Server has been installed.

With emphasis on performing the following steps:
1. Run INSTALL - console.
2. Answer "Yes" to license agreement.
3. Select I to install the license server.
4. Select I to continue the installation.
5. Install selected features.


2. Given environment variables have been set and sourced on a support UNIX/Linux server, install Netcool/OMNIbus V7.1 using the console, so that the selected Netcool/OMNIbus V7.1 components are installed.

With emphasis on performing the following steps:
1. Run install script - INSTALL -console.
2. Accept the license agreement.


3. Given OMNIbus is installed, download the probes patch from the IBM support site and install the patches using $OMNIHOME/install/nco_patch so the probe is installed.

With emphasis on performing the following steps:
1. Download probe patch from the IBM support site.
2. Untar the patch toa tmp directory.
3. Run $NCHOME/OMNIbus/install/nco_patch/path/patch.
4. Typed 'yes' and hit enter to install the probe.


4. Given OMNIbus V7.1 is installed and a patch downloaded from the IBM support site, unzip the patch and install the patch using the nco_patch command on a UNIX host, so that the selected patch has been installed.

With emphasis on performing the following steps:
1. Run the patch install command. nco_patch -install
2. Individual should receive a notice that the patch has successfully been installed.

Section 3 - Configuring

1. Given a supported UNIX/Linux operating system and a user with proper permissions, configure and verify Netcool environmental variables, so that the environmental variables have been configured.

With emphasis on performing the following steps:
1. Start the UNIX text editor.
2. Edit SYSTEM HOME PROFILE/etc/profile
3. Define Netcool Environment Variables: $NCHOME; $OMNIHOME; $NCLICENSE; $NETCOOL_LICENSE-FILE; LD.LIBRARY_PATH (opt); $PATH (opt.); $LANG (if required).
4. Netcool users must source this file when they login.


2. Given a UNIX/Linux OS, root owns Netcool directory and root access, configure system users and groups, so that the root user belongs to the new admin group.

With emphasis on performing the following steps:
1. Create nco admin group on operating system.
2. Add root user to the nco admin group within /etc/group.


3. Given OMNIbus V7.1 is installed on UNIX/Linux, configure OMNIbus communications, so that communications are configured.

With emphasis on performing the following steps:
1. Edit: $OMNIHOME/ETC/OMNI.DAT and replace "OMNIHOST" with local servers hostname.
2. Run $NCHOME/BIN/NCO_IGEN.


4. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environmental variables have been set on a supported Windows server, very OMNIbus communications, so that OMNIbus communications are available.

With emphasis on performing the following steps:
1. Run the Netcool Server Editor. Run ->All Programs->Netcool OMNIBUS-> System Utilities -> Server Editor.
2. Highlight appropriate ObjectServer and select 'test" check for "servers available " window.


5. Given and OMNIbus install, create object server using $OMNIHOME/bin/nco_dbinit, add a sever entry for the object server to %NCHOME/etc/omni.dat, run $NCHOME/bin/nco_igen and configure an ObjectServer instance, so that an ObjectServer has been created and an instance configured.

With emphasis on performing the following steps:
1. Open a command line and run $OMNIHOME/bin/nco_dbinit -server name.
2. Edit %NCHOME/etc/omni.dat file and set the ObjectServer name and post.
3. Run $NCHOME/bin/nco_igen.


6. Given the Netcool License Server is installed, start the license server and verify the license server is running by printing the licenses using nc_print_license , so that the license server is available.

With emphasis on performing the following steps:
1. Run $NCHOME/license/bin/nc_start_license.
2. Run $NCHOME/bin/nc_print_license to check if the License Server is running. .


7. Given that the license server and OMNIbus are installed on UNIX/Linux, start the ObjectServer, run nco_ping to start an ObjectServer and to verify that ObjectServer is running, so that the ObjectServer is available.

With emphasis on performing the following steps:
1. Run $NCHOME/omnibus/bin/nco_objserv - name .
2. Verify the ObjectServer is running by using the the $NCHOME/omnibus/bin/nco_ping - server .


8. Given and ObjectServer is installed and running on a supported Unix/Linux OS, and a license server is running with the appropriate licenses, start and verify a local event list, so that local event lists can connect to the local ObjectServer.

With emphasis on performing the following steps:
1. Launch event list (nco).
2. enter User name and password.
3. Verify event list connects to the ObjectServer.


9. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environmental variable have been set on a support Windows server/desktop, install the remote desktop, so that the remote desktop can connect to the ObjectServer.

With emphasis on performing the following steps:
1. Run the OMNIbus install package.
2. Accept the license agreement.
3. Choose the install directory.
4. Identify the License Server.
5. Define the vvalidObjectServer.
6. Choose custom configuration versus complete.
7. Deselect every program feature: ObjectServer; Process Agent; Proxy; Gateways; Conf Pack; Administrator. @Verify that only desktop is selected.
8. Click the Installation button.
9. Reboot the desktop.
10. LLaunchthe event list and log into the ObjectServer.


10. Given an OMNIbus install, edit the probe properties file, set the SERVER property to the name of the ObjectServer and configure a probe to connect to an ObjectServer, so that the Probe is configured.

With emphasis on performing the following steps:
1. Open the Probe properties file.
2. Set the server property to the name of the ObjectServer.


11. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environmental variables have been set and sourced on a supported UNIX/Linux server, and a probe package installed, start and verify the probes, so that the probes are running and tested.

With emphasis on performing the following steps:
1. Modify the simnet.property files. Verify the ObjectServer target $OOMNIHOME/ARCH>/PROBES/.
2. Modify rules file (simnet.rules) to iincludethe host system name in the manager field.
3. Start the probe using the command line (nco_p_siment).
4. Check process list to verify probe is running.
5. Launch the event list and verify probe events in the ObjectServer and verify events parsed correctly.
6. Check for log file errors.


12. Given OMNIbus is installed, configure a unidirectional gateway, so that the unidirectional gateway has been configured.

With emphasis on performing the following steps:
1. Create a directory for gateway files ex: $OMNIHOME/gates/UNI_GATE.
2. Copy all files from $OMNIHOME/gates/oobjserv_unito $OMNIHOME/gates/UNI_GATE.
3. Edit $OMNIHOME/gates?UNI/objserv.uniprop. File and set the following properties: Gate.MapFile, Gate.Ready.Server, Gate.Ready.Tbl.Trplivsyr Def filed, Gate.Startup Cmd File, & Gate.Writer.Server.
4. Copy $OMNIHOME/gates/UNI/objserv_uni.props to $OMNIHOME/etc/UNI_GATES.props.
5. Add an entry for the gateway to the $NCHOME/etc/OMNI.dat file.
6. Run $NCHOME/bin/nco_igen.


13. Given OMNIbus is installed, the license server and the ObjectServer are running, start a ObjectServer gateway, update events on one ObjectServer, verify that the events change similarly on the other ObjectServer to start and very the ObjectServer gateway.

With emphasis on performing the following steps:
1. Start a ObjectServer gateway using $OMNIHOME/bin/nnco_g_objserv_uni- name uni or $OMNIHOME/bin/nco_g_objserv_bin - name BIGATE.
2. Verify that the gateway is working by deleting and or modifying an even on the one ObjectServer and checking to see that the modification is made on the other ObjectServer.


14. Given OMNIbus is installed add a server entry for nco_pa in omni.dat, for nco_igen, edit nco_pa.conf, set the hostname and name of ObjectServer in nco_pa.conf and configure process control, so that process control is configured.

With emphasis on performing the following steps:
1. Open $NCHOME/OMNIbus/etc/nco_pa.conf file.
2. Change the name of the ObjectServer from NCOMS (if different).
3. Set the OMNIhost value to the hostname of the local machine under nco_routing entry.
4. Set user and password values under nco_routing if using secure mode, else delete the user and password values.
5. Add an entry to $NCHOME/etc/omnidat for nco_pa and run $NCHOME/bin/nco_igen.


15. Given OMNIbus is installed, process control is configured, run nco_pad, verify PA status using nco_pa_status to start process control and verify that process control is available and running.

With emphasis on performing the following steps:
1. Run $NCHOME/OMNIbus/bin/nco.pad.
2. Run $NCHOME/OMNIbus/bin/nco_pa status - server NCO_PA.
3. Manually kill one fofthe running processes using 'kill pid where pid is the process id of the process that was killed.
4. Run $NCHOME/OMNIbus/bin/nco_pa_status -server NCO_PA to verify that the killed process is running with a different process ID.


16. Given OMNIbus is installed on UNIX/Linux and root level access has been granted, configure, run and verify the startup scripts, so that start-up scripts have been configured and verified.

With emphasis on performing the following steps:
1. Execute the start-up script install script install.
2. Verify the creation of symbolic links.
3. Input/verify the process control name.
4. Select secure mode or not.
5. Enter a value for the netcool_license_file variable. Save the file.
6. Start nco script via the command line nco start.
7. Verify that the process control has started.
8. Run nco stop. Verify nco_pad has stopped.


17. Given an OMNIbus install, copy all gateway files from $OMNIHOME/gate/objserv-bi to a new directory, configure objserv-bi.props file, configure a server entry for the bi-directional gateway and create a bi-directional gateway between two ObjectServers, so that bi-directional gateway is configured.

With emphasis on performing the following steps:
1. Create a directory for ggatewayfiles. Example: $OMNIHOME/gates/BI_GATE.
2. Copy all files from $OMNIHOME/gates/objserv_bi to $OMNIHOME/gates/BI-GATE.
3. Edit $OMNIHOME/gates/BIGATE/objserv_bi.props and set the following properties: Gate.MapFile; Gate.Startkeys CMDFile; Gate.objectserverA.Server; Gate.ObjectServerA.TBLREplicate Def file; Gate.ObjectServerB.Server; Gate.ObjectServerB.TblReplicate DefFile.
4. Copy $OMNIHOME/gates/BIGATE/objserv_bi.props to $OMNIHOME/etc/BI_GATE.props
5. Edit $NCHOME/etc/omni.dat and add an entry for BI_GATE.
6. Run $NCHOME/bin/nco_igen.


18. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environmental variables have been set, add a user so that users are created.

With emphasis on performing the following steps:
1. From the main OMNIbus Administrator window, select the "user"tab and then select "user".
2. Click the "Add User" icon in the toolbar.
3. Enter a Name and Select an unused User ID.
4. Enter a Full Name.
5. Put a check in the "Create Conversion" ccheckbox
6. From the "Groups" tab, double-click Administrator to assign the administrator role. Click "OK".


19. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environmental variables have been set, create a view based on the statement of work, so that an event view has been created.

With emphasis on performing the following steps:
1. Launch View Builder from the Event List.
2. Select Filet --> New.
3. Enter View Name.
4. From Available Field pane select Node, Severity, and Summary.
5. From Available Sort Fields pane select Severity.
6. In the Sorted by pane, double-click the Severity icon to set sort order to descending order.
7. Click Apply.
8. Click Close.
9. Click File --> Save from Main Event List window.


20. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, utilize the Administrator GUI to create a Filter using the Desktop client, so that an event filter has been set.

With emphasis on performing the following steps:
1. Click Filter Builder button on Sub-Event List.
2. Click File --> New.
3. Provide Filter Name.
4. Select Severity from the Column drop down menu.
5. Select Greater than or Equal to from Operator drop down.
6. Select Minor (#) from Value drop down menu.
7. Click Apply.
8. Click File --> Save from the Main Event List window.


21. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, using the Administrator GUI to add a restriction filter, so that a restriction filter has been added.

With emphasis on performing the following steps:
1. From the main OMNIbus Administrator window, select the "Users" tab and then select Restriction Filters.
2. Select Add Restriction Filter from the toolbar.
3. Assign a Name to the filter.
4. Enter the filter criteria.
5. Click OK.


22. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, create a new menu, so that a menu is created.

With emphasis on performing the following steps:
1. From the Menu tab select Add New Item within the Configuration Manager GUI.
2. Select Menu Item Type, Tool, and Title, then click OK.


23. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, using the Administrator GUI create a new database field, so that a new database field has been created.

With emphasis on performing the following steps:
1. Select the System tab from the Administrator GUI.
2. Select Databases.
3. Select Databases Alerts and Table Status.
4. Select Add Column icon from the menu.
5. Enter Column Name, Data Type.
6. Click OK.


24. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, using the Administrator GUI add a tool, so that a tool has been added.

With emphasis on performing the following steps:
1. Within the Tools menu, click Add Tool.
2. Enter a Name.
3. Select Enter RRelevantTool Instructions.
4. Click OK.


25. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, using the Administrator GUI create a trigger, so that a trigger has been created.

With emphasis on performing the following steps:
1. Select DB Trigger.
2. Select Trigger Group.
3. Enter Trigger Name.
4. Set Trigger Priority.
5. Set Action on Delete.
6. Set Apply To pane to Statement.
7. Enter SQL code for action. Begin Write into dellogs1 values ('The following row was deleted at; getdate (), old.Node, old.Summary); End
8. Enable Trigger.
9. Click OK.


26. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, the ObjectServer is running, customize the Rules file, so that a customized probe rules file is available.

With emphasis on performing the following steps:
1. Open probe rules file with editor.
2. Create a temporary element to hold a value extracted from @Summary.
3. Assign a probe property to the @Summary field.
4. Add a "switch" statement to execute a rule based on node name.
5. Use an "include" statement to include a new rule file segment.
6. Make a change so that @Alert Key is updated on deduplication.
7. Discard events with the word "test" in the @Summary field.
8. Create a lookup table to look up department name based on node name.
9. Turn on probe details if @Summary=unknown.
10. Test the syntax of the new rules file and debug.
11. Update the probe rules file without stopping the probe.


27. Given an OMNIbus install, configure the primary ObjectServer, create a backup ObjectServer, set the backup ObjectServer property, configure a bi-directional gateway, add server entries for the primary backup ObjectServer and create a failover architecture, so that failover architecture is configured.

With emphasis on performing the following steps:
1. On the primary ObjectServer host, create the primary ObjectServer.
2. On the backup ObjectServer host, create the backup ObjectServer.
3. Edit $OMNIHOME/etc/BACKUP.props and set the Backup ObjectServer property to 'True'.
4. Configure a bi-directional gateway between the primary and backup ObjectServer.
5. On the primary ObjectServer host, configure $NCHOME/etc/omni.dat for the primary and backup ObjectServer entries.
6. On the primary ObjectServer host run $NCHOME/bin/nco_igen. Copy $NCHOME/etc/interfaces.APICH file to the backup ObjectServer host.


28. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, add entries to OMNI.dat for primary and desktop ObjectServer, copy the interface file from the primary ObjectServer host to the desktop ObjectServer host, configure the desktop ObjectServer, configure a unidirectional gateway between the primary and desktop ObjectServer to set up desktop architecture, so that the desktop architecture is configured.

With emphasis on performing the following steps:
1. On the primary ObjectSErver host edit $NCHOME/etc/omni.dat and add entries for the primary and desktop ObjectServers.
2. Run $NCHOME/bin/nco_igen copy $NCHOME/etc/interfaces.ARCH file from the primary OObjectServerhost to the desktop ObjectServer host.
3. Create and configure the primary ObjectServer.
4. Create the desktop ObjectServer using $OMNIHOME/bin/nco_dbinit -desktopserver -server DESKOS.
5. Start the desktop ObjectServer.
6. Using $OMNIHOME/bin/nco_sql insert the ffollowingrow in to the master national table or the DESKOS. (O, MASTEROS, 1).
7. Configure a uni-directional gateway between the primary ObjectServer and the desktop ObjectServer.


29. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, export configuration of the ObjectServer and import it into the ObjectServer uinthe nco_confpack, so that the ObjectServer configuration can be exported and imported.

With emphasis on performing the following steps:
1. Export NCOMSI configuration using: $OMNIHOME/bin/nco_confpack -export -server NCOMSI -package/tmp/NOCMSI_package.
2. Import NCOMSI configuration in to NCOMS2 using: $OMNIHOME/bin/nco_confpack -import -package/tmp/NCOMSI_package -server NCOMS2.


30. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environmental variables have been set, add a group, so that a group is added.

With emphasis on performing the following steps:
1. From the main OMNIbus Administrator window, select the Users tab and then select Groups.
2. Click the Add Group icon.
3. Assign a name to the group.
4. Assign an unused Group ID.
5. Assign a Role.
6. Click OK.


31. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, create a class, so that a class has been created.

With emphasis on performing the following steps:
1. Using the Configuration Manager, select Add Class from the Visual menu.
2. Assign an identifier.
3. Name the class.
4. Click OK.


32. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, create a role, so that a role is available.

With emphasis on performing the following steps:
1. Within the Configuration Manager select the Users tab.
2. Select Roles and Add New RRolemenu item.
3. Add Role name.
4. Assign Role Attributes.
5. Click Save.

Section 4 - Performance Tuning and Problem Determination

1. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, add devices to simnet.def file and run the simnet probe to generate test events using the simnet probe, so that test events are generated.

With emphasis on performing the following steps:
1. Edit $OMNIHOME/probes/ARCH/simnet.def file and add line device1 0 50 & device2 3 100.
2. Set the property in $OMNIHOME/probes/ARCH/simnet.props to $OMNIHOME/probes/ARCH/simnet.def.
3. Set the server property in $OMNIHOME/probes/ARCH/simnet.props to the name of the ObjectServer. Server: lt;NAMEgt;.
4. Start the simnet probe using $OMNIHOME/probes/nco_pnco_p_simnet/li>


2. Given a failover architecture, verify that the failover architecture is working, so that failover functionality has been confirmed.

With emphasis on performing the following steps:
1. Manually kill the Master ObjectSErver process using the kill command.
2. ConneConnectdesktop client to the backup ObjectServer using $OMNIHOME/bin/nco_event and check that the events are coming into the backup ObjectServer.
3. Restart the Master ObjectServer.
4. Connect the desktop client to the Master ObjectSErver using $OMNIHOME/bin/nco_event and check that the client indicates it is connected to the Master ObjectServer.


3. Given an OMNIbus install and the license server is configured and running, resolve licensing errors, so that icensing errors are resolved.

With emphasis on performing the following steps:
1. Verify that the environment varibvariableTCOOL_LICENSE_FILE is set correctly.
2. Verify that the license server host is reachable.
3. Verify that the license server is running on the license server host specified by NETCOOL_LICENSE_FILE environment variable.
4. Verify that the feature is supported by running $NCHOME/license/bin/nc_print_license on the license server host.
5. Verify th thte that theure license has not expired by running $NCHOME/license/bin/nc_print_license.


4. Given an OMNIbus installed and the license server is configured, determine why the ObjectServer does not start, so that the ObjectServer is running.

With emphasis on performing the following steps:
1. Check the environment variables NCHOME and OMNIHOME.
2. Check to makremake that the ObjectServer has been created using $OMNIHOME/bin/nco_dbinit.
3. Check to make sure that the entry for the ObjectServer exists in $NCHOME/etc/omni.dat and in the interfaces file.
4. Ensure that the port for the ObjectServer is not already in use.
5. Set the NETCOOL_LICENSE_FILE environment variable to point to the correct License Server.


5. Given an OMNIbus installed and the license server is configured, determine why probes do not connect, so that the probes are running.

With emphasis on performing the following steps:
1. Check probes log file.
2. Verify tha tthatNETCOOL_LICENSE_FILE is set correctly.
3. Verify that the server that the probe is connecting to is available.


6. Given an OMNIbus installed and the license server is configured, determine why the desktop does not start, so the that the desktop is running and connected to the ObjectServer.

With emphasis on performing the following steps:
1. Check and correct any licensing issues.
2. Ensure that X server settings are set correctly.
3. Ensure that the ObjectServer that the desktop is connecting to is running.


7. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environment variables have been set and sourced, users are complaining of slow response time, determine the reason for slow event list response, so that the problem can be resolved.

With emphasis on performing the following steps:
1. Check # of events.
2. Check OS profiles.
3. Check event rates.
4. Check # of desktops.
5. Check process on OS server.
6. Check resource usage of OS server, memory, CPU, & disk. (S0
7. Check network response times.
8. Check log files.
9. Check automations.
10. Check the number of journals and details.
11. Determine what other components are connected.


8. Given OMNIbus V7.1 has been installed and configured, a license server is running with the appropriate licenses, environment variables have been set, optimize system performance so that the ObjectServer performance is optimized.

With emphasis on performing the following steps:
1. Check frequency of triggers.
2. Check execution scope of triggers: once only, for each row.
3. Check number of details. Details($*).
4. Check SQL used in trigger for performance.
5. Check whether 'update via' is being used.
6. Check desktop filters.

Section 5 - Administering

1. Given a running and verified system, complete post implementation process including system backup, documentation, acceptance testing, so that customer acceptance can be obtained.

With emphasis on performing the following steps:
1. Backup the sytemsystemr the install.
2. Create system environment documentation.
3. Verify compliance with customer requirements.
4. Knowledge transfer to staff.
5. Demonstrate system to client.
6. Complete acceptance testing.
7. Customer sign-off.

Section 6 - Training

1. Given new users, provide formal training, so that users are educated on the new system.

With emphasis on performing the following steps:
1. Train users and administrators.