Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Cisco>
  3. BBA
terminating l2 ADSL customers
sysadmin at sunet
Feb 26, 2007, 7:41 PM
Post #1 of 6 (5190 views)
Permalink
Hi ,
I am using cisco 3660 router V-12.2 terminating DSL L2TP VPDN over ATM and
freeradius.

my configuration is as follows

aaa authentication login default local
aaa authentication ppp default if-needed group radius
aaa authorization network default group radius
aaa session-id common

vpdn enable
!
vpdn-group 1
accept-dialin
protocol l2tp
virtual-template 10
terminate-from hostname 172.31.248.207
lcp renegotiation always
l2tp tunnel password 7 xxxxxxxxxxxxxxxxxxx
!
virtual-template 10 pre-clone 600

interface Virtual-Template10
mtu 1492
ip unnumbered FastEthernet0/0.1
ppp authentication chap pap

this is my configuration to run l2 on ATM(AGVC).
I can ping the LAC.

1) do i need to create seperate VPDN-group for each LAC.
2)People who maintainLAC(which is Telstra in this case) told me session is initiated at their end and they get vpdn service unavailable.

when i start the debug for vpdn packets i don't see any thing.

Where am i going wrong. can u please point me through the right direction.any help is much appreciated.


cheers
phani.








_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba
Re: terminating l2 ADSL customers [ In reply to ]
oboehmer at cisco
Feb 26, 2007, 11:25 PM
Post #2 of 6 (4993 views)
Permalink
Sunet Sysadmin <> wrote on Tuesday, February 27, 2007 4:41 AM:

> Hi ,
> I am using cisco 3660 router V-12.2 terminating DSL L2TP VPDN over
> ATM and
> freeradius.
>
> my configuration is as follows
>
> aaa authentication login default local
> aaa authentication ppp default if-needed group radius
> aaa authorization network default group radius
> aaa session-id common
>
> vpdn enable
> !
> vpdn-group 1
> accept-dialin
> protocol l2tp
> virtual-template 10
> terminate-from hostname 172.31.248.207
> lcp renegotiation always
> l2tp tunnel password 7 xxxxxxxxxxxxxxxxxxx
> !
> virtual-template 10 pre-clone 600
>
> interface Virtual-Template10
> mtu 1492
> ip unnumbered FastEthernet0/0.1
> ppp authentication chap pap
>
> this is my configuration to run l2 on ATM(AGVC).
> I can ping the LAC.
>
> 1) do i need to create seperate VPDN-group for each LAC.

No. Just agree with your partner (Telstra) on a tunnel name and
reference this one in "terminate-from hostname <name>", see also below.

> 2)People who maintainLAC(which is Telstra in this case) told me
> session is initiated at their end and they get vpdn service
> unavailable.

Right, you have "terminate-from hostname 172.31.248.207" configured, and
IOS treats "172.31.248.207" as a literal name, not as an IP address. So
please check with Telstra which tunnel name they use, and use this one
in the vpdn-group..

> when i start the debug for vpdn packets i don't see any thing.

try "debug vpdn l2x-event" or "debug vpdn l2x-packet"..

oli

_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba
Re: terminating l2 ADSL customers [ In reply to ]
stavros at staff
Feb 26, 2007, 11:34 PM
Post #3 of 6 (5002 views)
Permalink
Hi,

> I am using cisco 3660 router V-12.2 terminating DSL L2TP VPDN
> over ATM and
> freeradius.

Really breifly....

> terminate-from hostname 172.31.248.207

Remove this, as the tunnel may be setup from multiple points on Telstras
network.

Also try adding source-ip x.x.x.x toyou vpdn configuration to ensure you are
using the right ip address to terminate the tunnel. This is the ip address
that you have given to Telstra for your LNS.

See how you go with that.

Stav!

_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba
Re: terminating l2 ADSL customers [ In reply to ]
sysadmin at sunet
Feb 27, 2007, 1:47 PM
Post #4 of 6 (4973 views)
Permalink
Thanks guys for your suggestions. Know I can see vpdn traffic coming
throw and the tunel is forming with a tunnel id but for some reason the
tunnel is breaking up. this keeps looping . Can you please suggest me
where i am going wrong or can u point me through the right direction.
following is the debug information for debug l2x-event. Any help is much
appreciated.

