Preventive Service Planning
Abstract
Known issues with Tivoli Netcool Performance Manager 1.4, including installation and upgrade issues.
Content
This technical note outlines issues for both the Wireline and Wireless Tivoli Netcool Performance Manager components, with an added section covering all known wireless tooling issues.
Important: 1.4.0.0-TIV-TNPM-IF0001 is a mandatory Fix Pack on top of Tivoli Netcool Performance Manager 1.4 GA version.
This technical note is organized as follows:
Wireline specific issues- Wireless specific issues
- Wireless specific tooling issues
- Common Reporting issues and limitations
- You open a report from Defined Resource View and open any other tab at the same time from Dashboard Application Services Hub.
- When the Administration page and Common Reporting page are open at the same time, the common pack lists do not appear on the Common Reporting page. This issue is seen in Internet Explorer 9 only. To temporarily resolve this issue, click the Sort icon, the common pack list reappears.
- If you open Administration console of two different servers simultaneously, it opens in the same window.
- If you close the Common Reporting page in Firefox, the Dashboard Application Services Hub interface elements are unavailable for clicking.
- The Search shortcut that you use in Dashboard Application Services Hub (Alt+F3) does not work with Common Reporting and Resource Metric Viewer pages.
A report is not rendered correctly in Defined Resource View on Dashboard Application Services Hub in Internet Explorer
Symptoms
Consider the following scenario:
For example, you open a report from Defined Resource View and also from Diagnostic view.
In this scenario, you notice that the report on Defined Resource View does not display correctly. This issue is seen in Internet Explorer only.
Resolving the problem
To temporarily resolve this issue, click Refresh, the report is rendered correctly again.
Switching between languages to view DataView components on Dashboard Application Services Hub
Symptoms
When you are switching between languages on Dashboard Application Services Hub, you might notice that the previously selected language might appear even after you change the browse locale. This issue is seen on Internet Explorer only.
Resolving the problem
To workaround this issue, change both browser locale and system locale as follows:
Note: On Mozilla Firefox, you can change the browser locale alone. For instructions, see:
https://support.mozilla.org/en-US/questions/794066
Change the browser locale on Internet Explorer as in these instructions:
http://windows.microsoft.com/en-my/windows-vista/change-your-internet-explorer-language-settings
Change the system locale as in these instructions:
http://windows.microsoft.com/en-my/windows/change-system-locale#1TC=windows-7
Manual configuration required to install Reporting Services as non root user
When you install Jazz for Service Management as a non root user, the installation fails at Reporting Services
Symptoms
When you install Jazz for Service Management as non root user, the Installation fails at Reporting Services. You might receive the following error:
Error during "post-install configure" phase: Failed in configuring Reporting Services Database. /home/non_root_user_home/opt/IBM/JazzSM/install/fsconfig.xml:227: The following error occurred while executing this line: /home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/reporting_services_config.xml:17: The following error occurred while executing this line: /home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/reporting_services_config.xml:23: The following error occurred while executing this line: /home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:54: The following error occurred while executing this line: /home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:66: The following error occurred while executing this line: /home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:123: The following error occurred while executing this line: /home/non_root_user_home/opt/IBM/JazzSM/install/reporting_services/tcr_db_config.xml:142: Failed in configuring Reporting Services Database.
Resolving the problem
To resolve this issue, follow these steps manually:
Go to REPORTING_HOME from user_home_directory and run the following command as non-root user:
./TCR_generate_content_store_db2_definition.sh database_name user_name
Where
database_name
The name of the database to create for the Cognos Content Store. The database name can have up to 8 characters. To avoid potential problems, do not use special characters such as @, #, and $ in the database name. The default database name that is used in a simple installation is tcrdb.
user_name
The user name to connect to the Content Store, that is, the database owner. The user name can be:
The common administrator user name that is created during the simple installation.
The database administrator that is created during DB2 setup.
The user name that is associated with the user account that was created on the database server for the Content Store.
For example:
./TCR_generate_content_store_db2_definition.sh tcrdb db2inst1
This command generates the tcr_create_db2_cs.sql script.
· Run the tcr_create_db2_cs.sql script by using the following command as db2 instance user:
db2 -vtf <user_home_dorectory>/<REPORTING_HOME>/tcr_create_db2_cs.sql
You receive the following message:
The CREATE DATABASE command completed successfully.
After completing these tasks, proceed with the installation.
LDAP configuration via the Topology Editor does not work during Tivoli Netcool Performance Manager installation
If you want to perform the LDAP configuration for authentication to Jazz for Service Management, perform the configuration via the Jazz for Service Management WebSphere Console that is accessible from Dashboard Application Services Hub portal by using the following information:
For more information on LDAP configuration, see:
Note The LDAP configuration must be done after the DataView installation has completed successfully.
Issue in viewing selected resources in Diagnostic view based on a property that does not have a value for all the selected resources
Symptoms
You can choose to view resources based on a list of properties such as Resource Name, Resource Label, customerfacingName. which you can set in the “User Preference Management” page on Dashboard Application Services Hub. However, some resources may not have value defined for that particular property and this might result in the resources not listed on Diagnostic View.
Resolving the problem
To work around this issue, view the resources by using common properties such as Resource Name and Resource Label on Diagnostic View as all resources will have values for these two properties.
Some settings from charts are not saved to the workspace
Symptoms
When you create charts in Diagnostic View and save them in a workspace, all the settings are not saved. For example, if you set the granularity to a value other than the non-default value, these settings are not saved when you reopen the chart.
Resolving the problem
To work around this issue, you must reset the granularity settings every time you open the saved chart.
The resmgr command for barwidth settings on a chart does not work
Symptoms
When you use resmgr command for barwidth settings on a DataView chart, the change does not reflect in the chart.
Resolving the problem
To work around this issue, change the barwidth setting from DV Navigator.
When you restore the User Roles page in Dashboard Application Services Hub, the scroll bars are not displayed
Symptoms
When you refresh or restore the User Roles page in Dashboard Application Services Hub, the scroll bars are not displayed and the options in the Filter list is not visible. This issue is not seen in Internet Explorer.
Dashboard Application Services Hub discovery message might appear even after the discovery is complete
Symptoms
When you import the Dashboard Application Services Hub from a remote server, you might see the following message even after the discovery is complete:
Running the DASH Discovery. This could take a few minutes
Resolving the problem
You can ignore this message and proceed to click the Next button after it is enabled.
Problem in opening a saved workspace multiple times
If you open a saved workspace from Diagnostic View multiple times, the workspace does not open and does not respond.
To work around this issue, close the Diagnostic View and reopen the workspace again.
Do not use the Modify Time configuration window to change the time period in chart in Diagnostic view
Symptoms
When you try to change the time period for a chart from the Modify Time configuration window in Diagnostic view, the change is not reflected in the chart after you run.
Resolving the problem
To workaround this issue, change the time period for a chart from the Modify Time list in the Diagnostic View.
Threshold violation settings in User Profile Management are not reflected correctly
When you change the threshold violation settings for either SLA or NOC profiles from Administration > User Profile Management in Dashboard Application Services Hub, the settings are not reflected correctly in a report that is created in the Diagnostic View with the same profiles.
DV Navigator from Define Resource View does not launch
This issue is seen in Internet Explorer 8 only.
A bookmarked report in Defined Resource View does not open in Mozilla Firefox
Use Internet Explorer 8 or 9 if you want to view a bookmarked report.
You cannot view DataView reports if you set the DATAVIEW_CONTEXT to a non-default value
Do not change the DATAVIEW_CONTEXT in a non-root installation. The default value for DATAVIEW_CONTEXT must be PV.
Do not use the DataChannel collector numbers 500 and above
If you assign collector numbers 500 and above, the collectors might not work correctly. Currently, collector numbers 500 and above are not supported.
Avoid deleting a DataChannel as all other DataChannels and associated DataLoad collectors also get deleted
It is a good practice to keep a copy of the previous topology before you update the DataChannel configuration. Typically, avoid deleting a DataChannel.
Install DB2 10.1 Fix Pack 3 to resolve issues related to administering and performance of DB2
Symptoms
You might encounter some administration and performance issues in DB2 10.1.0.1 that is the supported version for Tivoli Netcool Performance Manager 1.4.
Resolving the problem
To resolve those issues, install DB2 10.1 Fix Pack 3. You can download the DB2 10.1 Fix Pack 3 Universal Fix Pack from the following location:
http://www-01.ibm.com/support/docview.wss?uid=swg24035759
Note: The DB2 10.1.0 Fix Pack 3 must be applied on the DB2 V10.1.0.1 after the installation of Tivoli Netcool Performance Manager 1.4 is complete. Otherwise, the Prerequisite Scanner fails where the scanner is expecting DB2 version to be 10.1.0.1.
Follow these instructions to apply the new fix pack level:
The supported scripts that are used for collecting the sizing information do not work on DB2
Currently, the following supported scripts that are used for collecting the sizing information:
· check_proviso_sizing_adv.sql
· check_proviso_sizing.sql
· check_proviso_db.sql
These scripts do not work on Tivoli Netcool Performance Manager with DB2 as the database support.
Some additional UBA properties with no values are seen in a loaded topology in upgrade scenario
Symptoms
When you load a topology from the database, you might find some additional properties with no values in an upgrade scenario.
Resolving the problem
To resolve this issue, load the particular technology pack XSD file again. The original properties of the technology pack are loaded back.
Change the password for PV User in a migrated UBA channel from topology.xml file
When you want to migrate a UBA DataChannel from one host to another host, change the password for PV User from topology.xml file and deploy again.
Element descriptions in the Resource Editor are incorrect
Symptoms
In the Resource Editor, click Element > Apply Filter. You notice that the description is the same for all elements.
Resolving the problem
To view the correct description for an element, select the element and click Details. The property SysDescr displays the correct description for the element.
In Tivoli Netcool Performance Manager 1.4 GA build, High Availability Manager (HAM) unistallation is not supported
Symptoms
When you try to remove the Managed Definitions and spare collectors in a HAM environment from Topology Editor, it results in corrupting the FTE source values of an unrelated DataChannel. You notice this issue when more than one 3+2 Managed Definitions are present. Therefore, HAM uninstallation is not supported currently.
For more information about HAM, see Installing Tivoli Netcool Performance Manager -Wireline Component.
Diagnosing the problem
In the Topology Editor, the FTE source directory points to the primary collector SNMP.*.*/output source only and not to the primary and spare SNMP.*.*/output sources. Hence, the NRAW files are not moved into the FTE when there is a failover of primary collector to the spare collector. This results in data that is stuck in the spare collector's output directory.
Resolving the problem
If you have uninstalled and observe that the spare collector data is not moving into the FTE, follow these steps:
· Load the topology from the database.
· Click High Availability Manager and go to the Managed Definition of the required HAM.
· Remove the Managed Definitions.
· Go to the Collector Process folder and remove all spare collectors.
· Create the HAM managed definitions and spare collector processes, and then save the definition.
· Run Deployer for Installation.
· Load the topology from the database.
· Check if the FTE contains two sources.
· Restart the dccmd processes.
Note: If you have not attempted the HAM removal, but planned to do it later, apply the 1.4.0.0-TIV-TNPM-IF0001 before you attempt to remove the HAM.
Uninstallation of any Tivoli Netcool Performance Manager component fails in a 1+1 HAM configuration
Symptoms
When you try to uninstall a Tivoli Netcool Performance Manager component in a 1+1 HAM configuration setup, uninstallation fails. This issue is seen in Tivoli Netcool Performance Manager 1.4 GA build only.
Resolving the problem
To resolve this issue, apply the 1.4.0.0-TIV-TNPM-IF0001 fix pack.
Data from HAM spare collector is not processed if the DataLoad path is different from the primary collector's DataLoad path
Symptoms
In a HAM configuration, when DATALOAD_HOME directory is customized for the host with the primary collector, the value of FTE source property for the corresponding spares is also updated to the DATALOAD_HOME of the primary collector, in this scenario; the data from the spare collector is not processed.
Resolution
To resolve this issue, change the FTE source property value of the primary collector that is referencing the spare host to point to the DATALOAD_HOME of the spare host by following these steps:
1. Go the location where you have installed Topology Editor. By default, /opt/IBM/proviso/topologyEditor
2. Depending on your database, go to the location:
cd /opt/IBM/proviso/topologyEditor/ora/metadata/core/
cd /opt/IBM/proviso/topologyEditor/db2/metadata/core/
3. Open dataChannel.xsd file and search for the element “SOURCE.1”.
4. Set read-only property value to FALSE to edit this property in Topology Editor:
<ext:readOnly>FALSE</ext:readOnly>
5. Save the dataChannel.xsd file.
7. Start the Topology Editor. The “SOURCE.1” property for FTE component of the collector is now editable.
8. Edit the FTE “SOURCE.1” property that contains a reference to the spare host and make it point to the DATALOAD_HOME directory of the spare host. By default, DATALOAD_HOME directory is /opt/dataload.
9. Save the topology and run for installation. Data can be processed for the spare collector.
Aggregated Data Extraction query fails to extract the results into an XML file
When you create an Aggregated Data Extraction by using Mass Data Extraction interface, the results are not extracted into an XML file. Contact IBM Professional Services if you face this issue.
Cannot start the Rule Editor on an AIX machine
Symptoms
When you start the Rule Editor on an AIX machine, you see the following error on the terminal:
[1] 10879174 /opt/datamart/bin/ruleconf[3]: 14942322 Abort(coredump)
Resolving the problem
To work around this issue, follow these steps:
1. Back up the existing ruleconf file.
2. Manually add the following line in the ruleconf file.
==> LDR_CNTRL="MAXDATA=0x60000000" arcget `basename $0` "$@"
Instances of CME and cross collector CMEs crashing
In Tivoli Netcool Performance Manager with IBM DB2 environment, it is seen that when you add a formula from the FRMI utility, there are issues during re-synching of new formulas. This may cause the CME to crash.
There is currently no workaround to this issue. Refrain from adding new formulas by using the FRMI tool. Reinstallations of the CME may resolve the issue for the non-cross collector (CSE) CMEs.
Data flow obstruction at LDR
Symptoms
If you find that the data flow is obstructed at LDR, increase the size of the PV_PV_ADMIN_TEMP_001.dbf table space.
Resolving the problem
Increase the size of the PV_PV_ADMIN_TEMP_001.dbf table space by using the following command:
SQL> alter database tempfile ’/raid_3/oradata/PV/PV_PV_ADMIN_TEMP_001.dbf’ resize 3G
Specify the size as per your requirements.
You cannot view DataView reports if you set the DATAVIEW_CONTEXT to a non-default value
Do not change the DATAVIEW_CONTEXT in a non-root installation. The default value for DATAVIEW_CONTEXT must be PV.
Slow Dashboard Application Services Hub UI response time in Tivoli Netcool Performance Manager with IBM DB2 as the database support
Symptoms
If you find that the Dashboard Application Services Hub UI performance is slow in Tivoli Netcool Performance Manager with IBM DB2 as the database support, run the package binding utility on the DB2 database.
Resolving the problem
To improve the performance of the Dashboard Application Services Hub UI, follow these steps:
1. Make sure that there are no connections to the DB2 database by using the following command:
$ db2 list applications
2. To choose the latest statistics in the database, rebind all the packages in the database by using the following command:
$ db2rbind pv -l db2rbind.log all
Note: Run the db2rbind utility whenever you notice the slow response on the database side. For more information about the db2rbind command, see::
The /opt/oracle folder created by configure_client script has no permission granted to any other users
Distributed Tivoli Netcool Performance Manager installation would failed at remote host.
Resolving the problem
After you run the configure_ora script, assign the following permission to the $ORACLE_BASE directory (for example, /opt/oracle):
1. Log in as oracle user.
2. Run the following command:
chmod 755 /opt/oracle
Threshold lines for different metrics in the same chart uses the same colour-coding
Symptoms
When you have more than one metric in the chart, and has different threshold set for each of the metrics, user will see same color code used to represent the critical and warning threshold line for different metrics.
Resolving the problem
To workaround this issue, you must have the PVM GUI opened, to check the threshold value set for the metric, in order to find out which threshold line in the chart relates to which metric.
Some DataView functionalities might not work if WebSphere Administrative Console Security settings are done correctly
If you find that DataView features such as Synchronize.sh, real time report, Online Help and Personalize Granularity are not working, check that the Security settings on the WebSphere Administrative Console that is accessible via the Dashboard Application Services Hub portal are set correctly.
For more information about Enabling Jazz for Service Management security settings, see
LDR and DLDR logs for IBM DB2 performance
Review different logs to get the complete performance logs.
lastTime value shown in the TopN Near Real Time (NRT) report is incorrect
The lastTime value that is shown in the TopN NRT report is offset by the Server Operating System timezone.
Resolving the problem
You can choose not to display the lastTime column in the report by changing the setting via the DV Navigator.
Conflict of port number and collector number upon migration of DataLoad collectors from one host to another in an upgraded environment
This issue is seen in Tivoli Netcool Performance Manager 1.4 GA build. do not attempt to migrate an existing SNMP DataLoad collector to a host that has a collector with the same service port number. This scenario is applicable in a Tivoli Netcool Performance Manager 1.4 system that was upgraded from a previous release. Such attempt results in database corruption.
Symptoms
Consider the following upgrade scenario:
You want to migrate a deployed SNMP DataLoad collector to a host that has a collector with the same service port number.
In this scenario, the port number of the migrated collector conflicts with the existing collector's port number. In the 1.4 GA build, there was no capability to change the service port number. With this fix, when you attempt to move the collector, you will be required to specify a new service port number in the Move Collector configuration window.
Resolving the problem
Apply the fix pack 1.4.0.0-TIV-TNPM-IF0002, then only proceed with the migration. Specify a new service port number in the “Move Collector” configuration window for the collector during the move attempt.
LDR is stuck at ADDTRUNCATEPARTIOTION
Data is not seen moving into the LDR.
Resolving the problem
Resize the PV_ADMIN_TEMP table space to 3 GB and PV_undo_data files to 5000M
HAM installation - FTPERR appears on fresh install of High Availability Manager
If when checking the proviso.log file you see errors similar to the following:
V1:4159 2012.03.19-09.46.22 UTC FTE.1.1-10594:14390 FTPERR GYMDC10123W Unable to change remote working dir:...//opt/dataload/SNMP.1.1/output
V1:4164 2012.03.19-09.46.24 UTC FTE.1.1-10594:14390 FTPERR GYMDC10123W Unable to change remote working dir: ...//opt/dataload/SNMP.1.1/output
V1:2973 2012.03.19-09.46.38 UTC FTE.2.2-10598:12917 FTPERR GYMDC10123W Unable to change remote working dir: ...//opt/dataload/SNMP.2.2/output
V1:2977 2012.03.19-09.46.40 UTC FTE.2.2-10598:12917 FTPERR GYMDC10123W Unable to change remote working dir: ...//opt/dataload/SNMP.2.2/output
These errors can be ignored as they will disappear once you test HAM failover.
Testing of the High Availability Manager is discussed in TNPM Wireline High Availability Installation and Configuration guide, which is available on ISML:
https://www-304.ibm.com/software/brandcatalog/ismlibrary/
On Linux, if the Check DB step in the Deployer fails, ensure that the kernel parameters are correctly set
On Linux, if the Check DB step fails, ensure the kernel parameters are correctly set. Kernel parameters must be set to the recommended values for the Oracle installation. If any of the kernel parameters are incorrect, the step fails and an error message is logged with the expected value.
You can ignore the fact that the error message refers to "The Solaris semaphore" value. This is an open issue. The message should not just refer to Solaris.
You can set the correct kernel parameter by using the following command:
sysctl <param>=<value>
For example,
sysctl kernel.shmmax=27459232 (or whatever the recommended value is)
If the server has previously been used to install Tivoli Netcool Performance Manager then the existing kernel parameters are sufficient.
RSH is not available as a transfer protocol
The Deployer allows user to select "RSH", "SSH", or "RSH and SSH" for remote execution of commands. The RSH option is not supported. You can choose either the "SSH", option or the default "SSH and RSH" option. SSH needs to be configured for both of these options.
Proviso Pack Installer only gives space to enter one Tivoli Integrated Portal server at a time
You need to use the Topology Editor to configure multiple servers to get the check list with multiple servers. If there is no topology documented configured in the database, the screen will only allow you to enter the log in information for one server at a time.
You can either deploy the Technology Pack repeatedly by giving a different Tivoli Integrated Portal server each time using Proviso Pack Installer or you can use the DataView’s export.sh and import.sh scripts to move the content from one Tivoli Integrated Portal server to another. For more information on the export.sh and import.sh scripts, refer to the Using and Administering DataView .
Proviso InfoD startup scripts error
When installing DataMart, the Tivoli Netcool Performance Manager installer creates two files, one in /etc with the name pisrc3113ProvisoInfoServer.sh, and the other in /etc/rc.d/init.d/ with the name pis3113ProvisoInfoServer.
When running the pis3113ProvisoInfoServer command located in the /etc/rc.d/init.d directory, the following error is shown:
$ /etc/init.d/pis3113ProvisoInfoServer
bash: /etc/init.d/pis3113ProvisoInfoServer: /usr/bin/sh: bad interpreter: No such file or directory
Even if you change the directory from #!/usr/bin/sh to #!/bin/sh in the pis3113ProvisoInfoServer script and run the script again, the following error is shown:
$ /etc/init.d/pis3113ProvisoInfoServer
/etc/init.d/pis3113ProvisoInfoServer: line 95: .: filename argument required
.: usage: . filename [arguments]
Resolving the problem:
The Proviso InfoD process must be manually started on the Linux DataMart system that is rebooted. To accomplish this, follow these steps:
1. Log in to the DataMart server as pvuser.
2. Source the dataMart.env file.
3. Execute the command: pismgr start
Install steps do not appear if JRE step is unchecked for a DISC on remote host
When installing a DataMart with a Discovery Server to a remote host and this is the only host being deployed, if the JRE host is unchecked in the Host Summary page, the install DataChannel steps do not appear in the Deployer. This only occurs in a High Availability environment.
Resolving the problem
To workaround this issue, check the JRE host in the Deployer host selection pane. If the Deployer deploys to the DataMart host and the JRE host, all steps appear.
No trailing white space in the value for DiscoHostName for a High Availability install
The value for the DiscoHostName resource in the PVMHOME/res/C/inventory.User.res file must not have any trailing white space. When there is a trailing white space in the value for DiscoHostName, the GUI fails to utilize the value properly.
Unable to remove the database from the topology
If you are unable to remove the database from the Topology, run the deployer for uninstallation. You are presented with the Load Channel Configuration and Load Collector Configuration steps only. Run the steps and reload the topology from the database. The Remove action is now enabled on the Database Configurations object in
The Version Registration table contains DataLoad SNMP 0.0 entries for the previous version
A Version Registration table may contain DataLoad SNMP 0.0 collector entries for a previous version of Tivoli Netcool Performance Manager. These table entries, if present, are put there by the Topology Editor during the Upgrade Process.
When the Topology Editor loads the topology from a previous version it creates version registration entries for the previous version for all of the secondary DataLoad instances involved in HAM 1+1 instances.
This version registration entry does not impact anything in the system, except the Topology Editor and deployer.
Any DataLoad SNMP 0.0 for the previous Tivoli Netcool Performance Manager version within the version registration table can safely be ignored in the topology.
Load_SQL_Module fails as client is still connected to the system during an upgrade of Oracle Enterprise for a Tivoli Netcool Performance Manager
When Oracle Enterprise Management GUI client is still connected to the DB, additional steps are required to upgrade Oracle Enterprise for a Tivoli Netcool Performance Manager upgrade. You must run the following steps before doing an upgrade of Oracle Enterprise for the Tivoli Netcool Performance Manager to make sure that there are no more clients connected to the DB before applying an Oracle patch:
1. Connect to the system as a Tivoli Netcool Performance Manager database administrator (By default, pv_admin/pv@PV) using the sqlplus command:
sqlplus pv_admin/pv@PV
2. Check for connected user sessions:
Select * From V$Session Where Nvl( Username, User ) != User;
3. Close any sessions that are shown by the above query by closing the application listed. For example, close the DataChannel components and close any sqlplus sessions.
4. Check for connected user sessions again. If there are still sessions active in v$session and you cannot find the application to close, close each session with:
alter system kill session 'SID, serial#';
Where SID and serial# correspond with the session listed in v$session. For example:
alter system kill session (7,258);
5. Ensure that there are no connected user sessions before starting the patch process.
SNMP does not check for alternative Ipv4-Ipv6 addresses on DataLoad
The format “::10.127.77.7” is a deprecated IPv4 mapped IPv6 address. It is a valid address, but how the format is interpreted is up to the underlying operating system stack. The new format for IPv4 mapped addresses is “::FFFF:10.127.77.7”.
Linux and Solaris treat the “::10.127.77.7” address as a true IPv6 address. Collections do not work on these platforms unless a system has the address.
AIX treats the “::10.127.77.7” format the same as the “::FFFF:10.127.77.7” format. This allows collections to work because the IPv4 address is being used.
If you run “dialogTest2 IPCacheDump”, you can see that “::10.127.77.7” is mapped to “::FFFF:10.127.77.7” on AIX, and remains as “::10.127.77.7” on Solaris/AIX.
It is recommended that the standard IPv4 to IPv6 mapping are used on all three platforms for consistency. The format is “::FFFF:10.127.77.7”.
This issue is not a problem with Tivoli Netcool Performance Manager. This issue is caused by a difference in how different operating systems interpret certain IP addresses.
Limitation of qping
qping only supports up to 64 IP addresses on the command line at one time.
For IPv4 addresses, if there are 100 devices to the list of 'Specific elements' in the 'IPaddress include area' of the Inventory discovery tool wizard, then only 64 of these devices are discovered.
For IPv6 addresses, if there are 100 devices to the list of 'Specific elements' in the 'IPaddress include area' of the Inventory discovery tool wizard, then all 100 devices are discovered. There is no ping or SNMP message issued from the collector for the 36 undiscovered devices.
Correct notation for the Rule Editor filter
The following IPv6 style addresses should not be used:
%(Element.ipAddress)='0:0:0:0:0:FFFF:10.127.77.46'
%(Element.ipAddress)='::FFFF:10.127.77.46'
%(Element.ipAddress)='2002:092a:0111:0200:0010:0127:0077:0046'
The correct notation is as follows:
%(Element.ipAddress)='2002:92a:111:200:10:127:77:46 '
The TARGET HOST field is not refreshed when you select or toggle the "Change Target Host for BLB and IF to x host" option in Alcatel 5620 Bulk Load Balancer (BLB)
In the Topology Editor’s Logical View, if a user selects a BLB and uses the right-click operation to move the IV and BLB from channel to collector host or vice versa, the BLB TARGET HOST property will not automatically be refreshed once the operation is complete.
You need to click on the property or click away and then back to the BLB object again to see the refresh value. As a precaution, save the topology prior to the refresh to ensure the value in the memory is always the latest.
Cancelling topology load can leave problems view populated
If you cancel a topology load, the partially loaded topology is cleared from the Topology Editor views. However, the problem view sometimes retains a list of problems with the partially loaded topology. This issue has no functional impact.
Ignore MOVE_FAILED message for bufferedContainers file
The bufferedContainers file exists in the directory but CME is looking at elsewhere for the file.
An example of the MOVE_FAILED message in the proviso.log:
V1:12750 2010.11.25-02.02.50 UTC CME.1.2000-3867:5492 MOVE_FAILED GYMDC10421W Failed to move 'file:///opt/datachannel/CME.1.2000/SLE.2000/state/temp/state/bufferedContainers' to 'file:///opt/datachannel/CME.1.2000/SLE.2000/state/bufferedContainers', details: 'No such file or directory ("/opt/datachannel/CME.1.2000/SLE.2000/state/temp/state/bufferedContainers")'
When there is a MOVE_FAILED message in the proviso.log for the bufferedContainers file, then it can be safely ignored.
New logging process for DataChannel requires extra step when changing log settings
In the Topology Editor, the "Log Server" the properties are available.
The property FILTER is used for the proviso.log and the property LOG_FILTER is used for the tnpm.log.
When the values are changed to "FEWI 1234" for FILTER or LOG_FILTER, restarting the dccmd and findvisual will not effect the changes as LOG is not under the findvisual process. Logging is now a Java process.
A user must find the Java process for the LOG and kill it. Using ps -ef|grep analytics.Main will find the process to be killed. Kill this process and restart the log by running logw (the watchdog script for LOG) or wait 5 minutes for the cronjob to restart the process.
The Java process will be similar to this:
pvuser 26488 25744 0 18:01:59 pts/75 1:05 Java -Xms256m -Xmx384m com.ibm.tivoli.analytics.Main -a LOG
HAM - when restarting pvmd, core log is created
If you kill pvmd and don't kill the watchdog, you will get a "core" dump when the watchdog stops itself.
User action: you can ignore the core dump if you can see on startup that the core dump is the result of the WatchDog process.
Issue in starting the Topology Editor on an AIX 6.1 Technology Level (TL) 8 system
Symptoms
When you try to install Tivoli Netcool Performance Manager 1.4 on an AIX 6.1 TL8 system, the Topology Editor might not start. You might notice a javacore memory dump issue.
Resolving the problem
To resolve this issue, use AIX 6.1 TL 7. Or, replace the glib2-2.14.6-2 with glib2-2.12.4-2 rpm package on an AIX 6.1 TL8 system.
Note: The recommended AIX version for installing Tivoli Netcool Performance Manager 1.4 is AIX TL7. Make sure that you compare the packages available in AIX 6.1 TL7 and AIX 6.1 TL8 to understand the difference.
To resolve the other javacore memory dump issues effectively, you can use IBM Thread and Monitor Dump Analyzer for Java. For more information, see
https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=2245aa39-fa5c-4475-b891-14c205f7333c
For more information about handling dumps, see Debugging from dumps.
Related information
AIX Download and service information
List of issues that you might encounter while installing, upgrading, or using Tivoli Netcool Performance Manager for Wireless.
Invalid argument error is displayed when you install Tivoli Directory Server on RHEL 6.2 server
When you install Tivoli Directory Server on RHEL 6.2 server, the system displays mbind: Invalid argument error message. You can ignore this message.
Loader is recognizing only GMT timezone settings on AIX
When you install Tivoli Netcool Performance Manager - Wireless Component on an AIX system, the loader is recognizing only GMT timezone settings. The loader is operating all other timezone settings as default GMT timezone.
Issues on Dashboard Application Services Hub interface
When you access Dashboard Application Services Hub from various servers, you might see these issues.
You cannot open Common Reporting page of two different servers in the same browser
Symptoms
You cannot open two Common Reporting pages from two different servers in the same browser.
Resolving the problem
To resolve this issue, configure Single sign-on (SSO) in Jazz for Service Management. For more information, see Configuring SSO in Tivoli Common Reporting 3.1.
Mozilla Firefox is incompatible with KPI browser
Symptoms
When you open the KPI browser in Firefox 17, you notice the following issues:
· The browser does not display full string of the cell ID.
· You can select only one cell ID at a time.
· The output KPI selection box does not display the complete KPI name.
· After you select cell ID or KPI name, you cannot delete it. You must select the entity again to clear the previous selection.
Resolving the problem
Use Internet Explorer to view KPI browser instead of Firefox.
Daily history of summary gets truncated in summariser logs
When you run the daily history of summary through the CLI and the summariser-server.log rolls out to a new page, the summary is truncated.
Link to a Resource Metric Viewer report that is sent through an email does not work
Symptoms
After you generate a Resource Metric Viewer report and send it through an email with Include a link to the report option selected, the link does not show the report from the received email.
Causes
The mandatory prompt values are not passed to the report that is opened from the link in the email. This is a Cognos limitation
Resolving the problem
To resolve this issue, follow these steps:
1. Generate a report from the Resource Metric Viewer.
2. Click Keep this version and select Save as report view.
3. Specify a name and location to save the report view and click OK.
4. Go to the location where you have saved the report view and open the report.
5. Click Keep this version and select Email report.
6. Enter the email address in the To field.
7. Select Include a link to the report check boxes.
8. Click OK. When you click the link from the received email, the report opens.
Only one metric group is shown in a report from the deployed complex summary model
Symptoms
When you create a complex summary definition that has a combination traffic KPIs like UDC, peg count and Pcalc, you might see only one KPI in the report studio list after you import and deploy the summary model. The KPI name follows the sequence that is shown in the metric group from Model Maker Extractor. The report studio populates only the first group and the other group is not populated.
Resolving the problem
To resolve this issue, follow these steps:
· Create separate models for UDC, peg count and Pcalc.
· Combine the models. For more information about combining models. For more information, see Installing and Using Model Maker - Wireless Component.
· Publish the combined model.
Reverting to a prompt page in Resource Metric Viewer
If you want to revert to the prompt page on Resource Metric Viewer to edit your selection, click the Run button on the upper right of the page. The prompt page retains the previously elected entities.
Wireless specific tooling issues
Model Maker issues
Known issues with Model Maker and Common Reporting on Tivoli Netcool Performance Manager 1.4, including installation issues, Model Maker and Common Pack Service issues, and Common Reporting issues.
Note: Starting from Tivoli Netcool Performance Manager 1.4, dependency on Model Maker for creating or publishing the Common pack does not exist. Model Maker 1.4 is a wireless only component.
Details of the latest Base Common Pack Suite
| Release Date | Contents | Package |
| April 2014 | TCR Time BCP Wireless BCPs Wireline Common BCP | 1.0.0.4-TIV-TNPM-BCPSUITE This Base Common Pack Suite is packaged and delivered as 1.0.0.4-TIV-TNPM-BCPSUITE.tar.gz file with TNPM 1.4 core software. |
| October 2012 | TCR Time BCP Wireless BCPs Wireline Common BCP | 1.0.0.3-TIV-TNPM-BCPSUITE-FP0001 You can download the 1.0.0.3-TIV-TNPM-BCPSUITE-FP0001 Fix Pack from the following URL: http://www-933.ibm.com/support/fixcentral/swg/selectFix?product=ibm%2FTivoli%2FNetcool+Performance+Manager&fixids=1.0.0.3-TIV-TNPM-BCPSUITE-FP0001&source=dbluesearch&function=fixId&parent=ibm/Tivoli |
| April 2012 (obsoleted by the entry above) | TCR Time BCP Wireless BCPs Wireline Common BCP | 1.0.0.3-TIV-TNPM-BCPSUITE This Base Common Pack Suite is packaged and delivered in 1.0.0.3-TIV-TNPM-BCPSUITE.tar.gz file. This is obsolete as the 1.0.0.3-TIV-TNPM-BCPSUITE-FP0001 contains the latest version of BCPs. |
| January 2012 | Mobile GPRS BCPs | 1.0.0.2-TIV-TNPM-BCPSUITE-IF0002 |
| December 2011 | TCR Time BCP Mobile GSM BCP | 1.0.0.2-TIV-TNPM-BCPSUITE-IF0001 |
| September 2011 | TCR Time BCP Wireless BCPs Wireline Common BCP | 1.0.0.2-TIV-TNPM-BCPSUITE-FP0002 |
For all the existing Model Maker 1.4 known issues, see Troubleshooting Model Maker and Common Reporting.
Tivoli Netcool Performance Manager – Application Studio issues
A tool for creating and publishing simplified and enhanced data models on Dashboard Application Services Hub with IBM® Cognos® 10 support.
When you encounter a problem with using Tivoli Netcool Performance Manager - Application Studio components, the first thing to do is to check the detailed log files for that component. Most issues can be solved by referring to the log files.
Read the following known issues if you are experiencing problems with Common Reporting on Tivoli Netcool Performance Manager.
Restrict the number of KPIs used in creating a report from a Tivoli Netcool Performance Manager data model
Symptoms
When you create a report from a model that has many key performance indicators (KPIs), the report might not show all the KPIs that are selected from a single table.
You might see the following error message:
ORA-01792: maximum number of columns in a table or view is 1000
Causes
This is an Oracle limitation. An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view, which pushes it over the maximum allowable limit of 1000. The unused columns in the table are also counted toward the 1000-column limit.
Resolving the problem
To avoid this issue, plan and create a report with only those KPIs that are needed. Rather than using all the KPIs from a table.
Reporting fails with sort key too long error from a busy hour data model:
This issue occurs when you are creating a report from the busy hour data models.
Symptoms
When you are generating a report from a data model that has too many KPIs, you might see the following error message:
ORA-01467: sort key too long
Causes
A DISTINCT, GROUP BY, ORDER BY, or SET operations require a sort key longer than that supported by Oracle. Either too many columns or too many group functions are specified in the SELECT statement that is used to pull the KPIs from a Stored Busy Hour definition of a data model.
Resolving the problem
To avoid this issue, plan and create a report with only the required KPIs alone and not use all the KPIs for creating the report.
For all the known issues in Tivoli Netcool Performance Manager – Application Studio , see
http://www-01.ibm.com/support/knowledgecenter/SSBNJ7_1.4.0/com.ibm.tnpm_1.4_kc.doc/npm_as/ctnpm_npm_as_troubleshoot_npm-as_common_reporting.dita
Data values that are displayed in the report do not match with the columns in the database
This issue is due to certain lapses in creating reports. When you create a report,
follow the best practices that are described in the following link:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Netcool%20Performance%20Manager/page/Application%20Studio%201.4%20%28Wireless%20Modelling%29%20-%20Common%20Reporting
Common Reporting issues and limitations
Common Reporting in Tivoli Netcool Performance Manager 1.4 is implemented in IBM Tivoli Common Reporting 3.1.0.2, which is based on a subset of IBM Cognos Business Intelligence functionality.
When working with performance management reports in Common Reporting, you might encounter some of these known limitations or issues.
These issues or limitations can be caused by Tivoli Netcool Performance Manager, or by the underlying IBM Tivoli Common Reporting or IBM Cognos BI products.
For all the limitations and issues with Common Reporting on Tivoli Netcool Performance Manager 1.4, see the Getting Started with Common Reporting Guide.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21672840