|
|
These release notes describe important information and caveats for the Cisco Resource Pool Manager Server (Cisco RPMS) Release 1.1. Information in this document supplements information in the Cisco RPMS 1.1 documentation set.
The Cisco RPMS 1.1 documentation set includes the following books: the Cisco Resource Pool Manager Server 1.1 Installation Guide, the Cisco Resource Pool Manager Server 1.1 Configuration Guide, and the Cisco Resource Pool Manager Server 1.1 Solutions Guide.
The documentation set is included as Adobe Acrobat PDF files on the Cisco RPMS 1.1 software CD-ROM in the following directory:
They require the Adobe Acrobat Reader to view them. (To download the Reader, go to the Adobe Web site at http://www.adobe.com). The files included are:
Installation Guide: rpmsinst.pdf
You can also obtain the most current Cisco RPMS 1.1 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_1-1/index.htm
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The following topics are discussed:
Cisco RPMS 1.1 is an enhancement release to RPMS 1.0(4). New features in RPMS 1.1 include:
The following issues were found in Cisco RPMS 1.0(4), and have been resolved in Cisco RPMS 1.1.
This section describes information that was unavailable when the Cisco Resource Pool Manager Server Installation Guide was printed, possibly unexpected behavior, and known issues.
The following Solaris patches or later versions are required:
Table 1 Required Solaris patches
| Solaris 2.6 (5.6) | Solaris 7 (5.7) |
|---|---|
The installation of Cisco RPMS requires a JAVA virtual machine to be installed on the target Cisco RPMS host machine. The installation program will not complete successfully if using JVM 1.2.2 or higher.
If the following dialog appears while installing Cisco RPMS
and there is no application using port 49, remove this entry from /etc/services and continue with the installation.
If you click Browse while installing Cisco RPMS, the Browse dialog box fills the entire screen. To work around this problem, enter the path directly and do not click the Browse button.
This section describes limitations and restrictions of Cisco RPMS.
 |
Note A system-wide NAS audit degrades network performance for the duration of the audit. Performance may drop between 25%-50%. |
The NAS audit feature will not synchronize across different time zones. If your network spans across different time zones, Cisco recommends that you synchronize all servers across the network to one single time zone.
Configuring the NAS to use a single TACACS+ connection to Cisco RPMS will not work. This is because the TACACS+ server in the NAS looks for a bit to be set, determining whether the client is using a single connection to send packets. However, the NAS does not set the bit.
The Cisco RPMS server also expects the bit to be set. When it determines the single connection is not set, it closes the connection following the end of the packet.
Cisco RPMS cannot exist on the same system as CiscoSecure Access Control Server (ACS); however, Cisco RPMS and CiscoSecure ACS can share an Oracle server. For more information, see the Configuring Cisco RPMS and CiscoSecure ACS to Use the Same Oracle Server section.
If you plan to install Cisco RPMS on a system where CiscoSecure ACS was previously installed, see the Installing Cisco RPMS over a Previous CiscoSecure Installation section.
To configure Cisco RPMS and CiscoSecure ACS to use the same Oracle server:
Step 2 Create an Oracle user with a default tablespace equal to the one you created in Step 1.
Step 3 Use the Oracle user created in Step 2 to install Cisco RPMS.
|
Note Because there is existing CiscoSecure UNIX data on the machine, Cisco RPMS installation will fail until these steps are performed. |
Step 2 Create an Oracle user with a default tablespace equal to the one you created in Step 1.
Step 3 Use the Oracle user created in Step 2, to install Cisco RPMS.
To install Cisco RPMS over a previous CiscoSecure installation and delete the existing CiscoSecure UNIX data:
Step 4 Remove all the CiscoSecure UNIX or Oracle tables from the database.
Step 5 Enter the following commands:
Step 6 Install Cisco RPMS.
|
Note Cisco recommends this method for replacing a Cisco RPMS 1.0x installation. For more information on installing or uninstalling Cisco RPMS, see the Cisco Resource Pool Manager Server Installation Guide. |
View the database configuration:
Step 2 Note the TNS name and RPMS Oracle tablespace username and password.
Step 3 Stop the currently installed Cisco RPMS.
Step 4 Uninstall the current Cisco RPMS release.
Step 5 Manually remove any directories and/or files remaining in the Cisco RPMS home directory.
Step 6 After you have backed up the Cisco RPMS 1.0.x database tables and data, and uninstalled Cisco RPMS 1.0.x, you can install Cisco RPMS 1.1. with this exception:
When prompted with the question "Is this a new RPMS Installation?" select No.
|
Note When upgrading from 1.0.x to 1.1, you must choose "No." This preserves the configuration data (such as DNIS groups, and Customer profiles) and updates the Oracle tables to the new format. If you do not choose No, installation fails and the new tables are not created. |
Make sure that the resource service commands and parameters are entered correctly. Cisco RPMS does not perform any validation of the resource service values. As a result, incorrect service commands and/or parameters might cause calls to fail.
|
Note The Position field in the Valid Resource Data page determines the order resource groups and the assigned resource services are used when multiple resource groups are configured for the same customer profile. To change this setting, select Configuration>Customers >Resource Data. |
If the disk on which the RPMS server resides become full, the RPMS server will fail to perform. It is the responsibility of the user to manage the disk space.
Call Detail Records (CDR) are written to the disk on daily basis, on call initiation/termination. You must regularly archive data according to your operational requirements, so that the file system is not filled with historical information. Make sure to archive such information to tapes, or move it to another server periodically.
Following are the minimum Cisco IOS version requirements per platform:
| Router Platform | Cisco IOS version |
|---|---|
|
Note Currently, Cisco IOS version 12.2(1c) does not provide support for NAS audit and throttling, but Cisco IOS versions 12.2(2)XB and 12.2(5) will. |
|
Data over Voice Bearer Services (DOVBS) is a dial service that uses a customer profile and an assigned resource group of digital resources to direct data calls with a speech call type to HDLC controllers.
To support ISDN Data over Voice Bearer Service (DOVBS), use a DNIS group and a configured customer profile to direct the speech call to the appropriate digital resource.
The DNIS group assigned to the customer profile should have a call type of speech. The resource group assigned to this customer profile will be digital resources and will have a call type of speech, so the call will terminate on an HDLC controller rather than a modem.
 |
Caution This Cisco RPMS feature, which allows you to define the NAS resource group to use for a given call type, should be exercised with caution. If mis-configured to use improper NAS resources for a given call type, it can cause problems. For example, a speech call should not be configured to use the digital resource groups in the NAS unless DoVBS is required. Similarly, a digital call should not be configured to use analog/modem resources in the NAS. Mismatching call types and resources results in an attempt to utilize a resource that is unable to terminate the call, causing it to fail. |
By default, rpms.log has no maximum file size limit. Because Cisco RPMS defaults to no subsystem debugging, excessive rpms.log file size is not an issue until debugging is used. If it becomes necessary to limit the size, debug log limitations can be set with the following two keys under the [Debug] Section in the rpms.conf file:
|
Note Setting MaxFileSize to 0 results in no MaxFileSize limit. |
The following example sets the maximum log file size to 5 megabytes and the amount of data saved to 1 kilobyte when the log is reset. These settings cause rpms.log to be reset when it reaches 5 megabytes, and the last 1024 kilobyte of text would be retained.
After updating rpms.conf MaxFileSize and ResetSaveSize keys, you can commit the changes by running <RPMS_home_dir>/config/update.
You must configure a parameter named RPMSMaxHeap after installing RPMS. You can edit this variable in the rpms.conf file.
The value depends on the amount of RAM the Cisco RPMS host contains. The amount of available RAM also limits the maximum number of active calls Cisco RPMS can hold. The values are as follows:
| RAM | RPMSMaxHeap Value | Max. # Active Calls |
|---|---|---|
By default, the RPMSMaxHeap is set to 256m. Cisco RPMS must be restarted to apply these changes. This parameter is not updated by running <RPMS_home_dir>/config/update.
Under some heavy alert conditions, e-mail alerts might not be sent. To determine if the e-mail alert queue is being overrun, set the Minimum Error Log Level key under Administration>Server to moderate. If an overflow occurs, an "Unable to send alert message. Alert Queue was full" message is logged in the current error file.
To prevent the e-mail alert queue from being overrun, increase the MaxQueueSize key in the Alert>Server page or in the E-mail Alerter Local section of the rpms.conf file. The default queue size of 20 mail messages should be sufficient for most systems.
|
Note When alert logging is enabled, all e-mail notifications are logged in the alerts.log file. |
To commit changes, run <RPMS_home_dir>/config/update.
This section describes possibly unexpected behavior and known issues regarding release 1.1 of Cisco RPMS.
Multiple Cisco RPMS servers can be implemented in a network architecture to act as fail-over servers. However, each active Cisco RPMS server requires one dedicated fail-over server to ensure reliability.
Use a proper configuration with multiple servers, and do not exceed two servers in resource group.
When changing the backup server configuration from one server to the other, the secondary server (master destination) does not show the change properly on the GUI. This only happens with multiple master-to-master replications.
When using Secure Socket Layer (SSL) privacy, use Netscape v4.07 or above.
Remove any previously configured resource group. For example:
Ensure that resource pooling is still enabled.
To use RLM, you have to have a controller run PRI. For example, use the following commands:
To start the RLM, perform the following configurations:
When using SS7 signaling on a NAS that is configured to communicate with Cisco RPMS, like resources are automatically put into pre-defined resource groups.
One or more of the following predefined resource groups may be created on the NAS:
Once the predefined resource groups are created, no new resource groups may be created.
When the NAS receives the Call-Accept reply with the resource group name from Cisco RPMS, the NAS tries to allocate a resource from one of the preconfigured SS7 resource groups based on the following mapping:
| RPMS Resource Group | NAS Resource Group |
|---|---|
|
Note If the NAS needs to allocate a resource for an incoming Speech or V.110 call, the NAS tries rg_ss7_nextport first. Only when no resource is available from rg_ss7_nextport does the NAS then try rg_ss7_mica. |
Once one matching resource is allocated, the resource-group name, from which the resource is allocated, is copied to Resource-Allocated message and sent to Cisco RPMS. This way Cisco RPMS knows which resource group is used for the call.
When the Redundant Link Manager (RLM) is stopped, or Resource Management Protocol (RMP) is disabled on the NAS, the NAS puts the preconfigured SS7 resource groups back into system default resource groups, removing them from use.
Resource groups required for non-SS7 call processing must then be created on the NAS.
Cisco RPMS SS7 resource group configurations do not have to be changed. The Cisco RPMS SS7 resource group configurations can be used at the same time as the non-SS7 resource groups.
One TACACS+ connection is required to enable the Resource Management Protocol (RMP) for the NAS to communicate with Cisco RPMS. For example:
The default TACACS+ server timeout in the Cisco IOS software is five seconds, and the default ISDN guard-timer in the Cisco IOS software is eight seconds. If the primary Cisco RPMS server is not reachable in five seconds, the ISDN guard-timer may expire while waiting for a response from a secondary Cisco RPMS server, causing the call to drop.
Diagnose guard-timer issues by tracking the number of GUARDTIMER_EXPIRY_EVENT occurrences in the show resource-pool queue statistics command output in the Cisco IOS software.
Tag names, also known as tag value pairs, are used with command-line interface (CLI) commands to set individual attributes of a given profile. For example, the CreateCustomer command DESC tag allows the user to set the Customer profile's description.
Note that the backslash character is supported on a limited set of CLI tags, while the double quote is supported only with the CreateResourceService PARAMS tag.
To include a backslash or double quote within a CLI tag, you must precede these characters with an escape character "\" and surround the tag value with a single quote.
| Tag Element | Syntax | Result |
|---|---|---|
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Posted: Mon Jan 20 21:46:04 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.