Cisco Cisco IOS Software Release 12.4(22)XR
59
Cisco Packet Data Serving Node Release 5.1 for Cisco IOS Release 12.4(22)XR1
OL-20782-01
New Features in This Release
VPDN Conditional Debugging
The conditional debugging feature enables you to verify or observe the debugs of a particular session.
You can enable conditional debugging depending on the IMSI or the username, by using the following
CLI command.
You can enable conditional debugging depending on the IMSI or the username, by using the following
CLI command.
PDSN# debug condition ?
called called number
calling calling --------------------> for IMSI
glbp interface group
interface interface
ip IP address
mac-address MAC address
match-list apply the match-list
standby interface group
username username -------------------> for username
vcid VC ID
voice-port voice-port number
xconnect Xconnect conditional debugging on segment pair
In Cisco PDSN Release 5.1, conditional debugging is enabled for VPDN calls. If you enable IMSI
(calling station ID)-based conditional debugs, you must verify if the session IMSI matches the IMSI that
was set through the conditional debugging CLI command. If a match exists, VPDN context debug flags
are set. If a match does not exist, the debug flags in the VPDN context are not set, avoiding printing of
(calling station ID)-based conditional debugs, you must verify if the session IMSI matches the IMSI that
was set through the conditional debugging CLI command. If a match exists, VPDN context debug flags
are set. If a match does not exist, the debug flags in the VPDN context are not set, avoiding printing of
MS Term-Req in IPCP Phase(LCP
Term Req during IPCP nego rcvd)
Term Req during IPCP nego rcvd)
Total number of LCP term requests received from the MN
during authorization negotiation since the system was last
restarted.
during authorization negotiation since the system was last
restarted.
A11 De-Registration in IPCP
Phase(A10 release during IPCP nego
by PCF)
Phase(A10 release during IPCP nego
by PCF)
Total number of A10 releases during IPCP negotiation by
the PCF since the system was last restarted.
the PCF since the system was last restarted.
IPCP Negotiation Fail( Failure
Reasons Options)
Reasons Options)
Total number of PPP IPCP failures due to options.
Not enough IP resource for
allocation(Not enough IP resource for
allocation)
allocation(Not enough IP resource for
allocation)
Total number of PPP negotiations terminated per PCF due
to inadequate IP resources in the IP pool for allocation. The
IP pool is downloaded from the AAA server or locally.
to inadequate IP resources in the IP pool for allocation. The
IP pool is downloaded from the AAA server or locally.
When configuring the local IP pool or the wrong local IP
pool in Cisco PDSN, this counter does not increment;
however, the global counter is incremented.
pool in Cisco PDSN, this counter does not increment;
however, the global counter is incremented.
In earlier releases, if the remote IP pool is configured on
Cisco PDSN, the unknown counter was incremented along
with this counter. In Cisco PDSN Release 5.1, however, the
unknown counter does not increment along with this
counter.
Cisco PDSN, the unknown counter was incremented along
with this counter. In Cisco PDSN Release 5.1, however, the
unknown counter does not increment along with this
counter.
Other Failures in IPCP Phase
(Unknown)
(Unknown)
Total number of PPP connection requests that failed at the
IPCP phase due to unknown reasons, since system was last
restarted.
IPCP phase due to unknown reasons, since system was last
restarted.
Table 12
IPCP Phase Failure Counters (continued)