 Feedback
|
Table Of Contents
Cisco Prime Access Registrar 6.0.1
Release NotesNew and Enhanced Features in Cisco Prime Access Registrar 6.0.1
TACACS+ Command Authorization Support
Map Restore Data Authorization Support
MSISDN to IMSI Reverse Translation Support
Multiple Remote Server Support
Support for Blacklisting IMSI Values
Enhancements in Cisco Prime Access Registrar 6.0.1.1
Enhancements in Cisco Prime Access Registrar 6.0.1
Co-Existence With Other Network Management Applications
Cisco Prime Access Registrar 6.0.1 Licensing
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1.3
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1.2
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1.1
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1
Known Anomalies in Cisco Prime Access Registrar 6.0.1.3
Known Anomalies in Cisco Prime Access Registrar 6.0.1.2
Known Anomalies in Cisco Prime Access Registrar 6.0.1.1
Known Anomalies in Cisco Prime Access Registrar 6.0.1
Obtaining Documentation and Submitting a Service Request
Cisco Prime Access Registrar 6.0.1
Release Notes
Cisco Prime Access Registrar (Prime Access Registrar) is a high performance, carrier class RADIUS/Diameter solution that provides scalable, flexible, intelligent authentication, authorization, and accounting (AAA) services.
Prime Access Registrar comprises a RADIUS/Diameter server designed from the ground up for performance, scalability, and extensibility for deployment in complex service provider environments including integration with external data stores and systems. Session and resource management tools track user sessions and allocate dynamic resources to support new subscriber service introductions.
Note
Prime Access Registrar can be used with Solaris 10, or Red Hat Enterprise Linux 5.3/5.4/5.5/6.0/6.1/6.2 32-bit /64-bit operating system (with 32-bit library is only for 64-bit operating system) using kernel 2.6.18-128.el5 or later versions of 2.6, and Glibc version: glibc-2.5-34 or later.
Contents
This release note contains the following sections:
•
•
•
•
•
•
New and Enhanced Features in Cisco Prime Access Registrar 6.0.1
Prime Access Registrar introduces the following features:
•
TACACS+ Command Authorization Support
Prime Access Registrar provides command authorization support to authorize the cmd mode commands. Command authorization is based on device access rules and the decision to authorize is based on command sets and conditions or expressions defined for the access rules. They determine whether to authorize a set of commands for the user or not.
If you enable TACACS+ command authorization for a service, you must define the following:
•
•
•
When a packet enters the service, it selects the first device access rule and evaluates the condition. If the condition is met, then the service applies the device access rule for the request. If the command that is processed matches a command listed in the command set, the service decides on whether to permit the command for the user or not based on the permissions set up.
SIGTRAN-M3UA Enhancements
Prime Access Registrar provides the following enhancements for SIGTRAN-M3UA:
•
•
•
•
Map Restore Data Authorization Support
Prime Access Registrar provides the Map Restore Data functionality to fetch the profile information of a subscriber from the HLR. You can configure an M3UA service with the AuthorizationInfoLookUp parameter as Map-Restore to use this functionality. The GUI is updated with new fields to support this functionality.
Map Restore Data Authorization Flow
Prime Access Registrar sends a MAP_SEND_AUTH_INFO request to HLR on receiving EAP-SIM / EAP-AKA authentication request and fetches the authentication vectors in MAP_SEND_AUTH_INFO_RES message. Prime Access Registrar checks the IMSI and if it is authentic, sends a MAP_RESTORE_DATA_REQUEST to fetch the profile information from the HLR. HLR then responds with MAP_INSERT_SUBSCRIBER_DATA request to Prime Access Registrar. The request contains the circuit switched (CS) profile information for a subscriber.
Prime Access Registrar server stores the profile information based on the ProfileInfo configuration and sends a MAP_INSERT_SUBSCRIBER_DATA_RESPONSE to HLR. HLR responds with MAP_RESTORE_DATA_RESPONSE to Prime Access Registrar. After successful acknowledgment of MAP_RESTORE_DATA, Prime Access Registrar server maps the fetched profile through RestoreDataMappings to any of the environment variables configured by the user. The CS profile used to authorize WI-FI access which is fetched from HLR can be transported to access point in any of the radius attribute.
The mapping of the values in the response to a profile is possible based on the configuration in the profilemappings configuration.
MSISDN to IMSI Reverse Translation Support
You can configure an M3UA service to fetch MSISDN from IMSI or vice versa (IMSI from MSISDN) through RADIUS packets. Set the AuthorizationInfoLookUp parameter in the CLI to one of the following:
•
•
The GUI is also updated with the parameter to support this functionality.
SCTP Multihoming Support
Multihoming feature of Stream Control Transmission Protocol (SCTP) provides the ability for a single SCTP endpoint to support multiple IP addresses. With this feature, each of the two endpoints during an SCTP association can specify multiple points of attachment. Each endpoint will be able to receive messages from any of the addresses associated with the other endpoint. With the use of multiple interfaces, data can be sent to alternate addresses when failures occur and thus Prime Access Registrar runs successfully even during network failures.
Prime Access Registrar allows you to configure multiple source and destination addresses on the remote server using the CLI. The GUI is also updated with an option to provide additional source and destination IP addresses for the remote server.
Multiple Remote Server Support
Prime Access Registrar supports multiple remote servers with the protocol type, SIGTRAN-M3UA. However, Prime Access Registrar validates and ensures the following when multiple remote servers are available:
•
•
•
•
Support for Blacklisting IMSI Values
Prime Access Registrar allows you to blacklist one or more IMSI values available in the EAP-SIM or EAP-AKA requests forwarded to an HLR. A scripting point option is provided such that you can set an environment dictionary variable Blacklisted-IMSI to TRUE or FALSE to blacklist or whitelist IMSI values respectively. An IMSI value marked as blacklisted is rejected and will not be forwarded to the HLR. You can configure a notification code to represent failure. If no notification code is set, 16384 representing General Failure is sent upon rejection of an IMSI value.
Solaris 10 Support
Prime Access Registrar supports SIGTRAN-M3UA on Solaris platform in addition to Linux. You must ensure that you have the following packages while installing Prime Access Registrar in Solaris:
•
•
•
•
•
•
•
Enhancements in Cisco Prime Access Registrar 6.0.1.1
Table 1 gives the details on the enhancements made in Prime Access Registrar 6.0.1.1.
Enhancements in Cisco Prime Access Registrar 6.0.1
Table 2 gives the details on the enhancements made in Prime Access Registrar 6.0.1.
System Requirements
This section describes the system requirements to install and use the Prime Access Registrar software.
Table 3 lists the system requirements for Prime Access Registrar 6.0.1.
Co-Existence With Other Network Management Applications
To achieve optimal performance, Prime Access Registrar should be the only application running on a given server. In certain cases, when you choose to run collaborative applications such as a SNMP agent, you must configure Prime Access Registrar to avoid UDP port conflicts. The most common conflicts occur when other applications also use ports 2785 and 2786. For more information on SNMP configuration, see the Configuring SNMP section, in the Installing and Configuring Cisco Prime Access Registrar, 6.0.
Cisco Prime Access Registrar 6.0.1 Licensing
In Prime Access Registrar 6.0.1, licensing is based on transactions per second (TPS) or concurrent online/active subscribers/devices sessions (SUB). TPS is calculated based on the number of packets flowing into Prime Access Registrar. In Session based licensing model, the license is managed based on the number of sessions that resides in Prime Access Registrar. During Prime Access Registrar startup, either TPS based licensing or session based licensing model should be loaded. For more information on licensing, see the Open Source Used In Cisco Prime Access Registrar 6.0.1.
Bugs
This section provides information about known anomalies in Cisco Prime Access Registrar and information about anomalies from previous versions of Prime Access Registrar that have been fixed.
•
•
•
•
•
•
•
•
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1.3
Table 4 lists the anomalies fixed in Prime Access Registrar 6.0.1.3.
Table 4 Anomalies Fixed in Prime Access Registrar 6.0.1.3
RFC compliance for routing context mapping.
MAP request to support CgPA formatting to subsequent MAP requests in CdP.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1.2
Table 5 lists the anomalies fixed in Prime Access Registrar 6.0.1.2.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1.1
Table 6 lists the anomalies fixed in Prime Access Registrar 6.0.1.1.
Anomalies Fixed in Cisco Prime Access Registrar 6.0.1
Table 7 lists the anomalies fixed in Prime Access Registrar 6.0.1.
Known Anomalies in Cisco Prime Access Registrar 6.0.1.3
Table 8 lists the known anomalies in Prime Access Registrar 6.0.1.3.
Table 8 Known Anomalies in Prime Access Registrar 6.0.1.3
Need to set a limit or count of number of consecutive timeouts in sigtran-m3ua.
Known Anomalies in Cisco Prime Access Registrar 6.0.1.2
Table 9 lists the known anomalies in Prime Access Registrar 6.0.1.2.
Table 9 Known Anomalies in Prime Access Registrar 6.0.1.2
OCI should support same attributes occurrence of mutiple times in marker list.
Send Authentication Info message should handle the User error.
Unable to send packet while using scripting point (IMSI translation) in sigtran-m3ua remote server.
GT Prefix length has to be less than Dest GT length for prefix routing
After upgrade from CPAR6.0.1, the save and reload is not working. For a workaround, see Important Notes.
Validation error occurs after upgrading from CAR 5.0 FCS to CPAR 6.0.1.1 FCS. For a workaround, see Important Notes.
With Eap-sim failover, first packet is getting rejected with sigtran-m3ua.
Negative invoke ID in sigtran-m3ua map flow.
RFC compliance for routing context mapping.
Known Anomalies in Cisco Prime Access Registrar 6.0.1.1
Table 10 lists the known anomalies in Prime Access Registrar 6.0.1.1.
Table 10 Known Anomalies in Prime Access Registrar 6.0.1.1
OCI should support same attributes occurrence of mutiple times in marker list.
Send Authentication Info message should handle the User error.
Unable to send packet while using scripting point (IMSI translation) in sigtran-m3ua remote server.
GT Prefix length has to be less than Dest GT length for prefix routing
After upgrade from CPAR6.0.1, the save and reload is not working. For a workaround, see Important Notes.
Validation error occurs after upgrading from CAR 5.0 FCS to CPAR 6.0.1.1 FCS. For a workaround, see Important Notes.
Known Anomalies in Cisco Prime Access Registrar 6.0.1
Table 11 lists the known anomalies in Prime Access Registrar 6.0.1.
Important Notes
Table 12 identifies certain important observations documented against Prime Access Registrar 6.0.1, in addition to the open caveats mentioned in Known Anomalies in Cisco Prime Access Registrar 6.0.1.2 and Known Anomalies in Cisco Prime Access Registrar 6.0.1.1.
Related Documentation
The following is a list of the documentation for Prime Access Registrar 6.0.1. You can access the URLs listed for each document at www.cisco.com on the World Wide Web. We recommend that you refer to the documentation in the following order:
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Cisco Prime Access Registrar 6.0.1 Licensing" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2013 Cisco Systems, Inc. All rights reserved.
