ANS-C01 · Question #195
A company has a new AWS Direct Connect connection between its on-premises data center and the AWS Cloud. The company has created a new private VIF on this connection. However, the VIF status is…
The correct answer is B. TCP port 179 is blocked on the customer Direct Connect router. https://docs.aws.amazon.com/directconnect/latest/UserGuide/Troubleshooting.html#ts-layer-2 Ensure that there are no firewall or ACL rules that are blocking TCP port 179 or any high- numbered ephemeral TCP ports. These ports are necessary for BGP to establish a TCP connection…
Question
A company has a new AWS Direct Connect connection between its on-premises data center and the AWS Cloud. The company has created a new private VIF on this connection. However, the VIF status is DOWN. A network engineer verifies that the physical connection status is UP and RUNNING based on information from the AWS Management Console. The network engineer checks the customer Direct Connect router and can see the ARP entry for the VLAN interface created for the private VIF at AWS. What could be causing the private VIF to have a DOWN status?
Options
- AICMP is blocked on the customer Direct Connect router.
- BTCP port 179 is blocked on the customer Direct Connect router.
- CThe IEEE 802.1Q VLAN identifier is misconfigured on the customer Direct Connect router.
- DThe company has configured IEEE 802.1ad instead of 802.1Q on the customer Direct Connect
How the community answered
(27 responses)- A11% (3)
- B81% (22)
- C4% (1)
- D4% (1)
Explanation
https://docs.aws.amazon.com/directconnect/latest/UserGuide/Troubleshooting.html#ts-layer-2 Ensure that there are no firewall or ACL rules that are blocking TCP port 179 or any high- numbered ephemeral TCP ports. These ports are necessary for BGP to establish a TCP connection between the peers.
Community Discussion
No community discussion yet for this question.