Network ATC failed while applying the intent - The parameter is incorrect.

Brad 26 Reputation points
2021-12-28T08:30:25.673+00:00

We have a 4 node stretched Azure Stack HCI Cluster running v20348.405.

When we attempt to add a Network ATC intent for either storage, compute or Management, we receive the bellow error:

Network ATC failed while applying the intent (storage). Please refer to the service traces for details on the failure. Exception : (System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The parameter is incorrect.
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
at System.Management.Automation.PowerShell.CoreInvokeHelperTInput,TOutput
at System.Management.Automation.PowerShell.CoreInvokeTInput,TOutput
at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
at FabricManager.PsHelper.RunPs1Command(String commandName, Dictionary2 arguments, ActionPreference actionPreference, Nullable1 confirm)
at FabricManager.FabricManagerLibrary.PsWrap_CreateOrUpdateQosTrafficClass(String name, Byte priority, Byte bandwidthPercentage)
at FabricManager.FabricHelperFacade.CreateOrUpdateQosPolicy(QoSPolicy qoSPolicy, List`1 physicalAdapterNames)
at FabricManager.SwitchConfig.Provision()
at FabricManager.IntentService.OntimerCallback(Object state))

Each node has been rebooted multiple times & is updated to the latest version.

Nodes are all running identical hardware, including NICs

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
301 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Trent Helms - MSFT 2,536 Reputation points Microsoft Employee
    2022-01-03T14:04:20.953+00:00

    Hi @Brad ,

    Can you provide me with some additional information regarding your setup? Is this deployment on all physical hardware, and does this hardware support RDMA? If this is a virtual environment for testing, it would be expected that some of the intent deployments will fail. If everything is physical, can you also confirm all of the pre-reqs have been installed that Network ATC needs (specifically Data Center Bridging)? It would appear from the output above the failure is coming from an attempt to create QoS policies, and the DCB feature is required for this to happen.

    Hope this helps!

  2. Trent Helms - MSFT 2,536 Reputation points Microsoft Employee
    2022-01-14T17:18:25.857+00:00

    Hi @Brad ,

    I did some additional digging and found that this error can be caused when you already have a conflicting DCB configuration in place. Can you double-check and confirm if all prior configurations have been removed? You can use the steps documented here to ensure all previous configs are removed - https://video2.skills-academy.com/en-us/azure-stack/hci/manage/manage-network-atc#remove-an-intent.

    I hate to hear you are looking to shelve Network ATC. The feature itself is documented in the links below:
    https://video2.skills-academy.com/en-us/azure-stack/hci/deploy/network-atc
    https://video2.skills-academy.com/en-us/azure-stack/hci/manage/manage-network-atc

    I'd be glad if you could provide us with some feedback on what we could do to improve your experience - we would greatly appreciate it. If you would like, we'd even be willing to schedule a call with you to discuss your experience.

    Thanks so much!
    Trent