SIMULATION Configure a VRF called "VrfGreen" and the static route in it to network 172.16.128.64/28 through next-hop 10.10.10.1. Set an administrative distance of 213. Answer: Enter Configuration…

Question

Options

• APeer Link, Peer Address, and VRRP Status
• BSystem MAC, Peer Address, and Keepalive Interval
• CSource Address, Peer Address, and AS Number
• DSystem MAC, Mclag System MAC, and System IP Address

• A
  9% (2)
• B
  73% (16)
• C
  14% (3)
• D
  5% (1)

Explanation

Note: There appears to be a mismatch between the question body (VRF/static route configuration) and the answer choices (which relate to MCLAG configuration in SONiC). The explanation below addresses the answer choices in their proper MCLAG context.

Option B is correct because configuring an MCLAG domain in SONiC requires three core parameters: the System MAC (shared virtual MAC that identifies the MCLAG pair), the Peer Address (IP used to reach the MCLAG partner switch), and the Keepalive Interval (heartbeat timer to detect peer failure) - these together establish the domain identity and health-monitoring mechanism.

A is wrong because VRRP Status is a first-hop redundancy protocol concept entirely unrelated to MCLAG domain setup.
C is wrong because AS Number belongs to BGP configuration, not MCLAG - mixing routing protocol parameters with a link aggregation feature.
D is a trap: while System MAC and System IP are valid MCLAG concepts, "Mclag System MAC" as a third distinct field is a fabricated distractor that doesn't reflect actual SONiC MCLAG CLI parameters.

Memory tip: Think "MAC, Peer, Heartbeat" - you need to know who you are (System MAC), who your partner is (Peer Address), and how often you check in (Keepalive Interval). These three answer the what, who, and how-often of MCLAG.

No community discussion yet for this question.