Configuring MCP Syslog Logging Without Port Shutdown
Short answer
A Disable loop protection action, set initial delay to 60, and set Loop Detect Multiplication Factor to 10.
Question
Key Takeaways
The main trap is confusing 'Disable' with 'Enable'; enabling loop protection shuts down the port, while disabling it allows logging only.
Learn how to configure Cisco ACI MCP to log loop events via syslog by disabling the loop protection action and setting the appropriate detection factors.
Common mistake: Choosing 'Enable' because users assume loop protection must actively block loops, failing to notice the requirement was solely for syslog generation.
Expert Analysis
The question asks for a configuration to generate syslog messages after detecting a loop, without disrupting traffic. The key constraint is "generating syslog messages," which implies the port must remain operational.
Enable vs. Disable Loop Protection Action: In Cisco ACI Multi-Channel Protocol (MCP), the "Loop Protection Action" determines how the switch reacts to detected loops. If Enabled, MCP err-disables the port, shutting down connectivity. If Disabled, MCP does not shut down the port but generates faults and syslog messages instead. Since the goal is only to log the event, the action must be Disabled. This eliminates options B and D.
Parameter Selection: The question specifies receiving "10 continuous looped packets." In MCP loop detection settings, the Loop Detect Multiplication Factor is used to determine the threshold for detection based on packet counts or intervals. Setting this factor to 10 aligns with the requirement to detect 10 packets. The "Transmission Frequency" parameter is not the standard setting for defining the packet count threshold in this context. Therefore, setting the Loop Detect Multiplication Factor to 10 is the correct configuration step.
Combining these, we must Disable the action and set the Multiplication Factor to 10. This matches Option A.
Exam Strategy
Always read the desired outcome carefully. If the requirement is 'logging' or 'alerting', look for settings that keep the interface up (often 'Disable' or 'Trap' modes). If the requirement is 'prevention' or 'stopping traffic', look for 'Enable' or 'Shutdown' modes. Do not assume 'Protection' always means 'Blocking'.
Frequently Asked Questions
What happens if I enable loop protection action in ACI MCP?
Why use Loop Detect Multiplication Factor?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
ostych 👍 1 Answered AA -> When the loop protection action is enabled, MCP err-disables the port after it detects a loop. When it is disabled, MCP only logs the event as syslog/a fault and leaves the port up. The requirement here is only to generate syslog messages.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.