Test 000-019: IBM Tivoli Network Manager IP Edition V3.8 Implementation

Section 1: Planning

1. Given access to the customer technical staff and network information, determine the Network Manager requirements so that Network Manager requirements are documented and allow configuration to be carried out.


With emphasis on performing the following tasks:

1. Evaluate current Netcool components installed.
2. Request Access Control List (ACL) permission for the devices to be discovered
3. Perform a gap analysis against default functionality of the product.
4. Determine installation user (root, non-root).
5. Determine Federal Information Processing Standard (FIPS) compliance.
6. Gather SNMP Community String, including versions and applicable subnets, Telnet passwords, and DNS server details.
7. Gather network address space and topology.
8. Gather the EMS information for non-SNMP devices or network.
9. Gather network address space(s) for static Network Address Translation (NAT) gateways.
10. Determine the overall size of the network (ports, agents, etc).
11. Gather network equipment list. (indicate layer 2, 3 devices with name, management IP address, OID).
12. Determine any non-contiguous or unmanaged networks.
13. Determine routing protocols.
14. Gather detailed requirements for polling.
15. Gather detailed requirements for data collection.
16. Determine how to seed the discovery with customer.
17. Determine network devices for which detection must be restricted.
18. Determine any devices that must be removed from a completed discovery.
19. Determine the mgmt IP addresses of the Network Manager server switch and default router.
20. Determine discovery scheduling.
21. Set customer expectations regarding a timeline for completion.


2. Given customer network, determine if there is a firewall and NAT, calculate the number of interfaces, and determine the geographical division of network so that a detailed plan for failover and remote poller is available.


With emphasis on performing the following tasks:

1. Identify any restrictions imposed by firewall policies which prevent communication between IBM Tivoli Network Manager IP Edition (Tivoli Network Manager) and network devices.
2. Determine if multiple Tivoli Network Manager installations are required due to overlapping non-NATs address spaces.
3. Determine if a simple or distributed installation is required.
4. Determine the Netcool Common Information Model database type and location.
5. Determine the growth of network in percentage.
6. Identify the type of network (Multiprotocol Label Switching, WAN, MAN or LAN).
7. Determine if the network is divided into geographical locations.
8. Determine if FIPS is required based on location.
9. Get the disaster recovery location from the customer for failover.
10. Document the plan for failover and remote poller.


3. Given the network size (ports/interfaces) and architecture, determine the hardware and server specifications so that hardware and server are designed for a successful Tivoli Network Manager deployment.


With emphasis on performing the following tasks:

1. Review the detailed architecture plan.
2. Determine the hardware and type of operating system required.
3. Determine if remote pollers need to be used.
4. Calculate disk usage and verify that server meets memory requirements.
5. Determine a particular customized policy or polling interval for network devices.


4. Given customer high-level Architecture diagram/document, specify the type and location of the DB server and which port should be accessible to access DB from rest of Tivoli Network Manager server/components so that the server database is able to communicate with Tivoli Network Manager components/server.


With emphasis on performing the following tasks:

1. Review the High/Low Level Architecture diagram.
2. Review network dynamics.
3. Review the frequency of the backup and archive policy in conjunction with the fail back scenario.
4. Determine the geographical deficiencies for allocating servers, if any.
5. Determine the database to be used based on number of interfaces calculated and customer requirements.


5. Given installed Network Manager, enable the Collector Framework so that all devices are available on topology, which are imported by the Collector Framework after finishing the successful discovery.


With emphasis on performing the following tasks:

1. Configure the Collector.
2. Start the Collector.
3. Seed the Collector Finder.
4. Enable the Collector Agents.
5. Restart the NCP process and start the full or partial discovery.


6. Given access to Tivoli Network Manager 3.8 and requirements from the customer, determine data collection strategy and data polling definitions so that Tivoli Network Manager 3.8 configuration details are determined.


With emphasis on performing the following tasks:

1. Identify gap between the out of the box polls and the customer requirements.
2. Identify which poll definitions need to be created including details of the threshold and clear values, event description, and associated variables.
3. For each poll definition, determine the associated poll policy, including frequency, scope, filtering, and any required interface filtering.
4. For each poll definition, determine if the policy will be for fault only, historical data collection or for both.
5. Using information gathered about the network devices and logical topology, determine if remote pollers will be required.
6. If remote pollers are required, add these to the architecture or design.
7. Determine the database location for historical data collection.
8. Determine the average daily record numbers for historical data collection, and plan to configure the poll schema and database accordingly.


7. Given a requirement to install Tivoli Network Manager 3.8 and associated components, determine the suitable browser and JAVA plug-in so that the user environment supports the required browser and Java plug-ins to enable Tivoli Network Manager 3.8 to be used.


With emphasis on performing the following tasks:

1. Determine the currently supported browser and JVM/JRE versions for install and web application use.
2. Analyze the end user versions of both browser and JVM/JRE.
3. Perform a gap analysis.

Section 2: Installation

1. Given an installation environment, server, and user access method, determines if the IBM Tivoli Network Manager IP Edition (Tivoli Network Manager) installation prerequisites will affect the installation method so that a method for installation has been determined.


