Cisco Cisco Prime Access Registrar 6.1

Page de 6
   
3
Cisco Prime Access Registrar 6.1.3  Release Notes
 
  Cisco Prime Access Registrar 6.1.3 Bugs
Known Anomalies in Cisco Prime Access Registrar 6.1.3
 lists the known anomalies in Prime Access Registrar 6.1.3.
Anomalies Fixed in Cisco Prime Access Registrar 6.1.3.2
 lists the anomalies fixed in Prime Access Registrar 6.1.3.2.
Table 3
Known Anomalies in Prime Access Registrar 6.1.3
Bug
Description
After upgrade Prime Access Registrar should update the deleted attributes of the 
earlier version.
Upgrade getting failed during misconfiguration of the earlier version.
Table 4
Anomalies Fixed in Prime Access Registrar 6.1.3.2 
Bug
Description
Prime Access Registrar stops working randomly while handling 
Disconnect-Peer-Request (DPR) / Disconnect-Peer-Answer (DPA) requests.
Mobile Station International Subscriber Directory Number (MSISDN) decoding is 
failing when MSISDN bytes from Home Location Register (HLR) are in ASCII range 
and printable characters.
Device-Watchdog-Request (DWR) / Disconnect-Peer-Request (DPR) message 
handling in connection management.
Prime Access Registrar stops working randomly during Diameter connection 
establishment.
No validation error while configuring a client and a remote server with same IP 
address but different shared secret.
SIGTRAN-M3UA TCAP ID must be unique and same TCAP ID must not be used for 
multiple requests.
Two message authenticator in final RADIUS access-accept.
Packet leak in MRD call flow.
Prime Access Registrar stops working while processing response packet from the 
remote server.
Prime Access Registrar stops working randomly when StickySession is enabled.
Prime Access Registrar stops working while enabling fast-reauthentication with 
realm in dia-eap-aka service.