Get-DbaWsfcNetworkInterface

Want to see the source code for this command? Check out Get-DbaWsfcNetworkInterface on GitHub.
Want to see the Bill Of Health for this command? Check out Get-DbaWsfcNetworkInterface.

Synopsis

Retrieves network interface configuration from Windows Server Failover Cluster nodes.

Description

Retrieves detailed network adapter information from all nodes in a Windows Server Failover Cluster, including IP addresses, DHCP settings, and network assignments. This information is essential for troubleshooting SQL Server Failover Cluster Instance connectivity issues and verifying cluster network configuration.

Use this command to identify network misconfigurations that could impact SQL Server availability, document cluster network topology for compliance, or diagnose connectivity problems between cluster nodes.

All Windows Server Failover Clustering (Wsfc) commands require local admin on each member node.

Syntax

Get-DbaWsfcNetworkInterface
    [[-ComputerName] <DbaInstanceParameter[]>]
    [[-Credential] <PSCredential>]
    [-EnableException]
    [<CommonParameters>]

Examples

Example: 1

PS C:\> Get-DbaWsfcNetworkInterface -ComputerName cluster01

Gets network interface information from the failover cluster cluster01

Example: 2

PS C:\> Get-DbaWsfcNetworkInterface -ComputerName cluster01 | Select-Object *

Shows all network interface values, including the ones not shown in the default view

Optional Parameters

-ComputerName

Specifies the Windows Server Failover Cluster name or any cluster node name to query for network interface information.
Use this when troubleshooting SQL Server FCI connectivity issues or documenting cluster network topology.
Accepts cluster names, node names, or IP addresses of cluster resources.

-Credential

Allows you to login to the cluster using alternative credentials.

-EnableException

By default, when something goes wrong we try to catch it, interpret it and give you a friendly warning message.
This avoids overwhelming you with "sea of red" exceptions, but is inconvenient because it basically disables advanced scripting.
Using this switch turns this "nice by default" feature off and enables you to catch exceptions with your own try/catch.