 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
10 messages in net.nether.puck.cisco-nsp[c-nsp] RIP offset lists| From | Sent On | Attachments |
|---|---|---|
| Joe Maimon | Jan 20, 2005 7:05 am | |
| Rodney Dunn | Jan 20, 2005 9:21 am | |
| David Barak | Jan 20, 2005 10:22 am | |
| Joe Maimon | Jan 20, 2005 10:58 am | |
| Joe Maimon | Jan 20, 2005 11:01 am | |
| Rodney Dunn | Jan 20, 2005 11:26 am | |
| David Barak | Jan 20, 2005 11:46 am | |
| Joe Maimon | Jan 20, 2005 2:16 pm | |
| Joe Maimon | Jan 20, 2005 2:21 pm | |
| Hudson Delbert J Contr 61 CS/SCBN | Jan 20, 2005 3:29 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [c-nsp] RIP offset lists | Actions... |
|---|---|---|
| From: | Joe Maimon (jmai...@ttec.com) | |
| Date: | Jan 20, 2005 10:58:26 am | |
| List: | net.nether.puck.cisco-nsp | |
David Barak wrote:
--- Joe Maimon <jmaimon at ttec.com> wrote:
<many very good questions regarding RIP capabiliities snipped>
My primary question before delving into solving the mysteries is this: are you running RIP between your provider network and the customer network, and if so, why?
Often. Because thats what the customer's gear supports and it happens to be trivial to manage for those cases. What would you run? OSPF? Cisco proprietary EIGRP? BGP?
What routing protocols can you run on a pppoe l2tp VA link that can be managed from AAA attrs?
Assertions: If a customer is multihomed, the $40 linksys is no longer the appropriate CPE device (clearly multihoming is for resiliency, and the linksys is not exactly what we'd call "high-availability" ;)
Yes but the customer now believes that 2 $40 linksys routers are perfectly appropriate. After all, they can reboot them themselves.
Sure I would like to sell them the 1721 but that often as not does not happen. If you dont want those customers and I dont want those customers, that makes no never mind to management. Its always "can it work? Yes? So what if its not the right way? Do it anyways! Its a recurring revenue stream!"
The first question a customer asks after hearing what a 1721 with a WIC-1E and a WIC-T1 costs (with upgrades to run new IOS with features such as firewalling) are "can you do it cheaper with x or y, and if not explain it in writing?"
If a customer is singly-homed, why not statically route them? Let the routing protocol they run be exclusive to their network.
Mostly this is what we do. Sometimes we even do that with two links to the same router, but then again thats a cisco thing that makes that work.
If they're trying to do some kind of load-balancing or failover mechanism, get them to use something other than Layer-3 resiliency (perhaps layer-7 resiliency?)
Back to the $$ again. Such as a 1721/2620XM with 12.3(8)T or higher. Maybe they could just run a script on every computer that pings google and on failure changes their default gateway to their other NAT box, but I sure as heck dont want to support that.
So, while the problems Cisco has with RIPv2 are non-trivial, why are they impacting a production network?
Because of the gear thats in use, mostly the Customers gear which has a different budget approval process than mine.
-David
=====
Joe