With emphasis on performing the following tasks:

1. Determine the type of installation that can be used (Launchpad, interactive console install or silent install method).
2. Ensure that the installation user PATH contains the required OS tools.
3. Ensure that any installation restrictions are understood and factored into the installation choice, for example the Windows Administrator user may not allow GUI access forcing a silent install etc.
4. If installing into a Solaris Zone, understand if it is a full or sparse zone and the implications has for the installation method used.
5. For Windows installation, ensure that a supported version of the Windows Installer is installed and useable by the installation user. If this is not, or it cannot be installed, the installation method will need to be via one of the console/silent options.
6. Understand the installation directory requirements on both UNIX and Windows platforms and understand this directory choice for future Tivoli product support, e.g. IBM Tivoli Business Service Manager (TBSM) support..


2. Given a set of customer requirements and a suitable Tivoli Network Manager architecture, establish which installation option to choose during the installation process so that an installation method has been determined.


With emphasis on performing the following tasks:

1. Determine the type of installation to use (Basic or Custom).
2. For both installations, determine the installation directory ensuring compliance for any other Tivoli integration (e.g. for TBSM the path cannot contain a space " ").
3. Enter a domain name. - [this is now an uppercase enforced name - different from 3.7]
4. Follow the installation options for either the custom or basic install.
5. Verify that a discovery will run based on the inputs during the installation process at the end of a basic or custom install.


3. Given the server operating system, topology database type, and hardware specifications, verify the component prerequisites so that component prerequisites are met.


With emphasis on performing the following tasks:

1. Verify the OS is supported.
2. Verify that additional OS configuration steps are made.
3. Verify that topology database is installed if using Oracle or DB2.
4. Verify that user has sufficient rights to install.
5. Verify the bandwidth for the discovery.


4. Given the architecture design documentation, determine the user access required for installation with directory permissions so that the required user permissions are met for installation.


With emphasis on performing the following tasks:

1. Determine with customer whether to install as root or non-root.
2. Obtain root access on temporary basis to perform certain post installation task.
3. Verify directory permissions.


5. Given a server for installation with UNIX or Windows operating system and an account with sufficient rights, review the hardware size as per the architecture documentation to determine if X windows is allowed and create the input files for silent installation so that the product is installed on required operating system.


With emphasis on performing the following tasks:

1. Review the hardware size as per the architecture documentation.
2. Determine the type of operating system.
3. Determine prerequisites for Launchpad installation.
4. Input the required data for the installation using default or custom values, or create silent input files for the installation.
5. Start the installation.
6. Verify the installation completed successfully.
7. Determine the post-installation tasks to be performed.


6. Given access to the command line on the installation system(s) and installation media, start the installation process so that a command line install is performed.


With emphasis on performing the following tasks:

1. Uncompress the installation media into a suitable location, using the appropriate tool for the installation OS.
2. Ensure the impact of any preinstallation tasks is understood. (e.g. turning off SELinux, enabling ssh etc.)
3. Perform the operating system specific pre-installations tasks.
4. Perform any required database preinstallation tasks.
5. Run the installation script with the -i console option.


7. Given access to a graphical interface on the installation system(s) and installation media, start the installation process so that a GUI installation is performed.


With emphasis on performing the following tasks:

1. Uncompress the installation media into a suitable location, using the appropriate tool for the installation OS.
2. Ensure the impact of any preinstallation tasks is understood.
3. Perform the operating system specific pre-installations tasks.
4. Perform any required database preinstallation tasks.
5. Run the launchpad.exe or launchpad.sh script.


8. Given a new installation of Tivoli Network Manager, perform the required post installation tasks so that the system is ready for configuration.


With emphasis on performing the following tasks:

1. Configure root or non-root access depending on the installation user.
2. Configure Federal Information Processing Standard for TIP and OMNIbus as required.
3. Configure Service-affecting Events.
4. Configure inter-server communications.
5. Configure the Webtop data source information.
6. Configure database libraries as needed.
7. Perform integration with common Tivoli components (TADDM, ITM, TBSM).
8. Perform any operating system dependant tasks.
9. Configure any network devices for default monitoring in conjunction with the customer.

Section 3: Configuration

1. Given location of OMNIbus server, the port on which it is listening with system user and password with OMNIbus root user password to configure secure or non-secure connection, get the SQL file from remote IBM Tivoli Network Manager IP Edition (Tivoli Network Manager) server to create the alerts.status table using nco_sql command so that the OMNIbus database is created for working with Tivoli Network Manager.


With emphasis on performing the following tasks:

1. Determine the port on which object server is listening.
2. Identify the system user and password through which OMNIbus is installed.
3. Obtain the root password of OMNIbus if any.
4. Configure encrypted access.
5. Review the connectivity from Tivoli Network Manager server to OMNIbus using telnet.
6. Get the SQL file from remote Tivoli Network Manager to create the alerts.status table.
7. Run the SQL script using nco_sql command to upload the file.
8. Configure remote OMNIbus which includes Netcool Knowledge Library.


