In BGP, during which session state are update, keepalive and notification messages exchanged?

Master RIPE BGP Security with our comprehensive test. Understand the Border Gateway Protocol, explore multiple choice questions, and get ready for your exam with detailed hints and explanations.

Multiple Choice

In BGP, during which session state are update, keepalive and notification messages exchanged?

Explanation:
The essential idea is that routing updates, keepalives, and notifications flow only after the BGP session is fully up. BGP uses a TCP connection, and neighbors first exchange Open messages to negotiate parameters. Once both sides agree, the session moves into the Established state. In Established, peers regularly exchange Update messages to advertise or withdraw routes, send KeepAlive messages to verify liveness, and issue Notification messages to report errors. Before reaching Established—during Idle, Connect, OpenSent, or OpenConfirm—the session is still being set up, so Update and KeepAlive traffic doesn’t occur yet. So, the state where update, keepalive, and notification messages are exchanged is the Established state.

The essential idea is that routing updates, keepalives, and notifications flow only after the BGP session is fully up. BGP uses a TCP connection, and neighbors first exchange Open messages to negotiate parameters. Once both sides agree, the session moves into the Established state. In Established, peers regularly exchange Update messages to advertise or withdraw routes, send KeepAlive messages to verify liveness, and issue Notification messages to report errors. Before reaching Established—during Idle, Connect, OpenSent, or OpenConfirm—the session is still being set up, so Update and KeepAlive traffic doesn’t occur yet. So, the state where update, keepalive, and notification messages are exchanged is the Established state.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy