Need Help With Verizon ATM Host and Remote T1 Cisco Configuration!

I don't think you'll be able to do ATM on a WIC-1DSU-T1.  You definitely have the encapsulation wrong with HDLC, but I doubt you'd be able to hack up a workable ATM solution on a TDM card.

And please enable ip route-cache (or ip route-cache cef if it'll take that form of the command).  Your router will thank you for it.

Thanks for the reply, I forgot to post that I solved the problem, and you are correct it could not be done with the equipment I had, I tried using DXI and every other thing only to find out that my telco provided the wrong equipment from the start.  A Cisco 2801 is unable to do ATM connections, for ATM the lower end products are Cisco 2600 series (with appropriate memory expansion), Cisco 2811, 3600 and others.  A 2801 cannot accept the AIM interface.

For future reference for those of you heading into ATM for the first time, I needed to connect ATM over T1 using Cisco equipment.  This requires 2 expansion parts VWIC-1MFT-T1 and AIM-ATM or as a bundle the package is known as AIM-ATM-1T1, a combo of the VWIC Card and AIM-ATM expansion board which is an internal router add-on board.  This applies to the 2620 and 2811 routers I had, and several other models.

Once you have these you will have a Controller T1 interface which you use Mode ATM AIM 0 this will provide an ATM interface on the router upon reboot (and the correct Cisco IOS pack, which varies from router to router).  On the ATM interface you can then use the same commands as on the host DS3! once I had this, the whole thing started to make sense.  For each PVC setup a .252 subnet, have the ip address of one side be the protocol ip address of the remote and vice-versa.  This creates a direct connection between sites.  Make sure encapsalation is the same on both sides, and that your telco has scrambling configured the same on all of their equipment.  At this point its very straight forward.

Here is a snip of the final config on one of the remotes.

!
interface ATM0/1/0
 no ip address
 no scrambling-payload
 no atm ilmi-keepalive
!
interface ATM0/1/0.1 point-to-point
 ip address 192.168.100.101 255.255.255.252
 pvc 1/32
  protocol ip 192.168.100.102 broadcast
  cbr 1536
  encapsulation aal5snap
 !

I still had tons of line errors until I issed the command CBR 1536 on the Host and Remote Interfaces (this tells the int to use maximum constant bit rate bandwidth of 1536 kbs - leaving room for overhead)  Of course this will vary depending on your connection.

Lesson learned, do not rely on your telco to get things right when ordering a network no matter how large.  Our config was 1 host and 9 remotes, over $200K per year for the telco and still my they left it up to me and my sales guy to get it straight.  (Their third party equipment vendor and installation service were the ones who sent the wrong equipment!)  I even had to beg for the settings on the telco side for the line coding, framing, cbr, scrambling etc.  It took over a week to get them to get me this info, and get it right (they had different settings on different switches :)

Thanks for your reply, although I solved the issue, I would be glad to award points if you could tell me what routing protocol you would recommend with a small sample snip.  My config is 9 remotes to 1 host, no internet, all internal private traffic, very very little traffic other than from point to point from the remotes to host and back.  i.e. remote office 3 does not talk to office 4, etc.

I use 192.168.x.x  1.x being the host and 2.x, 3.x etc being the remotes.  My current routes are simply all traffic for the lan side to the ATM subinterface for each remote, and on the remote side, a default route back to the host.

Host
  ip route 192.168.2.x 255.255.255.0 ATM1/0.33
  ip route 192.168.3.x 255.255.255.0 ATM1/0.34
  ip route 192.168.4.x 255.255.255.0 ATM1/0.35
Remote
  ip route 0.0.0.0 0.0.0.0 ATM1/0/1.1

Thanks again, what a relief it is to finally be up and running, definitely more involved than my previous network using frame relay over good old Serial T1.

Off-topic, but a smart "lesson learned for next time" is to put terms in the contract such that:

L1/2/3 provisioning information must be received by N days before go-live date.  For every day that provisioning information is delayed beyond this deadline, billing start will be delayed beyond circuit acceptance by an equivalent amount (i.e. if they're three days late in supplying info, you get three free days of service).

Services must be ready for acceptance by X.  If services are not ready, customer has the right to cancel any or all services at no penalty, or customer may accept an equivalent period of free service.

Issued resolved.  Please Close and Refund Points.

You should be able to do this yourself.