JN0-106 Operational Monitoring and Maintenance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The BGP table is full

  Why it's wrong here

  A full BGP table does not cause the router to send a BGP Cease notification. When the routing table reaches its limit, the router may experience memory pressure or drop new routes, but the BGP session itself remains operational. The Cease error code specifically indicates that the remote peer decided to terminate the session for administrative or policy reasons, not because of local resource exhaustion. Therefore, the table being full is not the correct explanation for the logged Cease message.

• ✗

  The hold timer expired

  Why it's wrong here

  Hold timer expiry produces a different BGP notification code (Hold Timer Expired, code 4), not the Cease code (6) seen in the syslog. During a hold timer expiry, the local router has not received any keepalive or update messages within the configured hold interval, so it declares the peer unreachable and sends a Hold Timer Expired notification. In contrast, the log entry shows a Cease notification, which is sent when the peer actively closes the session. Thus, the hold timer scenario would generate a distinct error, making this option incorrect.

• ✓

  The remote peer closed the connection

  Why this is correct

  A BGP Cease notification indicates that the remote peer explicitly sent a NOTIFICATION message to terminate the BGP session. The Cease error code (6) covers several subcodes, such as administrative shutdown, peer de-configured, or local system restart, but all mean the remote peer closed the connection at the BGP protocol level. Because the log specifically records a Cease, the most direct inference is that the remote peer closed the connection, thereby causing the session to flap. This is why this is the correct answer.

• ✗

  The interface went down

  Why it's wrong here

  If the interface had gone down, the underlying TCP session would break immediately, resulting in a TCP reset or a loss of connectivity rather than a BGP Cease notification. BGP would eventually transition to the Idle state after the hold timer expires, but before that, the router would not have a chance to send a BGP NOTIFICATION. The Cease code in the log proves that a BGP protocol-level message was exchanged before the session terminated, which cannot happen if the link itself failed. Therefore, an interface down event is not the cause of this specific log entry.