> SSC Administration
> This chapter provides information and procedures to administer SSC node in PCC deployment.
> SSC is an element of Cisco Policy Charging and Control (PCC) solution. SSC acts as an intelligent database for policy services. By acting as a centralized policy software application engine, SSC complements IPCF for converged session handling.
> Depending upon SSC deployment configuration, administering SSC system involves tasks related to monitoring and administering the interfaces for Sh, Event Notification (EN) and User Data Repository (UDR) applications. SSC uses these interfaces to exchange the subscriber profile or service usage data with respective components of PCC solution. SSC administration also involves tasks related to administering subscriber profile, service plans and data store related to profile and plans.
> This chapter also discusses the pre-requisites for SSC administration.
> This chapter covers following sections for SSC administration:

> • | SSC Administration Overview

> • | Before You Begin SSC Administration

> • | Administering SSC Using Console

> • | Administering Sh Application

> • | User Data Repository (UDR) Administration

> • | Administering Event Notification Application

> • | Monitoring the Performance of SSC Using Console

> • | Profile Administration

> • | Group Administration

> • | Plan Administration

> • | Data Store Administration

> • | Monitoring Security of SSC Using Console

> SSC Administration Overview
> This section briefly describes SSC administration and monitoring tasks.
> In an SSC node deployment scenario all tasks can be divided in following major groups:

> • | Administration

> • | Performance

> • | Security

> Administering SSC involves tasks such as administering users, administering data and service plans for the subscribers, managing the interfaces for various applications that interact with SSC as well as configuring and monitoring alarms, logs and statistics generated by deployment.
> Administering SSC also includes tasks related to profile and usage policy administration for the subscriber. Tasks such as monitoring and administering subscriber profile and groups as well as subscription plans and data stores related to profile and policy fall under this category.
> Important: Profile, plans, group and data store administration tasks are available only when you log-in to SSC Administration Console as a policy administrator or as a user whose credentials include policy administration credentials. For more information refer User Administration section.
> Monitoring performance of SSC involves tasks such as monitoring system logs and statistics as well as monitoring system resources.
> Monitoring the security of SSC involves tasks such as using system audit to monitor the security.
> Before You Begin SSC Administration
> This section includes pre-requisites that must be satisfied and tasks that must be performed before you begin to administer SSC.
> This section includes following sub-sections:

> • | Pre-requisites for SSC Administration

> • | Accessing SSC Administration Console

> • | Checking Status of SSC Application

> • | Starting SSC Application

> • | Checking Status of IMDB Application

> • | Bulk Loading Subscriber Profile Data

> Pre-requisites for SSC Administration
> This section describes the pre-requisites for administering an SSC.
> Following are the pre-requisites for administering SSC:

> • | Status of the database, that is being used by the SSC to store subscriber, subscription and policy related data, must be active.

> • | Status of IMDB application that is being used by SSC to provide the database grid for the cluster deployment, must be active.

> • | Status of SSC application must be active.

> Important: You can verify the status of database and the IMDB, by executing the script sscdbstatus.sh located in the localhome/ssc/install/spr_install/tools directory.

> • | If SSC is deployed in the cluster mode then all the blades in a cluster must be accessible.

> Ensuring Accessibility of Blade Cluster
> Before initiating the administrative tasks for an SSC cluster deployment ensure that the blade cluster is accessible.
> To ensure accessibility of a blade cluster:

> Step 1 | Ping the host names by referring IP map and ensure that the individual host or blades are reachable.

> Step 2 | Check status of the SSC instance on all the blades in cluster. The status should be active on all the blades.

> Step 3 | Check status of the database, on the blades that are configured as primary or secondary database using the dbstatus.sh script. Database status should be active.

> Accessing SSC Administration Console
> This section describes the prerequisites and procedure to access the SSC administration console.
> You can access the SSC Administration Console provided that you satisfy following pre-requisites:

> • | SSC has been installed successfully either on a single host or in cluster mode.

> • | You have root administrative privileges for the host or the cluster of blades.

> • | You have system administrative privileges for the SSC installation.

> Important: PuTTY window must be maximized, if PuTTY application is being used to access SSC console.
> Using SSC Administration Console
> Before initiating the administrative tasks for an SSC cluster deployment using the SSC Administration Console, ensure that you can access this console.
> To access SSC administration console:

> Step 1 | Login to the host with root administrative privileges.

> Step 2 | Invoke system administrative privileges for the SSC node by issuing following command:

> su – sscadmin

> Step 3 | Execute SSC administration script by issuing following command:

> ./sscadm
> SSC Administration Console window appears.

> Step 4 | Specify login and password of appropriate user level.

> The console displays appropriate status messages in the message window.
> Checking Status of SSC Application
> This section describes the procedure to view the status of SSC application.
> Viewing Status of an SSC Application
> All SSC components run as independent processes. SSC allows you to check the status of each such process.
> To view status of an SSC application:

> Step 1 | Login with SSC Administrative privileges.

> Step 2 | Check the status of SSC application instance by issuing following command:

> ./sscadm status
> SSC displays current status of its various components such as Heart beat daemon, Login daemon, System manager and Scheduler. For each process the running status indicates that corresponding component is active and running.
> Important: You can also use the system status option from the SSC Administration Console to view current status of SSC service instance.
> Starting SSC Application
> This section describes the procedure to start an instance of SSC application.
> Starting an SSC Application Instance
> All SSC components run as independent processes. SSC provides a script to start or stop an application instance.
> To start an SSC application instance:

> Step 1 | Login with SSC Administrative privileges.

> Step 2 | Start SSC application instance by issuing following command:

> ./sscadm start
> SSC initiates its various components such as Heart beat daemon, Login daemon, System manager and Scheduler.

> Step 3 | Use status command to ensure that all SSC components are started successfully.

> Important: You can also use the system status option from the SSC Administration Console to view current status of SSC service instance as well as to start or stop an instance.
> Checking Status of IMDB Application
> This section describes the procedure to check status of IMDB application.
> Viewing Status of IMDB Application
> In a cluster deployment of SSC, the IMDB application provides a grid that can be used to access the database. Hence, all the instances of this application needs to be active and running for normal functioning of an SSC cluster.
> To view status of an IMDB application:

> Step 1 | Get the names of IMDB instances, by starting the SSC instance if it is not active by issuing following command:

> ./sscadm start

> Step 2 | Access the file ..\etc\system.cfg from SSC installation directory.

> Step 3 | Note the names of IMDB and database instances from the file mentioned in previous step.

> Step 4 | To ensure that these instances are active, login with SSC administrative privileges.

> Step 5 | Check the status of IMDB instances by issuing following command:

> ./<IMDB_App>status
> SSC displays a list of active connections to the data store. For each active connection it displays Type of connection, Process Id (PID), Context and Name of the connection along with its Connection Id (ConId). Names of database and IMDB application instances will be displayed here, if these instances are active.

> Step 6 | Ensure that a message that indicates that replication agent is running, is displayed while verifying the status of IMDB application using following command:

> <IMDB_App> status
> Bulk Loading Subscriber Profile Data
> This section describes the procedure to bulk load subscriber profile data.
> Bulk Loading Subscriber Profile Data
> SSC provides a script to bulk load subscriber profile data that is available in CSV format, to the subscribe database.
> SSC provides a script to bulk load subscriber profile data, if such data is available in CSV format. Refer to Bulk Load Provisioning feature in Overview chapter for more information regarding structure and nomenclature of the CSV file containing profile data.
> To bulk load subscriber profile data:

> Step 1 | Login to SSC deployment with administrative privileges.

> Step 2 | From SSC installation folder, access the script../tools/bulk_sub_load.

> Step 3 | View more information about this script and its syntax by issuing command:

> bulk_load_sub – h

> Step 4 | Provide information about location and name of CSV file that contains profile data, by issuing command:

> bulk_load_sub – f <file_Pname>
> .
> Important: The time required to execute this procedure depends on the amount of data available in comma separated value form in sub_load.txt file.

> Step 5 | SSC Administration Console loads this data in appropriate table in the database.

> Administering SSC Using Console
> This section describes the procedures and methods to use the SSC Administration Console, to perform administrative tasks for SSC.
> The SSC Administration Console displays current status of an SSC instance as well as starts or stops the SSC instance and displays appropriate messages.
> Important: PuTTY window must be maximized, if PuTTY application is being used to access SSC console.
> This section includes following sub-sections:

> • | System Status Monitoring

> • | User Administration

> • | Interface Management

> • | SSC Logs Administration

> • | SNMP Traps and Alarms Configuration

> • | Bulk Statistics Configuration

> • | Subscriber Profile Repository (SPR) Configuration

> • | Configuration Management

> • | Profile Controller Configuration

> • | Policy Provisioning Tool (PPT) Configuration

> System Status Monitoring
> This section describes procedures to view current status of the system along with active tasks related to SSC components and application interfaces as well as message routing table.
> Depending upon access privileges for the SSC instance, you can perform following tasks:

> • | Verifying System Status

> • | Viewing Active SSC System Tasks

> • | Viewing Message Routing Table

> Verifying System Status
> This section describes how to view system status and start or stop the system.
> Viewing System Status
> This section describes the procedure to verify the SSC system instance status on SSC node and to start/stop the instance.
> To viewing system status:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press a to monitor the status of SSC instance.

> Step 5 | Press V to view the current status of the system. It indicates whether this instance of SSC is running or it has stopped.

> If SSC instance is stopped and you want to start it, press s key. If SSC instance is running and you want to stop it, press the t key.
> Viewing Active SSC System Tasks
> This section describes how to view active tasks associated with an SSC instance.
> Viewing Active Tasks Associated with SSC System Instance
> An SSC instance is active when all tasks or processes associated with that instance are active.
> To view active SSC system tasks:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press K to monitor the status of processes associated with SSC instance.

> SSC Administration Console displays list of SSC processes along with their process is (PID) and the status of the individual process as running or not running
> Viewing Message Routing Table
> This section describes how to view the message routing tables.
> Viewing Message Routing Tables
> A message routing table displays available routes for a message.
> To view message routing tables:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press R to access the message routing table for SSC instance.

> SSC Administration Console displays the message routing table.
> User Administration
> This section describes the procedures to administer the users.
> SSC provides pre-defined roles that can be assigned to a user. Each of this user role has different access privileges. Depending upon the configuration of deployment.
> You can assign following roles to the users:

> • | Policy Administrator (PA): This role can perform administration tasks for Subscriber Profile Repository (SPR). This role can also add, delete or modify data in the database.

> • | Policy Operator (PO): This role can only view subscriber profile and related data in the database.

> • | System Administrator (SA): This role can perform all the tasks related to SSC application and deployment specific configurations.

> • | System Operator (SO): This role can only view the system configuration.

> Depending upon access privileges you can perform following tasks:

> • | Viewing Existing Users

> • | Adding New User

> • | Deleting Existing User

> • | Resetting User Password

> Viewing Existing Users
> This section describes how to view existing users who can access an SSC instance.
> Viewing Existing Users with Assigned Roles
> This section describes the procedure to view the existing users who can access SSC node, as well as their configured roles.
> To view existing users:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press b to access the user administration options.

> Step 5 | Press V to view the user roles configured for your deployment.

> Step 6 | Specify the role, to generate a list of users who can access this instance of SSC using the selected role

> SSC Admin Console displays the list of the users associated with this role.
> Adding New User
> This section describes how to add a new user.
> Adding a New User With Assigned Role
> This section describes the procedure to add a User with its assigned role to an SSC node.
> To add a new user to an SSC node:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press b to access the user administration options.

> Step 5 | Press N to add a new user.

> Step 6 | Specify the name of the user.

> Step 7 | Specify the password which can be used by this user to access the SSC node.

> Step 8 | Specify the role that is to be associated with this user.

> SSC Administration Console displays the message that the user has been added.
> Deleting Existing User
> This section describes how delete a user from an SSC node.
> Deleting an Existing User From SSC Node
> This section describes the procedure to delete a user from an SSC node.
> To delete a user from an SSC node:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press b to access the user administration options.

> Step 5 | Press t to delete an existing user.

> Step 6 | SSC Administration Console invokes the delete user action.

> Step 7 | Specify the name of the user that you want to delete.

> SSC Administration Console deletes the user and displays appropriate message.
> Resetting User Password
> This section describes how to re-set a user’s password.
> Resetting a User Password
> This section describes the procedure to re-set a user’s password.
> To re-set the password of an existing user:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press b to access the user administration options.

> Step 5 | Press R to access change password option.

> Step 6 | Specify the name of the user whose password you want to change.

> Step 7 | Specify the New password.

