> Uninstalling the WEM
> This chapter provides the step-by-step procedure of uninstalling WEM application using the GUI-based installation wizard and the console-based installation. Additionally it provides instructions for backing up all the critical files before starting the WEM uninstallation.
> This chapter includes the following topics:

> • | Understanding the Uninstall Process

> • | Determining the Best Uninstallation Method

> • | Using the GUI-based Uninstall Method

> • | Using the Console-based Uninstall Method

> Important: Unless otherwise specified, all information in this chapter applies to both Sun Solaris- and Red Hat Enterprise Linux-based WEM systems.
> Understanding the Uninstall Process
> Upgrading the Web Element software on the server requires that the currently installed version be uninstalled from the server before the newer version can be installed. Failure to do so will prevent your ability to install the new WEM version.
> Important: If you are uninstalling WEM in any clustered setup prior to an upgrade, the node has to be put into maintenance mode first (i.e. removed from the resource group). This ensures that all the processes running on this node are stopped and prevents the active node from failing over to become the standby node. For more information on this procedure, please refer to WEM High Availability Redundancy with Cluster Application in the appendices.
> Following is an overview of the uninstall process.
> Step 1 - Make Backup Copies of All Critical Files
> This step requires that you archive, at a minimum, the following files.

> • | All data files, typically located in the /<ems_dir>/server/data directory and all subdirectories residing there (i.e. /bulkstats, etc.).

> • | PostgreSQL data files, located in the ~postgres/data or users/postgresx.x.x/data directory. Refer to the Backing-up WEM Databases section of the WEM Database Maintenance chapter in this guide for more information.

> Important: Downgrading the WEM application to an earlier version is not supported at this time. You must uninstall the current version and install the older version using the instructions located in Installing the WEM Software chapter of this guide. Please contact your local sales representative for information on preserving data stored by the current WEM instance prior to uninstalling.
> Step 2 - Uninstall WEM Application
> The process used to perform this uninstall is dependent upon the method used to install the version currently running. See the section below for information on how to determine which installation method was used previously.
> Whichever uninstall method is used, it is generally preferable to install the new version of the application using the GUI-based installation method.
> Determining the Best Uninstallation Method
> The WEM, and its ancillary components such as the Apache web server and PostgreSQL database engine, may be uninstalled using one of two methods.

> • | GUI-based method: This method is the most often used uninstallation procedure. Requirements for using this method include:

> • | Logon account to the WEM server with display terminal (monitor) attached and some X-Windows client installed on server.

> • | Network connectivity to WEM server via Telnet or SSH, using some X-Windows client on remote workstation.

> Important: If the uninstall GUI does not open, add X-windows port (TCP/6000) in the exception list of Windows firewall.

> • | Console-based method: This method is available to users who do not have an X-Windows client available for remote network connectivity to the WEM server via Telnet or SSH.

> It is important to note that the uninstallation method is independent of the method used for installation. For example, if the console-based method was used for installation, either the GUI- or console-based method can be used to uninstall the program.
> Using the GUI-based Uninstall Method
> This section provides instructions for uninstalling the WEM application using the GUI-method.
> Important: The GUI-based uninstall script is designed to protect all the historical data files that are currently in use. However, it is still recommended that you manually perform a backup of these files before continuing.

> Step 1 | Log into the server on which the WEM application is installed. Use the root username and password.

> Step 2 | Go to the directory in which WEM is installed (the /users/ems directory by default) by entering the following command:

> cd /<ems_dir>

> Step 3 | Go to the /_uninst sub-directory by entering the following command:

> cd _uninst

> Step 4 | Execute the uninstall script by entering the following command:

> ./uninst
> A dialog box appears welcoming you to the WEM uninstallation wizard.

> Step 5 | Click the Next button. A dialog appears identifying the processes to be stopped.

> Step 6 | Click Next and follow the on-screen instructions.

> Step 7 | Click Finish to complete the uninstallation process.

> The uninstall script leaves the /ems directory in place with several sub-directories.

> Step 8 | Optional: If all critical and historical data files have been properly backed up, delete the /ems directory using the following commands:

> cd ..
> cd ..
> rm -R ems
> Important: If you decided to keep the /ems directory, it is highly recommended that at the very least you delete the _uninst directory. Failure to remove this directory before installing a new version of the WEM application using the GUI-based installation method will result in a different _uninst directory being created each time you perform a software upgrade. This results in the creation of multiple uninstall directories (i.e. named /_uninst2, /_uninst3, etc.). The uninst file needed for the next uninstall would have to be located there.
> Using the Console-based Uninstall Method
> This section provides instructions for uninstalling the WEM application using the console-based method.
> Important: The console-based uninstall script is designed to protect all the historical data files that are currently in use. However, it is still recommended that you manually perform a backup of these files before proceeding with this procedure.

> Step 1 | Log into the server on which the WEM application is installed. Use the root username and password.

> Step 2 | Go to the directory in which WEM is installed (the /users/ems directory by default) by entering the following command:

> cd /<ems_dir>

> Step 3 | Go to the /_uninst sub-directory by entering the following command:

> cd _uninst

> Step 4 | Execute the uninstall script by entering the following command:

> ./uninst
> -console
> A message appears welcoming you to the WEM uninstallation wizard.

> Step 5 | Enter “1” to proceed. A message appears listing the application processes to be uninstalled.

> Step 6 | Enter “1” to proceed with the uninstallation. A number of messages are displayed indicating the progress.

> Step 7 | Enter “3” to complete the uninstallation process.

> Upon completion, the uninstall script indicates that certain sub-directories were not deleted within the /ems directory.

> Step 8 | Optional: If all critical and historical data files have been properly backed up, delete the /ems directory using the following commands:

> cd ..
> cd ..
> rm -R ems
> Important: If you decide to keep the /ems directory, it is highly recommended that at the very least you delete the _uninst directory. Failure to remove this directory before installing a new version of the WEM application using the GUI-based installation method will result in a different _uninst directory being created each time you perform a software upgrade. This results in the creation of multiple uninstall directories (i.e. named /_uninst2, /_uninst3, etc.). The uninst file needed for the next uninstall would have to be located there.
> Appendix A
> Troubleshooting the WEM
> This appendix provides information on troubleshooting the following:

> • | Issues Pertaining to Installation

> • | Issues Related to Starting WEM

> • | Issues Related to Login

> • | Issues Related to the Web Browser

> • | Issues Pertaining to CORBA Communication

> • | Issues Related to Bulkstatistics

> • | Issues Pertaining to Configuration Backup

> • | Issues Pertaining to Alarms

> • | Issues Pertaining to the Process Monitor (PSMON)

> • | Issues Pertaining to Starting and Stopping EMS Processes

> • | Issues Pertaining to Java

> • | Issues Pertaining to WEM Upgrade

> In addition to the above, instructions are also provided for capturing client and server logs. These are provided in the Capturing WEM Client Logs and Capturing WEM Server Logs using Script sections of this appendix.
> Important: Unless otherwise specified, all information provided in this chapter applies to both Solaris and Red Hat Enterprise Linux-based WEM systems.
> Issues Pertaining to Installation

> Problem: | Installer window doesn't appear.
> Possible Cause(s): |
> • | If you received the “ERROR: could not initialize interface awt - exception: java.lang.InternalError: Cannot connect to X11 window server using ':0.0' as the value of the DISPLAY variable.” message, the display settings of your terminal program may be incorrect, or Exceed is not running on the client machine.
> • | The /tmp directory may be full.
> Action(s): |
> • | Verify the display settings of the terminal application on the client machine are correct.
> • | Verify that Exceed is installed properly on the client machine.
> • | Determine the status of the /var/tmp directory by entering the df -k command. If it is at or near capacity, choose another directory for the Host Base Directory parameter setting. This parameter can be set via the installation process.

> ‌

> Problem: | Received “Unable to install Element Management System <version> over Element Management System: Installed product has newer version.” message when attempting installation.
> Possible Cause(s): |
> • | A later version of the WEM is already installed.
> • | A previously installed version of the WEM was not completely uninstalled, or was uninstalled incorrectly.
> Action(s): |
> • | Completely uninstall the newer version and install the desired version.
> • | Determine if WEM packages exist in the /var/sadm/pkg directory. These packages begin with “EMS”. If packages exist, remove them by entering the pkgrm -n EMS* command. Once they’ve been removed, reinstall the application.

> ‌

> Problem: | WEM components did not start successfully upon installation.
> Possible Cause(s): | A previously installed version of the WEM was not completely uninstalled, or was uninstalled incorrectly.
> Action(s): |
> • | Check the installation log files (located in the directory) and EMS process log files (located in the <ems_dir>/server/log directory).
> • | Enter the ps -ef | grep server command to determine if any process instances from previous installations are running. If so, stop them using the instructions in the WEM Server Files and Operation chapter of this guide. Once stopped, start the processes for the current installation using the instructions in the same appendix.

> ‌
> Issues Related to Starting WEM

> Problem: | WEM server doesn't start.
> Possible Cause(s): |
> • | The PostgreSQL database is not running.
> • | The log directory may have been accidentally deleted.
> • | Processes from a previous WEM are still running.
> • | The “ServerPort” and/or “ServerIIOPPort” port values configured for the WEM are in use by other processes.
> • | The physical IP address of the WEM server might have been changed without modifying other related WEM configuration appropriately.
> Action(s): |
> • | Verify that the Postgres database is running by entering the ps -ef | grep post command. If is not, follow the instructions in WEM Server Files and Operation chapter of this guide to start it.
> • | Determine if the log directory exists in <ems_dir>/server (default directory) using the ls command to display the contents of the directory. If it is missing, create it using the mkdir command and stop and restart all WEM processes using the instructions in WEM Server Files and Operation chapter of this guide.
> • | Enter the ps -ef | egrep “server|bulkstatparser|bulkstatserver|scriptsrv” command to determine if WEM server processes are running and, if they are, what directory did they originate from. If they’re different, stop the processes and restart the server from within the desired installation directory using the instructions in WEM Server Files and Operation chapter of this guide.
> • | Determine if the “ServerPort” and/or “ServerIIOPPort” port numbers specified in the nms.cfg file (located in the <ems_dir>/server/etc directory by default) are already in use. The default “ServerPort” is 22222, and the default “ServerIIOPPort” is 15000. This can be determined by entering the netstat -a command which displays a list of all the process addresses and ports in use in “ipaddress.port” format. If they are in use, either stop the other processes or configure new values for these parameters.
> • | If the WEM server IP address has been changed, the appropriate modifications need to be made in the nms.cfg and /etc/hosts files, as per the WEM IP Address Change Procedure .

> ‌

> Problem: | Postgres doesn't start.
> Possible Cause(s): |
> • | A .s.PGSQL.5432.lock lock file is present in the /tmp directory prior to starting postgres.
> • | Shared resources are not released after another Postgres instance was terminated.
> • | The PostgreSQL system environment variables were not configured properly prior to installation.
> Action(s): |
> • | If the lock file is present, delete it using the rm .s.PGSQL.5432.lock command.
> • | Determine if a previous Postgres instance is still using system resources by entering the ipcs command. If it is, clear the resources by entering the ipcrm command.
> • | Ensure that the PostgreSQL system environment variables were configured properly using the information in Installing the WEM Software chapter of this guide.

> ‌

> Problem: | Received the following error message in postgres log: “2008-09-13 15:57:31 IST bsdb ERROR: column "data_touseravg_bps" does not exist at character 4332008-09-13 15:57:31 IST bsdb STATEMENT: SELECT "sampledate", "sampletime", "vpnname", "vpnid", "apn", "acc_req_sent", ... FROM apn_current WHERE ("boxername"='bngnc22') AND ( ( ("sampledate"='2008-09-13') AND ("sampletime">='33900') ) ... ORDER BY "sampledate", "sampletime", "vpnname", ...; ” NOTE: The table name in the above message is after the 'FROM' keyword.
> Possible Cause(s): | The mentioned table in error logs may not be in sync with the old table. There are two tables for each bulkstat subsystem in database: old and current (for example, card and card_current, port and port_current, etc.).
> Action(s): | There is one workaround for this but there will be data loss for that mentioned counter. Manually drop the column from table to make the tables in sync. There is data loss only for that particular column. After this, restart all the bulkstat processes (bulkstatparser and bulkstatserver). After restarting, bulkstatparser will re-add that column in both the tables and data will be populated for that column.

> ‌

> Problem: | Received the following error message in postgres log: “ERROR: trigger "xxxxxxxxxxxxxxxxxxxx" for table "yyyyyyyyyyyyy" does not exist ERROR: function ffffffffffffffffffff() does not exist ERROR: view "vvvvvvvvvvvvvvvvvvvvv" does not exist”
> Possible Cause(s): | Error messages regarding function, trigger and view are logged in logfile when the DROP statement is executed while initializing the EMS databases. SQL file used for initializing the database contains a sequence of DROP and CREATE statements for every function, trigger and view. These messages do not have any impact on postgres as well as WEM functionality.
> Action(s): | No action required. This is a normal behavior.

> ‌
> Issues Related to Login

> Problem: | Could not login to WEM.
> Possible Cause(s): | Invalid user name or password.
> Action(s): | Verify that the username and password you are entering is correct.

> ‌

> Problem: | Received “Could not connect to server, destroying applet” message.
> Possible Cause(s): |
> • | WEM Server is not running.
> • | Missing Interoperable Object Reference (IOR) files.
> • | A firewall is prohibiting communication between the client and the server.
> • | The user could have been locked out due to multiple failed login attempts.
> Action(s): |
> • | Verify that server processes are running using the information in WEM Server Files and Operation chapter of this guide.
> • | Verify that IOR files are present; they are stored in the <ems_dir>/client/<ems-version-number>/ior directory by default. A number of files ending in .ior should be present. These files pertain to various functions supported by the WEM.
> • | Edit the img.html file (located in the <ems_dir>/client directory (by default) to use fixed ports and open the required ports in the firewall. This requires the configuration of the “FIXED_PORT”, “FIXED_PORT_RANGE_START” and “FIXED_PORT_RANGE_END”.
> • | Verify that all the ports between FIXED_PORT_RANGE_START and FIXED_PORT_RANGE_END (both inclusive) are open on the firewall. If they are not, they should be opened.
> • | If the user is “superuser”, the set_superuser_password script can be used to reset the “superuser” password to the default. If the user is not “superuser” then the administrator needs to be contacted to reset the user’s password.

> ‌

> Problem: | Received “Java policy file is outdated or missing” message.
> Possible Cause(s): | The .java.policy file is either missing from the user’s home directory on the client machine or it has expired.
> Action(s): |
> • | Verify that the .java.policy file is present in your home directory. Refer to Preparing and Using the Client Workstation chapter of this guide for more information.
> • | Copy the .java.policy file from the “Java Policy File” link provided in img.html file to your home directory. Ensure that no extension (i.e., .txt) is appended to the file.
> Important: All instances of the browser must be closed and restarted after the policy file has been updated.

> ‌

> Problem: | Received “Server could not establish connection with client, therefore notifications will not work.” message.
> Possible Cause(s): |
> • | A firewall is prohibiting communication between the client and the server.
> • | The Hosts file does not have an entry for the client PC's hostname and corresponding physical IP address.
> Action(s): |
> • | Edit the img.html file (located in the <ems_dir>/client directory (by default) to use fix ports and open the required ports in the firewall. This requires the configuration of the “FIXED_PORT”, “FIXED_PORT_RANGE_START” and “FIXED_PORT_RANGE_END”.
> • | Verify that all the ports between FIXED_PORT_RANGE_START and FIXED_PORT_RANGE_END (both inclusive) are open on the firewall. If they are not, they should be opened.Edit the Hosts file (located in /etc directory) with the client PC's hostname and corresponding physical IP address.

> ‌

> Problem: | Superuser (any user) account locked.
> Possible Cause(s): | The configured number of consecutive failed logins has been reached.
> Action(s): | Check the configuration of the no limit ConsecutiveFailLogin parameter in the ua.cfg file (located in the <ems_dir>/server/etc directory by default). If users are frequently locked out due to reaching the maximum limit, you may consider increasing the limit, or disabling the functionality. You may also consider reducing the amount of time the account is locked out by modifying the configuration of the no locked out LockOutInterval parameter also contained in the ua.cfg file.

> ‌
> Issues Related to the Web Browser

> Problem: | WEM Client cannot be started.
> Possible Cause(s): | JRE 1.4.x is installed on the client machine.
> Action(s): | JRE 1.4.x is not supported. If it is currently installed on the client machine, uninstall it and install either JRE 1.5 or 1.6.

> ‌

> Problem: | Not able to invoke help
> Possible Cause(s): | The browser is configured to block pop-ups.
> Action(s): | Configure your browser to allow pop-ups from the WEM server.

> ‌

> Problem: | WEM Client-Server version mismatch message is received.
> Possible Cause(s): | Attempting to login into an older version of the WEM after having logged into a newer version of the application.
> Action(s): | This is caused by the browser storing the.jar files for the newer version of the WEM client in its cache.
> • | For JRE versions greater that 1.5: The Temporary Internet Files group in the General tab of the Java Control Panel should be used to disable caching.
> • | For JRE versions greater that 1.6: The Temporary Internet Files group in the General tab of the Java Control Panel should be used to disable caching.

> ‌

> Problem: | After WEM upgrade or installation of a new version, various screens, for example Graph/ Current Alarm View, do not open.
> Possible Cause(s): | Check the java console and if you get exceptions like "Exception in thread "AWT-EventQueue-2" java.lang.NoClassDefFoundError", it could be the case that the browser cache is enabled on your workstation and needs cleanup.
> Action(s): | Cleanup the temporary internet cache from your browser and re-invoke the WEM Client.

> ‌
> Issues Pertaining to CORBA Communication

> Problem: | IMG is unmanageable.
> Possible Cause(s): |
> • | The WEM Server cannot communicate with the system due to network issues.
> • | There is an ORBEM client identification mismatch between the chassis and WEM.
> • | The ORBEM client on the chassis is disabled.
> • | There is an IIOP port configuration mismatch between the chassis and WEM.
> • | The IIOP transport parameter on the chassis is not enabled.The chassis is unmanageable.
> Action(s): |
> • | Ensure ICMP connectivity between the system and the WEM Server using the ping <wem_server_ip_address> command from the chassis’ command prompt. Refer to the Command Line Interface Reference for more information on using this command.
> • | Verify that the ORBEM client identification on the chassis matches that configured on the WEM. The configuration of this parameter on the chassis can be determined by entering the show configuration | grep client CLI command. In WEM, check the ASID (Application Server ID), Port, and SSL-enabled flag (IIOP/SIOP) on the Modify IMG screen. Change these settings as needed.
> • | Check the status of the ORBEM client on the chassis by executing the show orbem client id <client_id> command on the chassis. The “State” should be “Enabled”. If the “State” is “Disabled”, execute the activate client id <client_id> command in the ORBEM Configuration Mode and check the status again-- it should now be “Enabled”.
> • | Verify that the configuration of the IIOP port on the chassis matches that configured for the WEM. The configuration of this parameter on the chassis can be determined by entering the show configuration | grep iiop-port. In WEM, check for the ASID (Application Server ID), Port, and SSL-enabled flag (IIOP/SIOP) on the Modify IMG screen. Change these settings as needed.
> • | Verify that the IIOP transport parameter is enabled on the chassis by entering the show configuration | grep iiop-transport command. If it is not, enable using the instructions found in the System Administration and Configuration Guide.
> • | Check if the SSL is enabled and/or enforced on the WEM. If the SSL is enabled, disable the IIOP transport on the chassis and set the value of IMG Port for the chassis such that it is identical to the SIOP port parameter configured on the chassis.

> ‌

> Problem: | Received “Callbacks between server and client are not working. Screen cannot be invoked.” message.
> Possible Cause(s): |
> • | A firewall is prohibiting communication between the client and the server.
> • | The network connection between the server and client machine might be slow.
> Action(s): |
> • | Edit the img.html file (located in the <ems_dir>/client directory (by default) to use fix ports and open the required ports in the firewall. This requires the configuration of the "FIXED_PORT", "FIXED_PORT_RANGE_START" and "FIXED_PORT_RANGE_END".
> • | Verify that all the ports between FIXED_PORT_RANGE_START and FIXED_PORT_RANGE_END (both inclusive) are open on the firewall. If they are not, they should be opened.
> • | The user can try performing a "ping" or “traceroute” from the server machine for the client's IP address and check for any packet-loss or network delay and contact the network administrator if required.

> ‌
> Issues Related to Bulk Statistics

> Problem: | WEM server not receiving bulkstats files.
> Possible Cause(s): |
> • | No FTP server is running on the server.
> • | User specified in bulkstats configuration screen to FTP files from chassis to WEM does not exist.
> • | Invalid FTP user password is being used to access the chassis.
> • | No “destination” path for bulkstats files is configured.
> • | Inadequate user privileges for bulkstatistics storage directory.
> • | Sun Solaris WEM Servers only: Solaris operating system patches may need to be updated.
> • | Poor quality connection between chassis and WEM.
> Action(s): |
> • | Verify that the FTP server process is running on the server by issuing the ps -ef | grep in.ftpd command. If it is not, start it.
> • | FTP user needs to be created by Administrator.
> • | Check the username and password used to ftp the bulkstats data from the chassis to Web Element Management server. Compare the “FTPUserName” and “FTPPassword” parameters in the nms.cfg file located in the <ems_dir>/server/etc directory by default to the names of administrative users with FTP privileges on the chassis.
> • | Verify that the “destination” directory is configured in the bsparser.cfg file located in the <ems_dir>/server/etc directory by default.
> • | Verify that the FTP user has permissions to write to the configured storage directory.
> • | Sun Solaris WEM Servers only: Verify that the latest Solaris operating system patches are installed. Refer to WEM Port and Hardware Information chapter of this guide for more information.
> • | Ensure that the configuration the bulk statistics receiver on the managed system Executing the show bulkstats command on the chassis displays this information. The “Remote File Format” field should contain a valid directory on the WEM Server. (Also verify that this directory exists on the server.) The “Bulkstats Receivers” field should contain the IP address of the WEM Server.
> • | Slow connections could affect the data transfer between the chassis and the WEM server. In this case, contact your system administrator.

> ‌

> Problem: | XML files are not getting generated.
> Possible Cause(s): |
> • | The Bulkstats Server component is not running.
> • | Invalid “sample-interval” parameter configuration on the system.
> • | Bulkstatistics functionality was configured through the system’s command line interface rather than through the WEM.
> • | XML file generation is disabled.
> Action(s): |
> • | Verify that the Bulkstats Server process is running by entering the ps -ef | grep bulkstatserver command. If it is not, execute the ./serv bulkstatserver start command from within the server directory (<ems_dir>/server by default).
> • | Verify that the “sample-interval” parameter on the system is set to either “1” or “5”. The value can be determined by entering the show bulkstats command on the command line.
> • | Make sure that the bulkstats schema configuration is done through WEM.
> • | Make sure that “XMLDataEnable” parameter in the etc/bsserver.cfg file is set to “1” (enabled). If it is not, change the setting, save the file, and execute the ./serv bulkstatserver start command from within the server directory (<ems_dir>/server by default).

> ‌

> Problem: | Received “No matching data found” error when fetching bulkstatistics reports.
> Possible Cause(s): |
> • | The bulk statistics may not be getting parsed properly.
> • | Invalid filter criteria used for the fetch operation.
> Action(s): |
> • | Verify that the filter criteria entered is valid.
> • | If you are querying server in another time zone, enter the timing filters according to your time zone only.
> • | Check if the corresponding data is present in the bsdb.
> • | Verify that the “sample-interval” parameter on the system is set to either “1” or “5”. The value can be determined by entering the show bulkstats command on the command line.

> ‌

> Problem: | Bulkstats files are not getting parsed.
> Possible Cause(s): |
> • | The Bulkstatistics Parser component is not running.
> • | Bulkstat configuration may have been done through the CLI.
> Action(s): |
> • | Verify that the Bulkstatistic Parser process is running by entering the ps -ef | grep bulkstatparser command. If it is not, execute the ./serv parserserver command from within the server directory (<ems_dir>/server by default).
> • | Verify that the bulkstatistics format is compatible with the WEM. Refer to the bs.cfg file (located in the <ems_dir>/server/etc directory by default) for WEM bulkstatistic formatting.

> ‌

> Problem: | Bulkstatserver process is not started.
> Possible Cause(s): | The function of 'bulkstatserver' is only to generate the XML files. It is possible that the “Generate XML Files” option was not enabled during installation.
> Action(s): |
> • | For an existing installation, edit the “XMLDataEnable” parameter in the etc/bsserver.cfg file to be set to “1” (enabled). Once the setting is changed and the files is saved, execute the ./serv bulkstatserver start command from within the server directory (<ems_dir>/server by default).
> • | For new installations, ensure that “Generate XML Files” option is selected during the installation process.

> ‌

> Problem: | ASCII files are not getting generated.
> Possible Cause(s): | Configuration may not be proper.
> Action(s): | Check for the following combination of configurables in bsserver.cfg: 1) XMLFileType = 0 2) ASCIIFileGeneration = 1 3) Configure proper licenses in emslic.cfg To reflect changes in any of the configurable values, restart the bulkstatserver. Important: If XMLFileType is set to 1, it will generate XML files irrespective of the other two mentioned configurables.

> ‌

> Problem: | File header in bulkstats file is not proper.
> Possible Cause(s): | The header might have been configured through CLI.
> Action(s): | Always configure the header format through WEM only; else it will affect the bulkstatparser functionality.

> ‌

> Problem: | XML files are getting re-generated.
> Possible Cause(s): | OverrideLastAccessFlag may be set to 1.
> Action(s): | Check if OverrideLastAccessFlag in bsserver.cfg is enabled. If it is enabled, disable it and restart the bulkstatserver.

> ‌

> Problem: | XML/ASCII files ftp operation failing frequently.
> Possible Cause(s): |
> • | Network problem
> • | PoolSize in bsserver.cfg is not adequate
> Action(s): |
> • | Check the network health to see if there is too much delay or packets getting dropped. Contact the network administrator in case of issues.
> • | If FTP is used, it is recommended that PoolSize should be 10. If SFTP is being used, Poolsize must be set to 3.

> ‌

> Problem: | Schema counters are not fetched/plotted properly.
> Possible Cause(s): |
> • | Reconfiguration of schema is not done after upgrade. Refer to the Reconfiguration of Bulkstat Schemas section of this guide for more information.
> • | Bulkstat parser is not running.
> • | There is no data matching the filter criteria.
> Action(s): |
> • | After upgrade, reconfigure the bulkstat schema for reflecting the new schema changes, if any.
> • | Start the bulkstatparser.
> • | Check if the filter criteria is correct and ensure that the data is available for that period.

> ‌

> Problem: | Counter names are visible in data files.
> Possible Cause(s): | The counters are not supported on the system. There are two possibilities:
> • | Counters removed from the boxer build. In this case, WEM cannot remove the counters from schemas as WEM maintains backward compatibility. This does not have any impact on the WEM functionality.
> • | System build is older than WEM build (for example, StarOS build 7.0 and WEM build 8.0). This does not have any impact on the WEM functionality. Bulkstat parser will ignore the counter strings while parsing data files.
> Action(s): | No action required. This is a normal behavior.

> ‌

> Problem: | Issues with file 2-4 format.
> Possible Cause(s): | WEM only supports 'file 1' format for configuring schemas - and only if it is configured through WEM. Problems related to other file formats are out of WEM scope.
> Action(s): | No action required.

> ‌
> Issues Pertaining to Configuration Backup

> Problem: | Configuration files are not getting backed up.
> Possible Cause(s): |
> • | No FTP server is running on the server.
> • | Invalid FTP username password being used to transfer files from chassis to WEM server.
> • | Inadequate user privileges for configbackup storage directory.
> • | Solaris WEM Servers only: Solaris operating system patches may need to be updated.
> • | Poor quality connection between chassis and WEM.
> Action(s): |
> • | Verify that the FTP server process is running on the server by issuing the ps -ef | grep in.ftpd command. If it is not, start it.
> • | Use the Configuration Backup screen to change the FTPUsername and FTPPassword.
> • | Verify that the FTP user has permissions to write to the configured storage directory.
> • | Solaris WEM servers only: Verify that the latest Solaris operating system patches are installed. Refer to WEM Port and Hardware Information chapter of this guide for more information.
> • | Slow connections could affect the data transfer between the chassis and the WEM server. In this case, contact your system administrator.

> ‌
> Issues Pertaining to Alarms

> Problem: | The WEM is not receiving alarms.
> Possible Cause(s): |
> • | Invalid configuration of SNMP target parameters on the chassis.
> • | An alternate application is receiving the alarms using the same port.
> Action(s): |
> • | Verify that the SNMP target IP address and port number configured on the chassis match that of the WEM server. The SNMP target configuration on the chassis can be determined by entering the show snmp transports command. Check this information against the WEM server IP address (“ServerIpAddress”, specified in the nms.cfg file) and the SNMP port number (“SnmpTrapPort”, specified in the fm.cfg file) parameters. (Both of these files are located in the <ems_dir>/server/etc directory by default.)
> • | Ensure no other application is running that receives the alarms on the port. Port status on the WEM server can be checked by executing the netstat -a command.

> ‌

> Problem: | Not able to receive Mail Notifications
> Possible Cause(s): |
> • | The E-mail server is not running.
> • | Invalid Mail identification information configured within the WEM for notifications.
> Action(s): |
> • | Verify that the E-mail parameters are properly configured in the fm.cfg file (located in the <ems_dir>/server/etc directory by default).
> • | Verify that the E-mail server is running.
> • | Verify that the E-mail information configured in the Alarm Configuration dialog of the WEM is correct.

> ‌

> Problem: | Script execution on receiving ALARM fails
> Possible Cause(s): |
> • | The WEM Script Server is not running.
> • | The script file is missing.
> • | The script file does not have proper executable permissions.
> Action(s): |
> • | Verify that the Script Server is running by entering the ps -ef | grep scriptsrv command. If it is not, execute the ./serv scriptserver command from within the server directory (<ems_dir>/server by default).
> • | Verify that the script file is located in the <ems_dir>/server/scripts directory (this is the default directory). If it is not, copy the script to that location.
> • | Verify that the script can be executed by entering the ls -al command from within the directory in which the script is located.

> ‌
> Issues Pertaining to the Process Monitor (PSMON)

> Problem: | WEM processes are not restarted after a crash.
> Possible Cause(s): |
> • | PSMON is not running
> • | Invalid PSMON configuration
> • | The PSMON may have given up after performing multiple retries in a specific duration
> Action(s): |
> • | Verify that PSMON is running by entering the ps -ef | grep psmon command. If it is not, start it using the instructions located in WEM Process Monitor chapter of this guide.
> • | Verify that PSMON is configured with the proper entries to start WEM processes. These entries may not be available if they were not selected for monitoring during the installation process. Refer to the instructions located in WEM Process Monitor chapter of this guide for information on PSMON configuration.
> • | The PSMON tries to restart the processes for "numretry" time within a duration of "tmintval" (refer to etc/psmon.cfg) per process. If the process still doesn't start, PSMON no longer monitors this process. Please check the <ems_dir>/log/watchdog.log for details. Try restarting the process using the serv script.

> ‌
> Issues Pertaining to Starting and Stopping EMS Processes

> Problem: | When starting or stopping a WEM process, the user receives the error message ld.so.1: httpd: fatal: libgcc_s.so.1: open failed: No such file or directory.
> Possible Cause(s): | Solaris WEM Servers: The configure runtime linking environment (crle) Default Library Path (ELF) on the Solaris server does not contain the EMS library path. Red Hat Enterprise Linux WEM Servers: The configure dynamic linker run time bindings (ldconfig) Default Library Path on the RHEL server does not contain the EMS library path.
> Action(s): | Solaris WEM Server:
> • | Log into the WEM Server as root and enter the crle command to view the current Default Library Path path. Here is an example where the crle path does not contain the EMS library path:
> # crleConfiguration file [version 4]: /var/ld/ld.config Default Library Path (ELF):/lib:/usr/lib:/opt/gss/lib:/opt/postgres/lib:/users/gss/lib:/users/postgres/lib:/users/usr/lib Trusted Directories (ELF):/lib/secure:/usr/lib/secure(system default) Command line: crle -c /var/ld/ld.config -l /lib:/usr/lib:/opt/gss/lib:/opt/postgres/lib:/users/gss/lib:/users/postgres/lib:/users/usr/lib
> • | If the crle Default Library Path does not contain the EMS library path, use the following crle command to update it:
> # crle –u –l $EMS_INSTALL_PATH/server/lib
> | Red Hat Enterprise Linux WEM Server:
> • | Log into the WEM Server as root and verify that the ems.conf file is present in the /<ems_dir> /etc/ld.so.conf.d/ directory. To view the exsiting ems.conf file, enter the following commands:
> # cd /etc/ld.so.conf.d # cat ems.conf #This file is used to setup the EMS runtime linking environment
> • | If the ems.conf file is not present, enter the following commands to create it:
> # cd /<ems_dir>/ems/server/lib # cd /etc/ld.so.conf.d # echo "$EMS_INSTALL_PATH/server/lib" > ems.conf
> • | Verify that the /etc/ld.so.conf file contains the ld.so.conf.d/*.conf entry. If the entry is not present, add it to the /etc/ld.so.conf file.
> • | Enter the following command to apply any changes made:
> ldconfig

> ‌
> Issues Pertaining to Java

> Problem: | The following message is displayed when attempting to access WEM dialogs containing tables after changing the look and feel option to Windows: “java.lang.NullPointerException”.
> Possible Cause(s): | This may be an issue related to JRE 1.4.x.
> Action(s): | If JRE 1.4.x is currently installed, uninstall it and then install JRE 1.5.

> ‌

> Problem | The WEM client hangs when the user tries to load the configuration from the client file system. This is typical with older WEM builds
> Possible Cause(s) | There is a bug in JRE 1.6.0_24 and above where JFileChooser class checks for the “modifyThreadGroup" permission which may not exist in the current .java.policy file.
> Action(s) | Update the.java.policy file on any client machine that uses JRE 1.6.0_24 and above with the following line: permission java.lang.RuntimePermission “modifyThreadGroup."

> ‌

> Problem | An error message displays to update the.java.policy file when the user invokes the WEM url. This is typical with newer WEM builds.
> Possible Cause(s) | There is a bug in JRE 1.6.0_24 and above, where JFileChooser class checks for the “modifyThreadGroup" permission, which may not exist in the current .java.policy file.
> Action(s) | Download the .java.policy file again from the options located on the WEM splash screen.

> ‌

> Problem: | The WEM Process Monitoring dialog shows “Could not connect to server. Screen will not be invoked”.
> Possible Cause(s): | This may be an issue related to JRE 1.4.x.
> Action(s): | If JRE 1.4.x is currently installed, uninstall it and then install JRE 1.5.

> ‌

> Problem: | After enabling audio support from the Alarm Management menu, the browser window crashes with the following error message: An unexpected exception has been detected in native code outside the VM. Unexpected Signal: EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x7131B60 Function=[Unknown.] Library=C:\Program Files\Java\j2re1.4.2_04\bin\jsound.dll In addition, the stack trace output shows: Current Java thread: at com.sun.media.sound.MixerThread.runNative(Native Method) at com.sun.media.sound.MixerThread.run(Unknown Source)
> Possible Cause(s): | This may be an issue related to 1.4.x.
> Action(s): | If 1.4.x is currently installed, uninstall it and then, install JRE 1.5.

> ‌
> Issues Pertaining to WEM Upgrade

> Problem: | The migrate script is not working if the postgres server is running on a port other than the default port.
> Possible Cause(s): | The postgres communication port parameter is not passed to the postgres application call through the migrate script.
> Action(s): | A script will prompt you to provide inputs for the postgres communication port at the time of data restoration (not at backup time) along with other input parameters (backup dir, WEM application path, postgres admin, password).

> ‌

> Problem: | Map could not be fetched after manual upgrade from version 'A' to version 'B'.
> Possible Cause(s): | While manually upgrading from version 'A' to version 'B', you may have used the original migrate script, i.e., the migrate script from version 'A' (since it is already available on the system) to restore the database.
> Action(s): | While manually upgrading from version 'A' to version 'B', if you use the migrate script from version 'A', the database will be backed up. However, to restore the database, you have to use the migrate script from version 'B', i.e., the script that is packaged with the version that you are upgrading to. You will get the latest migrate scripts for restoring the database after unpacking the lastest WEM install.xxx.tar.gz bundle. The reason for doing this is that the recent scripts are likely to be upgraded from previous versions.

> ‌
> Capturing WEM Client Logs
> In the event that an issue exists that could not be solved using the information provided previously in this chapter, you may need to capture client logs for debugging purposes. This section provides information on how to utilize logging for WEM clients.

> Step 1 | Launch the web browser on the client machine.

> Step 2 | Open the Java Console. Assuming that the client is a Microsoft Windows-based machine, this can be done using the following instructions:

> Step a | Right-mouse click on the Java(TM) 2 Platform icon in the status area (Windows System Tray).

> Step b | Select Open Console from the menu.

> Step 3 | Open the URL of the Web Element Management Server in the web browser, replacing img.html with imgdebug.html.

> Step 4 | Login to the WEM and perform the operations causing the issues.

> The Java Console contains log messages that could be used for debugging the issue.
> Capturing WEM Server Logs using 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 the WEM Server in the <EMS_INSTALL_DIR>/tools/supportdetails/ directory.
> This script refers to an XML file to get the list of logs. This XML 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 (/tmp/log/emssupportDetails.tar.gz), by default it is placed in /tmp/log directory.
> Requirements:
> Perl 5.8.5 and above is required for running the script. This is packaged with the WEM Server.
> 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:

> • | expat version 1.95.8

> • | expat version 1.95.8

> • | XML:Parser version 2.34

> • | XML-Parser-EasyTree

> • | Devel-CoreStack version 1.3

> These modules are installed by default by the WEM application. Please ensure that the above mentioned modules are installed when using a different installation of Perl.
> To run the script, go to the path where the script is present and enter:
> ./getSupportDetails.pl [--level=...] [--xmlfile=...] [--outputDir=] [--help]

> --level | Specifies the level of debug to run. It can have a maximum of 4 levels. The level 4 provides the most detailed information. Refer to README.txt file for more information. Default: 1
> --xmlfile | Specifies the xml file name to be used for collecting the log. Default: getSupportDetails.xml
> --outputDir | Specifies the output directory for the emssupportDetails.tar.gz file if different from the default output directory (/tmp/).
> --help | Display this information.

> ‌
> For example:
> ./getSupportDetails --level=4 --xmlfile=/tmp/something.xml --outputDir=/mywemlogscripts
> WEM IP Address Change Procedure
> In the event the customer’s network evolves, the IP address of the WEM server might be required to change from the existing one. In order to change the WEM server IP address, use the following defined IP planning process:

> Step 1 | Stop the EMS server using the following command:

> ./serv stop

> Step 2 | Change the interface IP address using the ifconfig command. For example:

> ifconfig bge0 192.168.1.1 netmask 255.255.255.0 up

> Step 3 | Change the new IP address in the nms.cfg file of the WEM configuration. For this, use the vi editor as follows:

> vi nms.cfg
> Replace the IP address with the new IP address in the modify serverIpAddress field. For example:
> ServerIpAddress = 192.168.1.1
> Save the file after making the appropriate changes.

> Step 4 | Modify the host file of the WEM server using following commands:

> # cat /etc/hosts
> <IP address> localhost
> <new_IP_address> solaris_hostname
> #

> Step 5 | Start the WEM server after these settings changes using the following command:

> ./serv start
> Important: /etc/netmasks needs to be modified if the user is subnetting existing address and subsequently using a different network mask than the default one. If the netmask being used for a given IP address is a default one, then there is no need to modify this file.
> Appendix B
> WEM High Availability Redundancy with Cluster Application
> Systems that rely on running Web Element Manager on a single server to manage their networks face the possibility of service disruption should the server fail. By using Oracle Solaris Cluster software, it is now possible to create redundant Web Element Manager servers with a primary host server running an active instance of Web Element Manager, and a redundant server in standby mode. This appendix provides information to help you successfully configure redundant instances of Web Element Manager over multiple servers. This appendix works closely with the Installing the WEM Software chapter in this guide.
> Important: Cluster configuration is not supported on Cisco Red Hat Enterprise Linux (RHEL) operating systems for this software release (12.2).
> This appendix addresses the following topics:

> • | System Requirements.

> • | Installing Web Element Manager for Failover Mode.

> • | Creating and Configuring a Cluster Resource Group.

> • | Upgrading Web Element Manager in a Clustered Environment.

> System Requirements
> Requirements for implementing High Availability are as follows:
> Web Element Manager must be installed on a minimum of two Sun Netra™ T5220 servers equipped with the hardware described in the Server Hardware Requirements section of this guide. We recommend a cluster installation restricted to two servers configured similar to that shown in the diagram below. The sample configurations in this appendix assume such an installation.
> Important: Ensure you have installed the latest version of Oracle Solaris software and all appropriate software patches as described in the Operating System Requirements section.
> IPMP is a feature supported on Oracle Solaris. For more complete configuration information, refer to Configuring IPMP for WEM Server and also to the Oracle product documentation.
> Oracle Solaris Cluster is a feature provided and supported by Oracle. For more complete information on configuring Resource Groups, refer to the Oracle Solaris Cluster product documentation.
> Installing Web Element Manager for Failover Mode
> This section specifies the configuration changes required when installing WEM in Failover Mode rather than Standalone Mode when following the installation instructions in the Installing the WEM Software chapter. For this release, please use the GUI to perform the installation rather than the command line.
> Important: Install and configure Web Element Manager in Failover Mode on both servers before configuring a cluster resource group.
> The following items are either different from, or prerequisites for, the installation steps defined in the Installing the WEM Software chapter:

> • | Create a file directory path <ems_dir> or use the default path: /users/ems.

> • | The logical hostname and a floating IP address shared between the two nodes must be configured in /etc/hosts. Ems-Service is used as the logical hostname in the examples in the rest of this appendix.

> • | Create the global disk path for a shared data directory, for example: /shareddir/ems-share.

> Important: The following options are not set when installing in Failover Mode:

> • | WEM Service started by default and monitored by Process Monitor. (See the WEM Process Monitor chapter for more information on processes.)

> • | Start EMS on machine start-up.

> Creating and Configuring a Cluster Resource Group
> This section explains how to create a Resource Group specifically for WEM servers in this cluster and configure it appropriately.
> Important: This process is configured on only one server in the cluster. It is reflected on both.
> Creating a Resource Group
> The following describe how to create a Resource Group.
> We recommend the cluster binary path is set in the shell environment as this means you can execute the cluster commands from any directory path.
> Before clsetup can create a network resource for any logical hostname, that hostname and a common floating IP address associated with it must be specified in the /etc/hosts directory on both servers. This example uses ems-service as the logical hostname.

> Step 1 | Login as root and run clsetup to open the Main Menu.

> Step 2 | From the Main Menu select Option 2: Resource Groups.

> Step 3 | From the Resource Groups Menu, select Option 1: Create a Resource Group.

> A resource group is a container into which you can place resources of various types, such as network and data service resources and then manage them. Only failover resource groups can contain network resources. A network resource would include logical hostname.

> Step 4 | When prompted to create a failover group, enter yes and select Option 1: Create a Failover Group. For this example, call the group ems-rg.

> Step 5 | When you are prompted to select a preferred server enter yes and enter the name of the Preferred server; for this example use Node1. Enter yes to continue the update.

> The screen will display the following message:
> clresourcegroup create -n <Node-1 Node Name> <Node-2 Node Name> ems-rg
> Command completed successfully.
> With the Resource Group created successfully, you can move on to the next step and add the logical hostname.
> Adding a Logical Hostname to a Failover Resource Group
> Follow steps 1 - 5 to add a logical hostname.

> Step 1 | After the confirmation screen from the last task displays, press Enter to continue. Enter yes when prompted to add network resources.

> Step 2 | From the Network Resources Menu, select Option 1: Add a Logical Hostname.

> If a failover resource group contains logical hostname resources, the most common configuration is to have one logical hostname resource for each subnet. Enter 1 to create a single resource.

> Step 3 | When prompted for a logical hostname, enter the logical hostname configured in /etc/hosts for the floating IP address, For this example use ems-service.

> Step 4 | Press Enter to continue. The screen displays:

> clreslogicalhostname create -g ems-rg -p R_description="LogicalHostname resource for ems-service" ems-service

> Step 5 | Enter no when prompted to add any additional network resources.

> Adding a Data Service Resource
> Follow steps 1 - 4 to add a data service.

> Step 1 | After the logical hostname confirmation screen, enter yes when prompted to begin adding data services.

> Step 2 | From the Data Services Menu select Option 1: EMSSCFO Server for Sun Cluster, and use the name ems-dsr for this example.

> The screen displays the following message:
> This data service uses the "Port_list" property. The default "Port_list" for this data service is as follows: <NULL>

> Step 3 | Enter no when prompted to override the default.

> Step 4 | Enter no when prompted to add more properties, then enter yes to continue.

> The screen displays the following message:
> Commands completed successfully
> Bringing the Resource Group Online
> Follow steps 1 - 2 to bring the Resource Group online.

> Step 1 | After the completion confirmation screen, press Enter to continue. Enter no when prompted to add any additional data service resources. Enter yes when prompted to manage and bring this resource group online.

> The screen displays the following message:
> clresourcegroup online -M ems-rg
> Commands completed successfully

> Step 2 | Press Enter to continue, then select Option q to Quit and return to the Main Menu.

> The process is now complete. At this point you can enter the scstat command to display the current online/offline status if required.
> Upgrading Web Element Manager in a Clustered Environment
> This section describes the process for upgrading Web Element Manager in a two-server cluster.
> Important: Network administrators are advised that they should have any connected clients log out at this time. If clients cannot reconnect after the upgrade, please refer to the Troubleshooting appendix for information on any Java-related errors.
> Prerequisite Steps for the Upgrade Process
> For the example configuration that follows you should confirm the following:

> • | The same version of Web Element Manager software (12.0 or newer) has been installed on both servers and configured in Failover Mode.

> • | Config files and scripts are identical.

> • | Devices can be failed over with no loss in connectivity.

> This can be confirmed either by a software switchover, or by running the scstat command to confirm the current node status.

> • | Resources have been configured in the Oracle Solaris Cluster software using the following example names:

> • | Two Cluster Nodes: N-1 (initially this is the active node) and N-2 (initially this is the redundant node).

> • | A Resource Group managed by Web Element Manager exists. ems-rg is used for this example.

> • | A logical hostname and floating (shared) IP address has been configured on both servers. This example uses the default /etc/hosts folder. Use ems-service as the hostname for this example.

> Upgrade Process Overview
> This section provides a broad overview of the procedures to follow.

> Step 1 | Start with two server nodes: N-1 and N-2. They share both data files and database information. N-1 is currently active and N-2 is currently in standby mode, as shown below:

> Step 2 | With Web Element Manager running on N-1, put N-2 into maintenance mode (this is described in Removing an Inactive Node from the Resource Group below). Then upgrade WEM to version 12.0 or later.

> At this point, the database is not yet updated. In cluster mode, when WEM is upgraded on N-2 the postgres database is not started. so a new DB schema is not created. This is because the schema will be updated through the currently active server N-1 with SQL scripts that are provided as part of the installation package; this is explained in the section Updating the Databases. At this point N-2 is still in maintenance mode but now with updated WEM software, and the database schema has now been updated as shown below:

> Step 3 | To prepare for the switchover, take N-2 out of maintenance mode.

> Step 4 | To upgrade WEM on N-1, bring N-2 back into the cluster and do a switchover from N-1 to N-2 so now N-2 is the active host and WEM starts running processes.

> Step 5 | Now place the formerly active node N-1 into maintenance mode and upgrade WEM software while N-2 is the active node as shown below:

> Step 6 | Once the upgrade is complete, N-1 can be switched back to its role of active node if necessary by using the Cluster commands, or N-2 can continue as the active node.

> Important: Refer to the Installing the WEM Software chapter for more complete information about scripts and files. All configuration files placed in the <EMS_HOME>/server/etc folder and the script files in the <EMS_HOME>/server/scripts folder must be identical. This ensures that after the switch between servers, the behavior of EMS does not change in any way.
> Removing an Inactive Node from the Resource Group
> Complete the following steps to remove N-2 from the Resource Group. Since the cluster resource group configuration will be same for both nodes, the cluster-related commands can be run on either node.

> Step 1 | Run the scstat command. scstat is used to verify the current status of the cluster resource group and ensures that on switchover/failover the servers will switch correctly. The following screen display reflects a properly configured cluster:

> Two cluster nodes: Online
> Two cluster transport paths: Online
> Quorum votes by node: Online
> Quorum votes by device: Online
> Resource Groups and Resources: ems-rg, ems-service, ems-dsr
> Ems-rg group N-1: Online N-2: Offline
> IPMP groups: Online
> Important: N-2 must not be allowed to run any WEM processes. This prevents the secondary node from taking ownership of resources. Removing it from the Resource Group prevents a failover from happening and N-1 continues to behave like a standalone WEM thus ensuring a successful upgrade. To do this:

> Step 2 | Enter clsetup to open the Main Menu and select Option 2: Resource Groups Menu.

> Step 3 | From the Resource Groups menu, select Option 8: Change the Properties of a Resource Group.

> Step 4 | Enter yes when prompted to continue.

> Step 5 | Select the group to be changed by selecting Option 1: ems-rg.

> Step 6 | Select Option 1: Change the Nodelist Resource Group Properties

> Step 7 | Enter yes when prompted to continue. Both N-1 and N-2 should now appear in the nodelist.

> Step 8 | Select Option 2: Remove a Node from the Nodelist, then select Option 1 to remove N-2.

> The nodelist now contains only N-1. When prompted to update the nodelist property, enter yes. If your update was successful you will see the following screen confirmation:
> command completed successfully
> Press Enter to continue. You will receive confirmation that only N-1 remains in the nodelist. Select Option q to Quit and exit back to the Resource Group Menu.

> Step 9 | From the Resource Group Menu select Option s: Show Current Status to confirm the current network resources if required.

> Upgrading WEM on the Inactive Server
> Complete the following steps to upgrade WEM on the inactive server, N-2.

> Step 1 | Web Element Manager begins installing along with Apache Server, PostgreSQL Server, and EMS Server. Installation continues until the following warning message appears:

> Updating PostgreSQL config file...This is an upgrade in Cluster mode; not updating postgres config.
> This message is normal because the database is to be updated from the active server, N-1.

> Step 2 | With the installation complete, select Option 3 to finish.

> Updating the Databases
> Complete the following steps to update the databases from node N-1.

> Step 1 | Copy the sqlfiles.tar file from the N-2 installation to a folder on N-1 and untar the file. This process is described fully in the Installing the WEM Software chapter.

> This will create a folder called sqlfiles.

> Step 2 | Go to the sqlfiles folder and run dbClusterUpgrade.sh.

> Step 3 | At the prompt, enter the EMS directory name and press Enter.

> Step 4 | Enter a complete directory path for saving the new SQL files and press Enter.

> Step 5 | Enter the postgres administrator name assigned during the installation process. This is postgres by default.

> Step 6 | Press Enter.

> Step 7 | Enter the database port number and press Enter.

> Important: Currently, this is port 5432, but this may change in a later release.

> Step 8 | The databases update and the screen displays the following message:

> Database schema upgraded successfully...
> Returning the Inactive Node to the Resource Group
> Complete the following steps to return N-2 to the Resource Group and take over resource ownership in order to upgrade the software on N-1.

> Step 1 | Run clsetup and then log in to access the Main Menu and select Option 2: Resource Groups.

> Step 2 | From the Resource Groups Menu select Option 8: Change the Properties of a Resource Group.

> Step 3 | Enter yes when prompted to continue.

> Step 4 | From the next screen select the Resource Group name.

> Step 5 | When prompted for the property to change, select Option 1: Nodelist.

> Step 6 | Enter yes to continue and open the next screen.

> Step 7 | Select Option 1: Add a Node/Zone to the Top of the Nodelist.

> Step 8 | Select Option 1: N-2.

> Step 9 | Enter yes when prompted to update the nodelist property.

> The screen will display the following message:
> Command completed successfully.

> Step 10 | Press Enter to continue and select Option q to Quit and return to the Resource Groups Menu.

> Switching Active Servers
> Complete the following steps to make N-2 the active node so N-1 can be updated.

> Step 1 | From the Resource Group Menu Select Option 5: Switch over a Resource.

> Step 2 | Scroll through the on-screen description and enter yes to continue.

> Step 3 | Select the name of the resource group. In this example it would be ems-rg.

> Step 4 | Select Option 1: Switch Group Ownership.

> Step 5 | Select the node to take ownership of ems-rg, which would be N-2. Enter yes to confirm. The screen will display the following message:

> Command completed successfully.

> Step 6 | Press Enter to continue and select Option q to Quit and return to the Resource Group Menu.

> Step 7 | From the Resource Group Menu select Option s Show Current Status. This shows that N-2 is now online and N-1 is offline.

> At this point return to Removing an Inactive Node from the Resource Group and begin the update process for N-1.
> Important: Since the database schema were previously updated and both N-1 and N-2 share the same database, it is not necessary to run the SQL scripts again for N-1.
> Appendix C
> WEM Configuration File Parameters
> This appendix provides information about the configuration file parameters pertaining to the Web Element Manager. WEM provides a number of configuration files which can be modified to fine-tune the operation of the application. These files are located in the /<ems_dir>/server/etc directory by default.
> The following configuration files have been deprecated from WEM:

> • | fmcorelation.cfg

> • | description.cfg

> • | dbphy.cfg

> • | dblog.cfg

> This chapter provides information on the following configuration files:

> • | The alarmid.cfg File

> • | The audio.cfg File

> • | The blacklist.cfg File

> • | The bs.cfg File

> • | The bsparser.cfg File

> • | The bsserver.cfg File

> • | The bstca.cfg File

> • | The cf.cfg File

> • | The configupdate.cfg File

> • | The db.cfg File

> • | The emslic.cfg File

> • | The fm.cfg File

> • | The hwinv.cfg File

> • | The ism.cfg File

> • | The mcrdbs.cfg File

> • | The mdproxy.cfg File

> • | The nb.cfg File

> • | The nbserver.cfg File

> • | The nms.cfg File

> • | The pcrefgen.cfg File

> • | The processmonitor.cfg File

> • | The ps.cfg File

> • | The psmon.cfg File

> • | The res.cfg File

> • | The temip.cfg File

> • | The thr.cfg File

> • | The ua.cfg File

> • | The vacuum.cfg File

> • | The wblist.cfg File

> Important: Unless otherwise specified, all information in this chpater applies to both Sun Solaris- and RHEL-based WEM systems.
> The alarmid.cfg File
> This file provides parameters pertaining to the configuration of SNMP alarms received from managed devices.
> Important: This configuration file is customer-specific and is not operational without the appropriate license. Please contact your local sales representative for additional information.
> The audio.cfg File
> This file provides alarm severity associations to specific audio files. The audio files are in .WAV format and are played by the Web Element Manager when an alarm/trap of that severity is received. Additionally, this file can be used to associate an audio file to a specific alarm for further customizing.
> The following table describes the AUDIO file parameters.
> audio.cfg File Parameters

> Parameters
> AUDIO: This file contains the mapping of the alarm severity level and the corresponding audio file to be played when an alarm is received. The first field contains the severity level (number): The nth row in the SEVERITY section is n-1 in the fm.cfg file. Please use the fm.cfg file for the severity configuration information in detail. The second field contains the audio file name. The audio files are present in the audio sub-directory in the client installation directory. The format is as follows: Severity Number = WAV File Path For example: 1 = Blank Line - This means that no audio file is to be played when a first level (Indeterminate) severity alarm is received. 3 = audio/chord.wav - This means that the audio/chord.wav file is to be played when a third level (Major) severity alarm is received.
> audioPlayedFor: This option will decide the priority of alarm to play an audio. The default value is 0. Valid configurables are: 0 - Only STxx audio will be played as per severity and no audio will be played for WEM alarm. 1 - Audio for STxx and WEM will be played but severity will be given to STxx alarms. 2 - Audio for STxx and WEM will be played but first priority will be based on device and severity. 3 - Audio will be played strictly based on the severity irrespective of STxx/WEM.
> Severity No. | Severity Name | Audio Filename
> 1 | Critical | 1 = audio/notify.wav
> 2 | Major | 2 = audio/ding.wav
> 3 | Minor | 3 = audio/chord.wav
> 4 | Warning | 4 = audio/Alarmrng.wav

> ‌
> The following table describes the TRAPAUDIO file parameters.
> TRAPAUDIO File Parameters

> Parameters
> TRAPAUDIO: This section defines the mapping for Trap Number and the corresponding AUDIO file. This file is the default file to be played when the trap is received. If the filename field is kept empty then, the file associated with the severity of the trap will be played. Severity-AudioFilename relationship is defined in the AUDIO section. The format is as follows: Trap Number = File Path For example: 1 = This suggests that no audio file is associated with trap #1. So, the file associated with its severity will be played. 3 = audio/test01.wav - This file will be played whenever trap #3 comes.
> Trap Number | Trap Name
> Generic Alarms
> 1-1 | coldStart
> 1-2 | warmStart
> 1-3 | linkDown
> 1-4 | linkUp
> 1-5 | authenticationFailure
> 1-6 | egpNeighborLoss
> ST 16 Enterprise Alarms
> 2-1 | starCardTempOverheat
> 2-2 | starCardTempOK
> 2-3 | starCardReset
> 2-4 | starCardRebootRequest
> 2-5 | starCardUp
> 2-6 | starCardVoltageFailure
> 2-7 | starCardRemoved
> 2-8 | starCardInserted
> 2-9 | starCardBootFailed
> 2-12 | starCardRCCFailed
> 2-13 | starCardMismatch
> 2-14 | starCardFailureLEDOn
> 2-15 | starCardFailureLEDOff
> 2-16 | starCardPACMigrateStart
> 2-17 | starCardPACMigrateComplete
> 2-18 | starCardPACMigrateFailed
> 2-19 | starCardSPCSwitchoverStart
> 2-20 | starCardSPCSwitchoverComplete
> 2-21 | starCardSPCSwitchoverFailed
> 2-22 | starFanFailed
> 2-23 | starFanRemoved
> 2-24 | starFanInserted
> 2-25 | starLogThreshold
> 2-26 | starCPUBusy
> 2-27 | starCPUMemoryLow
> 2-28 | starCPUMemoryFailed
> 2-29 | starCPUFailed
> 2-30 | starCPUWatchDogExpired
> 2-31 | starNPUARPPoolExhausted
> 2-32 | starPowerFilterUnitUnavail
> 2-33 | starPowerFilterRemoved
> 2-34 | starPowerFilterAvail
> 2-37 | starAlertsDisabled
> 2-38 | starAlertsEnabled
> 2-39 | starAAAAuthServerUnreachable
> 2-40 | starAAAAuthServerReachable
> 2-41 | starAAAAuthServerMisconfigured
> 2-42 | starAAAAccServerUnreachable
> 2-43 | starAAAAccServerReachable
> 2-44 | starAAAAccServerMisconfigured
> 2-45 | starLogMsg
> 2-46 | starPDSNServiceStart
> 2-47 | starPDSNServiceStop
> 2-48 | starHAServiceStart
> 2-49 | starHAServiceStop
> 2-50 | starFAServiceStart
> 2-51 | starFAServiceStop
> 2-52 | starCLISessionStart
> 2-53 | starCLISessionEnd
> 2-54 | starCritTaskFailed
> 2-55 | starCardActive
> 2-56 | starLACServiceStart
> 2-57 | starLACServiceStop
> 2-58 | starLNSServiceStart
> 2-59 | starLNSServiceStop
> 2-60 | starCardDown
> 2-63 | starGGSNServiceStart
> 2-64 | starGGSNServiceStop
> 2-65 | starLicenseExceeded
> 2-66 | starSubscriberLimit
> 2-67 | starSessionRejectNoResource
> 2-68 | starLongDurTimerExpiry
> 2-69 | starClosedRPServiceStart
> 2-70 | starClosedRPServiceStop
> 2-71 | starGtpcPathFailure
> 2-72 | starGtpuPathFailure
> 2-73 | starManagerFailure
> 2-74 | starEISServerAlive
> 2-75 | starEISServerDead
> 2-76 | starCgfAlive
> 2-77 | starCgfDead
> 2-78 | starStorageServerAlive
> 2-79 | starStorageServerDead
> 2-80 | starGgsnInitiatedUpdtFailed
> 2-81 | starCongestion
> 2-82 | starCongestionClear
> 2-83 | starServiceLossPTACs
> 2-84 | starServiceLossLC
> 2-85 | starServiceLossSPIO
> 2-86 | starIPSPAllAddrsFree
> 2-87 | starPCFUnreachable
> 2-88 | starDhcpAlive
> 2-89 | starDhcpDead
> 2-90 | starNTPPeerUnreachable
> 2-91 | starNTPSyncLost
> 2-92 | starL2TPTunnelDownPeerUnreachable
> 2-93 | starCardStandby
> 2-94 | starLicenseUnderLimit
> 2-95 | starIPSECPriTunDown
> 2-96 | starIPSECPriTunUp
> 2-97 | starIPSECSecTunDown
> 2-98 | starIPSECSecTunUp
> 2-99 | starIPSECTunSwitchFail
> 2-100 | starIPSECTunSwitchComplete
> 2-101 | starNwReachServerAlive
> 2-102 | starNwReachServerDead
> 2-103 | starStorageServerUnackedGcdrVolPurge
> 2-104 | starStorageServerUnackedGcdrFileGen
> 2-200 | starThreshCPUUtilitization
> 2-201 | starThreshClearCPUUtilitization
> 2-202 | starThreshCPUMemory
> 2-203 | starThreshClearCPUMemory
> 2-204 | starThreshLicence
> 2-205 | starThreshClearLicence
> 2-206 | starThreshSubscriberTotal
> 2-207 | starThreshClearSubscriberTotal
> 2-208 | starThreshSubscriberActive
> 2-209 | starThreshClearSubscriberActive
> 2-210 | starThreshPortRxUtil
> 2-211 | starThreshClearPortRxUtil
> 2-212 | starThreshPortTxUtil
> 2-213 | starThreshClearPortTxUtil
> 2-214 | starThreshPortHighActivity
> 2-215 | starThreshClearPortHighActivity
> 2-216 | starThreshAAAAuthFail
> 2-217 | starThreshClearAAAAuthFail
> 2-218 | starThreshAAAAuthFailRate
> 2-219 | starThreshClearAAAAuthFailRate
> 2-220 | starThreshAAAAcctFail
> 2-221 | starThreshClearAAAAcctFail
> 2-222 | starThreshAAAAcctFailRate
> 2-223 | starThreshClearAAAAcctFailRate
> 2-224 | starThreshAAARetryRate
> 2-225 | starThreshClearAAARetryRate
> 2-226 | starThreshCallSetup
> 2-227 | starThreshClearCallSetup
> 2-228 | starThreshCallSetupFailure
> 2-229 | starThreshClearCallSetupFailure
> 2-230 | starThreshCallRejectNoResource
> 2-231 | starThreshClearCallRejectNoResource
> 2-232 | starThreshPacketsFilteredDropped
> 2-233 | starThreshClearPacketsFilteredDropped
> 2-234 | starThreshPacketsForwarded
> 2-235 | starThreshClearPacketsForwarded
> 2-236 | starThreshSessCPUThroughput
> 2-237 | starThreshClearSessCPUThroughput
> 2-238 | starThreshIPPoolAvail
> 2-239 | starThreshClearIPPoolAvail
> 2-240 | starThreshCPUUtilitization10Sec
> 2-241 | starThreshClearCPUUtilitization10Sec
> 2-242 | starThreshCPULoad
> 2-243 | starThreshClearCPULoad
> 2-244 | starThreshCPUMemUsage
> 2-245 | starThreshClearCPUMemUsage
> 2-246 | starThreshPDSNSessions
> 2-247 | starThreshClearPDSNSessions
> 2-248 | starThreshGGSNSessions
> 2-249 | starThreshClearGGSNSessions
> 2-250 | starThreshHASessions
> 2-251 | starThreshClearHASessions
> 2-252 | starThreshLNSSessions
> 2-253 | starThreshClearLNSSessions
> 2-254 | starThreshPerServicePDSNSessions
> 2-255 | starThreshClearPerServicePDSNSessions
> 2-256 | starThreshPerServiceGGSNSessions
> 2-257 | starThreshClearPerServiceGGSNSessions
> 2-258 | starThreshPerServiceHASessions
> 2-259 | starThreshClearPerServiceHASessions
> 2-260 | starThreshPerServiceLNSSessions
> 2-261 | starThreshClearPerServiceLNSSessions
> 2-262 | starThreshIPPoolHold
> 2-263 | starThreshClearIPPoolHold
> 2-264 | starThreshIPPoolUsed
> 2-265 | starThreshClearIPPoolUsed
> 2-266 | starThreshIPPoolRelease
> 2-267 | starThreshClearIPPoolRelease
> 2-268 | starThreshIPPoolFree
> 2-269 | starThreshClearIPPoolFree
> 2-270 | starThreshAAAAcctArchive
> 2-271 | starThreshClearAAAAcctArchive

> ‌
> The blacklist.cfg File
> This file contains the flag that is set to enable or disable the blacklisting feature in WEM. The file provides parameters for specifying information such as blacklist backup limit, time interval to poll the blacklist directory, and so on.
> blacklist.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> BLACKLIST: This section describes parameters that store information related to blacklisting.
> EnableBlackListFeature | Flag to enable/disable the blacklisting feature in WEM. Setting this flag to 1 will enable the blacklisting feature in WEM. Needs a WEM Server restart. Values: 1: Enable 0: Disable | -- | -- | 0
> BlacklistBackupLimit | Number of Blacklist backups to be maintained. | 5 | 15 | 10
> ExportBLtoCDPInterval | BlackList files Export interval. This specifies the time interval in hours for Content Filtering Server to export OPTCMDB-BL to CDP. | 1 hr | 5 hrs | 2 hrs
> BlPollInterval | BlackList directory poll interval. This specifies the time interval in minutes to poll the Blacklist directory. | 5 | 60 | 15
> EnableDNSLookup | Flag to enable/disable the DNS lookup functionality. Setting this flag to 1 will enable the DNS lookup functionality. Values: 1: Enable 0: Disable | -- | -- | 0
> ThreadPoolSize | Thread pool size. | 1 | 10 | 5
> NCMEC:
> EnableNCMEC | Flag to enable/disable the import of cumulative.csv from NCMEC. Setting this flag to 1 will enable the import of cumulative.csv from NCMEC. Values: 1: Enable - import cumulative.csv from NCMEC 0: Disable - assume cumulative.csv will be available in <EMS ServerPath>/flash/blacklist/blacklist/ Important: Do not change the value of configurable as functionality when this flag 0 is disabled | -- | -- | 1
> NCMECUrl | This specifies the cumulative.csv file path at NCMEC. | -- | -- | --
> NCMECAuthUserName | This specifies the username required for authentication at NCMEC site. | -- | -- | --
> NCMECAuthPassword | This specifies the password required for authentication at NCMEC site. | -- | -- | --
> BlacklistImportInterval | This specifies the cumulative.csv file import interval (in hours). | 1 | 168 (one week) | 24 (one day)
> BlacklistReImportInterval | This specifies the cumulative.csv file re-import interval (in minutes). | 1 | 30 | 5
> BLThreadPoolSize | Specifies the blacklist thread pool size. | 5 | 20 | 10

> ‌
> The bs.cfg File
> This file provides bulk statistic configuration information pertaining to schemas, formatting, and parameters for specifying time tolerances for searching bulk statistic records. This is a multi-section server configuration file for bulkstat module.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> Caution: To ensure proper operation of the Web Element Manager, bulk statistic schema and formatting configuration in this file should not be altered.
> bs.cfg File Parameters (Schemas)

> Key | Description | Default Value in Config File
> Schema: This section provides the schema format string for each subsystem. The parameter values in this section are internally used by the bulkstat server module and should not be changed.
> CardSch | Card Schema | EMS,Card,%date%,%time%,%card%,%cpubusy%,%cpuidle%,%numproc%,%memused%,%memtotal%,%numcpu%,%cpu0-cpubusy%,%cpu0-cpuidle%,%cpu0-numproc%,%cpu0-memused%,%cpu0-memtotal%,%cpu0-cpuused-user%,%cpu0-cpuused-sys%,%cpu0-cpuused-io%,%cpu0-cpuused-irq%,%cpu0-cpuused-idle%,%cpu1-cpubusy%,%cpu1-cpuidle%,%cpu1-numproc%,%cpu1-memused%,%cpu1-memtotal%,%cpu1-cpuused-user%,%cpu1-cpuused-sys%,%cpu1-cpuused-io%,%cpu1-cpuused-irq%,%cpu1-cpuused-idle%,%cpu2-cpubusy%,%cpu2-cpuidle%,%cpu2-numproc%,%cpu2-memused%,%cpu2-memtotal%,%cpu2-cpuused-user%,%cpu2-cpuused-sys%,%cpu2-cpuused-io%,%cpu2-cpuused-irq%,%cpu2-cpuused-idle%,%cpu3-cpubusy%,%cpu3-cpuidle%,%cpu3-numproc%,%cpu3-memused%,%cpu3-memtotal%,%cpu3-cpuused-user%,%cpu3-cpuused-sys%,%cpu3-cpuused-io%,%cpu3-cpuused-irq%,%cpu3-cpuused-idle%,%15avg-cpubusy%,%15peak-cpubusy%,%5avg-cpubusy%,%5peak-cpubusy%,%1avg-cpubusy%,%15avg-memused%,%15peak-memused%,%5avg-memused%,%5peak-memused%,%1avg-memused%,%cpu0-15avg-cpubusy%,%cpu0-15peak-cpubusy%,%cpu0-5avg-cpubusy%,%cpu0-5peak-cpubusy%,%cpu0-1avg-cpubusy%,%cpu0-15avg-memused%,%cpu0-15peak-memused%,%cpu0-5avg-memused%,%cpu0-5peak-memused%,%cpu0-1avg-memused%,%cpu1-15avg-cpubusy%,%cpu1-15peak-cpubusy%,%cpu1-5avg-cpubusy%,%cpu1-5peak-cpubusy%,%cpu1-1avg-cpubusy%,%cpu1-15avg-memused%,%cpu1-15peak-memused%,%cpu1-5avg-memused%,%cpu1-5peak-memused%,%cpu1-1avg-memused%,%cpu2-15avg-cpubusy%,%cpu2-15peak-cpubusy%,%cpu2-5avg-cpubusy%,%cpu2-5peak-cpubusy%,%cpu2-1avg-cpubusy%,%cpu2-15avg-memused%,%cpu2-15peak-memused%,%cpu2-5avg-memused%,%cpu2-5peak-memused%,%cpu2-1avg-memused%,%cpu3-15avg-cpubusy%,%cpu3-15peak-cpubusy%,%cpu3-5avg-cpubusy%,%cpu3-5peak-cpubusy%,%cpu3-1avg-cpubusy%,%cpu3-15avg-memused%,%cpu3-15peak-memused%,%cpu3-5avg-memused%,%cpu3-5peak-memused%,%cpu3-1avg-memused%,%task-sessmgr-num%
> CardSch2 | Card 2 Schema | EMS,Card2,%date%,%time%,%card%,%task-sessmgr-avgcpu%,%task-sessmgr-avgmem%,%task-sessmgr-maxcpu%,%task-sessmgr-maxmem%,%task-a11mgr-num%,%task-a11mgr-maxcpu%,%task-a11mgr-maxmem%,%task-l2tpmgr-num%,%task-l2tpmgr-maxcpu%,%task-l2tpmgr-maxmem%,%task-famgr-num%,%task-famgr-maxcpu%,%task-famgr-maxmem%,%task-hamgr-num%,%task-hamgr-maxcpu%,%task-hamgr-maxmem%,%task-acsmgr-num%,%task-acsmgr-avgcpu%,%task-acsmgr-avgmem%,%task-acsmgr-maxcpu%,%task-acsmgr-maxmem%,%task-vpnmgr-num%,%task-vpnmgr-maxcpu%,%task-vpnmgr-maxmem%
> PortSch | Port Schema | EMS,Port,%date%,%time%,%card%,%port%,%rxbytes%,%txbytes%,%ucast_inpackets%,%ucast_outpackets%,%mcast_inpackets%,%mcast_outpackets%,%bcast_inpackets%,%bcast_outpackets%,%rxpackets%,%txpackets%,%rxdiscbytes%,%rxdiscpackets%,%txdiscbytes%,%txdiscpackets%,%maxrate%,%frag-rcvd%,%pkt-reassembled%,%frag-tokernel%,%util-rx-curr%,%util-tx-curr%,%util-rx-5min%,%util-tx-5min%,%util-rx-15min%,%util-tx-15min%
> PDSNSystemSch | PDSN System Schema | EMS,PDSNSystem,%date%,%time%,%sess-ttlarrived%,%sess-ttlrejected%,%sess-ttlconnected%,%sess-ttlauthsucc%,%sess-ttlauthfail%,%sess-ttllcpup%,%sess-ttlipcpup%,%sess-ttlsrcviol%,%sess-ttlkeepfail%,%sess-curttlcalls%,%sess-cursipconn%,%sess-curmipconn%,%sess-curactcall%,%sess-curdormcall%,%sess-curarrived%,%sess-curlcpnegot%,%sess-curlcpup%,%sess-curauth%,%sess-curauthed%,%sess-curipcpup%,%sess-curdisc%,%a11-ttlarrived%,%a11-ttlrejected%,%a11-ttldemult%,%a11-ttldereg%,%a11-curactive%,%fa-ttlarrived%,%fa-ttlrejected%,%fa-ttldemult%,%fa-ttldereg%,%fa-curactive%,%ha-ttlarrived%,%ha-ttlrejected%,%ha-ttldemult%,%ha-ttldereg%,%ha-curactive%,%sess-calldur-1min%,%sess-calldur-2min%,%sess-calldur-5min%,%sess-calldur-15min%,%sess-calldur-1hour%,%sess-calldur-4hour%,%sess-calldur-12hour%,%sess-calldur-24hour%,%sess-calldur-over24hour%,%sess-setuptime-100ms%,%sess-setuptime-200ms%,%sess-setuptime-300ms%,%sess-setuptime-400ms%,%sess-setuptime-500ms%,%sess-setuptime-600ms%,%sess-setuptime-700ms%,%sess-setuptime-800ms%,%sess-setuptime-900ms%,%sess-setuptime-1sec%,%sess-setuptime-2sec%,%sess-setuptime-3sec%,%sess-setuptime-4sec%,%sess-setuptime-6sec%,%sess-setuptime-8sec%,%sess-setuptime-10sec%,%sess-setuptime-12sec%,%sess-setuptime-14sec%,%sess-setuptime-16sec%,%sess-setuptime-over16sec%,%incremental%,%enddate%,%endtime%,%localenddate%,%localendtime%,%sess-ttlfailed%,%uptime%,%uptimestr%,%lic-pdsn%,%lic-ha%,%lic-ggsn%,%lic-l2tplns%,%sess-txbytes%,%sess-rxbytes%,%sess-txpackets%,%sess-rxpackets%,%sess-siptxbytes%,%sess-siprxbytes%,%sess-miptxbytes%,%sess-miprxbytes%,%aaa-ttlreq%,%aaa-curreq%,%aaa-ttlauthreq%,%aaa-curauthreq%,%aaa-ttlauthprobe%,%aaa-curauthprobe%,%aaa-ttlacctreq%,%aaa-curacctreq%,%aaa-ttlauthsucc%,%aaa-ttlauthfail%,%aaa-ttlauthpurged%,%aaa-ttlauthcancelled%,%aaa-ttlauthdmuchal%,%aaa-ttlradauthreq%,%aaa-curradauthreq%,%aaa-ttlradauthreqretried%,%aaa-ttllclauthreq%,%aaa-curlclauthreq%,%aaa-ttlpseudoauthreq%,%aaa-curpseudoauthreq%,%aaa-ttlauthnulluser%,%aaa-ttlacctsucc%,%aaa-ttlacctpurged%,%aaa-ttlacctcancelled%,%aaa-ttlradacctreq%,%aaa-ttlradacctreqretried%,%disc-reason-summary%,%sess-curaaaactive%,%sess-curaaadeleting%,%sess-curaaaacctpending%,%sess-ttlemptyfwd%,%sess-ttlemptyrev%,%sess-ttlonlineprepaiderr%,%sess-ttlprepaidinitautherr%,%sess-ttlcrprpattempt%,%sess-ttlcrprpsuccess%,%sess-ttlrpcrpattempt%,%sess-ttlrpcrpsuccess%,%sess-curpmipconn%,%sess-curl2tplacconn%,%sess-curalwayson%,%sess-curbcmcsauth%,%sess-curbcmcsconn%,%sess-curhaipsecconn%,%sess-curl2tplacconnecting%,%sess-curpdptypeipconn%,%sess-curpdptypepppconn%,%sess-curprepaid%,%sess-rxpkt-1023%,%sess-rxpkt-127%,%sess-rxpkt-16%,%sess-rxpkt-2047%,%sess-rxpkt-255%,%sess-rxpkt-4095%,%sess-rxpkt-4500%,%sess-rxpkt-511%,%sess-rxpkt-64%,%sess-rxpkt-over4500%,%sess-ttldisconn%,%sess-ttlhandoff%,%sess-ttlonlineauthfail%,%sess-ttlonlineauthreq%,%sess-ttlonlineauthsucc%,%sess-ttlprepaid%,%sess-ttlproxydns-drop%,%sess-ttlproxydns-passthru%,%sess-ttlproxydns-redirect%,%sess-ttlrenewal%,%sess-txpkt-1023%,%sess-txpkt-127%,%sess-txpkt-16%,%sess-txpkt-2047%,%sess-txpkt-255%,%sess-txpkt-4095%,%sess-txpkt-4500%,%sess-txpkt-511%,%sess-txpkt-64%,%sess-txpkt-over4500%,%aaa-ttlauthkeepalive%,%aaa-curauthkeepalive%,%aaa-ttlacctkeepalive%,%aaa-curacctkeepalive%,%aaa-ttlauthkeepalivesuccess%,%aaa-ttlauthkeepalivefailure%,%aaa-ttlauthkeepalivepurged%,%aaa-ttlacctkeepalivesuccess%,%aaa-ttlacctkeepalivetimeout%,%aaa-ttlacctkeepalivepurged%,%ipsg-total-call-arrived%,%ipsg-total-call-rejected%,%ipsg-total-call-demult%,%ipsg-total-dereg-rep-sent%,%ipsg-cur-active-call%,%ipsg-total-active-serv%
> PDSNSystemSch2 | PDSN2 System Schema | EMS,PDSNSystem2,%date%,%time%,%asngw-cur-active-call%,%asngw-total-sess-setup%,%asngw-retriesexhaust%,%asngw.sfs%,%asngw.tidfail%,%asngw-handoffattempt%,%asngw-handoffdenied%,%asngw-handoffcomp%,%asngw.authsucc%,%asngw-authfailures%,%sess-ttlcallop%,%sess-curnonanchorconn%,%sess-curdhcppending%,%sess-ttlinterasngwattempt%,%sess-ttlinterasngwsuccess%,%sess-ttlintraasngwattempt%,%sess-ttlintraasngwsuccess%,%sess-ttlconnected-1xrtt%,%sess-txbytes-1xrtt%,%sess-rxbytes-1xrtt%,%sess-txpackets-1xrtt%,%sess-rxpackets-1xrtt%,%sess-ttlconnected-evdorev0%,%sess-txbytes-evdorev0%,%sess-rxbytes-evdorev0%,%sess-txpackets-evdorev0%,%sess-rxpackets-evdorev0%,%sess-ttlconnected-evdoreva%,%sess-txbytes-evdoreva%,%sess-rxbytes-evdoreva%,%sess-txpackets-evdoreva%,%sess-rxpackets-evdoreva%,%flow-ttlestab%,%flow-ttldisconn%,%flow-curdynamic%,%pdif-cursess%,%pdif-curactive%,%pdif-curdormant%,%pdif-ttlsetup%,%sess-15peak-curactcall%,%sess-15peak-curttlcall%,%sess-cursipactive%,%sess-15peak-cursipactive%,%sess-curmipactive%,%sess-15peak-curmipactive%,%a11-15peak-curactive%,%crp-curactive%,%crp-15peak-curactive%,%fa-15peak-curactive%,%ha-15peak-curactive%,%flow-15peak-curdynamic%,%sess-15min-usageactive%,%sess-15min-usageall%,%cc-cursess%,%cc-ttlecsadd%,%cc-ttlstart%,%cc-ttlsessupd%,%cc-ttlterm%,%cc-sessfailover%,%cc-msg-recv%,%cc-msg-sent%,%cc-msg-request%,%cc-msg-answer%,%cc-msg-ccrinit%,%cc-msg-ccainit%,%cc-msg-ccainitaccept%,%cc-msg-ccainitreject%,%cc-msg-ccainittimeout%,%cc-msg-ccrupdate%,%cc-msg-ccaupdate%,%cc-msg-ccaupdatetimeout%,%cc-msg-ccrfinal%,%cc-msg-ccafinal%,%cc-msg-ccafinaltimeout%,%cc-msg-asr%,%cc-msg-asa%,%cc-msg-rar%,%cc-msg-raa%,%cc-msg-ccadropped%,%cc-msgerr-proto%,%cc-msgerr-badanswer%,%cc-msgerr-unknownsess%,%cc-msgerr-unknowncomm%,%cc-msgerr-reqtimeout%
> PDSNSystemSch3 | PDSN3 System Schema | EMS,PDSNSystem3,%date%,%time%,%cc-msgerr-parse%,%cc-msgerr-unkratinggrp%,%cc-msgerr-unkrulebase%,%cc-msgerr-unkfailure%,%cc-upd-threshold%,%cc-upd-qht%,%cc-upd-final%,%cc-upd-quotaexhaust%,%cc-upd-validitytime%,%cc-upd-otherquota%,%cc-upd-ratingchange%,%cc-upd-forcedreauth%,%cc-term-diamlogout%,%cc-term-servnotprov%,%cc-term-badanswer%,%cc-term-admin%,%cc-term-linkbroken%,%cc-term-authexpired%,%cc-term-usermoved%,%cc-term-sesstimeout%,%cc-traf-catcreate%,%cc-traf-catdelete%,%cc-traf-catlookup%,%cc-traf-hits%,%cc-traf-misses%,%cc-traf-triggerevent%,%cc-traf-finalunit%,%cc-traf-catsuccess%,%cc-traf-ratingfail%,%cc-traf-servdenied%,%cc-traf-limitreached%,%cc-traf-authreject%,%cc-traf-othererror%,%cf-static-ratereq%,%cf-static-ratesucc%,%cf-static-rateblock%,%cf-static-ratefail%,%cf-static-ratefail-nr%,%cf-static-ratefail-notindb%,%cf-dyn-ratereq%,%cf-dyn-ratesucc%,%cf-dyn-rateblock%,%cf-dyn-ratefail%,%cf-ratereq%,%cf-ratesucc%,%cf-rateblock%,%cf-ratefail%,%ikev2-cursa%,%ikev2-cursainit%,%ikev2-cursaresp%,%ikev2-ttlsa%,%ikev2-ttlsainit%,%ikev2-ttlsaresp%,%ikev2-attempt%,%ikev2-attemptinit%,%ikev2-attemptresp%,%ikev2-rxpacket%,%ikev2-txpacket%,%ikev2-rxoctet%,%ikev2-txoctet%,%ikev2-initfail%,%ikev2-initfail-noresp%,%ikev2-initfail-resp%,%ikev2-invcookie%,%ikev2-nattkeepalive-recv%,%ikev2-nattkeepalive-send%,%ikev2-dpd-recv%,%ikev2-dpd-send%,%ikev2-dpd-recv-reply%,%ikev2-dpd-send-reply%,%ikev2-dpd-timeout%,%ikev2-dpd-disconnect%,%ikev2-dpd-p1rekey%,%lic-combo-phone%,%lic-ecsv2%,%lic-ipservices-gateway%,%lic-evdoreva-pdsn%,%lic-scm-proxyregistrar-ietfrfc3261%,%lic-scm-proxypcscf%,%lic-scm-servingscscf%,%lic-scm-interrogatingicscf%,%lic-asngw%,%lic-asnlr%,%cf-cache-hits%,%cf-cache-misses%,%cf-cache-has-path-hits%,%cf-cache-flushes%,%sess-curimsauthorized%
> PDSNSystemSch4 | PDSN4 System Schema | EMS,PDSNSystem4,%date%,%time%,%sess-curimsauthorizing%,%pdif-curchildsa%,%ikev2-ikesadel%,%ikev2-ikesadelrep-recv%,%ikev2-ikesadelrep-sent%,%ikev2-ikesadelreq-recv%,%ikev2-ikesadelreq-sent%,%ipsec-dpd-p1rekey%
> GGSNSystemSch | GGSN System Schema | EMS,GGSNSystem,%date%,%time%,%sess-ttlarrived%,%sess-ttlrejected%,%sess-ttlconnected%,%sess-ttlauthsucc%,%sess-ttlauthfail%,%sess-ttllcpup%,%sess-ttlipcpup%,%sess-ttlsrcviol%,%sess-ttlkeepfail%,%sess-curttlcalls%,%sess-cursipconn%,%sess-curmipconn%,%sess-curactcall%,%sess-curdormcall%,%sess-curarrived%,%sess-curlcpnegot%,%sess-curlcpup%,%sess-curauth%,%sess-curauthed%,%sess-curipcpup%,%sess-curdisc%,%sess-calldur-1min%,%sess-calldur-2min%,%sess-calldur-5min%,%sess-calldur-15min%,%sess-calldur-1hour%,%sess-calldur-4hour%,%sess-calldur-12hour%,%sess-calldur-24hour%,%sess-calldur-over24hour%,%sess-setuptime-100ms%,%sess-setuptime-200ms%,%sess-setuptime-300ms%,%sess-setuptime-400ms%,%sess-setuptime-500ms%,%sess-setuptime-600ms%,%sess-setuptime-700ms%,%sess-setuptime-800ms%,%sess-setuptime-900ms%,%sess-setuptime-1sec%,%sess-setuptime-2sec%,%sess-setuptime-3sec%,%sess-setuptime-4sec%,%sess-setuptime-6sec%,%sess-setuptime-8sec%,%sess-setuptime-10sec%,%sess-setuptime-12sec%,%sess-setuptime-14sec%,%sess-setuptime-16sec%,%sess-setuptime-over16sec%,%incremental%,%enddate%,%endtime%,%localenddate%,%localendtime%,%sess-ttlfailed%,%uptime%,%uptimestr%,%lic-ggsn%,%lic-l2tplns%,%sess-txbytes%,%sess-rxbytes%,%sess-txpackets%,%sess-rxpackets%,%sess-siptxbytes%,%sess-siprxbytes%,%sess-miptxbytes%,%sess-miprxbytes%,%aaa-ttlreq%,%aaa-curreq%,%aaa-ttlauthreq%,%aaa-curauthreq%,%aaa-ttlauthprobe%,%aaa-curauthprobe%,%aaa-ttlacctreq%,%aaa-curacctreq%,%aaa-ttlauthsucc%,%aaa-ttlauthfail%,%aaa-ttlauthpurged%,%aaa-ttlauthcancelled%,%aaa-ttlauthdmuchal%,%aaa-ttlradauthreq%,%aaa-curradauthreq%,%aaa-ttlradauthreqretried%,%aaa-ttllclauthreq%,%aaa-curlclauthreq%,%aaa-ttlpseudoauthreq%,%aaa-curpseudoauthreq%,%aaa-ttlauthnulluser%,%aaa-ttlacctsucc%,%aaa-ttlacctpurged%,%aaa-ttlacctcancelled%,%aaa-ttlradacctreq%,%aaa-ttlradacctreqretried%,%disc-reason-summary%,%sess-curaaaactive%,%sess-curaaadeleting%,%sess-curaaaacctpending%,%sess-ttlemptyfwd%,%sess-ttlemptyrev%,%sess-ttlonlineprepaiderr%,%sess-ttlprepaidinitautherr%,%sess-ttlcrprpattempt%,%sess-ttlcrprpsuccess%,%sess-ttlrpcrpattempt%,%sess-ttlrpcrpsuccess%,%sess-curpmipconn%,%sess-curl2tplacconn%,%sess-curalwayson%,%sess-curbcmcsauth%,%sess-curbcmcsconn%,%sess-curhaipsecconn%,%sess-curl2tplacconnecting%,%sess-curpdptypeipconn%,%sess-curpdptypepppconn%,%sess-curprepaid%,%sess-rxpkt-1023%,%sess-rxpkt-127%,%sess-rxpkt-16%,%sess-rxpkt-2047%,%sess-rxpkt-255%,%sess-rxpkt-4095%,%sess-rxpkt-4500%,%sess-rxpkt-511%,%sess-rxpkt-64%,%sess-rxpkt-over4500%,%sess-ttldisconn%,%sess-ttlhandoff%,%sess-ttlonlineauthfail%,%sess-ttlonlineauthreq%,%sess-ttlonlineauthsucc%,%sess-ttlprepaid%,%sess-ttlproxydns-drop%,%sess-ttlproxydns-passthru%,%sess-ttlproxydns-redirect%,%sess-ttlrenewal%,%sess-txpkt-1023%,%sess-txpkt-127%,%sess-txpkt-16%,%sess-txpkt-2047%,%sess-txpkt-255%,%sess-txpkt-4095%,%sess-txpkt-4500%,%sess-txpkt-511%,%sess-txpkt-64%,%sess-txpkt-over4500%,%aaa-ttlauthkeepalive%,%aaa-curauthkeepalive%,%aaa-ttlacctkeepalive%,%aaa-curacctkeepalive%,%aaa-ttlauthkeepalivesuccess%,%aaa-ttlauthkeepalivefailure%,%aaa-ttlauthkeepalivepurged%,%aaa-ttlacctkeepalivesuccess%,%aaa-ttlacctkeepalivetimeout%,%aaa-ttlacctkeepalivepurged%,%ipsg-total-call-arrived%,%ipsg-total-call-rejected%,%ipsg-total-call-demult%,%ipsg-total-dereg-rep-sent%,%ipsg-cur-active-call%,%ipsg-total-active-serv%,%asngw-cur-active-call%,%asngw-total-sess-setup%,%asngw-retriesexhaust%,%asngw.sfs%,%asngw.tidfail%,%asngw-handoffattempt%,%asngw-handoffdenied%,%asngw-handoffcomp%,%asngw.authsucc%,%asngw-authfailures%
> PPP1Sch | PPP1 Schema | EMS,PPP1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%init%,%reneg%,%success%,%failed%,%released%,%released-local%,%released-remote%,%lcp-fail-maxretry%,%lcp-fail-option%,%ipcp-fail-maxretry%,%ipcp-fail-option%,%fail-ccp%,%fail-auth%,%entered-lcp%,%entered-auth%,%entered-ipcp%,%reneg-pdsn%,%reneg-mobile%,%reneg-addrmis%,%reneg-other%,%auth-attempt-chap%,%auth-attempt-ppp%,%auth-attemp-mschap%,%auth-success-chap%,%auth-success-pap%,%auth-success-mschap%,%auth-fail-chap%,%auth-fail-pap%,%auth-fail-mschap%,%comp-stac%,%comp-mppc%,%comp-defl%,%rcverr-basfcs%,%rcverr-unknproto%,%rcverr-badaddr%,%rcverr-badctrl%,%comp-vjhdr%,%disc-lcp-remote%,%disc-rp-remote%,%disc-admin%,%disc-idle-timeout%,%disc-abs-timeout%,%disc-ppp-keepalive%,%disc-no-resource%,%disc-misc%,%remote-term%,%misc-fail%
> PPP2Sch | PPP2 Schema | EMS,PPP2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%fail-reneg%,%lcp-fail-unknown%,%ipcp-fail-unknown%,%abort-auth%,%rp-disc%,%success-lcp%,%success-auth%,%reneg-rp_handoff%,%reneg-update%,%auth-abort-chap%,%auth-abort-pap%,%auth-abort-mschap%,%sess-skip-auth%,%comp-sess-neg%,%comp-sess-neg-fail%,%disc-rp-local%,%disc-add-flow-fail%,%disc-maxretry-lcp%,%disc-maxretry-ipcp%,%disc-max-setup-time%,%disc-bad-dest-vpn%,%disc-opt-neg-lcp%,%disc-opt-neg-ipcp%,%disc-no-remoteaddr%,%disc-typedetect-fail%,%disc-bad-src-addr%,%disc-remote%,%disc-long-timeout%,%disc-auth-fail%,%lcpecho-req-total%,%lcpecho-req-resent%,%lcpecho-rep-recved%,%lcpecho-timeout%,%recverr-ctrl-field%,%recverr-bad-length%,%in-oct%,%in-ucast%,%in-nucast%,%in-pkt%,%in-discard%,%in-discard-oct%,%out-oct%,%out-ucast%,%out-nucast%,%out-pkt%,%out-discard%,%out-discard-oct%,%num-sessions%,%lcpvse-req-total%,%lcpvse-req-resent%,%lcpvse-rep-recved%,%lcpvse-proto-reject%,%lcpvse-req-maxreach%,%svctype%,%conn-sess-reneg%,%comp-rohchdr%,%altppp-connected%,%reneg-rp-handoff%,%auth-attempt-pap%,%auth-attempt-mschap%
> MIPFA1Sch | MIPFA1 Schema | EMS,MIPFA1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%advert-send%,%disc-expiry%,%disc-dereg%,%disc-admin%,%auth-attempt%,%auth-success%,%auth-failure%,%recv-total%,%recv-initial%,%recv-renewal%,%recv-dereg%,%accept-total%,%accept-initial%,%accept-renewal%,%accept-dereg%,%denied-total%,%denied-initial%,%denied-renewal%,%denied-dereg%,%discard-total%,%discard-initial%,%discard-renewal%,%discard-dereg%,%relayed-total%,%relayed-initial%,%relayed-renewal%,%relayed-dereg%,%authfail-total%,%authfail-initial%,%authfail-renewal%,%authfail-dereg%,%denied-pdsn-total%,%denied-pdsn-initial%,%denied-pdsn-renewal%,%denied-pdsn-dereg%,%denied-ha-total%,%denied-ha-initial%,%denied-ha-renewal%,%denied-ha-dereg%,%denied-pdsn-unspec%,%denied-pdsn-timeout%,%denied-pdsn-admin%,%denied-pdsn-resource%,%denied-pdsn-mnauth%,%denied-pdsn-haauth%,%denied-pdsn-lifetoolong%,%denied-pdsn-badreq%,%denied-pdsn-badreply%,%denied-pdsn-missnai%,%denied-pdsn-misshomeagent%,%denied-pdsn-misshomeaddr%,%denied-pdsn-unkchallange%,%denied-pdsn-misschallenge%,%denied-pdsn-stalechallenge%,%denied-pdsn-mntoodistant%,%denied-pdsn-styleunavail%,%denied-pdsn-hanetunreach%,%denied-pdsn-hahostunreach%
> MIPFA2Sch | MIPFA2 Schema | EMS,MIPFA2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%denied-pdsn-haportunreach%,%denied-pdsn-haunreach%,%denied-pdsn-invcoa%,%denied-pdsn-encapunavail%,%denied-pdsn-revtununavail%,%denied-pdsn-revtunmand%,%denied-ha-faauth%,%denied-ha-badreq%,%denied-ha-mismatchid%,%denied-ha-simulbind%,%denied-ha-unknownha%,%denied-ha-revtununavail%,%replyrcv-total%,%replyrcv-totalrelayed%,%replyrcv-errors%,%replyrcv-initial%,%replyrcv-initialrelayed%,%replyrcv-renewal%,%replyrcv-renewalrelayed%,%replyrcv-dereg%,%replyrcv-deregrelayed%,%replysent-total%,%replysent-acceptreg%,%replysent-acceptdereg%,%replysent-badreq%,%replysent-lifetoolong%,%replysent-mnauthfail%,%replysent-haauthfail%,%replysent-adminprohib%,%replysent-noresources%,%replysent-revtununavail%,%replysent-revtunmand%,%replysent-senderrors%,%replysent-mntoodistant%,%replysent-invcoa%,%replysent-hanetunreach%,%replysent-hahostunreach%,%replysent-haportunreach%,%replysent-haunreach%,%replysent-regtimeout%,%replysent-missnai%,%replysent-misshomeagent%,%replysent-misshomeaddr%,%replysent-unkchallenge%,%replysent-misschallenge%,%replysent-stalechallenge%,%replysent-badreply%,%reqsent-initial%,%reqsent-initial-resend%,%reqsent-initial-noresend%,%reqsent-renew%,%reqsent-renew-resend%,%reqsent-renew-noresend%,%reqsent-dereg%,%reqsent-dereg-resend%,%reqsent-dereg-noresend%,%denied-pdsn-unkchallenge%,%denied-pdsn-unknowncvse%,%replysent-unspecified%,%replysent-delstyleunavail%,%ttlprepaid%,%curprepaid%,%ttlonlineauthsucc%,%ttlonlineauthfail%,%revoc-sent%,%revoc-retry-sent%,%revoc-ack-recv%,%revoc-timeout%,%revoc-recv%,%revoc-ack-sent%
> MIPHASch | MIPHA Schema | EMS,MIPHA,%date%,%time%,%vpnname%,%vpnid%,%servname%,%disconnects%,%expiry%,%dereg%,%admindrop%,%recv-total%,%recv-initial%,%recv-renew%,%recv-dereg%,%accept-total%,%accept-reg%,%accept-renew%,%accept-dereg%,%denied-total%,%denied-initial%,%denied-renew%,%denied-dereg%,%discard-total%,%reply-total%,%reply-acceptreg%,%reply-acceptdereg%,%reply-denied%,%reply-badreq%,%reply-mismatchid%,%reply-adminprohib%,%reply-unspecerr%,%reply-noresource%,%reply-mnauthfail%,%reply-faauthfail%,%reply-simulbind%,%reply-unknownha%,%reply-revtununavail%,%reply-revtunmand%,%reply-encapunavail%,%reply-senderror%,%farevocation%,%accept-ho%,%denied-ho%,%reply-error%,%num-sessions%,%recv-ho%,%revoc-sent%,%revoc-retry-sent%,%revoc-ack-recv%,%revoc-timeout%,%revoc-recv%,%revoc-ack-sent%,%miscerror%,%auth-attempt%,%auth-failure%,%auth-success%,%auth-real-failure%,%auth-misc-failure%,%reply-unknowncvse%,%reply-cong-drop%,%reply-cong-adminprohib%,%reply-cong-unknownha%,%reply-udp-encapunavail%,%ttlprepaid%,%curprepaid%,%ttlonlineauthsucc%,%ttlonlineauthfail%,%paaa-query-total%,%paaa-query-accept%,%paaa-query-denied%,%paaa-resp-sent%,%paaa-resp-found%,%paaa-resp-notfound%,%paaa-resp-poolover%,%paaa-resp-misc%,%ipsec-esp-txpackets%,%ipsec-esp-txbytes%,%ipsec-ah-txpackets%,%ipsec-ah-txbytes%,%ipsec-error-txpackets%,%ipsec-error-txbytes%,%ipsec-esp-rxpackets%,%ipsec-esp-rxbytes%,%ipsec-ah-rxpackets%,%ipsec-ah-rxbytes%,%ipsec-error-packets%,%ipsec-error-bytes%,%ipsec-replay-packets%,%ipsec-replay-bytes%,%ipsec-decode-packets%,%ipsec-decode-bytes%,%ipsec-auth-packets%,%ipsec-auth-bytes%,%ipsec-tooshort-packets%,%ipsec-tooshort-bytes%,%ipsec-dpdreq-sent%,%ipsec-dpdreq-recv%,%ipsec-dpdreply-sent%,%ipsec-dpdreply-recv%,%ipsec-dpdtimeout%,%ipsec-dpddisconn%,%ipsec-dpdrekey%
> MIPHA2Sch | MIPHA2 Schema | EMS,MIPHA2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%ipsec-nattkeepalive-sent%,%ipsec-nattkeepalive-recv%,%ipsec-ike-udpflows%,%ipsec-ike-cookieflows%,%ipsec-ike-txpackets%,%ipsec-ike-rxpackets%,%ipsec-ike-reqrecv%,%ipsec-ike-udpflowpackets%,%ipsec-ike-cookieflowpackets%,%ipsec-cur-tun%,%ipsec-cur-tunestablished%,%ipsec-ike-fails%,%ipsec-ttl-tun%,%ipsec-ttl-tunestablished%,%ipsec-call-req-rej%
> RP Schema | RPSch | EMS,RP,%date%,%time%,%vpnname%,%vpnid%,%servname%,%recv-total%,%accept-total%,%denied-total%,%discard-total%,%accept-initial%,%accept-intrapdsn%,%accept-interpdsn%,%denied-initial%,%accept-renew%,%denied-renew%,%accept-dereg%,%denied-dereg%,%send-error%,%hash-error%,%decode-error%,%unhandled%,%seqerror%,%deny-unspec%,%deny-adminprohib%,%deny-noresource%,%deny-auth%,%deny-idmismatch%,%deny-badrequest%,%deny-unknownpdsn%,%deny-revtununavail%,%deny-revtunreq%,%deny-unrecogvend%,%upd-total%,%upd-accept%,%upd-denied%,%upd-unack%,%upd-trans%,%upd-retrans%,%upd-received%,%upd-discard%,%upd-senderror%,%upd-upltrinit%,%upd-other%,%upd-handoff%,%upddeny-unspec%,%upddeny-adminprohib%,%upddeny-auth%,%upddeny-idmismatch%,%upddeny-badrequest%,%sec-violations%,%sec-badauth%,%sec-badid%,%sec-badspi%,%sec-mnhaauth%,%sec-regupdate%,%disc-absent%,%disc-nomem%,%disc-malform%,%disc-authfail%,%disc-bounce%,%disc-inputq%,%disc-mismatchid%,%disc-invpktlen%,%disc-misc%,%reply-total%,%recv-initial%,%accept-active-intrapdsn%,%accept-dormant-intrapdsn%,%recv-renew%,%active-start-renew%,%active-stop-renew%,%recv-dereg%,%active-stop-dereg%,%upd-ttlnoretrans%,%upd-ack-received%,%num-sessions%,%deny-sessclosed%,%deny-cong-drop%,%deny-cong-adminprohib%,%deny-cong-unknownpdsn%,%sess-num-transmitted%,%sess-accepted%,%sess-denied%,%sess-not-acknowledged%,%sess-initial-update%,%sess-update-retransmitted%,%sess-update-ack-received%,%sess-update-ack-discarded%,%sess-update-send-error%,%sess-always-on-indication%,%sess-reason-unspecified%,%sess-PDSN-auth-fail%,%sess-ID-mismatch%,%sess-poorly-formed-update%,%sess-para-not-update%,%sess-absent%,%sess-no-memory%,%sess-malformed%,%sess-auth-fail%,%sess-ID-bounce-error%,%sess-input-Q-exceeded%,%sess-mismatched-ID%,%sess-invalid-packet-length%,%sess-misc-reasons%,%sess-gre-packet-sent-sdb%,%sess-gre-byte-sent-sdb%,%ttlprepaid%,%curprepaid%,%ttlonlineauthsucc%,%ttlonlineauthfail%,%discard-initial%,%recv-initial-setupstart%,%accept-initial-setupstart%,%denied-initial-setupstart%,%discard-initial-setupstart%,%discard-renew%,%recv-renew-noairlink%,%accept-renew-noairlink%,%denied-renew-noairlink%,%discard-renew-noairlink%,%recv-renew-activestart%,%accept-renew-activestart%,%denied-renew-activestart%,%discard-renew-activestart%,%recv-renew-activestop%,%accept-renew-activestop%,%denied-renew-activestop%,%discard-renew-activestop%,%discard-dereg%,%recv-dereg-noactivestop%,%accept-dereg-noactivestop%,%denied-dereg-noactivestop%,%discard-dereg-noactivestop%,%recv-dereg-activestop%,%accept-dereg-activestop%,%denied-dereg-activestop%,%discard-dereg-activestop%,%recv-intrapdsn-activeanidhandoff%,%accept-intrapdsn-activeanidhandoff%,%denied-intrapdsn-activeanidhandoff%,%discard-intrapdsn-activeanidhandoff%,%recv-intrapdsn-dormantanidhandoff%,%accept-intrapdsn-dormantanidhandoff%,%denied-intrapdsn-dormantanidhandoff%,%discard-intrapdsn-dormantanidhandoff%,%recv-interpdsn-activemeianidhandoff%,%accept-interpdsn-activemeianidhandoff%,%denied-interpdsn-activemeianidhandoff%,%discard-interpdsn-activemeianidhandoff%,%rx-pkt-xoff%,%rx-pkt-xon%,%xontoxoff%,%pkt-dropped-xoff%,%bytes-dropped-xoff%
> RPSch2 | RP2 Schema | EMS,RP2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%a10-cursetup%,%a10-ttlreleased%,%a10-ttlsetup%,%a10aux-cursetup%,%a10aux-ttlreleased%,%a10aux-ttlsetup%,%a10main-cursetup%,%a10main-ttlreleased%,%a10main-ttlsetup%,%deny-badrequest-alractive%,%deny-badrequest-alrdorm%,%deny-badrequest-authextn%,%deny-badrequest-fieldlen%,%deny-badrequest-flags%,%deny-badrequest-hoanonzero%,%deny-badrequest-miscoaaddr%,%deny-badrequest-other%,%deny-badrequest-pkttoolong%,%deny-badrequest-pkttooshort%,%deny-badrequest-setupabsent%,%deny-badrequest-sse%,%deny-badrequest-unkextn%,%deny-badrequest-vse%,%deny-noresource-a11mgrrej%,%deny-noresource-inputq%,%deny-noresource-nomem%,%deny-noresource-nosessmgr%,%deny-noresource-policy%,%deny-noresource-sessmgrrej%,%deny-noresource-sessmgrretried%,%deny-unspec-crphandoff%,%deny-unspec-intrahandoff%,%deny-unspec-lifezero%,%deny-unspec-noairlink%,%deny-unspec-notready%,%deny-unspec-nullpkt%,%reva-rrq-accept%,%reva-rrq-denied%,%reva-rrq-recv%,%reva-rrq-reply%,%rrqdiscard-adminprohib%,%rrqdiscard-authfail%,%rrqdiscard-bounce%,%rrqdiscard-grekey%,%rrqdiscard-inputq%,%rrqdiscard-invlen%,%rrqdiscard-maxsess%,%rrqdiscard-misc%,%rrqdiscard-nomem%,%rrqdiscard-nosessmgr%,%rrqdiscard-overload%,%rrqdiscard-smgrdead%,%rrqdiscard-smgrnotready%,%rrqdiscard-unkpdsn%,%sess-currevasetup%,%sess-cursetup%,%sess-release-dereg%,%sess-release-expiry%,%sess-release-grekey%,%sess-release-other%,%sess-release-pcfmonfail%,%sess-release-ppplayer%,%sess-ttlreleased%,%sess-ttlrevasetup%,%sess-ttlsetup%,%sess-updackdisc-pktnothand%,%sess-updackdisc-sessdisc%,%sess-upddenied-adminprohib%,%sess-upddenied-handoff%,%sess-upddenied-idnotsupp%,%sess-upddenied-noresource%,%sess-updreason-alwayson%,%sess-updreason-qosinfo%,%sess-updreason-qosoptrig%,%sess-updreason-qostftviol%,%sess-updreason-qostrafpol%,%sess-updreason-qostrafviol%,%upd-discard-unhpkt%,%upd-discard-unkpcf%,%upd-lifetime%,%upd-smgrexit%
> RPSch3 | RP3 Schema | EMS,RP3,%date%,%time%,%vpnname%,%vpnid%,%servname%,%sess-ttlrevareleased%,%sess-ttlrevadowngrade%,%deny-bsninfo%,%upd-uplyrinit%,%upd-discard-absent%,%upd-discard-nomem%,%upd-discard-malform%,%upd-discard-authfail%,%upd-discard-bounce%,%upd-discard-inputq%,%upd-discard-mismatchid%,%upd-discard-invpktlen%,%upd-discard-misc%,%sess-pdsn-auth-fail%,%sess-id-mismatch%,%sess-release-purged%
> GTPC1Sch | GTPC1 Schema | EMS,GTPC1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%setup-total%,%setup-ip%,%setup-ppp%,%released-total%,%cpc-total%,%cpc-v0%,%cpc-v1%,%cpc-sec%,%cpc-retrans%,%cpc-accept%,%cpc-deny%,%cpc-discard%,%upc-rx%,%upc-rx-accept%,%upc-rx-deny%,%upc-rx-discard%,%upc-tx%,%upc-tx-accept%,%upc-tx-deny%,%dpc-rx%,%dpc-rx-accept%,%dpc-rx-deny%,%dpc-rx-discard%,%dpc-tx%,%dpc-tx-accept%,%dpc-tx-deny%,%cpc-aa%,%cpc-aa-accept%,%cpc-aa-deny%,%cpc-aa-discard%,%dpc-aa-rx%,%dpc-aa-rx-accept%,%dpc-aa-rx-deny%,%dpc-aa-rx-discard%,%dpc-aa-tx%,%dpc-aa-tx-accept%,%dpc-aa-tx-deny%,%err-ind-rx%,%err-ind-tx%,%cpc-noresource%,%cpc-addr-occupied%,%cpc-nomem%,%cpc-missing-apn%,%cpc-unknown-pdp%,%cpc-auth-fail%,%cpc-sys-fail%,%cpc-sem-tft%
> GTPC2Sch | GTPC2 Schema | EMS,GTPC2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%cpc-syn-tft%,%cpc-sem-pktfilter%,%cpc-syn-pktfilter%,%cpc-ie-err%,%cpc-ie-missing%,%cpc-opt-ie-err%,%cpc-malformed%,%cpc-version%,%disc-sgsn%,%disc-path-fail%,%disc-smgr-dead%,%disc-admin%,%disc-other%,%disc-teardown%,%disc-idle%,%disc-absolute%,%disc-src-addr%,%disc-flow-add%,%disc-dhcp-renew-fail%,%disc-long-durn%,%disc-aborted%,%disc-apn-rmvd%,%pdu-notif%,%pdu-notif-accpet%,%pdu-notif-deny%,%pdu-notif-rej%,%pdu-notif-rej-accept%,%pdu-notif-rej-deny%,%pdu-notif-rej-discard%,%sri-req%,%sri-accept%,%sri-deny%,%fail-rep%,%fail-rep-accept%,%fail-rep-deny%,%note-ms-gprs%,%note-ms-gprs-accept%,%note-ms-gprs-deny%,%note-ms-gprs-discard%,%num-bytes-in%,%num-pkts-in%,%num-bytes-out%,%num-pkts-out%,%cpc-srv-not-supp%,%gtpu-echo-req-rx%,%gtpu-echo-req-tx%,%gtpu-echo-rsp-tx%,%gtpu-echo-rsp-rx%,%ctrl-num-bytes-in%,%ctrl-num-pkts-in%,%ctrl-num-bytes-out%,%ctrl-num-pkts-out%,%echo-req-rx%,%echo-req-tx%,%echo-rsp-tx%,%echo-rsp-rx%,%setup-current%,%current-ip%,%current-ppp%,%current-ipv6%,%current-ntwkinitd%,%setup-ipv6%,%setup-sgsn%,%setup-ggsn%,%qosconv-bytes-in%,%qosconv-pkts-in%,%qosconv-bytes-out%,%qosconv-pkts-out%,%qosstrm-bytes-in%,%qosstrm-pkts-in%,%qosstrm-bytes-out%,%qosstrm-pkts-out%,%qosint1-bytes-in%,%qosint1-pkts-in%,%qosint1-bytes-out%,%qosint1-pkts-out%,%qosint2-bytes-in%,%qosint2-pkts-in%,%qosint2-bytes-out%,%qosint2-pkts-out%,%qosint3-bytes-in%,%qosint3-pkts-in%,%qosint3-bytes-out%,%qosint3-pkts-out%,%qosint-bytes-in%,%qosint-pkts-in%,%qosint-bytes-out%,%qosint-pkts-out%,%qosback-bytes-in%,%qosback-pkts-in%,%qosback-bytes-out%,%qosback-pkts-out%,%dyn-ipv4-attempt%,%dyn-ipv6-attempt%,%dyn-ppp-attempt%,%dyn-ipv4-success%,%dyn-ipv6-success%,%dyn-ppp-success%,%cpc-no-apn-subscription%
> GTPPSch | GTPP Schema | EMS,GTPP,%date%,%time%,%vpnname%,%vpnid%,%echo-req-rx%,%echo-req-tx%,%echo-rsp-rx%,%echo-rsp-tx%,%redir-rcvd%,%redir-rsp%,%node-alive%,%node-alive-rsp%,%data-rec-trans%,%dup-data-rec-trans%,%send-data-rec%,%rel-data-rec%,%cancel-data-rec%,%data-rec-trans-rsp%,%delete-node%,%node-addr%,%req-accept%,%req-not-fulfil%,%req-malform%,%version-not-supp%,%serv-not-supp%,%mand-ie-err%,%mand-ie-miss%,%opt-ie-err%,%dup-already-fulfil%,%already-fulfil%,%no-resource%,%sys-fail%,%normal-close%,%abnormal-close%,%vol-limit-close%,%time-limit-close%,%open-req%,%aaa-acct-arch%,%rdir-sys-fail%,%rdir-txbuf-full%,%rdir-rxbuf-full%,%other-node-dn%,%self-node-dn%,%rdir-no-res%,%rdir-serv-no%,%rdir-version-not-supp%,%rdir-mand-ie-miss%,%rdir-mand-ie-err%,%rdir-opt-ie-err%,%rdir-malformed%,%rdir-rsp-sys-fail%,%gss-echo-req%,%gss-echo-rsp%,%gss-gtpp-req%,%gss-gtpp-req-ret%,%gss-gtpp-rsp%,%gss-gtpp-rsp-failed%,%gss-gcdr-req%,%gss-gcdr-req-ret%,%gss-gcdr-rsp%,%gss-gcdr-rsp-failed%,%gss-aaaproxy-rec-req%,%gss-aaaproxy-rec-ret%,%gss-aaaproxy-rec-rsp%,%gss-aaaproxy-rec-rsp-failed%,%gss-aaamgr-rec-req%,%gss-aaamgr-rec-ret%,%gss-aaamgr-rec-rsp%,%gss-aaamgr-rec-rsp-failed%,%gss-update-cgf-req%,%gss-update-cgf-req-ret%,%gss-update-cgf-rsp%,%gss-update-cfg-rsp-failed%,%gss-clear-db-req%,%gss-clear-db-req-ret%,%gss-clear-db-rsp%,%gss-clear-db-rsp-failed%,%gss-update-req%,%gss-invalid-req-rcvd%
> IPPoolSch | IPPool Schema | EMS,IPPOOL,%date%,%time%,%vpnname%,%vpnid%,%name%,%used%,%hold%,%release%,%free%,%type%,%priority%,%state%,%startaddr%,%groupname%
> APNSch | APN Schema | EMS,APN,%date%,%time%,%vpnname%,%vpnid%,%apn%,%uplnk-bytes%,%dnlnk-bytes%,%uplnk-pkts%,%dnlnk-pkts%,%uplnk-drop%,%dnlnk-drop%,%bad-hdr%,%ttl-excd%,%frag-sent%,%frag-fail%,%inacl-drop%,%outacl-drop%,%bad-src-addr%,%addr-stat%,%addr-lpool%,%addr-rad%,%addr-dhcp%,%addr-dhcp-rly%,%addr-no-alloc%,%sess-curr%,%sess-curr-all%,%sess-tot%,%sess-tot-all%,%uplnk-bytes-drop%,%dnlnk-bytes-drop%,%data-fromuseravg-bps%,%data-touseravg-bps%,%data-fromusersust-bps%,%data-tousersust-bps%,%data-fromuseravg-pps%,%data-touseravg-pps%,%data-fromusersust-pps%,%data-tousersust-pps%,%qosconv-pkts-uplnk%,%qosconv-pkts-dnlnk%,%qosstrm-pkts-uplnk%,%qosstrm-pkts-dnlnk%,%qosint1-pkts-uplnk%,%qosint1-pkts-dnlnk%,%qosint2-pkts-uplnk%,%qosint2-pkts-dnlnk%,%qosint3-pkts-uplnk%,%qosint3-pkts-dnlnk%,%qosint-pkts-uplnk%,%qosint-pkts-dnlnk%,%qosback-pkts-uplnk%,%qosback-pkts-dnlnk%,%att-pdp-ctxt%,%att-deact-pdp-ggsn%,%succ-deact-pdp-ggsn%,%att-deact-pdp-ms%,%succ-deact-pdp-ms%,%dyn-ipv4-attempt%,%dyn-ipv6-attempt%,%dyn-ipv4-success%,%dyn-ipv6-success%,%auth-req-sent%,%auth-acc-rcvd%,%auth-timeout%,%acc-req-sent%,%acc-rsp-rcvd%,%acc-req-timeout%
> LAC1Sch | LAC Schema 1 | EMS,LAC1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%tun-conn-attempt%,%tun-conn-success%,%tun-conn-fail%,%tun-conn-curactive%,%sess-attempts%,%sess-successful%,%sess-failed%,%sess-curactive%,%sess-intrapdsnho-attempt%,%sess-intrapdsnho-success%,%sess-intrapdsnho-failed%,%sess-interpdsnho-attempt%,%recv-err-malformed%,%recv-err-ctrlfield%,%recv-err-pktlen%,%recv-err-avplen%,%recv-err-protover%,%recv-err-md5%,%recv-err-invattr%,%recv-err-unkattr%,%recv-err-invsessid%,%recv-err-invstate%,%recv-err-unkmsg%,%recv-err-unmatchpktlen%,%recv-err-invtunid%,%tun-genclear%,%tun-ctrlconnexists%,%tun-unauth%,%tun-badproto%,%tun-reqshutdown%,%tun-statemacherr%,%tun-badlen%,%tun-oor%,%tun-noresource%,%tun-vendspec%,%tun-tryanotherlns%,%tun-unkavp%,%tun-ipsecdisc%,%tun-ipsecfail%,%tun-license%,%tun-newcallpoldisc%,%tun-maxretry%,%tun-syslimit%,%tun-miscerr%,%sess-nogeneral%,%sess-admin%,%sess-lossofcarr%
> LAC2Sch | LAC Schema 2 | EMS,LAC2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%sess-remoteadmin%,%sess-nofactemp%,%sess-nofacperm%,%sess-invdest%,%sess-nocarrier%,%sess-busysig%,%sess-nodialtime%,%sess-lactimeout%,%sess-noframing%,%sess-noctrlconn%,%sess-badlen%,%sess-oor%,%sess-noresource%,%sess-invsessid%,%sess-vendspec%,%sess-tryanotherlns%,%sess-unkavp%,%sess-maxtunnel%,%sess-ipsecfail%,%sess-ipsecdisc%,%sess-newcallpoldisc%,%sess-license%,%sess-servmismatch%,%sess-miscerr%
> CLOSEDRP1Sch | ClosedRP Schema 1 | EMS,CLOSEDRP1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%tun-conn-attempt%,%tun-conn-success%,%tun-conn-fail%,%tun-conn-curactive%,%sess-attempts%,%sess-successful%,%sess-failed%,%sess-curactive%,%sess-intrapdsnho-attempt%,%sess-intrapdsnho-success%,%sess-intrapdsnho-failed%,%sess-interpdsnho-attempt%,%recv-err-malformed%,%recv-err-ctrlfield%,%recv-err-pktlen%,%recv-err-avplen%,%recv-err-protover%,%recv-err-md5%,%recv-err-invattr%,%recv-err-unkattr%,%recv-err-invsessid%,%recv-err-invstate%,%recv-err-unkmsg%,%recv-err-unmatchpktlen%,%recv-err-invtunid%,%tun-genclear%,%tun-ctrlconnexists%,%tun-unauth%,%tun-badproto%,%tun-reqshutdown%,%tun-statemacherr%,%tun-badlen%,%tun-oor%,%tun-noresource%,%tun-vendspec%,%tun-tryanotherlns%,%tun-unkavp%,%tun-ipsecdisc%,%tun-ipsecfail%,%tun-license%,%tun-newcallpoldisc%,%tun-maxretry%,%tun-syslimit%,%tun-miscerr%,%sess-nogeneral%,%sess-admin%,%sess-lossofcarr%
> CLOSEDRP2Sch | ClosedRP Schema 2 | EMS,CLOSEDRP2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%sess-remoteadmin%,%sess-nofactemp%,%sess-nofacperm%,%sess-invdest%,%sess-nocarrier%,%sess-busysig%,%sess-nodialtime%,%sess-lactimeout%,%sess-noframing%,%sess-noctrlconn%,%sess-badlen%,%sess-oor%,%sess-noresource%,%sess-invsessid%,%sess-vendspec%,%sess-tryanotherlns%,%sess-unkavp%,%sess-maxtunnel%,%sess-ipsecfail%,%sess-ipsecdisc%,%sess-newcallpoldisc%,%sess-license%,%sess-servmismatch%,%sess-miscerr%,%sess-hocomplete%,%sess-invho%,%sess-duplsess%,%ttlprepaid%,%curprepaid%,%ttlonlineauthsucc%,%ttlonlineauthfail%
> RADIUSSch | RADIUS Schema | EMS,RADIUS,%date%,%time%,%vpnname%,%vpnid%,%servertype%,%ipaddr%,%auth-req-sent%,%auth-req-sentwdmu%,%auth-req-pending%,%auth-req-retried%,%auth-req-retriedwdmu%,%auth-chal-rcvd%,%auth-acc-rcvd%,%auth-rej-rcvd%,%auth-rej-rcvdwdmu%,%auth-timeout%,%auth-cons-fail%,%auth-rsp-badauth%,%auth-rsp-malformed%,%auth-rsp-malformedattr%,%auth-rsp-unktype%,%auth-rsp-dropped%,%auth-rsp-roundtripusec%,%probe-issued%,%probe-success%,%probe-failed%,%probe-roundtriptimeusec%,%acc-req-sent%,%acc-req-pending%,%acc-req-retried%,%acc-rsp-rcvd%,%acc-req-timeout%,%acc-req-cons-fail%,%acc-rsp-badresp%,%acc-rsp-malformed%,%acc-rsp-unktype%,%acc-rsp-dropped%,%acc-rsp-roundtripusec%,%port%,%acc-start-sent%,%acc-stop-sent%,%acc-interim-sent%,%acc-start-retries%,%acc-stop-retries%,%acc-interim-retries%,%group%,%acc-ttl-g1%,%acc-ttl-g2%,%online-acc-req-sent%,%online-acc-req-pending%,%online-acc-req-retried%,%online-acc-rsp-rcvd%,%online-acc-rej-rcvd%,%online-acc-req-timeout%,%online-acc-rsp-badauth%,%online-acc-rsp-malformed%,%online-acc-rsp-malformedattr%,%online-acc-rsp-unktype%,%online-acc-badmsgauth%,%online-acc-nomsgauth%,%nasipaddr%,%keepalive-auth-req-sent%,%keepalive-auth-retried%,%keepalive-auth-acc-rcvd%,%keepalive-auth-timeout%,%keepalive-auth-rej-rcvd%,%keepalive-acct-req-sent%,%keepalive-acct-retried%,%keepalive-acct-success%,%keepalive-acct-timeout%,%keepalive-acct-rsp-badauth%,%cons-fail%,%keepalive-auth-rsp-badauth%,%keepalive-auth-rsp-malformed%,%keepalive-auth-rsp-malformedattr%,%keepalive-auth-rsp-unktype%,%keepalive-auth-rsp-dropped%,%acc-on-sent%,%acc-off-sent%,%acc-on-retries%,%acc-off-retries%,%keepalive-acct-rsp-malformed%,%keepalive-acct-rsp-unktype%,%keepalive-acct-rsp-dropped%
> MISCSch | Miscellaneous Schema | %ipaddr%,%host%,%uptime%,%time%,%localdate%,%localtime%,%localtz%,%time2%,%localtime2%
> MISCSchForEMS | New Miscellaneous Schema | EMS,MISC,%date%,%time%,%ipaddr%,%host%,%uptime%,%localdate%,%localtime%,%localtz%,%time2%,%localtime2%,%swversion%,%swbuild%,%localtzoffset%
> ECS1Sch | ECS1 Schema | EMS,ECS1,%date%,%time%,%ecs-subscribers%,%ecs-subscribers-cur%,%gcdrs-generated%,%edrs-generated%,%udrs-generated%,%ip-flows%,%ip-flows-cur%,%ip-uplk-bytes%,%ip-dwnlk-bytes%,%ip-uplk-pkts%,%ip-dwnlk-pkts%,%ip-uplk-pkts-frag%,%ip-dwnlk-pkts-frag%,%ip-uplk-bytes-frag%,%ip-dwnlk-bytes-frag%,%udp-flows%,%udp-flows-cur%,%udp-uplk-bytes%,%udp-dwnlk-bytes%,%udp-uplk-pkts%,%udp-dwnlk-pkts%,%udp-inv-pkts%,%tcp-flows%,%tcp-flows-cur%,%tcp-uplk-bytes%,%tcp-dwnlk-bytes%,%tcp-uplk-pkts%,%tcp-dwnlk-pkts%,%tcp-uplk-bytes-retr%,%tcp-dwnlk-bytes-retr%,%tcp-uplk-pkts-retr%,%tcp-dwnlk-pkts-retr%,%tcp-uplk-pkts-ooo-analyzd%,%tcp-dwnlk-pkts-ooo-analyzd%,%tcp-uplk-pkts-ooo-fail%,%tcp-dwnlk-pkts-ooo-fail%,%tcp-uplk-pkts-ooo-retr%,%tcp-dwnlk-pkts-ooo-retr%,%icmp-flows%,%icmp-flows-cur%,%icmp-uplk-bytes%,%icmp-dwnlk-bytes%,%icmp-uplk-pkts%,%icmp-dwnlk-pkts%,%icmp-ech-req%,%icmp-ech-rep%,%icmp-dst-unrch%,%icmp-redir%,%icmp-tm-excd%,%icmp-trace-route%,%icmp-oth%,%http-flows%,%http-flows-cur%,%http-uplk-bytes%,%http-dwnlk-bytes%,%http-uplk-pkts%,%http-dwnlk-pkts%,%http-uplk-bytes-retr%,%http-dwnlk-bytes-retr%,%http-uplk-pkts-retr%,%http-dwnlk-pkts-retr%,%http-req-succ%,%http-req-fail%,%http-get-req%,%http-post-req%,%http-connect-req%,%http-inv-pkts%,%https-flows%,%https-flows-cur%,%https-uplk-bytes%,%https-dwnlk-bytes%,%https-uplk-pkts%,%https-dwnlk-pkts%,%https-uplk-bytes-retr%,%https-dwnlk-bytes-retr%,%https-uplk-pkts-retr%,%https-dwnlk-pkts-retr%,%wtp-trans%,%wtp-cls-zero%,%wtp-cls-one%,%wtp-cls-two%,%wtp-uplk-bytes%,%wtp-dwnlk-bytes%,%wtp-uplk-pkts%,%wtp-dwnlk-pkts%,%wtp-uplk-bytes-retr%,%wtp-dwnlk-bytes-retr%,%wtp-uplk-pkts-retr%,%wtp-dwnlk-pkts-retr%,%wtp-invk-pkts%,%wtp-invk-tcl-zero%,%wtp-invk-tcl-one%,%wtp-invk-tcl-two%,%wtp-invk-tid-new%,%wtp-rslt-pkts%,%wtp-ack-to-resp%,%wtp-ack-to-init%,%wtp-abrt-to-resp%,%wtp-abrt-to-init%,%wtp-seg-invk%,%wtp-seg-rslt%,%wtp-neg-ack%,%wtp-tid-vrf%,%wtp-noninit-invk%,%wtp-unk-pdu%,%wsp-flows%,%wsp-flows-cur%,%wsp-co-conn%,%wsp-cl-conn%,%wsp-uplk-bytes%,%wsp-dwnlk-bytes%,%wsp-uplk-pkts%,%wsp-dwnlk-pkts%,%wsp-uplk-bytes-retr%,%wsp-dwnlk-bytes-retr%,%wsp-uplk-pkts-retr%,%wsp-dwnlk-pkts-retr%,%wsp-co-req-succ%,%wsp-co-req-fail%,%wsp-cl-req-succ%,%wsp-cl-req-fail%,%wsp-conn-pdu%,%wsp-conn-rep%,%wsp-redir%,%wsp-disc%,%wsp-susp%,%wsp-resm%,%wsp-opt%,%wsp-head%,%wsp-del%,%wsp-trace%,%wsp-reply%,%wsp-put%,%wsp-get%,%wsp-push%,%wsp-conf-push%,%wsp-post%,%wsp-data-frag%,%wsp-rsrvd%,%wsp-inv-pkts%,%mms-send%,%mms-send-succ%,%mms-send-fail%,%mms-retrv%,%mms-retrv-succ%,%mms-retrv-fail%,%mms-uplk-bytes%,%mms-dwnlk-bytes%,%mms-uplk-pkts%,%mms-dwnlk-pkts%,%mms-uplk-bytes-retr%,%mms-dwnlk-bytes-retr%,%mms-uplk-pkts-retr%,%mms-dwnlk-pkts-retr%,%mms-snd-req%,%mms-snd-conf%,%mms-ntf-ind%,%mms-ntf-ind-imm%,%mms-ntf-ind-del%,%mms-ntf-rsp%,%mms-retrv-conf%,%mms-ack-ind%,%mms-delvry-ind%,%mms-unk-pdu%,%mms-inv-pkts%,%sip-flows%,%sip-flows-cur%,%sip-calls%,%sip-uplk-bytes%,%sip-dwnlk-bytes%,%sip-uplk-pkts%,%sip-dwnlk-pkts%,%sip-uplk-bytes-retr%,%sip-dwnlk-bytes-retr%,%sip-uplk-pkts-retr%,%sip-dwnlk-pkts-retr%,%sip-invite%,%sip-bye%,%sip-ack%,%sip-cancel%,%sip-register%,%sip-inv-pkts%,%rtsp-flows%,%rtsp-flows-cur%,%rtsp-sess%,%rtsp-uplk-bytes%,%rtsp-dwnlk-bytes%,%rtsp-uplk-pkts%,%rtsp-dwnlk-pkts%,%rtsp-uplk-bytes-retr%,%rtsp-dwnlk-bytes-retr%,%rtsp-uplk-pkts-retr%,%rtsp-dwnlk-pkts-retr%,%rtsp-play%,%rtsp-setup%,%rtsp-pause%,%rtsp-record%,%rtsp-option%,%rtsp-redir%,%rtsp-desc%,%rtsp-announ%,%rtsp-trdwn%,%rtsp-get-param%,%rtsp-set-param%,%rtsp-inv-pkts%
> ECS2Sch | ECS2 Schema | EMS,ECS2,%date%,%time%,%rtp-flows%,%rtp-flows-cur%,%rtp-uplk-bytes%,%rtp-dwnlk-bytes%,%rtp-uplk-pkts%,%rtp-dwnlk-pkts%,%ftp-flows%,%ftp-flows-cur%,%ftp-uplk-bytes%,%ftp-dwnlk-bytes%,%ftp-uplk-pkts%,%ftp-dwnlk-pkts%,%ftp-retr%,%ftp-stor%,%ftp-inv-pkts%,%smtp-flows%,%smtp-flows-cur%,%smtp-uplk-bytes%,%smtp-dwnlk-bytes%,%smtp-uplk-pkts%,%smtp-dwnlk-pkts%,%smtp-uplk-bytes-retr%,%smtp-dwnlk-bytes-retr%,%smtp-uplk-pkts-retr%,%smtp-dwnlk-pkts-retr%,%smtp-unk-cmd%,%smtp-unk-resp%,%smtp-req-succ%,%smtp-req-fail%,%smtp-helo%,%smtp-ehlo%,%smtp-mail-frm%,%smtp-rcpt-to%,%smtp-data%,%smtp-bdat%,%smtp-vrfy%,%smtp-expn%,%smtp-noop%,%smtp-rset%,%smtp-quit%,%smtp-inv-pkts%,%pop3-flows%,%pop3-flows-cur%,%pop3-uplk-bytes%,%pop3-dwnlk-bytes%,%pop3-uplk-pkts%,%pop3-dwnlk-pkts%,%pop3-uplk-bytes-retr%,%pop3-dwnlk-bytes-retr%,%pop3-uplk-pkts-retr%,%pop3-dwnlk-pkts-retr%,%pop3-retr%,%pop3-retr-succ%,%pop3-list%,%pop3-list-succ%,%pop3-inv-pkts%,%imap-uplk-bytes%,%imap-dwnlk-bytes%,%imap-uplk-pkts%,%imap-dwnlk-pkts%,%imap-uplk-bytes-retr%,%imap-dwnlk-bytes-retr%,%imap-uplk-pkts-retr%,%imap-dwnlk-pkts-retr%,%imap-req-succ%,%imap-req-fail%,%imap-reply-untag%,%imap-reply-commcont%,%imap-unk-command%,%imap-unk-reply%,%p2p-flows%,%p2p-flows-cur%,%p2p-skype-uplnk-bytes%,%p2p-skype-dwlnk-bytes%,%p2p-skype-uplnk-pkts%,%p2p-skype-dwlnk-pkts%,%p2p-bittorrent-uplnk-bytes%,%p2p-bittorrent-dwlnk-bytes%,%p2p-bittorrent-uplnk-pkts%,%p2p-bittorrent-dwlnk-pkts%,%p2p-edonkey-uplnk-bytes%,%p2p-edonkey-dwlnk-bytes%,%p2p-edonkey-uplnk-pkts%,%p2p-edonkey-dwlnk-pkts%,%p2p-msn-uplnk-bytes%,%p2p-msn-dwlnk-bytes%,%p2p-msn-uplnk-pkts%,%p2p-msn-dwlnk-pkts%,%p2p-yahoo-uplnk-bytes%,%p2p-yahoo-dwlnk-bytes%,%p2p-yahoo-uplnk-pkts%,%p2p-yahoo-dwlnk-pkts%
> ECS3Sch | ECS3 Schema | EMS,ECS3,%date%,%time%,%p2p-orb-uplnk-bytes%,%p2p-orb-dwlnk-bytes%,%p2p-orb-uplnk-pkts%,%p2p-orb-dwlnk-pkts%,%p2p-winny-uplnk-bytes%,%p2p-winny-dwlnk-bytes%,%p2p-winny-uplnk-pkts%,%p2p-winny-dwlnk-pkts%,%p2p-slingbox-uplnk-bytes%,%p2p-slingbox-dwlnk-bytes%,%p2p-slingbox-uplnk-pkts%,%p2p-slingbox-dwlnk-pkts%,%p2p-fasttrack-uplnk-bytes%,%p2p-fasttrack-dwlnk-bytes%,%p2p-fasttrack-uplnk-pkts%,%p2p-fasttrack-dwlnk-pkts%,%p2p-gnutella-uplnk-bytes%,%p2p-gnutella-dwlnk-bytes%,%p2p-gnutella-uplnk-pkts%,%p2p-gnutella-dwlnk-pkts%,%p2p-jabber-uplnk-bytes%,%p2p-jabber-dwlnk-bytes%,%p2p-jabber-uplnk-pkts%,%p2p-jabber-dwlnk-pkts%,%ecs-ttlsuccess%,%ecs-ttlfail%,%ecs-curactive%,%ecs-15peak-curactive%,%ecs-ruleshit%,%ecs-ttldlinkbytes%,%ecs-ttlulinkbytes%,%ecs-ttldlinkpackets%,%ecs-ttlulinkpackets%,%ecs-ttlflowconn%,%ecs-ttlflowdisc%,%ecs-curflow%,%ecs-15peak-curflow%,%ecs-15min-usage-flowall%,%dns-dwnlk-bytes%,%dns-dwnlk-pkts%,%dns-flows%,%dns-flows-cur%,%dns-inv-pkts%,%dns-over-tcp-dwnlk-bytes%,%dns-over-tcp-dwnlk-pkts%,%dns-over-tcp-uplk-bytes%,%dns-over-tcp-uplk-pkts%,%dns-req-a-query%,%dns-req-cname-query%,%dns-req-ns-query%,%dns-req-ptr-query%,%dns-req-unknown-query%,%dns-rsp-a-query%,%dns-rsp-cname-query%,%dns-rsp-ns-query%,%dns-rsp-ptr-query%,%dns-rsp-unknown-query%,%dns-unk-opcode%,%dns-uplk-bytes%,%dns-uplk-pkts%,%icmp-inv-pkts%,%p2p-applejuice-dwlnk-bytes%,%p2p-applejuice-dwlnk-pkts%,%p2p-applejuice-uplnk-bytes%,%p2p-applejuice-uplnk-pkts%,%p2p-ares-dwlnk-bytes%,%p2p-ares-dwlnk-pkts%,%p2p-ares-uplnk-bytes%,%p2p-ares-uplnk-pkts%,%p2p-directconnect-dwlnk-bytes%,%p2p-directconnect-dwlnk-pkts%,%p2p-directconnect-uplnk-bytes%,%p2p-directconnect-uplnk-pkts%,%p2p-feidian-dwlnk-bytes%,%p2p-feidian-dwlnk-pkts%,%p2p-feidian-uplnk-bytes%,%p2p-feidian-uplnk-pkts%
> ECS4Sch | ECS4 Schema | EMS,ECS4,%date%,%time%,%p2p-filetopia-dwlnk-bytes%,%p2p-filetopia-dwlnk-pkts%,%p2p-filetopia-uplnk-bytes%,%p2p-filetopia-uplnk-pkts%,%p2p-gadugadu-dwlnk-bytes%,%p2p-gadugadu-dwlnk-pkts%,%p2p-gadugadu-uplnk-bytes%,%p2p-gadugadu-uplnk-pkts%,%p2p-imesh-dwlnk-bytes%,%p2p-imesh-dwlnk-pkts%,%p2p-imesh-uplnk-bytes%,%p2p-imesh-uplnk-pkts%,%p2p-manolito-dwlnk-bytes%,%p2p-manolito-dwlnk-pkts%,%p2p-manolito-uplnk-bytes%,%p2p-manolito-uplnk-pkts%,%p2p-msn-non-voice-dwlnk-bytes%,%p2p-msn-non-voice-dwlnk-pkts%,%p2p-msn-non-voice-uplnk-bytes%,%p2p-msn-non-voice-uplnk-pkts%,%p2p-msn-voice-dwlnk-bytes%,%p2p-msn-voice-dwlnk-pkts%,%p2p-msn-voice-uplnk-bytes%,%p2p-msn-voice-uplnk-pkts%,%p2p-mute-dwlnk-bytes%,%p2p-mute-dwlnk-pkts%,%p2p-mute-uplnk-bytes%,%p2p-mute-uplnk-pkts%,%p2p-pando-dwlnk-bytes%,%p2p-pando-dwlnk-pkts%,%p2p-pando-uplnk-bytes%,%p2p-pando-uplnk-pkts%,%p2p-pplive-dwlnk-bytes%,%p2p-pplive-dwlnk-pkts%,%p2p-pplive-uplnk-bytes%,%p2p-pplive-uplnk-pkts%,%p2p-ppstream-dwlnk-bytes%,%p2p-ppstream-dwlnk-pkts%,%p2p-ppstream-uplnk-bytes%,%p2p-ppstream-uplnk-pkts%,%p2p-qq-dwlnk-bytes%,%p2p-qq-dwlnk-pkts%,%p2p-qqlive-dwlnk-bytes%,%p2p-qqlive-dwlnk-pkts%,%p2p-qqlive-uplnk-bytes%,%p2p-qqlive-uplnk-pkts%,%p2p-qq-uplnk-bytes%,%p2p-qq-uplnk-pkts%,%p2p-skinny-dwlnk-bytes%,%p2p-skinny-dwlnk-pkts%,%p2p-skinny-uplnk-bytes%,%p2p-skinny-uplnk-pkts%,%p2p-skype-non-voice-dwlnk-bytes%,%p2p-skype-non-voice-dwlnk-pkts%,%p2p-skype-non-voice-uplnk-bytes%,%p2p-skype-non-voice-uplnk-pkts%,%p2p-skype-voice-dwlnk-bytes%,%p2p-skype-voice-dwlnk-pkts%,%p2p-skype-voice-uplnk-bytes%,%p2p-skype-voice-uplnk-pkts%,%p2p-sopcast-dwlnk-bytes%,%p2p-sopcast-dwlnk-pkts%,%p2p-sopcast-uplnk-bytes%,%p2p-sopcast-uplnk-pkts%,%p2p-soulseek-dwlnk-bytes%,%p2p-soulseek-dwlnk-pkts%,%p2p-soulseek-uplnk-bytes%
> ECS5Sch | ECS5 Schema | EMS,ECS5,%date%,%time%,%p2p-soulseek-uplnk-pkts%,%p2p-yahoo-non-voice-dwlnk-bytes%,%p2p-yahoo-non-voice-dwlnk-pkts%,%p2p-yahoo-non-voice-uplnk-bytes%,%p2p-yahoo-non-voice-uplnk-pkts%,%p2p-yahoo-voice-dwlnk-bytes%,%p2p-yahoo-voice-dwlnk-pkts%,%p2p-yahoo-voice-uplnk-bytes%,%p2p-yahoo-voice-uplnk-pkts%,%p2p-zattoo-dwlnk-bytes%,%p2p-zattoo-dwlnk-pkts%,%p2p-zattoo-uplnk-bytes%,%p2p-zattoo-uplnk-pkts%
> IPSGSch | IPSG Schema | EMS,IPSG,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%rad-servaddr%,%rad-servport%,%total-start-req-rcv%,%total-interim-update-req-rcv%,%total-stop-req-rcv%,%total-unknown-req-rcv%,%total-rsp-sent%,%total-start-req-retrans-rcv%,%total-start-rsp-sent%,%total-discard-msgs-unknown-clnt%,%total-discard-msgs-ignore-interim%,%total-discard-msgs-ignore-stop%,%total-discard-msgs-incorrect-secret%,%total-discard-msgs-attr-missing%
> ASNGW1Sch | ASNGW1 Schema | EMS,ASNGW1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%peeripaddr%,%r6mspreattreq-totsent%,%r6mspreattreq-retranssent%,%r6mspreattreq-totrec%,%r6mspreattreq-totacc%,%r6mspreattreq-totdenied%,%r6mspreattreq-totdiscard%,%r6mspreattreq-badform%,%r6mspreattreq-decodeerr%,%r6mspreattreq-unspecerr%,%r6mspreattreq-missmandtlv%,%r6mspreattreq-tlvvalinval%,%r6mspreattreq-unknowntlv%,%r6mspreattreq-duptlvfound%,%r6mspreattreq-nosessfound%,%r6mspreattreq-transiderr%,%r6mspreattrsp-totsent%,%r6mspreattrsp-retranssent%,%r6mspreattrsp-totrec%,%r6mspreattrsp-totacc%,%r6mspreattrsp-totdenied%,%r6mspreattrsp-totdiscard%,%r6mspreattrsp-badform%,%r6mspreattrsp-decodeerr%,%r6mspreattrsp-unspecerr%,%r6mspreattrsp-missmandtlv%,%r6mspreattrsp-tlvvalinval%,%r6mspreattrsp-unknowntlv%,%r6mspreattrsp-duptlvfound%,%r6mspreattrsp-nosessfound%,%r6mspreattrsp-transiderr%,%r6mspreattack-totsent%,%r6mspreattack-retranssent%,%r6mspreattack-totrec%,%r6mspreattack-totacc%,%r6mspreattack-totdenied%,%r6mspreattack-totdiscard%,%r6mspreattack-badform%,%r6mspreattack-decodeerr%,%r6mspreattack-unspecerr%,%r6mspreattack-missmandtlv%,%r6mspreattack-tlvvalinval%,%r6mspreattack-unknowntlv%,%r6mspreattack-duptlvfound%,%r6mspreattack-nosessfound%,%r6mspreattack-transiderr%,%r6contextreq-totsent%,%r6contextreq-retranssent%,%r6contextreq-totrec%,%r6contextreq-totacc%,%r6contextreq-totdenied%,%r6contextreq-totdiscard%,%r6contextreq-badform%,%r6contextreq-decodeerr%,%r6contextreq-unspecerr%,%r6contextreq-missmandtlv%,%r6contextreq-tlvvalinval%,%r6contextreq-unknowntlv%,%r6contextreq-duptlvfound%,%r6contextreq-nosessfound%,%r6contextreq-transiderr%,%r6contextrepo-totsent%,%r6contextrepo-retranssent%,%r6contextrepo-totrec%,%r6contextrepo-totacc%,%r6contextrepo-totdenied%,%r6contextrepo-totdiscard%
> ASNGW2Sch | ASNGW2 Schema | EMS,ASNGW2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%peeripaddr%,%r6contextrepo-badform%,%r6contextrepo-decodeerr%,%r6contextrepo-unspecerr%,%r6contextrepo-missmandtlv%,%r6contextrepo-tlvvalinval%,%r6contextrepo-unknowntlv%,%r6contextrepo-duptlvfound%,%r6contextrepo-nosessfound%,%r6contextrepo-transiderr%,%r6contextack-totsent%,%r6contextack-retranssent%,%r6contextack-totrec%,%r6contextack-totacc%,%r6contextack-totdenied%,%r6contextack-totdiscard%,%r6contextack-badform%,%r6contextack-decodeerr%,%r6contextack-unspecerr%,%r6contextack-missmandtlv%,%r6contextack-tlvvalinval%,%r6contextack-unknowntlv%,%r6contextack-duptlvfound%,%r6contextack-nosessfound%,%r6contextack-transiderr%,%r6autheaptra-totsent%,%r6autheaptra-retranssent%,%r6autheaptra-totrec%,%r6autheaptra-totacc%,%r6autheaptra-totdenied%,%r6autheaptra-totdiscard%,%r6autheaptra-badform%,%r6autheaptra-decodeerr%,%r6autheaptra-unspecerr%,%r6autheaptra-missmandtlv%,%r6autheaptra-tlvvalinval%,%r6autheaptra-unknowntlv%,%r6autheaptra-duptlvfound%,%r6autheaptra-nosessfound%,%r6autheaptra-transiderr%,%r6autheaptra-outofordrcd%,%r6autheapsta-totrec%,%r6autheapsta-totacc%,%r6autheapsta-totdenied%,%r6autheapsta-totdiscard%,%r6autheapsta-badform%,%r6autheapsta-decodeerr%,%r6autheapsta-unspecerr%,%r6autheapsta-missmandtlv%,%r6autheapsta-tlvvalinval%,%r6autheapsta-unknowntlv%,%r6autheapsta-duptlvfound%,%r6autheapsta-nosessfound%,%r6autheapsta-transiderr%,%r6autheapsta-outofordrcd%,%r6autheapsta-noresourcedrop%,%r6autheapsta-bsinireauth%,%r6msattreq-totsent%,%r6msattreq-retranssent%,%r6msattreq-totrec%,%r6msattreq-totacc%,%r6msattreq-totdenied%,%r6msattreq-totdiscard%,%r6msattreq-badform%,%r6msattreq-decodeerr%,%r6msattreq-unspecerr%,%r6msattreq-missmandtlv%,%r6msattreq-tlvvalinval%,%r6msattreq-unknowntlv%
> ASNGW3Sch | ASNGW3 Schema | EMS,ASNGW3,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%peeripaddr%,%r6msattreq-duptlvfound%,%r6msattreq-nosessfound%,%r6msattreq-transiderr%,%r6msattrsp-totsent%,%r6msattrsp-retranssent%,%r6msattrsp-totrec%,%r6msattrsp-totacc%,%r6msattrsp-totdenied%,%r6msattrsp-totdiscard%,%r6msattrsp-badform%,%r6msattrsp-decodeerr%,%r6msattrsp-unspecerr%,%r6msattrsp-missmandtlv%,%r6msattrsp-tlvvalinval%,%r6msattrsp-unknowntlv%,%r6msattrsp-duptlvfound%,%r6msattrsp-nosessfound%,%r6msattrsp-transiderr%,%r6msattack-totsent%,%r6msattack-retranssent%,%r6msattack-totrec%,%r6msattack-totacc%,%r6msattack-totdenied%,%r6msattack-totdiscard%,%r6msattack-badform%,%r6msattack-decodeerr%,%r6msattack-unspecerr%,%r6msattack-missmandtlv%,%r6msattack-tlvvalinval%,%r6msattack-unknowntlv%,%r6msattack-duptlvfound%,%r6msattack-nosessfound%,%r6msattack-transiderr%,%r6datapathregreq-totsent%,%r6datapathregreq-retranssent%,%r6datapathregreq-totrec%,%r6datapathregreq-totacc%,%r6datapathregreq-totdenied%,%r6datapathregreq-totdiscard%,%r6datapathregreq-badform%,%r6datapathregreq-decodeerr%,%r6datapathregreq-unspecerr%,%r6datapathregreq-missmandtlv%,%r6datapathregreq-tlvvalinval%,%r6datapathregreq-unknowntlv%,%r6datapathregreq-duptlvfound%,%r6datapathregreq-nosessfound%,%r6datapathregreq-transiderr%,%r6datapathregrsp-totsent%,%r6datapathregrsp-retranssent%,%r6datapathregrsp-totrec%,%r6datapathregrsp-totacc%,%r6datapathregrsp-totdenied%,%r6datapathregrsp-totdiscard%,%r6datapathregrsp-badform%,%r6datapathregrsp-decodeerr%,%r6datapathregrsp-unspecerr%,%r6datapathregrsp-missmandtlv%,%r6datapathregrsp-tlvvalinval%,%r6datapathregrsp-unknowntlv%,%r6datapathregrsp-duptlvfound%,%r6datapathregrsp-nosessfound%,%r6datapathregrsp-transiderr%,%r6datapathregack-totsent%
> ASNGW4Sch | ASNGW4 Schema | EMS,ASNGW4,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%peeripaddr%,%r6datapathregack-retranssent%,%r6datapathregack-totrec%,%r6datapathregack-totacc%,%r6datapathregack-totdenied%,%r6datapathregack-totdiscard%,%r6datapathregack-badform%,%r6datapathregack-decodeerr%,%r6datapathregack-unspecerr%,%r6datapathregack-missmandtlv%,%r6datapathregack-tlvvalinval%,%r6datapathregack-unknowntlv%,%r6datapathregack-duptlvfound%,%r6datapathregack-nosessfound%,%r6datapathregack-transiderr%,%r6datapathderegreq-totsent%,%r6datapathderegreq-retranssent%,%r6datapathderegreq-totrec%,%r6datapathderegreq-totacc%,%r6datapathderegreq-totdenied%,%r6datapathderegreq-totdiscard%,%r6datapathderegreq-badform%,%r6datapathderegreq-decodeerr%,%r6datapathderegreq-unspecerr%,%r6datapathderegreq-missmandtlv%,%r6datapathderegreq-tlvvalinval%,%r6datapathderegreq-unknowntlv%,%r6datapathderegreq-duptlvfound%,%r6datapathderegreq-nosessfound%,%r6datapathderegreq-transiderr%,%r6datapathderegrsp-totsent%,%r6datapathderegrsp-retranssent%,%r6datapathderegrsp-totrec%,%r6datapathderegrsp-totacc%,%r6datapathderegrsp-totdenied%,%r6datapathderegrsp-totdiscard%,%r6datapathderegrsp-badform%,%r6datapathderegrsp-decodeerr%,%r6datapathderegrsp-unspecerr%,%r6datapathderegrsp-missmandtlv%,%r6datapathderegrsp-tlvvalinval%,%r6datapathderegrsp-unknowntlv%,%r6datapathderegrsp-duptlvfound%,%r6datapathderegrsp-nosessfound%,%r6datapathderegrsp-transiderr%,%r6keychadir-totsent%,%r6keychadir-retranssent%,%r6keychadir-totrec%,%r6keychadir-totacc%,%r6keychadir-totdenied%,%r6keychadir-totdiscard%,%r6keychadir-badform%,%r6keychadir-decodeerr%,%r6keychadir-unspecerr%,%r6keychadir-missmandtlv%,%r6keychadir-tlvvalinval%,%r6keychadir-unknowntlv%,%r6keychadir-duptlvfound%,%r6keychadir-nosessfound%,%r6keychadir-transiderr%
> ASNGW5Sch | ASNGW5 Schema | EMS,ASNGW5,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%peeripaddr%,%r6keychaack-totsent%,%r6keychaack-retranssent%,%r6keychaack-totrec%,%r6keychaack-totacc%,%r6keychaack-totdenied%,%r6keychaack-totdiscard%,%r6keychaack-badform%,%r6keychaack-decodeerr%,%r6keychaack-unspecerr%,%r6keychaack-missmandtlv%,%r6keychaack-tlvvalinval%,%r6keychaack-unknowntlv%,%r6keychaack-duptlvfound%,%r6keychaack-nosessfound%,%r6keychaack-transiderr%,%r6unknown-totrec%,%r6unknown-totacc%,%r6unknown-totdenied%,%r6unknown-totdiscard%,%r6unknown-badform%,%r6unknown-decodeerr%,%r6unknown-unspecerr%,%r6unknown-missmandtlv%,%r6unknown-tlvvalinval%,%r6unknown-unknowntlv%,%r6unknown-duptlvfound%,%r6unknown-nosessfound%,%r6unknown-transiderr%,%r6datagrerec-totpackrec%,%r6datagrerec-prottyperrror%,%r6datagrerec-totbytrec%,%r6datagrerec-grekeyabs%,%r6datagrerec-grechkerr%,%r6datagrerec-invpacklen%,%r6datagrerec-nosessfou%,%r6datagrerec-unspecerr%,%r6datagresend-totpacksent%,%r6datagresend-senderr%,%r6datagresend-totbytsent%,%r6datagresend-unspeerr%
> SGSN1Sch | SGSN1 Schema | EMS,SGSN1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%3G-attached%,%2G-attached%,%3G-home-subscribers%,%2G-home-subscribers%,%3G-visiting-national%,%2G-visiting-national%,%3G-visiting-foreign%,%2G-visiting-foreign%,%pmm-connected%,%pmm-idle%,%3G-IMSI-Attch%,%2G-IMSI-Attch%,%3G-ptmsi-Attch%,%2G-ptmsi-Attch%,%3G-attach-accept%,%2G-attch-accept%,%3G-attach-complete%,%2G-attach-complete%,%3G-attach-reject%,%2G-attach-reject%,%3G-intra-rau%,%2G-intra-rau%,%3G-periodic-rau%,%2G-periodic-rau%,%3G-inter-sgsn-rau%,%2G-inter-sgsn-rau%,%3G-rau-complete%,%2G-rau-complete%,%3G-rau-reject%,%2G-rau-reject%,%3G-ms-init-detach%,%2G-ms-init-detach%,%3G-nw-init-detach%,%2G-nw-init-detach%,%3G-ms-init-detach-accept%,%2G-ms-init-detach-accept%,%3G-nw-init-detach-accept%,%2G-nw-init-detach-accept%,%3G-signalling-service-request%,%2G-signalling-service-request%,%3G-data-service-request%,%2G-data-service-request%,%3G-service-response%,%2G-service-response%,%3G-service-reject%,%2G-service-reject%,%3G-paging-request%,%2G-paging-request%,%3G-gmm-status-sent%,%2G-gmm-status-sent%,%3G-gmm-status-rcvd%,%2G-gmm-status-rcvd%,%3G-auth-cipher-request%,%2G-auth-cipher-request%,%3G-auth-cipher-response%,%2G-auth-cipher-response%,%3G-auth-cipher-reject%,%2G-auth-cipher-reject%,%3G-auth-cipher-mac-fail%,%2G-auth-cipher-mac-fail%,%3G-auth-cipher-syn-fail%,%2G-auth-cipher-syn-fail%,%3G-ptmsi-realloc%,%2G-ptmsi-realloc%,%3G-ptmsi-realloc-complete%,%2G-ptmsi-realloc-complete%,%3G-imsi-identity-request%,%2G-imsi-identity-request%,%3G-imeisv-identity-request%,%2G-imeisv-identity-request%,%3G-imsi-identity-response%,%2G-imsi-identity-response%,%3G-imeisv-identity-response%,%2G-imeisv-identity-response%,%3G-unknown-identity-response%,%2G-unknown-identity-response%
> SGSN2Sch | SGSN2 Schema | EMS,SGSN2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%common-id-sent%,%sec-mode-command%,%sec-mode-complete%,%sec-mode-reject%,%Iu-release-request%,%Iu-release-command%,%Iu-release-complete%,%Reset-received%,%Retransmitted-reset-received%,%Reset-Ack-sent%,%Reset-sent%,%Retransmitted-reset-sent%,%Reset-Ack-received%,%Resource-reset-received%,%Resource-reset-ack-sent%,%Resource-reset-sent%,%Resource-reset-ack-received%,%Error-indication-rcvd%,%Relocation-required%,%Relocation-command%,%Relocation-request%,%Relocation-request-ack%,%Relocation-failure%,%Relocation-prep-failure%,%Relocation-cancel%,%Relocation-cancel-ack%,%Relocation-detect%,%Relocation-complete%,%Forward-srns-context%,%GMM-received-nas-pdu%,%GMM-sent-nas-pdu%,%SM-received-nas-pdu%,%SM-sent-nas-pdu%,%Unidentified-nas-pdu%,%3G-total-actv-req%,%3G-total-actv-accept%,%3G-ms-modify-req%,%3G-ms-modify-accept%,%3G-nw-modify-req%,%3G-nw-modify-accept%,%3G-ms-deactv-req%,%3G-ms-deactv-accept%,%3G-sgsn-init-deact-req%,%3G-sgsn-init-deact-acc%,%RNC-rab-modify-req%,%RNC-rab-rel-req%,%rab-assign-req%,%rab-assign-rsp%,%rab-set/mod-req%,%rab-set/mod-acc%,%rab-rel-req%,%rab-rel-accept%,%map-open-req-tx%,%map-open-req-rx%,%map-open-rsp-tx%,%map-open-rsp-rx%,%map-close-tx%,%map-close-rx%,%map-abort-tx%,%map-abort-rx%,%map-gprs-update-loc-req-tx%,%map-gprs-update-loc-rsp-tx%,%map-gprs-update-loc-err-tx%,%map-gprs-update-loc-timeouts-rx%,%map-cancel-loc-req-rx%,%map-cancel-loc-rsp-tx%,%map-cancel-loc-err-tx%,%map-del-subs-req-rx%,%map-del-subs-rsp-tx%,%map-del-subs-ret-tx%,%map-auth-timeouts-rcvd%,%map-purge-timeouts-rcvd%,%map-insert-subs-rcvd%,%map-standalone-isd-rcvd%,%map-isd-rsp-tx%,%map-isd-err-tx%,%map-auth-fail-rept-req-tx%,%map-auth-fail-rept-rsp-rx%,%map-auth-fail-rept-err-rx%
> SGSN3Sch | SGSN3 Schema | EMS,SGSN3,%date%,%time%,%vpnname%,%vpnid%,%servname%,%map-auth-fail-rept-timeouts-rcvd%,%map-hlr-reset-rcvd%,%tcap-total-active-trans%,%tcap-total-active-invoks%,%tcap-total-msg-drops%,%tcap-total-msg-rcvd%,%tcap-total-msg-sent%,%tcap-total-abort-rcvd%,%tcap-total-abort-sent%,%tcap-total-comp-rx%,%tcap-total-comp-tx%,%tcap-comp-reterr-rx%,%tcap-comp-reterr-tx%,%tcap-comp-retrej-rx%,%tcap-comp-retrej-tx%,%tcap-tran-incorrect-rx%,%tcap-tran-incorrect-tx%,%tcap-tran-badformed-rx%,%tcap-tran-badformed-tx%,%tcap-tran-unrecognised-rx%,%tcap-tran-unrecognised-tx%,%tcap-comp-incorrect-rx%,%tcap-comp-incorrect-tx%,%tcap-comp-badformed-rx%,%tcap-comp-badformed-tx%,%tcap-comp-unrec-invid-res-rx%,%tcap-comp-unrec-invid-res-tx%,%tcap-comp-unexp-res-rx%,%tcap-comp-unexp-res-tx%,%tcap-user-unrec-opcode-rx%,%tcap-user-unrec-opcode-tx%,%tcap-user-incorr-params-rx%,%tcap-user-incorr-params-tx%,%tcap-user-resourcelimit-rx%,%tcap-user-resourcelimit-tx%,%rab-set/mod-tmr-expired%,%rab-rel-tmr-expired%,%3G-rau-accept-intra%,%3G-rau-accept-inter%,%2G-rau-accept-intra%,%2G-rau-accept-inter%,%3G-attached-with-pdp%,%3G-attached-no-pdp%,%3G-gmm-info-sent%,%2G-gmm-info-sent%,%3G-auth-cipher-rsp-sres-mismatch%,%2G-auth-cipher-rsp-sres-mismatch%,%3G-auth-unacceptable%,%2G-auth-unacceptable%,%3G-imei-identity-request%,%2G-imei-identity-request%,%3G-imei-identity-response%,%2G-imei-identity-response%,%Initial-UE-Rcvd%,%Direct-Trans-Rcvd%,%Error-indication-sent%,%3G-total-num-actv-pdp%,%3G-primary-actv-req%,%3G-primary-actv-accept%,%3G-primary-actv-reject%,%3G-secondary-actv-req%,%3G-secondary-actv-acc%,%3G-secondary-actv-rej%,%3G-dupl-ti-pdpactive%,%3G-dupl-nsapi-pdpactv%,%3G-dupl-pdpaddr-apn-pdpactv%,%3G-dupl-ti-n-pdpactive%,%3G-dupl-pdpaddr-apn-n-pdpactv%,%3G-ms-modify-rej%,%3G-nw-modify-rej%,%3G-ms-deactv-reject%
> SGSN4Sch | SGSN4 Schema | EMS,SGSN4,%date%,%time%,%vpnname%,%vpnid%,%servname%,%3G-sgsn-init-deact-rej%,%3G-total-sm-status-req-rx%,%3G-total-sm-status-req-tx%,%RNC-rab-modify-num%,%RNC-rab-rel-num%,%rab-set/mod-fail%,%rab-rel-fail%,%rab-queued%,%total-rab-rej%,%SRNS-ctxt-req-sent%,%SRNS-ctxt-rsp-rcvd%,%SRNS-ctxt-req-tmr-expired%,%SRNS-ctxt-total-pdp-acc%,%SRNS-ctxt-total-pdp-rej%,%SRNS-data-fwd-cmd-sent%,%map-auth-req-tx%,%map-auth-succes%,%map-auth-fail%,%map-imei-req-tx%,%map-imei-succes%,%map-imei-fail%,%map-imei-timeout%,%map-purge-req-tx%,%map-purge-success%,%map-purge-fail%,%tcap-uni-dir-msg-rcvd%,%tcap-uni-dir-msg-sent%,%tcap-begin-msg-rcvd%,%tcap-begin-msg-sent%,%tcap-continue-msg-rcvd%,%tcap-continue-msg-sent%,%tcap-end-msg-rcvd%,%tcap-end-msg-sent%,%tcap-total-comp-invoke-rx%,%tcap-total-comp-invoke-tx%,%tcap-comp-retresult-rx%,%tcap-comp-retresult-tx%,%tcap-tran-unrec-msgtype-rx%,%tcap-tran-unrec-msgtype-tx%,%tcap-tran-resource-limit-rx%,%tcap-tran-resource-limit-tx%,%tcap-comp-unrecognised-rx%,%tcap-comp-unrecognised-tx%,%tcap-comp-unrec-linkid-rx%,%tcap-comp-unrec-linkid-tx%,%tcap-comp-unrec-invid-err-rx%,%tcap-comp-unrec-invid-err-tx%,%tcap-comp-unexp-err-rx%,%tcap-comp-unexp-err-tx%,%tcap-user-duplicate-invid-rx%,%tcap-user-duplicate-invid-tx%,%tcap-user-unexp-linked-resp-rx%,%tcap-user-unexp-linked-resp-tx%,%tcap-user-unexp-linked-oper-rx%,%tcap-user-unexp-linked-oper-tx%,%tcap-user-res-incorr-params-rx%,%tcap-user-res-incorr-params-tx%,%tcap-user-res-unrec-errcode-rx%,%tcap-user-res-unrec-errcode-tx%,%tcap-user-res-unexp-errcode-rx%,%tcap-user-res-unexp-errcode-tx%,%tcap-user-err-incorr-params-rx%,%tcap-user-err-incorr-params-tx%,%tcap-user-initiate-release-rx%,%tcap-user-initiate-release-tx%,%3G-dupl-nsapi-n-pdpactv%,%Direct-Trans-Sent%,%3G-T3350-expiry%
> SGSN5Sch | SGSN5 Schema | EMS,SGSN5,%date%,%time%,%vpnname%,%vpnid%,%servname%,%2G-T3350-expiry%,%3G-T3360-expiry%,%2G-T3360-expiry%,%3G-T3370-expiry%,%2G-T3370-expiry%,%3G-T3322-expiry%,%2G-T3322-expiry%,%3G-T3313-expiry%,%2G-T3313-expiry%,%mcc%,%mnc%,%lac%,%rac%,%2G-local-ptmsi-Attch%,%2G-paging-success%,%2G-remote-ptmsi-Attch%,%3G-actv-rej-apn-restriction-incompatible%,%3G-actv-rej-by-ggsn%,%3G-actv-rej-conditional-ie-err%,%3G-actv-rej-ie-non-existent%,%3G-actv-rej-insufficient-resources%,%3G-actv-rej-invalid-mandatory-info%,%3G-actv-rej-missing-or-unknown-apn%,%3G-actv-rej-msg-not-compatible-with-prot-state%,%3G-actv-rej-msg-type-non-existent%,%3G-actv-rej-network-failure%,%3G-actv-rej-odb%,%3G-actv-rej-pdp-notft-actv%,%3G-actv-rej-prot-err-unspecified%,%3G-actv-rej-recovery-on-timer-expiry%,%3G-actv-rej-semantically-incorrect%,%3G-actv-rej-semantic-err-in-pkt-filter%,%3G-actv-rej-semantic-error-tft-operation%,%3G-actv-rej-service-not-subscribed%,%3G-actv-rej-service-not-supported%,%3G-actv-rej-svc-opt-tmp-out-of-order%,%3G-actv-rej-syntax-err-in-pkt-filter%,%3G-actv-rej-syntax-err-in-tft-operation%,%3G-actv-rej-unknown-pdp-addr-type%,%3G-actv-rej-unknown-pdp-context%,%3G-actv-rej-unspecified-error%,%3G-actv-rej-usr-auth-failed%,%3G-attach-rej-congestion%,%3G-attach-rej-illegal-me%,%3G-attach-rej-illegal-ms%,%3G-attach-rej-implicitly-detach%,%3G-attach-rej-imsi-unknown-at-hlr%,%3G-attach-rej-network-failure%,%3G-attach-rej-plmn-not-allowed%,%3G-attach-rej-unknown-cause%,%3G-detached%,%3G-ggsn-init-deact-acc%,%3G-ggsn-init-deact-rej%,%3G-ggsn-init-deact-req%,%3G-gprs-and-non-gprs-service-not-allowed%,%3G-gprs-service-not-allowed%,%3G-gprs-service-not-allowed-in-this-plmn%,%3G-hlr-init-deact-acc%,%3G-hlr-init-deact-rej%,%3G-hlr-init-deact-req%,%3G-local-ptmsi-Attch%
> SGSN6Sch | SGSN6 Schema | EMS,SGSN6,%date%,%time%,%vpnname%,%vpnid%,%servname%,%3G-no-suitable-cells-in-location-area%,%3G-paging-success%,%3G-total-attach-req%,%exist-conn-proc-rej-overload%,%new-connection-rejected-overload%,%3G-total-actv-pdp-with-dir-tunnel%,%3G-remote-ptmsi-Attch%,%3G-roaming-not-allowed-in-this-location-area%,%3G-inter-rau-reject%,%3G-total-inter-rau-failure%,%3G-rau-accept-periodic%,%3G-periodic-rau-reject%,%3G-total-periodic-rau-failure%,%3G-intra-rau-reject%,%3G-total-intra-rau-failure%,%3G-total-attach-fail%,%3G-total-actv-reject%,%3G-total-actv-fail%,%3G-intra-rau-rej-imsi-unknown-hlr%,%2G-intra-rau-rej-imsi-unknown-hlr%,%3G-intra-rau-rej-illegal-ms%,%2G-intra-rau-rej-illegal-ms%,%3G-intra-rau-rej-illegal-me%,%2G-intra-rau-rej-illegal-me%,%3G-intra-rau-rej-gprs-svc-not-allw%,%2G-intra-rau-rej-gprs-svc-not-allw%,%3G-intra-rau-rej-nongprs-svc-not-allow%,%2G-intra-rau-rej-nongprs-svc-not-allow%,%3G-intra-rau-rej-msid-not-derived-by-nw%,%2G-intra-rau-rej-msid-not-derived-by-nw%,%3G-intra-rau-rej-implicitly-detach%,%2G-intra-rau-rej-implicitly-detach%,%3G-intra-rau-rej-plmn-not-allowed%,%2G-intra-rau-rej-plmn-not-allowed%,%3G-intra-rau-rej-loc-area-not-allow%,%2G-intra-rau-rej-loc-area-not-allow%,%3G-intra-rau-rej-roam-not-allow-larea%,%2G-intra-rau-rej-roam-not-allow-larea%,%3G-intra-rau-rej-gprs-svc-not-allow-plmn%,%2G-intra-rau-rej-gprs-svc-not-allow-plmn%,%3G-intra-rau-rej-no-cells-in-loc-area%,%2G-intra-rau-rej-no-cells-in-loc-area%,%3G-intra-rau-rej-msc-not-reachable%,%2G-intra-rau-rej-msc-not-reachable%,%3G-intra-rau-rej-network-failure%,%2G-intra-rau-rej-network-failure%,%3G-intra-rau-rej-mac-failure%,%2G-intra-rau-rej-mac-failure%,%3G-intra-rau-rej-syn-failure%,%2G-intra-rau-rej-syn-failure%,%3G-intra-rau-rej-congestion%,%2G-intra-rau-rej-congestion%
> SGSN7Sch | SGSN7 Schema | EMS,SGSN7,%date%,%time%,%vpnname%,%vpnid%,%servname%,%3G-intra-rau-rej-gsm-auth-unacceptable%,%2G-intra-rau-rej-gsm-auth-unacceptable%,%3G-intra-rau-rej-no-pdp-ctx-actv%,%2G-intra-rau-rej-no-pdp-ctx-actv%,%3G-intra-rau-rej-retry-from-new-cell%,%2G-intra-rau-rej-retry-from-new-cell%,%3G-intra-rau-rej-inval-mand-info%,%2G-intra-rau-rej-inval-mand-info%,%3G-intra-rau-rej-msg-type-non-exist%,%2G-intra-rau-rej-msg-type-non-exist%,%3G-intra-rau-rej-mtype-incompat-pstate%,%2G-intra-rau-rej-mtype-incompat-pstate%,%3G-intra-rau-rej-ie-non-existent%,%2G-intra-rau-rej-ie-non-existent%,%3G-intra-rau-rej-cond-ie-error%,%2G-intra-rau-rej-cond-ie-error%,%3G-intra-rau-rej-msg-incompat-prot-state%,%2G-intra-rau-rej-msg-incompat-prot-state%,%3G-intra-rau-rej-prot-error%,%2G-intra-rau-rej-prot-error%,%3G-intra-rau-rej-unknown-error%,%2G-intra-rau-rej-unknown-error%,%3G-intra-prau-rej-imsi-unknown-hlr%,%2G-intra-prau-rej-imsi-unknown-hlr%,%3G-intra-prau-rej-illegal-ms%,%2G-intra-prau-rej-illegal-ms%,%3G-intra-prau-rej-illegal-me%,%2G-intra-prau-rej-illegal-me%,%3G-intra-prau-rej-gprs-svc-not-allow%,%2G-intra-prau-rej-gprs-svc-not-allow%,%3G-intra-prau-rej-nongprs-svc-not-allow%,%2G-intra-prau-rej-nongprs-svc-not-allow%,%3G-intra-prau-rej-msid-not-derived-by-nw%,%2G-intra-prau-rej-msid-not-derived-by-nw%,%3G-intra-prau-rej-implicitly-detach%,%2G-intra-prau-rej-implicitly-detach%,%3G-intra-prau-rej-plmn-not-allowed%,%2G-intra-prau-rej-plmn-not-allowed%,%3G-intra-prau-rej-loc-area-not-allowed%,%2G-intra-prau-rej-loc-area-not-allowed%,%3G-intra-prau-rej-roam-not-allowed-larea%,%2G-intra-prau-rej-roam-not-allowed-larea%,%3G-intra-prau-rej-gprs-svc-not-allowed-plmn%,%2G-intra-prau-rej-gprs-svc-not-allowed-plmn%,%3G-intra-prau-rej-congestion%,%2G-intra-prau-rej-congestion%
> SGSN8Sch | SGSN8 Schema | EMS,SGSN8,%date%,%time%,%vpnname%,%vpnid%,%servname%,%3G-intra-prau-rej-gsm-auth-unacceptable%,%2G-intra-prau-rej-gsm-auth-unacceptable%,%3G-intra-prau-rej-no-pdp-ctx-actv%,%2G-intra-prau-rej-no-pdp-ctx-actv%,%3G-intra-prau-rej-retry-from-new-cell%,%2G-intra-prau-rej-retry-from-new-cell%,%3G-intra-prau-rej-sem-wrong-msg%,%2G-intra-prau-rej-sem-wrong-msg%,%3G-intra-prau-rej-inval-mand-info%,%2G-intra-prau-rej-inval-mand-info%,%3G-intra-prau-rej-msg-type-non-exist%,%2G-intra-prau-rej-msg-type-non-exist%,%3G-intra-prau-rej-mtype-incompat-pstate%,%2G-intra-prau-rej-mtype-incompat-pstate%,%3G-intra-prau-rej-ie-non-existent%,%2G-intra-prau-rej-ie-non-existent%,%3G-intra-prau-rej-cond-ie-error%,%2G-intra-prau-rej-cond-ie-error%,%3G-intra-prau-rej-msg-incompat-pstate%,%2G-intra-prau-rej-msg-incompat-pstate%,%3G-intra-prau-rej-prot-error%,%2G-intra-prau-rej-prot-error%,%3G-intra-prau-rej-unknown-error%,%2G-intra-prau-rej-unknown-error%,%3G-inter-rau-rej-imsi-unknown-hlr%,%2G-inter-rau-rej-imsi-unknown-hlr%,%3G-inter-rau-rej-illegal-ms%,%2G-inter-rau-rej-illegal-ms%,%3G-inter-rau-rej-illegal-me%,%2G-inter-rau-rej-illegal-me%,%3G-inter-rau-rej-gprs-svc-not-allow%,%2G-inter-rau-rej-gprs-svc-not-allow%,%3G-inter-rau-rej-nongprs-svc-not-allow%,%2G-inter-rau-rej-nongprs-svc-not-allow%,%3G-inter-rau-rej-msid-not-derived-by-nw%,%2G-inter-rau-rej-msid-not-derived-by-nw%,%3G-inter-rau-rej-implicitly-detach%,%2G-inter-rau-rej-implicitly-detach%,%3G-inter-rau-rej-plmn-not-allowed%,%2G-inter-rau-rej-plmn-not-allowed%,%3G-inter-rau-rej-loc-area-not-allowed%,%2G-inter-rau-rej-loc-area-not-allowed%,%3G-inter-rau-rej-roam-not-allowed-larea%,%2G-inter-rau-rej-roam-not-allowed-larea%,%3G-inter-rau-rej-gprs-svc-not-allowed-plmn%,%2G-inter-rau-rej-gprs-svc-not-allowed-plmn%
> SGSN9Sch | SGSN9 Schema | EMS,SGSN9,%date%,%time%,%vpnname%,%vpnid%,%servname%,%3G-inter-rau-rej-no-cells-in-location-area%,%2G-inter-rau-rej-no-cells-in-location-area%,%3G-inter-rau-rej-msc-not-reachable%,%2G-inter-rau-rej-msc-not-reachable%,%3G-inter-rau-rej-network-failure%,%2G-inter-rau-rej-network-failure%,%3G-inter-rau-rej-mac-failure%,%2G-inter-rau-rej-mac-failure%,%3G-inter-rau-rej-syn-failure%,%2G-inter-rau-rej-syn-failure%,%3G-inter-rau-rej-congestion%,%2G-inter-rau-rej-congestion%,%3G-inter-rau-rej-gsm-auth-unacceptable%,%2G-inter-rau-rej-gsm-auth-unacceptable%,%3G-inter-rau-rej-no-pdp-ctx-actv%,%2G-inter-rau-rej-no-pdp-ctx-actv%,%3G-inter-rau-rej-retry-from-new-cell%,%2G-inter-rau-rej-retry-from-new-cell%,%3G-inter-rau-rej-sem-wrong-msg%,%2G-inter-rau-rej-sem-wrong-msg%,%3G-inter-rau-rej-inval-mand-info%,%2G-inter-rau-rej-inval-mand-info%,%3G-inter-rau-rej-msg-type-non-exist%,%2G-inter-rau-rej-msg-type-non-exist%,%3G-inter-rau-rej-mtype-incompat-pstate%,%2G-inter-rau-rej-mtype-incompat-pstate%,%3G-inter-rau-rej-ie-non-existent%,%2G-inter-rau-rej-ie-non-existent%,%3G-inter-rau-rej-cond-ie-error%,%2G-inter-rau-rej-cond-ie-error%,%3G-inter-rau-rej-msg-not-compat-pstate%,%2G-inter-rau-rej-msg-not-compat-pstate%,%3G-inter-rau-rej-prot-error%,%2G-inter-rau-rej-prot-error%,%3G-inter-rau-rej-unknown-error%,%2G-inter-rau-rej-unknown-error%,%3G-intra-ra-upd-rau-fail-iu_release%,%3G-intra-ra-upd-rau-fail-ongoing-proc%,%2G-intra-ra-upd-rau-fail-ongoing-proc%,%3G-intra-perio-rau-fail-iu_release%,%3G-intra-perio-rau-fail-ongoing-proc%,%2G-intra-perio-rau-fail-ongoing-proc%,%3G-inter-rau-fail-iu_release%,%3G-inter-rau-fail-ongoing-proc%,%2G-inter-rau-fail-ongoing-proc%,%3G-attach-fail-iu_release%,%3G-attach-fail-ongoing-proc%,%2G-attach-fail-ongoing-proc%
> SGSNASch | SGSNA Schema | EMS,SGSNA,%date%,%time%,%vpnname%,%vpnid%,%servname%,%2G-total-attach-fail%,%3G-total-rau-failure%,%2G-total-rau-failure%,%2G-rau-accept-periodic%,%3G-ret-rau-accept-periodic%,%2G-ret-rau-accept-periodic%,%2G-intra-rau-reject%,%2G-periodic-rau-reject%,%2G-inter-rau-reject%,%2G-total-intra-rau-failure%,%2G-total-periodic-rau-failure%,%2G-total-inter-rau-failure%,%2G-total-actv-req%,%2G-total-actv-accept%,%2G-total-num-actv-pdp%,%2G-primary-actv-req%,%2G-primary-actv-accept%,%2G-total-actv-reject%,%2G-primary-actv-reject%,%2G-secondary-actv-req%,%2G-secondary-actv-acc%,%2G-secondary-actv-rej%,%2G-actv-rej-odb%,%2G-actv-rej-insufficient-resources%,%2G-actv-rej-network-failure%,%2G-actv-rej-missing-or-unknown-apn%,%2G-actv-rej-unknown-pdp-addr-type%,%2G-actv-rej-usr-auth-failed%,%2G-actv-rej-by-ggsn%,%2G-actv-rej-unspecified-error%,%2G-actv-rej-service-not-supported%,%2G-actv-rej-service-not-subscribed%,%2G-actv-rej-svc-opt-tmp-out-of-order%,%2G-actv-rej-apn-restriction-incompatible%,%2G-actv-rej-semantically-incorrect%,%2G-actv-rej-invalid-mandatory-info%,%2G-actv-rej-msg-type-non-existent%,%2G-actv-rej-ie-non-existent%,%2G-actv-rej-conditional-ie-err%,%2G-actv-rej-msg-not-compatible-with-prot-state%,%2G-actv-rej-recovery-on-timer-expiry%,%2G-actv-rej-prot-err-unspecified%,%2G-actv-rej-llc-sndcp-fail%,%2G-actv-rej-qos-not-acc%,%2G-actv-rej-semantic-error-tft-operation%,%2G-actv-rej-syntax-err-in-tft-operation%,%2G-actv-rej-unknown-pdp-context%,%2G-actv-rej-semantic-err-in-pkt-filter%,%2G-actv-rej-syntax-err-in-pkt-filter%,%2G-actv-rej-pdp-notft-actv%,%2G-dupl-ti-pdpactive%,%2G-dupl-nsapi-pdpactv%,%2G-dupl-pdpaddr-apn-pdpactv%,%2G-dupl-ti-n-pdpactive%,%2G-dupl-nsapi-n-pdpactv%,%2G-dupl-pdpaddr-apn-n-pdpactv%
> SGSNBSch | SGSNB Schema | EMS,SGSNB,%date%,%time%,%vpnname%,%vpnid%,%servname%,%2G-ms-modify-req%,%2G-ms-modify-accept%,%2G-ms-modify-rej%,%2G-nw-modify-req%,%2G-nw-ret-modify-req%,%2G-nw-modify-accept%,%2G-nw-modify-rej%,%2G-modify-rej-insufficient-resources%,%2G-modify-rej-service-opt-not-supported%,%2G-modify-rej-semantic-err-tft-operation%,%2G-modify-rej-syntax-err-tft-operation%,%2G-modify-rej-semnatic-err-pkt-filter%,%2G-modify-rej-syntax-err-pkt-filter%,%2G-modify-rej-semnatic-incorrect-message%,%2G-modify-rej-invalid-mand-info%,%2G-modify-rej-msg-non-existent%,%2G-modify-rej-ie-non-existent%,%2G-modify-rej-conditional-ie-err%,%2G-modify-rej-msg-not-compatible-prot-state%,%2G-modify-rej-rcvry-on-tmr-expiry%,%2G-modify-rej-prot-err-unspec%,%2G-ms-deactv-req%,%2G-ms-deactv-accept%,%2G-ms-deactv-reject%,%2G-ms-deactv-rej-rx-odb%,%2G-ms-deactv-rej-rx-mbms-cap-insuff-res%,%2G-ms-deactv-rej-rx-llc-sndcp-fail-gb%,%2G-ms-deactv-rej-rx-insuff-res%,%2G-ms-deactv-rej-rx-miss-unkwn-apn%,%2G-ms-deactv-rej-rx-unkwn-pdp-addr%,%2G-ms-deactv-rej-rx-usr-auth-fail%,%2G-ms-deactv-rej-rx-actv-rej-ggsn%,%2G-ms-deactv-rej-rx-actv-rej-unspec%,%2G-ms-deactv-rej-rx-service-opt-no-support%,%2G-ms-deactv-rej-rx-service-opt-no-subs%,%2G-ms-deactv-rej-rx-svc-opt-temp-out-order%,%2G-ms-deactv-rej-rx-nsapi-already-used%,%2G-ms-deactv-rej-rx-reg-deactv%,%2G-ms-deactv-rej-rx-qos-not-acc%,%2G-ms-deactv-rej-rx-nwt-fail%,%2G-ms-deactv-rej-rx-reactivation-req%,%2G-ms-deactv-rej-rx-no-feature-support%,%2G-ms-deactv-rej-rx-sem-err-tft-op%,%2G-ms-deactv-rej-rx-syn-err-tft-op%,%2G-ms-deactv-rej-rx-unknown-ctx%,%2G-ms-deactv-rej-rx-ctx-no-tft-already-actv%,%2G-ms-deactv-rej-rx-mcast-grp-mem-tout%,%2G-ms-deactv-rej-rx-sem-err-pkt-filter%,%2G-ms-deactv-rej-rx-syn-err-pkt-filter%,%2G-ms-deactv-rej-rx-invalid-trans-id%
> SGSNCSch | SGSNC Schema | EMS,SGSNC,%date%,%time%,%vpnname%,%vpnid%,%servname%,%2G-ms-deactv-rej-rx-sem-incorrect-msg%,%2G-ms-deactv-rej-rx-inval-mand-info%,%2G-ms-deactv-rej-rx-msg-non-existent%,%2G-ms-deactv-rej-rx-ie-non-existent%,%2G-ms-deactv-rej-rx-cond-ie-err%,%2G-ms-deactv-rej-rx-prot-err-unspec%,%2G-ms-deactv-rej-rx-apn-rest-incomap-actv-pdp%,%2G-ms-deactv-rej-rx-msg-not-compat-prot-state%,%2G-ms-deactv-rej-rx-rcvry-on-tmr-expiry%,%2G-sgsn-init-deact-req%,%2G-sgsn-init-deact-acc%,%2G-sgsn-init-deact-rej%,%2G-ggsn-init-deact-req%,%2G-ggsn-init-deact-acc%,%2G-ggsn-init-deact-rej%,%2G-hlr-init-deact-req%,%2G-hlr-init-deact-acc%,%2G-hlr-init-deact-rej%,%2G-nw-deactv-rej-tx-odb%,%2G-nw-deactv-rej-tx-mbms-cap-insuff-res%,%2G-nw-deactv-rej-tx-llc-sndcp-fail-gb%,%2G-nw-deactv-rej-tx-insuff-res%,%2G-nw-deactv-rej-tx-miss-unkwn-apn%,%2G-nw-deactv-rej-tx-unkwn-pdp-addr%,%2G-nw-deactv-rej-tx-usr-auth-fail%,%2G-nw-deactv-rej-tx-actv-rej-ggsn%,%2G-nw-deactv-rej-tx-actv-rej-unspec%,%2G-nw-deactv-rej-tx-service-opt-no-support%,%2G-nw-deactv-rej-tx-service-opt-no-subs%,%2G-nw-deactv-rej-tx-svc-opt-temp-out-order%,%2G-nw-deactv-rej-tx-nsapi-already-used%,%2G-nw-deactv-rej-tx-reg-deactv%,%2G-nw-deactv-rej-tx-qos-not-acc%,%2G-nw-deactv-rej-tx-nwt-fail%,%2G-nw-deactv-rej-tx-reactivation-req%,%2G-nw-deactv-rej-tx-no-feature-support%,%2G-nw-deactv-rej-tx-sem-err-tft-op%,%2G-nw-deactv-rej-tx-syn-err-tft-op%,%2G-nw-deactv-rej-tx-unknown-ctx%,%2G-nw-deactv-rej-tx-ctx-no-tft-already-actv%,%2G-nw-deactv-rej-tx-mcast-grp-mem-tout%,%2G-nw-deactv-rej-tx-sem-err-pkt-filter%,%2G-nw-deactv-rej-tx-syn-err-pkt-filter%,%2G-nw-deactv-rej-tx-invalid-trans-id%,%2G-nw-deactv-rej-tx-sem-incorrect-msg%,%2G-nw-deactv-rej-tx-inval-mand-info%,%2G-nw-deactv-rej-tx-msg-non-existent%,%2G-nw-deactv-rej-tx-ie-non-existent%
> SGSNDSch | SGSND Schema | EMS,SGSND,%date%,%time%,%vpnname%,%vpnid%,%servname%,%2G-nw-deactv-rej-tx-cond-ie-err%,%2G-nw-deactv-rej-tx-prot-err-unspec%,%2G-nw-deactv-rej-tx-apn-rest-incomap-actv-pdp%,%2G-nw-deactv-rej-tx-msg-not-compat-prot-state%,%2G-nw-deactv-rej-tx-rcvry-on-tmr-expiry%,%2G-total-sm-status-req-rx%,%2G-total-sm-status-req-tx%
> SGTPSch | SGTP Schema | EMS,SGTP,%date%,%time%,%vpn-name%,%vpn-id%,%service-name%,%sgtpc-cpc-req-v1-pri%,%sgtpc-cpc-req-v0-pri%,%sgtpc-cpc-req-sec%,%sgtpc-cpc-req-accept%,%sgtpc-cpc-rsp-v1-pri%,%sgtpc-cpc-rsp-v0-pri%,%sgtpc-cpc-rsp-sec%,%sgtpc-upc-req-v1-tx%,%sgtpc-upc-req-v0-tx%,%sgtpc-upc-req-v1-rx%,%sgtpc-upc-req-v0-rx%,%sgtpc-upc-req-accept-tx%,%sgtpc-upc-req-accept-rx%,%sgtpc-dpc-req-v1-tx%,%sgtpc-dpc-req-v0-tx%,%sgtpc-dpc-req-v1-rx%,%sgtpc-dpc-req-v0-rx%,%sgtpc-dpc-req-accept-tx%,%sgtpc-dpc-req-accept-rx%,%sgtpc-ident-req-v1-tx%,%sgtpc-ident-req-v0-tx%,%sgtpc-ident-req-v1-rx%,%sgtpc-ident-req-v0-rx%,%sgtpc-ident-req-accept-tx%,%sgtpc-ident-req-accept-rx%,%sgtpc-sgsn-ctxt-req-v1-tx%,%sgtpc-sgsn-ctxt-req-v0-tx%,%sgtpc-sgsn-ctxt-req-v1-rx%,%sgtpc-sgsn-ctxt-req-v0-rx%,%sgtpc-sgsn-ctxt-req-accept-tx%,%sgtpc-sgsn-ctxt-req-accept-rx%,%sgtpc-sgsn-ctxt-ack-accept-tx%,%sgtpc-sgsn-ctxt-ack-accept-rx%,%sgtpc-fwd-reloc-req-tx%,%sgtpc-fwd-reloc-req-rx%,%sgtpc-fwd-reloc-discard-tx%,%sgtpc-fwd-reloc-req-accept-tx%,%sgtpc-fwd-reloc-req-accept-rx%,%sgtpc-fwd-srnsctxt-req-tx%,%sgtpc-fwd-srnsctxt-req-rx%,%sgtpc-fwd-srnsctxt-discard-rx%,%sgtpc-fwd-srnsctxt-ack-tx%,%sgtpc-fwd-srnsctxt-ack-rx%,%sgtpc-fwd-reloc-compl-tx%,%sgtpc-fwd-reloc-compl-rx%,%sgtpc-reloc-cncl-req-tx%,%sgtpc-reloc-cncl-req-rx%,%sgtpc-reloc-cncl-req-accept-tx%,%sgtpc-reloc-cncl-req-accept-rx%,%sgtpc-v1-echo-req-tx%,%sgtpc-v1-echo-req-rx%,%sgtpc-v1-echo-rsp-tx%,%sgtpc-v1-echo-rsp-rx%,%sgtpu-ggsn-pkt-sent%,%sgtpu-rnc-pkt-sent%,%sgtpu-sgsn-pkt-sent%,%sgtpu-ggsn-pkt-rcvd%,%sgtpu-rnc-pkt-rcvd%,%sgtpu-sgsn-pkt-rcvd%,%sgtpu-echo-req-tx%,%sgtpu-echo-req-rx%,%sgtpu-echo-rsp-tx%,%sgtpu-echo-rsp-rx%,%sgtpu-ggsn-errind-sent%,%sgtpu-ggsn-errind-rcvd%,%sgtpu-rnc-errind-sent%,%sgtpu-rnc-errind-rcvd%,%sgtpu-total-active-ggsn%,%sgtpu-total-active-rnc%
> SGTP2Sch | SGTP2 Schema | EMS,SGTP2,%date%,%time%,%vpn-name%,%vpn-id%,%service-name%,%sgtpc-total-cpc-req%,%sgtpc-cpc-req-denied%,%sgtpc-total-upc-req%,%sgtpc-upc-req-denied-tx%,%sgtpc-upc-req-denied-rx%,%sgtpc-total-dpc-req%,%sgtpc-dpc-req-denied-tx%,%sgtpc-dpc-req-denied-rx%,%sgtpc-ident-req-denied-tx%,%sgtpc-ident-req-denied-rx%,%sgtpc-sgsn-ctxt-req-denied-tx%,%sgtpc-sgsn-ctxt-req-denied-rx%,%sgtpc-sgsn-ctxt-ack-denied-tx%,%sgtpc-sgsn-ctxt-ack-denied-rx%,%sgtpc-fwd-reloc-denied-tx%,%sgtpc-fwd-reloc-denied-rx%,%sgtpc-fwd-srnsctxt-ack-denied-tx%,%sgtpc-fwd-srnsctxt-ack-denied-rx%,%sgtpc-fwd-rel-compl-ack-accept-tx%,%sgtpc-fwd-rel-compl-ack-accept-rx%,%sgtpc-fwd-rel-compl-ack-denied-tx%,%sgtpc-fwd-rel-compl-ack-denied-rx%,%sgtpc-reloc-cncl-denied-tx%,%sgtpc-reloc-cncl-denied-rx%,%sgtpc-ver-not-supported-rx%,%sgtpc-ver-not-supported-tx%,%sgtpc-supp-extn-hdr-notif-rx%,%sgtpc-supp-extn-hdr-notif-tx%,%sgtpu-ggsn-byts-sent%,%sgtpu-rnc-byts-sent%,%sgtpu-sgsn-byts-sent%,%sgtpu-ggsn-byts-rcvd%,%sgtpu-ggsn-pkt-queued%,%sgtpu-ggsn-byts-queued%,%sgtpu-ggsn-pkt-queue-full%,%sgtpu-ggsn-byts-queue-full%,%sgtpu-ggsn-pkt-unkwn-sess%,%sgtpu-ggsn-byts-unkwn-sess%,%sgtpu-ggsn-pkt-suspended-st%,%sgtpu-ggsn-byts-suspended-st%,%sgtpu-ggsn-pkt-invalid-msg-length%,%sgtpu-ggsn-byts-invalid-msg-length%,%sgtpu-rnc-byts-rcvd%,%sgtpu-rnc-pkt-queued%,%sgtpu-rnc-byts-queued%,%sgtpu-rnc-pkt-queue-full%,%sgtpu-rnc-byts-queue-full%,%sgtpu-rnc-pkt-unkwn-sess%,%sgtpu-rnc-byts-unkwn-sess%,%sgtpu-rnc-pkt-sess-dealloc%,%sgtpu-rnc-byts-sess-dealloc%,%sgtpu-rnc-pkt-invalid-msg-length%,%sgtpu-rnc-byts-invalid-msg-length%,%sgtpu-rnc-pkt-source-ip-viol%,%sgtpu-rnc-byts-source-ip-viol%,%sgtpu-sgsn-byts-rcvd%,%sgtpu-sgsn-pkt-queued%,%sgtpu-sgsn-byts-queued%,%sgtpu-sgsn-pkt-queue-full%,%sgtpu-sgsn-byts-queue-full%
> SGTP3Sch | SGTP3 Schema | EMS,SGTP3,%date%,%time%,%vpn-name%,%vpn-id%,%service-name%,%sgtpu-sgsn-pkt-unkwn-sess%,%sgtpu-sgsn-byts-unkwn-sess%,%sgtpu-sgsn-pkt-iu-release%,%sgtpu-sgsn-byts-iu-release%,%sgtpu-sgsn-pkt-invalid-msg-length%,%sgtpu-sgsn-byts-invalid-msg-length%,%sgtpc-v0-echo-req-tx%,%sgtpc-v0-echo-req-rx%,%sgtpc-v0-echo-rsp-tx%,%sgtpc-v0-echo-rsp-rx%,%sgtpu-ggsn-pkt-sess-dealloc%,%sgtpu-ggsn-byts-sess-dealloc%,%sgtpu-ggsn-pkt-page-fail%,%sgtpu-ggsn-byts-page-fail%,%sgtpu-ggsn-pkt-v0-seq-num-nt-pres%,%sgtpu-ggsn-byts-v0-seq-num-nt-pres%,%sgtpu-rnc-pkt-rau-in-active-st%,%sgtpu-rnc-byts-rau_in_active-st%,%sgtpu-rnc-pkt-reg_in_rau%,%sgtpu-rnc-byts-reg_in_rau%,%sgtpu-rnc-pkt-suspended-st%,%sgtpu-rnc-byts-suspended-st%,%sgtpu-sgsn-pkt-inconsistent-tunnel-state%,%sgtpu-sgsn-byts-inconsistent-tunnel-state%,%sgtpu-sgsn-pkt-sess-dealloc%,%sgtpu-sgsn-byts-sess-dealloc%,%sgtpu-total-ggsn-pkt-drop%,%sgtpu-total-ggsn-byts-drop%,%sgtpu-total-sgsn-pkt-drop%,%sgtpu-total-sgsn-byts-drop%,%sgtpu-total-rnc-pkt-drop%,%sgtpu-total-rnc-byts-drop%,%sgtpu-ggsn-pkt-drop-suspend-dealloc-st%,%sgtpu-ggsn-byts-drop-suspend-dealloc-st%,%sgtpu-rnc-pkt-rau-in-active-reg-st%,%sgtpu-rnc-byts-rau_in_active-reg-st%,%sgtpu-rnc-pkt-drop-suspended-dealloc-st%,%sgtpu-rnc-byts-drop-suspended-dealloc-st%,%sgtpu-total-pkt-ctxt-preserved%,%sgtpu-total-byts-ctxt-preserved%,%sgtpc-paket-discarded%,%sgtpc-v1-retrnas-echo-req-tx%,%sgtpc-v0-retrnas-echo-req-tx%,%sgtpu-errors-payload-length-mismatch%,%sgtpu-rnc-byts-unknown-version%,%sgtpu-rnc-pkt-unknown-version%,%sgtpu-ggsn-byts-unknown-version%,%sgtpu-sgsn-byts-unknown-version%,%sgtpu-ggsn-pkt-unknown-version%,%sgtpu-sgsn-pkt-unknown-version%,%iups-service%,%rnc-address%,%ggsn-address%
> SCCPSch | SCCP Schema | EMS,SCCP,%date%,%time%,%sccp-nw-id%,%ssa-txed%,%ss-oos-grant-txed%,%ss-oos-req-txed%,%ssp-txed%,%ss-status-test-txed%,%ssa-rcvd%,%ss-oos-grant-rcvd%,%ss-oos-req-rcvd%,%ss-prohibit-rcvd%,%ss-status-test-rcvd%,%ss-congested-txed%,%ss-congested-rcvd%,%sccp-rtf-notrans-addr-nature%,%sccp-rtf-notrans-addr-specific%,%sccp-rtf-netwfail-pc-unavail%,%sccp-rtf-netw-conges%,%sccp-rtf-ssn-fail%,%sccp-rtf-ssn-conges%,%sccp-syntax-error%,%sccp-reassem-err-timer%,%sccp-reassem-err-sequence%,%sccp-reassem-err-space%,%sccp-hop-counter-violation%,%sccp-provider-ini-reset%,%sccp-provider-ini-rel%,%sccp-msg-toolarge-segment%,%sccp-segmentation-fail%,%sccp-total-msgs-handled%,%sccp-total-msgs-handl-local-ss%,%sccp-total-msgs-req-gtt%,%sccp-udt-sent%,%sccp-udt-rcvd%,%sccp-udts-sent%,%sccp-udts-rcvd%,%sccp-xudt-sent%,%sccp-xudt-rcvd%,%sccp-xudts-sent%,%sccp-xudts-rcvd%,%sccp-ludt-sent%,%sccp-ludt-rcvd%,%sccp-ludts-sent%,%sccp-ludts-rcvd%,%sccp-cr-sent%,%sccp-cr-rcvd%,%sccp-cc-sent%,%sccp-cc-rcvd%,%sccp-cref-sent%,%sccp-cref-rcvd%,%sccp-rsr-msg-sent%,%sccp-rsr-msg-rcvd%,%sccp-err-msg-sent%,%sccp-err-msg-rcvd%,%sccp-unequipped-user%,%sccp-reason-unknown%,%sccp-class-0-sent%,%sccp-class-0-rcvd%,%sccp-class-1-sent%,%sccp-class-1-rcvd%,%sccp-DT1-sent%,%sccp-DT1-rcvd%,%sccp-rel-compl-supv-fail%,%sccp-rel-disconn-req-rx%,%sccp-routing-fail-invalid-ins-routing-req%,%sccp-routing-fail-invalid-isni-routing-req%,%sccp-routing-fail-isni-constrained-routing%,%sccp-routing-fail-redundant-isni-routing-req%,%sccp-routing-fail-isni-identify-network%,%sccp-inactivity-rcv-tmr-expired%,%sccp-inactivity-test-sent%,%sccp-inactivity-test-received%
> SS7RD1Sch | SS7RD1 Schema | EMS,SS7RD1,%date%,%time%,%ss7rd-number%,%ss7rd-asp_instance%,%ss7rd-sctp-init-tx%,%ss7rd-sctp-init-rtx%,%ss7rd-sctp-init-rx%,%ss7rd-sctp-init-ack-tx%,%ss7rd-sctp-init-ack-rx%,%ss7rd-sctp-shutdown-tx%,%ss7rd-sctp-shutdown-rtx%,%ss7rd-sctp-shutdown-rx%,%ss7rd-sctp-shutdown-ack-tx%,%ss7rd-sctp-shutdown-ack-rtx%,%ss7rd-sctp-shutdown-ack-rx%,%ss7rd-sctp-cookie-tx%,%ss7rd-sctp-cookie-rtx%,%ss7rd-sctp-cookie-rx%,%ss7rd-sctp-cookie-ack-tx%,%ss7rd-sctp-cookie-ack-rx%,%ss7rd-sctp-data-tx%,%ss7rd-sctp-data-rtx%,%ss7rd-sctp-data-rx%,%ss7rd-sctp-sack-tx%,%ss7rd-sctp-sack-rx%,%ss7rd-sctp-shutdown-compl-tx%,%ss7rd-sctp-shutdown-compl-rx%,%ss7rd-sctp-heartbeat-tx%,%ss7rd-sctp-heartbeat-rx%,%ss7rd-sctp-heartbeat-ack-tx%,%ss7rd-sctp-heartbeat-ack-rx%,%ss7rd-sctp-abort-tx%,%ss7rd-sctp-abort-rx%,%ss7rd-sctp-bytes-tx%,%ss7rd-sctp-bytes-rx%,%ss7rd-mtp3-data-tx%,%ss7rd-mtp3-paused-tx%,%ss7rd-mtp3-resumed-tx%,%ss7rd-mtp3-congest-tx%,%ss7rd-mtp3-restrict-tx%,%ss7rd-mtp3-reset-begin-tx%,%ss7rd-mtp3-reset-end-tx%,%ss7rd-mtp3-reset-upu-tx%,%ss7rd-mtp3-data-rx%,%ss7rd-mtp3-paused-rx%,%ss7rd-mtp3-resumed-rx%,%ss7rd-mtp3-congest-rx%,%ss7rd-mtp3-restrict-rx%,%ss7rd-mtp3-reset-begin-rx%,%ss7rd-mtp3-reset-end-rx%,%ss7rd-mtp3-reset-upu-rx%,%ss7rd-m3ua-data-tx%,%ss7rd-m3ua-duna-tx%,%ss7rd-m3ua-dava-tx%,%ss7rd-m3ua-daud-tx%,%ss7rd-m3ua-scon-tx%,%ss7rd-m3ua-dupu-tx%,%ss7rd-m3ua-drst-tx%,%ss7rd-m3ua-regreq-tx%,%ss7rd-m3ua-regrsp-tx%,%ss7rd-m3ua-deregreq-tx%,%ss7rd-m3ua-deregrsp-tx%,%ss7rd-m3ua-aspup-tx%,%ss7rd-m3ua-aspup-ack-tx%,%ss7rd-m3ua-aspdn-tx%,%ss7rd-m3ua-aspdn-ack-tx%,%ss7rd-m3ua-aspac-tx%,%ss7rd-m3ua-aspac-ack-tx%,%ss7rd-m3ua-aspia-tx%,%ss7rd-m3ua-aspia-ack-tx%,%ss7rd-m3ua-hearbeat-tx%,%ss7rd-m3ua-hearbeat-ack-tx%,%ss7rd-m3ua-error-tx%,%ss7rd-m3ua-notify-tx%,%ss7rd-m3ua-data-rx%
> SS7RD2Sch | SS7RD2 Schema | EMS,SS7RD2,%date%,%time%,%ss7rd-number%,%ss7rd-asp_instance%,%ss7rd-m3ua-duna-rx%,%ss7rd-m3ua-dava-rx%,%ss7rd-m3ua-daud-rx%,%ss7rd-m3ua-scon-rx%,%ss7rd-m3ua-dupu-rx%,%ss7rd-m3ua-drst-rx%,%ss7rd-m3ua-regreq-rx%,%ss7rd-m3ua-regrsp-rx%,%ss7rd-m3ua-deregreq-rx%,%ss7rd-m3ua-deregrsp-rx%,%ss7rd-m3ua-aspup-rx%,%ss7rd-m3ua-aspup-ack-rx%,%ss7rd-m3ua-aspdn-rx%,%ss7rd-m3ua-aspdn-ack-rx%,%ss7rd-m3ua-aspac-rx%,%ss7rd-m3ua-aspac-ack-rx%,%ss7rd-m3ua-aspia-rx%,%ss7rd-m3ua-aspia-ack-rx%,%ss7rd-m3ua-hearbeat-rx%,%ss7rd-m3ua-hearbeat-ack-rx%,%ss7rd-m3ua-error-rx%,%ss7rd-m3ua-notify-rx%,%ss7rd-m3ua-lower-intf-pdu-tx%,%ss7rd-m3ua-lower-intf-pdu-rx%,%ss7rd-m3ua-upper-intf-pdu-tx%,%ss7rd-m3ua-upper-intf-pdu-rx%,%ss7rd-m3ua-down-no-route-found%,%ss7rd-m3ua-down-pc-unvailable%,%ss7rd-m3ua-down-msg-failed%,%ss7rd-m3ua-down-loadshare-failed%,%ss7rd-m3ua-up-no-route-found%,%ss7rd-m3ua-up-pc-unvailable%,%ss7rd-m3ua-up-msg-failed%,%ss7rd-m3ua-up-loadshare-failed%,%ss7rd-sctp-error-tx%,%ss7rd-sctp-error-rx%,%ss7rd-m3ua-lower-intf-pdusize-tx%,%ss7rd-m3ua-lower-intf-pdusize-rx%,%ss7rd-m3ua-upper-intf-pdusize-tx%,%ss7rd-m3ua-upper-intf-pdusize-rx%,%ss7rd-m3ua-down-pc-congested%,%ss7rd-m3ua-down-no-psp-avail%,%ss7rd-m3ua-down-no-nsap-avail%,%ss7rd-m3ua-down-data-conges-q%,%ss7rd-m3ua-down-data-as-pend-q%,%ss7rd-m3ua-up-pc-congested%,%ss7rd-m3ua-up-no-psp-avail%,%ss7rd-m3ua-up-no-nsap-avail%,%ss7rd-m3ua-up-data-conges-q%,%ss7rd-m3ua-up-data-as-pend-q%,%ss7rd-mtp3-user-part-unavail-tx%,%ss7rd-mtp3-traffic-restart-allowed-tx%,%ss7rd-mtp3-traffic-restart-waiting-tx%,%ss7rd-mtp3-user-part-unavail-rx%,%ss7rd-mtp3-traffic-restart-allowed-rx%,%ss7rd-mtp3-traffic-restart-waiting-rx%,%ss7rd-mtp3-msu-dropped-routing-err%
> SS7RD3Sch | SS7RD3 Schema | EMS,SS7RD3,%date%,%time%,%ss7rd-number%,%ss7rd-asp_instance%,%ss7rd-m3ua-psp-ps-id%,%ss7rd-m3ua-psp-instance%,%ss7-adjacent-point-code%,%ss7-adjacent-spc-not-accessible%,%ss7rd-m3ua-psp-aspac-ack-rx%,%ss7rd-m3ua-psp-aspac-ack-tx%,%ss7rd-m3ua-psp-aspac-rx%,%ss7rd-m3ua-psp-aspac-tx%,%ss7rd-m3ua-psp-aspdn-ack-rx%,%ss7rd-m3ua-psp-aspdn-ack-tx%,%ss7rd-m3ua-psp-aspdn-rx%,%ss7rd-m3ua-psp-aspdn-tx%,%ss7rd-m3ua-psp-aspia-ack-rx%,%ss7rd-m3ua-psp-aspia-ack-tx%,%ss7rd-m3ua-psp-aspia-rx%,%ss7rd-m3ua-psp-aspia-tx%,%ss7rd-m3ua-psp-aspup-ack-rx%,%ss7rd-m3ua-psp-aspup-ack-tx%,%ss7rd-m3ua-psp-aspup-rx%,%ss7rd-m3ua-psp-aspup-tx%,%ss7rd-m3ua-psp-congestion-count%,%ss7rd-m3ua-psp-congestion-duration%,%ss7rd-m3ua-psp-congestion-level1%,%ss7rd-m3ua-psp-congestion-level2%,%ss7rd-m3ua-psp-congestion-level3%,%ss7rd-m3ua-psp-congestion-queue-hw%,%ss7rd-m3ua-psp-congestion-queue-size%,%ss7rd-m3ua-psp-data-pdu-rx%,%ss7rd-m3ua-psp-data-pdusize-rx%,%ss7rd-m3ua-psp-data-pdusize-tx%,%ss7rd-m3ua-psp-data-pdu-tx%,%ss7rd-m3ua-psp-data-rx%,%ss7rd-m3ua-psp-data-tx%,%ss7rd-m3ua-psp-daud-rx%,%ss7rd-m3ua-psp-daud-tx%,%ss7rd-m3ua-psp-dava-rx%,%ss7rd-m3ua-psp-dava-tx%,%ss7rd-m3ua-psp-deregreq-rx%,%ss7rd-m3ua-psp-deregreq-tx%,%ss7rd-m3ua-psp-deregrsp-rx%,%ss7rd-m3ua-psp-deregrsp-tx%,%ss7rd-m3ua-psp-drst-rx%,%ss7rd-m3ua-psp-drst-tx%,%ss7rd-m3ua-psp-duna-rx%,%ss7rd-m3ua-psp-duna-tx%,%ss7rd-m3ua-psp-dupu-rx%,%ss7rd-m3ua-psp-dupu-tx%,%ss7rd-m3ua-psp-error-rx%,%ss7rd-m3ua-psp-error-tx%,%ss7rd-m3ua-psp-hearbeat-ack-rx%,%ss7rd-m3ua-psp-hearbeat-ack-tx%,%ss7rd-m3ua-psp-hearbeat-rx%,%ss7rd-m3ua-psp-hearbeat-tx%,%ss7rd-m3ua-psp-notify-rx%,%ss7rd-m3ua-psp-notify-tx%,%ss7rd-m3ua-psp-regreq-rx%,%ss7rd-m3ua-psp-regreq-tx%,%ss7rd-m3ua-psp-regrsp-rx%,%ss7rd-m3ua-psp-regrsp-tx%,%ss7rd-m3ua-psp-scon-rx%
> SS7RD4Sch | SS7RD4 Schema | EMS,SS7RD4,%date%,%time%,%ss7rd-number%,%ss7rd-asp_instance%,%ss7rd-m3ua-psp-scon-tx%,%ss7rd-m3ua-psp-unvailable-count%,%ss7rd-m3ua-psp-unvailable-duration%,%ss7rd-m3ua-psp-up-data-as-pend-q%,%ss7rd-m3ua-psp-up-data-conges-q%,%ss7rd-m3ua-psp-up-loadshare-failed%,%ss7rd-m3ua-psp-up-msg-failed%,%ss7rd-m3ua-psp-up-no-nsap-avail%,%ss7rd-m3ua-psp-up-no-psp-avail%,%ss7rd-m3ua-psp-up-no-route-found%,%ss7rd-m3ua-psp-up-pc-congested%,%ss7rd-m3ua-psp-up-pc-unvailable%
> MIPV6HASch | MIPV6HA Schema | EMS,MIPV6HA,%date%,%time%,%vpnname%,%vpnid%,%servname%,%servid%,%num-subscriber%,%aaa-attempt%,%aaa-success%,%aaa-totfail%,%aaa-actauthfail%,%aaa-misauthfail%,%bindupdrec-totrec%,%bindupdrec-totacc%,%bindupdrec-totdeny%,%bindupdrec-totdisc%,%bindupdrec-totcongdisc%,%ibindupdreq-receive%,%ibindupdreq-accept%,%ibindupdreq-deny%,%rbindupdreq-receive%,%rbindupdreq-accept%,%rbindupdreq-deny%,%deregreq-receive%,%deregreq-accept%,%deregreq-deny%,%horeq-receive%,%horeq-accept%,%horeq-deny%,%bindacksent-total%,%bindacksent-acceptreg%,%bindacksent-acceptdereg%,%bindacksent-deny%,%denyreason-badreq%,%denyreason-mismatchid%,%denyreason-mnauthfail%,%denyreason-admprohibit%,%denyreason-noresource%,%denyreason-simbindexceed%,%denyreason-senderror%,%denyreason-unspereason%,%denyreason-msgidrequire%,%denyreason-dadfail%,%denyreason-nothomesubnet%,%denyreason-seqoutwindow%,%denyreason-regchadisallow%,%rrqdeny-admprohibit%,%rrqdeny-unknownha%,%datareceive-totpkt%,%datareceive-totpkt6in6%,%datareceive-totbyte%,%datareceive-totbyte6in6%,%datareceive-errorprotocol%,%datareceive-errorinvpkt%,%datareceive-errornosess%,%datasent-totpkt%,%datasent-totpkt6in6%,%datasent-totbyte%,%datasent-totbyte6in6%,%disconnect-lifetimeexp%,%disconnect-deregistration%,%disconnect-admdrop%,%disconnect-othreason%,%icmpv6-toobigreceive%,%icmpv6-toobigforward%,%icmpv6-toobiggenerate%
> CONTEXTSch | CONTEXT Schema | EMS,CONTEXT,%date%,%time%,%vpnname%,%vpnid%,%sfw-total-rxpackets%,%sfw-total-rxbytes%,%sfw-total-txpackets%,%sfw-total-txbytes%,%sfw-total-injectedpkts%,%sfw-total-injectedbytes%,%sfw-dnlnk-droppkts%,%sfw-dnlnk-dropbytes%,%sfw-uplnk-droppkts%,%sfw-uplnk-dropbytes%,%sfw-total-malpackets%,%sfw-ip-discardpackets%,%sfw-ip-malpackets%,%sfw-icmp-discardpackets%,%sfw-icmp-malpackets%,%sfw-tcp-discardpackets%,%sfw-tcp-malpackets%,%sfw-udp-discardpackets%,%sfw-udp-malpackets%,%sfw-total-dosattacks%,%sfw-total-flows%
> CSCF1Sch | CSCF1 Schema | EMS,CSCF1,%date%,%time%,%vpnname%,%vpnid%,%svcname%,%svcid%,%curregusers%,%failedauth%,%regexp%,%callattrx%,%callatttx%,%callsuccrx%,%callsucctx%,%callfailrx%,%callfailtx%,%curcscfsess%,%callrejpdf%,%callrejloc%,%sesstimeexp%,%hssacc%,%emergcalls%,%tollfreecalls%,%premservcalls%,%internationalcalls%,%longDistancecalls%,%opassistcalls%,%dirassistcalls%,%regreqrx%,%regreqtx%,%invreqrx%,%invreqtx%,%ackreqrx%,%ackreqtx%,%byereqrx%,%byereqtx%,%cancreqrx%,%cancreqtx%,%optreqrx%,%optreqtx%,%prackreqrx%,%prackreqtx%,%subreqrx%,%subreqtx%,%notreqrx%,%notreqtx%,%refreqrx%,%refreqtx%,%inforeqrx%,%inforeqtx%,%updreqrx%,%updreqtx%,%msgreqrx%,%msgreqtx%,%pubreqrx%,%pubreqtx%,%tryrsprx%,%tryrsptx%,%rngrsprx%,%rngrsptx%,%fwdrsprx%,%fwdrsptx%,%quersprx%,%quersptx%,%prgrsprx%,%prgrsptx%,%200-regrsprx%,%200-regrsptx%,%200-invrsprx%,%200-invrsptx%,%200-byersprx%,%200-byersptx%,%200-cnlrsprx%,%200-cnlrsptx%,%200-optrsprx%,%200-optrsptx%,%200-prackrsprx%,%200-prackrsptx%,%200-subrsprx%,%200-subrsptx%,%200-notrsprx%,%200-notrsptx%,%200-infrsprx%,%200-infrsptx%,%200-updrsprx%,%200-updrsptx%,%200-pubrsprx%,%200-pubrsptx%,%200-refrsprx%,%200-refrsptx%,%200-msgrsprx%,%200-msgrsptx%,%202-refrsprx%,%202-refrsptx%,%202-subrsprx%,%202-subrsptx%,%mchrsprx%,%mchrsptx%,%mpersprx%,%mpersptx%,%mtersprx%,%mtersptx%,%upxrsprx%,%upxrsptx%,%altrsprx%,%altrsptx%,%brqerrrx%,%brqerrtx%,%uauerrrx%,%uauerrtx%,%forerrrx%,%forerrtx%,%nfderrrx%,%nfderrtx%,%mnaerrrx%,%mnaerrtx%,%nac406errrx%,%nac406errtx%,%parerrrx%,%parerrtx%,%rtoerrrx%,%rtoerrtx%,%gonerrrx%,%gonerrtx%,%crferrrx%,%crferrtx%,%relerrrx%,%relerrtx%,%rulerrrx%,%rulerrtx%,%umterrrx%,%umterrtx%,%uuserrrx%,%uuserrtx%,%bexerrrx%,%bexerrtx%,%exrerrrx%,%exrerrtx%,%itberrrx%,%itberrtx%,%tnaerrrx%,%tnaerrtx%,%tdnerrrx%,%tdnerrtx%,%ldterrrx%,%ldterrtx%
> CSCF2Sch | CSCF2 Schema | EMS,CSCF2,%date%,%time%,%vpnname%,%vpnid%,%svcname%,%svcid%,%tmherrrx%,%tmherrtx%,%adierrrx%,%adierrtx%,%amberrrx%,%amberrtx%,%bhrerrrx%,%bhrerrtx%,%rqcerrrx%,%rqcerrtx%,%namerrrx%,%namerrtx%,%trperrrx%,%trperrtx%,%udperrrx%,%udperrtx%,%ineerrrx%,%ineerrtx%,%nimerrrx%,%nimerrtx%,%bgterrrx%,%bgterrtx%,%suaerrrx%,%suaerrtx%,%gtterrrx%,%gtterrtx%,%bsverrrx%,%bsverrtx%,%mtlerrrx%,%mtlerrtx%,%pcferrrx%,%pcferrtx%,%bewerrrx%,%bewerrtx%,%decerrrx%,%decerrtx%,%neaerrrx%,%neaerrtx%,%nac606errrx%,%nac606errtx%,%callsetuptime%,%callscounted%
> SS7LINK1Sch | SS7LINK1 Schema | EMS,SS7LINK1,%date%,%time%,%ss7rd-number%,%ss7-linkset-id%,%ss7-link-id%,%ss7-dpc-point-code%,%ss7-link-mtp3-changeover-order-tx%,%ss7-link-mtp3-changeover-order-rx%,%ss7-link-mtp3-changeover-order-ack-tx%,%ss7-link-mtp3-changeover-order-ack-rx%,%ss7-link-mtp3-changeback-declaration-tx%,%ss7-link-mtp3-changeback-declaration-rx%,%ss7-link-mtp3-changeback-ack-tx%,%ss7-link-mtp3-changeback-ack-rx%,%ss7-link-mtp3-emergency-changeover-tx%,%ss7-link-mtp3-emergency-changeover-rx%,%ss7-link-mtp3-emergency-changeover-ack-tx%,%ss7-link-mtp3-emergency-changeover-ack-rx%,%ss7-link-mtp3-inhibit-tx%,%ss7-link-mtp3-inhibit-rx%,%ss7-link-mtp3-inhibit-ack-tx%,%ss7-link-mtp3-inhibit-ack-rx%,%ss7-link-mtp3-uninhibit-tx%,%ss7-link-mtp3-uninhibit-rx%,%ss7-link-mtp3-uninhibit-ack-tx%,%ss7-link-mtp3-uninhibit-ack-rx%,%ss7-link-mtp3-inhibit-deny-tx%,%ss7-link-mtp3-inhibit-deny-rx%,%ss7-link-mtp3-force-uninhibit-tx%,%ss7-link-mtp3-force-uninhibit-rx%,%ss7-link-mtp3-local-inhibit-test-tx%,%ss7-link-mtp3-local-inhibit-test-rx%,%ss7-link-mtp3-remote-inhibit-test-tx%,%ss7-link-mtp3-remote-inhibit-test-rx%,%ss7-link-mtp3-connection-order-tx%,%ss7-link-mtp3-connection-order-rx%,%ss7-link-mtp3-connection-order-ack-tx%,%ss7-link-mtp3-connection-order-ack-rx%,%ss7-link-mtp3-test-tx%,%ss7-link-mtp3-test-rx%,%ss7-link-mtp3-test-ack-tx%,%ss7-link-mtp3-test-ack-rx%,%ss7-link-mtp3-sif-octet-tx%,%ss7-link-mtp3-sif-octet-rx%,%ss7-link-mtp3-sio-octet-tx%,%ss7-link-mtp3-sio-octet-rx%,%ss7-link-mtp3-sio-msu-tx%,%ss7-link-mtp3-tx-msu-dropped%,%ss7-link-mtp3-tx-msu-congestion-dropped%,%ss7-link-mtp3-invalid-pdu-rx%,%ss7-link-mtp3-congestion-threshold1%,%ss7-link-mtp3-congestion-threshold2%,%ss7-link-mtp3-congestion-threshold3%,%ss7-link-mtp3-unavail-duration%,%ss7-link-mtp3-congested-duration%
> SS7LINK2Sch | SS7LINK2 Schema | EMS,SS7LINK2,%date%,%time%,%ss7rd-number%,%ss7-linkset-id%,%ss7-link-id%,%ss7-dpc-point-code%,%ss7-signalling-link-failure%,%ss7-dpc-route-set-test-msg-tx%,%ss7-dpc-route-set-congestion-test-msg-tx%,%ss7-dpc-transfer-prohibited-tx%,%ss7-dpc-transfer-restricted-tx%,%ss7-dpc-transfer-allowed-tx%,%ss7-dpc-transfer-controlled-tx%,%ss7-dpc-sif-octets-tx%,%ss7-dpc-sio-octets-tx%,%ss7-dpc-route-set-test-msg-rx%,%ss7-dpc-route-set-congestion-test-msg-rx%,%ss7-dpc-transfer-prohibited-rx%,%ss7-dpc-transfer-restricted-rx%,%ss7-dpc-transfer-allowed-rx%,%ss7-dpc-transfer-controlled-rx%,%ss7-dpc-usn-msg-rx%,%ss7-dpc-unavailable-duration%,%ss7-dpc-unavailable-count%,%ss7-link-sscf-mtp3-frames-tx%,%ss7-link-sscf-out-of-service-pdu-tx%,%ss7-link-sscf-processor-outage-tx%,%ss7-link-sscf-in-service-pdu-tx%,%ss7-link-sscf-normal-pdu-tx%,%ss7-link-sscf-emergency-pdu-tx%,%ss7-link-sscf-alignment-not-successfull-pdu-tx%,%ss7-link-sscf-management-initiated-pdu-tx%,%ss7-link-sscf-protocol-error-pdu-tx%,%ss7-link-sscf-proving-not-successfull-pdu-tx%,%ss7-link-sscf-mtp3-frames-rx%,%ss7-link-sscf-out-of-service-pdu-rx%,%ss7-link-sscf-processor-outage-rx%,%ss7-link-sscf-in-service-pdu-rx%,%ss7-link-sscf-normal-pdu-rx%,%ss7-link-sscf-emergency-pdu-rx%,%ss7-link-sscf-alignment-not-successfull-pdu-rx%,%ss7-link-sscf-management-initiated-pdu-rx%,%ss7-link-sscf-protocol-error-pdu-rx%,%ss7-link-sscf-proving-not-successfull-pdu-rx%,%ss7-link-qsaal-vpi%,%ss7-link-qsaal-vci%,%ss7-link-qsaal-req-initialization-tx%,%ss7-link-qsaal-req-ack-tx%,%ss7-link-qsaal-connection-reject-tx%,%ss7-link-qsaal-disconnect-command-tx%,%ss7-link-qsaal-disconnect-ack-tx%,%ss7-link-qsaal-resynchronization-command-tx%
> SS7LINK3Sch | SS7LINK3 Schema | EMS,SS7LINK3,%date%,%time%,%ss7rd-number%,%ss7-linkset-id%,%ss7-link-id%,%ss7-dpc-point-code%,%ss7-link-qsaal-resynchronization-ack-tx%,%ss7-link-qsaal-recovery-command-tx%,%ss7-link-qsaal-seq-connection-mode-data-tx%,%ss7-link-qsaal-poll-tx%,%ss7-link-qsaal-stat-tx%,%ss7-link-qsaal-ustat-tx%,%ss7-link-qsaal-unnumbered-user-data-tx%,%ss7-link-qsaal-unnumbered-management-data-tx%,%ss7-link-qsaal-unknown-pdu-type-tx%,%ss7-link-qsaal-tx-discarded-sdus%,%ss7-link-qsaal-tx-pdus-error-pdus%,%ss7-link-qsaal-tx-discarded-pdus%,%ss7-link-qsaal-tx-buffer-in-use-counter%,%ss7-link-qsaal-tx-buffer-in-use-gauge%,%ss7-link-qsaal-req-initialization-rx%,%ss7-link-qsaal-req-ack-rx%,%ss7-link-qsaal-connection-reject-rx%,%ss7-link-qsaal-disconnect-command-rx%,%ss7-link-qsaal-disconnect-ack-rx%,%ss7-link-qsaal-resynchronization-command-rx%,%ss7-link-qsaal-resynchronization-ack-rx%,%ss7-link-qsaal-recovery-command-rx%,%ss7-link-qsaal-recovery-ack-rx%,%ss7-link-qsaal-seq-connection-mode-data-rx%,%ss7-link-qsaal-poll-rx%,%ss7-link-qsaal-stat-rx%,%ss7-link-qsaal-ustat-rx%,%ss7-link-qsaal-unnumbered-user-data-rx%,%ss7-link-qsaal-unnumbered-management-data-rx%,%ss7-link-qsaal-unknown-pdu-type-rx%,%ss7-link-qsaal-rx-pdus-error-pdus%,%ss7-link-qsaal-rx-discarded-pdus%,%ss7-link-qsaal-rx-buffer-in-use-counter%,%ss7-link-qsaal-rx-buffer-in-use-gauge%
> GPRS1Sch | GPRS1 Schema | EMS,GPRS1,%date%,%time%,%vpnname%,%vpnid%,%servname%,%nse-id%,%ns-num-bytes-rvcd%,%ns-num-bytes-sent%,%ns-num-nsvc-failed%,%ns-num-nsvc-congest%,%ns-num-unit-data-msg-rcvd%,%ns-num-unit-data-msg-sent%,%ns-num-alive-pdu-rcvd%,%ns-num-alive-pdu-sent%,%ns-num-alive-ack-pdu-rcvd%,%ns-num-alive-ack-pdu-sent%,%ns-num-block-pdu-rcvd%,%ns-num-block-pdu-sent%,%ns-num-block-ack-pdu-rcvd%,%ns-num-block-ack-pdu-sent%,%ns-num-unblock-pdu-rcvd%,%ns-num-unblock-pdu-sent%,%ns-num-unblock-ack-pdu-rcvd%,%ns-num-unblock-ack-pdu-sent%,%ns-num-reset-pdu-rcvd%,%ns-num-reset-pdu-sent%,%ns-num-reset-ack-pdu-rcvd%,%ns-num-reset-ack-pdu-sent%,%ns-num-status-pdu-rcvd%,%ns-num-status-pdu-sent%,%num-sns-size-rcvd%,%num-sns-size-ack-sent%,%num-sns-size-fail-rcvd-unknown-nse%,%num-sns-config-rcvd%,%num-sns-config-sent%,%num-sns-config-ack-sent%,%num-sns-config-ack-rcvd%,%sns-config-fail-rcv-pdu-not-compat-state%,%sns-config-fail-sent-pdu-not-compat-state%,%sns-config-fail-rcv-inval-ipv4-endpt%,%sns-config-fail-sent-inval-ipv4-endpt%,%sns-config-fail-rcv-inval-ipv6-endpt%,%sns-config-fail-sent-inval-ipv6-endpt%,%sns-config-fail-rcv-prot-err-unspec%,%sns-config-fail-sent-prot-err-unspec%,%sns-config-fail-rcv-inval-essential-param%,%sns-config-fail-sent-inval-essential-param%,%sns-config-fail-rcv-internal-err%,%sns-config-fail-sent-internal-err%,%sns-config-fail-rcv-inval-weight%,%sns-config-fail-sent-inval-weight%,%sns-config-fail-sent-no-rsp-from-peer%,%num-sns-add-rcvd%,%num-sns-add-sent%,%sns-add-fail-rcv-pdu-not-compat-state%,%sns-add-fail-sent-pdu-not-compat-state%,%sns-add-fail-rcv-inval-ipv4-endpt%,%sns-add-fail-sent-inval-ipv4-endpt%,%sns-add-fail-rcv-inval-ipv6-endpt%,%sns-add-fail-sent-inval-ipv6-endpt%,%sns-add-fail-rcv-prot-err-unspec%
> GPRS2Sch | GPRS2 Schema | EMS,GPRS2,%date%,%time%,%vpnname%,%vpnid%,%servname%,%nse-id%,%sns-add-fail-sent-prot-err-unspec%,%sns-add-fail-rcv-inval-essential-param%,%sns-add-fail-sent-inval-essential-param%,%sns-add-fail-rcv-internal-err%,%sns-add-fail-sent-internal-err%,%sns-add-fail-rcv-inval-weight%,%sns-add-fail-sent-inval-weight%,%sns-add-fail-sent-no-rsp-from-peer%,%num-sns-delete-rcvd%,%num-sns-delete-sent%,%sns-delete-fail-rcv-pdu-not-compat-state%,%sns-delete-fail-sent-pdu-not-compat-state%,%sns-delete-fail-rcv-unknown-ip-endpt%,%sns-delete-fail-sent-unknown-ip-endpt%,%sns-delete-fail-rcv-unknown-ip-address%,%sns-delete-fail-sent-unknown-ip-address%,%sns-delete-fail-rcv-prot-err-unspec%,%sns-delete-fail-sent-prot-err-unspec%,%sns-delete-fail-rcv-inval-essential-param%,%sns-delete-fail-sent-inval-essential-param%,%sns-delete-fail-rcv-internal-err%,%sns-delete-fail-sent-internal-err%,%sns-delete-fail-sent-no-rsp-from-peer%,%num-sns-cw-rcvd%,%num-sns-cw-sent%,%sns-cw-fail-rcv-pdu-not-compat-state%,%sns-cw-fail-sent-pdu-not-compat-state%,%sns-cw-fail-rcv-inval-weight%,%sns-cw-fail-sent-inval-weight%,%sns-cw-fail-rcv-unknown-ip-endpt%,%sns-cw-fail-sent-unknown-ip-endpt%,%sns-cw-fail-rcv-unknown-ip-addr%,%sns-cw-fail-sent-unknown-ip-addr%,%sns-cw-fail-rcv-prot-err-unspec%,%sns-cw-fail-sent-prot-err-unspec%,%sns-cw-fail-rcv-inval-essential-param%,%sns-cw-fail-sent-inval-essential-param%,%sns-cw-fail-rcv-internal-err%,%sns-cw-fail-sent-internal-err%,%sns-cw-fail-sent-no-rsp-from-peer%,%sns-num-ack-rcvd%,%sns-num-ack-sent%,%sns-num-unknown-msg%,%sns-num-status-pdu-sent%,%bssgp-total-usr-req-drop%,%bssgp-usr-req-drop-unknown-bvci%,%bssgp-usr-req-drop-blocked-bvc%,%bssgp-usr-req-drop-encoding-fail%,%bssgp-usr-req-drop-bvc-flow-ctrl-rvcd%
> | GPRS3 Schema | EMS,GPRS3,%date%,%time%,%vpnname%,%vpnid%,%servname%,%nse-id%,%bssgp-usr-req-drop-bvc-flow-ctrl-ack-sent%,%bssgp-usr-req-drop-block-rvcd%,%bssgp-usr-req-drop-block-ack-sent%,%bssgp-usr-req-drop-unblock-rcvd%,%bssgp-usr-req-drop-unblock-ack-sent%,%bssgp-usr-req-drop-bvc-reset-sent%,%bssgp-usr-req-drop-bvc-reset-rcvd%,%bssgp-usr-req-drop-bvc-reset-ack-sent%,%bssgp-usr-req-drop-bvc-reset-ack-rcvd%,%bssgp-flush-llc-msg-sent%,%bssgp-flush-llc-ack-msg-rcvd%,%bssgp-cs-paging-msg-sent%,%bssgp-ps-paging-msg-sent%,%bssgp-ra-cap-update-msg-rcvd%,%bssgp-ra-cap-update-ack-msg-sent%,%bssgp-radio-status-msg-sent%,%bssgp-radio-status-msg-rcvd%,%bssgp-suspend-msg-rcvd%,%bssgp-suspend-ack-msg-sent%,%bssgp-suspend-nack-msg-sent%,%bssgp-resume-msg-rcvd%,%bssgp-resume-ack-msg-sent%,%bssgp-resume-nack-msg-sent%,%bssgp-downlink-unitdata-sent%,%bssgp-uplink-unitdata-rcvd%,%bssgp-llc-pdu-discard-msg-rcvd%,%bssgp-ms-flow-ctrl-msg-rcvd%,%bssgp-ms-flow-ctrl-ack-msg-sent%,%bssgp-bvc-status-msg-rcvd%,%bssgp-bvc-status-msg-sent%,%sndcp-xid-req-ms-init%,%sndcp-xid-ind-sgsn-init%,%sndcp-npdus-ack-rcvd-ms%,%sndcp-npdus-ack-sent-ms%,%sndcp-npdus-uack-rcvd-ms%,%sndcp-npdus-uack-sent-ms%,%sndcp-bytes-ack-rcvd-ms%,%sndcp-bytes-ack-sent-ms%,%sndcp-bytes-uack-rcvd-ms%,%sndcp-bytes-uack-sent-ms%,%sndcp-pdu-drop-rcvd-from-llc%,%sndcp-inval-ref-num-rcvd-from-llc%,%sndcp-npdu-sent-sgsn-irau%,%sndcp-npdu-rcvd-sgsn-irau%,%llc-data-req-rx%,%llc-data-cfm-tx%,%llc-data-ind-tx%,%llc-data-sent-ind-tx%,%llc-unit-data-req-rx%,%llc-unit-data-ind-tx%,%llc-discarded-frames-rx%,%llc-discarded-frames-tx%,%llc-error-frames-rx%,%llc-unrecog-frames-rx%,%llc-xid-collisions%,%llc-ciphering-errors%,%llc-fcs-errors%,%llc-frame-stats-ui-rx%,%llc-frame-stats-ui-tx%

> ‌
> bs.cfg File Parameters (Other)

> Directory | Description | Minimum Value | Maximum Value | Default Value
> Format: This section deals with the format string other than the subsystem schemas.
> RemoteFile | The parameter values should not be edited manually. Used by the WEM server. |  |  |
> Tolerance: These values indicate that the server will search records within a range (below and above the expected timestamp) if the exact record is not present. All values are in seconds.
> 5MinTolerance | 0 | 150 (2.5 mins) | 0
> 15MinTolerance | 0 | 450 (7.5 mins) | 0
> 30MinTolerance | 0 | 900 (15 mins) | 0
> 45MinTolerance | 0 | 1350 (22.5 mins) | 0
> HourTolerance | 0 | 1800 (30 mins) | 0
> DayTolerance | 0 | 43200 (12 hrs) | 0
> MonthTolerance | 0 | 1296000 (15 days) | 0
> StartDateTime: These values indicate the date and time for fetching the records in case of daily and monthly report type respectively.
> DailyStartTime | From this value, we can configure the time field for daily report type if DailyStartTime is set to 20, then record present at 08:00 PM of every day will be fetched from the database. | 23 (11:00 PM) | 0 (12:00 AM) | 12
> MonthlyStartDate | From this value, we can configure the day field for monthly report type if MonthlyStartDate is set to 15, then record present at day 15 of every month will be fetched from the database. | 1 | 31 | 15

> ‌
> The bsparser.cfg File
> This file provides parameters for specifying such information as the directories in which bulk statistics records received from the chassis are stored and archived after they are processed, in addition to time intervals for polling and record transfer.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> Caution: Several parameters contained in this file are configurable through the installation process.
> bsparser.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> Directory: This section contains the directory path required for bulk statistics.
> Ftp | Base directory for bulkstat FTP from the ASR 5000. The FTP directory entry can be changed to one of the available directories in the host file system. If the specified directory does not exist, then the bulkstats files will be configured for FTPing in <serverpath>/data/. Important: The FTP directory path entry should always be an absolute path and not a relative path. | -- | -- | <serverpath>/data/
> SecFtp | Base directory for bulkstat secondary FTP from the ASR 5000. The FTP directory entry can be changed to one of the available directories in the host file system. If the specified directory does not exist, then the bulkstats files will be configured for FTPing in <serverpath>/data/. Important: The FTP directory path entry should always be an absolute path and not a relative path. | -- | -- | <serverpath>/data/
> Archive | It is recommended that the WEM server installer/admin changes this entry to one of the available directories in the host file system. This directory contains the archive of the bulkstat files from the ASR 5000. If the directory pointed by this entry is inaccessible or does not exist, then the files FTPed by the ASR 5000 will not be archived. Important: The Archive directory path entry can be an absolute or relative path. | -- | -- | ./bulkstat_archive/
> FileArchiveEnable: This flag enables/disables the archiving of bulkstat files.
> • | 1 = Enables the archiving of bulkstat files
> • | 0 = Disables this functionality
> | -- | -- | 0
> Polling: This section contains parameters that are used for optimization of the bulkstatistics module in terms of polling.
> PollInterval | Poll interval in seconds. | 10 sec | 60 sec | 30 sec
> PoolEnable |
> • | 1 = Enables the thread pool
> • | 0 = Disables the thread pool
> | -- | -- | 1
> Size | Size of the thread pool. Important: This value should not be greater than the MaxDbConnPool parameter defined in the etc/db.cfg file. | 5 | 100 | 10
> FetchConfig | Fetch bulkstat configuration parameters from the ASR 5000.
> • | 1 = Fetch
> • | 0 = Do not fetch
> | -- | -- | 0
> LatencyPeriod | Tolerance period to be considered for Bulkstat FTP operation. | 0 min | 2 min | 2 min
> Queue: This section contains parameters that are used for optimization of the bulkstatistics module in terms of queuing.
> QueueInterval | Queue interval in seconds. | 10 sec | 60 sec | 10 sec
> DBSession: This section contains parameters that are used for optimization of the bulkstatistics module for database calls in terms of DB sessions.
> PermanentSession |
> • | PermanentSession 1 = DB actions performed using permanent database sessions
> • | PermanentSession 0 = DB actions performed using temporary database sessions
> | -- | -- | 0
> Parser: This section contains parameters that are used for connection to the Parser Server process.
> ParserPort | The TCP port to which the WEM server binds. | 1025 | 65535 | 22224

> ‌
> The bsserver.cfg File
> This file provides parameters pertaining to the XML-parsing of bulk statistic records received from the chassis. These parameters provide the ability to enable/disable XML parsing and to specify the directory, in which parsed records are to be stored, time intervals for checking for new records, and whether a single XML file should be generated for all subsystems or one XML file per subsystem in accordance with 3GPP TS 32.401 V4.1.0 and 3GPP TS 32.435 V6.2.0.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> Caution: Several parameters contained in this file are configurable through the installation process.
> bsserver.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> Port: This section contains the server port to which the BulkStat server binds.
> ServerPort | The TCP port to which the WEM server binds. | 1025 | 65535 | 22223
> Directory: This section contains the directory path required for the BulkStat server.
> XMLDir | Base directory path where the measurement files are to be generated. | -- | -- | <EMSServerInstallDir>/xmldata/
> FTP | Base directory for bulkstat FTP from the ASR 5000. The FTP directory entry can be changed to one of the available directories in the host file system. If the specified directory does not exist, then the bulkstats files will be configured for FTPing in <serverpath>/data/. | -- | -- | <serverpath>/data/
> PMFormat | This configurable states the PM table format. | -- | -- | ST16
> XMLDataEnable |
> • | 1 = Enables the XML Data Parsing
> • | 0 = Disables the XML Data Parsing
> | -- | -- | 0
> XMLFileType |
> • | 1 = XML file containing all the subsystem reports
> • | 0 = XML file containing a single subsystem report
> | -- | -- | 0
> ASCIIFileGeneration |
> • | 1 = Creates ASCII file as per the subsystem report
> • | 0 = Creates XML file as per the subsystem report
> | -- | -- | 0
> XMLFileFormat |
> • | 1 = Creates XML measurement report file using the enhanced 3GPP format (V6.2.0)
> • | 0 = Creates XML measurement report file using the old format
> | -- | -- | 0
> Interval: This section contains the interval parameters for polling operations.
> DataPollInterval | Polling interval in seconds to check the availability of new data samples in the WEM bulkstat database subsystem table. | 5 sec | 3600 sec | 60 sec
> SynchInterval | Synchronization interval in seconds to check the availability of new NE (ASR 5000) for polling the data samples in the WEM bulkstat database subsystem table. | 5 sec | 3600 sec | 120 sec
> GranularityPeriod | Granularity period to generate XML report files. The following values are only supported: 300 sec (5 min), 900 sec (15 min), 1800 sec (30 min), 3600 sec (60 min) All values other than the above will be ignored and the default value will be used. | 300 sec | 3600 sec | 300 sec
> Thread Pool: This section contains the configuration values for the thread pool.
> Size | Size of the thread pool. | 5 | 20 | 10
> Access TIme: This section contains the configuration values for overriding the bulkstat XML measurement generation timestamp.
> OverrideLastAccessFlag | The bulkstat server utility can be made to generate complete data from the Iast record by changing the Override Last Access Flag.
> • | OverideLastAccessFlag = 1 (Set to ON)
> • | OverrideLastAccessFlag = 0 (Set to OFF)
> | -- | -- | 0
> XML Data: The following values are the default data values for the XML Measurement file for the 3GPP recommended XML nodes. For more information, refer to the 3GPP TS 32.401 V4.1.0 (2001-12) document.
> ffv | File format version applied by the EM | -- | -- | --
> sn | Sender Name | -- | -- | --
> st | Sender Type | -- | -- | --
> vn | Vendor Name | -- | -- | --
> neun | NE User Name | -- | -- | --
> nedn | NE Distinguish Name | -- | -- | --
> nesw | NE Software | -- | -- | --
> rsf | Representative Suspect Flag: Used as an indication to stop collecting data from any NE in abnormal conditions.
> • | 0 (FALSE) in the case of normal condition
> • | 1 (TRUE) if not normal condition
> | -- | -- | 0
> sf | Suspect Flag: Used as an indication of quality for the scanned data.
> • | 0 (FALSE) in the case of reliable data
> • | 1 (TRUE) if not reliable
> | -- | -- | 0
> es | Error State: Used as an indication to state that the statistics data collection is not completed due to the error condition.
> • | 0 (FALSE) in the case of normal condition
> • | 1 (TRUE) if not normal condition
> | -- | -- | 0
> UseIpAddress | Use ASR 5000 IP address as an NE User Name.
> • | 0: Do not use IP address as a neun, that is, use host name as neun.
> • | 1: Use IP address as neun.
> | -- | -- | 0
> Timezone: This section contains the configuration values for overriding the bulkstat XML measurement generation timestamp.
> TimezoneOffsetToUTC | Configuration for time zone offset for XML file creation. NE generates data in UTC time zone. The timestamp values of the measurement data can be converted to specific time zone by applying the differential value of time in hhmm wrt UTC.TimezoneOffsetToUTC=signhhmm
> • | Sign (optional) indicates the sign of the local time differential from UTC (+ or -). '+' is considered if sign is not given.
> • | hh is the two digit number of hours of the local time differential from UTC (-12..+13).
> • | mm is the two digit number of minutes of the local time differential from UTC (00..59).
> For example:
> • | For IST: Use TimezoneOffsetToUTC=+0530 indicating 05 hours, 30 mins ahead of UTC
> • | For KST: Use TimezoneOffsetToUTC=+0900 indicating 09 hours, 00 mins ahead of UTC
> • | For EST: Use TimezoneOffsetToUTC=-0500 indicating 05 hours, 00 mins behind UTC
> | -- | -- | +0000
> TimezoneOffsetFromUTC | Use the TimezoneOffsetFromUTC parameter for all ASR 5000s to generate XML report file.UsePerNETimezone=0
> • | 0 = Use TimezoneOffsetFromUTC parameter as a time zone to generate report file.
> • | 1 = Use time zone from MISC table in database to generate report file.
> | -- | -- | +0000
> UsePerNETimezone | This parameter indicates whether to use time zone as per ASR 5000. | -- | -- | 0
> BSFTP: The bulkstat server transfers the generated XML file to NM using FTP. This section defines the default values for FTP.
> BSFTPPerformOperation | Flag to indicate whether bulkstat server should perform FTP operation of generated XML files or perform local storage. Values:
> • | 0 = Disable FTP operation
> • | 1 = Enable FTP operation
> | -- | -- | 0
> BSFTPUserName | User name field for FTP operation. | -- | -- |
> BSFTPPassword | Password field for FTP operation. | -- | -- |
> HostIPAddr | IP Address of the host system where the file is to be transferred. | -- | -- |
> HostBaseDir | FTP directory where the file is to be stored on the host system. | -- | -- |
> PoolSize | Pool size for threads. | -- | -- |
> • | 10 for FTP
> • | 3 for SFTP
> PollInterval | Poll interval | -- | -- |
> BSFTPMaxRetries | Maximum retries if FTP failed. | -- | -- |
> BSFTPRetryInterval | Interval between retries of FTP. | -- | -- |
> BSUseSFTP | Flag to indicate whether the bulkstat server should use SFTP/FTP to transfer the XML file to NM. Changing the value of BSUseSFTP requires bulkstat server restart. When BSUseSFTP is set to 0, increase the value of PoolSize to 10. When BSUseSFTP is set to 1, reduce the value of PoolSize to 3. Values:
> • | 0 = Disable SFTP
> • | 1 = Enable SFTP
> | -- | -- | 0

> ‌
> The bstca.cfg File
> This file contains parameters pertaining to the threshold configuration for bulk statistic counters. This file includes the threshold values, that is, clear threshold and set threshold to notify and clear SNMP traps accordingly. These threshold values are specified based on the threshold limit.
> bstca.cfg File Parameters

> Filename | Description
> bstca.cfg | This file specifies the threshold configuration for bulkstat counters.
> • | Needs a Bulkstat Parser restart
> • | Can be changed by the use
> The format is as follows: [schema name] counter name=clear threshold,set threshold Example of the threshold configuration: [mipha] expiry=10,20 recv-total=20,40 Threshold Value (Clear) is less than or equal to 10 for delta value of the bulkstat counter “expiry”. Threshold Value (Set) is more than or equal to 20 for delta value of the bulkstat counter “expiry”.

> ‌
> The cdp.cfg File
> This file contains CDP specific parameters that are configured for generation of ad-hoc reports. The parameters are also configured to export Optimized Customer Master Database (OPTCMDB) files to CDP.
> cdp.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> UNKNOWNURL: This section displays unknown URL database files Import interval related information.
> UnknownUrlImportInterval | This specifies time interval in hours for Content Filtering Configuration to import various databases from CDP | 1 hr | 720 hrs (30 days; 1 Month) | 24 hrs
> Reports: This section displays the report related information.
> MaxNumberOfReports | This specifies the maximum number of reports that can be present in the reports/cf/ directory. | 50 | 500 | 250
> ReportDirSizeLimit | This specifies the directory size of the reports in MB. | 100 | 1024 | 500

> ‌
> The cf.cfg File
> This file contains parameters pertaining to content filtering.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> cf.cfg File Parameters

> Directory | Description | Minimum Value | Maximum Value | Default Value
> ContentFiltering
> EnableCFFeature | Flag to enable/disable the CF features in WEM. Needs a WEM Server restart. Setting this flag to 1 will enable the CF features in WEM.Values:
> • | 1: Enable
> • | 0: Disable
> | -- | -- | 0
> CFStatistics
> CFStatsInterval | Time Interval for generating statistics. This is the time interval in seconds after which the statistics will be generated for CF. | 60 sec | 1800 sec | 300 sec
> CFBackupArchiveDatabase: This section contains the config variables related to archive operation of various CF databases.
> FullDbFilesBackupLimit | This specifies the number of backups to be maintained by Content Filtering Server for Full databases. | 1 | 10 | 4
> IncrementalDbFilesBackupLimit | This specifies the number of days incremental backup is to be maintained for incremental databases. | 1 day | 90 days | 30 days
> ArchiveDbFiles | This allows user to enable/disable archiving of database files once outdated. Possible values: ENABLE, DISABLE | -- | -- | DISABLE
> ArchivePath | This specifies the path where archive files are maintained. ArchivePath = ./flash/archive/ | -- | -- | --
> CFTRAP
> CFSnmpVersion | SNMP version for generation of WEM traps. The supported version is SNMPv1. | -- | -- | --
> CFTrapReceiverHost | Alarm receiver machine IP Address.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | --
> CFTrapReceiverPort | The port on which traps will be generated by the WEM server.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 65535 | 162
> CFThreadPool
> CFThreadPoolSize | This is the thread pool size for export content rating databases to the chassis. | 5 | 20 | 10
> UnkURLImportThreadPool
> UnkURLImportThreadPoolSize | This is the thread pool size for pulling unknown URL databases from the inPilot application. | 5 | 20 | 10

> ‌
> The configupdate.cfg File
> This file contains parameters pertaining to chassis software configuration updates using the Web Element Manager. It includes the directory in which the configuration files are stored and the directory to which configuration update log files can be stored.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> configupdate.cfg File Parameters

> Directory | Description | Minimum Value | Maximum Value | Default Value
> ConfigUpdate
> LogDirPath | The directory where all generated log files are stored. It can be changed by the user. If the specified directory does not exist, then the config files will be stored in ./flash/ConfigUpdate/log. Important: The config file directory path entry should always be an absolute path and not a relative path. | 1 | 80 | ./flash/ConfigUpdate/log
> ConfigFileDirPath | The directory where all configuration files to be loaded on the ASR 5000 are stored. It can be changed by the user. If the specified directory does not exist, then the config files will be stored in ./flash/ConfigUpdate/config. Important: The config file directory path entry should always be an absolute path and not a relative path. | 1 | 80 | ./flash/ConfigUpdate/config

> ‌
> The db.cfg File
> This file contains parameters pertaining to the WEM’s use of the Postgres database. It identifies the various databases and their locations.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> Caution: Improper configuration of this file can adversely affect WEM operation. To ensure proper operation of the Web Element Manager, do not edit the parameters in these files.
> db.cfg File Parameters

> Directory | Description | Minimum Value | Maximum Value | Default Value
> Database | This file contains parameters pertaining to the Database Name, Database type, Host IP Address, Port, User Name and Password of the Web Element Manager application. Here, Database means Postgres, Oracle, etc. and CommitRecTime is in seconds. Important: Any change in the configuration files will restart the server resulting in client restart. The format is as follows: DbName,Database,HostAddress,Port,UserName,Password
> • | CONFIGDBASE = configdb,postgres,127.0.0.1,5432,postgres,postgres
> • | TRAPDBASE = trapdb,postgres,127.0.0.1,5432,postgres,postgresMI
> • | BDBASE = mibdb,postgres,127.0.0.1,5432,postgres,postgresAU
> • | DITDBASE = auditdb,postgres,127.0.0.1,5432,postgres,postgresB
> • | SDBASE = bsdb,postgres,127.0.0.1,5432,postgres,postgresP2P
> • | DBASE = p2pdb,postgres,127.0.0.1,5432,postgres,postgresNB
> • | DBASE = nbdb,postgres,127.0.0.1,5432,postgres,postgres
> | -- | -- | --
> MaxDbConnPool | Size of the DB connection pool. | 1 | 50 | 25
> PostgresDIR | This specifies the path of the Postgres directory. PostgresDIR = /<ems_dir>/postgres | -- | -- | --

> ‌
> The emslic.cfg File
> This file contains license information for the WEM Server installation.
> emslic.cfg File Parameters

> Key | Description | Value | Default Value
> License: This is the WEM License file.
> LicenseKey | License key for using WEM.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | LicenseKey = Basic|Customer-EU2|Customer-EU4 | No default value

> ‌
> The fm.cfg File
> This file contains parameters pertaining to the handling of received alarms. It provides parameters for configuring color indicators for the various severities, E-mail server information for alert notifications, and SNMP operation.
> fm.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> SEVERITY: This section describes the severity configuration for traps that contain various priorities and the color in which the traps of that severity should be displayed.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Severity Name | The severity name is similar to the severity color. The format is as follows: Severity Name = Severity color Severity color should be specified in a CSV format. (Comma Separated Values: red, green, blue) Valid color values range from 0 to 255. The following are some usual colors with CSV format: 255,0,0 - red 0,255,0 - green 0,0,255 - blue 255,192,203 - pink 190,190,190 - gray 255,255,255 - white 0,0,0 - black 255,255,0 - yellow 0,255,255 - cyan 169,169,169 - darkgray 211,211,211 - lightgray 255,0,255 - magenta 255,165,0 - orange 165,42,42 - brown Color entry can be of a decimal, octal or hexadecimal form.
> • | A decimal constant begins with a non-zero digit, and consists of a sequence of decimal digits.
> • | An octal constant consists of the prefix 0 optionally followed by a sequence of the digits 0 to 7 only.
> • | A hexadecimal constant consists of the prefix 0x or 0X followed by a sequence of the decimal digits and letters a (or A) to f (or F) with values 10 to 15 respectively.
> | -- | -- | Default color (red, green, blue) value is 127
> Severity Level | The Severity level (number) for the nth row in the SEVERITY section is n. For example: Clear severity level is 6Minor severity level is 4 The severity levels are as follows:
> • | Severity level 1: This specifies “Indeterminate” alarm with color code “140,140,0”.
> • | Severity level 2: This specifies “Critical” alarm with color code “255,0,0”.
> • | Severity level 3: This specifies “Major” alarm with color code “255,0,255”.
> • | Severity level 4: This specifies “Minor” alarm with color code “204,153,0”.
> • | Severity level 5: This specifies “Warning” alarm with color code “0,145,145”.
> • | Severity level 6: This specifies “Clear” alarm with color code “0,145,0”.
> | -- | -- | --
> EMAIL: This section describes the E-mail configuration for traps.
> MailFrom | E-mail address of the e-mail notification originator.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | No default value
> MailServerAddr | Address in DNS or IP address format on which the SMTP (e-mail) server should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | No default value
> MailServerPort | Port number on which the e-mail server should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 65535 | 25
> DisconnectTime | Time out for mail server TCP connection in seconds.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 secs | 3600 secs | 10 secs
> URLPath | URL path on which the WEM server should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | No default value
> SCRIPT: This section describes the script configuration for traps.
> ScriptSrvPort | Port number on which the script server should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 65535 | 22225
> ScriptDirPath | Base directory in which the scripts to be executed are stored.
> • | Needs a WEM Server restart
> • | Must not be changed by the user - There is a separate directory that exists for the user.
> |  |  | <serverpath>/scripts
> UserScriptDirPath | Base directory in which the user scripts to be executed are stored. Needs a WEM Server restart |  |  | <serverpath>/alarmscripts
> TRAP: This section describes the flags for logging traps.
> SnmpTrapPort | The port on which traps will be received by the WEM server.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> • | Server must be run as root in order to receive traps on privileged ports (1 to 1024)
> | 1 | 65535 | 162
> SelectionFlag | Flag to enable or disable e-mail, notification, forwarding, script execution and syslog.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values: ALL, IMG ALL: Processing the traps when it is ASR 5000 or non-ASR 5000 IMG: Only ASR 5000 traps are processed | -- | -- | ALL
> LoggingFlag | Flag for logging traps.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values: ALL, IMG ALL: All traps are logged. IMG: Only ASR 5000 traps are logged. | -- | -- | ALL
> BroadCastFlag | Flag for receiving broadcast-traps (case insensitive).
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values: ENABLE, DISABLE ENABLE: Receiving broadcast traps DISABLE: Don't receive broadcast traps. | -- | -- | DISABLE
> GlobalOverride | Flag for global override.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values: ENABLE, DISABLE ENABLE: Disable sending e-mail and executing script DISABLE: Enable e-mail and script | -- | -- | DISABLE
> SupressEmsTraps | Flag for suppressing WEM-only Traps.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values: ENABLE, DISABLE ENABLE: Disable generation of WEM traps DISABLE: Enable generation of WEM traps | -- | -- | DISABLE
> SnmpVersion | SNMP Version for generation of WEM traps. The supported versions are:
> • | SNMPv1
> • | SNMPv2c
> | -- | -- | --
> ProxyFwd | Flag for configuring WEM server as proxy to forward the received SNMP traps. In case of forwarding the received SNMP traps as SNMPv2 traps, we need to - # translate the notification parameters to appropriate SNMPv2 parameters.Flag for suppressing WEM-only Traps.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values: ENABLE, DISABLE ENABLE: Disable generation of WEM traps DISABLE: Enable generation of WEM traps |  |  | ENABLE
> SYSLOG: This section describes the Syslog server configuration for traps.
> LogHost | Address of the machine on which syslog should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> |  |  | 127.0.0.1
> LogPort | Port number on which syslog should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 65535 | 514
> Facility | Syslog facility.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> FACILITY contains the following possible values: LOG_KERN,LOG_USER,LOG_MAIL, LOG_DAEMON, LOG_AUTH,LOG_SYSLOG, LOG_LPR,LOG_NEWS,LOG_UUCP,LOG_CRON,LOG_LOCAL0,LOG_LOCAL1, LOG_LOCAL2,LOG_LOCAL3,LOG_LOCAL4,LOG_LOCAL5,LOG_LOCAL6,LOG_LOCAL7 | -- | -- | LOG_LOCAL3
> Priority | Syslog priority.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> PRIORITY contains the following possible values: LOG_EMERG, LOG_ALERT, LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, LOG_DEBUG | -- | -- | LOG_INFO
> EVENTSERVICE
> LogCLIShowCommands | Flag to enable(1)/disable(0) the logging of “show” CLI commands.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 0 | 1 | 1
> AUDIO
> AudioDir | Audio directory which contains audio files.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> |  |  | No default value
> GROUP | Alarm group configuration.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> The group number for nth row in the GROUP section is n. For example:
> • | “Communications Alarm” group number is 1
> • | “QOS Alarm” group number is 4
> The alarm groups are:
> • | Communications Alarm
> • | Processing Error Alarm
> • | Environmental Alarm
> • | QOS Alarm
> • | Equipment Alarm
> | -- | -- | No default value
> PROBABLECAUSE | Alarm probable cause configuration.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> The probable cause number for nth row in the PROBABLECAUSE section is n. For example:
> • | “Loss of multi frame sync” probable cause number is 1
> • | “Loss of frame sync” probable cause number is 4
> The probable causes are:
> • | Heating or ventilation system failure
> • | Equipment malfunction
> • | Manual configuration, software crash or voltage fluctuation
> • | Module inserted
> • | Module removed
> • | Software failure or crash
> • | Module slot mismatch
> • | Congestion
> • | Communication problem
> • | Configuration or customization error
> • | Manual configuration or threshold crossed
> • | Underlying resource unavailable
> | -- | -- | 0 (means empty)
> CLIInfoPolling: This section provides information needed for the configuration of Thread pool and Polling interval required for the FMCliInfoHandler module.
> CLIInfoPollInterval | Poll interval in seconds. Important: These value are dependent on the keepalive notification interval. | 1 sec | 30 sec | 15 sec
> CLIInfoThreadPoolSize | Size of the Thread Pool. | 5 | 20 | 10
> PENDINGALARM: This section describes the pending alarm related configuration.
> autoClearInterval | Time-out interval for pending alarms in days. If any alarm is in pending state for this configured interval, then it will be automatically cleared.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 30 | 3

> ‌
> The hwinv.cfg File
> This file provides the e-mail ID used when sending hardware change notifications.
> Important: The parameter in this file is configurable through the installation process.
> hwinv.cfg File Parameters

> Key | Description | Default Value
> HWEMAIL: This is the configuration file for Hardware Inventory.
> ChangeInHWMailFrom |
> • | E-mail address of the e-mail notification originator
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | No default value

> ‌
> The ism.cfg File
> This file contains parameters pertaining to communication between the Web Element Manager and managed chassis. These parameters include the security information used to access the chassis as well as the ports over which communication takes place.
> This file also contains a parameter that provides the ability to enable/disable the SSL encryption for client-to-server and server-to-boxer communication.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> ism.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> IMGSessMgt: This section describes the parameters that store ASR 5000 login information.
> ASID | Application Server ID that will be used by the WEM server to communicate with ASR 5000.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 10 | STARENT
> ASPasswd | Application Server Password for the ASR 5000 that will be used by the WEM server to communicate with the ASR 5000.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 35 | SN123
> IMGPort | Port number on which the ASR 5000 should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10000 | 65535 | 14132
> SSLConnect | Flag to enable or disable the SSL connection.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Currently, this feature is disabled and only IIOP connections will be used. | 0 | 1 | 0
> EnforceSSL | Flag to enforce SSL.
> • | Needs a WEM Server restart.
> • | Can be changed by the user.
> • | Overrides SSLConnect value, if set to 1.
> Change the value of ENFORCE_SSL parameter in ems/client/img.html and ems/client/imgdebug.html if this value is changed. If set to 1, then the sslflag field will be updated to 't' for all existing IMGs in the boxer table in ConfigDB at server restart. | 0 | 1 | 0
> SleepTime | Time for which the cleanup thread sleeps.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 5 | 300 | 60
> MaxIdleTime | Maximum time for which the servant reference can be idle.Needs a WEM Server restartCan be changed by the user | 30 | 1800 | 300
> IMGKeepAlive: This section describes parameters related to the ASR 5000 keep-alive.
> IcmpTimeout | Timeout value for ICMP requests in seconds. | 1 | 60 | 5
> IcmpRetries | Number of retries for ICMP requests. | 0 | 10 | 2
> IcmpKeepAliveInterval | Polling interval for ICMP requests in seconds. Important: The value must be greater than IcmpTimeout * (IcmpRetries + 1). | 5 | 300 | 30
> CorbaKeepAliveInterval | Polling interval for CORBA requests in seconds. Important: The value must be greater than or equal to IcmpKeepAliveInterval. | 10 | 600 | 2 * IcmpKeepAliveInterval

> ‌
> The mcrdbs.cfg File
> This file contains parameters that are configured to support the conversion of Vendor Format Master Database (VFMDB) to Starent Networks Format Master Database (SFMDB). This file also contains information on MCRDBS to handle the database files.
> mcrdbs.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> MCRDBS: This section describes parameters that store MCRDBS related information.
> FullDBFilesImportInterval | Database files Import interval: This specifies the time interval in hours for Content Filtering Server to import various databases from MCRDBS. (Databases: SFMDB) | 2 hrs | 4320 hrs (90 days; 6 months) | 24 hrs
> INCDBFilesImportInterval | Database files Import interval: This specifies the time interval in hours for Content Filtering Server to import various databases from MCRDBS. (Databases: SFMDB-INC) | 2 hrs | 720 hrs (30 days; 1 month) | 24 hrs
> StarentFormatDbFileImportPath | Starent format database file path: This specifies the path where SFMDB files are located in MCRDBS. Example: <Mcrdbs server path>/cfems/<cfems ip address>/sfmdb | -- | -- | --
> StarentFormatIncDbFileImportPath | Starent format incremental database file path: This specifies the path where SFMDB-INC files are located in MCRDBS. Example: <MCRDBS server path>/cfems/<cfems ip address>/sfmincdb | -- | -- | --
> MCRDBSInfo | This specifies the MCRDBS information in the following format:MCRDBS Host name, MCRDBS Ip address1, User name1, password1 Important: If the user does not want to enter any values, leave the fields blank separated by comma. Example: hostName, userName, password (OR), HostIPAddr, userName, Password | -- | -- | --

> ‌
> The mdproxy.cfg File
> This configuration file defines various properties used for the MD EMS Proxy functionality.
> mdproxy.cfg File Parameters

> Key | Description
> MDAUDIT
> MDAuditPath | The directory path to log the audit trail into file. The base is the WEM server's directory. MDAuditPath = log/RESP
> MDAuditSyncPath | MDAuditSyncPath = log/SYNC_RESP
> MDAlarmPath | MDAlarmPath = log/FM

> ‌
> The nb.cfg File
> This file contains parameters for NorthBound notifications from the WEM. The information in this file is used by the application for forwarding fault management information to other management devices on the NorthBound interface. This information includes such things as the device IP address and port number on which to forward notifications.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> nb.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> Fault Management: This section describes the parameters that store NorthBound Notification Service related configuration information.
> NSMode | Mode using WEM gets the Notification Service reference.Valid values: URL, IOR, NONE
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | NONE
> NSMode is URL� | Notification Service URL. The format is as follows: corbaloc:iiop:<NSAddr>:<NSPort>/<ChannelFactoryName> | -- | -- | corbaloc:iiop:127.0.0.1:5001/NOTIFY_SVC/CHANNEL_FACTORY
> NSAddr | Host IP Address on which the Notification Service should be running.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | 127.0.0.1
> NSPort | Port number on which the Notification Service should be running
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1000 | 65535 | 5001
> ChannelFactoryName | Names to be assigned to the channel factory created by the Notification Service daemon.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | NOTIFY_SVC/CHANNEL_FACTORY
> NSIORFILE | Path name of the Notification Service IOR (String field object reference) file. Here, the NSMode is IOR.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | No default value
> NSChannelId | Channel ID through which WEM notifies the events.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 0 | 1000 | 0

> ‌
> The nbserver.cfg File
> This file contains parameters for the configuration of NorthBound Server and Notification Service processes, and NorthBound interface.
> Important: The NorthBound Server and Notification Service processes are customer-specific and are not operational without the appropriate license. Please contact your local sales representative for additional information.
> The nms.cfg File
> This file contains parameters which control WEM access to the PostgreSQL database, client access to the server, and other properties used by the application for proper operation.
> Important: Many of the parameters contained in this file are configurable through the installation process.
> nms.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> DATABASE: This section describes parameters that store database configuration information.
> HostAddress | This specifies the host IP address. | -- | -- | 127.0.0.1
> UserName | This specifies the username to connect to the database. | -- | -- | postgres
> PassWord | This specifies the password to connect to the database. | -- | -- | postgres
> IOR
> Login |  | -- | -- | login.ior
> RESPath |  | -- | -- | res_path.ior
> SVPNIOR |  | -- | -- | svpn.ior
> ConfigAudit |  | -- | -- | audit.ior
> ClientSession: This section describes parameters related to client session management.
> UserLimit | Maximum number of user sessions allowed by the server at any time. | 1 | 100 | 10
> SecurityAdminLimit | Maximum number of Security Administrator sessions allowed by the server at any time. | 1 | UserLimit | 5
> ActiveToInactiveInterval | Time for activity time out in minutes. | 1 | -1 (infinite) | 15
> KeepAliveCallInterval | Keep alive polling time in seconds. | 0 | 86400 | 15
> KeepAliveRetryCnt | Retry count for keep alive: The minimum time for dismissing the client session if it is not reachable = KeepAliveCallInterval * KeepAliveRetryCnt | 1 | 5 | 2
> SessionInitTime | Time required for a typical session to initialize to ready state. Keep alive will be enabled after a specified time after client login. | KeepAliveCallInterval | 86400 | 120
> UserSessionLimit | Maximum number of sessions for a particular user. | 1 | UserLimit | 5
> ContextUserLimit | Maximum number of user sessions for a context. | 1 | UserLimit | 5
> Notification | Global flag to enable/disable the sending notification. Possible values: ENABLE, DISABLE | -- | -- | ENABLE
> Active timeout interval | This flag allows the user to login to the N+1st WEM Client and also, to cleanup any inactive / dead sessions. Session will get timed out after the given time (minutes) from the login time. Valid User: Security Administrator | -- | -- | --
> DenialService | Global Flag to enable/disable the Denial-Of-Service. Possible Values: ENABLE, DISABLE | -- | -- | DISABLE
> DefaultUPref | This is the default user preference configuration XML string. DefaultUPref = <xml version="1.0" encoding="UTF-8"> <screen id="SCR_ID_TOPOLOGY"> <dimension> <param name="RESOLUTION" value="1024X768"/> <param name="XPOS" value="137"/> <param name="YPOS" value="89"/> <param name="WIDTH" value="512"/> <param name="HEIGHT" value="384"/> </dimension> <information> <param name="MAP_COLOR" value="-1"/> <param name="MAP_IMAGE" value="none"/> <param name="LOOK_AND_FEEL"value="Metal"/> <param name="LAST_MAP_VISITED" value="true"/> <param name="LAST_MAP_NAME" value="default"/> <param name="LAST_IMG_VISITED" value="true"/> <param name="LAST_IMG_NAME" value="earth"/> <paramname="CLIENT_TIMEOUT" value="60"/> <param name="POLLING_INTERVAL" value="10"/> <param name="AUDIO_ALARMING" value="true"/> <param name="SHOW_TOOLBAR" value="true"/> <param name="TOOLBAR_POSITION" value="North"/> <param name="NOTIFICATION" value="true"/> </information> </screen> | -- | -- | --
> DefaultAppPath | This is the default Application Path XML string. DefaultAppPath=<xml version="1.0" encoding="UTF-8"> <screen id="SCR_ID_APPLICATION_PATH"> <dimension> <param name="RESOLUTION" value="1024X768"/> <param name="XPOS" value="272"/> <param name="YPOS" value="275"/> <param name="WIDTH" value="608"/> <param name="HEIGHT" value="313"/> </dimension> <os id="Windows 95"> <param name="telnet" value="cmd /c start c:\\telnet.exe"/> <param name="ftp" value="cmd /c start c:\\ftp.exe"/> <param name="ssh" value="cmd /c start c:\\ssh.exe"/> <param name="mibbrowser" value="cmd /c start c:\\mibbrowser.exe"/> </os> | -- | -- | --
> SWUpgrade: This section describes the parameters related to Software Upgrade.
> FTPSessLimit | Maximum number of FTP sessions. | -- | -- | 5
> FTPCallBackPeriod | Call back period in seconds with which the status of the FTP will be updated. | -- | -- | --
> NMSIMGBaseDir | Base directory for Software Upgrade Manager - Image files. | -- | -- | NMSIMGBaseDir = ./flash
> NMSIMGBaseDirForFileCompare | Base directory for Config file comparison - Image files. | -- | -- | NMSIMGBaseDirForFileCompare = ./flash
> FRV: This section describes the front/rear-view related parameters.
> PollInterval | Time interval used by the WEM Client for polling.
> • | Does not require WEM Server restart
> • | This value can be changed by the user
> | 10 secs | 60 secs | 30 secs
> Topology
> ClientBaseDir | Client base directory: This value is internally used by the Topology server module and should not be changed. | -- | -- | --
> MapImageDir | Directory Name which contains image files. This value can be changed and the subdirectory must exist in ClientBaseDir. | -- | -- | --
> POAPolicies: This section describes policies used for the POAs.
> ServerIIOPPort | Using this port, three sequential upward ports will be used to create POAs. Change the value of SERVER_BASE_PORT parameter in ems/client/img.html and ems/client/imgdebug.html if this value is changed. | 15000 | 15002 | 15000
> EMSLicense
> Mode | The mode in which WEM started. Valid values: PDSN, GGSN, BOTH The value must be specified otherwise, the server does not function. | -- | -- | --
> ConfigBackup
> FTPUserName | User name that will be used by the ASR 5000 to upload files on WEM server. This user account should be existing on the WEM server host machine.
> • | Needs server restart
> • | Can be changed by the user
> | 1 | 64 | guest
> FTPPassword | Password that will be used by the ASR 5000 while uploading files to WEM server. This user account should be existing on the WEM server host machine.
> • | Needs server restart
> • | Can be changed by the user
> | 1 | 64 | guest12
> EMSServer
> ServerIpAddress | This IP Address will be used by WEM server for generating IOR files. If the field has default loopback interface values then, WEM server will take the first active interface present on the machine. Change this IP value to change IP used for IOR generation. If the specified IP is not active, WEM server will not start. | -- | -- | 127.0.0.1
> ServerPort | The TCP port to which the WEM server binds. | 1025 | 65535 | 22222
> EMSORB: This section describes the parameters related to Object Request Broker.
> ORBReadTimeout | The read time out used for sockets in seconds. | 5 secs | 3600 secs | 30 secs
> ORBWriteTimeout | The write time out used for sockets in seconds. | 5 secs | 3600 secs | 30 secs
> EMSSSLORB
> SSLORBReadTimeout | The read time out used for sockets in seconds. | 5 secs | 3600 secs | 30 secs
> SSLORBWriteTimeout | The write time out used for sockets in seconds. | 5 secs | 3600 secs | 30 secs

> ‌
> The pcrefgen.cfg File
> Configuration file for 3GPP XML report generation of Camiant PCRF.
> pcrefgen.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> MPEManagerInfo: This section provides information required to configure the details of MPE Manager making the HTTP Post request.
> MPE Manager IP-address | EMS will make HTTP Post request to the configured address to fetch the MPE OM statistics periodically. Needs a PCRF Report generation restart. Needs a PCRF Report generation restart. | -- | -- | --
> MPE Manager host-name | EMS will use the configured name for generating 3GPP statistics for MPE Manager related counters. This name will be used as userLabel in the 3GPP XML file and also in the file name. This name should not be identical to any MPE name. Can be changed by the user. | -- | -- | Empty. In this case ip-address will be used.
> MPE Manager user-id | EMS will make HTTP Post request to the configured user-id for login to make HTTP Post request to MPE Manager. Can be changed by the user. | -- | -- | --
> MPE Manager password. | EMS will make HTTP Post request to the configured password for login to make HTTP Post request to MPE Manager. Needs a PCRF Report generation restart. Can be changed by the user. | -- | -- | --
> MPE Manager XML interface URL. | This URL, the ip-address and the userId-password will be used to construct the HTTP Post request URL. Needs a PCRF Report generation restart. Can be changed by the user. | -- | -- | mi/xmlInterfaceRequest.do
> XMLInterfaceUrl | -- | -- | -- | mi/xmlInterfaceRequest.do
> Report Generation
> Poll Interval | EMS will poll the MPE Manager as the configured poll-interval.This poll interval should be the same as the sample interval configured at MPEManager. Value in minutes. Can be changed by the user. PollInterval = 15 | -- | 5 | 15 minutes
> Latency Period. | This the latency (delay) in making the request to MPE Manager.So for fetching the statistics for time interval 12:15:00 to 12:30:00, the HTTPPOST request to MPE Manager will be made at 12:32:00 (endTime + LatencyPeriod). Value in seconds. Can be changed by the user. ReqLatencyPeriod = 120 | 0 | 900 (15 minutes). | 120 seconds.
> Initial offset for StartTime. | This is the offset in number of minutes before the utility's startup time to be used for fetching the PCRF statistics from the MPE Manager. e.g. if this value is set as 120 and the utility is started at 08:30:00 then the reports will be generated for statistics from 06:30:00. This value will be overridden by the next StartTime stored in database. Value in minutes. StartTimeOffset = 0 | 0 | 1400 | 0
> PCRFUseDoubleQuotes | 0 = Disable encapsulating all the values in the generated PCRF files in double quotes. 1 = Enable encapsulating all the values in the generated PCRF files in double quotes. PCRFUseDoubleQuotes=0 | -- | -- | 0
> PCRFFTP: The pcrfrepgen process transfers the generated 3GPP XML file to NM using ftp. This section defines the default values for ftp. The pcrfrepgen process uses the same host machine used by the bulkstat server for transferring the GGSN files. FTP configuration parameters 'HostIPAddr', BSFTPUserName', 'BSFTPPassword', 'BSFTPMaxRetries', 'BSFTPRetryInterval' and BSUseSFTP' from /etc/bsserver.cfg will be used to transfer the generated PCRF 3GPP XML files.
> PcrfFTPPort | Port number used to FTP/SFTP the PCRF XML files. This attribute can be changed by the user. When BSUseSFTP is set to 1, set BSFTPPort to 22. | -- | -- | 21 for FTP; 22 for SFTP.
> HostIPAddr | IP address of the host system where the file is to be transferred. | -- | -- | 127.0.0.1
> BSFTPUserName | User name field for ftp operation. | -- | -- | Anonymous.
> BSFTPPassword | Password field for ftp operation. | -- | -- | Guest.

> ‌
> The processmonitor.cfg File
> This file contains parameters used by the Process Monitor function. These include parameters such as the directories from which WEM-related processes are started, polling intervals, and maximum percentage thresholds.
> processmonitor.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> ProcessInfo: This section provides all the process information to be monitored by the module.
> ListServer | Lists all the servers to be monitored: 0 = WebServer 1 = DB 2 = EMSServer 3 = EMSScriptServer 4 = BulkstatServer 5 = BulkstatParser 6 = NBServer 7 = NotifyService | -- | -- | --
> WebServer | Web Server Process Information: In this case, it is the Apache Web Server.
> • | Name of the Process executable: ExeName=httpd
> • | Absolute or Relative path for executable file: ExePath=/<ems_dir>/apache/bin
> • | File name which contains the pid of the process: PidName=httpd.pid
> • | Absolute or Relative path for the pid file: PidPath=/<ems_dir>/apache/logs
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> DB | Database Process Information: In this case, it is Postgres.
> • | Name of the Process executable: ExeName=postmaster
> • | Absolute or Relative path for executable file: ExePath=/<ems_dir>/postgres/bin
> • | File name which contains the pid of the process: PidName=postmaster.pid
> • | Absolute or Relative path for the pid file: PidPath=/<ems_dir>/postgres/data
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> EMSServer | EMS Server Process Information.
> • | Name of the Process executable: ExeName=server
> • | Absolute or Relative path for executable file: ExePath=/<ems_dir>/server/bin
> • | File name which contains the pid of the process: PidName=server.pid
> • | Absolute or Relative path for the pid file: PidPath=/<ems_dir>/server
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> EMSScriptServer | EMS Script Server Process Information.
> • | Name of the Process executable: ExeName=scriptsrv
> • | Absolute or Relative path for executable file: ExePath=/<ems_dir>/server/bin
> • | File name which contains the pid of the process: PidName=script.pid
> • | Absolute or Relative path for the pid file: PidPath=/<ems_dir>/server
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> BulkstatServer | BulkstatServer Process Information.
> • | Name of the Process executable: ExeName=bulkstatserver
> • | Absolute or Relative path for executable file: ExePath=./bin
> • | File name which contains the pid of the process: PidName=bsserver.pid
> • | Absolute or Relative path for the pid file: PidPath=.
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> BulkstatParser | BulkstatParser Process Information.
> • | Name of the Process executable: ExeName=bulkstatparser
> • | Absolute or Relative path for executable file: ExePath=./bin
> • | File name which contains the pid of the process: PidName=bulkstatparser.pid
> • | Absolute or Relative path for the pid file: PidPath=.
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> NBServer | NBServer Process Information.
> • | Name of the Process executable: ExeName=nbserver
> • | Absolute or Relative path for executable file: ExePath=./bin
> • | File name which contains the pid of the process: PidName=nbserver.pid
> • | Absolute or Relative path for the pid file: PidPath=.
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> NotifyService | NotifyService Process Information.
> • | Name of the Process executable: ExeName=Notify_Service
> • | Absolute or Relative path for executable file: ExePath=./bin
> • | File name which contains the pid of the process: PidName=notify_service.pid
> • | Absolute or Relative path for the pid file: PidPath=.
> • | MultiProc: Flag indicating whether the process information should include the information of child processes or not.
> Valid values:
> • | 0: Disable
> • | 1: Enable
> | -- | -- | 0
> DirectoryInfo: This section provides information needed to monitor the directory size.
> DirEMSServer | EMS Server Directory Information. Path of EMS Server directory: DirPath=/<ems_dir>/server | -- | -- | --
> DirDB | Database Directory Information. Path of Database directory: DirPath=/<ems_dir>/postgres/data | -- | -- | --
> DirEMSFtp | EMS FTP Directory Information. Path of EMS FTP directory: DirPath=./data | -- | -- | --
> DirEMSBlkArch | EMS Bulkstat Archive Directory Information. Path of EMS Bulkstat archive directory: DirPath=./bulkstat_archive | -- | -- | --
> DirFTPCFDB | FTP CF DB Directory Information. Path of FTP directory for CF DB: DirPath=./flash/cf/cfdatabases | -- | -- | --
> Poll Information: This section provides information needed for the configuration of threshold poll interval in seconds. Each sub-module under monitor has its own poll interval defined to give fine tune support.
> ProcInfoPollInterval | The process which changes frequently can be monitored for threshold limits with a smaller poll interval, say 5 seconds. | 1 sec | 36000 sec | 5 sec
> DirInfoPollInterval | The directory size does not change suddenly and can be monitored with 1 Min OR greater than 1 Min poll interval for threshold limit. | 60 sec | 36000 sec | 300 sec
> IFInfoPollInterval | If information is constant, it can be monitored once in a Min. | 5 sec | 36000 sec | 60 sec
> Threshold Information: This section provides information needed for the configuration of default threshold values for various parameters monitored by the module. These values (if available to server successfully from this configuration file) are used for default configuration of the threshold values for the parameters.These values indicate the maximum percentage of threshold limits for the individual parameters as the default values. Note:
> • | WEM server will take the current configuration for the latest threshold values from the WEM Database saved in the last session of the server.
> • | The following values can be used as default configuration for the parameter(s) if no value(s) is/are available from the database. For example, first run of the server after a new installation or a database crash, etc.)
> To use the following values to override the database configurations with configuration values, WEM server administrator can turn on (set value to 1) the OverrideDBConfig flag.
> ThreshProcWebServer | This is the threshold value for disk utilization of Web Server process. | 0 | 100 | 25
> ThreshProcDB | This is the threshold value for disk utilization of DB Server process. | 0 | 100 | 25
> ThreshProcEMSServer | This is the threshold value for disk utilization of EMS Server process. | 0 | 100 | 25
> ThreshProcEMSScriptServer | This is the threshold value for disk utilization of EMS Script Server process. | 0 | 100 | 25
> ThreshProcBulkstatServer | This is the threshold value for disk utilization of Bulkstat Server process. | 0 | 100 | 25
> ThreshProcBulkstatParser | This is the threshold value for disk utilization of Bulkstat Parser process. | 0 | 100 | 25
> ThreshProcNBServer | This is the threshold value for disk utilization of NB Server process. | 0 | 100 | 25
> ThreshProcNotifyService | This is the threshold value for disk utilization of Notify Service process. | 0 | 100 | 25
> ThreshProcTotalCPU | This is the threshold value for total disk utilization of CPU. | 0 | 100 | 60
> ThreshProcTotalSwap | This is the threshold value for total disk utilization of swaps. | 0 | 100 | 75
> ThreshDirEMSServer | This is the threshold value for disk utilization of EMS Server Directory. | 0 | 100 | 25
> ThreshDirDB | This is the threshold value for disk utilization of Database Directory. | 0 | 100 | 25
> ThreshDirFTP | This is the threshold value for disk utilization of FTP Directory. | 0 | 100 | 25
> ThreshDirBlkArch | This is the threshold value for disk utilization of Bulkstat Archive Directory. | 0 | 100 | 25
> ThreshDirCFDB | This is the threshold value for disk utilization of CF DB Directory0. | 0 | 100 | 25
> OverrideDBConfig | Flag to override the current DB Configuration of the threshold values with the configuration values. Values:
> • | 1: True
> • | 0: False
> | -- | -- | 0
> CPU: This section describes the parameters used to calculate the CPU utilization.
> NumberofSample | This calculates the average of 'NumberofSample' given in the config file. | 1 | 360 | 5

> ‌
> The ps.cfg File
> This file contains parameters which control Web Element Manager polling intervals for managed chassis and database queries.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> ps.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> Polling: This section describes the parameters related to polling support.
> MinPollInterval | Minimum time interval used by the WEM server for polling.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 secs | 86400 secs | 10 secs
> MaxPollInterval | Maximum time interval used by the WEM server for polling.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 secs | 86400 secs | 86400 secs
> PoolEnable | Flag to enable/disable the thread pool.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Values:
> • | PoolEnable 1 = Thread pool enable
> • | PoolEnable 0 = Thread pool disable
> | 0 | 1 | 0
> Size | Size of the thread pool.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 | 100 | 10
> MaxSize | Maximum size of the thread pool.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 | 100 | 10
> ErrorCausingMethodRetries | Number of retries for error causing method. WEM server stops calling the error causing method after configurable successive method calls give the same error.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 1 | 10 | 3
> EnableInterval | Enabling interval for disabled fetch in seconds. The server periodically enables the disabled fetch.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 | 600 | 120
> Database: This section describes the parameters related to database information.
> QueryNameLimit | Number of queries to be stored in the database per user per context.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 100 | 200 | 100

> ‌
> The psmon.cfg File
> This file contains parameters for the operation of the PSMon (process monitor) function supported by the WEM.
> psmon.cfg File Parameters

> Key | Description | Default Value
> NotifyEmail | Defines the e-mail address where notification e-mails are to be sent. | root@localhost
> SmtpHost | Defines the IP address or hostname of the SMTP server to be used to send e-mail notifications. | localhost
> Frequency | Defines the frequency of process table queries. This is the polling interval. | 60 secs
> LastSafePID | When defined, psmon will never attempt to kill a process ID which is numerically less than or equal to the value defined by the last safepid. Important: Psmon will never attempt to kill a process ID lesser than or equal to 1, or itself. | 100
> ProtectSafePIDsQuietly | Accepts a boolean value of On or Off. Suppresses all notifications from preserved process IDs when used in conjunction with the last safepid directive. | Off
> DryRun | Forces this psmon to as if the --dryrun command line switch had specified. This is useful if you want to force a specific configuration file to only report and never actually take any automated action. This is enabled in this default distribution configuration to prevent people from blindly executing psmon “out of the box” and causing damage in live environments. The <Process *> scope is commented out by default. It should be used with extreme care. If used, run psmon in “DryRun” mode by adding the “DryRun” directive in this configuration file. Important: Read the config file thoroughly before enabling this feature. | Enabled
> For example: Use the following format to configure each process. Copy the following 6 lines for each WEM Process to monitor and modify according to the WEM Path: <Process /<ems_dir>/server/bin/server> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/server) pidfile /<ems_dir>/server/server.pid numretry 2 tmintval 300 </Process> Note: Do not remove the following statement as it is used to modify the config file while installing through the GUI Installer: <Process /<ems_dir>/postgres/bin/postmaster -i> spawncmd /<ems_dir>/server/scripts/postgresctl start pidfile /<ems_dir>/postgres/data/postmaster.pid numretry 10 tmintval 330 </Process> <Process /<ems_dir>/apache/bin/httpd -f /<ems_dir>/apache/conf/httpd.conf> spawncmd /<ems_dir>/apache/bin/apachectl start pidfile /<ems_dir>/apache/logs/httpd.pid numretry 10 tmintval 330 </Process> <Process /<ems_dir>/server/bin/server> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/server) pidfile /<ems_dir>/server/server.pid numretry 10 tmintval 330 </Process> <Process /<ems_dir>/server/bin/bulkstatserver> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/bulkstatserver) pidfile /<ems_dir>/server/bsserver.pid numretry 10 tmintval 330 </Process>
> <Process /<ems_dir>/server/bin/bulkstatparser> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/bulkstatparser) pidfile /<ems_dir>/server/bulkstatparser.pid numretry 10 tmintval 330 </Process> <Process /<ems_dir>/server/bin/Notify_Service> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/nbSrvr) pidfile /<ems_dir>/server/notify_service.pid numretry 10 tmintval 330 </Process> <Process /<ems_dir>/server/bin/nbserver> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/nbserver) pidfile /<ems_dir>/server/nbserver.pid numretry 10 tmintval 330 </Process> <Process /<ems_dir>/server/bin/scriptsrv> spawncmd (cd /<ems_dir>/server; /<ems_dir>/server/bin/scriptsrv) pidfile /<ems_dir>/server/script.pid numretry 10 tmintval 330 </Process> Where:
> • | numretry and tmintval are optional
> • | “tmintval” must be in seconds and greater than ('numretry' * 'Frequency’)
> • | Incase of wrong values, this will not work properly
> New Processes
> Do not edit these lines if you do not have enough information. The instances should not be 0. <Process /<ems_dir>/perl5.8.5/bin/perl -w ./psmon --daemon --cron> pidfile /<ems_dir>/server/psmon.pid instances 1 </Process>
> Sendmail SMTP Mail Daemon
> <Process sendmail> spawncmd /sbin/service sendmail start pidfile /var/run/sendmail.pid </Process>
> Apache Group HTTP Daemon
> <Process httpd> spawncmd /sbin/service httpd restart pidfile /var/run/httpd.pid instances 200 pctcpu 80 </Process>
> MySQL Database
> <Process mysqld> spawncmd /sbin/service mysqld restart killcmd /sbin/service mysqld stop pidfile /var/run/mysqld/mysqld.pid pctcpu 90 pctmem 60 </Process>

> ‌
> The res.cfg File
> This file contains parameters for associating resource-bundles to specific Web Element Manager dialogs. This is the configuration file for fetching screen-specific resource-bundle paths. Currently there are only two bundles. The resource-ids must be present in both the sections.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> Caution: To ensure proper operation of the Web Element Manager, do not edit the parameters in these files.
> res.cfg File Parameters

> Bundle 1 | Bundle 2
> GlobalCommonId = res.globalcommon.GlobalCommonCompFileChooserId = res.components.FileChooserCompColorChooserId = res.components.ColorChooserCompOptionPaneId = res.components.OptionPaneCompTableId=res.components.table.STableScrKeyExport = res.components.table.SExportFileScrKeyBoxerList = res.screens.boxerlist.GlobalListScrKeyUser = res.screens.useradm.UserAdminScrKeySubscriber = res.screens.subscriber.SubscriberScrKeyPPPSession = res.screens.ppp.SPPPScrKeyPPPConfig = res.screens.ppp.SPPPScrKeyPPPCounter = res.screens.ppp.SPPPScrKeyPPPSummary = res.screens.ppp.SPPPScrKeyPPPEchoTest = res.screens.ppp.SPPPScrKeyPPPStat = res.screens.ppp.SPPPScrKeyPPPInfo = res.screens.ppp.SPPPScrKeyAAATest = res.screens.aaa.SRADIUSScrKeyAAARADIUSTest = res.screens.aaa.SRADIUSScrKeyAAARADIUSCounter = res.screens.aaa.SRADIUSScrKeyAAARADIUSCounterDetails = res.screens.aaa.SRADIUSScrKeyAAARADIUSAuth = res.screens.aaa.SRADIUSScrKeyAAARADIUSAuthConfig = res.screens.aaa.SRADIUSScrKeyAAARADIUSAcct = res.screens.aaa.SRADIUSScrKeyAAARADIUSCharging = res.screens.aaa.SRADIUSScrKeyAAARADIUSChargingConfig = res.screens.aaa.SRADIUSScrKeyAAAContextConfig = res.screens.aaa.SRADIUSScrKeyModifyContextAAA = res.screens.aaa.SRADIUSScrKeyAAARADIUSResult = res.screens.aaa.SRADIUSScrKeyAAAGlobalConfig = res.screens.aaa.SRADIUSScrKeyModifyGlobalAAA = res.screens.aaa.SRADIUSScrKeySubsCriteria = res.screens.monitor.SMonitorFilterScrKeyFrontView = res.screens.csp.SCSPScrKeyRearView = res.screens.csp.SCSPScrKeySysInfo = res.screens.csp.SCSPScrKeyCardConfig = res.screens.csp.SCSPScrKeyPortConfig = res.screens.csp.SCSPScrKeyModifyPort = res.screens.csp.SCSPScrKeyPortInformation = res.screens.csp.SCSPScrKeyShowPortCounters = res.screens.csp.SCSPScrKeyIntfPortBind = res.screens.csp.SCSP | ScrKeyBoxerOperation = res.screens.boxerlist.BoxerOperationScrKeyNewMap = res.screens.boxerlist.NewMapScrKeySelectImage = res.screens.boxerlist.SelectImageScrKeyUserAdmin = res.screens.useradm.UserAdminScrKeyUser = res.screens.useradm.UserScrKeySubscriber = res.screens.subscriber.SubscriberScrKeyShowSubscriber = res.screens.subscriber.SShowSubscriberScrKeyShowSubscriberPDSNResult = res.screens.subscriber.SShowSubscriberPDSNResultScrKeyShowSubscriberGGSNResult = res.screens.subscriber.SShowSubscriberGGSNResultScrKeyAbout = res.topology.AboutDialogScrKeyTopology = res.topology.TopologyScrKeyPPPSession = res.screens.ppp.SPPPSessionScrKeyPPPConfig = res.screens.ppp.SPPPConfigScrKeyPPPCounter = res.screens.ppp.SPPPCounterScrKeyPPPSummary = res.screens.ppp.SPPPSummaryScrKeyPPPStat = res.screens.ppp.SPPPStatScrKeyPPPInfo = res.screens.ppp.SPPPInfoScrKeyContextAdministration = res.screens.contextlist.ContextAdministrationScrKeyContextAdd = res.screens.contextlist.ContextAddScrKeyContextModify = res.screens.contextlist.ContextModifyScrKeyAccessListUndefined = res.screens.contextlist.AccessListUndefinedScrKeyContextOperResults = res.screens.contextlist.ContextOperResultsScrKeyConfigPDSN = res.screens.pdsn.PDSNServiceScrKeyShowPDSN = res.screens.pdsn.PDSNServiceScrKeySPIBind = res.screens.pdsn.PDSNServiceScrKeyAddService = res.screens.pdsn.PDSNServiceScrKeyPDSNClosedRP = res.screens.pdsn.SPdsnClosedRPScrKeyPDSNClosedRPConfig = res.screens.pdsn.SPdsnClosedRPConfigScrKeyShowPcfStatus = res.screens.pdsn.SShowPcfStatusScrKeyUserPref = res.screens.userpreferences.UserPreferencesScrKeyAAATest = res.screens.aaa.SAAATestScrKeyAAARADIUSTest = res.screens.aaa.SRADIUSTestScrKeyAAARADIUSCounter = res.screens.aaa.SRADIUSCounter
> ScrKeyShowCardDiag = res.screens.csp.SCSPScrKeyCardHardware = res.screens.csp.SCSPScrKeyHardwareInventory = res.screens.csp.SCSPScrKeyHardwareVersion = res.screens.csp.SCSPScrKeyMacAddr = res.screens.csp.SCSPScrKeyMIPFA = res.screens.mip.SMIPScrKeyMIPFASess = res.screens.mip.SMIPScrKeyMIPFAStat = res.screens.mip.SMIPScrKeyMIPHA = res.screens.mip.SMIPScrKeyMIPHASess = res.screens.mip.SMIPScrKeyMIPHAStat = res.screens.mip.SMIPScrKeyAuditFilter = res.screens.audit.SAuditScrKeyAuditDetails = res.screens.audit.SAuditScrKeyCardMapping = res.screens.csp.SCSPScrKeySynch = res.screens.csp.SCSPScrKeyVLANDetails = res.screens.csp.SCSPScrKeySShowAlarm = res.screens.csp.SCSPScrKeyPortUtilization = res.screens.csp.SCSPScrKeyPrint = res.print.SPrintScrKey = res.screens.process.SProcessMonitorScrKeyProcessThreshold = res.screens.process.SProcessMonitorScrKeySAPNConfig = res.screens.apn.SAPNScrKeySAPNStat = res.screens.apn.SAPNScrKeyGTPPConf = res.screens.gtpp.SGTPPScrKeyGTPPStat = res.screens.gtpp.SGTPPScrKeyGTPPTest = res.screens.gtpp.SGTPPScrKeyIPSecMap = res.screens.ipsec.SIPSecScrKeyIsakmp = res.screens.ipsec.SIPSecScrKeyIsakmpSA = res.screens.ipsec.SIPSecScrKeyTransform = res.screens.ipsec.SIPSecScrKeyIPSecSA = res.screens.ipsec.SIPSecScrKeyIPSecStat = res.screens.ipsec.SIPSecScrKeyIPSecResult = res.screens.ipsec.SIPSecScrKeyPDSNClosedRPConfig = res.screens.pdsn.SPdsnClosedRPScrKeySPIOTiming=res.screens.csp.SCSP | ScrKeyAAARADIUSCounterDetails = res.screens.aaa.SRADIUSCounterScrKeyAAARADIUSAuth = res.screens.aaa.SRADIUSAuthScrKeyAAARADIUSAuthConfig = res.screens.aaa.SRADIUSAuthScrKeyAAARADIUSAcct = res.screens.aaa.SRADIUSAcctScrKeyAAAContextConfig = res.screens.aaa.SAAAContextConfigScrKeyModifyContextAAA = res.screens.aaa.SAAAContextConfigScrKeyAAARADIUSResult = res.screens.aaa.SRADIUSResultScrKeyAAAGlobalConfig = res.screens.aaa.SAAAGlobalConfigScrKeyModifyGlobalAAA = res.screens.aaa.SAAAGlobalConfigScrKeyRADIUSClientStatus = res.screens.aaa.SRADIUSClientStatusScrKeyAccessList = res.screens.vpn.AccessListScrKeyAccessListOpr = res.screens.vpn.AccessListScrKeyIPRoute = res.screens.vpn.IPRouteScrKeyIPRouteConf = res.screens.vpn.IPRouteScrKeySGetIntf = res.screens.vpn.IPRouteScrKeyIPPool = res.screens.vpn.IPPoolScrKeyIPPoolConf = res.screens.vpn.IPPoolScrKeyIPInterface = res.screens.vpn.IPInterfaceScrKeyIPInterfaceConf = res.screens.vpn.IPInterfaceScrKeyDNSConf = res.screens.vpn.SDNSConfScrKeyShowResult = res.screens.vpn.ResultCodeScrKeyIPInterfaceStats = res.screens.vpn.SIPInterfaceStatsScrKeyBusyoutRangeConf = res.screens.vpn.SBusyoutRangeConfScrKeyShowIPSP = res.screens.vpn.SShowIPSPScrKeyMonitorProtocols = res.screens.monitor.SMonitorScrKeyMonitorSubscribers = res.screens.monitor.SMonitorScrKeyProtoCriteria = res.screens.monitor.SMonitorFilterScrKeySubsCriteria = res.screens.monitor.SMonitorSubsFilterScrKeyFrontView = res.screens.csp.SIMGViewScrKeyRearView = res.screens.csp.SIMGViewScrKeySysInfo = res.screens.csp.SSysInfoScrKeyCardConfig = res.screens.csp.SCardConfig
> ScrKeyApplicationServerConfig=res.screens.vmg.SApplicationServerScrKeyAsAppDBConfig=res.screens.vmg.SAsAppDBScrKeyAsAppVimConfig=res.screens.vmg.SAsAppVimScrKeyAsAppChatConfConfig=res.screens.vmg.SAsAppChatConfScrKeyVmgMmsConfig=res.screens.vmg.SVmgMmsScrKeyAsDisConfig=res.screens.vmg.SAsDisScrKeyAsAppPttConfig=res.screens.vmg.SAsAppPttScrKeySTiming=res.screens.csp.SCSPScrKeyMultipleColSort = res.components.table.SMultipleColumnSortScrKeyIMGInfo = res.screens.hwinventory.SIMGInfoScrKeyProxyDns = res.screens.vpn.SProxyDnsScrKeyCscfPeerServer = res.screens.ims.SCscfPeerServerScrKeyCscfPolicy = res.screens.ims.SCscfPolicyScrKeyCscfService = res.screens.ims.SCscfServiceScrKeyCscfSessTemp = res.screens.ims.SCscfSessTempScrKeyCscfRoute = res.screens.ims.SCscfRouteScrKeyCscfACL = res.screens.ims.SCscfAclScrKeyCscfTranslation = res.screens.ims.SCscfTranslationScrKeyClassMap = res.screens.vpn.SClassMapScrKeyPolicyMap = res.screens.vpn.SPolicyMapScrKeyPolicyGroup = res.screens.vpn.SPolicyGroupScrKeyCscfURN = res.screens.ims.SCscfUrnScrKeyOnDemandReportConfig=res.screens.cf.SReportCommon | ScrKeyPortConfig = res.screens.csp.SPortConfigScrKeyModifyPort = res.screens.csp.SModifyPortScrKeyPortInformation = res.screens.csp.SPortInformationScrKeyShowPortCounters = res.screens.csp.SShowPortCountersScrKeySystem = res.screens.csp.SSysInfoScrKeyShowCardDiag = res.screens.csp.SShowCardDiagScrKeyCardHardware = res.screens.csp.SCardHardwareScrKeyHardwareInventory = res.screens.csp.SHardwareInventoryScrKeyHardwareVersion = res.screens.csp.SHardwareVersionScrKeyShowPower = res.screens.csp.SShowPowerScrKeySoftUpgrade = res.screens.softupgrade.SSoftUpgradeScrKeyShowVersion = res.screens.softupgrade.SShowVersionScrKeyOnlinePatchUpgrade = res.screens.softupgrade.SOnlinePatchUpgradeScrKeyFCFileSelection = res.screens.softupgrade.SFileSelectionScrKeyFCFileComparisonResult = res.screens.softupgrade.SFileComparisonResultScrKeyFCRemoteFileBrowser = res.screens.softupgrade.SRemoteFileBrowserScrKeyConfigurationFileEditor = res.screens.softupgrade.SConfigurationFileEditorScrKeyBootConfiguration = res.screens.softupgrade.SBootConfigurationScrKeyMIPFA = res.screens.mip.SMIPFAScrKeyMIPFASess = res.screens.mip.SMIPFASessScrKeyMIPFAStat = res.screens.mip.SMIPFAStatScrKeyMIPHA = res.screens.mip.SMIPHAScrKeyMIPHASess = res.screens.mip.SMIPHASessScrKeyMIPHAStat = res.screens.mip.SMIPHAStatScrKeyMIPFAContext = res.screens.mip.SMIPFAContextScrKeyMIPHAContext = res.screens.mip.SMIPHAContextScrKeySubsConfig = res.screens.subscriber.SubsConfigScrKeyChangePassword = res.screens.useradm.SChangePasswordScrKeyChangePasswordDialog = res.screens.useradm.SChangePasswordDialogScrKeyDefaultSubsConfig = res.screens.subscriber.SDefaultSubsConfigScrKeySysLog = res.screens.logging.SSysLogScrKeySysLogConf = res.screens.logging.SSysLog
> | ScrKeyLoggingConfig = res.screens.logging.SLoggingConfigScrKeyShowResultDialog = res.screens.logging.SResultDialogScrKeySNMPShow = res.screens.snmp.SSNMPScrKeySNMPConfig = res.screens.snmp.SSNMPConfigScrKeySNMPStatistics = res.screens.snmp.SSNMPStatisticsScrKeyUserSessInfo = res.screens.security.SUserSessInfoScrKeyInstall = res.screens.license.SInstallScrKeyLicense = res.screens.license.SLicenseScrKeyClock = res.screens.clock.SClockScrKeyAudit = res.screens.audit.SAuditScrKeyAuditFilter = res.screens.audit.SAuditFilterScrKeyAuditDetails = res.screens.audit.SAuditDetailsScrKeyBulkStat = res.screens.bulkstatistics.BulkStatsScrKeyBulkStatConf = res.screens.bulkstatistics.BulkStatsScrKeyBulkAnalysis = res.screens.bulkstatistics.performancestatScrKeyGraphScreenBulk = res.screens.bulkstatistics.performancestatScrKeyPerformanceStat = res.screens.bulkstatistics.performancestatScrKeyOrbemClientSession = res.screens.orbem.SOrbemClientSessionScrKeyOrbemConfig = res.screens.orbem.SOrbemConfigScrKeyModifyOrbemConfig = res.screens.orbem.SOrbemConfigScrKeyModifyOrbemClient = res.screens.orbem.SModifyOrbemClientScrKeyUCM = res.screens.ucm.SUCMScrKeyCardMapping = res.screens.csp.SCardMappingsScrKeySysInfoAdv = res.screens.csp.SAdvDataScrKeyHalt = res.screens.csp.SHaltScrKeyMigrate = res.screens.csp.SMigrateScrKeyPriority = res.screens.csp.SPriorityScrKeySynch = res.screens.csp.SSynchScrKeyVLANDetails = res.screens.csp.SVLANDetailsScrKeyMacAddr = res.screens.csp.SPortMacAddrScrKeyPortUtilization = res.screens.csp.SPortUtilizationScrKeyAllMgr = res.screens.session.SessionSubsystemScrKeySessRecovery = res.screens.session.SSessRecoveryScrKeyShowSessionProgress = res.screens.session.SShowSessionProgress
> | ScrKeySessProgressFilterDlg = res.screens.session.SShowSessionProgressScrKeyGenericRP = res.screens.rp.SGenericRPScrKeyGenericBCMCS = res.screens.bcmcs.SGenericBCMCSScrKeyMulticastSessions = res.screens.bcmcs.SMulticastSessionsScrKeyMulticastSessionFilter = res.screens.bcmcs.SMulticastSessionsFilterDialogScrKeyMulticastSessionsResult = res.screens.bcmcs.SShowMulticastSessionsResultScrKeySShowCpu = res.screens.cpu.SShowCpuScrKeySShowCpuDetails = res.screens.cpu.SShowCpuScrKeySShowTask = res.screens.cpu.SShowTaskScrKeyShowResources = res.screens.cpu.SShowResourcesScrKeyTaskConfig = res.screens.cpu.STaskConfigScrKeyProcessThreshold = res.screens.process.SThresholdScrKeyCOAlarms = res.screens.alarm.SCOAlarmsScrKeyAlarmStatFilters = res.screens.alarm.SAlarmStatFiltersScrKeyAlarmStat = res.screens.alarm.SAlarmStatFiltersScrKeyEventSetFilter = res.screens.alarm.SAlarmFilterScrKeyEventConfig = res.screens.alarm.SAlarmConfigScrKeyEvent = res.screens.alarm.SAlarmViewScrKeyEventDesc = res.screens.alarm.SDescScrKeySShowAlarm = res.screens.alarm.SShowAlarmScrKeyShowAlarmStat = res.screens.alarm.SShowAlarmStatScrKeyNTP = res.screens.system.SNTPScrKeyNetReqPDPCtxtConfig = res.screens.system.SNetReqPDPCtxtConfigScrKeyNetReqPDPCtxtConfigDlg = res.screens.system.SNetReqPDPCtxtConfigScrKeySAPN = res.screens.apn.SAPNScrKeySAPNConfig = res.screens.apn.SAPNConfigScrKeySAPNStat = res.screens.apn.SAPNStatScrKeyDhcpShow = res.screens.dhcp.SDHCPShowScrKeyDhcpConfig = res.screens.dhcp.SDHCPConfigScrKeyDhcpStat = res.screens.dhcp.SDHCPStatScrKeySDHCPStatus = res.screens.dhcp.SDHCPStatusScrKeyDhcpCache = res.screens.dhcp.SDHCPCacheScrKeyDhcpTest = res.screens.dhcp.SDHCPTestScrKeyLAC = res.screens.l2tp.L2tpScrKeyLACConfig = res.screens.l2tp.L2tp
> | ScrKeySShowL2TP = res.screens.l2tp.L2tpScrKeyLTTPTunnelFull = res.screens.l2tp.L2tpScrKeyLTTPTunnelCntrs = res.screens.l2tp.L2tpScrKeyLTTPTunnelSummary = res.screens.l2tp.L2tpScrKeyLTTPSessionFull = res.screens.l2tp.L2tpScrKeyLTTPSessionCntrs = res.screens.l2tp.L2tpScrKeyLTTPSessionSummary = res.screens.l2tp.L2tpScrKeyLTTPStat = res.screens.l2tp.L2tpScrKeyLNSShow = res.screens.l2tp.SLNSShowScrKeyLNSConfig = res.screens.l2tp.SLNSConfigScrKeyGTPPConf = res.screens.gtpp.SGTPPConfScrKeyGTPPStat = res.screens.gtpp.SGTPPStatScrKeyGTPPTest = res.screens.gtpp.SGTPPTestScrKeyGSNConf = res.screens.gtpp.SGSNScrKeyGTPPInterimNow = res.screens.gtpp.SGTPPInterimNowScrKeyShowGTPPCounters = res.screens.gtpp.SShowGTPPCountersScrKeyGTPPStorageSrvStat = res.screens.gtpp.SGTPPStorageServerStatisticsScrKeyGGSNService = res.screens.ggsn.SGGSNServiceScrKeyGGSNServiceInfo = res.screens.ggsn.SGGSNServiceInfoScrKeyGGSNServiceConfig = res.screens.ggsn.SGGSNServiceConfigScrKeyGTPCStat = res.screens.gtpc.SGTPCStatisticsScrKeyGTPCTest = res.screens.gtpc.SGTPCTestScrKeyIPSecMap = res.screens.ipsec.SIPSecMapScrKeyIsakmp = res.screens.ipsec.SIsakmpScrKeyIsakmpSA = res.screens.ipsec.SIsakmpSAScrKeyTransform = res.screens.ipsec.STransformScrKeyIPSecSA = res.screens.ipsec.SIPSecSAScrKeyIPSecStat = res.screens.ipsec.SIPSecStatScrKeyPeriodicSaveBoxerCfg = res.screens.configbackup.SPeriodicSaveBoxerCfgScrKeyIPRIPConfig = res.screens.rip.SIPRIPConfigScrKeyIPRIPConfigDlg = res.screens.rip.SIPRIPConfigScrKeyShowRouterRIPConfig = res.screens.rip.SRouterRIPConfigScrKeyModifyRouterRIPConfig = res.screens.rip.SRouterRIPConfigScrKeyKeyChainConfig = res.screens.rip.SKeyChainConfigurationScrKeyAddKeyChain = res.screens.rip.SKeyChainConfiguration
> | ScrKeyModifyKeyChainConfig = res.screens.rip.SModifyKeyChainConfigScrKeyExternalInlineServer = res.screens.vpn.SExternalInlineServerScrKeyIPPoolDefConfig = res.screens.vpn.SIPPoolDefaultConfigScrKeyAddBusyoutRangeConf = res.screens.vpn.SAddBusyoutRangeConfScrKeySFetchNonLocalInfo= res.globalcommon.FetchNonLocalInfoScrKeySThreshShow = res.screens.threshold.SThreshShowScrKeyThreshConfig = res.screens.threshold.SThreshConfigScrKeySCongestionControl = res.screens.threshold.SCongestionControlScrKeyCongestionControlStat = res.screens.threshold.SCongestionControlStatScrKeyShowNRPC = res.screens.system.SShowNRPCScrKeyNewCallPolicy = res.screens.system.SNewCallPolicyScrKeySBannerDisplay = res.screens.system.SBannerDisplayScrKeyShowSessionDuration = res.screens.session.SShowSessionDurationScrKeySessDurationFilterDlg = res.screens.session.SShowSessionDurationScrKeySessionDisconnectStatistics = res.screens.session.SessionDisconnectStatisticsScrKeySessionSetuptimeStat = res.screens.session.SSessionSetuptimeStatScrKeyPortMonitor = res.screens.portmonitor.SPortMonitorScrKeyNetworkReachability = res.screens.nr.SNetworkReachabilityScrKeyNrConfig = res.screens.nr.SNrConfigScrKeySShowVMGAll = res.screens.vmg.SShowVMGAllScrKeySShowVMGInterfaces = res.screens.vmg.SShowVMGInterfacesScrKeySShowVMGGCPStat = res.screens.vmg.SShowVMGGCPStatScrKeyVMGgpdsps = res.screens.vmg.SVMGgpdspsScrKeyGTPCInfo = res.screens.gtpc.SGTPCInfoScrKeyGTPCCounters = res.screens.gtpc.SGTPCCountersScrKeyGTPCSummary = res.screens.gtpc.SGTPCSummaryScrKeyGTPCSession = res.screens.gtpc.SGTPCSession
> | ScrKeyAlarmScheduler = res.screens.alarm.SAlarmSchedulerScrIDGraphConfig = res.graphs.SGraphConfigScrKeyGraphFilter = res.graphs.SGraphFilterScrKeyGraphScreen = res.graphs.SGraphScreenScrKeyIPPoolDetail = res.screens.vpn.IPPoolScrKeyIMGFileBrowser = res.screens.softupgrade.SIMGFileBrowserScrKeyShowGTPPStorageServerCounters = res.screens.gtpp.SSCounterDialogScrKeyOSPFExceptionHandler = res.screens.ospf.SOSPFExceptionHandlerScrKeyShowOSPFInformation = res.screens.ospf.SShowOSPFInformationScrKeyShowOSPFInterface = res.screens.ospf.SShowOSPFInterfaceScrKeyShowOSPFNeighbor = res.screens.ospf.SShowOSPFNeighborScrKeyOSPFConfiguration = res.screens.ospf.SOSPFConfigurationScrKeyModifyOSPFConfiguration = res.screens.ospf.SModifyOSPFConfigurationScrKeySDHCPExcpHandler = res.screens.dhcp.SDHCPExcpHandlerScrKeySDHCPServiceConfig = res.screens.dhcp.SDHCPServiceConfigScrKeySDHCPDetails = res.screens.dhcp.SDHCPDetailsScrKeySDHCPShowConfig = res.screens.dhcp.SDHCPShowConfigScrKeyUDR = res.screens.cdr.SCDRScrKeyUDRConfig = res.screens.cdr.SCDRConfigScrKeyShowOSPFBorderRouters = res.screens.ospf.SShowOSPFBorderRoutersScrKeyShowOSPFRoute = res.screens.ospf.SShowOSPFRouteScrKeyShowOSPFDatabase = res.screens.ospf.SShowOSPFDatabaseScrKeyShowOSPFDebugging = res.screens.ospf.SShowOSPFDebuggingScrKeySPIOTiming=res.screens.csp.SSPIOTimingScrKeyQosNpuStats=res.screens.npu.SQosNpuStatsScrKeyShowQoSNPUTrafficBanwidth = res.screens.npu.SShowQoSNPUTrafficBandwidthScrKeySQosnpuConfig = res.screens.npu.SQosnpuConfigScrKeyIPOSPFInterface = res.screens.ospf.SIPOSPFInterface
> | ScrKeyModifyIPOSPFInterface = res.screens.ospf.SModifyIPOSPFInterfaceScrKeySDHCPStatistics = res.screens.dhcp.SDHCPStatisticsScrKeyModifyOSPFDebugging = res.screens.ospf.SModifyOSPFDebuggingScrKeyOSPFAreaConfiguration = res.screens.ospf.SOSPFAreaConfigurationScrKeyVirtualLinks = res.screens.ospf.SVirtualLinksScrKeyModifyOSPFAreaConfiguration = res.screens.ospf.SModifyOSPFAreaConfigurationScrKeyBoundPortCounters = res.screens.csp.SBoundPortCountersScrKeyIsakmpKeepAlive = res.screens.ipsec.SIsakmpKeepAliveScrKeyCryptoGroupConfig = res.screens.ipsec.SCryptoGroupConfigScrKeyCryptoGroup = res.screens.ipsec.SShowCryptoGroupScrKeyModifySchema = res.screens.bulkstatistics.SModifySchemaScrKeyShowOSPFNeighborDetail = res.screens.ospf.SShowOSPFNeighborDetailScrKeySDHCPInfo = res.screens.dhcp.SDHCPInfoScrKeyModifyFileSystem = res.screens.softupgrade.SModifyFileSystemScrKeyChargingService = res.screens.chargingservice.SChargingServiceScrKeyModifyChargingServiceConfig = res.screens.chargingservice.SChargingServiceScrKeyCSService = res.screens.css.SCSServiceScrKeyCSServiceConfig =res.screens.css.SAddCSServiceScrKeyCSSServer =res.screens.css.SCSSServerScrKeyCSSServerConfig=res.screens.css.SCSSServerConfigScrKeyCSSDelSeq =res.screens.css.SCSSDeliverySequenceScrKeyCSSDelSeqConfig =res.screens.css.SCSSDeliverySequenceConfigScrKeySGlobalConfiguration =res.screens.chargingservice.SGlobalConfigurationScrKeySCSDetails=res.screens.chargingservice.SCSDetailsScrKeyChargingServiceFlows=res.screens.chargingservice.SChargingServiceFlowsScrKeyChargingServiceSessions = res.screens.chargingservice.SChargingServiceSessions
> | ScrKeyChargingServiceManagerStats = res.screens.chargingservice.SChargingServiceManagerStatsScrKeyIPAccessGroupStatistics=res.screens.vpn.SIPAccessGroupStatisticsScrKeyCommonClass=res.utils.SCommonClassScrKeySDataHandler=res.utils.SDataHandlerScrKeyAAARADIUSCharging = res.screens.aaa.SRADIUSChargingScrKeyAAARADIUSChargingConfig = res.screens.aaa.SRADIUSChargingScrKeyEDR = res.screens.cdr.SEDRScrKeyEDRConfig = res.screens.cdr.SEDRConfigScrKeyShowASInfo=res.screens.vmg.SShowASInfoScrKeyAsSigRoute=res.screens.vmg.SAsSigRouteScrKeyAsSigRouteConfig=res.screens.vmg.SAsSigRouteConfigScrKeyAsSigSIP=res.screens.vmg.SAsSigSIPScrKeyAsSigSIPConfig=res.screens.vmg.SAsSigSIPConfigScrKeyApplicationServer = res.screens.vmg.SApplicationServerScrKeyApplicationServerConfig = res.screens.vmg.SApplicationServerConfigScrKeyAsAppDB = res.screens.vmg.SAsAppDBScrKeyAsAppDBConfig = res.screens.vmg.SAsAppDBConfigScrKeyAsAppVim = res.screens.vmg.SAsAppVimScrKeyAsAppVimConfig=res.screens.vmg.SAsAppVimConfigScrKeyAsAppChatConf = res.screens.vmg.SAsAppChatConfScrKeyAsAppChatConfConfig=res.screens.vmg.SAsAppChatConfConfigScrKeySShowVMGPacketizers=res.screens.vmg.SShowVMGPacketizersScrKeyAsChatConfTable=res.screens.vmg.SAsChatConfTableScrKeyAsChatConfTableConfig=res.screens.vmg.SAsChatConfTableConfigScrKeyVMGCall=res.screens.vmg.SShowVMGCallScrKeySShowVMGConnections=res.screens.vmg.SShowVMGConnectionsScrKeyVMG=res.screens.vmg.SVMGScrKeyVMGConfig=res.screens.vmg.SVMGConfigScrKeySShowASAnnouncements=res.screens.vmg.SShowASAnnouncementsScrKeyVMGgpdsps= res.screens.vmg.SVMGgpdsps
> | ScrKeyVMGVop = res.screens.vmg.SVMGVopScrKeyVMGVopConfig = res.screens.vmg.SVMGVopConfigScrKeyVmgMms = res.screens.vmg.SVmgMmsScrKeyVmgMmsConfig=res.screens.vmg.SVmgMmsConfigScrKeyVMGres=res.screens.vmg.SVMGresScrKeyVMGGcp = res.screens.vmg.SVMGGcpScrKeyVMGGcpConfig = res.screens.vmg.SVMGGcpConfigScrKeyPrepaid3GPP2Statistics = res.screens.session.SPrepaid3GPP2StatisticsScrKeyRemoteServerList = res.screens.vpn.SRemoteServerListScrKeyConfigRemoteServerList = res.screens.vpn.SConfigRemoteServerListScrKeyAsDis = res.screens.vmg.SAsDisScrKeyAsDisConfig=res.screens.vmg.SAsDisConfigScrKeyShowAsConf=res.screens.vmg.SShowAsConfScrKeyAsAppPtt = res.screens.vmg.SAsAppPttScrKeyAsAppPttConfig=res.screens.vmg.SAsAppPttConfigScrKeyVMGchannel=res.screens.vmg.SVMGchannelScrKeyAsAppVinfo = res.screens.vmg.SAsAppVinfoScrKeyAsAppVinfoConfig=res.screens.vmg.SAsAppVinfoConfigScrKeyIpv4DnsProxy=res.screens.vpn.SDNSProxyCfgScrKeyORBStats=res.screens.security.SORBStatisticsScrKeyDeleteChargingService = res.screens.chargingservice.SChargingServiceScrKeyChargingServiceOprResult = res.screens.chargingservice.SChargingServiceScrKeySTiming=res.screens.vmg.STimingScrKeyDomainConfig=res.screens.contextlist.SDomainConfigScrKeySessionCounters=res.screens.session.SShowSessionCountersScrKeySROHCStatistics=res.screens.ppp.SROHCStatisticsScrKeyIPPolicyForward=res.screens.vpn.SIPPolicyForwardScrKeyModifyIPPolicyForward=res.screens.vpn.SModifyIPPolicyForwardScrKeyMIPIPAssignment=res.screens.mip.SMIPIPAssignmentScrKeyMIPIPAssignmentConfig=res.screens.mip.SMIPIPAssignmentConfigScrKeyEnforceImsi = res.screens.system.SEnforceImsi
> | ScrKeyIPv6Pool = res.screens.ipv6.SIPv6PoolScrKeyIPv6PoolConf = res.screens.ipv6.SIPv6PoolConfScrKeyIPv6PoolDetail = res.screens.ipv6.SIPv6PoolDetailScrKeyIPv6ShowResult = res.screens.ipv6.SShowResultScrKeySRPConfiguration = res.screens.srp.SSRPConfigurationScrKeyModifySRPConfiguration = res.screens.srp.SModifySRPConfigurationScrKeySRPStatistics = res.screens.srp.SSRPStatisticsScrKeySRPCheckPointInfo = res.screens.srp.SSRPCheckPointInfoScrKeySRPInfo = res.screens.srp.SSRPInfoScrKeySRPMonitorInformation = res.screens.srp.SSRPMonitorInformationScrKeySupportDetails = res.screens.system.SShowSupportDetailsScrKeyBatchJobs = res.screens.monitor.SBatchJobsScrKeyShowBGP = res.screens.bgp.ShowBGPScrKeyShowBGPDebugging = res.screens.bgp.ShowBGPDebuggingScrKeyShowBGPNeighbor = res.screens.bgp.ShowBGPNeighborScrKeyShowBGPSummary = res.screens.bgp.ShowBGPSummaryScrKeyConfigUpdateScheduler = res.screens.configupdate.SConfigSchedulerScrKeyScheduledConfigUpdate = res.screens.configupdate.SScheduledConfigScrKeyConfigUpdateFilter = res.screens.configupdate.SFilterScreenScrKeyFileTransfer = res.screens.configupdate.SFileTransferScrKeyBGPConfiguration = res.screens.bgp.SBGPConfigurationScrKeyModifyBGPConfiguration = res.screens.bgp.SModifyBGPConfigurationScrKeyClearIPBGPPeer = res.screens.bgp.SClearIPBGPPeerScrKeyAsPathAccessList = res.screens.bgp.AsPathAccessListScrKeyRouteMapConfiguration = res.screens.bgp.SRouteMapConfigurationScrKeyAddModifyRouteMapConfiguration = res.screens.bgp.SAddModifyRouteMapConfigurationScrKeySConfigCriteria = res.screens.showconfig.SConfigCriteriaScrKeySViewConfig = res.screens.showconfig.SViewConfig
> | ScrKeyShowSystemInfo = res.screens.system.SShowSystemInfoScrKeySearchIPPoolNames = res.screens.vpn.SSearchIPPoolNamesScrKeyAppConfig = res.topology.SApplicationConfigurationScrKeySCrashList = res.screens.crashlist.SCrashListScrKeySCrashInfo = res.screens.crashlist.SCrashInfoScrKeyAddressHoldTimerInformation = res.screens.vpn.SAddressHoldTimerInformationScrKeyPoolAddressInformation = res.screens.vpn.SPoolAddressInformationScrKeySShowSigSipDns = res.screens.vmg.SShowSigSipDnsScrKeyAcsAnalyzerStatistics = res.screens.acs.SAcsAnalyzerStatisticsScrKeyShowAcsSessions = res.screens.acs.ShowAcsSessionsScrKeyShowAcsSessionsFilter = res.screens.acs.ShowAcsSessionsFilterScrKeyShowAcsFlows = res.screens.acs.ShowAcsFlowsScrKeyAcsFlowsFliter = res.screens.acs.ShowAcsFlowsFilterScrKeyShowAcsSubsystem = res.screens.acs.ShowAcsSubsystemScrKeyAsAppVimProfile = res.screens.vmg.SAsAppVimProfileScrKeyAsAppVimProfileConfig = res.screens.vmg.SAsAppVimProfileConfigScrKeyAcsCommonClass=res.screens.acs.SAcsCommonClassScrKeyAcsConf=res.screens.acs.SAcsConfScrKeyAcsOperResults=res.screens.acs.SAcsOperResultsScrKeyAcsCFPolicyConfig=res.screens.acs.SAcsCFPolicyConfigScrKeyAcsRulebaseConfig=res.screens.acs.SAcsRuleBaseConfigScrKeyAcsRuledefConfig=res.screens.acs.SAcsRuleDefConfigScrKeyACS = res.screens.acs.SACSScrKeyACSDetails = res.screens.acs.SACSDetailsScrKeyACSGeneralConfig = res.screens.acs.SACSGeneralConfigScrKeyACSChargingActionConfig = res.screens.acs.SACSChargingActionConfigScrKeyACSEDRConfig = res.screens.acs.SACSEDRConfig
> | ScrKeyACSUDRConfig = res.screens.acs.SACSUDRConfigScrKeyConfirmAttributeDelete = res.screens.acs.SACSEDRConfigScrKeyShowDiameterRoute = res.screens.acs.SShowDiameterRouteScrKeyDHCPTest = res.screens.dhcp.SDHCPTestScrKeyAcsChargingActionStats = res.screens.acs.SAcsChargingActionStatsScrKeyAcsRulebaseStats = res.screens.acs.SAcsRulebaseStatsScrKeyAcsRuledefStats = res.screens.acs.SAcsRuledefStatsScrKeyGTPPStorageServerStatus = res.screens.gtpp.SShowGTPPStorageServerStatusScrKeyHardwareAudit = res.screens.hwinventory.SHardwareAuditScrKeyAddComment = res.screens.hwinventory.SAddCommentScrKeyHardwareFilter = res.screens.hwinventory.SHardwareFilterScrKeyHardwareDetails = res.screens.hwinventory.SHardwareDetailsScrKeyAcsDccaStats = res.screens.acs.SAcsDccaStatsScrKeyAcsDccaConfig = res.screens.acs.SAcsDccaConfigScrKeyRouteMapEntryDetails = res.screens.bgp.SRouteMapEntryDetailsScrKeyDiameter = res.screens.acs.SDiameterScrKeyDiameterConfig = res.screens.acs.SDiameterConfigScrKeyIMGInfo = res.screens.hwinventory.SIMGInfoScrKeyDiameterPeers = res.screens.acs.SDiameterPeersScrKeyDiameterEndpoint = res.screens.acs.SDiameterEndpointScrKeyDiameterStats = res.screens.acs.SDiameterStatsScrKeyProxyDns = res.screens.vpn.SProxyDnsScrKeySelectCounters = res.screens.bulkstatistics.SSelectCountersScrKeySROHCProfile = res.screens.rohc.SROHCProfileScrKeyPeriodicBackup = res.screens.periodicbackup.SPeriodicBackupScrKeyBackupHistory = res.screens.periodicbackup.SBackupHistoryScrKeyFilterScreen = res.screens.periodicbackup.SFilterScreenScrKeyShowRsvpStatistics = res.screens.rsvp.ShowRsvpStatistics
> | ScrKeyShowRsvpCounters = res.screens.rsvp.ShowRsvpCountersScrKeyAlarmInformation = res.screens.alarm.AlarmInformationScrKeyRouteAccessList = res.screens.vpn.RouteAccessListxListScrKeyTrapForwarding = res.screens.alarm.TrapForwardingScrKeySMIPFAHAStatus = res.screens.mip.SMIPFAHAStatusScrKeyIPPrefixList = res.screens.vpn.IPPrefixListScrKeyOfflineUpgrade = res.screens.softupgrade.SOfflineUpgradeScrKeyClassMap = res.screens.vpn.SClassMapScrKeyPolicyMap = res.screens.vpn.SPolicyMapScrKeyPolicyGroup = res.screens.vpn.SPolicyGroupScrKeyIpRoutingMaxPath = res.screens.vpn.IPRoutingMaxPathScrKeyAccessFlowStatistics = res.screens.subscriber.AccessFlowStatisticsScrKeySAcsCreditControlSessionStates = res.screens.acs.SAcsCreditControlSessionStatesScrKeyCscfPeerServer = res.screens.ims.SCscfPeerServerScrKeyCscfPolicy = res.screens.ims.SCscfPolicyScrKeyCscfService = res.screens.ims.SCscfServiceScrKeyCscfSessTemp = res.screens.ims.SCscfSessTempScrKeyCscfRoute = res.screens.ims.SCscfRouteScrKeyCscfACL = res.screens.ims.SCscfAclScrKeyCscfTranslation = res.screens.ims.SCscfTranslationScrKeySendBroadcastMessage = res.screens.security.SBroadcastMessageScrKeySendBroadcastMessageAlert = res.screens.security.SBroadcastMessageScrKeySProtocolConfig = res.screens.p2p.SProtocolConfigScrKeySProtocolAnalysis = res.screens.p2p.SProtocolAnalysisScrKeySP2PGraphView = res.screens.p2p.SP2PGraphViewScrKeySP2PTabularView = res.screens.p2p.SP2PGraphViewScrKeyCscfURN = res.screens.ims.SCscfUrnScrKeySyslog = res.screens.syslog.SSyslogScrKeySyslogConfig = res.screens.syslog.SSyslogConfigScrKeyShowMsg = res.screens.syslog.SShowMsg
> | ScrKeyShowSyslogConf = res.screens.syslog.SShowSyslogConfScrKeyShowSgsnTable = res.screens.ggsn.SGGSNServiceSgsnTableScrKeyShowOspfVirtualLinks=res.screens.ospf.SShowOSPFVirtualLinksScrKeySShowFirewallStatistics = res.screens.firewall.SShowFirewallStatisticsScrKeySRADIUSCounterSummary=res.screens.aaa.SRADIUSCounterSummaryScrKeyOnDemandReportConfig=res.screens.cf.SOnDemandReportConfigScrKeySearchFilter=res.screens.cf.SSearchFilterScrKeyViewStatusReportConfig=res.screens.cf.SViewReportStatusScrKeyReportDetails=res.screens.cf.SReportDetailsScrKeySSGSNMAPStats=res.screens.sgsn.SSGSNMAPStatsScrKeySSGTPUStats=res.screens.sgsn.SSGTPUStatsScrKeySSGTPCStats=res.screens.sgsn.SSGTPCStatsScrKeySSGSNOprPolicy=res.screens.sgsn.SSGSNOprPolicyScrKeySSGSNOprPolicyDetail=res.screens.sgsn.SSGSNOprPolicyScrKeySACSCFCateStatView=res.screens.acs.SACSCFCateStatView.javaScrKeySCFStatistics=res.screens.cf.SCFStatisticsScrKeySCFCategoryDb=res.screens.cf.SCFCategoryDbViewScrKeySSCCPStats=res.screens.sgsn.SSCCPStats

> ‌
> The temip.cfg File
> This configuration file is for a flat-file based interface between WEM and TEMIP.
> Important: This configuration file is customer-specific and is not operational without the appropriate license. Please contact your local sales representative for additional information.
> The thr.cfg File
> This file contains parameters pertaining to the WEM thread pool.
> Caution: To ensure proper operation of the WEM, do not edit the parameters in these files.
> thr.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> THREAD: This is the configuration file for Thread pool.
> PoolEnable | Flag for enable or disable the thread pool.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Values:
> • | 1 - Thread pool enable
> • | 0 - Thread pool disable
> | 0 | 1 | 0
> Size | Size of the thread pool.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 | 100 | 10
> MaxSize | Maximum size of the thread pool.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | 10 | 100 | 100

> ‌
> The ua.cfg File
> This file contains parameters pertaining to the WEM support for the ANSI T1.276 security specification. These include parameters granting and restricting access, login failures, password aging, and password complexity.
> Important: Any change in the configuration files will restart the server resulting in client restart.
> ua.cfg File Parameters

> Key | Description | Minimum Value | Maximum Value | Default Value
> Security: This file contains the list of security parameters for user access to WEM.
> AllowIpAddress | List of allowed IP addresses and mask.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> IP address 0.0.0.0: Allows all addresses Format: Allow IP address/subnet-mask number, IP address/subnet-mask number...Nothing: Allow nothing | -- | -- | --
> DenyIpAddress | List of deny IP addresses and mask.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> IP address 0.0.0.0: Deny all Addresses Format: Deny IP address/subnet-mask number, IP address/subnet-mask number...Nothing in list: Deny nothing | -- | -- | --
> ConsecutiveFailLogin | The system limit on consecutive failed login for a given user ID shall be configurable.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Value 0: No limit | 0 | 10 | 5
> LockOutInterval | Locked out login ID, automatically, following the crossing of a configurable timeframe. Value is in minutes.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Value 0: No lock out | 0 | 1440 | 60
> AlertExpiryThreshold | The account alert expiry threshold after WEM generates an alert. Value is in days.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Value 0: No alert | 0 | 30 | 10
> MinPasswordChangeInterval | Passwords will be user changeable at the user's discretion following a configurable minimum interval since the last change. Value is in seconds.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Value 0: No interval | 0 | 86400 | 86400
> NumOfPasswordInHistory | System will support a password history to prevent password reuse. The parameters will be configurable with a default of at least the past five password iterations.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Value 0: No password history | 0 | 10 | 5
> PasswordInHistoryAtLeast | System will support a password history to prevent password reuse. The parameters will be configurable with a default of at least the past 180 days.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Value 0: No expiry | 0 | 365 | 180
> EMSAdminMailId | E-mail address of the WEM account created/reset password notification originator.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | -- | -- | No default value
> PasswordComplexityRules | This flag indicates which rules should be used to verify password complexity.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values:
> • | 0: None
> • | 1: ANSI
> | -- | -- | 1
> PasswordMinLength | This flag sets the minimum length of a user-defined password.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | PasswordComplexityRules = None
> 1 | 63 | 8
> PasswordComplexityRules = ANSI
> 3 | 63 | 8
> PasswordMinCharChange | This flag defines the minimum number of characters that must be changed when a user changes the password.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> | If PasswordComplexityRules is None, then do not check this. (Value is 0) |  |
> |  | PasswordComplexityRules = ANSI |  |
> |  | 0 | 8 | 2
> ChangePasswordOnNextLogin | If this flag enabled then, on next login, the user will be required to change the password. Else, the user will not be required to change the password.
> • | Needs a WEM Server restart
> • | Can be changed by the user
> Possible values:
> • | 0: Password change will not be required
> • | 1: Password change will be required
> | -- | -- | 1

> ‌
> The vacuum.cfg File
> This file contains parameters pertaining to PostgreSQL database vacuuming.
> Configuring values for CompleteDB:

> • | If this value is 0, it means that vacuuming needs to be done on all the tables individually.

> • | If this value is 1, it means that vacuuming is done only to the database and not the tables individually.

> vacuum.cfg File Parameters

> Key | Description and Values
> Type: This section describes the type of vacuum to be done on database. |
> VACUUM | This parameter reclaims space and makes it available for re-use. This command can operate in parallel with normal reading and writing of the table, as an exclusive lock is not obtained. This is the default value.
> VACUUM ANALYZE | This parameter performs a VACUUM and then an ANALYZE for each selected table.
> VACUUM FULL | This parameter physically reorders the tables. This requires an exclusive lock on each table while it is being processed. Important: VACUUM FULL is not recommended for routine use.
> Database
> Database Name = hh,hh | First "hh" specifies the starting time to vacuum the database or table Second "hh" specifies the time interval for performing periodic vacuum after the starting time. Default value for database: 12,12Default value for table: 00, 00. This means that do not vacuum the database or table. It means midnight 12 as we have a separate value for the same, that is, 24. Any non-zero value for this will override the CompleteDB flag for this database. For example, if the ConfigDB value is 13 and CompleteDB value for ConfigDB is 0, means that the entire DB will be vacuumed along with all the tables. However, if the timestamp of start of vacuum for the DB and any of the tables conflicts, then, vacuum will not be started for that table, and the DB will get precedence in this case. Max value: 24,24 (24 is same as 12:00 AM) Important: It is not recommended to start table level vacuuming for all tables at the same time as it will increase number of transactions to the database. Database level vacuuming takes care of table level vacuuming, that means it vacuums whole database including all the tables present in that database so at critical point if we want to start vacuuming on all tables at the same time, at that point, we can start only database level vacuum. If we want to vacuum one or more (but not all) tables from the database, in that case we can use table level vacuuming by enabling vacuum for that tables.
> ConfigDB | TrapDB | AuditDB | BulkDB | P2PDB
> 12, 12 | 12, 12 | 12, 12 | 12, 12 | 12, 12
> Table Name = hh,hh | ConfigDB | TrapDB | AuditDB | BulkDB | P2PDB
> | CompleteDB= 1boxer = 00,00portmontable = 00,00boxeruserinfo = 00,00userpreference = 00,00processthreshold = 00,00ippooldefaults = 00,00scbrdefaults = 00,00csmsessioninfo = 00,00bkinfo = 00, 00graphscreeninfo = 00,00batchjobcleanup = 00,00batchjobinfo = 00,00boxeronmap = 00,00dbbackupinfo = 00,00maptable = 00,00p2pinfo = 00,00updateinfo = 00,00userinfo = 00,00dbcurrent = 00,00hostname = 00,00syslogkeywordlist = 00,00syslogmsgfileinfo = 00,00 | CompleteDB= 1trap = 00,00deletedtrap = 00,00forwardinginfo = 00,00forwardpurgeinfo = 00,00mailinfo = 00,00mailmessage = 00,00configure = 00,00schedule = 00,00forwardaddress = 00,00pendingtrap = 00,00trap_current = 00,00trapoperdetails = 00,00 | CompleteDB= 1auditlog = 00,00auditlog_current = 00,00chassisinfo = 00,00cpuinfo = 00,00daughtercardinfo = 00,00hardwareactivity = 00,00hardwareinfo = 00,00lcrccspioinfo = 00,00pactacinfo = 00,00rowcount = 00,00smcinfo = 00,00spccardinfo = 00,00imglastevtgentime = 00,00 | CompleteDB= 1card = 00,00card_current = 00,00port = 00,00port_current = 00,00system = 00,00system_current = 00,00ppp = 00,00ppp_current = 00,00mipfa = 00,00mipfa_current = 00,00mipha = 00,00mipha_current = 00,00rp = 00,00rp_current = 00,00gtpc = 00,00gtpc_current = 00,00gtpp = 00,00gtpp_current = 00,00ippool = 00,00ippool_current = 00,00apn = 00,00apn_current = 00,00lac = 00,00lac_current = 00,00closedrp = 00,00closedrp_current = 00,00 | CompleteDB= 1bwstat = 00,00bwstat_current = 00,00dailystat = 00,00dailystat_current = 00,00hourlystat = 00,00hourlystat_current = 00,00protocolstat = 00,00protocolstat_current = 00,00scbrdailystats = 00,00scbrdailystats_current = 00,00scbrhourlystats = 00,00scbrhourlystats_current = 00,00scbrstats = 00,00scbrstats_current = 00,00tempp2p = 00,00thresholdstats = 00,00
> |  |  |  | radius = 00,00radius_current = 00,00imgaccess = 00,00ecs = 00,00ecs_current = 00,00misc = 00,00misc_current = 00,00ipsg = 00,00ipsg_current = 00,00asngw = 00,00asngw_current = 00,00sgsn = 00,00sgsn_current = 00,00sgtp = 00,00sgtp_current = 00,00sccp = 00,00sccp_current = 00,00ss7rd = 00,00ss7rd_current = 00,00mipv6ha = 00,00mipv6ha_current = 00,00context = 00,00context_current = 00,00cscf = 00,00cscf_current = 00,00ss7link = 00,00ss7link_current = 00,00gprs = 00,00gprs_current = 00,00 |

> ‌
> The wblist.cfg File
> This file provides information on the white black list database file paths that are mainly used for content filtering.
> wblist.cfg File Parameters

> Key | Description
> WBLIST: This section describes the parameters that store Content Filtering Server information.
> WblistPath | White Black list file path: This specifies the path where white black list database files are located. WblistPath = ./flash/cf/cfdatabases/wblistdb/

> ‌
> Appendix D
> XML Output Formats
> This appendix provides information about the various eXtensible Markup Language (XML) file format definitions in the Bulkstat server. The XML file format definition is based on XML schema. The 3GPP standards are followed to generate XML report files in the XML report generator. These defined file format definitions correspond to each other (except for some minor XML specific optimizations).
> This chapter includes the following topics:

> • | Supported XML Output Formats

> • | Examples of XML Output Formats

> • | File Naming Conventions

> • | Supported Standards

> • | Understanding WEM Bulk Statistics Output in XML Reports

> Important: Unless otherwise specified, all information in this chapter applies to both Sun Solaris- and Red Hat Enterprise Linux-based WEM systems.
> Supported XML Output Formats
> The following XML output formats are supported:

> • | DTD Based Format: This format is DTD based and it can be enabled/disabled using the configurable parameter, ‘XMLFileFormat’ provided in the configuration file bsserver.cfg in the /<ems_dir>/etc directory.

> • | 3GPP Format: This is the new and default 3GPP recommended format to generate the XML report file. This format reduces the XML file size.

> WEM generates two types of files for the above two formats. These are individual XML files for all subsystems and single XML file for all subsystems which can be configured using the parameter ‘XMLFileType’ in the bsserver.cfg file.
> Refer Appendix B for information on the configurable parameters in the bsserver.cfg file.
> Examples of XML Output Formats
> This section provides the sample outputs for the DTD based and 3GPP XML formats.
> DTD Based Format
> This following output is an example of individual files for all subsystems in DTD based XML format.
> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
> <!DOCTYPE mdc SYSTEM "MeasurementStat.dtd">
> <?xml-stylesheet type="text/xsl" href="simple_table.xsl" ?>
> <mdc>
> <mfh>
> <ffv>2</ffv>
> <sn>Starent Network Inc.</sn>
> <st>MSC</st>
> <vn>Samsung corp.</vn>
> <cbt>2006-01-03 13:10:00</cbt>
> </mfh>
> <md>
> <neid>
> <neun></neun>
> <nedn></nedn>
> <nesw></nesw>
> </neid>
> <mi>
> <mts>2006-01-03 13:15:00</mts>
> <gp>300</gp>
> <rsf>false</rsf>
> <ms>
> <msn>CardStat</msn>
> <sf>false</sf>
> <es>false</es>
> <mt p="0">card</mt>
> <mt p="1">cpubusy</mt>
> <mt p="2">cpuidle</mt>
> <mt p="3">numproc</mt>
> <mt p="4">memused</mt>
> <mt p="5">memtotal</mt>
> <mv>
> <moid> card=17 </moid>
> <r p="0">6</r>
> <r p="1">0.76</r>
> <r p="2">99.24</r>
> <r p="3">158</r>
> <r p="4">1057704</r>
> <r p="5">4194304</r>
> </mv>
> <mv>
> <moid> card=8 </moid>
> <r p="0">8</r>
> <r p="1">0.45</r>
> <r p="2">99.55</r>
> <r p="3">65</r>
> <r p="4">306512</r>
> <r p="5">1048576</r>
> </mv>
> </ms>
> </mi>
> </md>
> <mff>
> <ts>2006-01-03 13:15:00</ts>
> </mff>
> </mdc>
> This following output is an example of all subsystems in a single file in DTD based XML format.
> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
> <!DOCTYPE mdc SYSTEM "MeasurementStat.dtd">
> <?xml-stylesheet type="text/xsl" href="simple_table_all.xsl" ?>
> <mdc>
> <mfh>
> <ffv>2</ffv>
> <sn>Starent Network Inc.</sn>
> <st>MSC</st>
> <vn>Samsung corp.</vn>
> <cbt>2006-01-03 13:10:00</cbt>
> </mfh>
> <md>
> <neid>
> <neun></neun>
> <nedn></nedn>
> <nesw></nesw>
> </neid>
> <mi>
> <mts>2006-01-03 13:15:00</mts>
> <gp>300</gp>
> <rsf>false</rsf>
> <ms>
> <msn>CardStat</msn>
> <sf>false</sf>
> <es>false</es>
> <mt p="0">card</mt>
> <mt p="1">cpubusy</mt>
> <mt p="2">cpuidle</mt>
> <mt p="3">numproc</mt>
> <mt p="4">memused</mt>
> <mt p="5">memtotal</mt>
> <mv>
> <moid> card=17 </moid>
> <r p="0">17</r>
> <r p="1">0</r>
> <r p="2">100</r>
> <r p="3">0</r>
> <r p="4">0</r>
> <r p="5">0</r>
> </mv>
> <mv>
> <moid> card=8 </moid>
> <r p="0">8</r>
> <r p="1">0.45</r>
> <r p="2">99.55</r>
> <r p="3">65</r>
> <r p="4">306512</r>
> <r p="5">1048576</r>
> </mv>
> </ms>
> <ms>
> <msn>PortStat</msn>
> <sf>false</sf>
> <es>false</es>
> <mt p="0">card</mt>
> <mt p="1">port</mt>
> <mt p="2">rxbytes</mt>
> <mt p="3">txbytes</mt>
> <mt p="4">ucast_inpackets</mt>
> <mt p="5">ucast_outpackets</mt>
> <mt p="6">mcast_inpackets</mt>
> <mt p="7">mcast_outpackets</mt>
> <mt p="8">bcast_inpackets</mt>
> <mt p="9">bcast_outpackets</mt>
> <mt p="10">rxpackets</mt>
> <mt p="11">txpackets</mt>
> <mt p="12">rxdiscbytes</mt>
> <mt p="13">rxdiscpackets</mt>
> <mt p="14">txdiscbytes</mt>
> <mt p="15">txdiscpackets</mt>
> <mt p="16">maxrate</mt>
> <mt p="17">frag-rcvd</mt>
> <mt p="18">pkt-reassembled</mt>
> <mt p="19">frag-tokernel</mt>
> <mv>
> <moid> card=17,port=1 </moid>
> <r p="0">17</r>
> <r p="1">1</r>
> <r p="2">43346</r>
> <r p="3">1792</r>
> <r p="4">328</r>
> <r p="5">28</r>
> <r p="6">0</r>
> <r p="7">0</r>
> <r p="8">1</r>
> <r p="9">0</r>
> <r p="10">329</r>
> <r p="11">28</r>
> <r p="12">0</r>
> <r p="13">0</r>
> <r p="14">0</r>
> <r p="15">0</r>
> <r p="16">0</r>
> <r p="17">0</r>
> <r p="18">0</r>
> <r p="19">0</r>
> </mv>
> </ms>
> <ms>
> <msn>IPPoolStat</msn>
> <sf>false</sf>
> <es>false</es>
> <mt p="0">vpnname</mt>
> <mt p="1">vpnid</mt>
> <mt p="2">name</mt>
> <mt p="3">used</mt>
> <mt p="4">hold</mt>
> <mt p="5">release</mt>
> <mt p="6">free</mt>
> <mt p="7">type</mt>
> <mt p="8">priority</mt>
> <mt p="9">state</mt>
> <mv>
> <moid> vpnname=network,vpnid=2,name=Pool </moid>
> <r p="0">network</r>
> <r p="1">2</r>
> <r p="2">Pool</r>
> <r p="3">0</r>
> <r p="4">0</r>
> <r p="5">0</r>
> <r p="6">254</r>
> <r p="7">S</r>
> <r p="8">0</r>
> <r p="9">G</r>
> </mv>
> </ms>
> </mi>
> </md>
> <mff>
> <ts>2006-01-03 13:15:00</ts>
> </mff>
> </mdc>
> 3GPP Format
> This following output is an example of individual files for all subsystems in 3GPP XML format.
> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
> <!--?xml-stylesheet type="text/xsl" href="MeasDataCollection.xsl?"-->
> <measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec">
> <fileHeader dnPrefix="Unknown" fileFormatVersion="2" vendorName="Sagar">
> <fileSender elementType="Nikhil" localDn="Same"/>
> <measCollec beginTime="2008-04-25 04:40:00"/>
> </fileHeader>
> <measData>
> <managedElement localDn="Same" swVersion="7.1.19504" userLabel="st16"/>
> <measInfo>
> <job jobId="7381"/>
> <granPeriod duration="PT300S" endTime="2008-04-25 04:45:00"/>
> <msn>CardStat</msn>
> <suspect>false</suspect>
> <measTypes>card cpubusy cpuidle numproc memused memtotal</measTypes>
> <measValue measObjLdn="card=22">
> <measResults>22 0 100 0 0 0</measResults>
> </measValue>
> <measValue measObjLdn="card=24">
> <measResults>24 0 100 0 0 0</measResults>
> </measValue>
> </measInfo>
> </measData>
> <fileFooter>
> <measCollec endTime="2008-04-25 04:45:00"/>
> </fileFooter>
> </measCollecFile>
> This following output is an example of all subsystems in a single file in 3GPP XML format.
> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
> <!--?xml-stylesheet type="text/xsl" href="MeasDataCollection.xsl?"-->
> <measCollecFile xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec http://www.3gpp.org/ftp/specs/archive/32_series/32.435#measCollec">
> <fileHeader dnPrefix="Unknown" fileFormatVersion="2" vendorName="Sagar">
> <fileSender elementType="Nikhil" localDn="Same"/>
> <measCollec beginTime="2008-04-25 04:40:00"/>
> </fileHeader>
> <measData>
> <managedElement localDn="Same" swVersion="7.1.19504" userLabel="st16"/>
> <measInfo>
> <job jobId="7381"/>
> <granPeriod duration="PT300S" endTime="2008-04-25 04:45:00"/>
> <msn>CardStat</msn>
> <suspect>false</suspect>
> <measTypes>card cpubusy cpuidle numproc memused memtotal</measTypes>
> <measValue measObjLdn="card=22">
> <measResults>22 0 100 0 0 0</measResults>
> </measValue>
> <measValue measObjLdn="card=24">
> <measResults>24 0 100 0 0 0</measResults>
> </measValue>
> <msn>PortStat</msn>
> <suspect>false</suspect>
> <measTypes>card port rxbytes txbytes ucast_inpackets ucast_outpackets mcast_inpackets mcast_outpackets bcast_inpackets bcast_outpackets rxpackets txpackets rxdiscbytes rxdiscpackets txdiscbytes txdiscpackets maxrate frag-rcvd pkt-reassembled frag-tokernel</measTypes>
> <measValue measObjLdn="card=22,port=1">
> <measResults>22 1 1236 1024 16 16 0 0 2 0 18 16 0 0 0 0 100000000 0 0 0</measResults>
> </measValue>
> <measValue measObjLdn="card=22,port=2">
> <measResults>22 2 212 0 0 0 0 0 2 0 2 0 0 0 0 0 100000000 0 0 0</measResults>
> </measValue>
> <msn>IPPoolStat</msn>
> <suspect>false</suspect>
> <measTypes>vpnname vpnid name startaddr groupname used hold release free type priority state</measTypes>
> <measValue measObjLdn="vpnname=egress,vpnid=6,name=dynamic,startaddr=17.0.0.1,groupname=">
> <measResults>egress 6 dynamic 17.0.0.1 0 0 0 65534 P 0 G</measResults>
> </measValue>
> <measValue measObjLdn="vpnname=egress,vpnid=6,name=static,startaddr=18.0.0.1,groupname=">
> <measResults>egress 6 static 18.0.0.1 0 0 0 65534 S 0 G</measResults>
> </measValue>
> </measInfo>
> </measData>
> <fileFooter>
> <measCollec endTime="2008-04-25 04:45:00"/>
> </fileFooter>
> </measCollecFile>
> File Naming Conventions
> The naming conventions for the files are as per 3GPP standard. The naming convention is different only for individual subsystem files where we include subsystem names in the file name (for example, “CardStat”, “PortStat”, etc.).
> The following convention will be applied for measurement result file naming:
> <Type><Startdate>.<Starttime>-[<Enddate>.]<Endtime>_[<UniqueId>][:<RC>]

> Field Name | Description
> Type | Indicates if the file contains measurement results for single or multiple NEs and/or granularity periods, where:
> • | “A” indicates single NE, single granularity period;
> • | “B” indicates multiple NEs, single granularity period;
> • | “C” indicates single NE, multiple granularity periods;
> • | “D” indicates multiple NEs, multiple granularity periods.
> Startdate | Indicates the date when the granularity period began if the Type field is set to “A” or “B”. If the Type field is either “C” or “D” then, Startdate contains the date when the first granularity period of the measurement results contained in the file started. The Startdate field is of the form YYYYMMDD, where:
> • | YYYY is the year in four digit notation;
> • | MM is the month in two digit notation (01-12);
> • | DD is the day in two digit notation (01-31).
> Starttime | Indicates the time when the granularity period began if the Type field is set to A or B. If the Type field is either “C” or “D” then, Starttime contains the time when the first granularity period of the measurement results contained in the file began. The Starttime field is of the form HHMMshhmm, where:
> • | HH is the two digit hour of the day (local time), based on 24 hour clock (00-23);
> • | MM is the two digit minute of the hour (local time), possible values are 00, 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, and 55;
> • | s is the sign of the local time differential from UTC (+ or -), in case the time differential to UTC is 0 then the sign may be arbitrarily set to “+” or “-”;
> • | hh is the two digit number of hours of the local time differential from UTC (00-23);
> • | mm is the two digit number of minutes of the local time differential from UTC (00-59).
> Enddate | This field will only be included if the Type field is set to “C” or “D”, that is, measurement results for multiple granularity periods are contained in the file. It identifies the date when the last granularity period of these measurements ended, and its structure corresponds to the Startdate field.
> Endtime | Indicates the time when the granularity period ended if the Type field is set to A or B. If the Type field is either “C” or “D” then, Endtime contains the time when the last granularity period of the measurement results contained in the file ended. Its structure corresponds to the Starttime field, however, the allowed values for the minute of the hour are 05, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, and 00.
> UniqueId | This is the name of the NE, EM or domain (for example, a distinguishedName). The field may be omitted only if the distinguishedName is not available from the CM applications.
> RC | This parameter is a running count, starting with the value of “1”, and will be appended only if the filename is not unanimous, that is, more than one file is generated and all other parameters of the file name are identical. Therefore, it may only be used by the Network Element Manager (EM), since the described situation can not occur with Network Element (NE) generated files.

> ‌
> A few examples describing the file naming convention are as follows:

> • | File name: A20000626.2315+0200-2330+0200_NodeBId;

> Meaning: File produced by NodeB <NodeBId> on June 26, 2000, granularity period 15 minutes from 23:15 local to 23:30 local, with a time differential of +2 hours against UTC.

> • | File name: B20021224.1700-1130-1705-1130_EMId,

> Meaning: File containing results for multiple NEs, produced by EM <EMId> on December 24, 2002, granularity period 5 minutes from 17:00 local to 17:05 local, with a time differential of –11:30 hours against UTC.

> • | File name: D20050907.1030+0000-20050909.1500+0000_DomainId:2,

> Meaning: File containing results for NEs belonging to domain <DomainId>, start of first granularity period 07 September 2005, 10:30 local, end of last granularity period 09 September 2005, 15:00 local, with a time differential of 0 against UTC. This file is produced by the EM managing the domain, and it is the second file for this domain/granularity periods combination.
> Supported Standards
> WEM complies with the following 3rd Generation Partnership Project (3GPP) standards for generation of XML report files in DTD based format and 3GPP format respectively.

> • | 3GPP TS 32.401 V4.1.0 (2001-12): “Concept and Requirements”

> • | 3GPP TS 32.435 V6.2.0 (2006-03): “Performance measurement: eXtensible Markup Language (XML) file format definition”

> Understanding WEM Bulk Statistics Output in XML Reports
> WEM can be configured to generate bulk statistics reports in XML format at user-defined intervals. The reports generate statistical output based on the bulk statistic type (Counter or Gauge) and its availability (e.g., per context, per service, per APN or across all services on the system). For bulk statistics of type “Incremental,” WEM will calculate and generate a delta value. For bulk statistics of type “Gauge,” WEM always provides the absolute value.
> Important: A bulk statistic type of 'Counter' is referred to as an 'Incremental Counter' in WEM files.
> How WEM Parses Bulk Statistic Data
> The ASR 5000 chassis keeps a running aggregate total of bulk statistics configured for collection. The total continues to increase until the counters are cleared or the chassis is reset. However, the XML reports generated by WEM do not provide a running aggregate total for each statistical value of a counter of type “Incremental.” Instead, WEM performs a calculation on each bulk statistic counter configured for the XML report so that only the incremental value for a configured time interval appears in the generated report.
> Once bulk statistic generation is enabled, WEM uses the first configured report interval to obtain the raw statistical value for each configured bulk statistic. This first group of statistical values will be used by the system as a reference value for each of the bulk statistics configured to appear in the report. WEM does not generate a report based on this first group of reference values.
> When the second configured report interval is reached, WEM obtains the raw statistical value from the ASR 5000 chassis, compares those values to the reference values obtained from the first interval, and outputs the delta to the XML report. This process continues for each scheduled time interval, with the latest interval’s statistical output being compared against the previous one, and the delta being generated in succeeding XML reports.
> Important: WEM must be able to reference two consecutive bulk statistics collection records before it can generate an XML report. If two consecutive records are not found, WEM does not generate a report.
> Example
> In this example, a WEM user has enabled bulk statistic collection to occur at 15-minute intervals beginning at 11:00. WEM will then use the information gathered from the ASR 5000 to calculate the incremental totals for each 15-minute interval and output them to reports in XML format.

> 1. | At 11:00, WEM stores the raw statistical reference value for the bulk statistics obtained from the ASR 5000. An XML report is not generated.

> 2. | At 11:15, WEM obtains the raw statistical bulk statistics values for counters of type Incremental and Gauge from the ASR 5000 and compares these to the values obtained at 11:00.

> 3. | For bulk statistics of counter type Incremental, WEM subtracts the stored statistical values of the 11:00 collection from the values obtained at the 11:15 collection. The deltas between the two sets of values are then generated in the XML report. For bulk statistics of type Gauge WEM performs no delta calculation and outputs the absolute value to the XML report.

> 4. | During each of the succeeding report intervals, WEM obtains the raw statistical values of counter type “Incremental” from the chassis and subtracts the previous report’s value from them to calculate and generate the XML output. Bulk statistics of type “Gauge” are always generated as absolute values.

> Example: Incremental Bulk Statistic Calculations for a WEM XML Report

> Report Number | Time | Raw Bulk Statistic Value | Value Generated in XML Report
> n/a | 11:00 | 100 | Raw reference value obtained. No XML report is generated.
> 1 | 11:15 | 200 | 100 (200-100=100)
> 2 | 11:30 | 400 | 200 (400-200=200)
> 3 | 11:45 | 1000 | 600 (1000-400=600)
> 4 | 12:00 | 1500 | 500 (1500-1000=500)

> ‌
> Sample XML Bulk Statistics Report
> The generated XML report includes the following information:

> • | Start and end time of the bulk statistic collection interval.

> • | The granularity period for bulk statistics collection (in seconds).

> • | The bulk statistic variable names that have been configured to appear in the report.

> • | The context, session, service name or APN name associated with the collected bulk statistics. The identifiers available will vary depending on the bulk statistic schema for which statistics are being collected.

> • | The values for bulks statistics of counter types Incremental and Gauge.

> Example WEM XML Report (3GPP 6.2.0 Format)

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