User guide

MPR > IMA Link > Error Management Near-End.
General Alcatel-Lucent 5620 SAM LogToFile 2.2.0.0 Technology Pack
issues
These are the general issues for Alcatel-Lucent 5620 SAM LogToFile 2.2.0.0
Technology Pack.
Data for the Inbound Errors might not be displayed
Symptoms
If you run the Packet Health for LAG interface Group report on the Tivoli
Integrated Portal, data for the Inbound Errors might not be displayed. To run the
Packet Health for LAG interface Group report, browse to the following path on the
Tivoli Integrated Portal: NOC Reporting > Alcatel-Lucent 5620 SAM > SAM
Router Health > Link Aggregation Groups (LAG Interfaces). On this report, in
the table, the data for the Inbound Errors might not be displayed.
SAM server generates the XML file that contains more than
one datapoint
Symptoms
In the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 technology pack, the SAM server
generates the XML file that contains more than one datapoint for the same
resource. For example, at the SAM server, if you configure the OAM classes for 5
minutes, the OAM XML file is generated after every five minutes. However, this
XML file contains more than one datapoint for the same resource. As a result, the
CSV file that is received by the UBA also contains more than one datapoint. Only
the first datapoint is processed properly while the remaining two datapoints are
ignored.
The description property is not updated in the Resource
Editor
Symptoms
In the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 technology pack, on the SAM
server, you modify the Description property for SAP, SAP Queue, and Network
Queue. The JMS update event is triggered, and the modifications are reflected in
the CSV files that are produced by DataStage. However, these modifications in the
Description property are not reflected in the Resource Editor after the UBA
processes the CSV files.
SQL error occurs during the Fulldump process
Symptoms
After you install the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology pack
for the first time, you configure multiple UBA collectors. For example, you set
collectors that are numbered 100 and 102 for the Performance metrics, and
collectors that are numbered 101 and 103 for the Accounting metrics. When both
the Performance or Accounting collectors process the Fulldump file at the same
time, SQL error occurs.
Resolving the problem
To avoid this problem, you must not start more than one Performance or
Accounting collector during the resource provisioning. You must start one
Performance and one Accounting collector, and wait until the corresponding
Fulldump files are processed. You can then start the remaining Performance and
Chapter 11. Troubleshooting Alcatel-Lucent 5620 SAM LogToFile Technology Pack 77