In a Mesh network, engineers found that the MP failed to go online. Which of the following may be the reasons for this problem? (Multiple choice)

Question

Options

• AAP does not obtain the neighbor information of the AP
• BImproper distance parameter configuration
• CLeaf node MP is not added offline
• DThe root node MPP is not online

• A
  100% (29)

Explanation

All four options represent legitimate causes of an MP failing to go online in a Mesh network, each targeting a different layer of the mesh establishment process. A is correct because MPs rely on neighbor discovery to form mesh links - without neighbor information, an MP has no peers to connect through. B is correct because distance parameters control link thresholds; misconfiguration can cause MPs to reject valid neighbors or fail to establish stable links. C is correct because in many Mesh implementations, leaf MPs must be pre-provisioned (added offline) before they are permitted to join the mesh fabric - skipping this step blocks authentication or association. D is correct because the MPP (Mesh Portal Point) is the network's root and upstream gateway; if it is offline, downstream MPs have no path to complete their mesh topology and cannot reach the network.

Since every option is a valid failure cause, there are no distractors to eliminate here - the question tests whether you understand the full dependency chain of mesh bring-up: provisioning → root node availability → neighbor discovery → correct link parameters.

Memory tip: Think of mesh bring-up as a chain - Provisioning → Root → Neighbors → Parameters (mnemonic: PR-NP, "Prepare the Network Properly"). If any link in that chain breaks, the MP fails to come online.

No community discussion yet for this question.