Re: Distributed Router Fabrics

[Mike Hammett <nanog () ics-il net>]

*nods* Yeah, I knew that's how a traditional chassis worked. In a distributed setup, you have the option for a single 
"line card", which obviously doesn't happen in the traditional chassis world. 




I do see in a DDCv2 document where they briefly mention 2 compute boxes, so now that makes sense. I had to look up some 
of the acronyms because the document didn't define them within itself. 




----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Randy Bush" <randy () psg com> 
To: "Mike Hammett" <nanog () ics-il net> 
Cc: "NANOG" <nanog () nanog org> 
Sent: Thursday, December 26, 2024 4:51:45 PM 
Subject: Re: Distributed Router Fabrics 

> > In a distributed fabric, where is the traditional control plane run? 
> > Say I've got 100 BGP sessions of upstream,peer, and downstream across 
> > ten routers. Is each pizza box grinding this out on its own, or is the 
> > work done on the x86 box mentioned in the larger installations? 
>
> one way to think of it is that each pizza box (customer facing ports) 
> recognizes control plane messages (e.g. port 179) and "punts" them to 
> the control plane box, aka routing engine. 

fwiw, that is pretty much what line cards on a big-box fabric do, punt 
to the RE. 

randy