Feb 28 08:58:44 210.80.157.1 30541: 16:00:24: Tnl35407 L2TP: Shutdown
tunnel
Feb 28 08:58:44 210.80.157.1 30542: 16:00:24: Tnl35407 L2TP: Tunnel
state change from shutting-down to idle
Feb 28 09:02:53 210.80.157.1 30543: 16:04:33: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30544: 16:04:33: L2X: Parse SCCRQ
Feb 28 09:02:53 210.80.157.1 30545: 16:04:33: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30546: 16:04:33: L2X: Protocol Ver 256
Feb 28 09:02:53 210.80.157.1 30547: 16:04:33: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30548: 16:04:33: L2X: Hostname n2158726k-vez8
Feb 28 09:02:53 210.80.157.1 30549: 16:04:33: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30550: 16:04:33: L2X: Framing Cap 0x1
Feb 28 09:02:53 210.80.157.1 30551: 16:04:33: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30552: 16:04:33: L2X: Assigned Tunnel ID 668
Feb 28 09:02:53 210.80.157.1 30553: 16:04:33: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30554: 16:04:33: L2X: Rx Window Size 64
Feb 28 09:02:53 210.80.157.1 30555: 16:04:33: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:02:53 210.80.157.1 30556: 16:04:33: L2X: Chlng
Feb 28 09:02:53 210.80.157.1 30557: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:02:53 210.80.157.1 30558: 7F 34 58 93 68 4E 5A
Feb 28 09:02:53 210.80.157.1 30559: 16:04:33: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:02:53 210.80.157.1 30560: 16:04:33: L2X: Firmware Ver 0x1428
Feb 28 09:02:53 210.80.157.1 30561: 16:04:33: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:02:53 210.80.157.1 30562: 16:04:33: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:02:53 210.80.157.1 30563: 16:04:33: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:02:53 210.80.157.1 30564: 16:04:33: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:02:53 210.80.157.1 30565: 16:04:33: L2X: Ignoring unknown AVP 76
Feb 28 09:02:53 210.80.157.1 30566: 16:04:33: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:02:53 210.80.157.1 30567: 16:04:33: L2X: Ignoring unknown AVP 76
Feb 28 09:02:53 210.80.157.1 30568: 16:04:33: L2X: No missing AVPs in SCCRQ
Feb 28 09:02:53 210.80.157.1 30569: 16:04:33: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:02:53 210.80.157.1 30570: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:02:53 210.80.157.1 30571: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:02:53 210.80.157.1 30572: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:02:53 210.80.157.1 30573: 16:04:33: L2TP: I SCCRQ from
n2158726k-vez8 tnl 668
Feb 28 09:02:53 210.80.157.1 30574: 16:04:33: Tnl59502 L2TP: Got a
challenge in SCCRQ, nxxxxxxxxk-vez8
Feb 28 09:02:53 210.80.157.1 30575: 16:04:33: Tnl59502 L2TP: New
tunnel created for remote n2158726k-vez8, address 172.30.108.207
Feb 28 09:02:53 210.80.157.1 30576: 16:04:33: Tnl59502 L2TP: O SCCRP
to n2158726k-vez8 tnlid 668
Feb 28 09:02:53 210.80.157.1 30577: 16:04:33: Tnl59502 L2TP: O SCCRP,
flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:02:53 210.80.157.1 30578: C8 02 00 98 02 9C 00 00 00 00
00 01 80 08 00 00
Feb 28 09:02:53 210.80.157.1 30579: 00 00 00 02 80 08 00 00 00 02
01 00 80 0A 00 00
Feb 28 09:02:53 210.80.157.1 30580: 00 03 00 00 00 00 80 0A 00 00
00 04 00 00 00 ...
Feb 28 09:02:54 210.80.157.1 30581: 16:04:33: Tnl59502 L2TP: Control
channel retransmit delay set to 1 seconds
Feb 28 09:02:54 210.80.157.1 30582: 16:04:33: Tnl59502 L2TP: Tunnel
state change from idle to wait-ctl-reply
Feb 28 09:02:54 210.80.157.1 30583: 16:04:34: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:02:54 210.80.157.1 30584: 16:04:34: Tnl59502 L2TP: Control
channel retransmit delay set to 2 seconds
Feb 28 09:02:54 210.80.157.1 30585: 16:04:34: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30586: 16:04:34: L2X: Parse SCCRQ
Feb 28 09:02:54 210.80.157.1 30587: 16:04:34: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30588: 16:04:34: L2X: Protocol Ver 256
Feb 28 09:02:54 210.80.157.1 30589: 16:04:34: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30590: 16:04:34: L2X: Hostname nxxxxxxxk-vez8
Feb 28 09:02:54 210.80.157.1 30591: 16:04:34: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30592: 16:04:34: L2X: Framing Cap 0x1
Feb 28 09:02:54 210.80.157.1 30593: 16:04:34: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30594: 16:04:34: L2X: Assigned Tunnel ID 668
Feb 28 09:02:54 210.80.157.1 30595: 16:04:34: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30596: 16:04:34: L2X: Rx Window Size 64
Feb 28 09:02:54 210.80.157.1 30597: 16:04:34: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:02:54 210.80.157.1 30598: 16:04:34: L2X: Chlng
Feb 28 09:02:54 210.80.157.1 30599: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:02:54 210.80.157.1 30600: 7F 34 58 93 68 4E 5A
Feb 28 09:02:54 210.80.157.1 30601: 16:04:34: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:02:54 210.80.157.1 30602: 16:04:34: L2X: Firmware Ver 0x1428
Feb 28 09:02:54 210.80.157.1 30603: 16:04:34: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:02:54 210.80.157.1 30604: 16:04:34: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:02:54 210.80.157.1 30605: 16:04:34: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:02:54 210.80.157.1 30606: 16:04:34: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:02:54 210.80.157.1 30607: 16:04:34: L2X: Ignoring unknown AVP 76
Feb 28 09:02:54 210.80.157.1 30608: 16:04:34: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:02:54 210.80.157.1 30609: 16:04:34: L2X: Ignoring unknown AVP 76
Feb 28 09:02:54 210.80.157.1 30610: 16:04:34: L2X: No missing AVPs in SCCRQ
Feb 28 09:02:54 210.80.157.1 30611: 16:04:34: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:02:55 210.80.157.1 30612: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:02:55 210.80.157.1 30613: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:02:55 210.80.157.1 30614: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:02:55 210.80.157.1 30615: 16:04:34: L2TP: I SCCRQ from
nxxxxxxxk-vez8 tnl 668
Feb 28 09:02:56 210.80.157.1 30616: 16:04:36: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:02:56 210.80.157.1 30617: 16:04:36: Tnl59502 L2TP: Control
channel retransmit delay set to 4 seconds
Feb 28 09:02:56 210.80.157.1 30618: 16:04:37: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30619: 16:04:37: L2X: Parse SCCRQ
Feb 28 09:02:56 210.80.157.1 30620: 16:04:37: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30621: 16:04:37: L2X: Protocol Ver 256
Feb 28 09:02:56 210.80.157.1 30622: 16:04:37: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30623: 16:04:37: L2X: Hostname nxxxxxxxxk-vez8
Feb 28 09:02:56 210.80.157.1 30624: 16:04:37: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30625: 16:04:37: L2X: Framing Cap 0x1
Feb 28 09:02:56 210.80.157.1 30626: 16:04:37: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30627: 16:04:37: L2X: Assigned Tunnel ID 668
Feb 28 09:02:56 210.80.157.1 30628: 16:04:37: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30629: 16:04:37: L2X: Rx Window Size 64
Feb 28 09:02:56 210.80.157.1 30630: 16:04:37: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:02:56 210.80.157.1 30631: 16:04:37: L2X: Chlng
Feb 28 09:02:56 210.80.157.1 30632: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:02:56 210.80.157.1 30633: 7F 34 58 93 68 4E 5A
Feb 28 09:02:56 210.80.157.1 30634: 16:04:37: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:02:56 210.80.157.1 30635: 16:04:37: L2X: Firmware Ver 0x1428
Feb 28 09:02:56 210.80.157.1 30636: 16:04:37: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:02:56 210.80.157.1 30637: 16:04:37: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:02:56 210.80.157.1 30638: 16:04:37: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:02:56 210.80.157.1 30639: 16:04:37: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:02:56 210.80.157.1 30640: 16:04:37: L2X: Ignoring unknown AVP 76
Feb 28 09:02:56 210.80.157.1 30641: 16:04:37: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:02:56 210.80.157.1 30642: 16:04:37: L2X: Ignoring unknown AVP 76
Feb 28 09:02:56 210.80.157.1 30643: 16:04:37: L2X: No missing AVPs in SCCRQ
Feb 28 09:02:57 210.80.157.1 30644: 16:04:37: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:02:57 210.80.157.1 30645: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:02:57 210.80.157.1 30646: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:02:57 210.80.157.1 30647: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:02:57 210.80.157.1 30648: 16:04:37: L2TP: I SCCRQ from
nxxxxxxxxk-vez8 tnl 668
Feb 28 09:03:00 210.80.157.1 30649: 16:04:40: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:00 210.80.157.1 30650: 16:04:40: Tnl59502 L2TP: Control
channel retransmit delay set to 8 seconds
Feb 28 09:03:00 210.80.157.1 30651: 16:04:41: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30652: 16:04:41: L2X: Parse SCCRQ
Feb 28 09:03:00 210.80.157.1 30653: 16:04:41: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30654: 16:04:41: L2X: Protocol Ver 256
Feb 28 09:03:00 210.80.157.1 30655: 16:04:41: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30656: 16:04:41: L2X: Hostname nxxxxxxxxk-vez8
Feb 28 09:03:00 210.80.157.1 30657: 16:04:41: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30658: 16:04:41: L2X: Framing Cap 0x1
Feb 28 09:03:00 210.80.157.1 30659: 16:04:41: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30660: 16:04:41: L2X: Assigned Tunnel ID 668
Feb 28 09:03:00 210.80.157.1 30661: 16:04:41: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30662: 16:04:41: L2X: Rx Window Size 64
Feb 28 09:03:00 210.80.157.1 30663: 16:04:41: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:03:00 210.80.157.1 30664: 16:04:41: L2X: Chlng
Feb 28 09:03:00 210.80.157.1 30665: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:03:00 210.80.157.1 30666: 7F 34 58 93 68 4E 5A
Feb 28 09:03:00 210.80.157.1 30667: 16:04:41: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:03:00 210.80.157.1 30668: 16:04:41: L2X: Firmware Ver 0x1428
Feb 28 09:03:00 210.80.157.1 30669: 16:04:41: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:03:00 210.80.157.1 30670: 16:04:41: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:03:00 210.80.157.1 30671: 16:04:41: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:03:00 210.80.157.1 30672: 16:04:41: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:03:00 210.80.157.1 30673: 16:04:41: L2X: Ignoring unknown AVP 76
Feb 28 09:03:00 210.80.157.1 30674: 16:04:41: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:03:00 210.80.157.1 30675: 16:04:41: L2X: Ignoring unknown AVP 76
Feb 28 09:03:00 210.80.157.1 30676: 16:04:41: L2X: No missing AVPs in SCCRQ
Feb 28 09:03:01 210.80.157.1 30677: 16:04:41: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:03:01 210.80.157.1 30678: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:03:01 210.80.157.1 30679: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:03:01 210.80.157.1 30680: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:03:01 210.80.157.1 30681: 16:04:41: L2TP: I SCCRQ from
nxxxxxxxxk-vez8 tnl 668
Feb 28 09:03:08 210.80.157.1 30682: 16:04:48: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:08 210.80.157.1 30683: 16:04:49: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30684: 16:04:49: L2X: Parse SCCRQ
Feb 28 09:03:08 210.80.157.1 30685: 16:04:49: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30686: 16:04:49: L2X: Protocol Ver 256
Feb 28 09:03:08 210.80.157.1 30687: 16:04:49: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30688: 16:04:49: L2X: Hostname nxxxxxxxxxk-vez8
Feb 28 09:03:08 210.80.157.1 30689: 16:04:49: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30690: 16:04:49: L2X: Framing Cap 0x1
Feb 28 09:03:08 210.80.157.1 30691: 16:04:49: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30692: 16:04:49: L2X: Assigned Tunnel ID 668
Feb 28 09:03:08 210.80.157.1 30693: 16:04:49: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30694: 16:04:49: L2X: Rx Window Size 64
Feb 28 09:03:08 210.80.157.1 30695: 16:04:49: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:03:08 210.80.157.1 30696: 16:04:49: L2X: Chlng
Feb 28 09:03:08 210.80.157.1 30697: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:03:08 210.80.157.1 30698: 7F 34 58 93 68 4E 5A
Feb 28 09:03:08 210.80.157.1 30699: 16:04:49: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:03:08 210.80.157.1 30700: 16:04:49: L2X: Firmware Ver 0x1428
Feb 28 09:03:08 210.80.157.1 30701: 16:04:49: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:03:08 210.80.157.1 30702: 16:04:49: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:03:08 210.80.157.1 30703: 16:04:49: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:03:08 210.80.157.1 30704: 16:04:49: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:03:08 210.80.157.1 30705: 16:04:49: L2X: Ignoring unknown AVP 76
Feb 28 09:03:08 210.80.157.1 30706: 16:04:49: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:03:08 210.80.157.1 30707: 16:04:49: L2X: Ignoring unknown AVP 76
Feb 28 09:03:08 210.80.157.1 30708: 16:04:49: L2X: No missing AVPs in SCCRQ
Feb 28 09:03:08 210.80.157.1 30709: 16:04:49: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:03:09 210.80.157.1 30710: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:03:09 210.80.157.1 30711: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:03:09 210.80.157.1 30712: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:03:09 210.80.157.1 30713: 16:04:49: L2TP: I SCCRQ from
nxxxxxxxxk-vez8 tnl 668
Feb 28 09:03:17 210.80.157.1 30714: 16:04:56: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:24 210.80.157.1 30715: 16:05:04: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:24 210.80.157.1 30716: 16:05:05: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30717: 16:05:05: L2X: Parse SCCRQ
Feb 28 09:03:24 210.80.157.1 30718: 16:05:05: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30719: 16:05:05: L2X: Protocol Ver 256
Feb 28 09:03:24 210.80.157.1 30720: 16:05:05: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30721: 16:05:05: L2X: Hostname nxxxxxxxk-vez8
Feb 28 09:03:24 210.80.157.1 30722: 16:05:05: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30723: 16:05:05: L2X: Framing Cap 0x1
Feb 28 09:03:24 210.80.157.1 30724: 16:05:05: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30725: 16:05:05: L2X: Assigned Tunnel ID 668
Feb 28 09:03:24 210.80.157.1 30726: 16:05:05: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30727: 16:05:05: L2X: Rx Window Size 64
Feb 28 09:03:24 210.80.157.1 30728: 16:05:05: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:03:24 210.80.157.1 30729: 16:05:05: L2X: Chlng
Feb 28 09:03:24 210.80.157.1 30730: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:03:24 210.80.157.1 30731: 7F 34 58 93 68 4E 5A
Feb 28 09:03:24 210.80.157.1 30732: 16:05:05: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:03:24 210.80.157.1 30733: 16:05:05: L2X: Firmware Ver 0x1428
Feb 28 09:03:24 210.80.157.1 30734: 16:05:05: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:03:24 210.80.157.1 30735: 16:05:05: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:03:24 210.80.157.1 30736: 16:05:05: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:03:24 210.80.157.1 30737: 16:05:05: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:03:24 210.80.157.1 30738: 16:05:05: L2X: Ignoring unknown AVP 76
Feb 28 09:03:24 210.80.157.1 30739: 16:05:05: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:03:24 210.80.157.1 30740: 16:05:05: L2X: Ignoring unknown AVP 76
Feb 28 09:03:24 210.80.157.1 30741: 16:05:05: L2X: No missing AVPs in SCCRQ
Feb 28 09:03:24 210.80.157.1 30742: 16:05:05: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:03:25 210.80.157.1 30743: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:03:25 210.80.157.1 30744: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:03:25 210.80.157.1 30745: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:03:25 210.80.157.1 30746: 16:05:05: L2TP: I SCCRQ from
nxxxxxxxxxk-vez8 tnl 668
Feb 28 09:03:33 210.80.157.1 30747: 16:05:12: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:40 210.80.157.1 30748: 16:05:20: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:40 210.80.157.1 30749: 16:05:21: L2X: Parse AVP 0, len 8,
flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30750: 16:05:21: L2X: Parse SCCRQ
Feb 28 09:03:40 210.80.157.1 30751: 16:05:21: L2X: Parse AVP 2, len 8,
flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30752: 16:05:21: L2X: Protocol Ver 256
Feb 28 09:03:40 210.80.157.1 30753: 16:05:21: L2X: Parse AVP 7, len 20,
flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30754: 16:05:21: L2X: Hostname n2158726k-vez8
Feb 28 09:03:40 210.80.157.1 30755: 16:05:21: L2X: Parse AVP 3, len 10,
flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30756: 16:05:21: L2X: Framing Cap 0x1
Feb 28 09:03:40 210.80.157.1 30757: 16:05:21: L2X: Parse AVP 9, len 8,
flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30758: 16:05:21: L2X: Assigned Tunnel ID 668
Feb 28 09:03:40 210.80.157.1 30759: 16:05:21: L2X: Parse AVP 10, len 8,
flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30760: 16:05:21: L2X: Rx Window Size 64
Feb 28 09:03:40 210.80.157.1 30761: 16:05:21: L2X: Parse AVP 11, len
29, flag 0x8000 (M)
Feb 28 09:03:40 210.80.157.1 30762: 16:05:21: L2X: Chlng
Feb 28 09:03:40 210.80.157.1 30763: C5 A0 78 0E F2 39 21 08 C3 2E
9F F6 AE F6 EC 4B
Feb 28 09:03:40 210.80.157.1 30764: 7F 34 58 93 68 4E 5A
Feb 28 09:03:40 210.80.157.1 30765: 16:05:21: L2X: Parse AVP 6, len 8,
flag 0x0
Feb 28 09:03:40 210.80.157.1 30766: 16:05:21: L2X: Firmware Ver 0x1428
Feb 28 09:03:40 210.80.157.1 30767: 16:05:21: L2X: Parse AVP 8, len 28,
flag 0x0
Feb 28 09:03:40 210.80.157.1 30768: 16:05:21: L2X: Vendor Name Juniper
Networks, Inc.
Feb 28 09:03:40 210.80.157.1 30769: 16:05:21: L2X: Parse AVP 76, len
12, flag 0x0
Feb 28 09:03:40 210.80.157.1 30770: 16:05:21: L2X: Unknown AVP 76 in CM
SCCRQ
Feb 28 09:03:40 210.80.157.1 30771: 16:05:21: L2X: Ignoring unknown AVP 76
Feb 28 09:03:40 210.80.157.1 30772: 16:05:21: L2X: Unknown AVP found
during length verification. AVP is 76, vendor code is 0, len is 12
Feb 28 09:03:40 210.80.157.1 30773: 16:05:21: L2X: Ignoring unknown AVP 76
Feb 28 09:03:40 210.80.157.1 30774: 16:05:21: L2X: No missing AVPs in SCCRQ
Feb 28 09:03:40 210.80.157.1 30775: 16:05:21: L2X: I SCCRQ, flg TLS, ver
2, len 151, tnl 0, cl 0, ns 0, nr 0
Feb 28 09:03:41 210.80.157.1 30776: C8 02 00 97 00 00 00 00 00 00
00 00 80 08 00 00
Feb 28 09:03:41 210.80.157.1 30777: 00 00 00 01 80 08 00 00 00 02
01 00 80 14 00 00
Feb 28 09:03:41 210.80.157.1 30778: 00 07 6E 32 31 35 38 37 32 36
6B 2D 76 65 7A ...
Feb 28 09:03:41 210.80.157.1 30779: 16:05:21: L2TP: I SCCRQ from
nxxxxxxxk-vez8 tnl 668
Feb 28 09:03:49 210.80.157.1 30780: 16:05:28: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:03:57 210.80.157.1 30781: 16:05:36: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:05 210.80.157.1 30782: 16:05:44: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:13 210.80.157.1 30783: 16:05:52: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:21 210.80.157.1 30784: 16:06:00: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:29 210.80.157.1 30785: 16:06:08: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:37 210.80.157.1 30786: 16:06:16: Tnl59502 L2TP: O Resend
SCCRP, flg TLS, ver 2, len 152, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:45 210.80.157.1 30787: 16:06:24: Tnl59502 L2TP: O
StopCCN to nxxxxxxxxk-vez8 tnlid 668
Feb 28 09:04:45 210.80.157.1 30788: 16:06:24: Tnl59502 L2TP: O
StopCCN, flg TLS, ver 2, len 66, tnl 668, cl 0, ns 0, nr 1
Feb 28 09:04:45 210.80.157.1 30789: C8 02 00 42 02 9C 00 00 00 00
00 01 80 08 00 00
Feb 28 09:04:45 210.80.157.1 30790: 00 00 00 04 80 08 00 00 00 09
E8 6E 80 1E 00 00
Feb 28 09:04:45 210.80.157.1 30791: 00 01 00 02 00 06 54 6F 6F 20
6D 61 6E 79 20 ...
Feb 28 09:04:45 210.80.157.1 30792: 16:06:24: Tnl59502 L2TP: Tunnel
state change from wait-ctl-reply to shutting-down
Feb 28 09:04:50 210.80.157.1 30793: 16:06:29: Tnl59502 L2TP: Shutdown
tunnel
Feb 28 09:04:50 210.80.157.1 30794: 16:06:29: Tnl59502 L2TP: Tunnel
state change from shutting-down to idle

