Oracle Communications Performance Intelligence Center (PIC) Software
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec PIC
 

In this Document

Purpose

Troubleshooting Steps

References

Applies to:

Purpose

 This documents explains all that is necessary to properly configure an Export Server to receive files from an IXP server where DataExport is running.

Troubleshooting Steps

DataExport process on IXP is configured via NSP Datafeed application. In NSP Datafeed, each datafeed has a set of parameters configured by the user to tell where the data is going to be exported: "NFS Remote server", "Remote file system" and "Remote directory"

1. "NFS Remote server" is the IP address of the Export Server (the NFS server that is going to receive the exported csv files)
2. "Remote file system" is the path on the Export server that will be mounted as nfs share to store the data
3. "Remote directory" is the directory in the nfs share where the csv files be stored.

Let's take a example:

The Export Server will have the following IP address: 10.20.30.40 this is the "NFS Remote server" field in Datafeed configuration.

The default "Remote File system" on a preconfigured Export Server is usually /es/es_1 (but it can be any other path if configured properly)

The "Remote directory" is the folder where you want your csv files to be stored in remote file system. For the example we will call it es_test

To summarize the csv files will be transfered via NFS to a mount point 10.20.30.40:/es/es_1 and written into the es_test folder. That means the customer will find the files in /es/es_1/es_test on 10.20.30.40.

On the server exporting the data the mount point 10.20.30.40:/es/es_1 is mounted on a subfolder of /usr/TKLC/TKLCdataexport/mount/, in this example it will be /usr/TKLC/TKLCdataexport/mount/10.20.30.40+es+es_1. The NFS share is mounted and unmounted automatically by DataExport process on the servers exporting the data. There is no need to mount it manually.

Note that es_test does not need to exist, the DataExport process will create it automatically but the mount point /es/es_1 must already exist on the export server, if it does not then DataExport will not be able to mount the NFS share.

Now the export server itself must be configured to accept inbound NFS connections from the server where the DataExport process is running. In order to do that the following conditions must be met:

1. NFS (2049 UDP and TCP) port and ECHO (7 UDP and TCP) port must be opened between the exporter server (where DataExport runs) and the export server.
2. /etc/exports file on the export server must contain the path shared via NFS, the name or IPs of the exporter servers and the following options: (rw,sync,anonuid=-1). If the name of exporter server is used then that server must be present /etc/hosts to allow name to IP resolution. if the content of /etc/exports is modified, used "exportfs -f" as root user to make sure the NFS daemon refreshes its config.
3. The path shared via NFS must have read and write permissions for the cfguser user.
4. cfguser must be part of cfg group and have a UID of 2000 (this can be verified in /etc/passwd)

Getting back to our example:

The content of /etc/exports on 10.20.30.40 export server would be the following:

Note that the example is using wild cards to determine the exporter server name: any servers with a name defined in /etc/hosts and starting with ixp0001- will be allowed to open an NFS share to /es/es_1 on 10.20.30.40.

/es/es_1 must be owned by cfguser from the cfg group (UID and GID = 2000 ) with a minimum permission level of 750: 

References

This solution has no attachment