Jason Berenson wrote: > Greetings, > > We just got a new Covad DS3 and ordered an end T1 as frame relay. The > backhaul is ATM. Here's my network:
Covad will perform FRF ATM conversion for you. You just take the pvc and do your ip routing on it. Now if you want a multilink configuration, thats a bit different. This is the simplest way to do it CPE conf t int s0 no ip addr enc fra IETF frame-relay lmi-type ansi int s0.16 p ip address 10.3.4.210 255.255.255.252 frame-relay interface-dlci 16 ip route 0.0.0.0 0.0.0.0 s0.16 10.3.4.209 end CORE conf t int a3/0.70 p ip address 10.3.4.209 255.255.255.252 pvc 0/70 end > > customer (dlci 16 and 17) --> covad cloud --> atm switch (0/xxx) --> atm > switch (0/xxx) --> cisco 7206 (atm pvc) Why dlci 16 and 17? > > Here's what I did on the customer router: > > interface Serial0 > no ip address > encapsulation frame-relay IETF > no fair-queue > frame-relay lmi-type ansi > ! > interface Serial0.1 point-to-point > frame-relay interface-dlci 17 ppp Virtual-Template17 Why are you bothering with ppp? > ! > interface Virtual-Template17 > ip address 10.3.4.210 255.255.255.252 > ! > > Here's the core: > > interface ATM3/0.26 point-to-point > pvc 0/70 > ip addr inarp > protocol ppp Virtual-Template1000 > ! > interface Virtual-Template1000 > ip address 10.3.4.209 255.255.255.252 Why are you bothering with ppp? Just put the IP address on the subinterface. > ! > > I'm not sure if this is going to work yet. Has anyone done this > before? If so, does this look right? > > Thanks, > Jason Its fairly common. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
