Pass 350-601 Exam Guide

 The correct configuration for a unified I/O link that supports both LAN and SAN traffic using a single Ethernet transport is to configure the interface as a trunk port. This allows multiple VLANs (for LAN traffic) and VSANs (for SAN traffic) to coexist on the same physical link. The auto qos trust dscp command ensures that the Quality of Service (QoS) markings are preserved, which is essential for maintaining traffic prioritization across the network.

References: For more detailed information, please refer to the Cisco Data Center Core Technologies study materials and official documentation available on the Cisco website. These resources provide comprehensive guidance on configuring and managing Cisco Nexus and MDS switches in a data center environment.

To facilitate communication between the APIC controller and an OpenStack OpFlex agent, it’s necessary to enable the Infra VLAN on the Attachable Access Entity Profile (AAEP). The AAEP is used in Cisco ACI to group interfaces that share common policies and extending the Infra VLAN to these interfaces allows the OpFlex agent, which is part of the Cisco Application Centric Infrastructure (ACI), to communicate with the APIC controller. This setup is crucial for the OpFlex agent to function correctly, as it relies on the Infra VLAN for communication with the APIC controller1.

References:

• Cisco ACI Installation Guide for Red Hat OpenStack Using the OpenStack Platform 13 Director1.
• Cisco ACI Installation Guide for Red Hat OpenStack Using the OpenStack Platform 16.1 Director

The action that must be performed before renumbering a Cisco UCS chassis is to re-acknowledge the chassis. Re-acknowledging the chassis is a process that forces the Cisco UCS Manager to rediscover the chassis and its components, such as the I/O modules, the power supplies, and the fans. Re-acknowledging the chassis is necessary before renumbering the chassis, because it ensures that the Cisco UCS Manager has the latest information about the chassis and its configuration. Re-acknowledging the chassis also allows the network engineer to apply any pending configuration changes or policies to the chassis and its components. Re-acknowledging the chassis can be done from the Cisco UCS Manager GUI or CLI, by selecting the chassis and choosing the Re-Acknowledge option. References :=

• Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 5: Cisco Unified Computing System, Lesson 5.1: Cisco UCS Architecture
• Cisco UCS Manager GUI Configuration Guide, Release 4.0, Chapter: Managing Chassis, Section: Re-Acknowledging a Chassis

The In-Service Software Upgrade (ISSU) process is designed to upgrade the system software with minimal disruption to the network. Nonstop forwarding (NSF) and stateful switchover (SSO) are two features that work together to maintain packet forwarding and switch state information during the ISSU process. NSF allows the router to continue forwarding packets even when the route processor is failing over, while SSO synchronizes state information between redundant route processors to ensure a seamless transition during a failover1.

References := For a deeper understanding of the ISSU process and its associated features, you can refer to Cisco’s official documentation on In-Service Software Upgrade (ISSU), which provides detailed information on how NSF and SSO contribute to a nondisruptive upgrade