Cisco Cisco Prime Access Registrar 6.1

Solaris support for Prime Access Registrar Version 6.1 will be implemented in a future release.

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 

 lists the known anomalies in Prime Access Registrar 6.1.

 lists the anomalies fixed in Prime Access Registrar 6.1.

With OCI buffering, during restarts, rarely few packets can be missing.

odbc-acc failover is not working when backup server buffer is disabled. 

Prime Access Registrar intermittently crashes in stress test. 

Send Authentication Info message should handle the user error.

Prime Access Registrar crashes if ORACLE path is invalid or without ORACLE path.

Replication takes more time to stop If SNMP is enabled while restarting 
Prime Access Registrar.

Radius Process restart (crash) when Prime Access Registrar encounters ORA native 
error

Service Indicator value is not reflecting in sigtran M3UA remote server

Replication issues in Prime Access Registrar 6.0.1

In GUI while trying to access replication it prompts for reload

Exception error when cancelling clients after validation error is thrown

MRD flow need to support for map version 3 in m3ua remoteserver

User List is not getting deleted in GUI