Question 790
An IRB interface is present but an operator assumes it creates a bridge domain automatically. What diagnosis and engineering response are most appropriate?
Explanation
Correct Answer
This is the model-intended best choice because integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. The targeted correction is to verify VLAN or bridge-domain membership and its L3 IRB binding. Validate it by observing that the bridge domain and IRB interface share the configured gateway context.
Incorrect Answers
Check whether GRES is paired with the intended GR or NSR support and verify protocol state is a relevant step for the separate scenario in which a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. It does not directly fix this case. Instead verify VLAN or bridge-domain membership and its L3 IRB binding; verify: The bridge domain and IRB interface share the configured gateway context.
The alternative addresses a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, not the present root cause. Here the selected correction must reflect integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Test for: The bridge domain and IRB interface share the configured gateway context.
This answer would be more suitable when a virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed, where the corrective action is to compare candidate and committed configurations and confirm actual bridge membership. The failure here is different: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Required validation: The bridge domain and IRB interface share the configured gateway context.