cluster count not working in 3.5

[a2alpha]

Hi, I am running a script on a vSphere environment and when using the following line it works fine however when I run it on 3.5 it just leaves a blank. When running the line direct in the vi-toolkit it doesn't return anything suggesting that count is not an option.

$cluster = get-cluster

$cluster.count

Is there an alternative method of counting the number of clusters which would work for both vSphere and 3.5.

Thanks,

Dan

[LucD · Accepted solution]

This should work on 3.5 and vSphere.

Could it be that you only have 1 cluster in your 3.5 environment ?

In that case Get-Cluster won't return an array and you won't have the Count property.

You can do

(Get-Cluster | Measure-Object).Count

[alanrenouf]

You can also force it to be an array:

$cluster = @{get-cluster}
$cluster.count

If you found this information useful, please consider awarding points for Correct or Helpful.

Alan Renouf

http://virtu-al.net

[LucD]

Please ignore, original text removed.

[a2alpha]

$ESXhost = get-vmhost <host> | get-view

$ESXHost.config.firewall.defaultPolicy.outgoingBlocked

When I run the esxcfg-firewall -allowOutgoing, the above still yields a true response. Is there a way to update it or am I querying the wrong part.

Thanks for the cluster part, works fine now.

Dan

[LucD]

The properties of the variable $ESXHost are not automatically updated.

You can force a refresh with

$ESXHost.UpdateViewData()

[a2alpha]

Thanks for that, although it still gives a true response. Looking at the name though it looks like it is for the default policy rather than the current status.

Is there a way of querying whether the firewall has been set to allowOutgoing and allowIncoming?

Thanks,

[LucD]

Afaik there is no specific method to query that info.

The HostFirewallDefaultPolicy object, in which you find the incomingBlocked and outgoingBlocked properties, defines the actions the FW will take for all traffic for which there is no specific rule.

The FW first checks the rules.

If there is no rule that covers that specific type of traffic, the FW takes the default action.

[a2alpha]

Thanks for all your help and thanks for the info.

Dan