[c-nsp] ATM PVC auto-provisioning

[Brian Lehigh]

Hello all,
Tomorrow morning I will be deploying a new router to handle our broadband
aggregation (7206 NPE-G1).  Currently, we create a subinterface for every
PVC and our configuration is obscenely large.  Additionally, we are always
fighting with the Telco to get PVC's provisioned correctly (i.e. Telco waits
until the last minute to create the PVC, etc).  I would like to implement
PVC auto-creation but would like to hear from the list if there are any
caveats, performance issues, etc. that I should take into consideration
before going this route.
 
Here's part of the config. that I plan to use:
 
-----------------------------------------------------
virtual-profile if-needed
virtual-profile virtual-template 1
vpdn enable
!
vpdn-group broadband-00
 accept-dialin
  protocol pppoe
  virtual-template 1
 !
!
!
!
vc-class atm pppoe
  protocol pppoe
  encapsulation aal5snap
  create on-demand
!
!
interface ATM3/0
 description ATM DS3 for DSL
 no ip address
 shutdown
 class-int pppoe
 atm scrambling cell-payload
 no atm ilmi-keepalive
!
!
interface Virtual-Template1
 mtu 1492
 ip unnumbered FastEthernet0/0
 no logging event link-status
 peer default ip address pool atm00pool
 ppp authentication pap
!
-----------------------------------------------------
 
Does this look like it should work?  Do any of you use this method for PVC
creation?  Also, what would you recommend for "idle-timeout" values?  I've
seen "idle-timeout 300 10" used.
Thanks,
 
-Brian