Author | Chrissy LeMaire (@cl), netnerds.net |
Availability | Windows, Linux, macOS |
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.
Gets information about one or more network adapters in a failover cluster.
Gets information about one or more network adapters in a failover cluster.
All Windows Server Failover Clustering (Wsfc) commands require local admin on each member node.
Get-DbaWsfcNetworkInterface
[[-ComputerName] <DbaInstanceParameter[]>]
[[-Credential] <PSCredential>]
[-EnableException]
[<CommonParameters>]
PS C:\> Get-DbaWsfcNetworkInterface -ComputerName cluster01
Gets network interface information from the failover cluster cluster01
PS C:\> Get-DbaWsfcNetworkInterface -ComputerName cluster01 | Select-Object *
Shows all network interface values, including the ones not shown in the default view
The target cluster name. Can be a Network or the cluster name itself.
Alias | |
Required | False |
Pipeline | true (ByValue) |
Default Value | $env:COMPUTERNAME |
Allows you to login to the cluster using alternative credentials.
Alias | |
Required | False |
Pipeline | false |
Default Value |
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.
Alias | |
Required | False |
Pipeline | false |
Default Value | False |