> SSC Administration Console changes the password of the user and displays appropriate message.
> Interface Management
> This section describes the procedures to administer the host machines and application interfaces that are used by various applications to exchange data with SSC.
> SSC uses various network interfaces such as Sp, XML-RPC or FTP to exchange the subscriber profile and session information with other components of the Policy Charging and Control (PCC) solution such as Intelligent Policy Control Function (IPCF), Policy Provisioning Tool (PPT) or Operation Support System (OSS) or Billing Support System (BSS).
> Binding an interface with SSC, indicates SSC to associate a task such as Sh application or profile application or event application with a particular server or host machine. If SSC deployment has multiple hosts, then multiple options will appear for binding interfaces.
> Binding an interface does not associate an IP address with the task. For associating the IP address with a task, you need to configure IP address for that individual component. For example IP address for Sh application is specified in Sh configuration, where as the bind interface option is used to select the host machine to run the Sh application.
> Depending upon SSC deployment configuration, SSC needs to interact with various application interfaces. The bind interface option allows binding of an SSC application interface or one of the SSC components with the host machine.
> SSC interface management involves following tasks:

> • | Listing Hosts

> • | Listing Interface Bindings

> • | Binding an Interface

> • | Un-binding an Interface

> Listing Hosts
> This section describes how to list machines that are hosting SSC application.
> Listing SSC Host Machines
> This section describes the procedure to list machines that are hosting SSC application.
> To list hosts:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press c to access the interface management options.

> Step 5 | Press L to view the list of hosts configured for SSC node.

> SSC Administration Console displays information of the hosts machines available for this deployment.
> Listing Interface Bindings
> This section describes how to list interface bindings
> Listing Interface Bindings of SSC Components
> This section describes the procedure to list interface bindings used by various components of SSC application.
> To list interface bindings:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press c to access the interface management options.

> Step 5 | Press t to view the list of bindings configured for SSC node.

> SSC Administration Console displays the bindings configured for this deployment.
> Binding an Interface
> This section describes how to bind an application interface of any SSC component with the host machine.
> Binding SSC Application Interface With Host Machine
> This section describes the procedure to bind an SSC application interface with a host machine.
> To bind an interface:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press c to access the interface management options.

> Step 5 | Press i to bind the interface.

> SSC Administration Console displays the bindings configured for this deployment.

> Step 6 | Specify the details of binding between the host machine and SSC component.

> SSC Administration Console binds the interface to the host machine and displays appropriate message.
> Important: SSC displays appropriate warning message, if some other SSC related task or application is already associated with this machine that you are currently attempting to bind with additional SSC related task or application.
> Un-binding an Interface
> This section describes how to un-bind an SSC application interface from the host machine.
> Un-binding SSC Application Interface From Host Machine
> This section describes the procedure to un-bind an SSC application interface from its host machine.
> To un-bind an interface:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press c to access the interface management options.

> Step 5 | Press u to delete the binding of this interface.

> SSC Administration Console severs the connection between interface and host machine and displays appropriate message.
> Important: This option allows you to un-bind an SSC application interface or SSC component from the host machine and isolate that host machine for troubleshooting or maintenance purpose.
> SSC Logs Administration
> This section provides information about SSC logs.
> SSC logs can be used to monitor the availability of various application interfaces and host machines as well as for the troubleshooting issues associated with deployment.
> SSC logs are categorized as:

> • | Event logs: SSC records information related to events that affect subscriber profile or their service usage. These logs are used to troubleshoot the issues related to profile and service usage of the subscriber. Event logs consist of e-mail and SMS notifications that have been generated by SSC and sent to the subscriber.

> Following is an example of an event log entry:
> Timestamp:12-APR-2011 16:31, Module Id:SPR Audit, Event Id: Create Data Plan(15), client_context session_id: 45668734556, user_name: policyadmin, Request: plan_name: plan-2, Response: result_code :0
> Important: Event logs are also known as audit logs.

> • | System logs: SSC also records information related to deployment infrastructure such as web servers and active sessions. System logs are mostly used for administering SSC node and troubleshooting issues related to hardware and software infrastructure of SSC node, such as web servers and associated sessions. System logs can be used to troubleshoot issues related to system performance by analyzing errors and access information related to web servers and AXIS framework.

> Following is an example of a system log entry:
> 11-May-03+14:59:05.226 [sysmgr:1 (24703/18752)] [sysctrl_callback.cpp:329] [info sysmgr 7505] Logged in: user name - SA, role - 10, session id - 1498446599
> Important: For more information about system logs, refer to the section Monitoring System Logs.
> SSC uses event or audit logs to record information related to:

> • | System configuration events.

> • | Subscriber Profile Repository (SPR) provisioning events.

> • | Subscriber notification logs.

> • | Specific logs that are being triggered by the Intelligent Policy Control Function (IPCF) to record specific events related to SSC.

> SSC can log e-mail and SMS event notifications that have been generated and sent to the subscriber. The event notification log records time, user id and details of the notification. Subscriber’s preferences determine the events that are being logged. Following events implicitly generate the notifications:

> • | Recharge of a data or usage plan.

> • | Crossing the threshold associated with the usage of a plan.

> • | Resetting of user account at the start of billing cycle.

> Important: Billing cycle re-set dates for subscribers and usage threshold levels for configured data plans can be defined using Policy Provisioning Tool (PPT).
> IPCF is used to provision the event log actions and trigger logging in SSC, using notification interface between IPCF and SSC.
> Event logs are stored in a database. Depending upon access privilege, and deployment configuration. You can access these logs using SPR API as well as purge these logs as per requirements.
> SSC logs administration involves following tasks:

> • | Changing Sink Settings

> • | Changing Debug Level

> • | Changing Session Log Level

> • | Viewing Logging Level Configuration

> • | Managing Syslog

> Changing Sink Settings
> This section describes how to change sink settings while capturing logging information from an SSC node.
> Changing SSC Log Sink Settings
> This section describes the procedure to change sink settings while capturing SSC logs.
> To change sink settings:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press d to access log configuration options.

> Step 5 | Press K to access sink settings.

> Step 6 | Specify maximum size for the individual log file. The range is from 1 to 50 Mb. Maximum size defines upper limit for the size of a log file in MegaBytes (MB).

> Step 7 | Specify maximum duration between successive samples. The range is from 1 to 360 minutes. SSC creates a new log file after set duration time is lapsed.

> Step 8 | Specify Maximum count. The range is between 0 to 50. Maximum count defines the number of files in which the logs are recorded in rotation.

> Important: Count zero indicates that the files will not be rotated while recording the logs.

> Step 9 | Specify log verbosity as detail, brief or normal. Log verbosity defines the degree of details that are to be recorded while logging values for this parameter.

> SSC Administration Console updates the sink setting for the log as per the values specified in steps 6 to 9.
> Changing Debug Level
> This section describes how to change debug levels of the logs that are being captured.
> Changing Debug Level For SSC Node
> This section describes the procedure to change the Debug level on SSC node.
> To change debug level:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press d to access log configuration options.

> Step 5 | Press L to access debug level settings.

> Step 6 | SSC Administration Console displays existing logging configuration. The log categories correspond to the SSC processes for deployment.

> Step 7 | Specify the log category for which you want to change the log level.

> Step 8 | Specify the log level. Valid values for the log levels are info, critical, notice, emergency, trace, alert, warning, error and debug.

> SSC Administration Console assigns updated logging level to the selected logging category.
> Changing Session Log Level
> This section describers how to change the session log level.
> Changing Session Log Level For SSC Node
> This section describes the procedure to change the session log level on SSC node.
> To change session log level:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press d to access log configuration options.

> Step 5 | Press S to change the existing level of session logs.

> Step 6 | Specify new logging level.

> SSC Administration Console changes the logging level and displays appropriate message.
> Viewing Logging Level Configuration
> This section describes how to view logging level configuration.
> Viewing Configured Logging Level For SSC Node
> This section describes the procedure to view configured logging levels.
> To view log level configuration:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press d to access log configuration options.

> Step 5 | Press V to view existing log configuration.

> SSC Administration Console displays the default/configured log level.
> Important: Currently available logging levels are Debug, Information, Warning, Critical and Error.
> Managing Syslog
> This section describes how to manage syslog.
> Enabling or Disabling Syslog Storage
> This section describes the procedure to manage syslog information by enabling or disabling the syslog storage.
> To enable or disable the syslog storage:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press d to access log configuration options.

> Step 5 | Press M to access manage syslog option.

> Step 6 | SSC Administration Console displays whether the syslog option is enabled or disabled, and allows you to change that status by specifying y or n.

> Step 7 | If in the previous step, you chose to enable this option then you need to specify name or IP address of the remote computer where you want to store the syslog.

> Step 8 | Specify root password for this computer.

> Step 9 | SSC Administration Console enables or disables the storage and displays appropriate message in the message window.

> SNMP Traps and Alarms Configuration
> This section describes the procedures to view and configure the SNMP traps and alarms.
> Simple Network Management Protocol (SNMP) traps or alarms, provide information about the network status to system administrators. Alarms can also be used for troubleshooting the issues. Alarms are classified as critical, warning and informational.They mostly indicate the status of various SSC hardware and software components such as chassis, blades, power, I/O and storage modules.
> SNMP traps are sent to the configured SNMP traps receiver. These traps are also stored in the file sn_SSC.log. In the log file the traps can be identified by the keyword alarm.
> SNMP traps and alarms configuration involves following tasks:

> • | Configuring SNMP Traps and Alarms Parameters

> • | Verifying SNMP Traps and Alarms Configuration

> • | Supported SNMP Traps and Alarms

> Configuring SNMP Traps and Alarms Parameters
> This section describes how to configure SNMP traps and alarms.
> Configuring SNMP Traps and Alarms
> This section describes the procedure to configure SNMP traps and alarms.
> To set SNMP traps and alarms parameters:

> Step 1 | Login with SSC administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press e to access SNMP configuration options.

> Step 5 | Press i to view existing SNMP configuration.

> Step 6 | Specify the IP address and Port number of the SNMP sever for which you are configuring alarms.

> Verifying SNMP Traps and Alarms Configuration
> This section describes how to verify SNMP traps and alarms configuration.
> Viewing SNMP Traps and Alarms Configuration
> This section describes the procedure to verify SNMP traps and alarms configuration.
> To view SNMP traps and alarm configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press e to access SNMP configuration options.

> Step 5 | Press V to view existing SNMP configuration.

> SSC Administration Console displays existing SNMP collection server configuration. Such as Port number and server IP address.
> Supported SNMP Traps and Alarms
> This section describes the list of supported SNMP traps and alarms on SSC node.
> Following table lists supported SNMP traps along with their respective ids.
> SNMP Traps and Object IDs for SSC

> Traps | Object ID
> starSSCEntityStart | starSSCMIBTraps 1
> starSSCEntityStop | starSSCMIBTraps 2
> starSSCProcessStart | starSSCMIBTraps 3
> starSSCProcessStartFail | starSSCMIBTraps 4
> starSSCProcessRestartFail | starSSCMIBTraps 5
> starSSCFTPServerUnreachable | starSSCMIBTraps 6
> starSSCFTPServerReachable | starSSCMIBTraps 7
> starSSCShCtrlPeerUp | starSSCMIBTraps 8
> starSSCShCtrlPeerDown | starSSCMIBTraps 9
> starSSCEnCtrlPeerUp | starSSCMIBTraps 10
> starSSCEnCtrlPeerDown | starSSCMIBTraps 11
> starSSCSysMgrFailover | starSSCMIBTraps 12
> starSSCCpuThresholdCrossed | starSSCMIBTraps 13
> starSSCCpuThresholdCleared | starSSCMIBTraps 14
> starSSCSwapThresholdCrossed | starSSCMIBTraps 15
> starSSCSwapThresholdCleared | starSSCMIBTraps 16
> starSSCEnMgrConnFailed | starSSCMIBTraps 17
> starSSCEnMgrConnEstablished | starSSCMIBTraps 18
> starSSCProcTheshCrossed | starSSCMIBTraps 19
> starSSCProcTheshCleared | starSSCMIBTraps 20
> starSSCMaxShSessionsCrossed | starSSCMIBTraps 21
> starSSCMaxShSessionsCleared | starSSCMIBTraps 22
> starSSCMaxPendReqAppMgrCrossed | starSSCMIBTraps 23
> starSSCMaxPendReqAppMgrCleared | starSSCMIBTraps 24
> starSSCMaxPendReqAppMgrSysCrossed | starSSCMIBTraps 25
> starSSCMaxPendReqAppMgrSysCleared | starSSCMIBTraps 26
> starSSCSprDown | starSSCMIBTraps 27
> starSSCSprUp | starSSCMIBTraps 28
> starSSCSprCacheDown | starSSCMIBTraps 29
> starSSCSprCacheUp | starSSCMIBTraps 30
> starSSCLdapInitFailed | starSSCMIBTraps 31
> starSSCLdapInitSuccess | starSSCMIBTraps 32

