DR and BDR selection Lab

at

 #ospf #protocol #configuration #lab #DR #BDR


Lab objectives:

Ensure router R1 is the DR for network 100.1.1.0 /24.

Ensure router R3 is the BDR for network 100.1.1.0 /24.

Ensure router R5 is the DR for network 100.1.2.0 /24. without changing the priority

Ensure router R2 is the BDR for network 100.1.2.0 /24. You are not allowed to change the priority.


Solution configurations:

R1:

conf t

int fa 0/0

ip address 100.1.1.2 255.255.255.0

no shutdown

exit

router ospf 10

network 100.1.1.0 0.0.0.255 area 0

network 100.1.2.0 0.0.0.255 area 0

log-adjacency-changes

conf t

router ospf 10

log-adjacency-changes

exit

exit


R2:



























































the solution to achieve all objectives:

change priority of R1 must be higher than R3

change priority of R2 must be lower than R1

change router-id manually to higher router ID 120.120.120.2 




Labels:

Featured Post

Day 41 — BGP Confederations: Sub-AS Design, External View and Migration

1. Opening Confederations are another way to scale BGP inside a large administrative domain. They divide the domain into member autonomous systems while presenting a single confederation identifier to external peers. They are powerful, but their operational model is more complex than simply 'using private ASNs inside.' The engineering goal is not to memorize another BGP command. It is to understand what information each speaker is allowed to propagate, what path information can be hidden, and what failure domain is created by the chosen control-plane architecture . 2. Concept and standards behavior RFC 5065 defines AS_CONFED_SEQUENCE and AS_CONFED_SET and how member-AS relationships are represented. Confederation external sessions have eBGP-like properties inside the confederation, while the confederation is presented externally as one AS. Modern guidance must also account for the fact that RFC 9774 prohibits new origination of AS_SET/AS_CONFED_SET in ordinary aggregation c...