Skip to main content

 
Professional certification

  >  
Certifications

  >  
Test information

Test 897: IBM Tivoli Network Manager IP Edition V3.7 Implementation


Overview Objectives Test Preparation

Section 1: Planning

  1. Given access to the customer, technical staff and discovery related information, obtain the Network Manager IP requirements from customer technical staff so that Network Manager IP requirements are documented and ready for configuration review. With emphasis on the following steps:
    1. Evaluate current Netcool components installed.
    2. Request access control list (ACL) permission for the devices to be discovered.
    3. Determine network access details.
    4. Discuss root level access.
    5. Gather SNMP Community String, include versions and applicable subnets, Telnet or SSH passwords, DNS server details.
    6. Gather network address space and topology.
    7. Gather network address space(s) for static NAT gateways.
    8. Determine the overall size of the network (ports, agents).
    9. Determine what agents to run for full discovery.
    10. Determine what agents to run for a partial rediscovery.
    11. Determine if out of band network exists.
    12. Determine if Advanced tab options will need to be configured.
    13. Gather network equipment list (indicate layer 2, 3 devices with name, management IP address, OID).
    14. Determine any non-contiguous or unmanaged networks.
    15. Determine routing protocols.
    16. Gather detailed requirements using polling.
    17. Determine how to see the discovery with the customer.
    18. Determine network devices for which detection must be restricted.
    19. Determine any devices that must be removed from a completed discovery.
    20. Determine the management IP addresses of the Network Manager server switch and default router.
    21. Set customer expectations regarding a timeline for completion.

  2. Given access to Network Manager IP and requirements from the customer, develop Network Manager configuration details so that Network Manager IP configuration details are determined. With emphasis on the following steps:
    1. Review and determine architecture (servers, database, failover, sizing).
    2. Identify the database location and access credentials.
    3. Define which agents are needed based upon the network equipment and management requirements.
    4. Define agents to be enabled for Full and Partial Discovery.
    5. Identify implications of not enabling specific agents.
    6. Determine integration points with other products.
    7. Determine server specifications.
    8. Determine the network discovery requirements.
    9. Verify and obtain licensing details.

Section 2: Installation

  1. Given that the server has been installed and base operating system is running, verify that the server meets predefined requirements, so that the hardware and operating system software prerequisites have been verified and met. With emphasis on the following steps:
    1. Verify that the latest OS patch sets are required have been installed as recommended in the Network Manager IP install guide.
    2. Verify that the server Operating System is listed under ‘Supported Platforms’ in Prerequisites for Installation section of the Install guide, one of the following: Solaris 9 and 10 for SPARC; Red Hat Enterprise Linux 3.0 and 4.0; SUSE Enterprise Linux 9 and 10; AIX 5.3; Windows 2003 Server
    3. Verify that the server meets MINIMUM system requirements under ‘Hardware Requirements’ in Prerequisites for Installation section of the Install guide
    4. Verify that the server meets MINIMUM memory requirements under ‘DISCO Memory Requirements’ in Prerequisites for Installation section of the Install guide
    5. Evaluate the Installation-specific requirements against the Prerequisites for Installation section ‘Hardware Requirements’.
    6. Verify that the server meets the newly evaluated requirements

      7. -If not using the default MySQL database for NCIM, verify the location of the database that NCIM will installed into.
    7. Verify the size of the database that NCIM will use with respect to the NCIM installation requirements.

      8. -If installing on AIX, install the Run-time libraries for IBM XLC/C++ version 8
      -If installing on AIX, enable Asynchronous I/O using the supplied procedure
    8. Review release notes for the particular sub-version of Network Manager 3.7 for any new updates.

  2. Given the Network Manager IP software available, architecture design provided to install all Network Manager IP components on a single server and environment variables set and sourced on this supported UNIX/Linux server running all required Netcool components as ‘non-root’ user, install all Network Manager IP components as this user on this server using console mode, so that all Network Manager components are installed on UNIX/Linux as non-root user using console mode to be run as either root or non-root user. With emphasis on the following steps:
    1. Log in to the server as non-root user.
    2. Go to the folder where Network Manager IP software is available.
    3. Extract available Network Manager IP software.
    4. Run ./INSTALL script with ‘–console’ option.
    5. Select installation folder (NCHOME).
    6. Accept end user software agreement.
    7. Select the appropriate components to be installed.
    8. Fill in the appropriate access credentials in the component installation properties (ObjectServer, Database, Security Manager, Webtop Datasource connection details, license server, NGF)
    9. Start the installation.
    10. Log in as root user and run the appropriate script to run Network Manager as root or non-root user.

  3. Given the Network Manager IP software available, architecture design provided to install all Network Manager IP components on a single server and environment variables set and sourced on this supported WINDOWS server running required Netcool components, install all Network Manager IP components on this server using console mode so that all Network Manager components are installed on windows using console option. With emphasis on the following steps:
    1. Log in to the server as ‘Administrator’ user.
    2. Using windows explorer go to the folder containing Network Manager software.
    3. Extract available Network Manager IP software.
    4. Go to Start Run type cmd.
    5. Go to the folder where Network Manager IP software is available using windows command line.
    6. Run Setup with ‘–console’ option.
    7. Accept end user software agreement.
    8. Select the appropriate components to be installed.
    9. Select installation folder (%NCHOME%).
    10. Fill in the appropriate access credentials in the component installation properties (ObjectServer, Database, Security Manager, Webtop Datasource connection details, license server, NGF)
    11. Start the installation.

  4. Given the Network Manager IP software is available and the architecture design provided to install all Network Manager IP components on a single server with environment variables set and sourced on this supported UNIX/Linux server running the required Netcool components as ‘non-root’ user, install all Network Manager IP components as this user on this server using GUI mode so that all Network Manager components are installed on UNIX/Linux as non-root user using GUI mode to be run as either root or non-root user. With emphasis on the following steps:
    1. Log in to the server as non-root user.
    2. Go to the folder where Network Manager IP software is available.
    3. Extract available Network Manager IP software.
    4. Export the DISPLAY for GUI installation.
    5. Run ./INSTALL script.
    6. Accept end user software agreement.
    7. Select installation folder (NCHOME).
    8. Select the Default installation option which installs MySQL Database, Core Component, Web Application, Webtop Integration and Webtools, Element Management Systems integration collectors.
    9. Fill in the appropriate access credentials in the component installation properties (ObjectServer, Database, Security Manager, Webtop Datasource connection details, license server, NGF)
    10. Select the database to host the NCIM Database instance and the database schema creations.
    11. Specify the name of the Network Manager IP domain.
    12. Review the selections.
    13. Start the installation.
    14. Log in as root user and run the appropriate script to run Network Manager as root or non-root user.

  5. Given the Network Manager IP software available, architecture design provided to install all Network Manager IP components on a single server and environment variables set on this supported WINDOWS server running the appropriate Netcool components, install all Network Manager IP components on this server using GUI mode so that all Network Manager IP components are installed on windows using GUI option. With emphasis on the following steps:
    1. Log in to the server as ‘Administrator’ user.
    2. Using windows explorer go to the folder containing Network Manager software. .
    3. Extract available Network Manager IP software.
    4. Double-click Setup.exe.
    5. Accept end user software agreement.
    6. Select the appropriate components to be installed.
    7. Select installation folder (%NCHOME%).
    8. Fill in the appropriate access credentials in the component installation properties (ObjectServer, Database, Security Manager, Webtop Datasource connection details, license server, NGF)
    9. Start the installation.

  6. Given Network Manager IP is installed and all other Tivoli Netcool components are running on a UNIX platform, verify the Network Manager IP Components and preferred database are installed and integrated with other Tivoli Netcool components so that the Network Manager IP installation is verified. With emphasis on the following steps:
    1. Log in to the UNIX server running the Tivoli Netcool products as the root user.
    2. Verify that the Tivoli Netcool components are installed using ‘$NCHOME/install/ncisetup –console’
    3. Verify that the Tivoli Netcool components are properly installed by referring to the setup installation log file in ‘$NCHOME/log/install/ncisetup. log’.
    4. Verify that interfaces. file contains connectivity entries for the Object Server.
    5. Start the installed components, log in the NGF and verify it is working.
    6. Verify that the $NCHOME/etc/precision directory contains domain-specific CtrlServices..cfg file.
    7. Start Network Manager and verify that the log files do not contain errors.