> ‌
> Important: For detailed descriptions of SSC traps and alarms, refer to Cisco ASR 5000 Series SNMP MIB Reference. For alarms related to other software or hardware components of the solution such as CRM/OSS/BSS or IBM Blade Center HT chassis or Cisco UCS C210M1, refer to respective documentation.
> Bulk Statistics Configuration
> This section describes the procedures to configure the bulk statistics parameters on SSC node.
> Depending upon SSC configuration, system statistics can record the information such as:

> • | Service level statistics for SSC, IMDB and database services.

> • | Database layer parameters.

> • | Sh protocol parameters.

> • | Subscriber Profile Repository (SPR) API parameters.

> Bulk statistics records counters, gauges and fixed value strings for various application schema that are associated with SSC, such as:

> • | Sh application.

> • | Event notification application.

> • | Profile application.

> A counter records incremental data cumulatively and rolls over when the limit value is reached. This limit depends upon the data type of the counter. SSC can perform various calculations and record the historical information in form of peak, average or total counters. A gauge records a single value representation of a single instance. A gauge can be used to track particular events in time.
> SSC can be configured to save this information at periodic intervals. This information can be saved in a local directory or on a remote server using FTP.
> Bulk statistics configuration for an SSC instance involves following tasks:

> • | Configuring Bulk Statistics Parameters

> • | Enabling Bulk Statistics Collection

> • | Verifying Bulk Statistics Configuration

> Important: Refer to appendices for available event notification, profile and Sh application, bulk statistics schema.
> Configuring Bulk Statistics Parameters
> This section describes how to configure bulk statistics parameters.
> Configuring Bulk Statistics Parameters for SSC Deployment
> This section describes the procedure to configure bulk statistics parameters.
> To set bulk statistics parameters:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press f to access statistics configuration options.

> Step 5 | Press n to configure bulk statistics parameters.

> Step 6 | Provide Sample Interval in minutes.

> SSC Administration Console displays a message indicating completion of statistical configuration.
> Enabling Bulk Statistics Collection
> This section describes how to enable bulk statistics collection on an SSC node
> Enabling Bulk Statistics Collection For SSC Deployment
> This section describes the procedure to enable bulk statistics collection on an SSC node.
> To enable bulk statistics collection:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press f to access statistics configuration options.

> Step 5 | Press r to enable or disable the bulk statistics configuration depending on available status.

> SSC Administration Console displays the following message:
> The bulk statistics feature is disabled. Do you want to enable it? (y/n)
> Press y to start the Bulk statistics collection on SSC node.
> Press n to stop the Bulk statistics collection on SSC node.
> Verifying Bulk Statistics Configuration
> This section describes how to verify bulk statistics configuration.
> Viewing Bulk Statistics Configuration
> This section describes the procedure to verify Bulks Statistics collection configuration on SSC node.
> To view the bulk statistics configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press f to access statistics configuration options.

> Step 5 | Press V to view existing configuration for bulk statistics.

> SSC Administration Console displays existing bulk statistics configuration parameters such as Sampling interval (in min), FTP interval (in minutes), password, user name, FTP server and the location of the bulk statistics configuration file indicated by the field, Place file at.
> Subscriber Profile Repository (SPR) Configuration
> This section describers the procedures to view and configure the subscriber identifier in SPR.
> SSC uses Subscriber Profile Repository (SPR) data storage along with centralized PCRF functions to implement usage control policies for subscribers. Depending upon your system configuration and services, SPR includes information related to subscriber profile, entitlements and rate plans. It can be a standalone database or it can be integrated with exiting subscriber database such as Home Subscriber Server (HSS).
> SPR can store following information related to a subscriber’s profile and its state:

> • | IMSI

> • | MSISDN

> • | Initial subscriber quality of Service (QoS) profile identifier.

> • | Mobile 3GPP QoS as defined in home Location Register (HLR)

> • | Home location

> • | Current subscriber QoS profile

> • | Current subscriber class Id

> • | Service event Id

> • | Remaining balance

> • | Usage parameters such as volume or time that are being tracked for this service event.

> • | Active event queue and usage history

> SPR configuration involves following tasks:

> • | Configuring Subscriber Identifier in SPR

> • | Verifying Subscriber Identifier in SPR

> Configuring Subscriber Identifier in SPR
> This section describes how to configure subscriber identifier in SPR.
> Configuring Identifier For SPR Subscriber
> This section describes the procedure to configure subscriber identifier in SPR.
> To configure SPR subscriber identifier:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press g to access SPR configuration option.

> Step 5 | Press S to configure identifier for the SPR subscriber.

> Step 6 | Specify subscriber identifier, use MSIDN, NAI or IMSI associated with this subscriber as his or her unique identifier.

> SSC Administration Console configures the identifier for this subscriber and displays appropriate message.
> Verifying Subscriber Identifier in SPR
> This section describers how to verify a subscriber identifier in SPR.
> Verifying Identifier For SPR Subscriber
> This section describes the procedure to verify subscriber identifier in SPR.
> To verify SPR subscriber identifier:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press g to access SPR configuration option.

> Step 5 | Press V to view the identifier for SPR subscriber.

> SSC Administration Console displays the identifier associated with this subscriber. The identifier is either MSISDN, NAI or IMSI associated with this subscriber.
> Configuration Management
> This section describes how to manage SSC system configuration.
> Depending upon your access privilege for an SSC node, you can configure:

> • | Users that can access this deployment with pre-defined privileges.

> • | Interfaces for Sh, EN, Ud and other applications that exchange data with SSC.

> • | Binding of SSC host machine with various application host machines that need to exchange data with SSC.

> • | System logs that store values for system parameters.

> • | SNMP alarms or traps for various system parameters.

> • | Bulk statistics, counters or thresholds that can be used for administering as well as troubleshooting the SSC node.

> Configuration management for an SSC instance involves following tasks:

> • | Saving Configuration

> • | Loading Configuration

> SSC system configuration is saved in XML format. Save Configuration option is used to save or export existing system configuration to an XML format.Whereas Load Con figuration option is used to import a system configuration from XML format, by deleting existing system configuration and loading or using new or imported configuration.
> Saving Configuration
> This section describes how to save system configuration.
> Saving SSC System Configuration
> This section describes the procedure to save system configuration.
> To save configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press h to access configuration management option.

> Step 5 | Press S to save existing configuration.

> Step 6 | Specify the filename, along with its relative path from the SSC home directory.

> Admin Console saves the configuration in a file at specified location and displays appropriate message.
> Loading Configuration
> This section describes how to load any available system configuration.
> Loading SSC System Configuration
> This section describes the procedure to load previously saved system configuration.
> To load a saved configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press h to access configuration management option.

> Step 5 | Press L to load an existing SSC system configuration from the file.

> Step 6 | Provide SSC configuration file name which you want to load in SSC system from the existing saved configurations in local directory.

> SSC Administration Console loads the system configuration described in the file and displays appropriate message.
> Profile Controller Configuration
> This section describes the procedure to configure the Profile Controller on SSC node.
> Profile controller or usage manager application provides an interface with PCRF. This interface is used for querying subscriber profile or getting account updates from the PCRF.
> Profile controller configuration contains following tasks:

> • | Configuring Profile Controller

> • | Verifying Profile Controller Configuration

> Configuring Profile Controller
> This section describes how to configure a profile controller on an SSC node.
> Configuring Profile Controller For SSC Node
> This section describes the procedure to configure a profile controller.
> To configure the profile controller:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press i to access profile controller configuration option.

> Step 5 | Press S to set profile controller configuration.

> Step 6 | Specify the IP address of the machine that is hosting the profile controller application.

> Step 7 | Specify the port that is to be used to communicate with profile controller application.

> SSC Administration Console configures the profile controller or displays appropriate error message.
> Verifying Profile Controller Configuration
> This section describes the procedure to verify the Profile Controller configuration on SSC node.
> Verifying Profile Controller configuration For SSC Node
> This section describes the procedure to verify the configuration of profile controller.
> To verify the Profile Controller configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press i to access profile controller configuration option.

> Step 5 | Press V to view existing profile configuration.

> Step 6 | SSC Administration Console displays the IP address of the machine hosting the profile controller and the port which can be used to connect to it.

> Policy Provisioning Tool (PPT) Configuration
> This section describes the procedure to configure the Policy Provisioning Tool (PPT) for SSC deployment.
> Policy Provisioning Tool (PPT) is a component of Cisco PCC solution. PPT is a web based client –server application that provides a wizard based interface to configure usage policies using rules and rule bases.
> PPT configuration for an SSC instance contains following tasks:

> • | Viewing PPT Configuration

> • | Configuring PPT Controller (PPTCtrl)

> • | Adding PPT Peer

> • | Deleting PPT Peer

> Viewing PPT Configuration
> This section describes how to view existing PPT configuration.
> Viewing PPT Configuration For SSC Node
> This section describes the procedure to view existing PPT configuration.
> To view PPT configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press j to access PPT configuration option.

> Step 5 | Press V to view existing configuration.

> SSC Administration Console displays authentication information for PPT controller as well as PPT peer machine configuration parameters such as ip address, name, user name and password.
> Configuring PPT Controller (PPTCtrl)
> This section describes how to configure a PPT controller for an SSC node.
> Configuring PPT Controller For SSC Node
> This section describes the procedure to configure a PPT controller for SSC node.
> To configure PPT controller:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press j to access PPT configuration option.

> Step 5 | Press P to configure PPT controller.

> Step 6 | Specify whether you want to authenticate the PPT instance.

> SSC Administration Console configure the PPT controller.
> Adding PPT Peer
> This section describes how to add a PPT peer.
> Adding PPT Peer For SSC Node
> This section describes the procedure to add a PPT peer for SSC node.
> To add a PPT peer:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press j to access PPT configuration option.

> Step 5 | Press T to add a PPT peer machine.

> Step 6 | Specify the name for PPT peer.

> Step 7 | Specify the user name that can used to access this PPT peer.

> Step 8 | Specify password to access this machine

> Step 9 | Specify the client IP address of the PPT peer machine, with which this SSC instance will be communicating.

> SSC Administration Console configures PPT client and displays appropriate error message.
> Deleting PPT Peer
> This section describes how to delete a PPT peer.
> Deleting PPT Peer From SSC Deployment
> This section describes the procedure to delete a PPT peer from SSC deployment.
> To delete a PPT peer:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 1 to access System Administration options.

> Step 4 | Press j to access PPT configuration option.

> Step 5 | Press r to delete an existing PPT peer machine.

> Step 6 | Specify the name of PPT peer machine with which you want to sever communication from this SSC instance.

> Sh Application Configuration
> This section describes the procedures to administer the Sh application.
> SSC uses Sp interface to query data related to service usage and balance as well as to exchange subscriber profile information with IPCF. Sp interface uses a standard Sh protocol. In an SSC deployment a single Sp endpoint can be connected to multiple SPR peer servers simultaneously for providing load balancing and high availability of profile and usage database. This is achieved by either configuring primary and secondary SPR servers or by using round robin mechanism. Sh application configuration is used for configuring Sh servers and peers for the SSC deployment. This configuration can be used to provide better connection management between the servers and peers. It can also be used to provide load balancing for Sh messages in the deployment.
> While administering Sh application you can perform following tasks:

> • | Sh Server Configuration

> • | Sh Peer Configuration

> Sh Server Configuration
> This section describes the configuration of Sh servers.
> While configuring Sh server you perform following tasks:

> • | Configuring Sh Server

> • | Deleting Sh Server Configuration

> • | Verifying Sh Server Configuration

> Configuring Sh Server
> This section describes how to configure an Sh server.
> Configuring Sh Server Host Machine
> This section describes the procedure to configure an Sh server.
> To configure Sh Server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm

> Step 3 | Press 2 to access Sh App Admin options.

> Step 4 | Press b to access Sh Server Config options.

> Step 5 | Press S to configure the Sh server.

> Step 6 | Specify the host name of the machine on which you want to configure the Sh server.

> Step 7 | Specify the realm for the server.

> Step 8 | Specify the IP address for this host machine.

> Step 9 | Specify the port that will be used by this server for communicating Sh protocol related messages.

