ND Reports Troubleshooting

The most frequent problems related to ND Reports

are missing reports, missing cells or wrong data.

ND reports troubleshooting steps can be broadly

classified into 2 categories:
Entire report missing. Missing cells or wrong data

For internal use only 1 Nokia Siemens Networks

Submitted by: Rahul Jain-61354367 / 5/1/2012 1:29 AM

Case-1(Entire report missing)

Step 1
Ask customer to send the problematic report and SQL script from
$PRODUCTROOT/content/ndobss for which report is wrong. For Eg. Ndp111mx.sql.

Step 2
Analyze the report if error is displayed in the report itself such as Unable to extend
tablespace or Table or view doesnt exist

Step 3
In case error is Unable to extend tablespace as in step-2, capture the tablespace name
and extend its size and then retry the report.

Step 4
In case error is Table or view doesnt exist, its again a tablespace error but complete
details can only be seen in /m/home/omc/nd_tmp.lst file. Therefore login into target system, run the report using CLI and capture the content of nd_tmp.lst file and it will display the tablespace name which can be extended to resolve the error.

For internal use only 2 Nokia Siemens Networks

Submitted by: Rahul Jain-61354367 / 5/1/2012 1:29 AM

Case-2(Missing cells or wrong details)

Step 1
Ask customer to send the problematic report and SQL script from
$PRODUCTROOT/content/ndobss for which report is wrong. For Eg. Ndp111mx.sql. Also ask for report which shows the list of missing cells.

Step 2
Since a single report is using 1 or more tables to collect data, it may happen that data for
NE is not present in OSS table itself. Therefore, check each and every table for raw data into OSS using the counter used displayed in the beginning of every ND report. For Eg. P_nbsc_power, p_nbsc_rx_qual etc

Step 3
In some of the report like ND 208, trx not carrying any traffic will be missing from the
report, therefore please verify from the report details(in beginning of every ND Report) about the report type. Also analyze the missing data using the report that is fetched using 0 threshold. Reports fetched without any threshold will display the complete details.

Step 4
Also compare the SQL script provided in step1 with any other site for any discrepancies
using any comparison tool.

For internal use only 3 Nokia Siemens Networks

Submitted by: Rahul Jain-61354367 / 5/1/2012 1:29 AM

Case-2 Contd

Step 5
ND report with wrong data could be due to database inconsistencies or wrong SQL script. Run RAC doctor scripts, compare SQL script as stated in step-4 and then verify the results.

For internal use only 4 Nokia Siemens Networks

Submitted by: Rahul Jain-61354367 / 5/1/2012 1:29 AM

Known Issues

ND reports related to adjacencies like 60, 61, 70 etc displays wrong adjacencies in some cases. This is due to site creating using MML instead of CM plan. In case these discrepancies are not solved even after running RAC doctor, kindly ask team to re-create some adjacencies using CM Editor and then verify the results.

For internal use only 5 Nokia Siemens Networks

Submitted by: Rahul Jain-61354367 / 5/1/2012 1:29 AM

Attachments

Attached is ND reports detailed manual for reference.

For internal use only 6 Nokia Siemens Networks

Submitted by: Rahul Jain-61354367 / 5/1/2012 1:29 AM