Cisco Cisco Prime Access Registrar 6.0

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.

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 

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.

 lists the 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.