350-601 Exam Dumps - Cisco CCNP Data Center Questions and Answers

To enable port security on all Cisco MDS series switches in the fabric and avoid the extensive manual configuration of the switch ports, the network engineer must activate the CFS (Cisco Fabric Services) distribution and enable the auto-learning port security feature on a per-VSAN basis. CFS is a protocol that allows the switches to distribute and synchronize configuration information across the fabric. By activating the CFS distribution for port security, the network engineer can propagate the port security configuration to all the switches in the fabric automatically, without having to configure each switch individually. The auto-learning port security feature allows the switches to learn and store the port security information of the devices that are already logged in and authorized on the ports, and prevent any unauthorized devices from logging in. The auto-learning port security feature can be enabled on a per-VSAN basis, which means that the port security information is specific to each VSAN and does not affect other VSANs. This provides more flexibility and granularity for the port security configuration. References :=

• Implementing and Operating Cisco Data Center Core Technologies (DCCOR) v1.2, Module 7: Data Center Storage Connectivity, Lesson 7.3: Fibre Channel Protocol
• Cisco MDS 9000 Family NX-OS Security Configuration Guide, Chapter: Configuring Port Security

To achieve the most optimal on demand CPU performance while configuring the BIOS settings of a UCS C-series rack mount server, you should set the CPU Performance option to C0/C1 state. This option enables the CPU to operate in the highest performance state (C0) or the lowest power state (C1) depending on the workload demand. This allows the CPU to maximize its performance and efficiency without compromising its thermal and power limits. The other options (C6 Retention, C2 state, and C6 non-Retention) reduce the CPU performance by putting the CPU into deeper sleep states (C2 or C6) when idle, which can increase the latency and power consumption when resuming the CPU activity. References: For more details on how to configure the BIOS settings of a UCS C-series rack mount server, please refer to the following resources:

• Cisco UCS C-Series Servers Integrated Management Controller GUI Configuration Guide
• Cisco UCS C-Series Rack-Mount Server BIOS Settings

Graphical user interface, text, application Description automatically generated

 When a VLAN is added to a trunk and it does not appear on the vNIC of an associated server, it typically indicates that the vNIC template is not updating as it should to reflect changes. By changing the template type of Trunk-A to an updating template, any changes made to the trunk configuration, such as adding a new VLAN, will be dynamically applied to all vNICs associated with that template. This action will allow the newly added VLAN to be included in the vNIC configuration without the need to manually update each vNIC or recreate the templates.

References := This recommendation aligns with best practices for managing vNIC templates in Cisco UCS environments, where updating templates are used to ensure changes propagate automatically to all associated instances

The roles required to modify system logs, faults, and power management settings, as well as view access to all other configurations in the UCS domain, are typically those that provide broad administrative capabilities. The Operations role allows for the modification of operational aspects such as logs and power management, while the Administrator role provides full access to all configurations and settings within the UCS domain1.

References: = For more detailed information on user roles and permissions in Cisco UCS, you can refer to the Cisco UCS Manager Administration Management Guide2 and other official Cisco documentation1.

 To make a capture task persistent after a reboot, the command sequence in Option C should be used. This typically involves enabling the service to start at boot time using systemctl enable and then starting the service with systemctl start. This ensures that the capture task will automatically resume after the system is rebooted4

Diagram Description automatically generated

 In a vPC (Virtual Port-Channel) configuration, multicast traffic is handled based on the vPC design and operational rules. When a host sends traffic to a multicast group, the vPC switches determine the forwarding path based on the source and the vPC domain configuration. If multicast traffic is received on a vPC member port, such as Po10 on Switch1, the traffic is typically forwarded out on all ports that are part of the same VLAN and have receivers interested in the multicast group, which includes Po1 and Po20 in this case. This ensures that the multicast traffic reaches all intended recipients across the vPC domain.

References: For a comprehensive understanding, the Cisco documentation on “Multicast forwarding in vPC based on location of the source” provides detailed scenarios and explanations on how multicast traffic is forwarded in a vPC environment1. Additionally, the “Cisco Nexus 9000 Series NX-OS Multicast Routing Configuration Guide” offers insights into the configuration and behavior of multicast routing on Nexus switches, which can be applied to understand the vPC behavior with multicast traffic

NFSv2

NFSv4

Kerberos

RADIUS

Two statements that are true about the process of performing an EPLD upgrade on a Cisco MDS 9000 series Switch are:

• If an upgrade is interrupted, the upgrade continues after a connection is restored. This means that the EPLD upgrade process is resilient to network or power failures and can resume from where it left off once the connection is reestablished.
• The upgrade can be performed from the standby supervisor module. This allows the active supervisor module to continue to provide management and control functions while the EPLD upgrade is in progress. The standby supervisor module can also take over the active role if needed during the upgrade.

The other statements are not true because:

• The active supervisor cannot be upgraded. The EPLD upgrade process requires the supervisor module to be in standby mode before it can be upgraded. The active supervisor module must be switched to standby mode manually or automatically before the upgrade can begin.
• Modules do not need to be online to be upgraded. The EPLD upgrade process can upgrade modules that are offline or powered down as well as modules that are online. The offline modules are upgraded when they are brought online or powered up.
• The upgrade process disrupts all modules that are being upgraded. The EPLD upgrade process requires a module reload for each module that is being upgraded, which causes a temporary disruption of traffic and services on that module. The disruption can be minimized by using hitless or non-disruptive EPLD upgrade modes, which preserve the forwarding state and configuration of the module during the reload. References: For more details on how to perform an EPLD upgrade on a Cisco MDS 9000 series Switch, please refer to the following resources:
• Cisco MDS 9000 Family NX-OS System Management Configuration Guide
• Cisco MDS 9000 Family EPLD Upgrade Release Notes