|
|
These release notes describe important information and caveats for the Cisco Resource Pool Manager Server (Cisco RPMS) Release 1.04. Information in this document supplements information in the Cisco Resource Pool Manager Server Installation Guide, the Cisco Resource Pool Manager Server Configuration Guide, and the Cisco Resource Pool Manager Server Solutions Guide.
The following topics are discussed:
This section describes information that was unavailable when the Cisco Resource Pool Manager Server Installation Guide was printed, possibly unexpected behavior, and known issues.
Sun has replaced patch 105490-05 with 107733-06; as a result, the new Sun patch requirement has changed. You must now load patch 105490-05 (or later) or 107733-06 (or later).
It is also recommend you install the Solaris 2.6 patch cluster.
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. [CSCdk62201]
This section describes limitations and restrictions of Cisco RPMS.
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. |
To install Cisco RPMS over a previous CiscoSecure installation and keep the existing CiscoSecure UNIX data:
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 2 Enter the following commands:
Step 3 Install Cisco RPMS.
|
Note Cisco recommends this method for replacing a Cisco RPMS 1.03 installation. For more information on installing or uninstalling Cisco RPMS, please see the "Installing Cisco RPMS" section in the Cisco Resource Pool Manager Server Installation Guide. |
Step 2 Install Cisco RPMS 1.04.
|
Note When you get to the step in the installation asking for the hostname and FQDN, enter Yes to clear the Database or No to leave the database intact. |
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.
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.
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.log 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, restart Cisco RPMS.
You must configure a parameter named RPMSMaxHeap after installing RPMS. 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.
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. |
This section describes possibly unexpected behavior and known issues regarding release 1.04 of Cisco RPMS.
When failover occurs from primary to backup, port usage information in primary is not available to backup. The NAS fails over from one Cisco RPMS server to another and the port-usage information in the failed server is not available to the backup server. The backup servers starts tracking port-usage from zero.
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.
VPDN authorization via AAA server not used if there is no VPDN group on RPMS. When VPDN information is not found on the RPMS server, the call is processed as a retail dial service call without trying to create VPDN tunnel by using local AAA server configuration.
When using Secure Socket Layer (SSL) privacy, use Netscape v4.07 or above.
Changes in Cisco RPMS are required when the Cisco NAS is connected to the PSTN by SS7 signaling and trunking.
Cisco RPMS provides predefined, system-wide resource groups to support SS7 calls. The desired SS7 resource group is configured for a customer's DNIS group/call type association. This DNIS group/call type/SS7 resource group association is then assigned to the customer profile. If an optional resource service is desired, also configure the SS7 resource group as part of the resource data assigned to the customer profile.
When assigning the desired DNIS Groups and call types to the customer profile, also assign the predefined SS7 resource group from the SS7 Resource Group pull-down menu by selecting Configuration>Customer>DNIS Grps/Call Types&SS7. The SS7 Resource Group menu options are:
Use the None option to indicate that there are no SS7 calls for the current DNIS group.
When SS7 and RPMS are enabled on the NAS:
|
Note If any of these conditions are not met, the NAS displays a message indicating that SS7/RPM/RPMS internetworking cannot be performed. |
One TACACS connection is required to enable the Resource Management Protocol (RMP) for the NAS to communicate with Cisco RPMS. For example,
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 and when the NAS is configured to communicate with Cisco RPMS, like resources in the NAS are put into single resource groups.
|
Note All of the groups must have the same number of resources and that number must equal the number of interface channels available from the public network switch. This grouping scheme prevents a channel-not-available (CNA) signal from being sent to the signaling point. |
The following predefined resource groups are created on the NAS:
When these resource groups are configured, the NAS will not allow any customer configuration for new resource groups.
|
Note The exception is the resource group cisco_tac. The cisco_tac resource group is reserved for Cisco TAC to log in to the NAS for debugging. It can be configured for any kind of resource available on the NAS. It is the only allowed resource group configuration (in NVRAM) with SS7. |
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 that if the NAS needs to allocate a speech resource for an incoming call, the NAS tries rg_ss7_v24_analog first. Only when no resource is available from rg_ss7_v24_analog, does the NAS then try rg_ss7_mica. This same process is applied to the rg_ss7_v110 and rg_ss7_mica resource groups. For V.110 calls, the NAS looks for Toucan boards first and then Mica h/w with V.110 supported in p/w.
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.
Any resource groups used for non-SS7 call processing must then be reconfigured 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.
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. |
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
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 comme nts.
Posted: Tue Jan 21 01:10:41 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.