# PPT Administration

This chapter describes how to configure and administer the PPT application.

Policy Provisioning Tool (PPT) is an element of Cisco Policy Charging and Control (PCC) solution. PPT acts as a GUI based policy management tool used by service providers to design, implement and maintain policies. These policies can be used to provide various services to subscribers as well as control network usage via differential policies for different subscribers.
PPT application provides a GUI based wizard to perform following activities in the policy configuration and management process:

- Mapping attributes to a subscriber profile. This profile is used as a benchmark for applying policy to existing subscribers.
- Configuring session based usage monitors for the policy.
- Associating single or multiple data plans with the policy.
- Configuring the business logic for the policy using rules, rule bases as well as user defined actions and conditions.
- Generating a summary of the configured policy.
- Committing or transferring the configured policy to relevant IPCF instance.

IMPORTANT:

Refer on-line help of PPT application for more information and tasks related to configuration and maintenance of policies as well as configuration of IPCF and SSC instances in the PPT application.
PPT is an integral part of PCC solution and works in conjunction with other PCC components such as Intelligent Policy Control Function (IPCF) and Subscriber Service Controller (SSC) for policy management. PPT administration includes tasks such as:

- Configuring IPCF instances in the PPT application for provisioning IPCF related policy parameters such as QoS profiles or dynamic rules.
- Configuring SSC instances in the PPT application for provisioning SSC related policy parameters such as data plans or subscription tiers.
- Configuring PCEF instances in the PPT application for provisioning PCEF related policy parameters such as APN names, Ruledef names and Rulebase names.
- Administering users for the PPT application.
- Generating application monitoring information such as audit trail and debug information.

This chapter includes following sections:

- IPCF Setup
- SSC Setup
- PCEF Setup
- Synchronization
- User Administration
- Change Password
- Debug Information
- Audit Trail

IMPORTANT:

On user login, Administration or Subscriber Service Management page is displayed based on configuration present in the database. If IPCF and SSC are configured then Subscriber Service Management page is displayed. If either IPCF or SSC is not configured, then the default page is Administration page.

IPCF Setup

This section describes how to configure an IPCF instance in the PPT application.

The Intelligent Policy Control Function (IPCF) provides policy control and charging rule function in a core network. IPCF is supplemented by usage monitoring capability that is enabled by the policies related to data consumption and usage monitoring.

PPT acting as an integral part of the PCC solution, allows service providers to create, update and monitor policies using local libraries of rules and rule bases, as well as Access Point Names (APNs) that exist with Policy Control and Enforcement Function (PCEF).

IMPORTANT:

For detailed information and configuration examples of IPCF, refer the IPCF Administration Guide.
To configure an IPCF instance in the PPT application, following information is required:

- IPCF Name: This is the name of IPCF instance. User can specify any name by which this IPCF instance is to be identified.
- IP Address: This is the IP or IOP address for CORBA to communicate with Cisco© chassis running the IPCF instance. This IP address can be retrieved by executing show orbem status command on chassis. A sample output of this command is shown below:

      Service State
                  : On

      Management Functions
                 : FCAPS

      IOP Address
                  : 10.4.10.35

      SSL Port
                   : 12125

      TCP Port
                   : 12126

      Session Timeout
                   : 300 secs

      Max Login Attempts
                   : 3

      IIOP Transport
                   : On

      Number of Current Sessions
           : 0

      Number of Operations
      Completed  : 504

      Number of Events Processed
           : 0

      Avg Operation Processing
      time   : 7396 usecs

      (last 1000)  : 7519
      usecs

- Port Number: This is the TCP port over which the CORBA could communicate with an IPCF instance. This port number must be identical to the IIOP port setting on the IPCF. It can also be retrieved using the show orbem status command.

  IMPORTANT:

  IP address and Port number of the chassis can be obtained from IPCF administrator.

  CAUTION:

  If PPT and Web Element Manager (WEM) are co-located on single hardware platform, then ensure that WEM is installed before PPT and PostgreSQL component of PPT is not listening on port 5432 as this port is reserved for WEM.
