SQL SERVER – Error: Parameter ‘ProbePort’ does not exist on the cluster object. Unable to set Probe Port for Azure Load Balancer

SQL
No Comments

Azure is gaining popularity and I am getting clients who want to create Always On availability group as their high availability solution in Azure Virtual machine. To keep myself up to date, I also try creating the customer’s scenario in my lab. In this blog, we would how to fix error Parameter ‘ProbePort’ does not exist on the cluster object while configuring probe port.

SQL SERVER – Error: Parameter 'ProbePort' does not exist on the cluster object. Unable to set Probe Port for Azure Load Balancer alwaysonerror

I was following Microsoft’s article about Configure a load balancer for an Always On availability group in Azure. I was going flawlessly without any error till I ran below script.

$ClusterNetworkName = “WinCluster” $IPResourceName = “MyListenerIP” $ListenerILBIP = “10.0.0.22” [int]$ListenerProbePort = 59999 Import-Module FailoverClusters Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{“Address”=”$ListenerILBIP”;”ProbePort”=$ListenerProbePort;”SubnetMask”=”255.255.255.255″;”Network”=”$ClusterNetworkName”;”EnableDhcp”=0}

Solarwinds

It failed with below long error.

Set-ClusterParameter : Parameter ‘ProbePort’ does not exist on the cluster object ‘WinCluster’. If you are trying to update an existing parameter, please make sure the parameter name is specified correctly. You can check for the current parameters by passing the .NET object received from the appropriate Get-Cluster* cmdlet to “| Get-ClusterParameter”. If you are trying to update a common property on the cluster object, you should set the property directly on the .NET object received by the appropriate Get-Cluster* cmdlet. You can check for the current common properties by passing the .NET object received from the appropriate Get-Cluster* cmdlet to “| fl *”. If you are trying to create a new unknown parameter, please use -Create with this Set-ClusterParameter cmdlet.
At line:5 char:39
+ … ourceName | Set-ClusterParameter -Multiple @{“Address”=”$ILBIP”;”Prob …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Set-ClusterParameter], ClusterCmdletException
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.FailoverClusters.PowerShell.SetClusterParameterCommand

The message says that ProbePort in not the right parameter. I initially thought that my PowerShell might be old and its doesn’t understand the parameter. This was not the cause.

WORKAROUND/SOLUTION

Actually, I was using the wrong parameter values which were causing the error. If you look closely at my command, I was using Windows Cluster Network Name in first parameter “$ClusterNetworkName”. This ideally should be “Cluster Network 1” (or a value shown by Get-ClusterNetwork).

The second mistake was “$IPResourceName” value. This should be the name of the IP Address resource, not the value shown by cluster manager UI. We need to right click on IP resource, go to properties and pick Name from there.

Once I fixed both the parameters, I was able to run the script and configure ILB correctly.

Reference: Pinal Dave (https://blog.sqlauthority.com)

Solarwinds
, , ,
Previous Post
Detect and Diagnose SQL Server Performance Issues with Spotlight Cloud
Next Post
SQL SERVER – Fix : Error Msg 1813, Level 16, State 2, Line 1 Could not open new database databasename. CREATE DATABASE is aborted

Related Posts

Leave a Reply

Menu