Section 3: Configuration

  1. Given a text editor and read/write permissions to the Network Manager configuration files, configure DISCO so that it will write to the default log file using the appropriate debug level. With emphasis on the following steps:
    1. Open the $NCHOME/etc/precision/CtrlServices..cfg file using a text editor.
    2. Locate the section for ncp_disco.
    3. Add the – discoOnStartup command line argument for ncp_disco.
    4. Set the option value to 1 for the discoOnStartup argument.
    5. Enter the file name using the absolute path for the new log file.
    6. Adjust the value for –debug to the appropriate level.
    7. Save the results and exit the text editor.

  2. Given Network Manager IP has been installed on a supported Windows Server platform create a new domain so that it is listed in the Windows Services. With emphasis on the following steps:
    1. Log in to the server as Administrator user.
    2. Using windows CMD.exe go to the folder containing ncp_perl.bat .
    3. Issue the command: ncp_perl.bat c:\ibm\netcool\precision\scripts\perl\scripts\domain_create.pl -domain TEST -password
    4. Issue the command: ncp_install_services.bat -domain TEST.

  3. Given proper login access for a UNIX server, login to UNIX server and verify $NCHOME/etc/precision/DbLogin.cfg contains required details and run the command domain_create.pl, so that a new domain named NEWDOMAIN is created and registered in NCIM database and the default poll policies are set up for NEWDOMAIN. With emphasis on the following steps:
    1. Log in to UNIX server.
    2. Verify $NCHOME/etc/precision/DbLogin.cfg already contains valid details.
    3. Run the command $NCHOME/precision/perl/bin/perl. $NCHOME/precision/scripts/perl/scripts/domain_create.pl -domain NEWDOMAIN -password .
    4. Verify the domain is created by checking the $NCHOME/etc/precision folder and logging in to the database.

  4. Given that a user is logged in with the appropriate Network Manager administration rights to the Netcool GUI Foundation, locate and select the Network Manager (IP) Admin selector, select the Discovery Configuration and enter the appropriate information, so that a discovery is seeded using the Ping Finder. With emphasis on the following steps:
    1. Log in to NGF.
    2. Select Network Manager (IP) Admin from page selector.
    3. Select Discovery Configuration Tab.
    4. Select Seed Tab.
    5. Check the Use Ping Finder in Discovery box.
    6. Click + to create a new seed.
    7. Enter Subnet for seed and network mask.
    8. Click OK.
    9. Click the save icon.

  5. Given that Network Manager IP has been installed and configured for a network discovery which includes devices that are in-scope but that should be filtered out by the pre-discovery filter, create a filter so that a pre-discovery filter has been applied to the Network Manager IP discovery configuration for the selected domain. With emphasis on the following steps:
    1. Log in to the Netcool GUI Foundation server.
    2. Select Network Manager (IP) Admin from the page selector menu.
    3. Select the Discovery Configuration from under the Discovery tab, select the appropriate domain from the Domain drop-down and click on the subsequently displayed Filters tab in the Discovery @Configuration panel.
    4. Select an existing filter from the Available Filters list in the Pre-Discovery Filter section, if applicable, by highlighting the required filter and clicking the Add Filter button so the highlighted filter becomes a Selected Pre-Discovery Filter.

      5. -Alternatively, create a new pre-discovery filter by clicking on the Filter Library button in the Pre-Discovery Filter section. Once the Pre-Discovery Filter Library window appears, click the Add Filter button and enter a filter name and specify the Boolean conditions that shall filter-out the appropriate devices. Click the Save and then Close buttons. Select the new filter from the Available Filters list in the Pre-Discovery Filter section.
    5. With the desired filter highlighted from the Available Filters in the Pre-Discovery Filter section, click this section’s Add Filter button so the highlighted filter becomes a Selected Pre-Discovery Filter.
    6. Click the Save Configuration disk icon in the Discovery Configuration panel.

  6. Given that Network Manager IP has been installed and configured for a basic discovery which includes devices in scope that are to be filtered out by the post discovery filter, create a filter that prevents devices with certain attributes from being passed to the Network Manager model, that only select devices are passed to the Network Manager model. With emphasis on the following steps:
    1. Log in to NGF.
    2. Select the Network Manager (IP) Admin from the menu.
    3. Choose the discovery tab, select discovery configuration and then the Filter tab.
    4. Select an existing filter from the Post-discovery filter section if appropriate, click Add Filter and then the save icon.

      5. -Alternatively, in the Post discovery filter section, click Filter Library, then Add Filter to create a new filter.
    5. In this New filter window, add a name for the filter, add the appropriate Boolean conditions and click Save and then Close.
    6. Highlight the filter just created and then click Add Filter.
    7. Click Save.

  7. Given that a user is logged in to the Netcool GUI Foundation with the appropriate Network Manager administration rights, configure the discovery so that the appropriate community strings will be configured for devices being discovered. With emphasis on the following steps:
    1. Launch NGF and navigate to Network Manager (IP) Admin ->Discovery Configuration -> Password tab.
    2. Click the + symbol.
    3. Enter the Community String.
    4. Select the appropriate Radio button: Globally
    5. Select IP address Enter the IP address of a single device
    6. Select Enter a subnet with / mask (optionally enter the mask manually)
    7. Select SNMP Version

      8. -Option 1: V1 Do nothing
      -Option 2: V2 Do nothing
      -Option 3: V3 Select the Auth Level Enter the Auth Password Enter the Private Password
    8. Enter the Time Out.
    9. Enter the number of Retries.
    10. Enter the Port if not the default (161)
    11. Click OK.
    12. Click Save.

  8. Given a requirement to configure SNMP community strings for discovery using the command line, modify the ITNM configuration files so that a global SNMP community strings is configured and is encrypted. With emphasis on the following steps:
    1. Log in to the ITNM server as a user with sufficient privilege to modify the ITNM configuration files in $NCHOME/etc/precision
    2. Ensure that the m_EncryptPasswords configuration option is set to 1 in the ConfigSchema,cfg file (or domain specific ConfigSchema..cfg if present).
    3. Create the encrypted community string on the command line using the ncp_crypt program – ncp_crypt –password lt;COMMUNITY_STRINGgt;
    4. Using a suitable editor, open the domain specific SNMP community string configuration file – SnmpStackSecurityInfo..cfg.
    5. If this file does not exist copy the default file to a domain specific file.
    6. Create a suitable entry for the community string using the encrypted password generated using ncp_crypt above ensuring that m_EncryptedPwd is set to 1.
    7. Save the file and exit.

  9. Given that a user is logged in to the Netcool GUI Foundation with the appropriate Network Manager IP administration rights, locate and select the Network Manager (IP) Admin page, select the Discovery Configuration and configure the passwords tab so that a discovery will be configured to use the appropriate telnet or SSH passwords for devices being discovered. With emphasis on the following steps:
    1. Launch NGF and navigate to Network Manager (IP) Admin ->Discovery Configuration -> Password tab.
    2. Click the + symbol.
    3. Select the appropriate Option and fill in the required parameters.
    4. Modify the Username Prompt regex if needed.
    5. Enter the Username.
    6. Modify the Password Prompt if needed.
    7. Enter the Password.
    8. Modify the Console Prompt if needed.
    9. Modify the timeout.
    10. Select SSH if it will be an SSH based login.
    11. Click OK.
    12. Click Save.

  10. Given that a user is logged in to the Netcool GUI Foundation with the appropriate Network Manager IP administration rights, locate and select the Network Manager (IP) Admin page, select the Discovery Configuration and configure NAT, so that devices will be discovered over a NAT domain to the address of the associated NAT gateway device. With emphasis on the following steps:
    1. Select the Network Manager (IP) Admin from the menu.
    2. Choose the discovery tab, select discovery configuration.
    3. Select NAT Tab.
    4. Specify the public IP address of the NAT gateway device in the IP Address field.
    5. Specify the address space identifier to use for the associated NAT domain in the Address Space ID field.
    6. Click OK to confirm your settings. The gateway you specified appears as a hyperlink row within the NAT Support table.
    7. Click the New button to define more NAT gateway mappings.
    8. Click the Save button to save your settings.

  11. Given customer requirements and Network Manager IP installed and running, configure the discovery agents for full discovery so that the system is configured to run appropriate discovery agents. With emphasis on the following steps:
    1. Launch NGF and navigate to Network Manager (IP) Admin ->Discovery Configuration -> Full Discovery Agents tab.
    2. Choose agents, from pre-defined list of Full Discovery agents, for your discovery by selecting the appropriate check boxes.
    3. Select an agent type check box to enable a group of agents for a specific type of discovery. Agents may be disabled individually.
    4. Click the + symbol.
    5. Browse the Agent tree and select the agents to be activated.
    6. Click the Save button to save your settings.

  12. Given Network Manager IP is installed on a supported UNIX platform and configured to perform a discovery, an available Alcatel 5620 SAM EMS and access credentials and root user access to the Network Manager IP server, modify the configuration of Network Manager IP so that data from the Alcatel 5620 SAM EMS is retrieved. With emphasis on the following steps:
    1. Log in to the UNIX server running the Tivoli Netcool products as the root user.
    2. Edit the DiscoSchema.cfg file in the $NCHOME/etc/precision directory using the text editor. Find the commented-out OQL insert for ‘ncp_df_collector’ and remove the comments (--) for the OQL insert.
    3. Edit the Alcatel5620SamSoapCollector.cfg file in the $NCHOME/precision/collectors/perlCollectors/Alcatel5620SamSoap directory using the text editor. @If necessary, remove all of the comment indicators (#) from the line following ‘Example Configuration:’ onwards
    4. If the default collector listening port needs modifying from the default value of 8081, edit the General section’s ‘Listen’ property and specify a new TCP port as necessary.
    5. Specify the DataSource parameters by providing Alcatel 5620 SAM EMS access credential values for Host, Port, Username, Password and, optionally, Timeout.
    6. Save the modified configuration file using the appropriate command in the text editor
    7. Start the collector before running a network discovery by executing:-

      8. ncp_perl $NCHOME/precision/collectors/perlCollectors/Alcatel5620SamSoap/main.pl –cfg $NCHOME/precision/collectors/perlCollectors/Alcate5620SamSoap/Alcatel5620SamSoap Collector.cfg
    8. Verify that collector is running by checking the UNIX process table by executing ‘ps aux | grep Alcatel5620SamSoapCollector’, the command should return a line indicating the collector is running.
    9. Inform Network Manager IP of the collector that should be queried by editing the DiscoCollectorFinderSeeds.cfg file to insert data into the collectorFinder.collectorRules table.
    10. Log in to the Netcool GUI Foundation server.
    11. Select Network Manager (IP) Admin from the page selector menu.
    12. Select the Discovery Configuration from under the Discovery tab, select the appropriate domain and click the subsequently displayed Full Discovery Agents tab in the Discovery Configuration panel.
    13. Select (enable) the Collector Discovery check box to enable collector-assisted discovery.
    14. Click the Save Configuration disk icon in the Discovery Configuration panel.

  13. Given Network Manager IP server with devices discovered and monitored, and access to OQL available, configure Linger Time on an entity, so that Network Manager IP is configured to remove an entity from topology after next discovery. With emphasis on the following steps:
    1. Log in to MODEL Service using OQL.
    2. Using OQL command, update LingerTime field in master.entityByName table for all the entities that represent the device using update command.
    3. Validate the LingerTime is changed to 0 for all entities by running a select query against the same device.
    4. Ensure the device is no longer in the Discovery scope or has been removed by discovery filter.
    5. Force the model to be refreshed using Discovery or use the SendTopologyToModel stitcher.

  14. Given Network Manager IP is installed and running and a complete discovery has been completed, set a specific time every day for a discovery to be run, so that a daily discovery has been scheduled. With emphasis on the following steps:
    1. Change directory to /opt/netcool/precision/disco/stitchers.
    2. Edit the FullDiscovery.stch file.
    3. Edit the statement: ActOnTimedTrigger(( m_TimeOfDay ) values ( 0600 ) ; ); and then uncomment the statement.
    4. Save and exit the file.

  15. Given that the Network Manager server has been installed and is running, activate the ifInErrors, ifOutErrors polls for all devices so that all network devices have ifInErrors, ifOutErrors monitored. With emphasis on the following steps:
    1. Select the Network Manager (IP) Admin from the menu.
    2. Choose the Monitoring tab
    3. Select the appropriate domain to apply poll configuration.
    4. Select the ifInErrors Poll Definition from the Poll Policies Browser by clicking on Poll Status Icon or Poll Name.
    5. Select the Poll Enabled check box from the Poll Policy Properties tab in the Poll Policy Editor window.
    6. Select the Classes tab from the Poll Policy Editor window.
    7. Select the NetworkDevice Class from the top of the Classes Navigation Tree.
    8. Click the Save button to save your settings.
    9. Confirm Save changes to Monitor Config database.
    10. Repeat steps 4-9 for ifOutErrors

  16. Given Network Manager IP is installed and a new device type with a sysObjectId of ‘1.3.6.1.4.1.2.999’, create a new AOC class named ‘MyNewClass’ that is a subclass of ‘NetworkDevice’ and uses the myNewClass.svg icon so that a new AOC class and icon assignment have been configured. With emphasis on the following steps:
    1. Log in to the Network Manager IP server as the administrator or root user.
    2. Create a new file using the text editor named MyNewClass.aoc in the $NCHOME/precision/aoc directory.
    3. Add the following lines to the new file to create a new, skeleton AOC sub-class named ‘MyNewClass’.

      4. active object 'MyNewClass'
      {
      };
    4. Within the MyNewClass AOC definition, sub-class the NetworkDevice class by adding a ‘super_class’ entry as follows:-

      5. active object 'MyNewClass'
      {
      super_class = 'NetworkDevice';
      };
    5. Within the MyNewClass AOC definition, specify the instantiation rule for the AOC by adding an ‘instantiate_rule’ entry as follows:-

      6. active object 'MyNewClass'
      {
      super_class = 'NetworkDevice';
      instantiate_rule = "EntityOID = 1\.3\.6\.1\.4\.1\.2\.999";
      };
    6. Within the MyNewClass AOC definition, specify default fault extension rules for the AOC by adding an ‘extension for Fault’ entry as follows:-

      7. active object 'MyNewClass'
      {
      super_class = 'NetworkDevice';
      instantiate_rule = "EntityOID = 1\.3\.6\.1\.4\.1\.2\.999";
      extension for Fault = {
      rules = [],
      poll_list = []
      };
      };
    7. Within the MyNewClass AOC definition, specify a default visual icon for AOC by adding a ‘visual_icon’ entry as follows:-

      8. active object 'MyNewClass'
      {
      super_class = 'NetworkDevice';
      instantiate_rule = "EntityOID = 1\.3\.6\.1\.4\.1\.2\.999";
      extension for Fault = {
      rules = [],
      poll_list = []
      };
      visual_icon = 'NetworkDevice';
      };
    8. Save the new AOC file with the appropriate command in the text editor.
    9. Edit the $NCHOME/etc/precision/topoviz.properties file and add a property that defines the image to use for the new AOC definition, overriding the default icon. Save the file using the appropriate command after editing the file:-

      10. topoviz.deviceicon.MyNewClass=myNewClass.svg
    10. Restart the ncp_class process to repopulate the NCIM entityClass table and verify that the ncp_class process has restarted by checking the process table in an appropriate to the Network Manager IP platform.
    11. Check the log files for errors.
    12. Verify the devices of this class have the correct icon in Topoviz.

  17. Given a text editor and read/write permissions to the Network Manager IP configuration files, configure Network Manager IP message bus so that it uses port 7700. With emphasis on the following steps:
    1. Open the $NCHOME/etc/precision/Precision.rvd.cfg file using a text editor.
    2. Add an entry for service to be 7700.
    3. Add an entry for daemon to equal tcp:7700.
    4. Save the results and exit the text editor.
    5. Stop and restart the RVD and RVA processes.

  18. Given that two separate instances of Network Manager IP are installed in on the same subnet standalone mode, configure each Network Manager IP instance, so that the Network Manager IP Servers form a failover pair.
    1. On the Primary Network Manager IP Server, navigate to the CtrlServices.lt;DOMAIN_NAMEgt;.cfg file in $NCHOME/etc/precision.
    2. Edit the file and add an entry at the end of the file for the Virtual Domain component as follows: ncp_virtualdomain –domain PRIMARY -virtualDomain VIRTUAL -backupDomain BACKUP –latency 100000.
    3. On the Backup Network Manager IP Server, navigate to the CtrlServices.lt;DOMAIN_NAMEgt;.cfg file in $NCHOME/etc/precision.
    4. Open the file and edit the arguments to the ncp_poller startup and the ncp_ncogate startup so that they both include the – backup option.
    5. Add an entry at the end of the file for the Virtual Domain component as follows: ncp_virtualdomain –domain BACKUP -virtualDomain VIRTUAL -primaryDomain PRIMARY –latency 100000.
    6. Configure appropriate communications.
    7. Remove or comment out the entries for the ncp_disco startup, and the ncp_d_helpserv startup.

  19. Given that the Network Manager server has been installed, and that a pair of ObjectServers have been installed and configured for failover, configure the Network Manager Probe for UNIX/Windows so that Network Manager IP connects to the virtual ObjectServer. With emphasis on the following steps:
    1. Open the file $NCHOME/etc/interfaces..
    2. Ensure that entries occur for each of the object servers (primary and backup), and that the host and port entries are correct for each.
    3. Ensure that an entry exists for a virtual object server, and that the primary and backup entries are correct for each.
    4. If changes are required, perform the required changes to omni.dat in UNIX or SQL.ini in Windows, save the file, then run $NCHOME/bin/nco_igen on UNIX or save your changes in the Windows Server Editor on Windows.
    5. Open the file $NCHOME/probes/$ARCH/nco_p_ncpmonitor.props on UNIX or %NCHOME%\probes\win32\nco_p_ncp_monitor.props on Windows.
    6. Ensure that a “Server” entry line exists in the file, and that it matches the name of your VIRTUAL object server, as defined in the omni.dat or SQL.ini file.
    7. If failback is desired, ensure that a “PollServer” entry exists in this file, and that it is set to the number of seconds you want to poll the primary object server to initiate failback, and is NOT set to zero.
    8. Ensure that the – server command line parameter in the $NCHOME/etc/precision/CtrlServices..cfg also reflects the name of the VRTUAL objectserver.

  20. Given that the Network Manager server has been installed, and all Network Manager processes are running, verify that the NCIM database configuration is correct so that Topoviz will be able to build its topology maps.
    1. Enter the URL for the NGF server and port (http://servername:port#).
    2. Navigate to log in and navigate to the Database Configuration tab.
    3. Ensure that the database host and port is correct for the MySQL database, and that the username and password are correct.
    4. Launch Topoviz Hop View to verify connectivity.

  21. Given that Network Manager IP has been installed and an initial discovery and a network discovery have been completed, configure the preset layer stitcher to resolve an undiscoverable connection between two discovered devices so that the connection between the devices is represented in Network Manager IP.
    1. Log in to the Network Manager IP server as the administrator or root user.
    2. Edit the PresetLayer.stch stitcher file in the $NCHOME/precision/disco/stitchers directory. In the StitcherRules section, modify the ExecuteOQL parameter such that the OQL insert’ s m_Name and m_NbrName attributes are set to the EntityName of the device and/or interface that should be connected.
    3. ExecuteOQL

      4. (
      "insert into PresetLayer.entityByNeighbor( m_Name, m_NbrName )
      values ( 'deviceA[ 0 [ 1 ] ]' , 'deviceB[ 0 [ 3 ] ]' );"
      );
    4. Remove the following ExecuteOQL section such that there are no OQL inserts into workingEntities database tables being executed by the PresetLayer stitcher within the StitcherRules section.
    5. Save and close the modified PresetLayer.stch stitcher file with the appropriate command in the text editor.
    6. Edit the BuildLayers.stch stitcher file in the $NCHOME/precision/disco/stitchers and uncomment the line that reads //ExecuteStitcher(‘PresetLayer’); by removing the // characters.
    7. Save and close the modified BuildLayers.stch stitcher file with the appropriate command in the text editor.
    8. Edit the CreateAndSendTopology.stch stitcher file and ensure that the PresetLayer stitcher is part of the ‘MergeLayers’ process by modifying the stitcher call starting with the line ‘ExecuteStitcher(‘MergeLayers’,1,’ includes a call to the ‘PresetLayer’ stitcher.
    9. Save and close the modified CreateAndSendTopology.stch stitcher file with the appropriate command in the text editor.
    10. To add the connection defined in the PresetLayer stitcher to the topology model, execute the CreateAndSendTopology stitcher by using the ncp_oql process to execute the following OQL insert:-

      11. insert into stitchers.actions (m_Name) values (‘CreateAndSendTopology’);

  22. Given that a discovery has been completed, create a Physical network view, so that a network view of Chassis where the first 2 octets of their IP address matches ‘192.168.’ has been created showing all connections and end nodes. With emphasis on the following steps:
    1. Click the New View button, at the top right of the Topoviz Navigation Panel.
    2. In the Name field, label a name for the network view, for My Subnet
    3. In the Parent drop-down list define where you want the view to appear in the Navigation Panel hierarchy. Choose NONE if you want the view to be a top-level view.
    4. Set the Type drop-down list set to IP Filter.
    5. Click the Filter tab.
    6. Ensure the Domain drop-down list is set to your network domain.
    7. In the Address Patterns field, specify an IP address pattern 192,168.
    8. Choose End Nodes list. Select End Nodes
    9. Choose Connectivity list select Layer 3
    10. Click OK.
    11. Click the Save button to save the new network view settings.

  23. Given a text editor and read/write permissions to the Network Manager configuration files, configure Disco to enable the ExtraDetails agent from the command line, so that Disco has been configured to enable the ExtraDetails agent. With emphasis on the following steps:
    1. Open the $NCHOME/etc/precision/DiscoAgents..cfg file using a text editor.
    2. Locate the insert section for the ExtraDetails agent.
    3. Change the m_Valid parameter to a value of 1 for the ExtraDetails agent, and save the file changes.
    4. Restart or start the ncp_disco process.

  24. Given that Network Manager IP is installed, the Entity agent enabled, a network discovery has been performed and devices and their composition are viewable in the Topoviz structure browser; demonstrate understanding of the mechanism used to transfer device and containment data from the OQL model database to the NCIM relational model so that an understanding of the mapping mechanism is demonstrated. With emphasis on the following steps:
    1. Log in to the Network Manager IP server and change the current working directory to $NCHOME, source the Network Manager IP environment on UNIX platforms.
    2. Change the current working directory to the $NCHOME/etc/precision directory and edit the ModelNcimDb..cfg configuration file using the text editor.
    3. Using the text editor, identify how one OQL into the dbModel.entityMap table that maps basic entity information from all OQL records data to the NCIM relational model’s entity table.
    4. Using the text editor, identify an OQL insert into the dbModel.entityMap table that maps additional class and containment data considering that the identified insert must handle the fact that the class of record may contain more than one other record. Also identify the Column and value responsible for mapping OQL containment data to the NCIM contains table.
    5. Identify the NCIM database tables that will be used to represent the slot and any contained entities.
    6. Using the ncp_oql OQL manipulation application and referencing ModelNcimDb..cfg configuration file, query the OQL model database for a slot record with containment data.

  25. Given that Network Manager IP is installed, a network discovery has been performed and network connectivity data is viewable in the Topoviz GUI explain how network topology and connectivity information is mapped from the OQL model database to the NCIM relational model so that understanding of the mechanism has been demonstrated. With emphasis on the following steps:
    1. Log in to the Network Manager IP server and change the current working directory to $NCHOME, source the Network Manager IP environment on UNIX platforms.
    2. Change the current working directory to the $NCHOME/etc/precision directory and edit the ModelNcimDb..cfg configuration file using the text editor.
    3. Using the text editor, identify the one OQL insert into the dbModel.entityMap table that maps connectivity information from all OQL records data to the NCIM relational database. Also identify the column and values responsible for mapping the connectivity information from the OQL record to the NCIM connects table.
    4. Once the OQL insert has been identified, identify which NCIM topology entity names and types for each of the mapped connections shall belong to once the OQL data has been mapped to the NCIM relational database.
    5. Identify the NCIM database tables that will be used to represent connectivity between entities.
    6. Using the ncp_oql OQL manipulation application and referencing ModelNcimDb..cfg configuration file, query the OQL model database for records that contain connectivity data that will be mapped to the NCIM layer 3 topology.

  26. Given that Network Manager IP is installed, a network discovery has been performed and IP subnet data is viewable in the Topoviz GUI explain how IP subnets and addresses are mapped from the OQL model database to the NCIM relational model and how they’re associated with the implementing interface and/or chassis.so that understanding of the mechanism has been demonstrated. With emphasis on the following steps:
    1. Log in to the Network Manager IP server and change the current working directory to $NCHOME, source the Network Manager IP environment on UNIX platforms.
    2. Change the current working directory to the $NCHOME/etc/precision directory and edit the ModelNcimDb..cfg configuration file using the text editor.
    3. Using the text editor, identify the OQL inserts that are responsible for mapping OQL database IP addresses to the NCIM relational model for all OQL records having IP addresses.
    4. Given the previously identified OQL inserts, identify the column and value that are responsible for associating the IP addresses as protocolEndPoints with their implementing records.
    5. Identify the OQL insert and attribute from which subnet membership is mapped to the NCIM relational model.
    6. Identify the NCIM tables that are used to represent IP subnets, related addresses and the relationship between addresses and implementing entities.
    7. Using the ncp_oql OQL manipulation application and referencing ModelNcimDb..cfg configuration file, query the OQL model database for records that contain IP subnet and IP address data.

Section 4: Performance Tuning and Problem Determination

  1. Given that Network Manager IP is installed, demonstrate knowledge of the Network Manager IP logging system by being able to modify the Network Manager IP configuration such that the ncp_disco process is logged at the maximum debug level, change the logging level of a running Network Manager IP process and change the logging level of a specific Network Manager IP discovery agent so that an understanding of debugging is demonstrated. With emphasis on the following steps:
    1. Log in to the Network Manager IP server as the root/administrative user.
    2. Edit the CtrlServices..cfg file in the $NCHOME/etc/precision directory.
    3. Edit the OQL insert into the services.inTray OQL database table for the ncp_disco process such that the –debug parameters default value of 0 is increased to 4.
    4. Save and close the modified CtrlServices..cfg configuration file.

      5. Incrementally increase the debug level of a running Network Manager IP process by using the operating system kill command to send a user signal 2 to the process, each invocation of the kill command increases the debug level by one, the debug level is set back to zero on a 5th invocation of the kill command:-
      kill –USR2
    5. Edit the DiscoAgents..cfg file in the $NCHOME/etc/precision directory.
    6. Edit the OQL insert into the disco.agents table for the ‘Entity’ discovery agent and add the m_DebugLevel attribute to the columns part of the insert followed by the value 4 in the values part of the insert.
    7. Save and close the modified file and run a network discovery.
    8. Verify that the logging level has been increased by viewing the ‘Entity’ discovery agents logging file by editing the ncp_agent.Entity.NCOMS.log file in the $NCHOME/log/precision directory.

  2. Given that a Network Manager IP Server and an OMNIbus Object Server have been installed, determine why Network Manager IP events are not being seen in the OMNIbus Object Server, so that the problem can be resolved. With emphasis on the following steps:
    1. Check the Network Manager IP log files in $NCHOME/log/precision for example, nco_p_ncpmonitor..log).
    2. Confirm that the Network Manager IP Probe process, nco_p_monitor, is running.
    3. Confirm that the nco_p_monitor process is configured to connect to the correct ObjectServer name
    4. Confirm that the OMNIbus interfaces. file contains the correct values for the host and port for the ObjectServer name that the nco_p_monitor is configured to connect to
    5. Check the mapping and rules files in $NCHOME/probes/lt;ARCHgt; to ensure that the rules will pass the events to the ObjectServer with the correct field settings
    6. Confirm that the ncp_poller –domain process is running
    7. Check ObjectServer log file.

  3. Given that a Network Manager IP Server is installed and entities are being monitored, confirm that Network Manager IP is configured to monitor a specific entity, so that it is established that Network Manager IP is configured to monitor the entity. With emphasis on the following steps:
    1. Confirm that the Poll Policy Default Chassis Ping Status is checked green
    2. Click the Default Chassis Ping Policy
    3. Check the Poll Definition to ensure that it says Default Chassis Ping
    4. Select the Classes Tab
    5. Check if the appropriate device class is checked
    6. Select the Scope Tab
    7. Ensure that the Scope is not limited to rule out the device you wish to monitor
    8. Confirm that the entity passes the poll scope criteria by querying the Model database using the poll scope criteria and confirming that the entity is returned in the records.

  4. Given that a Network Manager IP Server is installed, discovery has been completed, and a Network View has been opened, determine why the Network Manager IP entity icons within the view do not reflect the status of the underlying entities, so that the reason why the Network Manager IP entity icons do not reflect the status of the underlying entities is known. With emphasis on the following steps:
    1. Check that ncp_poller service has started.
    2. Open an OMNIbus Event List, and check that the LocalNodeAlias field in the events is populated, and that the information matches the information related to the entity.
    3. Check that the NmosObjInst ObjectServer field is populated.
    4. Check that the NmosDomainName ObjectServer field is populated.
    5. Check that the NmosEntityId ObjectServer field is populated.
    6. Check that the NmosManagedStatus ObjectServer field is populated as Managed.
    7. Open a Webtop Active Event List, right click an event related to the entity, and select ShowTopology.
    8. Select the Network Manager (IP) Admin from the menu.
    9. Select the “Tools” tab.
    10. Select the appropriate Domain name for device being investigated
    11. Select “Amos” from the Service menu.
    12. Check that the entity exists in topoCache.entityByName using ncp_oql: select * from topoCache.entityByName where EntityName = ‘EntityName’;
    13. Check if the ServerName ObjectServer field is defined in NCIM DB domainMgr.domainName.

  5. Given that a Network Manager IP Server and an ObjectServer are installed and running, and that the Network Manager IP Gateway is installed, determine if the Network Manager IP Gateway is functioning, so that the status of the Network Manager IP Gateway is known. With emphasis on the following steps:
    1. Check that events in OMNIbus relating to devices discovered by Network Manager IP are being enriched with topology information and are being processed by the Root Cause Analysis system by checking whether or not the event’s Network Manager IP NmosObjInst and NmosEntityId are populated with a non-zero value. Note: if this is true, this task is complete.
    2. Check that the Network Manager IP Gateway process ncp_ncogate is running using ps aux | grep ncp_ncogate.
    3. Depending on the outcome, check the Network Manager IP Gateway log files in $NCHOME/log/precision (e.g. ncp_ncogate..log).
    4. Depending on the outcome, check the Network Manager IP Gateway configuration files in $NCHOME/etc/precision - NcoGateSchema.cfg, NcoLogin.cfg and NcoGateInserts.cfg.
    5. On Windows, Launch the Task Manager, select the Processes Tab, and check that the ncp_ncogate process is running.
    6. On Windows, depending on the outcome, check the Network Manager IP Gateway log file in %NCHOME%\log\precision (for example, ncp_ncogate..log).
    7. On Windows, depending on the outcome, check the Network Manager IP Gateway configuration files in %NCHOME%\etc\precision – NcoGateSchema.cfg, NcoLogin.cfg and NcoGateInserts.cfg.

  6. Given that a Network Manager IP Server is installed and the Network Manager host is in the MODEL topology, determine why Network Manager IP Root Cause Analysis is not working, so that the reason for Root Cause Analysis not working is identified. With emphasis on the following steps:
    1. Confirm that there is a contiguous path in the MODEL topology between the source and destination.
    2. Check that the Network Manager Gateway ncp_ncogate and the AMOS service ncp_f_amos are running.
    3. 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) Removed Type <> 2
    4. Confirm that the EventID field contains a valid EventMapName.
    5. 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.
    6. 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’;
    7. Check that an Alert has been created in mojo.events using ncp_oql: select * from mojo.events where EntityName = ‘LocalNodeAlias’;
    8. Check if the Alert in mojo.events has been updated by the RCA engine.
    9. If the alert is in mojo.events issue a kill –USR2 on the ncp_ncogate process and monitor the logs and search for the problem event and errors.
    10. If the Alert has not been updated as expected by RCA, check how the event is being processed by the TopologicalAlertCorrelation ruleset under $NCHOME/precision/aoc/rca_rules/TopologicalAlertCorrelation.
    11. 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 a text editor and read/write permissions to the ITNM configuration files, configure ITNM IP agent threads, so that discovery time is reduced. With emphasis on the following steps:
    1. Log in to the ITNM server as a user with sufficient privelege to modify the ITNM configuration files ($NCHOME/etc/precision)
    2. Open the $NCHOME/etc/precision/DiscoAgents..cfg file using a text editor.
    3. Locate the insert statement for the agent that you wish to modify.
    4. Add the m_NumThreads field to the insert statement if it does not already exist.
    5. Add a value for the number of threads to the values part of the insert statement.
    6. Save and exit the DiscoAgents file.

  8. Given that Network Manager IP and the dependant Netcool components are installed and running and you have admin access to the Network Manager Admin GUI, disable VLAN modeling so that Network Manager IP VLAN modeling has been disabled in order to decrease discovery time in an initial discovery pass whilst ensuring that the customer understands the impact of this change. With emphasis on the following steps:
    1. Explain to the customer the effect of disabling VLAN modeling to the containment structure of discovered devices, including the effect on viewing devices using Structure Browser and the impact on root cause analysis.
    2. Navigate to Advanced tab.
    3. Locate the Advanced Discovery Configuration.
    4. Remove the check from the checkbox next to Disable VLAN Modeling.
    5. Click the Save Configuration icon.

  9. Given that Network Manager IP and the dependant Netcool components are installed and running and you have admin access to the Network Manager Admin GUI, adjust the Network Manager IP Ping Finder timeouts and retries so that Network Manager IP will be more tolerant to discoveries in slow networks. With emphasis on the following steps:
    1. Navigate to the Network Manager AdminDiscovery Discovery Configuration -> Advanced tab.
    2. Locate the Advanced Ping Finder configuration.
    3. Increase the Default Timeout to a larger value.
    4. Increase the Default Number of Retries value to a larger value.
    5. Click on the Save Configuration icon.

  10. Given a text editor and read/write permissions to the Network Manager configuration files, configure Disco to enable discovery failover from the command line, so that Disco has been configured to enable discovery failover. With emphasis on the following steps:
    1. Open the $NCHOME/etc/precision/DiscoSchema..cfg file using a text editor.
    2. Locate the insert section that assigns value to the m_UseFailover variable.
    3. Change the value assigned m_UseFailover to 1 to enable discovery failover, save file changes.
    4. Restart or start the ncp_disco process.
    5. Verify that the failover cache files are created in the $NCHOME/var/precision directory.

  11. Given Network Manager IP has been installed and configured for a basic discovery, determine why device names are not resolving correctly within Network Manager IP, so that the issue can be resolved. With emphasis on the following steps:
    1. In the Network Manager IP discovery configuration tab, select the DNS tab to determine if the correct naming methods in the correct order are being used.
    2. In the Network Manager IP discovery configuration tab, select the Advanced tab and examine the Advanced Discovery Configuration section. Verify the Enable SysName naming option been checked.
    3. In the Network Manager IP discovery configuration tab, select the Device Support tab, expand the Full Layer 2 and Layer 3 Discovery section and determine if the LoopBackDetails agent is enabled.
    4. In the Network Manager IP discovery configuration tab, select the “Seed” tab and determine which seed file the file finder is using if enabled. Open this seed file and determine if device names are being forced to be named using this file for example are there two columns in this file; one for IP address and the other for name.

  12. Given that a Network Manager IP Server is installed and a discovery has been completed, determine why certain devices have not been fully discovered, so that the reason why the devices have not been fully discovered is known. With emphasis on the following steps:
    1. Log in to the Disco service using ncp_oql.
    2. Check to see if the Network Manager Server has SNMP access to the device by querying the Details.returns table using the command: select * from Details.returns where m_HaveAccess = 0
    3. Launch Network Manager (IP) Admin, select Discover tab, Discovery Configuration. Select the SNMP Tab, and verify the SNMP Community settings.
    4. Verify connectivity using the MIB Browser.

  13. Given a working Network Manager IP v3.7 installation use the advanced features of Network Manager IP so that nondefault topology information is visible in the structure browser and available for network partition views. With emphasis on the following steps:
    1. Log in to Network Manager IP server.
    2. Log in to NCIM DB.
    3. Create a new database table to contain the custom data.
    4. Change to the directory containing the DbEntityDetails.domains.cfg and edit it.
    5. Add an insert for dbModel.entityDetails to add the required data to the entityDetails ncim table.
    6. Add an insert for dbModel.entityMap to populate the custom table with the required data
    7. Edit the ncimMetaData.xml file to configure Topoviz to use the new custom table in network partitions.
    8. Stop and Start Network Manager IP and NGF to read in DbEntityDetails edits

  14. Given a working ITNM installation, describe the basic debugging process so that a working knowledge of the discovery process is demonstrated. With emphasis on the following steps:
    1. Describe the interaction of the core discovery tables (Details, AssocAddress, finders etc.).
    2. Describe at a high level how the stitchers accessible via the Advanced tab work.

Section 5: Administration

  1. Given that Network Manager IP is installed, access to the Network Manager Discovery GUI, read access to the Network Manager configuration files and optionally access to ncp_oql, determine when a discovery cycle has been completed so that discovery cycle completion is determined using several techniques. With emphasis on the following steps:
    1. Log in to the Network Manager IP server and change the current working directory to $NCHOME, source the Network Manager IP environment on UNIX platforms.
    2. Also log in to the Network Manager IP GUI and navigate to the Discovery Status
    3. In the GUI, navigate to the Discovery Status page by selecting Network Manager (IP) Admin -> Discovery -> Discovery Status and observe the Discovery Phase indicator under the Discovery Details sub-tab.
    4. In the CLI, use ncp_oql to access an OQL session for the disco service and run the following OQL query to determine whether or not the current discovery cycle has completed: “SELECT * FROM disco.status;”

  2. Given login access to a working Network Manager IP Domain Management GUI initiate a partial discovery so that Partial discovery is started for a device or subnet. With emphasis on the following steps:
    1. To run a partial rediscovery, within the Domain Management GUI, under the Discovery tab, click Discovery Status.
    2. Select Partial Discovery from the Discovery Type option menu and specify IP address(es) or subnets containing devices to be rediscovered.
    3. To add an IP address or subnet to the list of devices to be rediscovered, click New… and type an IP address or a netmask in the Partial Rediscovery Node/Subnet dialog box
    4. Once you have specified all IP addresses and subnets to rediscover, you can modify the discovery scope to limit the scope of this rediscovery. To do this, click Scope…. The Edit Partial Rediscovery Scope dialog box appears, showing the scope settings that you set for the discovery.
    5. To add a scope zone, click the New button and type an IP address and a netmask in the Scope dialog box
    6. Once you have specified all scope zones, click OK in the Edit Partial Rediscovery Scope dialog box.
    7. Click Go on the Partial Rediscovery dialog box to launch the discovery.

  3. Given a working ITNM installation and a named file containing the appropriate seed file entries, configure the discovery so that only available devices are discovered. With emphasis on the following steps:
    1. Navigate to the “Discovery Configuration->Seed” tab within the “Discovery” tab of the “Network Manager (IP) Admin”, and select the “Use File Finder in Discovery” check box to enable the File Finder.
    2. Click the New button above the File finder table.
    3. In the File Seed window that appears, enter the path to a file containing seed devices.

      4. Provide the absolute path to the seed file on the Network Manager IP host machine in the Filename field; any column delimiter in the Delimiter field; the column number for the IP Column in the file; the column number for the Name Column if present.
    4. Click OK to confirm settings
    5. Navigate to the “Advanced” tab in the “Discovery Configuration” GUI.
    6. Check the “Enable File Finder Verification” checkbox.
    7. Click Save to save new discovery Config settings.

  4. Given Network Manager IP server with devices discovered and monitored, log in NGF to launch the Structure Browser to check the events/status on device and interface and unmanage an interface, so that the Structure Browser is accessed to check the status of the device, status of interface and to run a tool to unmanage an interface. With emphasis on the following steps:
    1. Log in to NGF.
    2. Launch the Structure Browser either from Topoviz ( Hop View or Network View) OR from @Netcool/Webtop AEL tool for a device.
    3. Expand the Device Structure tree to see all the device components.
    4. Browse the device component and select an interface from the tree.
    5. Verify the status of the interface from the ‘Component Details Tab’.
    6. Verify if the interface is managed/unmanaged.
    7. Verify the alert status on this interface.
    8. Launch a tool on this interface to unmanage this interface.

  5. Given that a user is logged in with the appropriate Network Manager administration rights to the Netcool GUI Foundation, locate and select the Network Manager Admin selector, select the Monitor tab and enter the appropriate information so that a Ping poll definition is defined. With emphasis on the following steps:
    1. Select Poll Definitions from the left side menu navigation.
    2. Click the + in the Poll Definition Browser.
    3. Enter a unique Poll Definition name.
    4. Select either an interface or a chassis Poll Definition Type.
    5. Select an Event Severity.
    6. Click Ok.

  6. Given that a user is logged in with the appropriate Network Manager administration rights to the Netcool GUI Foundation, locate and select the Network Manager Admin selector, select the Monitor tab and enter the appropriate information so that a Ping Definition is defined for Cisco 26xx Class of Device. With emphasis on the following steps:
    1. Select Poll Policies from the left side menu navigation.
    2. Click the + in the Poll Policies Browser.
    3. Select a Poll Definition Type Default Chassis Ping.
    4. Modify polling interval if needed.
    5. Check Poll Enabled.
    6. Select Classes tab.
    7. Check Cisco26xx Class.
    8. Modify scope if required.
    9. Click Ok.

  7. Given that a Network Manager IP Server is installed, discovery has been completed and monitoring is enabled change the monitoring state of an entity from Managed to Unmanaged. With emphasis on the following steps:
    1. Select the Network Manager IP (Desktop) from the menu.
    2. Choose the Hop View tab
    3. Select the appropriate domain to search for the device.

      4. 2Input the Chassis IP or EntityName of the device to Unmanage in the Seed: field.
    4. Alternatively use the Search for Seed button to find the chassis or interface to be unmanaged.
    5. Ensure device is retrieved in Hop View.
    6. Right-click the device and choose Unmanage from the context menu.
    7. Verify an Unmanaged icon now is applied visually over the topology icon representing the device now unmanaged.

  8. Given an installation of Network Manager IP, with access to the Network Manager Discovery GUI, and read access to the Network Manager configuration files, ensure that all interfaces of a particular type are unmanaged so that the state cannot be altered using the GUI. With emphasis on the following steps:
    1. Log in to the Network Manager IP server, and go to the $NCHOME/precision/disco/sticthers directory.
    2. Use a text editor to open the TagManagedEntities stitcher file.
    3. Modify the initial OQL statement so that only interfaces with an interface description or interface name containing the terms ‘Dialup’ or ‘Dialer’ are permanently unmanaged by disco, by setting their status to 2.
    4. Trigger a discovery and wait until it has completed.
    5. Initiate an OQL session (on the command line or through the OQL workbench in the GUI) to query model. Check the set of entities in the topology with a managed status of 2 by running the following query: “SELECT EntityName, EntityType, ExtraInfo->m_IfDescr, ExtraInfo->m_IfName FROM master.entityByName where ExtraInfo->m_ManagedStatus = 2;”
    6. View the contents of the ncim.managedStatus table.
    7. View the interfaces through the structure browser in the GUI, and observe the spanner icon beside the unmanaged interfaces.
    8. Return to the TagManagedEntities stitcher file.
    9. Modify the initial OQL statement so that only interfaces with an interface description or interface name containing the terms ‘Dialup’ or ‘Virtual’ are permanently unmanaged by disco, by setting their status to 2.
    10. Trigger a rediscovery and wait until it has completed.
    11. Initiate an OQL session (on the command line or through the OQL workbench in the GUI) to query model. Check the set of entities in the topology with a managed status of 2 by running the following query: “SELECT EntityName, EntityType, ExtraInfo->m_IfDescr, ExtraInfo->m_IfName FROM master.entityByName where ExtraInfo->m_ManagedStatus = 2;”
    12. View the contents of the ncim.managedStatus table.
    13. View the interfaces through the structure browser in the GUI, and observe the spanner icon beside the unmanaged interfaces.

  9. Given a default ITNM installation, modify the configuration so that the Service Affecting Event functionality is activated. With emphasis on the following steps:
    1. Log in to the ITNM server as a user with sufficient rights to modify ITNM configuration files ($NCHOME/etc/precision).
    2. Locate the ITNM control services file for the domain you want to enable Service Affecting Events for ($NCHOME/etc/precision/CtrlServices..cfg).
    3. If this file does not exist, copy the default Ctrl configuration file to a domain specific file – (cp $NCHOME/etc/precision/default/CtrlServices.cfg $NCHOME/etc/precision/CtrlServices..cfg).
    4. Edit the CtrlServices..cfg file using a suitable editor.
    5. Locate the entry for “ncp_ncosae”.
    6. Uncomment the lines for the ncp_ncosae insert statement.
    7. Save the file and exit the editor.
    8. Locate the ITNM scripts directory – (cd $NCHOME/precision/scripts). .
    9. Ensure that you have administrator access to the Omnibus database system
    10. Run nco_sql using input from the “create_sae_automation.sql” sql input file – nco_sql – user -password -server < ./.create_sae_automation.sql.
    11. Start the ncp_ncosae service under ncp_ctrl – either as an insert into Ctrl or by restart of the ncp_ctrl process system (preferred).

  10. Given an ITNM installation (including dependant components), suitable access to the appropriate ObjectServer, and a suitable VPN discovery, determine if the appropriate structures are populated so that Service Affecting Events are created when necessary and the service affecting event functionality has been enabled. With emphasis on the following steps:
    1. Edit the CtrlServices.cfg file and search for ncp_ncosae and read the comment.
    2. Uncomment the ncp_ncosae after the following step.
    3. Execute $NCHOME/precision/scripts/create_sae_automation.sql against all Object Servers related to Tivoli Network Manger.
    4. Log in to the command line of the ITNM server as a user with sufficient privilege to run ncp_oql.
    5. Run ncp_oql for the model service – ncp_oql –service model –username admin –domain
    6. Validate that VPN Service objects exist in the master.entityByName table –

      7. select * from master.entityByName where EntityOID='VIRTUAL_PRIVATE_NETWORK' AND ExtraInfo->m_MPLSVPNType <> 'MPLS Core' AND ExtraInfo->m_MPLSVPNMemberships is not NULL;
    7. Exit OQL
    8. Log in to the ObjectServer using nco_sql or using the ncp_config GUI
    9. Query the appropriate precision tables for data -

      10. -select * from precision.entity_service;
      -select * from precision.service_details;
    10. Exit nco_config GUI or nco_sql CLI

Test registration

Authorized Prometric test centers (worldwide testing)