2. Given a Tivoli Network Manager installation, a virtual ObjectServer pair, appropriate server information, and access to the appropriate configuration files, configure Tivoli Network Manager to communicate with a virtual ObjectServer failover pair.


With emphasis on performing the following tasks:

1. Determine the failover pair server and port information.
2. Create the OMNIbus interfaces file in a supported way to reflect this information.
3. Modify the Webtop data source information if required to reflect the failover pair.
4. Modify the Tivoli Network Manager process configuration files to ensure that the appropriate processes connect to the failover pair as required.
5. Ensure that the configuration is reflected on both the primary and failover Tivoli Network Manager servers if failover is enabled.


3. Given an installation of Tivoli Network Manager, domain information, access to the appropriate command line, and configuration GUIs, create a new Tivoli Network Manager domain with the default poll policies in place so that a new domain is created on Windows and UNIX with the default polling policies.


With emphasis on performing the following tasks:

1. Determine domain information.
2. Determine database login information.
3. Copy the appropriate default configuration files to domain specific versions as required.
4. Modify the configuration files to reflect domain and database information.
5. Create the windows services.
6. Use the domain_create.pl script to register the domain within Netcool Common Information Model (NCIM) and populate the domain with the default polls.
7. Modify automated startup scripts to automatically start the domain if required.
8. Configure the discovery information for the domain as required.


4. Given the Architecture doc, configure the remote DB so that it is accessible from various Tivoli Network Manager components.


With emphasis on performing the following tasks:

1. Check the type of database.
2. Verify database server is up and running.
3. Verify Privileged Access to Database to create the NCIM DB.
4. Create table schema with the script provided with the Tivoli Network Manager.
5. Verify required port should be accessible from the other Netcool component.
6. Perform any database library actions necessary.


5. Given that Tivoli Network Manager is installed, configure TIP so that a user is created and defined with sufficient privileges.


With emphasis on performing the following tasks:

1. Access the Web Interface and enter the Tivoli Network Manager admin credentials.
2. From the navigation pane, click Manage Users.
3. Create a new user defining appropriate parameters.
4. Assign the user to a group.
5. Click Group Membership and assigned required group.
6. Define the role for sufficient privileges.


6. Given that a user is logged in with the appropriate Network Manager administration rights to the TIP, select the Network Discovery Configuration and enter the appropriate information, so that a discovery is scoped.


With emphasis on performing the following tasks:

1. Log in to TIP.
2. Click Discovery-> Network Discovery Configuration
3. Select Scope tab.
4. Select Scoped Discovery option.
5. Specify one or more subnets to use for scoping by clicking New and typing an IP address and a netmask.
6. Determine to include or exclude the subnet.
7. Determine whether to include the subnet in the ping seed list.
8. Click OK.
9. Click the save icon.


7. Given access to the Tivoli Integrated Portal and a user with sufficient privilege, access the Tivoli Network Manager Discovery Configuration panel and enter the appropriate information to seed the discovery with the File finder, Ping finder or both so that a file or Ping finder seed file is created.


With emphasis on performing the following tasks:

1. Log in to the TIP.
2. Click Discovery-> Network Discovery Configuration. From the Domain list, select the required domain.
3. To switch off the Ping finder or File finder, clear the Use Ping Finder in Discovery or Use File Finder in Discovery check boxes.
4. Add or edit a ping seed.
5. Complete the fields and click OK.
6. Add or edit a file seed.
7. Complete the fields and click OK.
8. Click the Save button to save the config.


8. Given a seed file and a discovery configured to use the seed file, configure the discovery process to only discover devices that are available in the seed file so that File finder is configured to the validate entries in the seed file before they are included in the discovery.


With emphasis on performing the following tasks:

1. Go to the Advanced tab in the Discovery configuration.
2. Enable the File finder verification.
3. Alternatively edit the DiscoSchema.DOMAIN.cfg file to enable the appropriate flag in the disco.config section.
4. Ensure that the Ping finder is configured to run.
5. Stop and start the discovery process to activate the new configuration.


9. Given access to devices, configure SNMP community string and telnet username and password, so that the devices can be browsed.


With emphasis on performing the following tasks:

1. Click Discovery -> Network Discovery Configuration. From the Domain list, select the required domain.
2. Click Passwords.
3. To add a new SNMP community string, click New and complete the appropriate fields on the SNMP Password Properties page.
4. Click Move Up and Move Down to arrange the SNMP community strings in to the order of most frequently-expected use, with the most frequently-used strings at the top of the list.
5. Click Save.
6. To add Telnet/ssh access information, click New and complete the appropriate fields on the Telnet Password Properties page.
7. Configure Telnet-privileged access mode properties.
8. Click OK. Click Save.


10. Given that Tivoli Network Manager is installed and running, select required discovery agents so that system is configured to run the appropriate agents during discovery.


With emphasis on performing the following tasks:

