Примечания к выпуску для Cisco Cisco Prime Access Registrar 6.1
7
Cisco Prime Access Registrar 6.1.2 Release Notes
OL-32180-01
Known Anomalies in Cisco Prime Access Registrar 6.1.2.1
Known Anomalies in Cisco Prime Access Registrar 6.1.2.1
lists the known anomalies in Prime Access Registrar 6.1.2.1.
Known Anomalies in Cisco Prime Access Registrar 6.1.2
lists the known anomalies in Prime Access Registrar 6.1.2.
Anomalies Fixed in Cisco Prime Access Registrar 6.1.2.5
lists the anomalies fixed in Prime Access Registrar 6.1.2.5.
Table 5
Known Anomalies in Prime Access Registrar 6.1.2.2
Bug
Description
access-challenge is also sent in case of no STP connection in EAP-SIM/EAP-AKA.
Prime Access Registrar does not resync with the HLR when EAP-AKA AT_AUTN is
out of sync.
out of sync.
Outgoing scripting point not working in 3GPP authorization service.
“3GPP Pseudonym cannot be decoded” error appears in all EAP message traces.
Prime Access Registrar throws an error message every second into the stack log.
Table 6
Known Anomalies in Prime Access Registrar 6.1.2.1
Bug
Description
SNMP traps contain wrong values.
Prime Access Registrar does not resync with the HLR when EAP-AKA AT_AUTN is
out of sync.
out of sync.
Table 7
Known Anomalies in Prime Access Registrar 6.1.2
Bug
Description
Diameter EAP stats not getting updated.
Unable to configure different shared secrets in the same netmasked remote server.
While initiating MAR from Prime Access Registrar to HSS over Swx interface, it is
not setting the proxy bit in command-code.
not setting the proxy bit in command-code.
Prime Access Registrar does not work during Diameter server connection
establishment with TLS while using SSL (2.x).
establishment with TLS while using SSL (2.x).
Outage policy attribute is missing in EAP-AKA-Prime service.