針對叢集驗證報告進行疑難排解Troubleshoot cluster validation reporting

適用于: Azure Stack HCI、版本 20H2;Windows Server 2019Applies to: Azure Stack HCI, version 20H2; Windows Server 2019

本主題可協助您針對網路和存放裝置 QoS 的叢集驗證報告進行疑難排解, (Azure Stack HCI 叢集中伺服器之間的服務) 設定品質,並確認已定義重要的規則。This topic helps you troubleshoot cluster validation reporting for network and storage QoS (quality of service) settings across servers in an Azure Stack HCI cluster, and verify that important rules are defined. 為了達到最佳連線能力和效能,叢集驗證程式會確認資料中心橋接 (DCB) QoS 設定是一致的,而且如果已定義,就會包含適用于容錯移轉叢集和 SMB/SMB 直接流量類別的適當規則。For optimal connectivity and performance, the cluster validation process verifies that Data Center Bridging (DCB) QoS configuration is consistent and, if defined, contains appropriate rules for Failover Clustering and SMB/SMB Direct traffic classes.

透過交集 Ethernet (RoCE) 網路上的 RDMA 需要 DCB,而且是選擇性的 (但建議用於網際網路廣域網路區域 RDMA 通訊協定 (iWARP) 網路的) 。DCB is required for RDMA over Converged Ethernet (RoCE) networks, and is optional (but recommended) for Internet Wide Area RDMA Protocol (iWARP) networks.

安裝資料中心橋接Install data center bridging

必須安裝資料中心橋接,才能使用 QoS 專用的 Cmdlet。Data Center Bridging must be installed to use QoS-specific cmdlets. 若要檢查伺服器上是否已安裝資料中心橋接功能,請在 PowerShell 中執行下列 Cmdlet:To check if the Data Center Bridging feature is already installed on a server, run the following cmdlet in PowerShell:

Get-WindowsFeature -Name Data-Center-Bridging -ComputerName Server1

如果未安裝資料中心橋接,請在叢集中的每部伺服器上執行下列 Cmdlet 來安裝它:If Data Center Bridging is not installed, install it by running the following cmdlet on each server in the cluster:

Install-WindowsFeature –Name Data-Center-Bridging -ComputerName Server1

執行叢集驗證測試Run a cluster validation test

在 Windows Admin Center 中使用 [驗證] 功能,方法是選取 [ 工具 > 伺服器 > 清查 > 驗證 叢集],或執行下列 PowerShell 命令:Either use the Validate feature in Windows Admin Center by selecting Tools > Servers > Inventory > Validate cluster, or run the following PowerShell command:

Test-Cluster –Node Server1, Server2

此外,測試會驗證 DCB QoS 設定是否一致,而且叢集中的所有伺服器都有相同數目的流量類別和 QoS 規則。Among other things, the test will validate that DCB QoS Configuration is consistent, and that all servers in the cluster have the same number of traffic classes and QoS Rules. 它也會確認所有伺服器都已針對容錯移轉叢集和 SMB/SMB 直接流量類別定義 QoS 規則。It will also verify that all servers have QoS rules defined for Failover Clustering and SMB/SMB Direct traffic classes.

您可以在 Windows Admin Center 中看到驗證報告,或是存取目前工作目錄中的記錄檔。You can view the validation report in Windows Admin Center, or by accessing a log file in the current working directory. 例如: C:\Users <username> \AppData\Local\TempFor example: C:\Users<username>\AppData\Local\Temp\

在接近報表底部的地方,您會看到「驗證 QoS 設定設定」,以及叢集中每部伺服器的對應報告。Near the bottom of the report, you will see "Validate QoS Settings Configuration" and a corresponding report for each server in the cluster.

若要瞭解伺服器上已設定的流量類別,請使用 Get-NetQosTrafficClass Cmdlet。To understand which traffic classes are already set on a server, use the Get-NetQosTrafficClass cmdlet.

若要深入瞭解,請參閱 驗證 Azure Stack HCI叢集。To learn more, see Validate an Azure Stack HCI cluster.

驗證網路 QoS 規則Validate networking QoS rules

在叢集中的伺服器之間,驗證 DCB 願意狀態和優先順序流量控制狀態設定的一致性。Validate the consistency of DCB willing status and priority flow control status settings between servers in the cluster.

DCB 願意的狀態DCB willing status

支援資料中心橋接功能 Exchange 通訊協定 (DCBX) 的網路介面卡可以接受來自遠端裝置的設定。Network adapters that support the Data Center Bridging Capability Exchange protocol (DCBX) can accept configurations from a remote device. 若要啟用這項功能,網路介面卡上的 DCB 願意位必須設定為 true。To enable this capability, the DCB willing bit on the network adapter must be set to true. 如果願意位設為 false,裝置將會拒絕遠端裝置的所有設定嘗試,並只強制執行本機設定。If the willing bit is set to false, the device will reject all configuration attempts from remote devices and enforce only the local configurations. 如果您在交集乙太網路上使用 RDMA (RoCE) 介面卡,則在所有伺服器上都應該將願意的位設為 false。If you're using RDMA over Converged Ethernet (RoCE) adapters, then the willing bit should be set to false on all servers.