1. Launch and log in to TIP.
2. Navigate to Discovery -> Netowork Discovery Configuration
3. Select the required domain from the list.
4. Click on either "Full Discovery Agents" tab or "Partial Rediscover Agents" tab.
5. Select the check box next to the required agent.
6. Click the Save button.


11. Given the Architecture document and an understanding of the Network Address Translation (NAT) environment, configure discovery so that the NAT environment is discovered correctly.


With emphasis on performing the following tasks:

1. In the Discovery Configuration GUI, select the NAT tab.
2. Define appropriate settings in the NAT tab.
3. Click the Save button to save your settings.
4. Activate NAT for your discovery,
5. Click the Save button to save your settings.
6. Map the discovery scope zones to NAT address,
7. Verify that NAT addresses are set in the translations.NATAddressSpaceIds table.


12. Given that Tivoli Network Manager is installed, configure filters so that devices, which are passed to the filter criteria, would be interrogated or instantiated in the topology.


With emphasis on performing the following tasks:

1. Go to the Filter tab in Tivoli Network Manager admin configuration page.
2. Click Filter Library then Click Add Filter.
3. Define Filter Name and Filter Criteria and Save the changes.
4. Select Defined filter into Available Filter option then click Add Filter.
5. Save the Changes.


13. Given that a user is logged in with the appropriate Network Manager administration rights to the TIP, select the Network Discovery Configuration and enter the appropriate information, so that advanced options are configured.


With emphasis on performing the following tasks:

1. Log in to TIP.
2. Click Discovery-> Network Discovery Configuration
3. Select Advanced tab.
4. Configure the advanced settings.
5. Click the save icon.


14. Given the IP address and port on which the collector is running or listening, enable default collectors so that the default collectors are enabled and configured for discovery.


With emphasis on performing the following tasks:

1. Edit the collector configuration file appropriately.
2. Save the collector configuration file.
3. Start a collector by going to the relevant collector directory and issuing a command-line interface command.
4. Obtain the hostname and the port on which the collector is running/listening.
5. Edit the DiscoCollectorFinderSeeds.DOMAIN.cfg configuration file by appending an insert into the collectorFinder.collectorRules table.
6. In the Discovery Configuration GUI, select the Full Discovery Agents tab.
7. Select the appropriate agents by checking the box next to the agent.
8. Verify the configuration settings saved in the DiscoAgents.DOMAIN_NAME.cfg.


15. Given a list of devices not discovered correctly, configure an active object class so that the device is represented correctly.


With emphasis on performing the following tasks:

1. Determine the instantiate filter for the class (usually defined by the SNMP ObjectID).
2. Create the Active Object Class file in $PRECISION_HOME/aoc (%PRECISION_HOME\aoc on Windows).
3. Define the active_class which is the name the class will use NOT the file name.
4. Define the super_class for the class.
5. Define the instantiate rule for the class.
6. If the instantiate rule for this class is not a subset of the super_class (or hierarchically upwards), add the instantiate rule to all super_class levels.
7. Define the basic device type for this class (router, switch, node) which will be the base icon used in the GUI.
8. Run ncp_class -read_aocs_from aoc -domain XXXXX (where XXXXX is the domain name), and if any errors are reported, these should be rectified.
9. Stop and restart the ncp_class process. .
10. Stop and restart the ncp_model process.
11. Check if the new class has been applied to the intended devices.
12. Force an update from model to Netcool Common Information Model (NCIM) for the specified class.
13. If required, modify the topoviz.properties file to reflect any icon changes for the new class.


16. Given the SNMP variable that contains requested data, modify the appropriate agent definition file so that agent is able to retrieve extra data during discovery.


With emphasis on performing the following tasks:

1. Determine which entity that records the data should be added.
2. Find appropriate agent definition in $NCHOME/precision/disco/agents.
3. Edit the agent definition and change type to DiscoCombinedAgent.
4. Create Entries for DiscoAgentMediationFilter, DiscoAgentMediationLayer, and DiscoAgentProcessingLayer.
5. Add DiscoAgentProcLayerAddTags and DiscoAgentProcLayerAddLocalTags.


17. Given the Tivoli Network Manager environment, configure the polling and historical collector for the Network Devices so that required Polling Definitions are configured and reports are available for the configured historical Data collection.


With emphasis on performing the following tasks:

1. Click Administration-> Network Polling and scroll to the Configure Poll Definitions page.
2. Click Add New Row. The New Poll Definition Type Selection page is displayed.
3. Select Generic Threshold from the list and click OK.
4. In the Poll Definition Editor, under the General tab, complete the General Properties fields.
5. Click the Trigger Threshold tab. Build the threshold using the Basic tab or the Advanced tab.
6. Specify the message that is displayed in the Active Event List (AEL) for the generated event.
7. Click the Clear Threshold tab. Build the formula that specifies the threshold by using either the Basic or Advanced tab.
8. Specify the message that is displayed in the AEL for the generated event.
9. Click Save, then click OK.
10. Verify the poll definition is added to the bottom of the list.
11. Click Administration -> Network Polling and navigate to the "Configure Poll Policy" page
12. Click Add New Row.
13. Complete the policy Name and Interval fields, and select the poll definition to use.
14. Enable the poll, select the "Store poll data" checkbox, and assign the policy to the appropriate poller if more than one poller is registered.
15. Define the scope for the poll based on the classes of device to be polled.
16. Define a device and interface filter to further narrow down the scope of the poll.
17. Save the policy.