> SSC Administration Console configures the servers and displays appropriate message.
> Deleting Sh Server Configuration
> This section describes how to delete an Sh server configuration.
> Deleting Sh Server Configuration Form Host Machine
> This section describes the procedure to delete an Sh server configuration.
> To delete Sh Server Configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access Sh App Admin

> Step 4 | Press b to access Sh Server Config options.

> Step 5 | Press S to configure the Sh server.

> Step 6 | Press t to access the Delete Sh Server option.

> Step 7 | Press Y if you want to delete the Sh server.

> SSC Administration Console deletes the Sh server and displays appropriate message.
> Caution: Deleting an Sh server deletes all the peers associated with this server.
> Verifying Sh Server Configuration
> This section describes how to verify the Sh sever configuration on SSC node.
> Verifying Sh Server Configuration For SSC Instance
> This section describes the procedure to verify existing Sh server configuration.
> To verify Sh Server Configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access Sh Application Administration (Sh App Admin) option.

> Step 4 | Press V to view existing server and peer configuration for Sh application.

> SSC Administration Console displays Name, IP address as well as Port number for Sh server as well as peers.
> Important: If Sh server is already configured for your deployment, then SSC Administration Console displays the host name of the machine on which this server is configured.
> Sh Peer Configuration
> This section describes the configuration of Sh peer server.
> While configuring Sh peer servers you perform following tasks:

> • | Adding Sh Peer

> • | Viewing Sh Peer

> • | Removing Host Machine From Sh Peer Configuration

> Adding Sh Peer
> This section describes how to add an Sh peer.
> Adding Host Machine to Sh Peer Configuration
> This section describes the procedure to add an Sh peer.
> To add Sh peer Configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access Sh Application Administration (Sh App Admin) option.

> Step 4 | Press c access Sh peer configuration (Sh Peer config) options.

> Step 5 | Press P to add Sh peer machine.

> Step 6 | Specify the Name, Realm and IP address for the Sh peer.

> SSC Administration Console configures the peer and displays appropriate message.
> Viewing Sh Peer
> This section describes how to view an Sh peer.
> Viewing Sh Peer Configuration
> This section describes the procedure to view existing Sh peer configuration.
> To view Sh peer Configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access Sh Application Administration (Sh App Admin) option.

> Step 4 | Press c access Sh peer configuration (Sh Peer config) options.

> Step 5 | Press V to access view peers option.

> SSC Administration Console displays Sh peer machines configured for your deployment
> Important: If your session has timed out then, you need to log out and again log in to view Sh peer configuration.
> Deleting Sh Peer
> This section describes how to delete an Sh peer.
> Removing Host Machine From Sh Peer Configuration
> This section describes the procedure to delete an Sh peer.
> To delete Sh peer Configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access Sh Application Administration (Sh App Admin) option.

> Step 4 | Press c access Sh peer configuration (Sh Peer config) options.

> Step 5 | Press t to delete an Sh peer.

> Step 6 | Specify the Name of the Sh peer, that you want to delete.

> Step 7 | Press Y to delete the Sh peer.

> SSC Administration Console deletes the peer and displays appropriate message.
> User Data Repository (UDR) Administration
> This section describes the procedures to administer Ud interface.
> Subscriber Profile Repository (SPR) stores the subscriber profiles. These are essentially a set of profile attributes indexed by subscriber identity such as International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN). Subscriber profiles can be accessed using various protocols such as Sh, LDAP or SOAP/XML over an Sp interface. If the SPR is implemented using Universal Data Collection (UDC) schema, then User Data Repository (UDR) serves as SPR for such SSC deployments. In such case the profiles are accessed using Ud interface.
> Ud interface of SSC allows you to introduce SSC in your network and exchange the subscriber profile data with other components of Policy Charging and Control (PCC) solution, such as Customer Relationship Management (CRM), Operation Support System (OSS) or Billing Support System (BSS). This is possible even if these components are storing data in different database formats, provided that the Ud capabilities or Light weight Directory Access Protocol (LDAP) is supported by the data stores that are exchanging the data with SSC.
> An SSC instance can be configured as:

> • | Ud Server: In this capacity SSC can allow other components of PCC solution to query the profile database. Acting as a server SSC can send the notifications to these component applications when profile data is updated.

> • | Ud Client: In this capacity SSC can query and fetch data from other components of PCC solution.

> This section includes following sub- sections:

> • | Configuring User Data Repository (UDR) Server

> • | Configuring UDR Search Query

> • | Configuring Attribute Map

> • | Configuring UDR Client

> • | Configuring UDR Policy

> • | Configuring Usage Policy

> • | Configuring UDR Controller

> • | Configuring Ud Client for CRM

> • | Configuring an Update Query

> Configuring User Data Repository (UDR) Server
> This section describes the procedures to configure UDR server.
> SSC can act as an Ud server, while exchanging the data with other PCC solution components such as CRM and can allow these components to query as well as modify the subscriber usage and profile data stored in SSC.
> UDR server configuration involves following tasks:

> • | Adding a UDR Server

> • | Deleting UDR Server

> • | Viewing UDR Server Configuration

> Adding a UDR Server
> This section describes the procedure to add an UDR server.
> To add UDR server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press a access UDR server configuration option.

> Step 5 | Press S to add an UDR server to your deployment.

> Step 6 | Specify UDR server Id, such as ip address or Fully Qualified Domain Name (FQDN).

> Important: Server Name or Id should be alphanumeric and less than 32 characters in length.

> Step 7 | Specify primary IP of the UDR Server.

> Step 8 | Specify Primary UDR server port.

> Step 9 | Specify secondary IP of the UDR server.

> Step 10 | Specify secondary server UDR port.

> Step 11 | Specify whether you want this server to be Ud compliant, by entering y for yes or n for no.

> Step 12 | Specify the user name for the UDR.

> Step 13 | Specify password for this UDR server.

> Step 14 | Specify the UD service url, that is to be used for accessing this server.

> SSC Administration Console configures the UDR server and displays appropriate message.
> Deleting UDR Server
> This section describes the procedure to delete an UDR server.
> To delete a UDR server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press a access UDR server configuration option.

> Step 5 | Press t to delete an existing UDR server.

> SSC Administration Console deletes the UDR server and displays appropriate message.
> Viewing UDR Server Configuration
> This section describes the procedure to view configuration of an existing UDR server.
> To view UDR server configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press a access UDR server configuration option.

> Step 5 | Press V to view configuration of an existing UDR server.

> SSC Administration Console displays information such as primary and secondary UDR server Ids, corresponding IP addresses. It also displays whether the given server is Ud compliant or not.
> Configuring UDR Search Query
> This section describers the procedures to configure a UDR search query, when an SSC instance is acting as a UDR client to query and fetch data from other PCC components.
> UDR search query configuration involves following tasks:

> • | Adding UDR Search Query

> • | Viewing UDR Search Query

> • | Deleting UDR Search Query

> Adding UDR Search Query
> This section describes the procedure to add an UDR search query.
> To add a UDR search query:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press b access UDR search query configuration option.

> Step 5 | Press S to add a new search query for the UDR server.

> Step 6 | Specify the search query Id.

> Important: Name or id of the search query should be alphanumeric and less than 32 characters in length.

> Step 7 | Specify Base Domain Name (DN) for this query. The query will be executed on this domain only.

> Step 8 | Specify the search filter. This is the search criteria.

> Step 9 | Specify the output parameters for this query.

> Step 10 | Specify whether you want to execute this query or not.

> Step 11 | Specify the server Id of the UDR server, on which to execute this query.

> SSC Administration Console configures the UDR search query and displays appropriate message.
> Viewing UDR Search Query
> This section describes the procedure to view an existing UDR search query.
> To view UDR search query:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press b access UDR search query configuration option.

> Step 5 | Press e to view an existing search query.

> SSC Administration Console displays the list of all existing search queries. For each search query it displays query id, search filter, associated server id, whether this query is to be executed or not and what are the query output parameters.
> Deleting UDR Search Query
> This section describes the procedure to delete an existing UDR search query.
> To delete a UDR search query:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press b access UDR search query configuration option.

> Step 5 | Press t to delete an existing search query from the UDR server.

> SSC Administration Console deletes the search query and displays appropriate message.
> Configuring Attribute Map
> This section describers the procedures to configure an attribute map Between User Data Repository (UDR) and SSC schema.
> An attribute map defines the relationship between attribute types in hierarchical LDAP schema and corresponding columns in the tables of a relational database schema. The map also contains rules that define the procedures for copying or transforming an attribute while exchanging the information between two different data sets.
> Attribute map configuration involves following tasks:

> • | Adding UDR-SSC Attribute Map

> • | Viewing UDR-SSC Attribute Configuration

> • | Deleting UDR-SSC Attribute Map

> Adding UDR-SSC Attribute Map
> This section describes the procedure to add an UDR- SSC attribute map.
> To add UDR-SSC attribute map:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press c to access UDR attribute map configuration option.

> Step 5 | Press S to add a new attribute map for UDR-SSC.

> Step 6 | Specify attribute Id, that you want to map with a column in a relational database schema table.

> Step 7 | Specify the LDAP attribute that you want to map with an SSC attribute.

> Step 8 | Specify the SSC attribute that you want to map with an LDAP attribute.

> Step 9 | Specify table name that maps LDAP and SSC attributes for the UDR.

> SSC Administration Console adds the Ud attribute map and displays appropriate message.
> Viewing UDR-SSC Attribute Configuration
> This section describes the procedure to view existing UDR -SSC attribute configuration.
> To view attribute configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press c to access UDR attribute map configuration option.

> Step 5 | Press i to view existing attribute maps. These maps display relationship between LDAP and SSC attributes.

> SSC Administration Console displays UDR attribute id along with LDAP and SSC UDR attributes and the name of SSC table where these attributes are mapped.
> Deleting UDR-SSC Attribute Map
> This section describes the procedure to delete an existing UDR-SSC attribute map.
> To delete UDR-SSC attribute map:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press c to access UDR attribute map configuration option.

> Step 5 | Press t to delete an entry from UDR-SSC attribute map.

> Step 6 | Specify id of the attribute that you want to remove from the LDAP-UDR attribute map.

> Step 7 | Confirm that you want to delete this attribute configuration.

> SSC Administration Console deletes the mapping for UDR-LDAP attribute map from the table and displays appropriate message.
> Configuring UDR Client
> This section describers the procedures to configure an UDR client.
> SSC can also act as an Ud client or a front end application for the User Data Repository (UDR) and support multiple target databases. It can read data from LDAP or 3GPP R9 compliant Ud databases.
> UDR client configuration involves following tasks:

> • | Viewing UDR Client Configuration

> • | Setting UDR Client Configuration

> Viewing UDR Client Configuration
> This section describes the procedure to view the configuration of a UDR client.
> To view UDR client configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press d to access UDR client configuration option.

> Step 5 | Press V to view configuration of all existing UDR clients.

> SSC Administration Console displays the front-end Id and the service name for all the UD clients configured for your system.
> Setting UDR Client Configuration
> This section describes the procedure to set the configuration of a UDR client.
> To set UDR client configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press d to access UDR client configuration option.

> Step 5 | Press C to configure UDR client.

> Step 6 | Specify the front-end id. This indicates the front end which you want to set SSC front end.

> Step 7 | Specify the service name or subscription, whose information will be exchanged with SSC using this front end.

> SSC Administration Console configures new Ud client and displays appropriate message.
> Configuring UDR Policy
> This section describes the procedures to configure Ud polices.
> Ud policies are used by the Sh Manager component of SSC to send a message to LDAP interface manager component that fetches the profile from SSC’s LDAP interface.
> Following pre-defined Ud policies are available:

> 1. | Fetch always: This policy will always fetch the user profile, irrespective of its availability in the destination database.

> 2. | Fetch if absent: This policy will fetch the user profile if it is not available in the destination database.

> UDR policy configuration involves following tasks:

> • | Viewing UDR Policy

> • | Setting UDR Policy

> Viewing UDR Policy
> This section describes the procedure to view an existing UDR policy.
> To view UDR policy:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press c to access UDR attribute map configuration option.

> Step 5 | Press p to view existing UDR policies.

> Setting UDR Policy
> This section describes the procedure to set a UDR policy.
> To set UDR policy:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press c to access UDR attribute map configuration option.

> Step 5 | Press Y to set UDR policy.

> Step 6 | Specify the number, to indicate the policy that you want to set. For example select 1 to specify fetch always or 2 specify fetch if absent as a UDR policy.

> SSC Administration Console configures the Ud policy and displays appropriate message.
> Configuring Usage Policy
> This section describes the procedures to configure policy for exchanging service usage data with UDR.
> SSC can receive the service usage related data from User Data Repository (UDR) servers. You can configure a policy either to update the service usage data in SSC from UDR server or to ignore such data from the UDR server.
> Usage policy configuration involves following tasks:

> • | Viewing Usage Policy

> • | Setting Usage Policy

> Viewing Usage Policy
> This section describes the procedure to view usage policy.
> To view usage policy:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press f to access usage policy configuration option.

> Step 5 | Press P to view existing usage policies for receiving the usage data from User Data Repository (UDR) to SSC.

> SSC Administration Console displays the configured usage data exchange policy between SSC and UDR.
> Setting Usage Policy
> This section describes the procedure to set usage policy.
> To set usage policy:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press f to access usage policy configuration option.

> Step 5 | Press Y to configure policy for updating usage data from UDR.

> Step 6 | Specify the usage policy number. Select 1to receive updated usage data from UDR or select 2if you do not want SSC to receive current usage data from the UDR server.

> SSC Administration Console configures usage policy for UDR data and displays appropriate message.
> Configuring UDR Controller
> This section describes the procedures to configure UDR controller.
> UDR controller configuration involves following tasks:

> • | Viewing UDR Controller Configuration

> • | Setting UDR Controller Configuration

> Viewing UDR Controller Configuration
> This section describes the procedure to view configuration of an existing UDR controller.
> To view UDR controller configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press g to access UDR controller configuration option.

> Step 5 | Press V to view configuration of an existing UDR controller.

> SSC Administration Console displays UDR controller parameters such as, Base DN, password, IP address, Port number and User Name.
> Setting UDR Controller Configuration
> This section describes the procedure to set configuration of a UDR controller.
> To set UDR controller configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press g to access UDR controller configuration option.

> Step 5 | Press C to set the controller configuration.

> Step 6 | Specify IP address for UDR controller.

> Step 7 | Specify the port number which will be used by this UDR controller for communication.

> Step 8 | Specify the Base DN for this controller.

> Step 9 | Specify the user name which will be used to access this controller.

> Step 10 | Specify the password required to access this controller.

> SSC Administration Console configures the controller with parameters and displays appropriate message.
> Configuring Ud Client for CRM
> This section describes the procedures to configure a Ud client for Customer Relationship Management (CRM) application.
> Configuring Ud client for CRM, involves following tasks:

> • | Configuring Ud Client for CRM

> • | Viewing Ud Client Configuration

> Configuring Ud Client for CRM
> This section describes the procedure to configure a Ud client for CRM.
> To configure UD client for CRM:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press h to configure a Ud client for CRM.

> Step 5 | Press C to access the configuration option for this client.

> Step 6 | Specify Id for the front end for this CRM client.

> Step 7 | Specify the URL which is required to access this front end.

> Step 8 | Specify the port number that will be used for communicating with this front end of CRM client.

> SSC Administration Console configures the Ud client and displays appropriate message.
> Viewing Ud Client Configuration
> This section describes the procedure to view configuration of a Ud client.
> To view Ud client configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press h to configure a Ud client for CRM.

> Step 5 | Press V to view existing configuration for CRM Ud client.

> SSC Administration Console displays Id for the front end and the URL that is to be used to access this CRM client, along with the port number that is to be used for communicating with this client.
> Configuring an Update Query
> This section describers the procedures to configure an update query for a UDR server.
> Update query configuration involves following tasks:

> • | Adding Update Query

> • | Viewing Update Query

> • | Deleting Update Query

> Adding Update Query
> This section describes the procedure to add an update query.
> To add an update query:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press i to access update query configuration option.

> Step 5 | Press U to add a new update query for the UDR server.

> Step 6 | Specify the update query Id.

> Step 7 | Specify Base Domain Name (DN) for this query. The query will be executed on this domain only.

> Step 8 | Specify the search filter. This is the search criteria.

> Step 9 | Specify the output parameters for this query.

> Step 10 | Specify whether you want to execute this query or not.

> Step 11 | Specify the server Id of the UDR server, on which to execute this query.

> SSC Administration Console configures the update query and displays appropriate message.
> Viewing Update Query
> This section describes the procedure to view an existing update query.
> To view an update query:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press i to access update query configuration option.

> Step 5 | Press p to access view update query option.

> SSC Administration Console displays a list of all the configured update queries. For each query it displays all the configuration parameters explained in the previous section.
> Deleting Update Query
> This section describes the procedure to delete an existing update query.
> To delete an update query:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access UDR Administration option.

> Step 4 | Press i to access update query configuration option.

> Step 5 | Press r to delete an existing update query for the UDR server.

> Step 6 | Specify the id of an update query that you want to delete.

> SSC Administration Console deletes the update query, and displays appropriate message.
> Administering Event Notification Application
> This section describes the procedures to administer an event notification application.
> Event notifications are used to generate and send the notifications to subscribers. These notifications are mostly related to subscribers service usage and policy changes that may affect the subscriber.
> This section includes following sub-sections:

> • | Configuring Event Notification Server

> • | Configuring SMTP Server

> • | Configuring SMPP Server

> • | Configuring E-mail Layout

> • | Configuring Interface Monitor

> Configuring Event Notification Server
> This section describers the procedures to configure an event notification server.
> Event notification server is used by SSC to communicate with other components of PCC solutions such as IPCF that want to use the event notification functionality provided by SSC. Notification server can also be used to handle load balancing among SMTP and SMPP servers used by the event notification module.
> Event notification server configuration involves following tasks:

> • | Configuring Event Notification Server Instance

> • | Viewing Event Notification Server Instance

> Configuring Event Notification Server Instance
> This section describes the procedure to configure an event notification server instance.
> To configure an event notification server instance:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press S to configure an event notification server.

> Step 5 | Specify server IP address.

> Step 6 | Specify server port to communicate with this server.

> SSC Administration Console displays the IP address and port for all configured event notification servers.
> Viewing Event Notification Server Instance
> This section describes the procedure to view an event notification server instance.
> To view an event notification server instance:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press a to access event notification server configuration option.

> Step 5 | Press V to view existing server configuration.

> SSC Administration Console displays the IP address and port for all configured event notification servers.
> Configuring SMTP Server
> This section describes the procedures to configure an SMTP server.
> Simple Mail Transfer Protocol (SMTP) is a standard used by Internet Protocol (IP) networks to transmit e-mails. SMTP is used by mail servers and Mail Transfer Agents (MTAs) to send or receive mails. Mail client applications use SMTP to send messages to servers. SSC allows you to configure SMTP servers that can be used to send event notification related messages as e-mails.
> SMTP server configuration involves following tasks:

> • | Configuring Primary SMTP Server

> • | Configuring Secondary SMTP Server

> • | Viewing SMTP Server Configuration

> Configuring Primary SMTP Server
> This section describes the procedure to configure primary SMTP server.
> To configure primary SMTP server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press b to access SMTP server configuration option.

> Step 5 | Press P to configure primary SMTP server.

> Step 6 | Specify the server IP address.

> Step 7 | Specify the port used to communicate with this server.

> Step 8 | Specify the e-mail throttle rate. This indicates maximum number of e-mails that can be sent per second.

> SSC Administration Console configures the server or displays appropriate error message.
> Configuring Secondary SMTP Server
> This section describes the procedure to configure secondary SMTP server.
> To configure secondary SMTP server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press b to access SMTP server configuration option.

> Step 5 | Press S to configure secondary SMTP server.

> Step 6 | Specify IP address of the machine that is hosting secondary SMTP server.

> Step 7 | Specify the port used to communicate with this server.

> Step 8 | Specify e-mail throttle rate. This rate indicates maximum number of e-mails that can be sent per second.

> SSC Administration Console configures the secondary SMTP server or displays appropriate error message.
> Viewing SMTP Server Configuration
> This section describes the procedure to view configuration of existing SMTP servers.
> To view SMTP server configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press b to access SMTP server configuration option.

> Step 5 | Press V to view existing SMTP server configuration.

> SSC Administration Console displays IP address, port that is to be used for communication with this server, and e-mail throttle rate for all the configured primary as well as secondary SMTP servers.
> Configuring SMPP Server
> This section describes the procedures to configure an SMPP server.
> Short Message Peer to Peer (SMPP) protocol is used for exchanging SMS messages between Short Message Service Centers (SMSCs) and external short messaging entities. SSC allows you to configure SMPP servers that can be used to send event notifications and related messages as an SMS.
> SMPP server configuration involves following tasks:

> • | Configuring Primary SMPP Server

> • | Configuring Secondary SMPP Server

> • | Viewing SMPP Server Configuration

> Configuring Primary SMPP Server
> This section describes the procedure to configure primary SMPP server.
> To configure primary SMPP server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press c to access SMPP server configuration option.

> Step 5 | Press P to configure primary SMPP server.

> Step 6 | Specify client system Id. This indicates unique identification number of client system or subscriber system. This is supplied by SMPP provider.

> Step 7 | Specify password to access the machine hosting SMPP server.

> Step 8 | Specify system type. This indicates the category of client (or subscriber) system. Maximum 8 characters are allowed to indicate the system type.

> System type is always SMPP for an SMPP server.

> Step 9 | Specify the service type. This indicates the category of service being used by the subscribers receiving this notification. Maximum 8 characters are allowed to indicate the service type.

> Service type is the event, regarding which the notification is being sent thru SMS.

> Step 10 | Specify the IP address or FQDN of the SMPP primary server. This indicates the IP address or Fully Qualified domain Name (FQDN) of the machine that is hosting the SMPP server.

> Step 11 | Specify server port. This indicates the port number that is to be used for communicating with the machine that is hosting SMPP server.

> Step 12 | Specify source address. This indicates IP address of the SMPP server.

> Step 13 | Specify server response time in seconds. This indicates the time by which the machine hosting the event notification server should acknowledge or drop the event request.

> Step 14 | Specify enquire link time in seconds. This indicates time by which the link is accessible.

> Step 15 | Specify event throttle rate. This rate indicates maximum number of SMSs that can be sent per second.

> SSC Administration Console configures primary SMPP server or displays appropriate error message.
> Configuring Secondary SMPP Server
> This section describes the procedure to configure secondary SMPP server.
> To configure secondary SMPP server:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press c to access SMPP server configuration option.

> Step 5 | Press S to configure secondary SMPP server.

> SSC Administration Console configures parameters for secondary SMPP server, as per step 6 to step 15 of previous section – Configuring primary SMPP server.
> Viewing SMPP Server Configuration
> This section describes the procedure to view configuration of SMPP servers.
> To view SMPP server configuration:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press c to access SMPP server configuration option.

> Step 5 | Press V to view existing SMPP server configuration.

> SSC Administration Console displays configured values of SMPP server parameters, mentioned in sections configuring primary and secondary SMPP servers.
> Important: This information is displayed for all configured SMPP servers i.e. for primary as well as secondary servers.
> Configuring E-mail Layout
> This section describes the procedures to configure an e-mail layout.
> E-mail layout configuration involves following tasks:

> • | Configuring E-mail Parameters

> • | Viewing E-mail Parameters

> Configuring E-mail Parameters
> This section describes the procedure to configure e-mail parameters.
> To configure e-mail parameters:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press d to access e-mail parameters configuration option.

> Step 5 | Press P to configure e-mail parameters.

> Step 6 | Specify e-mail footer.

> Step 7 | Specify e-mail header.

> Step 8 | Specify sender's e-mail address.

> SSC Administration Console configures e-mail parameters or displays appropriate error message.
> Viewing E-mail Parameters
> This section describes the procedure to view mail parameters.
> To view e-mail parameters:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press d to access mail parameters configuration option.

> Step 5 | Press V to view existing e-mail parameters.

> SSC Administration Console displays the header, footer and sender’s e-mail address that will be used for sending the event notification thru e-mail
> Configuring Interface Monitor
> This section describers the procedures to configure and view interface parameters for event notification interface.
> SSC allows you to configure and view the retry count and retry interval for event notification interface.
> Interface monitor configuration involves following tasks:

> • | Configuring Retry Parameters for Event Notification (EN) Interface

> • | Viewing Retry Parameters for Event Notification (EN) Interface

> Configuring Retry Parameters for Event Notification (EN) Interface
> This section describes the procedure to configure retry parameters for an EN interface.
> To configure retry parameters for an EN interface:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press e to access interface monitor configuration option.

> Step 5 | Press C to configure the retry parameters for EN interface.

> Step 6 | Specify interface retry count.

> Step 7 | Specify interface retry interval.

> SSC Administration Console configures interface monitoring parameters.
> Viewing Retry Parameters for Event Notification (EN) Interface
> This section describes the procedure to view retry parameters, configured for an EN interface.
> To view an event notification server instance:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access Event notification Application Administration (EventAppAdmin) options.

