A network engineer is configuring an IPv4 static route on router HQ to reach the destination subnet . Router HQ connects to the next-hop router over an Ethernet broadcast multi-access segment via interface GigabitEthernet0/1. The engineer enters the command `ip route 172.16.40.0 255.255.255.0 GigabitEthernet0/1` without specifying the next-hop IP address. Which operational issue will occur on router HQ as a result of configuring only the exit interface on a multi-access link?
- The router treats the destination network as directly connected and sends an ARP request for every destination IP address in the 172.16.40.0/24 subnet, causing ARP table bloat and performance degradation.Cevap
- BThe router assigns an administrative distance of 255 to the route, rendering it unusable and removing it from the IPv4 routing table.
- CThe route is rejected by Cisco IOS syntax validation because an administrative distance value is required whenever an interface parameter is used.
- DThe router drops packets matching the route because recursive lookup logic is automatically disabled on Layer 3 GigabitEthernet interfaces.
Cevap
The router treats the destination network as directly connected and sends an ARP request for every destination IP address in the 172.16.40.0/24 subnet, causing ARP table bloat and performance degradation.
Specifying only an exit interface on a broadcast multi-access link (like Ethernet) causes the router to treat the remote prefix as directly connected. When forwarding traffic, the router issues an ARP request for every individual destination IP within that prefix. This relies heavily on proxy ARP from the next-hop router, causing unnecessary ARP broadcast traffic and consuming significant Memory/CPU resources due to ARP cache growth.
Adım Adım Çözüm
Anahtar Kavram
Directly Attached Static Routes on Multi-Access Ethernet Links
Tahmini Süre:1m 30s