Hi Chang Min
Yes, SMB Multichannel can get pretty messy when you mix link speeds like that it tries to be “smart” but ends up thrashing connections because the throughput math never stabilizes. The clean way to handle this is to tell SMB to only use the faster NICs. You can do that by disabling multichannel on the 10GbE adapters with Set-SmbClientConfiguration -DisableMultiChannel $true or by tweaking the SMB Multichannel constraints so only the 25GbE interfaces are eligible. Another option is to use Interface Binding via PowerShell, where you explicitly bind SMB traffic to the NICs you want. That way, the 10G links can stay connected for management traffic but won’t be part of the SMB channel pool.
Some admins also prefer to separate management and data networks entirely with different subnets/VLANs, so SMB never even “sees” the slower adapters. Bottom line: you don’t need to pull cables just restrict SMB Multichannel to the 25GbE side and let the 10G links handle their own role.