nanog mailing list archives
Re: Cost per prefix [was: request for help w/ ATT and terminology]
From: Joe Greco <jgreco () ns sol net>
Date: Mon, 21 Jan 2008 16:56:24 -0600 (CST)
On Mon, 21 Jan 2008, Joe Greco wrote:Given that the 3750 is not acceptable, then what exactly would you propose for a 48 port multigigabit router, capable of wirespeed, that does /not/ hold a 300K+ prefix table? All we need is a model number and a price, and then we can substitute it into the pricing questions previously posed. If you disagree that the 7600/3bxl is a good choice for the fully-capable router, feel free to change that too. I don't really care, I just want to see the cost difference between DFZ-capable and non-DFZ-capable on stuff that have similar features in other ways.If using the 7600/3bxl as the cost basis of "the upgrade", you might as well compare it to the 6500/7600/sup2 or sup3b. Either of these would likely be what people buying the 3bxls are upgrading from, in some cases just because of DFZ growth/bloat, in others, to get additional features (IPv6).
I see a minor problem with that in that if I don't actually need a chassis as large as the 6500/sup2, there's a bit of a hefty jump to get to that platform from potentially reasonable lesser platforms. If you're upgrading, though, it's essentially a discard of the sup2 (because you lose access to the chassis), so it may be fair to count the entire cost of the sup720-3bxl. Punching in 720-3bxl to Froogle comes up with $29K. Since there are other costs that may be associated with the upgrade (daughterboards, incompatible line cards, etc), let's just pretend $30K is a reasonable figure, unless someone else has Figures To Share. ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "We call it the 'one bite at the apple' rule. Give me one chance [and] then I won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN) With 24 million small businesses in the US alone, that's way too many apples.
Current thread:
- Re: Cost per prefix [was: request for help w/ ATT and terminology], (continued)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Patrick W. Gilmore (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] William Herrin (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Patrick W. Gilmore (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] William Herrin (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Patrick W. Gilmore (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] William Herrin (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Patrick W. Gilmore (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] William Herrin (Jan 20)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Joe Greco (Jan 21)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Jon Lewis (Jan 21)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Joe Greco (Jan 21)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] David Barak (Jan 21)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Patrick W. Gilmore (Jan 22)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Joe Greco (Jan 22)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] William Herrin (Jan 22)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Bill Woodcock (Jan 22)
- RE: Cost per prefix [was: request for help w/ ATT and terminology] andrew2 (Jan 22)
- RE: Cost per prefix [was: request for help w/ ATT and terminology] Michael K. Smith - Adhost (Jan 22)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Andy Davidson (Jan 23)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Mikael Abrahamsson (Jan 23)
- Re: Cost per prefix [was: request for help w/ ATT and terminology] Paul Vixie (Jan 23)