- Application Server ID: This is the ID by which the PPT instance is identified by IPCF server. The application server id can be retrieved by executing show orbem client table command on Cisco© chassis. Application server Id is set on the IPCF chassis by executing commands similar to following set of commands using Command Line Interface (CLI) in EXEC Mode:

      [local]asr5000#configure

      [local]asr5000(config)#orbem

      [local]asr5000(config-orbem)#client id client_id password password

  This information can be retrieved by executing the show configuration command. The sample output of this command is shown below:

      orbem

      iiop-transport

      client id STARENT encrypted
      password 5c4a38dc2ff61f72

  CAUTION:

  If PPT and WEM are co-located on a single hardware platform, then ensure that, for the CORBA management both PPT and WEM are using different application server ids.
- Application Server Password: This is the password set for the ORBEM client configuration as shown in the above sample set of command lines. It is used by PPT application to communicate with the IPCF instance.

  IMPORTANT:

  Application server ID and password information can be obtained from the IPCF administrator.
- Node Type: A PCC deployment can contain multiple IPCF instances. An IPCF instance can be designated as a Primary or Secondary. At any given instance only one IPCF instance can be designated as Primary, where as multiple IPCF instances can be designated as Secondary. PPT communicates with Primary IPCF instance to exchange information such as PCC and data service, user defined conditions and actions, timedefs and traffic types.

IMPORTANT:

An IPCF instance can be configured in the PPT application even if it is not active or manageable, provided that correct values of all the configuration parameters mentioned above are available.

SSC Setup

This section describes how to configure an SSC instance in the PPT application.

Subscriber Service Controller (SSC) is a component of PCC solution. It acts as a Subscriber Profile Repository (SPR) for maintaining subscriber profile and service usage data. SSC uses centralized Policy Charging and Rules Function (PCRF) along with the SPR data store to assist policy implementation. SSC handles session state and account details information for subscribers. SSC also manages the event notification function for the PCC solution by sending e-mails and text messages to subscribers. SSC interacts with other components of PCC solution such as Customer Relationship Management (CRM), Operation Support System (OSS), and Billing Support System (BSS) for subscriber related information.

PPT interacts with an SSC instance using an XML-RPC interface and HTTP as a data transport mechanism.
To configure an SSC instance in the PPT application, following information is required:

- SSC Name: This is the name entered to identify the SSC machine where the profile controller of an SSC instance is installed.
- Main SSC IP Address: This is the IP address of the host on which SSC profile controller is running.

  IMPORTANT:

  SSC supports geo-redundancy with multiple SSC instances in different geographical locations. Each SSC instance can be accessed by the PPT application, by using IP address of the host on which profile controller of SSC is running. For the PPT application, only one SSC instance can be configured as a Primary instance and all other SSC instances are configured as Secondary.
- Port Number: This is the port using which the XML-RPC could communicate with profile controller interface of the active SSC instance. Default value for this port is 8080.
- Standby SSC IP Address: This is the IP address of host machine on which profile controller of the standby SSC instance is running.

  IMPORTANT:

  In a geo-redundant setup, there will be two physical SSCs each addressable with a different IP address. In case of a failover to the redundant SSC, administrator has to manually change the standby node to active in the PPT application. There is no automatic detection of SSC instance fail-over. Once the main node start working normally, administrator has to manually change the node back to Active. Primary SSC can also be active SSC if only the geo-redundancy is configured on SSC. IP address and Port information can be retrieved through the Apache configuration file httpd.conf or, it can be obtained from SSC administrator.
- Node Type: Select Primary or Secondary from drop-down list.

  IMPORTANT:

  When configuring an SSC node into the system, it has to be designated as primary/secondary. Primary node is like a reference node and all data which is displayed to the user is fetched from the node which is designated as the primary. While configuring an object on any of the nodes, it is mandatory to configure on the primary. So, user can configure on primary and secondary nodes but it is mandatory to configure on primary. The assumption is that all nodes added into PPT will have the same configuration.

