Troubleshooting guide

7 — 5620 SAM database management
7-10 Alcatel-Lucent 5620 Service Aware Manager
5620 SAM
System Administrator Guide
3 Review the Object Count information in the Status panel. The information refers
to the most recent object deletion, and can help you define the appropriate
ageout time and deletion interval values for the policy.
4 Configure the parameters.
5 Save your changes and close the form.
6 If required, edit the ageout constraint policy configuration file to modify the
following parameters in the Deletion Interval panel:
• Synchronization Time—shown as ageoutSyncTime in the configuration file
• Interval (hours)—shown as ageoutInterval in the configuration file
i Log in to the main server station as the samadmin user.
ii Open a console window.
iii Navigate to the /opt/5620sam/server/nms/config directory.
iv Open the AgeoutConstraint.xml file using a plain-text editor.
v Locate the following tag shown in Code 7-1:
<ageout>
vi Locate the object class section that you need to modify; Code 7-1 shows the
residential subscriber instance object class as an example.
Note 1 — The default Qualified Ageout Time for non-DC object types is:
• 24 hours, if the 5670 RAM is not enabled using the 5620 SAM installer
• 1464 hours, if the 5670 RAM is enabled using the 5620 SAM installer
The default value does not change when the 5670 RAM is enabled using
a different method, in which case the value must be changed manually
to enable optimum 5620 SAM and 5670 RAM interoperation.
Note 2 — The Qualified Ageout Time defaults are guidelines. Consider
the following when setting the Qualified Ageout Time:
• A small value can prevent excessive database table growth.
• The value must be great enough to allow sufficient time to upload
the database records to a third-party application.
Caution — Contact Alcatel-Lucent technical support before you
attempt to modify a 5620 SAM configuration file. Modifying a 5620 SAM
configuration file can have serious consequences that may include
service disruption.
Note — If the 5620 SAM is deployed in a redundant configuration, you
must perform the following steps on each main server in the
deployment.
Release 13.0 R2 | May 2015 | 3HE 09815 AAAB TQZZA Edition 01