A network engineer is configuring a static route on a Cisco router interface connected to a broadcast multiaccess Ethernet network. If the engineer configures the command using only the egress interface (e.g., `ip route 10.20.30.0 255.255.255.0 GigabitEthernet0/0`) without specifying a next-hop IPv4 address, which network behavior or operational issue will occur?
- AThe router automatically assigns an administrative distance of 255 to the route, preventing it from being installed in the routing table.
- The router treats the destination subnet as directly connected and generates an ARP request for every destination IP address, leading to high CPU load and ARP table bloat.Answer
- CThe router drops incoming packets destined for 10.20.30.0/24 because static routes on Ethernet interfaces strictly mandate a recursive lookup using a loopback IP address.
- DThe static route functions identically to specifying a next-hop IPv4 address because Ethernet interfaces automatically resolve the next-hop MAC address using CDP.
Answer
The router treats the destination prefix as a directly connected subnet on the Ethernet segment and attempts to perform an ARP lookup for every host IP address in that destination network.
When an IPv4 static route on a broadcast multiaccess Ethernet interface specifies only the exit interface, Cisco IOS considers the destination prefix directly connected. Consequently, the router attempts to resolve the MAC address for every individual destination IP address in that subnet via ARP requests. This leads to severe ARP table growth, high CPU usage, and dependence on Proxy ARP.
Step-by-Step Solution
Key Concept
Static Route Exit Interface vs. Next-Hop IP on Multiaccess Broadcast Networks