nanog mailing list archives
Re: ISP support for use of 4-byte ASNs in peering
From: Michael Hare <michael.hare () doit wisc edu>
Date: Tue, 09 Aug 2011 11:15:51 -0500
Granted I've never worked outside academia but the me3400 is otherwise a cost effective gig-e demarc for very simple bgp multihoming.
They have made a strategic decision to not implement a simple software update support RFC4893 [it has been 4 years] and to set an artificial price point on entry. Fine, that is their choice. There are other vendors offering 4 byte ASN in simliar products at or near this price point and we'll probably have to move to them.
-Michael On 8/9/2011 10:38 AM, Nick Hilliard wrote:
On 09/08/2011 15:45, Michael Hare wrote:While attempting to focus on ISPs there is still [unbelievably] a vendor support issue. You may consider this a procurement failure, but the fact remains that some products [Cisco me3400e] have yet to implement support.the me3400 is a metro core ethernet switch with L3 extensions. It's not intended as a border router. If you use the wrong tool for the job... Nick
Current thread:
- ISP support for use of 4-byte ASNs in peering John Curran (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Nick Hilliard (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Michael Hare (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Nick Hilliard (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Michael Hare (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Blake Dunlap (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Nick Hilliard (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Michael Hare (Aug 09)
- Re: ISP support for use of 4-byte ASNs in peering Nick Hilliard (Aug 09)