IMPORTANT:

An SSC instance can be configured in the PPT application, even if it is not active or manageable, provided that correct values of all the configuration parameters mentioned above are available.

PCEF Setup

This section describes how to configure an PCEF instance in the PPT application.

Policy and Charging Enforcement Function, the logical function in 3GPP network is responsible for enforcing the policy and charging as per PCC rules.

PCEF, typically located at the gateway is responsible for enforcing the policy and charging related decisions received from PCRF. PCEF performs service data flow detection as well as gate enforcement for the data flows.
The functions done by PCEF are mainly to:

- Detect service data flows.
- Perform gate control over flows.
- Bearer binding as well issue bearer procedures.
- QoS enforcement based on the authorized policy decision.
- Perform charging based on the charging decision supplied by PCRF.

IPCF interfaces with Policy Charging and Enforcement Function (PCEF) over standard Gx interface. IPCF handles operation of PCC Rule and activate/deactivate/install/modify/remove the PCC rules at PCEF. PCC rule operation may fail on PCEF due to various reasons. In such failure cases PCEF sends back a Charging Rule Report containing PCC rules failed and corresponding failure cause.

IMPORTANT:

PPT server will fetch APNs, ruledef and rulebase directly from PCEF and cannot be configured/modified using PPT application client.
To configure an PCEF instance in the PPT application, following information is required:

- PCEF Name: This is the name of PCEF instance. User can specify any name by which this PCEF instance is to be identified.
- IP Address: This is the IP or IOP address for CORBA could communicate with Cisco© chassis running the PCEF instance. This IP address can be retrieved by executing show orbem status command on chassis. A sample output of this command is shown below:

      Service State
                  : On

      Management Functions
                 : FCAPS

      IOP Address
                   : 10.4.10.35

      SSL Port
                   : 12125

      TCP Port
                   : 12126

      Session Timeout
                   : 300 secs

      Max Login Attempts
                   : 3

      IIOP Transport
                   : On

      Number of Current Sessions
           : 0

      Number of Operations
      Completed  : 504

      Number of Events Processed
           : 0

      Avg Operation Processing
      time   : 7396 usecs

      (last 1000)  : 7519 usecs

- Port Number: This is the TCP port over which the CORBA could communicate with an PCEF instance. This port number must be identical to the IIOP port setting on the PCEF. It can also be retrieved using the show orbem status command.

  IMPORTANT:

  IP address and Port number of the chassis can also be obtained from PCEF administrator.

  CAUTION:

  If PPT and Web Element Manager (WEM) are co-located on single hardware platform, then ensure that WEM is installed before PPT and PostgreSQL component of PPT is not listening on port 5432. As this port is reserved for WEM.
- Application Server ID: This is the ID by which the PPT instance is identified by PCEF. The application server id can be retrieved by executing show orbem client table command on Cisco© chassis.

  CAUTION:

  If PPT and WEM are co-located on a single hardware platform, then ensure that, for the CORBA management both PPT and WEM are using different application server ids.
- Application Server Password: This is the password used by PPT application to communicate with the PCEF.

  IMPORTANT:

  Application server ID and password information can be obtained from the PCEF administrator.
- IPCF Controller: This is the IPCF that could communicate to the PCEF and conveys the policy and charging related decisions. The relation between PCEF and IPCF could be many to 1 i.e., multiple PCEF’s communicating to one IPCF.

Synchronization

This section describes various synchronization approaches.
PPT has to synchronize the IPCF/SSC/PCEF instances on the known/configured IPCFs, SSCs and PCEFs. The following are the reasons for synchronization:

- PPT has faster access to the configuration on all IPCFs/SSCs/PCEFs.
- Any changes made directly on the IPCF CLI or on the SSC or on the PCEF are also available at the PPT with some delay.
- PPT can do configuration comparisons across different IPCFs/SSCs/PCEFs.
- Reduce network traffic between the PPT server and IPCFs/SSCs/PCEFs.
- Synchronization helps in optimization of condition groups and action sets.

The following are various approaches used for synchronization:

- Manual Synchronization
- Automatic Synchronization

Manual Synchronization

Manual synchronization synchronizes IPCF/SSC/PCEF data when request is received from user. The possibilities could be to synchronize with all IPCFs/SSCs/PCEFs or only the selected IPCFs/SSCs/PCEFs. This type of synchronization can be supported through GUI and/or shell script.

The following figure displays Synchronization screen.

You can select an element to be synchronized and click Sync to synchronize. In the above figure, the Synchronization Status of SSC-1 and SSC-3 is Running, i.e., the synchronization is under process. For rest of the elements the status is Successful, i.e., the synchronization is complete.

Advantages:

Manual synchronization can be used at any time when there is a need to synchronize with IPCFs/SSCs/PCEFs. For example., if the operator does some changes directly on IPCFs/SSCs/PCEFs or knows that some changes have been done, then, manual synchronization can be done to get the changes in PPT.

Automatic Synchronization

Automatic synchronization takes place only when IPCF/SSC/PCEF state changes to manageable. It can happen that there are many state changes like manageable - unmanageable, unmanageable - manageable within a short time period. These changes can be due to network issues or they could be genuine state changes because of software malfunctioning on the IPCF/SSC/PCEF platform. To handle this scenario and to avoid repeated synchronization attempts because of this:

- API checks the 'last successful synchronization attempt time' and if it is more than an hour then only state change synchronization take places.
- The 'short time period' is configurable and the default is 1 hour.

Also when a new manageable IPCF/SSC/PCEF instance is added in PPT, the synchronization takes place automatically. Also when an IPCF/SSC/PCEF instance is deleted from PPT, then all the information related to that IPCF/SSC/PCEF instance is removed from the PPT database.

User Administration

This section describes how to administer users and generate audit trail as well as debug information.

For each user accessing the PPT application, a unique ID and password is provided. PPT application categorizes users as administrator and operator. Administrator user has the privileges to perform all the possible operations in the PPT application, where as only viewing privileges are provided to the operator user. The Operator user cannot add, delete, or modify any service or configuration using PPT application.
While adding a new user for the PPT application, the Session Timeout is set for the user. This time is set in number of minutes which ranges from 1 to 1440 minutes. With this session timeout setting, a user session expires when no request-response happens between the PPT client and PPT server during the prescribed time interval.In such a scenario the user has to login again and initiate a new session to access the PPT application.

IMPORTANT:

PPT installation creates a default user. The login credentials of this user can be used to create other users and assign administrator or operator roles to them. It is recommended that you change the password of the default user on first login. Contact Cisco support for the default username and password. The default session timeout for this user is 15 minutes.

The privilege, session timeout, and password for the users added through PPT application can be modified later, however the user ID once configured, is not allowed to be modified.

IMPORTANT:

Refer on-line help of PPT application for tasks related to user administration such as adding or modifying user credentials.

Change Password

PPT administrator can reset the application password of any other user using the Modify button in User Administration option. A logged-in user can change his or her password using Change Password option.

Debug Information

The debug information can be used for troubleshooting as well as monitoring purpose. PPT application logs information related to processes associated with its components such as Apache and notification server, PostgreSQL database.
Debug Information provides following options to generate this data:

- Level 1: Choosing this option, user can access application, installation as well as web server logs. The following is the list of the commands for level 1:
  - getLogDir
  - getFile
  - getDirectory
  - executeCommand
  - getDirectory
- Level 2: Choosing this option user can access all level 1 logs along with database logs.

PPT application generates the pptsupportDetails.tar archive containing detailed logs as per the selected level. This tar archive contains certain log files, PPT and PsMon configuration files as well as output of some system commands.
pptsupportDetails.tar archive includes following log categories:

- PostgresSQL database log
- Apache web server log
- PPT server installation log

pptsupportDetails.tar archive also includes output of following system commands:

- netstat – an
- ifconfig –a
- df –k
- ipcs
- ps-eaf
- env
- "prstat 1 1" (SunOS) / "top -d 1 -n 1 -b" (Linux)
- "cat /etc/release" (SunOS) / "cat /etc/redhat-release" (Linux)
- /opt/VRTSvcs/bin/hares -state
- /opt/VRTSvcs/bin/hagrp -state

IMPORTANT:

For more information on support details, refer section Get Support Details Script in chapter Administrative Scripts.

Audit Trail

This section describes an audit trail of user activities in the PPT application.
Audit trail allows you to generate a trail of user activity in the PPT application. Depending upon the business model and assigned privileges, a user can perform following type of activities using PPT application:

- Accessing PPT application by logging in to the PPT server.
- Setting up IPCF and SSC instances in PPT application for communicating with IPCF and SSC deployments.
- Administering users.
- Accessing debug information and audit trail.
- Configuring user defined actions and conditions.
- Configuring rules, profiles and policies.
- Configuring subscription tiers and notification templates.
- Executing various PPT scripts and services.
- Accessing profile attributes QoS profiles and traffic types.

You can generate a time based, operation specific audit trail of activities performed by any user. This audit trail can be generated using following parameters as filters:

- User Id: Filters activities performed by user ids. You can list activities performed by all the users by selecting value Any for this parameter.
- Operation Type: Filters activities performed by the category or type of operations permissible in PPT application. You can list activities performed by all operation categories, irrespective of user’s privilege by selecting value Any for this parameter. Depending upon your business model following operation categories are available - login, logout, user administration, IPCF and SSC setup, change password, session, traffic types, configuration of rules, policy, subscription tiers, user defined conditions and actions.
- Log Severity: Filters activities by severity of logs associated with the activities. You can list all the activities that are logged, by selecting value Any for this parameter. The log severity is categorized as debug, information, warning, error and critical.
- To: Filters activities by upper limit or end of date and time stamp associated with the activities. Format of date and time stamp is DD/MM/YYYY HH:MM.
- From: Filters activities by lower limit or the beginning of the date and time stamp associated with the activities. Format of date and time stamp associated with the activities is DD/MM/YYYY HH:MM.

IMPORTANT:

You can access the record of activities from a particular date up to the last available record in the database, by keeping the To field blank and entering a particular date in From field. Alternately, you can access the record of all activities from the beginning up to a particular date, by keeping From field blank and enter a particular date in To field. If both From and To fields are kept blank then all records in the database are fetched.
An audit trail displays following information:

- User Id: Name of the user who has performed this activity.
- Operation Type: The category of the activity that was performed.
- Time stamp: Date and time when this activity was performed.
- Log: Brief description of the activity.

Objects and Notifications

This section lists SNMP objects and notifications generated by the PPT application.

Simple Network Management Protocol (SNMP) objects and notifications provide information about the network status to system administrators. Alarms can also be used for troubleshooting the issues. Objects or alarms mostly indicate status of various PPT server or client component such as web server or database. SNMP objects are used to manage and monitor the PPT services in the PCC deployment.

Following is the list of supported objects and notifications:
Table 1. Objects

Objects | Description
--- | ---
cPPTNotifTimeStamp | This object indicates the time when the notification was generated.
cPPTBackupDirPath | This object indicates the backup directory path where backup operation has failed.
cPPTAvailBackupDiskSpace | This object indicates the available space on backup disk.
cPPTIpcfName | This object indicates the name of IPCF.
cPPTIpcfAddressType | This object indicates the address type of cPPTIpcfAddress object.
cPPTIpcfAddress | This object indicates the IP address of IPCF. The type of this address is determined by the value of cPPTIpcfAddressType object.
cPPTIpcfUnmanageableCause | This object indicates the reason for IPCF being unmanageable in PPT.
cPPTSscName | The object indicates the name of SSC.
cPPTSscAddressType | This object indicates the address type of cPPTSscAddress object.
cPPTSscAddress | This object indicates the IP address of SSC. The type of this address is determined by the value of cPPTSscAddressType object.
cPPTSscUnmanageableCause | This object indicates the reason for SSC being unmanageable in PPT.
cPPTEnableNotif | This variable specifies whether the system produces the notifications. A 'false' value will prevent these notifications from being generated.
cPPTSynchronizationFailureCause | This object indicates the reason for failure of synchronization operation.
cPPTPcefName | This object indicates the name of PCEF.
cPPTPcefAddressType | This object indicates the address type of cPPTPcefAddress object.
cPPTPcefAddress | This object indicates the IP address of PCEF. The type of this address is determined by the value of cPPTPcefAddressType object.
cPPTPcefUnmanageableCause | This object indicates the reason for PCEF being unmanageable in PPT.
cPPTPreviousHostname | This object indicates the host name of cluster node on which PPT was running before cluster failover event occurred.
cPPTCurrentHostname | This object indicates the host name of cluster node on which PPT is running after cluster failover event occurred.

