Session information for PDSN service in the show resource command will not match the limit value for PDSN from show license info in the case where PDSN Rev-A is also licensed on the chassis because the PDSN service shares licenses with Rev-A and can borrow from it.
In the Session information of the show resource command, the limit value in the PDSN service will not match the limit value for PDSN from show license info in the case where PDSN Rev-A is also licensed, and in fact it keeps changing each time the command is run. But the other services do match exactly with the license info.
Here is an example:
show resource
Session information:
PDSN Service:
In Use : 23478
Max Used : 33676
Limit : 113247
License Status : Within Acceptable Limits
HA Service:
In Use : 9057
Max Used : 14893
Limit : 30000
License Status : Within Acceptable Limits
L2TP LNS Service:
In Use : 0
Max Used : 0
Limit : 1000
License Status : Within Acceptable Limits
EV-DO Rev A PDSN Service:
In Use : 17753
Max Used : 26909
Limit : 25000
License Status : Within Acceptable Limits
Show license info
Session Limits:
Sessions Session Type
-------- -----------------------
106000 PDSN
30000 HA
1000 L2TP LNS
25000 EV-DO Rev A / PDSN
Note that the EVDO Rev A, HA and L2TP service limits match between the commands, but the PDSN service does not:
113,247 vs. 106,000
The reason for this is that the PDSN license actually shares its license limit with the EV-DO Rev A PDSN license limit, and can “borrow” licenses from EV-DO. This allows the maximum number of subscribers to connect in the case where there are many more subscribers that do not have Rev-A capability than the system is licensed for. The limit is calculated by simply adding together the two license limits (106,000 + 25,000 = 131,000) and then subtracting the currently used EV-DO licenses (17753), to get 131,000 – 17,753 = 113,247 as displayed above. As a result, this value will be constantly changing.
Imported from Starent Networks Knowledgebase Article # 10400