Cisco Cisco Packet Data Gateway (PDG)
PDSN Changes in Release 16
PDSN Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
309
CSCun65435 - Assertion at sessmgr_imsa.c:453 Function:
sessmgr_authorize_with_imsa()
Feature Changes
IMSA Session for Mobile-IP Call on PDSN and HA
Previous Behavior: Earlier, an IMSA session was being created for mobile-ip call on PDSN and HA together.
New Behavior: For mobile-ip call, the IMSA session is present only on HA, while the earlier IMSA session created by
PDSN is terminated. This behaviour is only for IMSA session, while it is consistent for ACS session.
PDSN is terminated. This behaviour is only for IMSA session, while it is consistent for ACS session.
CSCzn10122 - After configuring no max-login failures local user is not granted
acces
Feature Changes
No Max-Login Failure Command Behavior Changes
The command
“no local-user max-failed-logins”
is not intuitive.
Previous Behavior: The command
“no local-user max-failed-logins”
sets the max login failuers to one
(functionally). But the user assumed that the command disabled the feature of checking the max login failures. Instead,
the command to disable the max login failures check is
the command to disable the max login failures check is
“local-user username <username> no-lockout-
login-failures password <password>”
which disables locking for the specific local-user account on login
failures.
New Behavior: The command
“no local-user max-failed-logins”
now causes the system to not check for
max login failures and disables the lock-out feature for all local-users.
Customer Impact: Existing customer who are currently using this feature expecting the old functionality will no
longer see the old behavior as described above.
longer see the old behavior as described above.
Command Changes
no local-user max-failed-logins
The CLI
“no local-user max-failed-logins”
does not check for max login failures. It also disables the lock-out
feature for all local-users.