| Oracle® Communications Service Broker VPN Implementation Guide Release 6.0 Part Number E23531-02 |
|
|
View PDF |
| Oracle® Communications Service Broker VPN Implementation Guide Release 6.0 Part Number E23531-02 |
|
|
View PDF |
This chapter explains the monitoring features of the Oracle Communications Service Broker VPN. It describes how to capture and view statistics generated by activities of the VPN application.
Service Broker VPN generates and collects information you can use to monitor VPN activities. The information include counter-based statistics, such as the number of calls originated by VPN users, the number of calls received by VPN users, and the number of calls to partner organizations.
In addition to counter-based statistics, the VPN application generates audit information in the form of the calls per second (CPS) log. The CPS serves as the charging basis for the VPN application.
Every 24 hours, the VPN application calculates the busy hour CPS value. This value represents the average number of successful calls per second during the busiest hour of the previous 24-hour period. It is derived by determining the busiest hour in the period, and then dividing the total call count by 3600.
The VPN application can generate SNMP trap notifications based on the CPS value. If the CPS threshold you configure is exceeded, the VPN application sends a trap to the monitoring agent.
You configure the CPS threshold and other settings that control how the VPN application performs monitoring-related tasks by using JMX-based configuration MBeans. To access configuration MBeans, connect to the Administration Console runtime process from a JMX browser.
Runtime statistics are available by connecting to the Processing Server process and invoking MBean operations to retrieve runtime statistics.
Note:
For more information about connecting to the Service Broker processes from a JMX client, see Oracle Communications Service Broker System Administrator's Guide.Runtime information reflects the current statistics for the specific managed server you access. By default, every 5 minutes the VPN application collects the runtime information from all managed servers in the cluster and aggregates it in the statistics database.
The database preserves the data for a period of one year by default, enabling you to access the historical records of VPN application activities.
The VPN application stores historical monitoring data in a database you configure for the purpose. The statistics information is stored in three tables:
stats_collect_info: Stores the most recently collected statistical data. The collection time value in this table indicates when the data was collected.
stats_history: Stores historical statistic data. The service writes to this table every 5 minutes by default. The information includes the CPS count, the calls per second count that is used for the busy hour CPS value.
stats_audit: Stores the busy hour CPS value for each day.
See "Configuring Data Persistence" for information about connecting and configuring the external database used to store monitoring data.
You can configure how the VPN application performs monitoring related tasks by using the statConfig configuration MBean. The MBean interface is available by accessing the Administration Server process from a JMX client.
There are two MBeans relevant to statistics: one is common to both VPN and SVC and the other contains the attribute specific for VPN.
The object name of the common statConfig MBean is:
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.apps.common.statistic,version=1.1.0.0,name0=statConfig
The statConfig MBean has the following attributes:
archivePeriod: The time span, in days, for which statistics are kept in data storage. This default value is 365. Statistics older than 365 days are purged from the database.
busyHourAverageCPSCheckTimeHour: The daily hour at which the VPN application performs the CPS calculation. Can be from 0 to 24. By default, the calculation occurs at 2:00 AM.
busyHourAverageCPSCheckTimeMinute: The daily minute at which the VPN application performs the CPS calculation. Together with the hour, this value determines the time of day the calculation occurs. Can be from 0 to 60. By default, the calculation occurs at 2:00 AM.
collectionDelay: The collection delay, in seconds, between synchronizations of the VPN application statistics with the underlying Service Broker framework statistics. This ensures that data in memory awaiting collection by the platform data collection process is not lost. This value should match the collectionPeriod attribute in the oracle.axia.logging.stats.statisticsConfig.collectionPeriod MBean. Note that collectionDelay is in seconds (60, by default), whereas collectionPeriod is in minutes (1, by default).
collectionInterval: How often, in minutes, the VPN application collects statistics from the managed servers in the cluster. The default is 5 minutes. The minimum value is 1. Collecting VPN statistics from managed servers complements the collection process performed by the underlying Service Broker framework by aggregating VPN application statistics from multiple managed services.
The object name of the VPN-specific statConfig MBean is:
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.apps.vpn.vpnconfiguration,version=1.1.0.0,name0=vpnConfig,name1=statConfig
This statConfig MBean contains the busyHourAverageCPSThreshold attribute. This attribute specifies the CPS value that, if exceeded, causes the VPN application to generate an SNMP trap notification. See "Configuring CPS Threshold SNMP Traps" for more information.
You can view runtime monitoring data by using operations in runtime MBeans exposed by the managed server process.
The runtime values represent the statistics of that particular managed server. They do not represent cluster-wide statistics, which are stored in the VPN application statistics database.
You can use operations in VPNRuntimeStatisticsMBean to view runtime statistics for the VPN application.
The object name of the runtime statistics MBean is:
oracle:type=oracle.axia.apps.vpn.statistic.mangement.VPNRuntimeStatisticsMBeanoracle.axia.apps.vpn.statistic.management.
Table 5-1 lists the operations that return runtime statistics.
Table 5-1 VPN Runtime Statistics MBean Operations
| Operation | Description |
|---|---|
|
retrieveTotalCallCount |
Total number of incoming and outgoing calls attempted. |
|
retrieveSuccessfulCallCounts |
Number of successful calls established. |
|
retrieveTotalOriginatingCallCounts |
Total number of call attempts that were originated by VPN users. |
|
retrieveSuccessfulOriginatingCallCounts |
Number of successful calls originated by VPN users. |
|
retrieveTotalTerminatingCallCounts |
Total number of incoming calls attempted to VPN users. |
|
retrieveSuccessfulTerminatingCallCounts |
Number of successful calls made to VPN users. |
|
retrieveTotalIntraVPNCallCounts |
Total number of call attempts between users of VPN subscriber organizations. |
|
retrieveSuccessfulIntraVPNCallCounts |
Number of successful calls between users of VPN subscriber organizations. |
|
retrieveTotalPartnerVPNCallCounts |
Total call attempts from VPN users to partner VPN users. |
The audit log provides a historical view of the CPS rate for the cluster. It shows the CPS rate for each 24-hour period in the time span you specify.
You can access the audit log using the following runtime MBean:
oracle:type=oracle.axia.apps.vpn.statistic.mangement.VPNCPSAuditLogMBean
To view the log, connect to the managed server process and invoke the genCPSAuditLog operation in the VPNCPSAuditLogMBean MBean.
As parameters to the operation, pass the name for the audit log file and the time range of the records to report. The operation creates the audit log file with the name you specify in this location:
oracle_home/ocsb60/managed_server/filename
To specify the time range, indicate the start and end date of the range using the format "yyyy-mm-dd", for example, 2011-05-01.
The following example illustrates the format of the audit log file:
<calls_limit_log>
<start>2011-04-01<start>
<end>2011-06-01</end>
<log_entry group="VPN" start="2011-04-23 16:00" end="2011-04-23 17:00"
cps="0.05" limit="-1" exceeded="false"/>
<log_entry group="VPN" start="2011-04-24 16:00" end="2011-04-24 17:00"
cps="0.07" limit="-1" exceeded="false"/>
<checksum>1a909c2b3420850e1e16c6b51f32dfcb</checksum>
</calls_limit_log>
In the log, each audit log item is represented by a log_entry element. The element represents the audit information for a given time period. It contains the following attributes:
group: Indicates the Service Broker application for which this log entry was created, either VPN or Social Voice Communicator (SVC).
start: The start date and hour of the time span represented by the log entry.
end: The end date and hour of the time span represented by the log entry.
cps: The busy hour calls per second for the time period.
limit: Not currently used. Always set to -1.
exceeded: Not currently used. Always set to false.
You can use the reset operation to clear the current the statistics count for a managed server. This resets the StatsBeginTime value to the current time.
The operation is in the following runtime MBean:
oracle:type=oracle.axia.apps.vpn.statistic.mangement.VPNRuntimeStatisticsMBean
You can configure a CPS threshold that, if exceeded, causes the VPN application to generate an SNMP trap. The SNMP monitoring capabilities of the VPN application rely on the Service Broker application framework.
To use traps, you must enable the SNMP agent and configure the trap destination in the configuration MBean:
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.snmp, version=1.0.0.1,name0=SnmpConfig
For more information about setting up SNMP and JMX monitoring for Service Broker, see the discussion on monitoring Service Broker in Oracle Communications Service Broker Administrator's Guide.
By default, the CPS threshold is 100 calls per second. To modify the threshold, set the new threshold value in the busyHourAverageCPSThreshold attribute in the following MBean:
oracle:type=oracle.axia.cm.ConfigurationMBean,name=oracle.axia.apps.vpn.vpnconfiguration,version=1.0.0.SNAPSHOT,name0=vpnConfig,name1=statConfig, name2=busyHourAverageCPSThreshold
If triggered, the trap indicates when the log was created and the triggering CPS value. The trap OID for the CPS audit log trap is:
iso.org.dod.internet.pricate.enterprises.oracle.sdp.notificationGroup. defaultNotification genCPSAuditLog
|
 Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|