Network in which AS 17 has two separate confederations: sub-AS 64512Īnd sub-AS 64513, each of which has multiple routers. Uses only the privately assigned sub-AS numbers. Uses a confederation sequence, which operates like an AS path but To other confederations are made with standard EBGP, and peers outside Within a sub-AS, the same IBGP full mesh requirement exists. Numbers are taken from the private AS numbers between 6455. Within the confederation AS by a sub-AS number. BGP confederations effectively break up a largeĪS into subautonomous systems. Is one method used to solve the scaling problems created by the IBGPįull mesh requirement. To maintain connections between IBGP routing devices. Member autonomous systems (ASs) must be external BGP (EBGP) links,īGP confederations reduce the number of peer sessions and TCP sessions Within a BGP confederation, the links between the confederation Is advertised out of the confederation AS. The sub-AS numbers are removed when the route It does not include the confederation sequence or the privatelyĪssigned sub-AS numbers. The AS path received by other ASs shows only the globally assignedĪS number. The confederation AS appears whole to other confederation ASs.
Operates like an AS path but uses only the privately assigned sub-AS To avoid routing loops, a sub-AS uses a confederation sequence, which Connections to other confederations are made with standardĮxternal BGP (EBGP), and peers outside the sub-AS are treated as external. Within a sub-AS, the same internal BGP (IBGP) full mesh requirementĮxists. Private AS numbers between 64,512 and 65,535. Typically, sub-AS numbers are taken from the Each sub-AS must be uniquely identified within the confederationĪS by a sub-AS number. BGP confederations effectivelyīreak up a large autonomous system (AS) into subautonomous systems
BGP confederations are another way to solve the scaling problemsĬreated by the BGP full mesh requirement.
0 kommentar(er)