> Step 4 | Press e to access interface monitor configuration option.

> Step 5 | Press V to view existing retry parameters for the EN interface.

> SSC Administration Console displays interface retry count and interface retry interval configured for the EN interface.
> Monitoring SSC Performance Using Console
> This section describes the procedures to use the SSC Administration Console, to monitor the performance of SSC system.
> This section includes following sub-sections:

> • | Monitoring System Log

> • | Monitoring System Statistics

> • | Monitoring Resources

> • | Monitoring Threshold Policies

> Monitoring System Log
> This section describes the procedures to monitor the system logs.
> SSC node, logs certain system parameters periodically. System logs record information about the web servers used in the deployment along with session and system information. These logs can be used for troubleshooting issues related to both system hardware and related operating system software used by the SSC node.
> Depending upon the deployment configuration, these logs can be:

> • | stored locally in files on the SSC host machines.

> • | using system syslog, these logs can be stored on some external server.

> Important: System logs are different from event logs. Refer SSC Logs Administration, for more information on event logs.
> System logs are categorized as:

> • | System Log

> • | Session Log

> • | Web Server Log.

> The web server logs are further categorized as:

> • | Web server error logs: These contain the errors encountered while accessing the web server. These are stored in error.log file in ./3rdparty/apapche/logs directory.

> • | Web server access logs: These contain access details for the web server. These are stored in access.log file in ./3rdparty/apachelogs directory.

> • | AXIS framework log: These contain SSC framework related information. These are stored in axis.log file in ./log directory.

> System logs monitoring involves following tasks:

> • | Accessing System Log

> • | Accessing Session Log

> • | Accessing Web Server Log

> Accessing System Log
> This section describes the procedure to access system logs.
> To access system log:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press a to access system log option.

> Step 5 | Press S to view system logs.

> SSC Administration Console displays the locations where system process logs as well as system start-up and internal log files are created.
> Important: The file sn-SSC.log contains system process logs and the file startup.log contains system start-up and internal logs.
> Accessing Session Log
> This section describes the procedure to access session log.
> To access session log:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press n to access session log option.

> SSC administration Console displays location of the session log file.
> Important: The file session_xxxxx.log contains the session log, where xxxxxx is concatenation of the date on which the logs are generated and a system generated number. For example a file session_2010122117346.log stores the session logs for 21st December 2010.
> Accessing Web Server Log
> This section describes the procedure to access web server log.
> To access web server log:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press w to access web server log option.

> SSC administration Console displays location of the web server log files.
> Monitoring System Statistics
> This section describes the procedures to monitor the system statistics.
> SSC node stores certain system parameters at periodic time interval. These parameters can be used to monitor the system performance as well as for troubleshooting purpose.
> Depending upon your access privilege following system statistics views are available:

> • | Summary View: This view generates a summary of important statistical parameters.

> • | By Process View: The SSC node spawns different processes such as SysMgr, AppMgr, EnCtrl and ShCtrl for the installed SSC components. This view displays the statistical parameters related to the selected process.

> • | Refresh View: This view updates the statistical information on the UI with latest available values for the selected parameters.

> • | Clear Stats View: This view clears the displayed values of bulk statistics parameters.

> Monitoring system statistics involves following tasks:

> • | Viewing System Statistics by Summary

> • | Viewing System Statistics by Process

> • | Clearing System Statistics View

> • | Refreshing System Statistics View

> Viewing System Statistics by Summary
> This section describes the procedure to view system statistics summary.
> To access system statistics by summary:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press b to access system statistics option.

> Step 5 | Press s to access the summary view.

> SSC Administration Console displays a summary of system statistics. It displays current values of important statistical parameters related to different SSC processes such as Sh and event notification applications, UDR controller, that are active for this SSC instance.
> Viewing System Statistics by Process
> This section describes the procedure to view system statistics associated with various SSC processes.
> To access system statistics by process:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press b to access system statistics option.

> Step 5 | Press P to access system statistics related to specific processes.

> SSC Administration Console displays active processes associated with this instance of SSC.

> Step 6 | Specify the number associated with process, whose statistics you want to view.

> Step 7 | enter N if you want to view IPC statistics, V for verbose display or B for basic display.

> Step 8 | Specify the instance, whose statistical parameters you want to view.

> SSC Administration Console displays available data or appropriate error message.
> Clearing System Statistics View
> This section describes the procedure to clear the displayed statistics.
> To clear system statistics view:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press b to access system statistics option.

> Step 5 | Press t to clear the displayed statistics.

> SSC Administration Console displays active process related to this SSC instance.

> Step 6 | Specify the process for which you want to clear the bulk statistics.

> SSC Administration Console clears the statistics related to this process.
> Refreshing System Statistics View
> This section describes the procedure to refresh the displayed statistics.
> To refresh system statistics view:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press b to access system statistics option.

> Step 5 | Press R to refresh existing view.

> SSC Administration Console displays updated values for the bulk statistics.
> Important: The refresh view option will work only when you have selected summary or by process view options.
> Monitoring System Resources
> This section describes the procedures to monitor the system resources using thresholds.
> Threshold is a concept used to monitor a system, such as SSC, for conditions that could potentially introduce errors or cause outage. In most cases these conditions are temporary, such as high CPU utilization or inconsistency in the processes associated with scheduler or heart beat daemon and are resolved quickly.
> However continuous occurring of such conditions in large number and during specific time interval may indicate larger issues.
> Thresholds help to identify such conditions and allow administrators to take preventive actions.
> Depending upon the system configuration following threshold models are supported:

> • | Alert: A resource is monitored and alert condition occurs when value associated with this resource reaches or exceeds the configured high threshold within specified polling interval. An alert is then generated and sent at the end of polling interval.

> • | Alarm: For a resource, both high and low thresholds are defined, alarm condition occurs when resource value reaches or exceeds high threshold value, in such case alarm is generated and sent at end of polling interval. This alarm is cleared if during the next polling interval the resource value equals or falls below the low threshold value.

> Thresholds can be used for system administration as well as troubleshooting purpose.You can configure threshold percentage for certain system resources such as processes associated with CPU usage, logging or scheduling.
> As per the deployment configuration and your access privileges, you can view or configure the thresholds associated with following:

> • | System resources.

> • | System processes.

> • | Applications.

> As per your deployment system resources can be further categorized as:

> • | CPU

> • | SWAP

> As per your deployment, active SSC processes associated with this SSC instance can be categorized as:

> • | Heart Beat Daemon (HbD)

> • | Log Daemon (LogD)

> • | System Manager (SysMgr)

> • | Scheduler

> • | Sh Controller (ShCtrl)

> • | Application Manager (AppMgr)

> • | Event Notification Controller (EnCtrl)

> • | Profile Controller (ProCtrl)

> • | UDR Manager(UdrMgr)

> As per your deployment the applications associated with this SSC instance can be categorized as:

> • | Maximum active Sh sessions.

> • | Maximum input queue size for application manager per blade.

> • | Maximum input queue size for application manager across the system.

> System resource monitoring involves following tasks:

> • | Viewing Thresholds

> • | Configuring Thresholds

> • | Viewing System Status

> Viewing Thresholds
> This section describes the procedure to view thresholds.
> To view thresholds:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press C to access resource monitor option.

> Step 5 | Press V to view existing thresholds.

> SSC Administration Console displays thresholds in percentage for processes associated with configured resources.
> Configuring Thresholds
> This section describes the procedure to configure thresholds.
> To configure thresholds:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press C to access resource monitor option.

> Step 5 | Press C to configure thresholds.

> Step 6 | Specify thresholds in percentage for process associated with configured resources.

> Important: The SSC installation process, sets the default threshold values for resources while configuring the data base.
> Viewing System Status
> This section describes the procedure to view system status.
> To view system status:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press C to access resource monitor option.

> Step 5 | Press S to view system status.

> SSC administration Console displays the system status. it displays percentage of active processes associated with the host name.
> Important: System status includes information such as active processes and Sh sessions associated with the host (or blade) name. This includes processes such as Logd. SysMgr, ShCtrl as well as processes associated with CPU and swap. The status also displays items in input queue for the AppMgr process.
> Monitoring Threshold Policies
> This section describes the procedures to monitor threshold policies.
> Threshold policies can be used for monitoring the service usage of the subscribers. You can also use policies for administering some parameters of SSC.
> Monitoring threshold policies involves following tasks:

> • | Viewing Threshold Policies

> • | Configuring Threshold Policies

> Viewing Threshold Policies
> This section describes the procedure to view threshold policies.
> To view threshold policies:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press d to access threshold policy option.

> Step 5 | Press V to view existing threshold policies.

> SSC administration Console displays a list of configured threshold policies.
> Important: Depending upon services that are being offered and your threshold configuration strategy, threshold policies can be categorized as, threshold breach policies or maximum active Sh session breach policies.
> Configuring Threshold Policies
> This section describes the procedure to configure threshold policies.
> To configure threshold policies:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 5 to access performance options.

> Step 4 | Press C to access resource monitor option.

> Step 5 | Press P to configure a threshold policy.

> Step 6 | Specify whether you want to reject the new session when the threshold is breached.

> SSC Administration Console configures the threshold breach policy and displays appropriate message.
> Profile Administration
> This section describes the procedures to administer the subscriber profile.
> Important: The profile administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then profile administration option can be accessed by pressing 1 otherwise it can be accessed by pressing 6 or associated option number. For more information refer User Administration section.
> A subscriber profile identifies various usage and data plans associated with a subscriber, along with the privileges and entitlements that can be availed by the profile holder.
> Depending upon the services that are being provided, a subscriber profile has following parameters:

> • | Mobile Subscriber ISDN Number (MSISDN).

> • | International Mobile Subscriber Identity (IMSI).

> • | Enable e-mail flag.

> • | Enable SMS flag.

> • | Subscription Status.

> • | Flag Name.

> • | Flag value.

> • | Billing start date.

> This section includes following sub-sections:

> • | Viewing Subscriber Profile and Usage

> • | Administering Subscriber Profile

> • | Administering Plans

> Viewing Subscriber Profile and Usage
> This section describes the procedures to view subscriber’s profile and service usage.
> Viewing subscriber profile and associated usage of services involves following tasks:

> • | Viewing Existing Subscriber Profile

> • | Viewing Service Usage

> Viewing Existing Subscriber Profile
> This section describes the procedure to view existing subscriber profile.
> To view existing profile:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press a to access view profile option.

> Step 5 | Specify International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN) or NAI associated with the subscriber whose profile you want to view.

> SSC Administration Console displays the subscriber record.
> Viewing Service Usage
> This section describes the procedure to view existing usage of a subscriber profile.
> To view usage:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press b to access view usage option.

> Step 5 | Specify International Mobile Subscriber Identity (IMSI) or Mobile Subscriber ISDN Number (MSISDN) or NAI associated with the subscriber, whose usage you want to view.

> Step 6 | Specify do you want to view usage for a specific data plan.

> Step 7 | Provide the plan id, if you have answered as yes in the previous step.

> Step 8 | Specify plan name, if you have answered as yes in step 6.

> SSC Administration Console displays the subscriber usage or appropriate error message.
> Administering Subscriber Profile
> This section describes the procedures to administer a subscriber profile.
> Subscriber profile administration involves following tasks:

> • | Adding Subscriber Profile

> • | Deleting Subscriber Profile

> • | Modifying Subscriber Profile

> Adding Subscriber Profile
> This section describes the procedure to add a subscriber profile.
> To add a subscriber profile:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press c to access add subscriber option.

> Step 5 | SSC Administration Console displays a message for providing subscriber credentials.

> Important: For steps 6 to 8, press enter key if you do not want to change the existing value.

> Step 6 | Specify either IMSI, MSISDN or NAI as an id for this subscriber.

> Step 7 | Specify subscriber name and description.

> Step 8 | Specify Billing Date in format DD/MM/YYYY.

> Step 9 | Specify subscription tire.

> Step 10 | Specify whether you want to send SMS notifications to this subscriber.

> Step 11 | Specify e-mail address for sending the notifications through mail.

> Step 12 | Specify whether you want to give profile attribute to this subscriber.

> SSC Administration Console communicates this information to the back-end database and displays appropriate message.
> Deleting Subscriber Profile
> This section describes the procedure to delete a subscriber profile.
> To delete a subscriber profile:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press d to access delete subscriber option.

> Step 5 | Specify either IMSI, MSISDN or NAI as an id for this subscriber whose record you want to delete from the database.

> SSC Administration Console deletes the record and displays appropriate message. Or it displays an error message indicating that such record is not available.
> Modifying Subscriber Profile
> This section describes the procedure to modify a subscriber profile.
> To modify a subscriber profile:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press e to access modify subscriber option.