18. Given an existing poll definition and access to the appropriate configuration file, configure the Tivoli Network Manager gateway so that a named poll is passed correctly from the Tivoli Network Manager gateway for Root Cause Analysis (RCA).


With emphasis on performing the following tasks:

1. Determine the EventID of the poll either using the GUI or using OQL.
2. Modify the gateway schema file to include an entry representing this EventID with the appropriate precedence vandEventMap values.
3. Ensure that the event will be processed correctly by the default Precision Monitor RCA event map (based on polled EntityID).
4. If required, create a new event map to handle the RCA event correctly.
5. Ensure that the gateway process uses the new configuration.


19. Given the Tivoli Network Manager server or alternative IP address, ensure RCA is configured correctly so that RCA will work after successful discovery.


With emphasis on performing the following tasks:

1. Select Tivoli Network Manager administration page and Click the Discovery Configuration.
2. Click the Scope.
3. Add Tivoli Network Manager server IP address and subnet mask and check the box for PING Seed.

OR
Edit the NcoGateSchema.cfg file and Set the $NcpServerEntity field with Tivoli Network Manager server or alternative IP Address under config.defaults.
4. Save the Configuration.
5. Restart the discovery if the scope has changed or restart the ncp_ncogate.


20. Given some additional data in the discovery and sufficient user privileges, modify the Tivoli Network Manager configuration files to allow the additional data to be displayed in the structure browser.


With emphasis on performing the following tasks:

1. Determine the topology attribute that needs to be included in the Structure browser using OQL and the model service.
2. Determine the entity type the attribute is held against.
3. Log in as a user with sufficient privilege to edit the $NCHOME/etc/precision/DbEntityDetails.cfg file for the domain.
4. Modify the contents of the DbEntityDetails file to map the topology attribute to a suitable entity details name.
5. Ensure that these attributes exist in the model topology and if so, stop and restart the model process, and if required, ensure model contents are transferred to NCIM.
6. If the attributes do not exist, ensure that these will be picked up during the next discovery process, and run the discovery as usual.


21. Given a discovered network and additional data that is required to be partitioned on, appropriate command line privileges to edit Tivoli Network Manager config files, and a suitable database login to modify NCIM tables and modify the configuration of Tivoli Network Manager so that non-standard data is available to create Network Views from.


With emphasis on performing the following tasks:

1. Determine the data that is required to be partitioned on.
2. Determine where this data is held in the topology database, for example at a chassis or interface level.
3. Determine the data type for each new topology attribute, for example text, integer etc.
4. Extend the NCIM database tables to include a new table that will hold the new additional data.
5. Modify the DbEntityDetails.DOMAIN.cfg file to include an EntityMap allowing population of the new NCIM table with the required topology data.
6. Modify the ncimMetaData.xml file to ensure that the extend NCIM table is available for use in Topoviz.
7. Stop and start the model process to force a population of the new data into NCIM.
8. Ensure that Topoviz has picked up the new ncimMetaData by cycling the TIP/Topoviz.
9. Verify the data is available in the network views.


22. Given that Tivoli Network Manager and the dependant Netcool components are installed and running and admin access to the command line is available, perform configuration tasks so that a new icon is available for a class of device.


With emphasis on performing the following tasks:

1. Create icon as an image file.
2. Copy icon to appropriate directory.
3. Add the appropriate line to the topoviz.properties file.
4. Save the topoviz.properties file.


23. Given a Tivoli Network Manager installation and a third-party Web-based tool, configure Tivoli Network Manager so that the third-party tool is available as a context sensitive right-click menu tool form the topology views.


With emphasis on performing the following tasks:

1. Determine the URL for launching the tool, including any encoded parameters that need to be passed from the entity.
2. Determine the Tivoli Network Manager core tool attributes.
3. Determine the context for launching the tool based on the available attributes.
4. Determine the security contexts for launching the tool.
5. Determine the menu the tool will run from.
6. Edit the tool and menu XML config files to incorporate the tool.
7. Stop and start TIP.
8. Verify that the new tool is available and launches correctly in the correct object and security context, with the expected parameters being passed.


24. Given the operation setup of the Tivoli Network Manager and the user requirements. create and configure the network view so that the required network view would be available for the specific user.


With emphasis on performing the following tasks:

1. Navigate to the Network View Wizard.
2. Select the type of view and select the appropriate parameters.
3. Populate the filters for this view.
4. Copy or move the view to a specific user.


25. Given a running OMNIbus environment, configure reports so that reports are available.


With emphasis on performing the following tasks:

1. Click Reporting -> Common Reporting in the navigation pane of the Tivoli Integrated Portal.
2. In a command prompt, change directory to /products/tnm/bin (use backslashes for Windows), and run the itnm_currentStatus command against the Object Server.
3. Execute the command itnm_currentStatus -host -user root -password .
4. Generate the reports from the GUI.
5. Execute the script /products/tnm/output.


