|
|
This chapter presents operations and maintenance tasks related to the Cisco ASAP Solution only, as provided by the application Cisco RPMS, Release 2.0. The main focus is on the Web-based form of the application. However, where CLI commands are applicable, the reader is referred to related commands. CLI commands can be run only on the host machine.
 |
Note This chapter does not apply to the Cisco SS7 Interconnect for Voice Gateways Solution and the Cisco PSTN Gateway Solution only supports RPMS using dial calls. |
Tips for troubleshooting Cisco RPMS are provided in "Troubleshooting the Cisco RPMS."
 |
Tip In some Cisco RPMS documents, "RPMS" may be indicated to stand for "Resource Pool Manager System." The applications are the same. |
|
Note The features of Cisco RPMS as they relate to the Cisco ASAP Solution are introduced in the Cisco ASAP Solution Overview and Planning Guide. |
This chapter presents the following major management topics:
|
Tip See also Task Summary. |
The Cisco RPMS application manages the following components of the Cisco ASAP Solution: Cisco AS5000 series.
For the following procedures, refer to Cisco Resource Policy Management System 2.0 documentation at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_2-0/index.htm
The following documents there are referenced:
|
Note For the Cisco RPMS CLI commands, refer to Appendix G, "Using the Command-Line Interface," of the Cisco Resource Policy Management System 2.0 Configuration Guide. |
Make sure that you are familiar with the above documents.
The tasks in this chapter are listed below, grouped by major category.
For information on configuring a Cisco RPMS wholesale dial solution, refer to the Cisco Resource Policy Management System 2.0 Wholesale Dial Addendum. For general information, refer to these topics:
Summary |
You can configure Cisco RPMS settings related to CDRs (Call Data Records), log files, active call times, and threshold settings. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure Cisco RPMS settings:
Step 2 Read Overview: Configuring Cisco RPMS Settings. As appropriate, select from among the following options and follow the directions for each option: Call Detail Record Logging and Miscellaneous.
Summary |
Cisco RPMS supports multiple administrators with different privilege levels. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To add administrators and select a privilege level:
Step 2 Read Overview: Configuring Administrators and Administrators' Privileges and follow the steps therein.
Step 3 Select privilege levels as appropriate.
Summary |
You can configure Cisco RPMS to send e-mail notifications when alerts occur. You can also enable alert logging. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure alert notifications or enable alert logging:
Step 2 Read Overview: Configuring Alert Notifications and follow the steps for each of the following tasks, as appropriate:
a. Configuring the Email Server and Sender Email Address
Summary |
Cisco Vendor Specific Attributes (VSAs) are sent in the preauthentication "accept" message from Cisco RPMS to direct the UG how to handle the call. Cisco RPMS provides a Web-based interface to (1) define a vendor (specific RADIUS application type), and (2) administer and associate any VSA with a customer-based call-accept message. This increases control over resources and service management for each call. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure a RADIUS vendor and VSAs:
Step 2 Read Overview: Configuring RADIUS Vendors and follow the steps for each of the following tasks, as appropriate:
d. Editing a Vendor Specific Attribute
e. Deleting a Vendor Specific Attribute
f. Associating a Vendor Specific Attribute to a Customer Profile
Summary |
Cisco RPMS and UGs communicate by using the RADIUS protocol. You can create a list of UGs that communicate with Cisco RPMS. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To add UGs that communicate with Cisco RPMS:
Step 2 Read Overview: Communicating with Universal Gateways and follow the steps to add a UG.
Summary |
The UG can be provisioned to communicate with a list of AAA RADIUS servers. The use of proxy servers for redundancy provides fault tolerance in case one server is unreachable—the UG can redirect traffic to another RADIUS server in the list. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure AAA servers or AAA proxy servers:
Step 2 Read Overview: AAA Servers and follow the steps therein.
Summary |
Cisco RPMS includes an SNMP agent to monitor Cisco RPMS state information. The Cisco RPMS state information includes attributes such as system up time, customer profiles, and VPDN group information and statistics. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
Step 2 Read Overview: SNMP Management and follow the steps therein.
Summary |
Cisco RPMS uses two types of counters that can be reset: system counters and informational counters. System counters help manage and maintain session counts on the UGs, directly affecting port management decisions and thresholds. Informational counters increment until they are reset. These maintain information on rejected sessions, rejected VPDN sessions, and sessions that were rejected because of insufficient resources. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To reset system or informational counters:
Step 2 Read Overview: Counters and reset system or informational counters, as appropriate.
Summary |
Cisco RPMS can monitor the UG's state. If a UG fails to respond to an SNMP Get message or cannot be reached by means of ICMP, Cisco RPMS resets the corresponding active calls. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
Step 2 Read Overview: The Universal Gateway Heartbeat and follow the steps therein.
Summary |
There are a variety of options for configuring administration tasks in Cisco RPMS. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure Cisco RPMS administration tasks:
Step 2 Read Overview: Cisco RPMS Administration Tasks and configure the appropriate tasks.
Summary |
A DNIS group is a configured list of DNIS numbers corresponding to the numbers dialed by particular customers, service offerings, or both. Cisco RPMS checks the DNIS number of inbound calls against the configured DNIS groups or the default DNIS group. If a match is found, the configured information in the customer profile to which the DNIS group is assigned is used. If a match is not found, the default DNIS group and default customer profile are used. If a default customer profile is not configured, the call is rejected. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure a DNIS group, complete the following tasks:
Step 2 Read Overview: Configuring DNIS Groups and follow the steps therein.
Summary |
Trunk groups contain a list of trunks that belong to a customer. Both trunks and trunk groups allow Cisco RPMS users to manage multiple calls from different areas, by using more than one customer profile. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure trunk groups, complete the following tasks:
Step 2 Read Overview: Configuring Trunk Groups and follow the steps therein.
Summary |
Customer profiles use call types to identify which default customer profile to use for an incoming call. For DNIS groups, when multiple default customer profiles are used, the call type of the DNIS group identifies which default customer profile to use for an incoming call. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To read about call types, complete the following tasks:
Step 2 Read Overview: Call Types.
Summary |
A customer profile is a set of parameters created for a specific service provider customer. The parameters are configured by the Cisco RPMS administrator and are based on the DNIS and call types. You can assign configured DNIS groups, trunk groups, and IP groups to customer profiles. The customer profiles are selected by matching the incoming call characteristics (DNIS, call type, trunk) with the combinations of the entries within these associated groups. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure a customer profile, complete the following tasks:
Step 2 Read Overview: Configuring Customer Profiles and follow the steps therein.
Summary |
Call discrimination uses DNIS groups to prevent specific call types from accessing resources on the UGs. For example, if a customer signs up for modem access, you can prevent that customer from accessing the UG through ISDN by creating a table entry that prevents digital access for the customer's DNIS group. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure call discrimination, complete the following tasks:
Step 2 Read Overview: Configuring Call Discrimination and follow the steps therein.
Summary |
If the UG is configured for VPDN service, it sends a request to Cisco RPMS for VPDN information after answering a call. Cisco RPMS determines whether to authenticate the call with a home gateway through a VPDN tunnel based on the type of VPDN services configured in Cisco RPMS. Cisco RPMS supports the following types of VPDN services: |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure VPDN services, follow the steps in one or more of the following sections as appropriate:
Step 2 Read Overview: Configuring VPDN Services.
Step 3 If configuring DNIS-based VPDN, read Overview: DNIS-Based VPDN.
Step 4 If configuring domain name-based VPDN, read Overview: Domain Name-Based VPDN.
Step 5 If configuring VPDN request forwarding, read Overview: VPDN Request Forwarding to External AAA Server.
Summary |
With Cisco RPMS, you can control overflow access through shared overflow pools. To create an overflow pool, you must give it a name, and then associate one or more trunk groups to it. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To create an overflow pool, complete the following tasks:
Step 2 Read Overview: Configuring Overflow Pools.
Summary |
Cisco RPMS allows you to build fault tolerance and resiliency into your dial service offerings. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure Cisco RPMS fault tolerance:
Step 2 Read Overview: Configuring Cisco RPMS Fault Tolerance.
Step 3 As appropriate, follow the steps in one or more of the following sections:
Summary |
To enhance fault tolerance in case of a server failure, configure Cisco RPMS servers as hot standby pairs. The pairs communicate with each other and constantly share information. By remaining in synchronization, both servers in a hot standby pair always have identical active call counts and other network state information. You can also configure Cisco RPMS proxies, to use one server as an active server and the other as a standby server. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure fault tolerance in Cisco RPMS servers, complete the following tasks:
Step 2 Read the Overview: Tolerance to Cisco RPMS Server Failure.
Step 3 As appropriate, follow the steps in one or more of the following sections:
a. Configuring a Hot Standby Pair
b. Configuring the Cisco RPMS Proxy for Failover to the Standby Server
Summary |
To enhance fault tolerance in case of an AAA server failure, Cisco RPMS allows you to create a prioritized list of AAA servers. Cisco RPMS proxies use this list to determine the destination of authorization and accounting messages received from the UG. The proxies forward messages to the AAA server with the highest priority. If they detect that this AAA server has failed, they switch over to the server with the next highest priority. |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To configure tolerance to AAA server failure:
Step 2 Read Overview: Tolerance to AAA Server Failure and follow the steps therein.
Summary |
Cisco RPMS reports data for network dial service analysis and troubleshooting. Various types of reports can be generated for different purposes. |
Target Platform(s) |
|
Application |
See Introduction. |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To view or edit Cisco RPMS reports:
Step 2 Read Overview: Report Types.
Summary |
|
Target Platform(s) |
|
Application |
See Introduction. |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
To generate various Cisco RPMS reports:
Step 2 Read Overview: Report Types and select the appropriate report types.
Summary |
Accounting allows you to specify where Cisco RPMS forwards messages, and to generate Call Detail Records (CDRs). |
Target Platform(s) |
|
Application |
See Introduction |
Frequency |
Cisco Resource Policy Management System 2.0 Configuration Guide
For all related documents, see References.
Step 2 Read Overview: Accounting and follow the steps therein.
Posted: Wed Jan 22 02:03:05 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.