Guest

Cisco Resource Policy Management System

Cisco Resource Policy Management System 2.0.2 Release Notes

  • Viewing Options

  • PDF (223.5 KB)
  • Feedback
Release Notes for Cisco Resource Policy Management System Release 2.0.2

Table Of Contents

Release Notes for Cisco Resource Policy Management System Release 2.0.2

Cisco RPMS Release 2.0.2 Summary

What's New

UG/NAS Host Name Configuration

Cisco RPMS Restart Scenarios for UG/NAS Host Name configuration

Adding new entry in /etc/hosts:

Changing Name of an existing mapping in /etc/hosts:

Changing IP address of an existing mapping in /etc/hosts:

Duplicate Trunk Configuration

Per Customer AAA List

Format-E support for AAA transaction

Important Notes

System Requirements

Hardware Requirements

Disk Space Requirements

Database Requirements

Installing Cisco RPMS 2.0.2

Upgrading to Cisco RPMS Release 2.0.2 from Previous Releases

Cisco IOS Release Requirements for Cisco RPMS 2.0.2

Uninstalling Cisco RPMS

Caveats

Resolved Caveats—Cisco RPMS Release 2.0.2

Caveats for Cisco RPMS Release 2.0.2

Troubleshooting

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Assistance Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


Release Notes for Cisco Resource Policy Management System Release 2.0.2


These release notes describe important information and caveats for the Cisco Resource Policy Management System (Cisco RPMS) Release 2.0.2.

You can obtain the most current Cisco RPMS 2.0.2 documentation from the following link on the Cisco Connection Online (CCO) Web site:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_202/index.htm

The following topics are discussed in these release notes:

Cisco RPMS Release 2.0.2 Summary

What's New

System Requirements

Installing Cisco RPMS 2.0.2

Caveats

Troubleshooting

Obtaining Documentation

Obtaining Technical Assistance

Cisco RPMS Release 2.0.2 Summary

Cisco RPMS Release 2.0.2 is an enhancement to Cisco RPMS Release 2.0.1. It introduces three new features and resolves a number of DDTSs:

Universal Gateway /NAS Host Name configuration

Per Customer AAA List

Format-E support for AAA Transaction.

What's New

UG/NAS Host Name Configuration

Cisco RPMS Release 2.0.2 reintroduces the Universal Gateway (UG) Host Name configuration feature that was previously available in Cisco RPMS 1.x and was not in Cisco RPMS 2.0/2.0.1 in a refined manner. You can now configure the UG using Hostname or IP Addresses. Note that Cisco RPMS will not allow configuring invalid or unresolvable Hostname/IP Addresses.

Cisco RPMS Restart Scenarios for UG/NAS Host Name configuration

Adding new entry in /etc/hosts:

If you add new entries in /etc/hosts, you do not need to restart RPMS.

Add the new entry first in the /etc/hosts and configure it in RPMS.

Changing Name of an existing mapping in /etc/hosts:

If you change a name of the existing mappings in /etc/hosts, you do not need to restart RPMS.

Add the name to be changed first in /etc/hosts and configure it in RPMS.

Changing IP address of an existing mapping in /etc/hosts:

If you change an IP address of the existing mappings in /etc/hosts, you must restart RPMS.


Note Since JVM internally has a cache that has IP address -->Host Name mapping. This cache is not updated when the change is made in /etc/hosts to an existing mapping. So you must restart RPMS to reflect the change.


Duplicate Trunk Configuration

A Trunk with UG Name/slot/port & IP Address of the same UG/ slot/port is allowed.When duplicate Trunks are configured using IP Address and UG Name, only the Trunks configured with IP Address will be considered for customer profile matching.

Duplicate UG Name/slot/port is prevented. (UG Name with a difference in Case is considered as a duplicate.)


Note If you are upgrading from Cisco RPMS 1.x/2.x, the valid Host names are transferred to Cisco RPMS 2.0.2.

If you are using a DNS server for UG names, ensure that the reverse zone is configured in the DNS server.