Thanks guys
phani.

cisco-bba-request@puck.nether.net wrote:

>Send cisco-bba mailing list submissions to
> cisco-bba@puck.nether.net
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://puck.nether.net/mailman/listinfo/cisco-bba
>or, via email, send a message with subject or body 'help' to
> cisco-bba-request@puck.nether.net
>
>You can reach the person managing the list at
> cisco-bba-owner@puck.nether.net
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of cisco-bba digest..."
>
>
>Today's Topics:
>
> 1. terminating l2 ADSL customers (Sunet Sysadmin)
> 2. Re: terminating l2 ADSL customers (Oliver Boehmer (oboehmer))
> 3. Re: terminating l2 ADSL customers (Stavros Patiniotis)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 27 Feb 2007 14:41:29 +1100
>From: Sunet Sysadmin <sysadmin@sunet.com.au>
>Subject: [cisco-bba] terminating l2 ADSL customers
>To: cisco-bba@puck.nether.net
>Message-ID: <45E3A869.3030801@sunet.com.au>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi ,
>I am using cisco 3660 router V-12.2 terminating DSL L2TP VPDN over ATM and
>freeradius.
>
>my configuration is as follows
>
>aaa authentication login default local
>aaa authentication ppp default if-needed group radius
>aaa authorization network default group radius
>aaa session-id common
>
>vpdn enable
>!
>vpdn-group 1
> accept-dialin
> protocol l2tp
> virtual-template 10
> terminate-from hostname 172.31.248.207
> lcp renegotiation always
> l2tp tunnel password 7 xxxxxxxxxxxxxxxxxxx
>!
>virtual-template 10 pre-clone 600
>
>interface Virtual-Template10
>mtu 1492
>ip unnumbered FastEthernet0/0.1
>ppp authentication chap pap
>
>this is my configuration to run l2 on ATM(AGVC).
>I can ping the LAC.
>
>1) do i need to create seperate VPDN-group for each LAC.
>2)People who maintainLAC(which is Telstra in this case) told me session is initiated at their end and they get vpdn service unavailable.
>
>when i start the debug for vpdn packets i don't see any thing.
>
>Where am i going wrong. can u please point me through the right direction.any help is much appreciated.
>
>
>cheers
>phani.
>
>
>
>
>
>
>
>
>
>
>------------------------------
>
>Message: 2
>Date: Tue, 27 Feb 2007 08:25:02 +0100
>From: "Oliver Boehmer \(oboehmer\)" <oboehmer@cisco.com>
>Subject: Re: [cisco-bba] terminating l2 ADSL customers
>To: "Sunet Sysadmin" <sysadmin@sunet.com.au>,
> <cisco-bba@puck.nether.net>
>Message-ID:
> <70B7A1CCBFA5C649BD562B6D9F7ED784034DE259@xmb-ams-333.emea.cisco.com>
>Content-Type: text/plain; charset="us-ascii"
>
>Sunet Sysadmin <> wrote on Tuesday, February 27, 2007 4:41 AM:
>
>
>
>> Hi ,
>>I am using cisco 3660 router V-12.2 terminating DSL L2TP VPDN over
>>ATM and
>>freeradius.
>>
>>my configuration is as follows
>>
>>aaa authentication login default local
>>aaa authentication ppp default if-needed group radius
>>aaa authorization network default group radius
>>aaa session-id common
>>
>>vpdn enable
>>!
>>vpdn-group 1
>> accept-dialin
>> protocol l2tp
>> virtual-template 10
>> terminate-from hostname 172.31.248.207
>> lcp renegotiation always
>> l2tp tunnel password 7 xxxxxxxxxxxxxxxxxxx
>>!
>>virtual-template 10 pre-clone 600
>>
>>interface Virtual-Template10
>>mtu 1492
>>ip unnumbered FastEthernet0/0.1
>>ppp authentication chap pap
>>
>>this is my configuration to run l2 on ATM(AGVC).
>>I can ping the LAC.
>>
>>1) do i need to create seperate VPDN-group for each LAC.
>>
>>
>
>No. Just agree with your partner (Telstra) on a tunnel name and
>reference this one in "terminate-from hostname <name>", see also below.
>
>
>
>>2)People who maintainLAC(which is Telstra in this case) told me
>>session is initiated at their end and they get vpdn service
>>unavailable.
>>
>>
>
>Right, you have "terminate-from hostname 172.31.248.207" configured, and
>IOS treats "172.31.248.207" as a literal name, not as an IP address. So
>please check with Telstra which tunnel name they use, and use this one
>in the vpdn-group..
>
>
>
>>when i start the debug for vpdn packets i don't see any thing.
>>
>>
>
>try "debug vpdn l2x-event" or "debug vpdn l2x-packet"..
>
> oli
>
>
>
>------------------------------
>
>Message: 3
>Date: Tue, 27 Feb 2007 18:04:14 +1030
>From: "Stavros Patiniotis" <stavros@staff.esc.net.au>
>Subject: Re: [cisco-bba] terminating l2 ADSL customers
>To: "'Sunet Sysadmin'" <sysadmin@sunet.com.au>,
> <cisco-bba@puck.nether.net>
>Message-ID: <0dea01c75a41$ae5b6db0$9f00000a@WKSTN10>
>Content-Type: text/plain; charset="us-ascii"
>
>
>Hi,
>
>
>
>>I am using cisco 3660 router V-12.2 terminating DSL L2TP VPDN
>>over ATM and
>>freeradius.
>>
>>
>
>Really breifly....
>
>
>
>> terminate-from hostname 172.31.248.207
>>
>>
>
>Remove this, as the tunnel may be setup from multiple points on Telstras
>network.
>
>Also try adding source-ip x.x.x.x toyou vpdn configuration to ensure you are
>using the right ip address to terminate the tunnel. This is the ip address
>that you have given to Telstra for your LNS.
>
>See how you go with that.
>
>Stav!
>
>
>
>------------------------------
>
>_______________________________________________
>cisco-bba mailing list
>cisco-bba@puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-bba
>
>
>End of cisco-bba Digest, Vol 45, Issue 5
>****************************************
>
>
_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba
Re: terminating l2 ADSL customers [ In reply to ]
stavros at staff
Feb 27, 2007, 2:39 PM
Post #5 of 6 (4980 views)
Permalink
Hi,

