Cisco 350-601 - Implementing Cisco Data Center Core Technologies v1.1 (350-601 DCCOR)

The correct choices are A and D. In Cisco UCS, when the requirement is to aggregate links between the Fabric Interconnects and the I/O modules, the chassis discovery policy must use Link Grouping Preference = Port Channel. Cisco documents that for UCS 2200 I/O modules, selecting Port Channel causes the IOM-connected server ports to be automatically added to a port channel, which is exactly what provides link aggregation across the four 10-GbE connections per I/O module.

The second required step is D, because Cisco also states that after changing the link grouping preference, the chassis must be reacknowledged so the links are rediscovered and formed into the fabric port channel. Cisco’s UCS Manager infrastructure policy documentation explicitly notes that links can be added or removed by changing the link group preference and reacknowledging the chassis.

Options B and C do not create FI-to-IOM aggregation, and E is unrelated because unified ports are FI ports for Ethernet/FCoE or Fibre Channel flexibility, not a chassis-side requirement for this aggregation task.

To monitor FCoE traffic associated with a vHBA, the corresponding VSAN should be selected as the traffic-monitoring source. This captures the relevant storage traffic without incorrectly selecting a vNIC, Ethernet port channel, or individual Fibre Channel uplink. Cisco UCS requires a dedicated, unconfigured physical Ethernet port as the monitoring destination so that copied frames can be delivered to an external analyzer. The session must also be enabled after defining its source and destination. Option A incorrectly uses a Fibre Channel port as the source and an active uplink as the destination. Option B uses Ethernet and vNIC components that do not represent the required VSAN traffic. Option C reverses the source and destination roles and attempts to send monitored traffic to an FC uplink, which is not the correct destination for an external Ethernet analyzer.

The install all epld command initiates installation of the specified Electronic Programmable Logic Device image on applicable components of the Nexus switch. EPLD updates reprogram hardware logic and commonly require affected modules or the switch to reload, making the operation disruptive. The command shown does not contain a verification, compatibility-check, or simulation keyword; consequently, it performs the upgrade rather than merely reporting its expected effect. A compatibility or impact assessment would require the appropriate pre-upgrade verification mechanism. A simulated upgrade would likewise require a specific simulation or dry-run option that is absent from the displayed command. Administrators should confirm platform compatibility, save the configuration, schedule a maintenance window, and account for traffic interruption before executing the actual EPLD installation. Therefore, the direct result of the command is a disruptive EPLD upgrade.

The correct answer is D because the SPAN session must capture only the traffic relevant to the two reported problems. For PC1, the diagram shows it is in VLAN 10, so using source vlan 10 rx focuses the capture on traffic received in that VLAN and avoids collecting unnecessary traffic from VLAN 15, which belongs to PC2. That makes option D more precise than option C, which would also mirror VLAN 15 traffic and add noise to the analyzer output.

For the server issue, the servers are behind SW2, which is connected to the Nexus on Ethernet 1/2. Therefore, the uplink toward SW2 must also be included as a source so the engineer can inspect traffic related to the packet drops affecting those servers. Cisco NX-OS SPAN supports mixing VLAN sources and interface sources in the same monitor session when the goal is targeted troubleshooting.

Options A and B mirror both switch uplinks only, which does not isolate PC1 specifically. Option C is too broad because it mirrors VLANs 10 through 15. Thus, D is the best configuration because it captures PC1’s VLAN 10 traffic and the SW2 uplink traffic needed for investigation.