[cisco-bba] 'sessions' versus 'PPPoA/E sessions' counts

[Tassos Chatzithomaoglou]

"sh pppoe sum" has a raw called TRANS which are the PPPoE sessions that are in in 
transient state, i.e. ppp negotiation hasn't finished.

"sh caller sum" shows only the number of PPPoE sessions that have completed ppp 
negotiation and are terminated locally.

For PPPoE, you can find the number of pending sessions (+ their macs) with :

sh pppoe ses | i LCP

For PPP, you can find the number of incomplete "sessions" with :

sh ppp stat | i Links at

A PPPoE session is defined as pending when the first PADI packet arrives. In order for 
this session to become established, it must pass through the PPPoE (PADI/PADO/PADR/PADS) 
and PPP (LCP/NCP/IPCP) phases (although NCP/IPCP might not be needed for VPDN).

-- 
Tassos

Frank Bulk wrote on 05/06/2009 06:33:
> Ah, so you're saying that even though it says
> 	PPPoA sessions = 3711
> 	PPPoE sessions = 212
> it doesn't mean they are *active* sessions.  That doesn't seem to make
> sense, because "sh pppatm summary" and "sh pppoe summary" give the same
> totals as "sh subsc statis".  I bet if I screen-scraped my "show callers"
> they would match up with "show subsc statis".
> 
> So it's not any clearer to me what pending really means.
> 
> Frank
> 
> -----Original Message-----
> From: cisco-bba-bounces at puck.nether.net
> [mailto:cisco-bba-bounces at puck.nether.net] On Behalf Of Tassos
> Chatzithomaoglou
> Sent: Thursday, June 04, 2009 8:12 AM
> To: cisco-bba at puck.nether.net
> Subject: Re: [cisco-bba] 'sessions' versus 'PPPoA/E sessions' counts
> 
> Number of sessions currently up + Number of sessions currently pending =
> PPPoA + PPPoE
> 
> PPPoA or PPPoE doesn't take into account whether the sessions have finished
> their negotiation.
> 
> --
> Tassos
> 
> Frank Bulk wrote on 04/06/2009 13:22:
>> When I looked at my "sh subscriber statistics" I noticed that 
>> - my "sessions currently up" does not add up to the number of PPPoA and
>> PPPoE sessions: how can that be?
>> - I have a very high "Number of sessions failed to come up"
>> - my call rate is 3341/minute, which is 56/second
>>
>> I know I have lots of provisioned VP/VCs that don't have an active DSLAM
>> port, but I'm not sure if that contributes to an explanation.
>>
>> If there's a debug I need to turn on to "see", please suggest the
>> appropriate one.  It seems that the box is overly busy.
>>
>> Frank
>>
>> ==================================================================
>> Router#sh subscriber statistics
>>
>> Current Subscriber Statistics:
>>
>> Number of sessions currently up: 2596
>> Number of sessions currently pending: 1327
>> Number of sessions currently authenticated: 2596
>> Number of sessions currently unauthenticated: 1327
>> Highest number of sessions ever up at one time: 2647
>> Mean up-time duration of sessions: 00:01:08
>> Total number of sessions up so far: 543761664
>> Mean call rate per minute: 3341, per hour: 200502
>> Number of sessions failed to come up: 543534572
>> Access type based session count:
>> PPPoA sessions = 3711
>> PPPoE sessions = 212
>>
>> _______________________________________________
>> cisco-bba mailing list
>> cisco-bba at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-bba
>>
> 
> _______________________________________________
> cisco-bba mailing list
> cisco-bba at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-bba
> 
>