achatz at forthnet
May 6, 2004, 10:46 AM
Post #3 of 3
(560 views)
Permalink
|
That's what i'm trying to avoid, because i'm already using radius accounting for
per-session "logging".
I'm trying to do per-tunnel logging ;-)
adama.faye [at] bell wrote:
> For this I am using the following commands
>
> vpdn logging
> vpdn logging local
> vpdn logging user
> vpdn history failure
>
> You will receive this kind of logging information when the connection is
> down.
>
> Mar 3 15:56:22: %VPDN-6-CLOSED: L2TP LNS Ro-C7204 closed user
> sec_user2 [at] pns; Result 2, Error 6
>
>
> You can also have the failure history with the command :
>
> Ro-C7204-10#sh vpdn history failure
>
> Number of entries in table: 1
> Table size: 20
> User: sec_user2 [at] pns, MID = 338
> NAS: bas1, IP address = 10.64.64.1, CLID = 0
> Gateway: Ro-C7204, IP address = 10.64.64.2, CLID = 0
> Log time: Mar 3 16:08:56.045, Error repeat count: 2
> Failure type: The remote server closed this session
> Failure reason: Result 2, Error 6
>
>
> Thanks.
>
>
>
> -----Original Message-----
> From: cisco-bba-bounces [at] puck
> [mailto:cisco-bba-bounces [at] puck] On Behalf Of Tassos
> Chatzithomaoglou
> Sent: May 6, 2004 12:21 PM
> To: cisco-bba
> Subject: [cisco-bba] vpdn logging tunnel-drop
>
> What exactly does "vpdn logging tunnel-drop" log?
>
> I'm looking for a way to see (sh logging, syslog) when my L2TP tunnels
> drop and the reason
> of drop.
>
>
--
***************************************
Chatzithomaoglou Anastasios
Network Design & Development Department
FORTHnet S.A.
<achatz [at] forthnet>
***************************************
|