Azure Stack HCI 叢集中的所有伺服器都應該以相同的方式設定 DCB。All servers in an Azure Stack HCI cluster should have the DCB willing bit set the same way.

使用 Set-NetQosDcbxSetting Cmdlet 將 DCB (願意位)設定為 true 或 false,如下列範例所示:Use the Set-NetQosDcbxSetting cmdlet to set the DCB willing bit to either true or false, as in the following example:

Set-NetQosDcbxSetting –Willing $false

DCB 流量控制狀態DCB flow control status

如果上層通訊協定 (如光纖通道) 假設底層傳輸不會損耗,那麼以優先順序為主的流量控制就很重要。Priority-based flow control is essential if the upper layer protocol, such as Fiber Channel, assumes a lossless underlying transport. 您可以在全域或個別網路介面卡上啟用或停用 DCB 流量控制。DCB flow control can be enabled or disabled either globally or for individual network adapters. 啟用時,可讓您建立排定特定應用程式流量優先順序的 QoS 原則。If enabled, it allows for the creation of QoS policies that prioritize certain application traffic.

為了讓 QoS 原則在容錯移轉期間順暢地運作,Azure Stack HCI 叢集中的所有伺服器都應具有相同的流量控制狀態設定。In order for QoS policies to work seamlessly during failover, all servers in an Azure Stack HCI cluster should have the same flow control status settings. 如果您使用的是 RoCE 介面卡,則必須在所有伺服器上啟用優先順序流量控制。If you're using RoCE adapters, then priority flow control must be enabled on all servers.

使用 Get-NetQosFlowControl Cmdlet 來取得目前的流程式控制制設定。Use the Get-NetQosFlowControl cmdlet to get the current flow control configuration. 預設會停用所有優先順序。All priorities are disabled by default.

使用 Enable-NetQosFlowControlDisable-NetQosFlowControl Cmdlet 搭配-priority 參數,開啟或關閉優先權流程式控制制。Use the Enable-NetQosFlowControl and Disable-NetQosFlowControl cmdlets with the -priority parameter to turn priority flow control on or off. 例如,下列命令會啟用以優先權3標記之流量的流量控制:For example, the following command enables flow control on traffic tagged with priority 3:

Enable-NetQosFlowControl –Priority 3

驗證儲存體 QoS 規則Validate storage QoS rules

確認所有節點都有適用于容錯移轉叢集和 SMB 或 SMB 直接存取的 QoS 規則。Validate that all nodes have a QoS rule for failover clustering and for SMB or SMB Direct. 否則,可能會發生連接問題和效能問題。Otherwise, connectivity problems and performance problems may occur.

容錯移轉叢集的 QoS 規則QoS Rule for failover clustering

如果叢集中有定義 任何 儲存體 QoS 規則,則應該要有容錯移轉叢集的 qos 規則,否則可能會發生連線問題。If any storage QoS rules are defined in a cluster, then a QoS rule for failover clustering should be present, or connectivity problems may occur. 若要為容錯移轉叢集新增 QoS 規則,請使用 New-NetQosPolicy Cmdlet,如下列範例所示:To add a new QoS rule for failover clustering, use the New-NetQosPolicy cmdlet as in the following example:

New-NetQosPolicy "Cluster" -IPDstPort 3343 -Priority 6

適用于 SMB 的 QoS 規則QoS rule for SMB

如果部分或所有節點已定義 QOS 規則,但沒有 SMB 的 QOS 規則,這可能會導致 SMB 的連線能力和效能問題。If some or all nodes have QOS rules defined but do not have a QOS Rule for SMB, this may cause connectivity and performance problems for SMB. 若要為 SMB 新增網路 QoS 規則,請使用此 New-NetQosPolicy Cmdlet,如下列範例所示:To add a new network QoS rule for SMB, use the New-NetQosPolicy cmdlet as in the following example:

New-NetQosPolicy -Name "SMB" -SMB -PriorityValue8021Action 3

適用于 SMB Direct 的 QoS 規則QoS rule for SMB Direct

SMB 直接存取會略過網路堆疊,改為使用 RDMA 方法來傳送資料。SMB Direct bypasses the networking stack, instead using RDMA methods to transfer data. 如果部分或所有節點已定義 QOS 規則,但沒有適用于 SMB 直接存取的 QOS 規則,這可能會導致 SMB Direct 的連線能力和效能問題。If some or all nodes have QOS rules defined but do not have a QOS Rule for SMB Direct, this may cause connectivity and performance problems for SMB Direct. 若要建立 SMB 直接存取的新 QoS 原則,請發出下列命令:To create a new QoS policy for SMB Direct, issue the following commands:

New-NetQosPolicy "SMB Direct" –NetDirectPort 445 –Priority 3

後續步驟Next steps

如需相關資訊,另請參閱:For related information, see also: