JN0-683: Data Center, Professional (JNCIP-DC)Demo

This is the classic EBGP IP-fabric problem where all leaf devices share the same autonomous system number. When a route originated by one leaf is relayed through the spine to another leaf, the receiving leaf sees its own AS in the AS_PATH and treats it as a loop, so the route is received but marked hidden and never installed. Two valid fixes are: on the receiving side, raise the permitted loop count with 'set routing-options autonomous-system <as> loops 2' (option C); or on the advertising/spine side, use 'as-override' so the neighbor's AS is replaced before advertisement, eliminating the perceived loop (option D). Option B (multipath multiple-as) only affects load balancing and does not un-hide the routes, and option A (next-hop self) addresses a different next-hop-reachability symptom.