From: Fabrice Bobes (study@6colabs.com)
Date: Mon Jan 12 2004 - 03:08:22 GMT-3
Hi Guys,
This is something I tried recently between 2 routers running 12.2T.
To get the SVC up, I had to add a static mapping on the router
initiating the call (see config below). If I reload, the static mapping
disappears though so it doesn't seem like a supported feature or may be,
I just didn't get the config right (not an expert on PPP over ATM over
SVC, never tried that before).
Here is what I got:
R13(initiates call)--ATM Switch--(called side)R14
R13:
interface ATM2/0
ip address 133.1.34.13 255.255.255.252
atm nsap-address 47.009181000000123456781234.131313131313.00
no atm ilmi-keepalive
pvc 0/5 qsaal
!
pvc 0/16 ilmi
!
svc ppp nsap 47.009181000000123456781234.141414141414.00
encapsulation aal5auto
protocol ppp Virtual-Template1
!
interface Virtual-Template1
ip unnumbered ATM2/0
R14:
interface Loopback14
ip address 133.1.34.14 255.255.255.252
!
interface ATM2/0
no ip address
atm nsap-address 47.009181000000123456781234.141414141414.00
no atm ilmi-keepalive
pvc 0/5 qsaal
!
pvc 0/16 ilmi
!
svc ppp
encapsulation aal5auto
protocol ppp Virtual-Template1
!
interface Virtual-Template1
ip unnumbered Loopback14
Test:
R13#debug atm err
ATM errors debugging is on
R13#debug atm eve
ATM events debugging is on
R13#ping 133.1.34.14
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 133.1.34.14, timeout is 2 seconds:
*Mar 1 00:01:41.819: ATM(ATM2/0): Encapsulation error1, link=7,
host=8501220E.
*Mar 1 00:01:43.815: ATM(ATM2/0): Encapsulation error1, link=7,
host=8501220E.
*Mar 1 00:01:45.815: ATM(ATM2/0): Encapsulation error1, link=7,
host=8501220E.
*Mar 1 00:01:47.815: ATM(ATM2/0): Encapsulation error1, link=7,
host=8501220E.
*Mar 1 00:01:49.815: ATM(ATM2/0): Encapsulation error1, link=7,
host=8501220E.
Success rate is 0 percent (0/5)
=> I added a static mapping:
R13(config)#int atm 2/0
R13(config-if)#svc ppp nsap 47.009181000000123456781234.141414141414.00
R13(config-if-atm-vc)#protocol ip 133.1.34.14 br
R13(config-if-atm-vc)#^Z
R13#ping 133.1.34.14
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 133.1.34.14, timeout is 2 seconds:
*Mar 1 00:02:42.039: %SYS-5-CONFIG_I: Configured from console by
console
*Mar 1 00:02:43.567: atm_kbps_to_cps: 149760 kbps to 353208 cps
*Mar 1 00:02:43.567: atm_kbps_to_cps: 149760 kbps to 353208 cps
*Mar 1 00:02:43.567: atm_cps_to_kbps: 353208 cps to 149760 kbps
*Mar 1 00:02:43.567: atm_cps_to_kbps: 353208 cps to 149760 kbps
*Mar 1 00:02:43.567: Reserved bw for 0/0 Available bw = 155000
*Mar 1 00:02:43.587: atm_cps_to_kbps: 353208 cps to 149760 kbps
*Mar 1 00:02:43.587: atm_cps_to_kbps: 353208 cps to 149760 kbps
*Mar 1 00:02:43.587: ATM2/0: vc 0/148 - enable idle timer
*Mar 1 00:02:43.587: ATM2/0: vc 0/148 - start idle timer 300 sec,
*Mar 1 00:02:43.587: rs8234_setup_vc(ATM2/0): vc:3 vpi:0 vci:148
*Mar 1 00:02:43.587: peak rate configured is 155000000
*Mar 1 00:02:43.591: rs8234_setup_vc_common() VCD=3 vp/vc=0/148 etype=0
*Mar 1 00:02:43.591: rs8234_open_connection_seg
*Mar 1 00:02:43.591: vcd:3
*Mar 1 00:02:43.591: vcc_id:102
*Mar 1 00:02:43.591: ds->p_vcd_table[ccb_ptr->vcd].host_vccid:102
*Mar 1 00:02:43.591: ccb_ptr->av_bit_rate:0
*Mar 1 00:02:43.591: ccb_ptr->cdvt:0
*Mar 1 00:02:43.591: ccb_ptr->peak_bit_rate:148772272
*Mar 1 00:02:43.591: p_host_seg_vc_table:0x6368BF38:
*Mar 1 00:02:43.591: aal type word value 0x80100080.
*Mar 1 00:02:43.591: rs8234_setup_cos(ATM2/0): vc:3 wred_name:- max_q:0
*Mar 1 00:02:43.635: ATM(ATM2/0): vcd-3/vpi-0/vci-148 making cktid
request vc_info..
*Mar 1 00:02:45.567: ATMSM(ATM2/0): Attaching to VC #3 for type 1
traffic.!!!
Success rate is 60 percent (3/5), round-trip min/avg/max = 1/2/4 ms
R13#
R13#sh atm svc ppp
VCD / VA Peak Avg/Min
Burst VC
ATM Int. Name VPI VCI Type VA St SC Kbps Kbps
Cells St
2/0 ppp 0 138 SVC 2.1 UP UBR 155000
UP
R14#sh atm svc ppp
VCD / VA Peak Avg/Min
Burst VC
ATM Int. Name VPI VCI Type VA St SC Kbps Kbps
Cells St
2/0 10 0 71 SVC 2.1 UP UBR 155000
UP
R14#sh atm svc 0/71
ATM2/0: VCD: 10, VPI: 0, VCI: 71
UBR, PeakRate: 155000
AAL5-LLC/SNAP, etype:0x0, Flags: 0x40, VCmode: 0x0, OAM retry frequency:
0 second(s)
--- removed ----
Status: UP
TTL: 3
interface = ATM2/0, call remotely initiated, call reference = 8388783
vcnum = 10, vpi = 0, vci = 71, state = Active(U10)
, point-to-point call
Retry count: Current = 0
timer currently inactive, timer value = 00:00:00
Remote Atm Nsap address: 47.009181000000123456781234.131313131313.00
, VC owner:
PPP: Virtual-Access2.1 from Virtual-Template1
PPPoA Current State = PTA
PPPoA Latest Event = Vaccess Up
PPPoA Latest Error = None
PPPoA Session ID = 8
PPPoA Handle = 0x97000007, SSS Handle = 0xCC00000E
Not sure if this helps but I thought you may want to reproduce this on
your racks,
Thanks,
Fabrice Bobes, #8609 (Security, R&S)
http://www.6CoLabs.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
John Matijevic
Sent: Sunday, January 11, 2004 8:04 PM
To: Brian Dennis; ccielab@groupstudy.com
Subject: Re: ATM PPP OVER SVC
Thanks Again Brian,
I was just hoping to see it work. Thanks again for your information.
Sincerely,
John
----- Original Message -----
From: "Brian Dennis" <bdennis@internetworkexpert.com>
To: "'John Matijevic'" <matijevi@bellsouth.net>;
<ccielab@groupstudy.com>
Sent: Sunday, January 11, 2004 9:55 PM
Subject: RE: ATM PPP OVER SVC
> John,
> You will not find a working configuration between two Cisco routers
> because the routers can not initiate a connection between them using
PPP
> over ATM SVCs. The routers will never try to setup the SVC when using
PPP
> over ATM SVC as of IOS 12.2T. This is what the restriction means in
the
> release notes by "does not support PPP over ATM SVC dialout". PPP
over
ATM
> SVC can only be used on a Cisco router as a 'receive only'
configuration.
> The router can not initiate the connection (SVC) itself.
>
> If you want to try it for yourself, configure an ATM SVC between two
> routers. Ping across to make sure that it works. Then add the PPP
related
> configuration (virtual-template, aal5auto encapsulation, move the IP
address
> to virtual-template, etc) and then try to ping. You won't be able to
ping
> because the routers will never attempt to setup the SVC as per the
> restriction of not supporting dialout. Dialout translates to not
being
able
> to initiate the SVC connection. If the routers can not initiate the
SVC
> setup, they will never be able to connect.
>
> Are you by chance looking for a configuration between a DSL modem
> and a Cisco router? If so the Cisco router configuration in the link
below
> will work.
>
>
http://www.cisco.com/en/US/products/sw/iosswrel/ps1834/products_feature_
guid
> e09186a0080080295.html
>
> Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> bdennis@internetworkexpert.com
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Direct: 775-745-6404 (Outside the US and Canada)
>
>
> -----Original Message-----
> From: John Matijevic [mailto:matijevi@bellsouth.net]
> Sent: Sunday, January 11, 2004 6:28 PM
> To: Brian Dennis; ccielab@groupstudy.com
> Subject: Re: ATM PPP OVER SVC
>
> Thanks Brian,
> Thats great, however, I am looking for a working configuration, or if
> someone has implemented before to please post configuration that
worked
for
> him/her.
> Sincerley,
> Matijevic
> ----- Original Message -----
> From: "Brian Dennis" <bdennis@internetworkexpert.com>
> To: "'John Matijevic'" <matijevi@bellsouth.net>;
<ccielab@groupstudy.com>
> Sent: Sunday, January 11, 2004 6:10 PM
> Subject: RE: ATM PPP OVER SVC
>
>
> > Here are the restrictions for this feature:
> >
> > Restrictions
> > The PPP over ATM SVCs feature does not support PPP over ATM SVC
dialout
> > mode.
> >
> >
>
http://www.cisco.com/en/US/products/sw/iosswrel/ps1834/products_feature_
guid
> > e09186a0080080295.html#1015337
> >
> > Before implementing a feature or technology, it is important to look
for
> any
> > requirements and/or restrictions listed in the documentation. In
this
> case,
> > the restriction is that a router can not be used to initiate the
SVC.
> >
> > Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
> > bdennis@internetworkexpert.com
> > Internetwork Expert, Inc.
> > http://www.InternetworkExpert.com
> > Toll Free: 877-224-8987
> > Direct: 775-745-6404 (Outside the US and Canada)
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> John
> > Matijevic
> > Sent: Sunday, January 11, 2004 2:52 PM
> > To: asadovnikov; 'Kaiser Anwar'; ccielab@groupstudy.com
> > Subject: Re: ATM PPP OVER SVC
> >
> > Hello Alexi,
> > I tried to test your command over the weekend and was not able to
get
ppp
> > over svc to work. Specifically I had problem with the following:
> > svc ppp-call nsap BC.CDEF01234567890ABCDEF012.345678901334.13
> > encapsulation aal5mux ppp virtual-template 1
> >
> > I could enter the svc command but underneath it,
> > I could not set the encapsulation to ppp in otherwords I got as far
as
> > encapsulation aal5mux, then I did not have option for PPP.
> > If anyone has gotten this to work with SVC, I would like to know. I
have
> > tried via doccd, configuration and cisco.com, but with no success.
> > Also, I got this to work with PVC no problem.
> > Sincerley,
> > John
> > ----- Original Message -----
> > From: "asadovnikov" <asadovnikov@comcast.net>
> > To: "'Kaiser Anwar'" <kaiseranwar@sbcglobal.net>;
<ccielab@groupstudy.com>
> > Sent: Thursday, December 25, 2003 7:58 PM
> > Subject: RE: ATM PPP OVER SVC
> >
> >
> > > The configuration you provided will accept SVC calls, but not
initiate
> > them.
> > > If you use this configuration you need to configure another side
such
as
> > it
> > > will initiate SVC call to this router, i.e. specify the NSAP
address
of
> > this
> > > router under SVC of another one. Here is an example (I have not
tried
> it
> > > before posting though):
> > >
> > > On another router...
> > >
> > > interface Loopback0
> > > ip address 192.168.2.1 255.255.255.0
> > > !
> > > interface ATM0/0
> > > no ip address
> > > atm nsap-address BC.CDEF01234567890ABCDEF012.345678901300.00
> > > no atm ilmi-keepalive
> > > pvc 0/5 qsaal
> > > !
> > > pvc 0/16 ilmi
> > > !
> > > svc ppp-call nsap BC.CDEF01234567890ABCDEF012.345678901334.13
> > > encapsulation aal5mux ppp virtual-template 1
> > > !
> > > interface Virtual-Template1
> > > ip unnumbered Loopback0
> > > !
> > >
> > > You would obviously need to configure NSAP addresses in accordance
with
> > what
> > > you got on the switch.
> > >
> > > Best regards,
> > > Alexei
> > >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf
Of
> > > Kaiser Anwar
> > > Sent: Wednesday, December 24, 2003 12:58 AM
> > > To: ccielab@groupstudy.com
> > > Subject: ATM PPP OVER SVC
> > >
> > >
> > > HI,
> > > I have a config here, according to the doc cd I am not missing
anything
> > but
> > > it is not working. here is the config. I am using pvc 0/5 qsaal
and
0/16
> > > ilmi. they are not in the doc cd. but I tried it without them
too.it
> does
> > > not say to statically map it. thanks in advance.
> > >
> > > interface Loopback0
> > > ip address 192.168.1.1 255.255.255.0
> > > interface ATM0/0
> > > no ip address
> > > atm nsap-address BC.CDEF01234567890ABCDEF012.345678901334.13
> > > no atm ilmi-keepalive
> > > pvc 0/5 qsaal
> > > !
> > > pvc 0/16 ilmi
> > > !
> > > svc ppp
> > > encapsulation aal5auto
> > > protocol ppp Virtual-Template1
> > >
> > > interface Virtual-Template1
> > > ip unnumbered Loopback0
> > >
> > >
> > > Sincerely,
> > > Kaiser Anwar
> > >
> > >
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:39 GMT-3