I was under the impression Cogent no longer did the multi-hop BGP thing,
but then I got a copy of their NA user guide, and saw the peer-a/peer-b
configuration. Not a fan.
Anyone know if this is still required for Cogent IP transit service?
(on/off list is fine.)
depends on the site.
in st. louis, we connect to their only router, direct peering, no a/b/ stuff, if you are in a colo that they have several access routers as well, then you will typically do the a/b.
Dennis Burgess, Mikrotik Certified Trainer Author of "Learn RouterOS- Second Edition"
Link Technologies, Inc -- Mikrotik & WISP Support Services
Office: 314-735-0270 Website: http://www.linktechs.net - Skype: linktechs
-- Create Wireless Coverage's with www.towercoverage.com - 900Mhz - LTE - 3G - 3.65 - TV Whitespace
If you mean required in order to load share over multiple circuits, no. They support LAG in most places now and LAG is their preferred method for load sharing over multiple links.
For what it's worth, we started with Cogent doing the A/B peer thing when we were running IPv4 only with them. Once we added IPv6 BGP they migrated us to a direct peering. Much simpler and preferred. This is in Chicago at 710 Lakeshore.
Ryan Wilkins
As an update to interested parties: I have been informed that Cogent no
longer do the A/B peer config. This is a documentation bug apparently.
Tim Durack wrote:
I was under the impression Cogent no longer did the multi-hop BGP thing,
but then I got a copy of their NA user guide, and saw the peer-a/peer-b
configuration. Not a fan.Anyone know if this is still required for Cogent IP transit service?
(on/off list is fine.)
A/B multihop has plenty of good points. I would not mind it being a more widely available deployment option.
B does not have to be your edge device.
Joe