Can I ask, what is the compelling reason for you to do this? The CAS is an appliance, designed to perform a specific function in the NAC deployment. While it might be able to function as a router, you will now be asking the appliance to perform a function other than the one for which it was originally intended, and deployed. The appliance now will have to maintain a routing table, and a link table, and depending upon the size of such tables, may consume additional resources (memory/CPU) within the appliance - a resource utilization increase that wasn't accounted for when the appliance was spec'd/sized. Furthermore, you have added complexity to troubleshooting of any issues on the device, as the device is now serving an ancilliary function as well as the one for which it was intended. rebooting an appliance in the course is one thing. With what you are proposing to do, every time you need to do maintenance on the CAS, you will also be doing maintenance on a router.
Let a router perform this function if at all possible. On Wed, Oct 29, 2008 at 3:27 PM, Miles, Shane <[EMAIL PROTECTED]> wrote: > Before I go cabling it up, does anyone see a problem with me running > EIGRP through a VG CAS? I can't imagine why it wouldn't work but I've seen > too many unimaginable things happen since I entered this NAC world. Thanks. > > -- > Shane > > > -- To him who is able to keep you from falling and to present you before his glorious presence without fault and with great joy
