For iBGP number of peers (i.e. the number of BGP routers inside an AS), the only significant limiting factor is that iBGP peers must be fully meshed (N.B.: not directly interconnected! An iBGP peering can span all the hops you can fit into the IP TTL field) – because it is the only way for iBGP to prevent… Read More »
Apparently, there are several very distinct topics in routing which have the word “demand” in them. First, there is Cisco On-Demand Routing quasi-protocol, and then there are on-demand circuits which routing protocols must treat differently. Last but not least, the on-demand circuits are used for Routing Backup.
Internet Protocol Routing, nowadays commonly known as L3 Switching, is part of the process of forwarding an IP packet from Source to Destination. Interestingly, it happens more often then commonly understood: even on a common subnet we often need to make an IP routing decision.
In continuation of my last post, here I will write down about EIGRP operation a little mote. Packets On the wire, EIGRP is present with five types of packets: Hello and Acknowledgements (ACKs are just Hellos with the relevant bit set). They are the only EIGRP packets sent unreliably – that is, without acknowledgement. Any other packet must… Read More »
I’ve decided to listen to some advice and use blogging as a learning aid. And to begin with, I’d like to tackle on the subject of EIGRP. It’s no secret that EIGRP is Cisco’s beloved proprietary (it is published as an IETF draft, but apparently public version lacks a feature or two) routing protocol, and thus it is… Read More »