Table 2. Notifications

Notifications | Description
--- | ---
cPPTWebserverStartNotif | This notification is generated when Webserver process is started. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTWebserverStopNotif | This notification is generated when Webserver process is stopped. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTWebserverRestartedNotif | This notification is generated when Webserver process is restarted. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTDatabaseStartNotif | This notification is generated when Database process is started. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTDatabaseStopNotif | This notification is generated when Database process is stopped. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTDatabaseRestartedNotif | This notification is generated when Database process is restarted. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTPSMonStartNotif | This notification is generated when Process Monitoring process is started. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTPSMonStopNotif | This notification is generated when Process Monitoring process is stopped. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTPSMonRestartedNotif | This notification is generated when Process Monitoring process is restarted. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTCriticalConditionNotif | This notification is generated when Database process is down due to critical error condition and cannot be restarted by Process Monitoring process. No new logins will work, existing logins will be invalidated. Database process needs to be restarted manually to resume normal working of PPT. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTDBBackupDestinationNotAccessibleNotif | This notification is generated when PPT backup operation has failed. The reason for failure is that the destination directory is not accessible. Value of object cPPTBackupDirPath indicates the destination directory which is inaccessible via PPT. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTDBBackupNotEnoughDiskSpaceNotif | This notification is generated when PPT backup operation has failed. The reason for failure is that the destination directory is not accessible. Value of object cPPTBackupDirPath indicates the destination directory which is inaccessible via PPT. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTMonitorServerStartNotif | This notification is generated when Monitor Server process is started. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTMonitorServerStopNotif | This notification is generated when Monitor Server process is stopped. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTMonitorServerRestartedNotif | This notification is generated when Monitor Server process is restarted. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTIpcfUnmanageableNotif | This notification is generated by Monitor Server when IPCF state changes from manageable to unmanageable. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTIpcfName object indicates the name of IPCF which is unmanageable via PPT. Value of cPPTIpcfAddrType object indicates the type of IP address contained in cPPTIpcfAddr object. Value of cPPTIpcfAddr object indicates the IP address of IPCF which is unmanageable via PPT. Value of cPPTIpcfUnmanageableCause object indicates the reason for IPCF to be unmanageable via PPT.
cPPTIpcfManageableNotif | This notification is generated by Monitor Server when IPCF state changes from unmanageable to manageable. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTIpcfName object indicates the name of IPCF which is manageable via PPT. Value of cPPTIpcfAddrType object indicates the type of IP address contained in cPPTIpcfAddr object. Value of cPPTIpcfAddr object indicates the IP address of IPCF which is manageable via PPT.
cPPTSscUnmanageableNotif | This notification is generated by Monitor Server when SSC state changes from manageable to unmanageable. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTSscName object indicates the name of SSC which is unmanageable via PPT. Value of cPPTSscAddrType object indicates the type of IP address contained in cPPTSscAddr object. Value of cPPTSscAddr object indicates the IP address of SSC which is unmanageable via PPT. Value of cPPTSscUnmanageableCause object indicates the reason for SSC to be unmanageable via PPT.
cPPTSscManageableNotif | This notification is generated by Monitor Server when SSC state changes from unmanageable to manageable. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTSscName object indicates the name of SSC which is manageable via PPT. Value of cPPTSscAddrType object indicates the type of IP address contained in cPPTSscAddr object. Value of cPPTSscAddr object indicates the IP address of SSC which is manageable via PPT.
cPPTSchedulerStartNotif | This notification is generated when Scheduler process is started. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTSchedulerStopNotif | This notification is generated when Scheduler process is stopped. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTSchedulerRestartedNotif | This notification is generated when Scheduler process is restarted. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time.
cPPTSynchronizationFailedOnIpcfNotif | This notification is generated by synchronization server when synchronization operation fails on manageable IPCF. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTIpcfName object indicates the name of IPCF on which synchronization operation has failed. Value of cPPTIpcfAddrType object indicates the type of IP address contained in cPPTIpcfAddr object. Value of cPPTIpcfAddr object indicates the IP address of IPCF on which synchronization operation has failed. Value of cPPTSynchronizationFailureCause object indicates the reason for failure of synchronization operation.
cPPPTSynchronizationFailedOnSscNotif | This notification is generated by synchronization server when synchronization operation fails on manageable SSC. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTSscName object indicates the name of SSC on which synchronization operation has failed. Value of cPPTSscAddrType object indicates the type of IP address contained in cPPTSscAddr object. Value of cPPTSscAddr object indicates the IP address of SSC on which synchronization operation has failed. Value of cPPTSynchronizationFailureCause object indicates the reason for failure of synchronization operation.
cPPTSynchronizationFailedNotif | This notification is generated by synchronization server when synchronization operation fails due to some internal error in PPT. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTSynchronizationFailureCause object indicates the reason for failure of synchronization operation.
cPPTPcefUnmanageableNotif | This notification is generated by Monitor Server when PCEF state changes from manageable to unmanageable. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTPcefName object indicates the name of PCEF which is unmanageable via PPT. Value of cPPTPcefAddrType object indicates the type of IP address contained in cPPTPcefAddr object. Value of cPPTPcefAddr object indicates the IP address of PCEF which is unmanageable via PPT. Value of cPPTPcefUnmanageableCause object indicates the reason for PCEF to be unmanageable via PPT.
cPPTPcefManageableNotif | This notification is generated by Monitor Server when PCEF state changes from unmanageable to manageable. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTPcefName object indicates the name of PCEF which is manageable via PPT. Value of cPPTPcefAddrType object indicates the type of IP address contained in cPPTPcefAddr object. Value of cPPTPcefAddr object indicates the IP address of PCEF which is manageable via PPT.
cPPTSynchronizationFailedOnPcefNotif | This notification is generated by synchronization server when synchronization operation fails on manageable PCEF. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTPcefName object indicates the name of PCEF on which synchronization operation has failed. Value of cPPTPcefAddrType object indicates the type of IP address contained in cPPTPcefAddr object. Value of cPPTPcefAddr object indicates the IP address of PCEF on which synchronization operation has failed. Value of cPPTSynchronizationFailureCause object indicates the reason for failure of synchronization operation on PCEF.
cPPTClusterFailoverNotif | This notification is generated when cluster failover event occurs. Value of cPPTNotifTimeStamp object indicates the time when this notification was generated. This will be system's current time. Value of cPPTPreviousHostName object indicates the host name of cluster node on which PPT was running before cluster failover event occurred. Value of cPPTCurrentHostName object indicates the host name of cluster node on which PPT is running after cluster failover event occurred.
cPPTMIBCompliance | The compliance statements for entities which implement the CISCO PPT MIB.
cPPTNotifMgmtGroup | A collection of objects related to notification management on PPT.
cPPTNotifGroup | A collection of notifications which indicate change in the state of PPT processes and change in the state of IPCF and SSC managed by PPT.
cPPTEnableNotifGroup | The collection of objects which are used to enable a group of notifications.

IMPORTANT:

For more information on PPT objects and notifications, please refer the IPCF PPT Application MIB chapter of the Cisco ASR5000 Series SNMP MIB Reference guide.