*smacks his forehead* my eyes flipped and I said Invoke-NcSSH (for clustered Data ONTAP) instead of Invoke-NaSSH (for traditional Data ONTAP). So it looks like the cmdlet does not work with the test feature (honestly, I hadn't tried to use that feature before). I decided to create a quick command to checks the status of cluster failover and log the output. This works just fine:
--------------------------------------------
param (
[parameter(Mandatory=$true, HelpMessage="Controller")]
[string]$Controller
)
#Connect to controller
Connect-WFAController -Array $Controller
$msg=Invoke-NaSsh -Command 'cf status'
Get-WFALogger -message ("Test-"+$msg)
--------------------------------------------
18:56:16.780 INFO [Check Cf Status] ### Command 'Check Cf Status' ###
18:56:17.640 INFO [Check Cf Status] Executing command: ./Check_Cf_Status6041434406201535123.ps1 -Controller 10.101.100.30
18:56:17.687 INFO [Check Cf Status] Get-NaCredentials -Host 10.101.100.30
18:56:17.702 INFO [Check Cf Status] Credentials successfully provided for '10.101.100.30'
18:56:17.718 INFO [Check Cf Status] Connect-NaController (with credentials) -Name 10.101.100.30
18:56:18.796 INFO [Check Cf Status] Connected to controller
18:56:19.421 DEBUG [Check Cf Status] Cluster enabled, p1-3240cl2 is up.
RDMA Interconnect is up (Link 0 up, Link 1 up).
18:56:19.499 INFO [Check Cf Status] Command completed, took 2719 milliseconds