26. Given that a communication port for rendezvous is assigned and correctly forwarded in firewall, configure a fixed port for rendezvous communication so that failover communication can be made on assigned port.


With emphasis on performing the following tasks:

1. On primary server, start ncp_virtual domain.
2. Edit the $NCHOME/etc/precision/ServiceData.cfg file.
3. Edit the VIRTUALDOMAIN reference and set DYNAMIC: YES to NO and change the PORT property to a valid port.
4. Copy line and paste the line in backupservers $NCHOME/etc/precision/ServiceData.cfg file.


27. Given a default installation of Tivoli Network Manager, enable the Service-affecting Events (SAE) functionality and configure it to use a named topology field within the resulting SAE events so that the SAE process is enabled, the ObjectServer is configured to accept Service data and the SAE events contain the named topology field.


With emphasis on performing the following tasks:

1. Enable the SAE process to be started automatically.
2. Ensure that the ObjectServer is configured to accept Service Data from the SAE process.
3. Modify the SAE configuration file to use the named topology attribute as the CustomerName field within the SAE events.
4. Ensure that the SAE process is started.


28. Given an existing topology attribute and an existing ObjectServer event field, configure the Tivoli Network Manager gateway to enrich events with the topology attribute in the ObjectServer field so that the Tivoli Network Manager gateway is configured to enrich all events with a named topology attribute into a named ObjectServer field.


With emphasis on performing the following tasks:

1. Identify the topology attribute's location within the topology object.
2. Determine if the attribute type is compatible with the destination ObjectServer field.
3. Modify the Tivoli Network Manager gateway configuration to include a mapping from the topology attribute to the ObjectServer field in the appropriate section of the configuration file.
4. Ensure that the Tivoli Network Manager gateway uses the new configuration.
5. Validate that ObjectServer events are enriched with the topology attribute once they have passed through the Tivoli Network Manager gateway.

Section 4: Administration

1. Given a working installation of Network Manager and sufficient user privileges, use the command line or wizard to uninstall IBM Tivoli Network Manager IP Edition (Tivoli Network Manager) so that the required components will be uninstalled.


With emphasis on performing the following tasks:

1. On a Windows installation remove all the installed domains prior to the uninstall using the %ITNM_HOME%\bin\ncp_install_services -domain -remove for each installed domain.
2. Stop all running Tivoli Network Manager processes either using the services (Windows) or the itnm_stop script (UNIX).
3. Run the uninstall script Uninstall_ITNM _sh (UNIX) or Uninstall_ITNM.exe.
4. Use the correct command line parameter to this script to change from a GUI to command line uninstall.
1. If you installed in other than GUI mode and wanted to uninstall using the GUI use -i swing
2. If you installed in GUI mode and wanted to uninstall using the command line use -i console
5. Follow the on screen prompts to remove the components you require.
6. To uninstall in silent mode Edit the appropriate options in ITNM-uninstall-response.txt.
7. Save the ITNM-uninstall-response.txt file.
8. Stop all running Network Manager processes using the itnm_stop.
9. Run the uninstall script.


2. Given a time the discovery should run, configure the appropriate stitcher so that discovery is started on given time.


With emphasis on performing the following tasks:

1. Edit the $NCHOME/precision/disco/stichers/FullDiscovery.stch file.
2. Uncomment the appropriate ActOnTimedTrigger line and set values.
3. Set the time the discovery should run.
4. Save the file.


3. Given appropriate access to the GUI, the appropriate tool security privilege, and access to the Tivoli Network Manager configuration files, unmanage a topology entity using the GUI and permanently unmanage a filtered set of entities via the discovery configuration files so that an entity unmanaged via the GUI/command line and a set of entities are unmanaged automatically via the discovery process.


With emphasis on performing the following tasks:

1. Using the hop view, or network view, select a topology entity and unmanage it using the right click menu tools.
2. Using the Structure browser, select a topology entity and unmanage it using the drop down menu tool.
3. Using the command line, use the Unmanage.pl scripts to unmanage a node.
4. Modify the appropriate discovery stitcher to permanently unmanage a set of entities (interfaces) according to the defined filter condition.


4. Given the operational setup of the Tivoli Network Manager, start, stop, and verify the status of discovery process so that the discovery process is managed and verified.


With emphasis on performing the following tasks:

1. Start discovery process from the command line or the GUI.
2. Stop discovery process from the command line or the GUI.
3. Verify the status of disco using Discovery ncp_oql and the Web OQL interface.


5. Given that Tivoli Network Manager core components are installed, make changes into CtrlServices.domain.cfg file, so that Tivoli Network Manager processes are started automatically.


With emphasis on performing the following tasks:

1. Verify and perform the appropriate task on user privileges to configure the automatic startup of the processes.
2. Back up $NCHOME/etc/precision/CtrlServices.cfg file.
3. Save a copy of the CtrlServices.cfg file with the domain name appended to the filename, for example, CtrlServices.Domain.cfg.
4. Edit the CtrlServices.Domain.cfg file according to the requirement.
5. Execute the "create_startup_scripts.sh" in UNIX environment. It will create startup ncp script into init.d directory on UNIX environment.