Per Customer AAA List

Cisco RPMS Release 2.0.2 release introduces a new AAA List feature to load balance AAA servers. Cisco RPMS 2.0.2 allows separate AAA lists for various retail customers, instead of one global AAA list. Each of these lists is called an AAA Group. There will be an active AAA server for each group. Thus, there could be a separate active AAA server for each customer.


Note If you are upgrading from Cisco RPMS 1.x, configure an AAA List using the GUI/CLI in Cisco RPMS 2.0.2.

If you are upgrading from Cisco RPMS 2.0/2.0.1, existing customer names and AAA List in Cisco RPMS 2.0/2.0.1 are transferred to Cisco RPMS 2.0.2 and stored in the default AAA group list.


Format-E support for AAA transaction

Format-E standard for AAA transaction has been added to support the AS5850 STM-1 card with 63 E1 controllers.


Note In Format-E support, the format-E specifier configuration should contain lower case letters s, p, and c only. This is because RPMS, by default, assumes that NAS is sending ds0 slot, port, and channel. Because the lower case letters s, p, and c correspond to ds0 slot, port and channel, only these letters can be used for a Format-E configuration in RPMS and in Cisco IOS.


Important Notes

For making CAS calls, enter the following commands in the Universal gateway configuration.

router(config)# aaa nas port extended 
router(config)# radius-server vsa send accounting
router(config)# radius-server vsa send authentication

System Requirements

This section describes the hardware, memory, and database requirements required to install Cisco RPMS.

Hardware Requirements

The hardware requirements for Cisco RPMS are dependent on the expected call volume and the number of simultaneous active calls in your network. Cisco RPMS components are built to run on Solaris. For Solaris patch requirements, refer to the Cisco RPMS 2.0 Release Notes at:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/rpms/rpms_2-0/rn2_0.htm.

Disk Space Requirements

The minimum free disk space required to install Cisco RPMS is 250 MB. A minimum of 800 MB free disk space is required for installing Cisco RPMS and the Oracle database on the same machine. Additional disk space requirements depend on factors such as generation of call detail records (CDRs) and log files.

Upgrading from a previous version of Cisco RPMS may require additional disk space for data backup. For more information, refer to Chapter 3, "Upgrading to Cisco RPMS Release 2.0.2 from Previous Releases" of the Cisco Resource Policy Management System 2.0.2 Installation Guide.

Database Requirements

You must have an Oracle database running with remote access by using SQL net. For further details, refer to the Cisco RPMS 2.0 documentation.

Installing Cisco RPMS 2.0.2

Execute installcrpms.sh to install Cisco RPMS Release 2.0.2 by using the GUI.


Step 1 Place the crpms-v2.0.2 file into the crpms-home directory.

Step 2 Untar the file by using the command:

tar xvfo crpms-v2.0.2.tar 

Note The o option is important.


Step 3 Start the Cisco RPMS installation by executing install.sh.


Step 4 Start Cisco RPMS by using the command:

crpms-home/sbin/crpms start

Step 5 To stop Cisco RPMS, use this command:

crpms-home/sbin/crpms stop


For detailed steps on installation, see the Cisco Resource Policy Management System 2.0.2 Installation Guide.


Note For Console mode installation, you need a proper DISPLAY setting. The DISPLAY setting should refer a valid XServer.


Upgrading to Cisco RPMS Release 2.0.2 from Previous Releases

If upgrading from a previous release of Cisco RPMS and you wish to preserve the configuration data stored in the Oracle RDBMS, choose No when asked "Is this a new RPMS Installation?"

For information on upgrading to Cisco RPMS Release 2.0.2 from previous releases, see the Cisco Resource Policy Management System 2.0.2 Installation Guide.

Cisco IOS Release Requirements for Cisco RPMS 2.0.2

You must use a Cisco IOS release that supports preauthentication functionality. For Cisco IOS release requirements, the Cisco RPMS team recommends the following Cisco IOS releases:

Cisco AS5300, Cisco AS5400, Cisco AS5800, Cisco AS5850: Cisco IOS Release 12.3(3)

Cisco AS5850 with eRSC: Cisco IOS Release 12.3(2)T2


Note Cisco IOS Release 12.3(2)T is only recommended for sites using the eRSC.


Uninstalling Cisco RPMS

For more information on uninstalling Cisco RPMS Release 2.0.2, refer to Chapter 2, "Installing Cisco Resource Policy Management System" of the Cisco Resource Policy Management System 2.0.2 Installation Guide.

Caveats

Resolved Caveats—Cisco RPMS Release 2.0.2

The problems listed in Table 1 are resolved or closed in Cisco RPMS Release 2.0.2.

Table 1 Resolved Issues in Cisco RPMS Release 2.0.2

DDTS Number
Status
Description

CSCdy08131

Resolved

User may bypass aaa authen with Cisco RPMS.

CSCin46055

Resolved

CDR Terminate cause field always has value RPMS.


Caveats for Cisco RPMS Release 2.0.2

The Cisco RPMS and Cisco IOS issues that are still in Cisco RPMS Release 2.0.2 are shown in Table 2.

Table 2 Open Cisco RPMS Release 2.0.2 Issues 

DDTS Number
Cisco RPMS Issue
Caveat
Workaround

CSCec30014

Active call report shows calls even after all the calls are cleared.

When NAS secret configured in the Cisco RPMS does not match with that of NAS, calls will be active in Cisco RPMS but NAS will drop these calls.

This will lead to "Customer profile count limit reached" rejection or the call will be replaced with reason "Another call on same NAS-port".

Shared secret key configured in NAS and Cisco RPMS should be same.

CSCin43953

VPDN IP Endpoint Counter Button shows Server Not Found (rarely)

When you press the counter button in the GUI, the following sequence of events occurs:

Client establishes a TCP connection with the server

Client sends an http request.

Server responds with redirect http response (containing URL of the page to be requested next).

Client sends FIN to close the connection together with the above http response.

In the correct scenario, the client responds to this FIN and terminates the current TCP connection. It then establishes a new TCP connection and sends the new http request with the URL received in the last http response.

In the faulty scenario, the client ignores the FIN and continues to send the new request on the current TCP connection. Because the server expects a response for the FIN, it does not send the page contents. Therefore, a problem exists because the client ignores (rarely) the FIN message.

The bug did not occur in the lab when the configuration was as follows: (i) Machine: Win2k, SP3 Browser: IE (5.5) Http: 1.1 (ii) Machine: Win2k, SP3 Browser: Netscape 6.2.3 Http:1.1.

Use the Refresh button on the browser.

or

Use the Back button on the RPMS page or browser to go to the previous page and click the counter button.

CSCin46189

UG Termination report has some percentage values >100%

A higher termination percentage indicates higher terminations in the particular sampling interval.

Termination% will be zero when there is no attempted call in that interval.

None.

CSCin57839

RPMS2.x upgrade fails due to non-default calltype in Cisco RPMS1.x.

Upgrade fails with SQL exception.

Before upgrade, delete non-default call types in Cisco RPMS 1.x and proceed with the upgrade.

CSCin62458

NAS fails to send ACCT_STOP when decryption fails.

When IOS (NAS) and Cisco RPMS (AAA Server) is configured with different radius-server key, IOS fails to decrypt the access-accept packets from Cisco RPMS and also fails to send ACCT-STOP message to Cisco RPMS. This leads to an active call count mis-match issue between NAS and Cisco RPMS.

Correct the radius-server key (secret key) configured in Cisco RPMS.


Troubleshooting

For information on troubleshooting Cisco RPMS Release 2.0.2, refer to the Cisco Resource Policy Management System 2.0.2 Troubleshooting Guide.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco Technical Assistance Website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco Technical Assistance Website

The Cisco Technical Assistance Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco Technical Assistance Website is available 24 hours a day, 365 days a year. The Cisco Technical Assistance Website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco Technical Assistance Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html