Cisco 300-640 Dumps Questions Answers

Extended Power Capacity is specifically designed to increase usable power in a Cisco UCS X-Series chassis while the chassis remains configured in a redundant power mode. Cisco states that enabling Extended Power Capacity permits the chassis to borrow power capacity from the supplies reserved for redundancy, thereby increasing the total power that can be allocated to workloads.

Cisco provides a six-PSU example in Grid redundancy mode. Without Extended Power Capacity, the workload is capped at 8,400 W. Enabling the feature increases the available workload capacity to approximately 9,660 W—an increase of 15 percent—while retaining the configured redundant power mode.

Power capping in option A would restrict consumption rather than make additional power available. Adding more PSUs is impossible when the chassis already contains its supported complement of six supplies. Disabling Extended Power Capacity would reduce rather than increase the available power envelope.

This feature is particularly useful after installing additional accelerator, PCIe, memory, or compute resources that raise chassis power demand. It should nevertheless be applied within the data center's electrical and thermal design limits.

Study Guide Reference: AI Infrastructure Operations and Troubleshooting — UCS X-Series chassis power policy, redundancy, Extended Power Capacity, and capacity management.

===============

ECN (Explicit Congestion Notification)

PFC (Priority Flow Control)

ECN and PFC address different congestion conditions in a RoCEv2 fabric and are intended to complement rather than replace each other. ECN is the appropriate mechanism for fabric-level congestion generated by incast patterns. When several GPU or storage senders simultaneously transmit toward the same destination, switch queues begin to build. ECN-capable switches mark packets rather than immediately dropping them, allowing the receiving endpoint to generate congestion feedback so the transmitting source can reduce its sending rate.

PFC provides hop-by-hop loss prevention for the designated lossless Ethernet priority. When an endpoint or downstream interface cannot accept a burst quickly enough and a queue approaches its configured threshold, PFC transmits pause frames for that specific priority. This temporarily stops upstream transmission and prevents packet loss.

Cisco's RoCEv2 designs combine ECN and PFC precisely because ECN provides proactive end-to-end congestion management while PFC acts as the protective mechanism when queue buildup becomes severe or occurs faster than endpoint rate adaptation can respond.

WRED can provide the queue-marking mechanism associated with ECN, but the requested logical congestion-control mechanism is ECN. AFD is not the corresponding RoCEv2 lossless mechanism for either description.

Study Guide Reference: AI Infrastructure Deployment and Data Management — congestion control, RoCEv2, ECN, PFC, QoS, and lossless Ethernet.

===============

In Cisco Intersight Managed Mode, Fabric Interconnect physical port roles and port-channel definitions are configured through the Port Policy . Cisco's current Intersight configuration documentation states that a Port Policy configures ports and port roles on a Fabric Interconnect and permits administrators to enable or disable individual ports or port channels. Supported roles include Ethernet uplinks and Ethernet uplink port channels.

The Port Policy is subsequently associated with the UCS Domain Profile. Cisco documents that a Domain Profile configures an FI pair through reusable policies and controls ports, port channels, VLANs, and VSANs. During Domain Profile creation, the administrator attaches the appropriate Port Policy to each Fabric Interconnect.

A LAN Connectivity Policy is used primarily at the server-profile level to define vNIC connectivity. A Network Connectivity Policy configures DNS-related server-management settings rather than FI uplink topology. An Ethernet Network Group Policy defines VLAN groups associated with Ethernet connectivity and can be referenced by uplink configurations, but it does not itself create the FI port channel.

Consequently, the policy that must be changed to build the multiple-100-GbE uplink port channel is the Port Policy .

Study Guide Reference: AI Infrastructure Deployment and Data Management — Intersight Managed Mode, UCS Domain Profiles, Fabric Interconnect port configuration, and uplink resiliency.

===============