CPU Spike - Network Change

Zadok — Wed, 04 Jun 2025 09:47:05 GMT

We had a 1GB switch for service management and data traffic on NetApp storage and ESXI servers. All VM data are on NetApp storage

after buying a new 10Gb switch, data ports on both devices were switched to the new switch. But the management port remained on the 1Gb switch.

right now, the CPU usage of some of these VMs is currently spiking. We are thinking it’s because of the change. However, I believe NetApp storage should auto negotiate.

Are there any issues we might have overlooked?

Re: CPU Spike - Network Change

Ontapforrum — Mon, 17 Jul 2023 13:46:16 GMT

Historically, NetApp had recommended that flow control be disabled on all network ports within a NetApp Data ONTAP cluster. This approach is no longer the case. Guidance in this area has since changed, and the new recommended best practice is as follows:

• Disable flow control on cluster network ports in the Data ONTAP cluster.
• Flow control on the remaining network ports (the ports that provide data, management, and intercluster connectivity) should be configured to match the settings within the rest of your environment.

In short, Flow control setting should be the same end-2-end. (Either disable it or set the fixed speed, but do not let it auto-negotiate).

I don't know how VM's CPU usage could be affected by this, haven't come across it. Throughput could be an issue .

topic CPU Spike - Network Change in Network and Storage Protocols

CPU Spike - Network Change

Re: CPU Spike - Network Change