> Thanks guys for your suggestions. Know I can see vpdn traffic coming
> throw and the tunel is forming with a tunnel id but for some
> reason the
> tunnel is breaking up. this keeps looping . Can you please suggest me
> where i am going wrong or can u point me through the right direction.
> following is the debug information for debug l2x-event. Any
> help is much
> appreciated.

(I haven't closely analysed your debug)

Telstra's has configured to drop the tunnel if there are no active session
across it. So you may be bringing up a tunnel, by the initiation of a ppp
session, but because you are not authenticating successfully the tunnel is
torn down. Are you seeing the radius attempt to authenticate your session?
Try debugging some radius/aaa info. You should also note that it may take a
couple of simultaneous logins to bring the first session up, because the
tunnels seem to take a little while to become active.


Cheers,

Stavros Patiniotis
EscapeNet ~ 08 8292 5200


_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba
Re: terminating l2 ADSL customers [ In reply to ]
sysadmin at sunet
Feb 28, 2007, 1:32 PM
Post #6 of 6 (4984 views)
Permalink
Stavros Patiniotis wrote:

>Hi,
>
>
>
>>Thanks guys for your suggestions. Know I can see vpdn traffic coming
>>throw and the tunel is forming with a tunnel id but for some
>>reason the
>>tunnel is breaking up. this keeps looping . Can you please suggest me
>>where i am going wrong or can u point me through the right direction.
>>following is the debug information for debug l2x-event. Any
>>help is much
>>appreciated.
>>
>>
>
>(I haven't closely analysed your debug)
>
>Telstra's has configured to drop the tunnel if there are no active session
>across it. So you may be bringing up a tunnel, by the initiation of a ppp
>session, but because you are not authenticating successfully the tunnel is
>torn down. Are you seeing the radius attempt to authenticate your session?
>Try debugging some radius/aaa info. You should also note that it may take a
>couple of simultaneous logins to bring the first session up, because the
>tunnels seem to take a little while to become active.
>
>
>Cheers,
>
>Stavros Patiniotis
>EscapeNet ~ 08 8292 5200
>
>
>
Thanks guys got every thing working finally. i will post my
configuration steps soon here.
thanks again guys.

cheers
phani.
_______________________________________________
cisco-bba mailing list
cisco-bba@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-bba

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal