When configuring BGP, if such an alarm is generated: "BGP!6ESTABLISHED-OID[old] The BGP FSM enters the Establishedstate , which of the following description is correct?"

Question

Options

• AIndicates that the BGP neighbor has been established
• BThe neighbor relationship has been reset, no problem with
• CExplain that such alarms are generated due to TCP problems
• DExplain that there is a problem in the negotiation of OPEN packets between BGP neighbors

• A
  80% (20)
• B
  4% (1)
• C
  12% (3)
• D
  4% (1)

Explanation

Option A is correct because the alarm message explicitly states "The BGP FSM enters the Established state" - the Finite State Machine (FSM) reaching the Established state is the precise moment a BGP neighbor relationship becomes fully formed and operational.

Why the distractors are wrong:

• B is wrong because "Established" means the relationship was successfully formed, not reset. A reset would generate a different alarm (e.g., state moving away from Established).
• C is wrong because TCP issues would prevent BGP from ever reaching the Established state in the first place - a TCP failure would cause the FSM to stay in or return to Idle/Active/Connect states.
• D is wrong because OPEN packet negotiation failures occur earlier in the FSM (during the OpenSent/OpenConfirm states). Successfully passing OPEN negotiation is a prerequisite to reaching Established, not a symptom of it failing.

Memory tip: Think of BGP's FSM as having 6 states in order - Idle → Connect → Active → OpenSent → OpenConfirm → Established. "Established" is always the final, successful state, so any alarm saying "enters Established" is purely good news: the neighbor is up.

No community discussion yet for this question.