> Step 5 | Specify either IMSI, MSISDN or NAI as an id for this subscriber, whose record you want to modify in the database.

> Important: For steps 6 to 8, press enter key if you do not want to change the existing value.

> Step 6 | Specify subscriber name and description.

> Step 7 | Specify Billing Date in format DD/MM/YYYY.

> Step 8 | Specify subscription tire.

> Step 9 | Specify whether you want to send SMS notifications to this subscriber.

> Step 10 | Specify e-mail address for sending the notifications through mail.

> Step 11 | Specify whether you want to give profile attribute to this subscriber.

> SSC Administration Console communicates this information to the back-end database and displays appropriate message.
> Administering Plans
> This section describes the procedures to administer usage and data plans for the subscriber.
> Administering usage and data plans for the subscribers involves following tasks:

> • | Associating Plan

> • | Toping -up Quota

> • | Updating Plan

> • | Resetting Usage

> • | Recharging Plan

> • | Disassociating Plan

> Associating Plan
> This section describes the procedure to associate a usage or data plan with the subscriber profile.
> To associate a plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press f to access associate plan option.

> Step 5 | Specify subscriber profile details.

> Step 6 | Specify details for the data plan such as Plan Name, Subscription order, start date and end date in the format DD/MM/YYYY.

> Step 7 | Specify whether you want to generate the notifications for this subscriber.

> Step 8 | Specify whether you want to associate more plans for this subscriber.

> Step 9 | If you have selected y in the previous step, then continue to provide the details for additional data plans.

> SSC Administration Console associates the specified data plans with this subscriber. If such plans are not available in the database, then it displays appropriate error message.
> Important: While specifying subscriber profile details, you can use either IMSI/MSIDN or NAI of this subscriber as well as its subscriber id.
> Toping -up Quota
> This section describes the procedure to update the usage limit or to top-up the quota for subscriber.
> To top-up quota:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press g to access top-up quota option.

> Step 5 | Specify subscriber profile details. While specifying subscriber profile details, you can use either IMSI/MSIDN or NAI of this subscriber as well as its subscriber id.

> Step 6 | If you are specifying the top-up quota for a data plan, then specify plan name or plan Id.

> Step 7 | If you are specifying the top-up quota for the service plan, then specify plan name along with parent plan name or plan Id.

> Step 8 | Specify volume quota in bytes.

> Step 9 | Specify time quota in seconds.

> SSC Administration Console updates the values in the data base and displays appropriate message.
> Updating Plan
> This section describes the procedure to update a usage or data plan.
> To update plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press h to access update plan option.

> Step 5 | Specify subscriber credentials. You can use either IMSI/MSIDN or NAI of this subscriber as well as its subscriber id, for specifying the credentials. SSC Administration Console will update the subscription details for this subscriber.

> Step 6 | Specify plan name.

> Step 7 | Specify subscription order.

> Step 8 | Specify start date.

> Step 9 | Specify end date.

> Step 10 | Specify the subscription status details such as 1- disabled, 2 – Forever, 3- Enabled, 4- For current billing cycle. You can specify the required status by entering associated number.

> Step 11 | Specify whether you want to generate the notification.

> Step 12 | Specify whether you want to update more plans. If you select yes, then provide the information.

> SSC Administration Console updates the plan in the database.
> Resetting Usage
> This section describes the procedure to re-set a subscriber’s service usage.
> To re-set usage:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press j to access reset usage option.

> Step 5 | Specify the subscriber profile key such as subscriber id, of the subscriber whose usage you want to reset

> Step 6 | Specify the id or name of the plan that you want to reset.

> Important: For re-setting a service plan you need to specify the id of the parent plan as well.

> Step 7 | SSC Administration Console re-sets the subscriber usage that is associated with the selected service plan or displays appropriate error message.

> Recharging Plan
> This section describes the procedure to re-charge a data or service plan associated with the subscriber.
> To re-charge plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press k to access recharge plan option.

> Step 5 | Specify the subscriber profile key such as subscriber id, of the subscriber whose plan you want to recharge.

> Step 6 | Specify the id or name of the plan that you want to recharge.

> Important: For re-charging a service plan you need to specify the id of the parent plan as well.

> Step 7 | SSC Administration Console recharges the selected plan associated with this subscriber or displays associated error message.

> Disassociating Plan
> This section describes the procedure to dis-associate a usage or data plan.
> To disassociate a plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 1 to access profile administration option.

> Step 4 | Press i to access disassociate plan option.

> Step 5 | Specify subscriber credentials. You can use either IMSI/MSIDN or NAI of this subscriber as well as its subscriber id, for specifying the credentials.

> Step 6 | Specify the id or name of the plan that you want to disassociate from this subscriber.

> SSC Administration Console disassociates this plan from subscriber or displays appropriate error message.
> Group Administration
> This section describes the procedures to administer the subscriber group accounts.
> Important: The group administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then group administration option can be accessed by pressing 2 otherwise it can be accessed by pressing 7 or associated option number. For more information refer User Administration section.
> The group account is mostly associated with family plan.
> This section includes following sub-sections:

> • | Manage Group

> • | Manage Members

> • | Manage Subscriptions

> Manage Group
> This section describers the procedure to view, add and delete group accounts.
> Managing group profile involves following tasks:

> • | Viewing Existing Group Profile

> • | Adding Group Account

> • | Deleting Group Account

> Viewing Existing Group Profile
> This section describes the procedure to view an existing group profile.
> To view existing group profile:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access group administration option.

> Step 4 | Press a to access view option.

> This option allows you to view existing group accounts and plans.

> Step 5 | Press V to access view details option.

> Step 6 | Specify the group name whose details you want to view.

> SSC Administration Console displays the group profile details such as its name, MSISDN, subscription tire, billing date, short description of the group, its status and e-mail as well as SMS notification status.

> Step 7 | Press P to view plan details option.

> Step 8 | Specify group name.

> SSC Administration console displays the plan details.
> Adding Group Account
> This section describes the procedure to add a group account.
> To add a group account:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access group administration option.

> Step 4 | Press b to add a new group account.

> Step 5 | Specify the group account name.

> Step 6 | Specify the description of this group account.

> Step 7 | Specify the subscription tire associated with this group.

> Step 8 | Specify SMS notification preference. If you select, yes, then notifications will be sent as SMS.

> Step 9 | Specify MSISDN.

> Step 10 | Specify e-mail notification preference. If you select yes, then notifications will be sent as an e-mail.

> Step 11 | If you select yes in the previous step, then specify the e-mail address.

> Step 12 | Specify billing date in dd/mm/yyyy format.

> Deleting Group Account
> This section describes the procedure to delete a group account.
> To delete a group account:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access group administration option.

> Step 4 | Press c to delete an existing group account.

> SSC Administration Console deletes the group account and displays appropriate message.
> Manage Members
> This section describes the procedures to add a member to and delete a member from group account.
> Managing members of a group account involves following tasks:

> • | Adding Member to Group Account

> • | Deleting Member from Group Account

> Adding Member to Group Account
> This section describes the procedure to add a member to a group account.
> To add a member to group account:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access group administration option.

> Step 4 | Press d to add a member to an existing group account.

> Step 5 | Specify name of the group to which you want to add this member.

> Step 6 | Specify subscriber credentials. You can use either IMSI/MSIDN or NAI of this subscriber as well as its subscriber id, and add this subscriber to the group.

> Step 7 | Specify whether you want to add this subscriber as group administrator

> SSC Administration Console adds the member to the group and displays appropriate message.
> Deleting Member from Group Account
> This section describes the procedure to delete a member from a group account.
> To delete a member from group account:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access group administration option.

> Step 4 | Press e to delete a member from an existing group account.

> Step 5 | Specify name of the group account from which you want to delete this member.

> Step 6 | Specify whether you want to delete this subscriber from the associated group account.

> SSC Administration Console adds the member to the group and displays appropriate message.
> Manage Subscriptions
> This section describes the procedure to associate a plan with the group profile.
> Managing subscriptions for a group account involves following tasks:

> • | Associating Plan with Group Profile

> Associating Plan with Group Profile
> This section describes the procedure to associate a plan with group profile.
> To associate a plan with group profile:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 2 to access group administration option.

> Step 4 | Press f to associate a plan with an existing group account.

> Step 5 | Specify the group account name.

> Step 6 | Specify subscription order.

> Step 7 | Specify start date and end date in DD/MM/YYYY format.

> Step 8 | Specify whether you want to generate the notifications.

> Step 9 | Specify whether you want to associate more plans with this group.

> Step 10 | If you select yes in previous step, then provide the information for additional plans.

> SSC Administration Console associates the plan with the group account and displays appropriate message.
> Plan Administration
> This section describes the procedures to administer the subscription and data plans.
> Important: The plan administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then plan administration option can be accessed by pressing 3 otherwise it can be accessed by pressing 8 or associated option number. For more information refer User Administration section.
> This section includes following sub-sections:

> • | View Plans

> • | Administer Plans

> View Plans
> This section describes the procedures to view a specific plan or all plans.
> Viewing plans involves following tasks:

> • | Viewing a Specific Plan

> • | Viewing All Plans

> Viewing a Specific Plan
> This section describes the procedure to view a specific usage or data plan.
> To view a specific plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access plan administration option.

> Step 4 | Press a to access view option.

> Step 5 | Specify the name of the plan whose details you want to view.

> SSC Administration Console displays the plan details such as plan id, name, type, volume and time, usage and quota limit along with validity and start as well as end date.
> Viewing All Plans
> This section describes the procedure to view all existing usage as well as data plans.
> To view all plans:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access plan administration option.

> Step 4 | Press e to access view all plans option.

> SSC Administration Console displays a list of all existing usage as well as data plans.
> Administer Plans
> This section describers the procedures to administer plans.
> Administering plans involves following tasks:

> • | Adding New Plan

> • | Deleting Plan

> • | Modifying Plan

> Adding New Plan
> This section describes the procedure to add a new usage or data plan.
> To add a new plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access plan administration option.

> Step 4 | Press b to add a new plan.

> Step 5 | Specify the name and short description for a new plan.

> Step 6 | Specify base usage limits, such as volume limit in bytes and time usage limits in seconds.

> Step 7 | Specify the validity period for this plan in days.

> Step 8 | Specify the start date for this plan in YYYY –MM- DD format and the start time in HH:MM:SS format.

> Step 9 | Specify end date and end time in same format as of start date and start time.

> Step 10 | Specify the roaming details, use values 1 for home, 2 for roaming and 3 for both.

> Step 11 | Enter quota limit type, use values 1 for hard limit and 2 for soft limit.

> Step 12 | Specify y if you want to add another threshold for this plan.

> Important: While configuring a new plan, if you select the threshold category as time or any, then you need to specify absolute and percentage value for such threshold category.

> Step 13 | Specify the quota or usage type, use values 1 for volume, 2 for any and 3 for time based usage of the service.

> Step 14 | If you have selected volume as a quota or usage type then specify absolute volume.

> Step 15 | Specify y if you want to generate a notification, when the threshold mentioned in previous steps is crossed

> Step 16 | Specify whether you want to configure additional usage limits (service plans) for this plan. If you select yes, then specify the name for the usage limit (service plan).

> Step 17 | Specify the volume usage limits in bytes and time usage limits in seconds.

> Step 18 | Specify the validity period.Select value 1 for hard limit and 2 for soft limit.

> Step 19 | Specify whether you want to add additional threshold. If you select no, then specify whether you want to configure additional usage limits (service plans).

> Once you have configured all the data plans and corresponding usage limits (service plans), then SSC Administration Console displays the message that the plan is added successfully to the database.
> Deleting Plan
> This section describes the procedure to delete an existing plan.
> To delete a plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access plan administration option.

> Step 4 | Press c to access delete plan option.

> Step 5 | SSC Administration Console displays a list of existing plans. Select the plan that you want to delete.

> SSC Administration Console deletes the selected plan.
> Modifying Plan
> This section describes the procedure to modify an existing plan.
> To modify a plan:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 3 to access plan administration option.

> Step 4 | Press d to access modify plan option.

> Step 5 | Specify name of the plan that you want to modify.

> Step 6 | Specify following values as per the category of modifications that you want to perform on the existing plan.Select 1 for changing plan details, 2 for changing existing usage limits, 3 for adding new usage limits to the plan, 4 for deleting existing usage limits from the plan.

> Step 7 | If you select option 1 in previous step, then specify the description for the plan.

> Step 8 | Specify updated volume and time usage limits.

> Step 9 | Specify new validity period.

> Step 10 | Specify new start and end date as well as time.

> Step 11 | Specify the changed roaming status for the plan, the valid options are 1 for home, 2 for roaming and 3 for both.

> Step 12 | Specify changed quota limits, the valid options are 1 – for hard limit, 2 – for soft limit.

> Step 13 | Select y, if you want to change any other threshold for this plan.

> Step 14 | Specify updated quota type. Valid values are 1 for volume, 2 for any and 3 for time quota.

> Step 15 | Specify your choice for modified quota or usage and provide new absolute as well as percentage values.

> Step 16 | Specify whether you want to generate a notification when this threshold is crossed.

> Step 17 | Specify the template name, if you want to store this plan as a template.

> Step 18 | Specify whether you want to change any threshold for this plan.

> Step 19 | Specify whether you want to change volume, time or any other category of quota associated with this plan.

> SSC Administration Console updates the plan details in the database.
> Data Store Administration
> This section describes the procedures to administer the subscriber data store.
> Important: The data store administration option is available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials. If you have logged in using default policy administrator credentials then data store administration option can be accessed by pressing 4 otherwise it can be accessed by pressing 9 or associated option number. For more information refer User Administration section.
> This section includes following sub-sections:

> • | Administering Subscriber Tires

> • | Administering Profile Attributes

> • | Administering Notification Templates

> In a Policy Charging and Control (PCC) solution SSC acts as a data store for Subscriber Profile Registry (SPR). As per your PCC implementation and the services that are being offered, SSC stores following information in a database:

> • | Subscriber Tire.

> • | Profile Attribute.

> • | Notification Template.

> Administering Subscriber Tires
> This section describes the procedures to administer the data related to subscriber tire.
> Administering subscriber tire involves following tasks:

> • | Adding New Subscriber Tire

> • | Viewing All Subscriber Tires

> • | Viewing a Specific Subscriber Tire

> • | Deleting Specific Subscriber Tire

> Adding New Subscriber Tire
> This section describes the procedure to add a new subscriber tire.
> To add a new subscriber tire:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press a to access subscriber tire option.

> Step 5 | Press N to add a new tire.

> Step 6 | specify tire name.

> Step 7 | Specify description for this tire.

> SSC Administration Console adds the subscriber tire and displays appropriate message.
> Viewing All Subscriber Tires
> This section describes the procedure to view all existing subscriber tires.
> To view all existing subscriber tires:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press a to access subscriber tire option.

> Step 5 | Press V to view all existing subscriber tires.

> SSC Administration Console displays names of all available subscriber tires.
> Viewing a Specific Subscriber Tire
> This section describes the procedure to view details of a specific subscriber tire.
> To view a specific subscriber tire:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press a to access subscriber tire option.

> Step 5 | Press w to view a specific subscriber tire.

> Step 6 | Specify the name of subscriber tire, whose details you want to view.

> SSC Administration Console displays tire id, its name and description.
> Deleting Specific Subscriber Tire
> This section describes the procedure to delete a specific subscriber tire.
> To delete a subscriber tire:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press a to access subscriber tire option.

> Step 5 | Press i to access delete a subscriber tire option.

> Step 6 | Specify the name of subscriber tire, that you want to delete.

> SSC Administration Console deletes the subscriber tire and displays appropriate message.
> Administering Profile Attributes
> This section describes the procedures to administer the data related to profile attributes.
> Administering profile attributes involves following tasks:

> • | Adding New Attribute

> • | Viewing specific Profile Attribute

> • | Viewing All Profile Attributes

> • | Deleting Profile Attribute

> • | Updating a Profile Attribute

> Adding New Attribute
> This section describes the procedure to add a new attribute to the subscriber profile.
> To add a new attribute:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press b to access profile attribute option.

> Step 5 | Press N to add a new profile attribute.

> Step 6 | Specify a name for this profile attribute.

> Step 7 | Specify the expected value for this attribute.

> Step 8 | Specify default value for this attribute.

> SSC Administration Console adds this attribute to the subscriber profile.
> Viewing specific Profile Attribute
> This section describes the procedure to view a specific attribute of the subscriber profile.
> To view a specific profile attribute:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press b to access profile attribute option.

> Step 5 | Press V to access view option.

> Step 6 | Specify the name of subscriber profile attribute whose details you want to view.

> SSC Administration Console displays the attribute details such as its id, name, expected value and default value.
> Viewing All Profile Attributes
> This section describes the procedure to view a specific attribute of the subscriber profile.
> To view all profile attributes:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press b to access profile attribute option.

> Step 5 | Press w to access view all attributes option.

> SSC Administration Console displays a list of all configured subscriber profile attributes.
> Deleting Profile Attribute
> This section describes the procedure to delete a specific attribute of the subscriber profile.
> To delete a profile attribute:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press b to access profile attribute option.

> Step 5 | Press t to delete a profile attribute.

> Step 6 | specify the name of the profile attribute that you want to delete.

> SSC Administration Console deletes this profile attributes or displays appropriate error message.
> Updating a Profile Attribute
> This section describes the procedure to update a specific attribute of the subscriber profile.
> To update a profile attribute:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press b to access profile attribute option.

> Step 5 | Press U to update a profile attribute.

> Step 6 | specify the name of the profile attribute that you want to modify.

> Step 7 | Specify modified expected value for this attribute, or press enter to keep the expected value un-changed.

> Step 8 | Specify the modified default value for this attribute, or press enter to keep the default value un-changed.

> SSC Administration Console updates the profile attribute and displays appropriate message.
> Administering Notification Templates
> This section describes the procedures to administer the data related to notification templates.
> Administering notification templates involves following tasks:

> • | Adding New Notification Template

> • | Viewing Notification Template

> • | Viewing all Notification Templates

> • | Deleting Notification Template

> • | Updating Notification Template

> Adding New Notification Template
> This section describes the procedure to add a new notification template.
> To add new notification template:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press c to access notification template option.

> Step 5 | Press N to add a new template.

> Step 6 | specify template name.

> Step 7 | Specify event type associated with this notification template.

> Event type indicates occurrence of some event or status change related to the service usage of the subscriber.For example you can create an event type as say Quota80%Full, which indicates that the subscriber has utilized 80% of his or her quota.

> Step 8 | Specify the SMS message that you want to associate with this template or press enter to skip this option.

> Step 9 | Specify the e-mail message that you want to associate with this template or press enter to skip this option.

> SSC Administration Console adds the notification template to the database.
> Viewing Notification Template
> This section describes the procedure to view an existing notification template.
> To view a notification template:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press c to access notification template option.

> Step 5 | Press V to view an existing notification template.

> Step 6 | Specify the name of template that you want to view.

> SSC Administration Console displays the template id, name, associate event and description.
> Viewing all Notification Templates
> This section describes the procedure to view all available notification templates.
> To view all notification templates:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press c to access notification template option.

> Step 5 | Press w to view all configured notification templates.

> SSC Administration Console displays the list of all available notification templates.
> Deleting Notification Template
> This section describes the procedure to delete a notification template.
> To delete a notification template:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press c to access notification template option.

> Step 5 | Press t to delete an existing notification template.

> Step 6 | Specify name of the notification template that you want to delete.

> SSC Administration Console deletes this notification template and displays appropriate message.
> Updating Notification Template
> This section describes the procedure to update a notification template.
> To update a notification template:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 4 to access data store administration option.

> Step 4 | Press c to access notification template option.

> Step 5 | Press U to update a notification template.

> Step 6 | Specify name of the notification template that you want to update.

> Step 7 | Specify the event type associated with this notification template.

> Event type indicates occurrence of some event or status change related to the service usage of the subscriber.For example you can create an event type as say Quota80%Full, which indicates that the subscriber has utilized 80% of his or her quota.

> Step 8 | Specify updated notification message that you want to send through SMS or press enter key to keep this field blank.

> Step 9 | Specify the updated notification message that you want to send through e-mail or press enter key to keep this field blank.

> SSC Administration Console updates the notification template and displays appropriate message.
> Monitoring SSC Security Using Console
> This section describes the procedures to monitor the security of SSC.
> This section includes following sub-sections:

> • | Changing Password

> • | Monitoring Security Using System Audit

> • | Managing Session

> Changing Password
> This section describes how to change the system password.
> Changing Password
> This section describes the procedure to change system password.
> To change password:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 9 to access security option.

> Step 4 | Press a to access change password option.

> Step 5 | Specify old and new password.

> Step 6 | Confirm new password.

> SSC Administration Console changes the password and displays appropriate message.
> Monitoring Security Using System Audit
> This section describes the procedures to use audit logs to monitor security of SSC node.
> Various provisioning operations and events associated with the SSC deployment are recorded or audited. Such records are known as audit records. These records are categorized as system log, SPR log and event log. Audit records can be used for security, monitoring as well as troubleshooting purpose.
> An audit record contains:

> • | Audit Id A unique identifier for each record. The audit id is generated by the SSC.

> • | Event Id It represents a category of event associated with the SSC deployment. For example adding a subscriber is an event associated with SSC it will have an identifier, sending a notification through SMS is another event associated with SSC so it will have a different identifier.

> • | Module Id It represents the SSC module that has recorded or audited this information. For example provisioning events will be recorded by profile manager.

> • | Client Context It represent the type of client associated with this event. For example, the client can be SSC Console, a SOAP or XML API used for SSC provisioning or a PPT client.

> • | Subscriber Id It represents the subscriber associated with this event. For example when a subscriber is created or deleted then corresponding subscriber id will be stored in the audit record.

> • | Plan Id It represents a data, service or group plan associated with the event. For example if a plan is created or recharged then corresponding plan id will be stored in audit record.

> • | Audit Date It represents the date when this audit record is generated.

> • | Request Data It represents the data requested by the SSC operation. It is available in XML format.

> • | Response Data It represents the response received by the SSC operation. It is available in XML format.

> Important: Audit record stores only successful transactions. Unsuccessful transactions that do not affect SSC deployment are not stored.
> Depending upon your access privilege you can monitor and maintain security of the SSC instance by accessing following audit records:

> • | System Audit: This record category logs all the modifications in SSC configuration, such as changes in Sh or event notification controller.

> • | SPR Audit: This record category logs all the provisioning events such as addition, deletion or modification of subscriber profiles and usage as well as data plans.

> • | Event Log Audit:This record category logs all the notification events.

> Important: The SPR and Event Log audit options are available only when you log in to SSC Administration Console as policy administrator or as a user whose credentials include the policy administration credentials.
> Refer to sections SSC Logs Administration and Monitoring System Logs for detailed information.
> System as well as SPR or event audit involves following tasks:

> • | Viewing Logs

> • | Viewing Log Records

> • | Purging Log Records

> Viewing Logs
> This section describes the procedure to view system audit logs.
> To view logs:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 9 to access security option.

> Step 4 | Press b to access system audit option.

> Step 5 | Press V to access view logs option.

> Step 6 | Specify the start date and start time of the period for which you want to view the logs. In DD- MM-YYY HH:MM format.

> Step 7 | Specify the end date and end time in the format mentioned in the previous step.

> Step 8 | Select the filter that is to be used to access the SPR or event audit logs, by specifying y or n. You can select module id, event id or subscriber details as the filter.

> SSC Administration Console displays the logs.
> Viewing Log Records
> This section describes the procedure to view records of system audit log.
> To view log records:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 9 to access security option.

> Step 4 | Press b to access system audit option.

> Step 5 | Press L to access view log record option.

> Step 6 | Specify the record Id of the log record that you want to view.

> SSC Administration Console displays the log record.
> Purging Log Records
> This section describes the procedure to purge records of system audit log.
> To purge log records:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 9 to access security option.

> Step 4 | Press b to access system audit option.

> Step 5 | Press P to access purge record option.

> Step 6 | Specify the start date and start time of the period for which you want to view the logs. In DD- MM-YYY HH:MM format.

> Step 7 | Specify the end date and end time in the format mentioned in the previous step.

> Step 8 | Confirm the purge operation by selecting y or cancel it by selecting n.

> If you select y then SSC Administration Console permanently deletes the records filtered by start and end time.
> Managing Session
> This section describes how to manage system sessions.
> Viewing Existing Session
> This section describes the procedure to view existing system session.
> To view existing session:

> Step 1 | Login to the SSC node with administrative privileges.

> Step 2 | Access the SSC Administration Console by executing the script ./sscadm.

> Step 3 | Press 9 to access security option.

> Step 4 | Press c to access manage session option.

> Step 5 | Press V to view information regarding existing session.

> SSC Administration Console displays User Name, Role, Log on Time, time and date of Last Activity, for all the active sessions.

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