100-490 · Question #67
An Ethernet interface is up and the line protocol is down. What are two possible causes? (Choose two.)
The correct answer is A. There is a speed or duplex mismatch with the remote device. B. There is a Layer 2 mismatch in the encapsulation type. While the initial answers focused on the most common causes, here's why the other options could also contribute to an interface being stuck in the "up/down" state: Speed or Duplex Mismatch: Devices on either end of an Ethernet connection need to use compatible speed (e.g., 100…
Question
An Ethernet interface is up and the line protocol is down. What are two possible causes? (Choose two.)
Options
- AThere is a speed or duplex mismatch with the remote device.
- BThere is a Layer 2 mismatch in the encapsulation type.
- CThe Ethernet interface has been manually disabled.
- DKeepalives are not being received by the local device.
- EThe Ethernet cable might not be attached properly.
How the community answered
(43 responses)- A79% (34)
- C7% (3)
- D2% (1)
- E12% (5)
Explanation
While the initial answers focused on the most common causes, here's why the other options could also contribute to an interface being stuck in the "up/down" state: Speed or Duplex Mismatch: Devices on either end of an Ethernet connection need to use compatible speed (e.g., 100 Mbps, 1 Gbps) and duplex (full-duplex or half-duplex) settings. Mismatches can prevent the line protocol from coming up even if the physical link is established. Layer 2 Mismatch in Encapsulation Type: Some protocols used on Ethernet networks, like ISL and 802.1Q, have specific encapsulation requirements. If devices on each end aren't using the same encapsulation type, the line protocol will likely remain down.
Topics
Community Discussion
No community discussion yet for this question.