Net-Net 2610
 
Net-Net 2620
 
Oracle Communications Application Session Controller
 

PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
 

In this Document

Goal

Solution

Applies to:

Goal

 When opening a Service Request for an Oracle Communications Applications Session Controller or Net Net 2600 system, the logfiles are an important piece of information. Collecting those quickly and without service interruption is important. 

Solution

The OS-E has the ability to collect support data and store it in a single compressed file to be downloaded and forwarded to the Acme Packet support team for analysis. A collect action has been created which allows you to collect the information necessary to troubleshoot problems occurring on the OS-E. By default, the OS-E collects the following data when the collect action is executed.

• Configuration data, including the following:
• Current running configuration (even if it has not been saved yet)
• Current /cxc/cxc.cfg configuration file
• Backup configuration files in /cxc/backup
• Schema files (*.xsd in /cxc/web)
• Certificate files found in the /cxc/certs directory
• Status data which is collected in two forms:
• Text files that contain output equivalent to the status show commands
• XML files that contain the same data, but in a structured format that is machine-readable and is used for automated analysis

 Status data can be collected in two different ways:

• Default collection, in which a standard, pre-configured list of status classes is collected
• Custom collection, in which status classes not included in the default list can be specified
• Crash files found in the /cxc_common/crash directory
• Log files found in the /cxc_common/log directory
• Directory contents

 Basic Usage

After logging into the system, from the CLI prompt, run the “collect” command.

Copy that file, named collect.tar.gz that is located in the /cxc_common/collect directory off of the system and attach that to your SR.

Enabling and Disabling Default Collection Parameters

Using the services > collect > default-collect-settings parameter, you can enable or disable these default parameters. When one of these properties is set to disabled, the corresponding data is not collected.

Note: Do not change the default-collect-settings object unless told to do so by technical support personnel.

Under this object you can also edit the list of status classes, databases, and directories from which data is collected.

The status-class property specifies additional status classes to be collected. This property is a vector, so you can specify multiple entries. In addition, wildcards can be specified as well as the -v property to specify a verbose display in the status text file.

For example:

The database property specifies the databases you want to collect. The valid databases are:

• log
• spotlite
• status
• dos
• directory
• accounting

This property is a vector, so you can specify multiple entries. For example:

Note: Use the directory property with caution as it is possible to specify the collection of enormous amounts of data.

The directory property specifies any additional directories to be collected. For example:

Note: Use the directory property with caution as it is possible to specify the collection of enormous amounts of data.

Customizing Collection Parameters

In addition to the default parameters, you can configure custom collection parameters using the services > collect > collect-group parameter. Once you create a collect-group, you have the ability to disable the default collection parameters, certificates, status, crash-files, and log-files for that collect-group.

The following example shows the OS-E configured to collect only data related to accounting, while disabling collection of the other default collection parameters:

To collect this customized data, specify the group name when executing the collect action.

Managing Collection Output Files

You can specify where the output files will be stored via the services > collect > directory property. The default (/cxc_common/collect) is sufficient in most cases. However, if you are collecting the contents of large databases, this property allows you to specify a mount with more available disk space. When a new collect file is created, the old files are saved as backups. Older backup files are deleted when the number of backups exceeds the services > collect >max-old-files property.

Collecting Data from a Cluster

By default, the collect action collects data only from the box on which it is executed. Cluster-wide data collection can be specified by adding the cluster parameter to the action. To collect the default data throughout the cluster, you must specify the default parameter.

 To collect custom data from a configured collect-group, specify the collect-group (in this example accounting is used).

When cluster-wide data collection is specified, each OS-E collects the appropriate data independently and simultaneously. The OS-E on which the collect action is executed then combines the resulting data into a single file.

Viewing Status Classes Being Collected

The show collect-status-classes action displays which status classes are being collected. When entered with the default parameter, the OS-E default status classes are listed.

 You can also use the show collect-status-classes status provider to display status classes defined in custom configurations. The following shows accounting as an example.

Collect Log Messages

The log class ‘collect’ has been added. The following messages are logged:

• collect[warning]: Collect action invoked with the following arguments:
• collect[info]: <various progress messages>
• collect[warning]: Collect action succeeded after X seconds; file ‘/cxc_common/
• collect/collect.tar.gz’ is X bytes
• collect[error]: <various error messages>
• collect[error]: Collect action failed; <error message>

The recommended setting for the ‘collect’ log class is ‘warning’. The ‘info’ setting produces many log messages, all of which will appear in the log file (e.g., /box1/ box1.txt).

This solution has no attachment