inPilot Administration and Management


inPilot Administration and Management
 
This chapter provides information on administering and managing the inPilot application.
This chapter describes the following topics:
Launching the inPilot GUI
To launch the inPilot interface:
 
 
1.
http://<inPilot-server-hostname or IP address>:<apache port>
For example, http://10.4.5.2:8080
2.
The password must meet the following criteria:
It is recommended to use the following browsers:
Note that:
Administration
This section provides information on how to administer and manage the inPilot application.
Managing User Accounts
The inPilot application provides two levels of access privileges:
 
 
Important: Only administrator with admin name can create user accounts.
Managing Gateways
The inPilot application supports configuring multiple gateways for which reports can be customized and generated. Gateways are the chassis from which EDR and bulkstat files are fetched to the reporting server.
 
Important: Users with administrative privilege can only add and manage gateways.
When a gateway is added through the GUI, a directory by the name of the gateway is created in the <inpilot_install_dir>/starbi/server/data directory.
The gateway directory structure looks like the following:
<data directory>
|
|--> <Gateway name>
|
|--> edr
The inPilot application expects the EDR files in the directories that are created when adding the gateway.
Configuring Logging
The inPilot application facilitates logging to trace and debug problems identified within the reporting system.
 
Important: Users with administrative privilege can only manage logging.
Operations and Management
This section provides information on the scripts that can be used to manage the inPilot components and the reports.
 
Using the Maintenance Utility
A shell script utility called serv is included with inPilot in the <inpilot_install_dir>/starbi/bin directory.
 
This serv script can be used to manage the following inPilot processes:
This utility can report the status of the inPilot processes on the system or it can be used to stop the inPilot process.
Following are the options available with the serv script:
./serv { psmonitor | scheduler | postgres | apache } [ start | stop | status ]
 
For example, if you want to start only the PSMON, then enter the following command:
./serv start psmonitor
or
./serv psmonitor start
Important: If you stop the inPilot process, make sure that PSMON is not running. Otherwise PSMON will restart the inPilot application.
The following is a sample output of the serv status command:
---------------------------------------------------
--------------- inPilot Process Status ------------
   PID Process Status
---------------------------------------------------
4245 Process Monitor Running
4256 Scheduling server Running
4267 Postgres Server Running
4289 Apache Server Running
---------------------------------------------------
Using the PSMON Script
PSMON is a perl script that is used to monitor the Scheduling Server, Postgres Server, and Apache Server processes. This script can start or stop the processes based on certain thresholds specified in the inPilot configuration file. The PSMON respawns any dead processes using the set of rules defined in the configuration file.
This script can also optionally send notifications to users via e-mail.
Generating Reports in Excel Format
 
To generate the reports in excel format, execute the following script from the <inpilot_install_dir>/starbi/bin directory.
./get_excel_report.sh -day <date for report generation> -f<path where report to be stored> -filter<filter for the report>
The script takes three parameters, the date for which report is to be generated, the path where generated report is to be stored, and the filter for the reports. The date must be in mm-dd-yyyy format only, and the filter can be based on Type Allocation Code (TAC) or Access Point Name (APN).
Using the unanonymize_msisdn.sh Script
inPilot currently supports reporting of subscriber’s private data like Mobile Station Integrated Network (MSISDN) both in GUI and excel format. This particular subscriber data is visible only to users with administrator privilege. By default, the excel report will be presenting MSISDNs in an encrypted format in all subscribers based reports.
A separate shell script utility, unanonymize_msisdn.sh, is available to decrypt the MSISDNs. This utility will check for user’s privilege before decrypting the MSISDNs list. It will prompt for the GUI administrator password.
To decrypt the MSISDNs, execute the following script from the <inpilot_install_dir>/starbi/bin directory:
./unanonymize_msisdn.sh -u <username> -f <file containing list of encrypted MSISDNs -o <output file path>
Important: Please note that the users require GUI administrator credentials to access this utility.
Using the generate_dns_mapp_sql.sh Script
To generate the DNS mapping for the specified list of IP addresses, execute the following script from the <inpilot_install_dir>/starbi/bin directory:
 
./generate_dns_mapp_sql.sh <input file for IP> <output file where mapping should be stored>
This script is used to perform Internet DNS lookup of the specified IP addresses. It uses the ‘nslookup’ system administration command to find the DNS name of the specified IP. Please note that the machine must be connected to Internet for successful execution.
Using the getSupportDetails Script
In the event additional troubleshooting assistance is required, debugging information can be collected using a script called getSupportDetails.pl. This script collects different log files and captures the output of certain system commands that aid in troubleshooting issues. This script is packaged with inPilot in the <inpilot_install_dir>/starbi/tools/supportdetails/ directory.
 
This script refers to an XML file to get the list of logs. This XML file resides in the same directory as the script. Once executed, the script retrieves the contents of logs, files, folders, and output of certain commands and prepares a zipped file (inpilotsupportDetails.tar.gz), by default it is placed in /tmp/log directory.
Requirements
Perl 5.8.5 and above is required for running the script.
Apart from standard Perl modules (which are included in default installation of Perl), some additional modules are required for running the script. The list is as follows:
These modules are installed by default by the product. Please ensure that the above mentioned modules are installed when using a different installation of Perl.
To run the script, change to the directory path where the script is present and type:
./getSupportDetails.pl [--level=...] [--xmlfile=...] [--help]
 
For example, ./getSupportDetails.pl --level=4 --xmlfile=/tmp/getSupportDetails.xml
Supported Levels
The logs that can be collected for different levels are as follows:
netstat -an
ifconfig -a
df -k
etc..
ipcs
ps -eaf
etc..
Server script parameters
The number of files being processed during each parsing interval for HTTP and non-HTTP EDRs can be controlled using the following parameters defined in settings.py file.
EDR_TOTAL_NO_OF_FILES = 25
EDR_MAX_NO_OF_PROCESSES = 5
HTTP_TOTAL_NO_OF_FILES = 25
HTTP_MAX_NO_OF_PROCESSES = 5
With the above default configuration, if the number of files being accumulated are less than 25 and not in multiples of 5, then inPilot spawns one more process to parse the remaining files.
Troubleshooting inPilot
This section provides information on how to resolve situations you might encounter with using inPilot software. This section provides problem definitions, their likely cause(s), and solutions.
 
 
 
On the Tools menu, click Clear Private Data.
Select Cache check box.
Click Clear Private Data Now.
On the Tools menu, click Internet Options.
Click Delete.
Select Temporary Internet files check box.
Click Delete.
Important: The Firefox version supported for inPilot is 3.0.10 and later. For Internet Explorer, it is 7.0 and later.
 
On the ADMIN menu, check the bulkstats audit under AUDIT. The audit should indicate whether the bulkstats files are being parsed or not. For more information, refer to the inPilot Online Help.
Important: If you do not have Web Element Manager (WEM) application installed, then you should refer to the configuration file in Sample Bulkstats Schema Configuration appendix of the inPilot Installation and Administration Guide.
Important: inPilot is compatible with WEM 9.x. Therefore, you should use WEM 9.x to configure bulkstats on gateways.
 
 
 
 
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883