Hi @SG MUHAMMAD HASHIM ,
Can you confirm if you are installing Azure Stack HCI version 22H2 or 23H2?
With 23H2, the entire deployment and cluster creation process is automated. Manually deploying a cluster on 23H2 is not supported. As such, the network is configured during the deployment using Network ATC, so there are generally very few changes that need to be made prior to the deployment. Instead, you provide the necessary information in the deployment wizard which configures your nodes for you accordingly.
Given you seem to be manually creating the cluster, my assumption is that you are deploying 22H2. In this scenario, I would recommend using Network ATC to configure all of the host network settings. Doing so configures all of the required QoS/DCB/RDMA settings for the network adapters based on the intent types applied to them. It will also automatically assign IP addresses to each of your storage NICs so you don't need to worry about managing IPs or VLANs. This is especially useful in switchless environments where the storage networks are completely separated from the physical network. But if you need to change a setting on an adapter that Network ATC manages, you can do so by setting an override. More information on Network ATC can be found in the links below.
Deploy host networking with Network ATC
A common issue with switchless environments that I have seen is that customers will attempt to put their two storage adapters on the same IP subnet and VLAN which won't work. The cluster assumes that all IPs on the same IP subnet will be able to talk to each other, so if it can't reach a particular IP in that range, it shows the network as 'partitioned'.
Hope this helps!