OR
for Windows Click Start-> Control Panel-> Administrative Tools-> Services.
6. Select ncp_ctrl for domain DOMAIN from the Services list.
7. Select Properties from the Action menu. Select the General tab.
8. Change the startup type to Automatic.
9. Leave all other Network Manager services as manual startups.


6. Given an installation of Tivoli Network Manager, appropriate access to the Tivoli Network Manager discovery configuration files, and a list of unconnected entities that need connecting, configure the PresetLayer stitcher mechanism so that the unconnected devices are connected and the model database is populated with this information.


With emphasis on performing the following tasks:

1. Determine the entity names of the entities to be connected.
2. Determine if these entity names are liable to change with each discovery.
3. Modify the PresetLayer stitcher to include the desired connections, add any additional entities, and provide the correct containment.
4. Enable the PresetLayer stitcher using via the correct calling stitcher.
5. Ensure that the connections defined within PresetLayer assume the correct priority in the final topology.
6. Pass the topology to the model process including the newly defined PresetLayer connections.
7. Verify that the connections appear in the appropriate topology map.


7. Given that Tivoli Network Manager is installed and access to the Tivoli Network Manager database is available, administer Tivoli Network Manager database so that administration tasks can be performed.


With emphasis on performing the following tasks:

1. Configure access to the topology database.
2. Create the Tivoli Network Manager database schemas by provided scripts.
3. Remove the Tivoli Network Manager database.
4. Query the Tivoli Network Manager database.
5. Retrieve data about a device.


8. Given a discovered topology, select the appropriate devices for the rediscovery and set the partial agents so that rediscovery of devices could be performed successfully.


With emphasis on performing the following tasks:

1. Verify if the partial discovery agents are configured.
2. Select the devices to be rediscovered from HOP View or Network View and right-click, and Rediscover Node(s). Or
3. Use the Discovery Configuration GUI Rediscovery button to enter devices or subnets to be discovered.
4. Complete the basic and advanced fields if required.
5. Click Go to launch the rediscovery.


9. Given a MIB file and access to the TIP Server, make the appropriate actions so that MIB information is successfully written to the Netcool Common Information Model (NCIM) database.


With emphasis on performing the following tasks:

1. Verify that the MIB file has the correct sufflix.
2. Copy the MIB file to the $NCHOME/precision/mib directory of the TIP server containing the Tivoli Network Manager web application.
3. Edit the $NCHOME/etc/precision/MibDBLogin.cfg and verify that correct database credentials are used (m_UserName, m_Password).
4. Save the file.
5. Start the ncp_mib process by issuing ncp_mib command.
6. Verify that MIB has successfully loded by query the database table ncmib.mib_modulefor the MIB name : select * from ncmin.mib_modules where modulename = ‘MODULENAME';

Section 5: Performance Tuning and Problem Determinatin

1. Given the running setup of the IBM Tivoli Network Manager IP Edition (Tivoli Network Manager), verify the device can be contacted from Tivoli Network Manager so that the reason for which the device fails is known.


With emphasis on performing the following tasks:

1. Ping and verify the reach ability of the device from the Tivoli Network Manager server.
2. Verify the device was included in the finders.
3. From Tivoli Network Manager Web-console, use MIB browser to verify the SNMP connectivity from Tivoli Network Manager with the given SNMP credentials to device.
4. Verify that the device or IP address was passed to the post AssocAddress agents.
5. Verify the device is not being removed by discovery filters.
6. Verify that the collector is able to import the required device list from respective EMS/data source and those devices are accessible from Tivoli Network Manager.
7. Verify any Network Address Translation configuration.


2. Given a running OMNIbus environment, start the nco_p_ncpmonitor, ncogate, ncp_poller processes and enable debug level higher for these processes so that events are properly mapped on discovered devices.


With emphasis on performing the following tasks:

1. Check nco_p_ncpmonitor, ncp_ncogate, and ncp_poller processes are running.
2. Use kill -USR2 process_name for _p_ncpmonitor, ncp_ncogate, and ncp_poller processes.
3. Enable Debug level 4 for nco_p_ncpmonitor, ncp_ncogate, and ncp_poller processes.
4. Verify that events are receiving nco_p_ncpmonitor and ncp_poller processes into their respective log files.
5. Verify that nco_p_ncpmonitor and ncp_ncogate processes are connected to OMNIbus environment.
6. Verify that events are received by the ObjectServer.
7. Verify that incoming events are matching event map criteria defined into NcoGateSchema.cfg file in ncp_ncogate.domain.log
8. Verify that events are mapping on topology on discovered devices.


3. Given administrative access to Tivoli Network Manager system, perform configuration tasks so that the log levels of Tivoli Network Manager are changed.


With emphasis on performing the following tasks:

1. Connect with administrative privileges to the Tivoli Network Manager system.
2. Change at the needed level the debug parameters in the CtrlServices.DOMINIO.cfg file under the $NCHOME/etc/precision directory or use the kill -USR2 (Name of the process) command on a specific process as many times as the debug level desired.
3. Restart the ncp_ctrl processes if required.


4. Given the failing Tivoli Network Manager process or component and access to the Tivoli Network Manager server, locate the appropriate logfile so that problem can be identified.


With emphasis on performing the following tasks:

1. Locate the appropriate logfile.
2. Look for significant error messages.


5. Given completely installed product, verify the basic criteria, and based on the outcome, make the required changes, so that Tivoli Network Manager is connected with OMNIbus and TIP.


With emphasis on performing the following tasks:

1. Obtain the ObjectServer port and name on which it is running.
2. Verify the interfaces file.
3. Verify if the ObjectServer is running using nco_ping, ps -ef commands.
4. Verify if the /etc/hosts file is correct in the Operating system.
5. If remote installation of OMNIbus verifies whether two systems are able to communicate using Ping command and Telnet, the port object server is running from Tivoli Network Manager server.
6. Verify that the Tivoli Network Manager to OMNIbus processes have no error in their log files.
7. Verify if it is able to login into OMNIbus using nco_Sql.
8. If remote TIP installation verifies whether two systems are able to communicate using Ping command and Telnet, the port object server is running from Tivoli Network Manager server.


6. Given that Tivoli Network Manager is installed and the Tivoli Network Manager host is in the MODEL topology, determine why Tivoli Network Manager Root Cause Analysis (RCA) is not working, so that the reason for Root Cause problem is identified.


With emphasis on performing the following tasks:

1. Confirm that there is a contiguous path in the MODEL topology between the source and destination.
2. Check that the Gateway ncp_ncogate and the AMOS service ncp_f_amos are running.
3. If service or gateway is not running or cannot be started, review the log files in $NCHOME/log/precision.
4. Open an OMNIbus Event List and confirm that the events expected to partake in RCA contain the required data to pass across the Network Manager Gateway. (LocalNodeAlias and EventID are populated) and Type <> 2.
5. Confirm that the EventID field contains a valid EventMapName.
6. Open the NcoGateSchema.cfg file in $NCHOME/etc/precision, and confirm that the EventMapName is mapped to an ncpRuleName, and that SendForRCA is set to 1.
7. Check that the value for LocalNodeAlias in the event exists as an entity in topocache.entityByName using ncp_oql: select * from topoCache.entityByName where EntityName = ‘LocalNodeAlias';
8. Check that an Alert has been created in mojo.events using ncp_oql: select * from mojo.events where EntityName = ‘LocalNodeAlias';
9. Check if the Alert in mojo.events has been updated by the RCA engine.
10. If the alert is in mojo.events force synchronization by issuing a kill -HUP [PID] ncp_ncogate process, monitor the logs and search for the problem event and errors.
11. If the Alert has not been updated as expected by RCA, check how the event is being processed by the TopologicalAlertCorrelation rule set under $NCHOME/precision/amos/rca_rules.
12. If the Alert has been updated as expected by RCA, check the NcoGateSchema.cfg file to determine why the update has not been passed back to the OMNIbus Event List.


7. Given the operational setup of Tivoli Network Manager, configure the monitor probe to communicate with the Object server, and populate an event field with new data so that Tivoli Network Manager Monitor probe is able to communicate with ObjectServer.


With emphasis on performing the following tasks:

1. Ensure that the ObjectServer interfaces file contains the IP address or hostname of the ObjectServer server and the ObjectServer port number.
2. Modify the probe map file to include the new source variable name in the event.
3. Modify the probe rules file to include the new source variable in an appropriate event field.


8. Given that all Tivoli Network Manager processes are running and discovery configuration parameters are configured, demonstrate knowledge of the various phases of discovery, and the common databases used in troubleshooting discovery issues so that detailed information about the discovery processes is available.


With emphasis on performing the following tasks:

1. Determine which phase a discovery is using ncp_oql (not the GUI).
2. Determine if the discovery has cycled and what causes this.
3. Determine how many seeded addresses were found.
4. Determine how many devices were filtered by the Pre-Discovery filter.
5. Determine which agents are still running, and why.
6. Determine the neighbor data returned from a specific device using the agent returns tables.
7. Enable the PresetLayer stitcher and make it override all other connectivity.
8. Find out how many chassis objects will be in the final topology with a sysname like "lon".
9. After making changes to the PostScratchProcessing stitcher, rerun the stitcher and send the modified topology to model.


9. Given a requirement to enable discovery failover, configure the discovery to use failover via the GUI and via the configuration file so that discovery is configured via the GUI or the configuration file to work in failover mode for the next discovery.


With emphasis on performing the following tasks:

1. Navigate to the Advanced tab of the discovery configuration.
2. Select "Enable Discovery Failover".
3. Save the configuration and ensure that the discovery process will use it.
4. Alternatively modify the domain specific disco configuration file and ensure that failover is enabled.
5. Ensure the discovery will use this configuration.