An engineer needs to avoid loops in the ACI network and needs an ACI leaf switch to error- disable an interface if the interface receives an ACI-generated packet. Which action meets these requirements

Question

Options

• ASet Rogue EP Control in the Endpoint Controls Policy.
• BUncheck the Loop Protection Action check box in MCP Instance Policy.
• CEnable the Loop Indication by MCP event in the Error Disabled Recovery Policy.
• DChange the default administrative state of the global MCP Instance Policy.

• B
  6% (1)
• D
  94% (17)

Explanation

MisCabling Protocol (MCP) detects loops from external sources (i.e., misbehaving servers, external networking equipment running STP, etc.) and will err-disable the interface on which ACI receives its own packet. Enabling this feature is a best practice, and it should be enabled globally and on all interfaces, regardless of the end device. For MCP to be enabled, you need to have it enabled globally and on a per-interface basis. While MCP is enabled on all interfaces by default, it is not turned “on” until you also enable it globally. The global configuration knob for MCP can be enabled by configuring the global settings here: Fabric > Access Policies > Global Policies > MCP Instance Policy default. centric-infrastructure/aci-guide-using-mcp-mis-cabling-protocol.pdf

No community discussion yet for this question.