vCloud Director 9.1 – Tenant Portal displays “No Datacenters are Available” after upgrade

Posted on March 13, 2018 by Adrian Begg

vCloud Director 9.1 continues to strengthen the functionality of the tenant portal and introduces new functionality including upload of OVA/media without the Client Integration plugin. I ran into an issue immediately after the upgrade however with the Tenant Portal displaying “No Datacenters are available”.

If you are using certificates signed by an internal CA when you upgrade you may run into this issue. The issue is due to changes in enforcement of certificates in the API/Tenant Portal. The fix is pretty straight forward; you must configure the Public Key certificate chain in Base64 format against the API/Tenant portal Public Address settings if you haven’t done this (like me).

Process

Step 1. Using a Browser navigate to your vCloud Director instance and view the Public Key for the SSL Certificate (in Chrome Developer Tools > Security > View Certificate) that is assigned against the Installation and select Details > Copy to File …

Step 2. Click Next and select Base-64 encoded X.509 (.CER) and click Next and save the certificate file.

Step 3. Next select the Certificate Path and repeat this process for any certificates in the Certificate Path

Step 4. Open the .cer files generated in Notepad and copy and paste all of the Certificates into one certificate chain.

Step 5. Logon to vCloud Director as a System Administrator (via the FlexUI) and select Administration > Public Addresses, under the API (and if relevant the Tenant Portal sections) paste the certificate chain created in Step 4 into the Certificate Chain and click Apply

Step 6. Now refresh the Tenant Portal and everything should be in order.

Thanks to jm13 on the VMTN forums and Daniel Paluszek from VMWare for the information regarding this issue and resolving it. Hopefully a KB article will be published by VMWare soon.

vSAN Health PRTG Sensor

Posted on March 4, 2018 by Adrian Begg

I just wanted to create a quick post on a PRTG Network Monitoring Sensor that I created to provide some monitoring for vSAN deployed in my Lab. The script is not extensively tested as I am just using it in the Lab however hopefully you will get some value from it. The sensor performs an Invoke of a vSAN Health check against a VSAN cluster and reports any failures or warnings for components.

The sensor is available from my Github and uses a module from Roman Gelman (@rgelman75) VSAN.psm1 which is available from here.

Sensor Setup

Download PRTG-vSphere-vSANealth.ps1 from here and place it in C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\ on your Probe
Download the prtg.customlookups.vsan.status.ovl from here (Custom Lookup for PRTG) and place this file in C:\Program Files (x86)\PRTG Network Monitor\lookups\custom\ on your Central Probe
Download VSAN.psm1 from here and place this in C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML\ on your Probe
Logon to PRTG and select Setup > Administrative Tools > Load Lookup and File Lists

5. Next against your vCenter device create a new Sensor of type EXE/Script Advanced

6. Enter the following parameters and then click Continue to finish the setup:

Sensor Name: The name of the sensor (e.g. VSAN Cluster Status – Development)
EXE/Script: PRTG-vSphere-vSANHealth.ps1
Parameters: -vCenterServer “<FQDN of your vCenter>” -vSANCluster “<Name of the VSAN Cluster>”
Security Context: Use Windows Credentials of parent device
Timeout (Sec): 300

After configuration it should start reporting the status and you can setup notifications, monitoring frequency and channel limits as desired.

Troubleshooting

The User executing the scripts (the Windows account specified in PRTG) must have sufficient rights to the vCenter Server
PRTG runs all PowerShell scripts under the 32-bit image; this will cause PowerCLI not to run unless the modules are installed under the x86 Modules folder. The easiest way to fix this is to run: Save-Module -Name VMware.PowerCLI -Path SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\Modules\
If you encounter a number of virtual machines in your enviornment “vsan-healthcheck-disposable….” in your environment this is due to the Timeout value (which is statically set to 2 seconds) not being high enough in the VSAN.psm1 module; find any references to VsanQueryVcClusterHealthSummary and replace the Integer 2 with something higher (eg. 30 seconds)

The Code

###############################################################################################
# Name: PRTG-vSphere-vSANealth.ps1
# Author: Adrian Begg (adrian.begg@ehloworld.com.au)
#
# Date: 03/03/2018
# Purpose: The purpose of the script is to provide a simple VSAN Health Check sensor
# for PRTG Network Monitoring.
#
# Requires: Roman Gelman (@rgelman75) VSAN.psm1 available at https://github.com/rgel/PowerCLi
###############################################################################################
[CmdletBinding()]
Param(
    [ValidateNotNullorEmpty()] [Parameter(Mandatory=$True)] [string] $vCenterServer,
    [ValidateNotNullorEmpty()] [Parameter(Mandatory=$True)] [string] $vSANCluster
)

#Functions
Function Write-PRTGError{
    <#
    .SYNOPSIS
    Returns an error which can be read by PRTG.

    .DESCRIPTION
    Returns an error which can be read by PRTG.

    .PARAMETER ErrorMessage
    A string which will be displayed to the user as an error message in PRTG.

    .EXAMPLE
    Write-PRTGError -ErrorMessage "An error occured running the sensor against the machine LABADDS1."

    Returns XML formated as requried by PRTG with the error message "An error occured running the sensor against the machine LABADDS1."

	.NOTES
	  NAME: Write-PRTGError
	  AUTHOR: Adrian Begg
	  LASTEDIT: 2018-01-22
	#>
    Param(
        [ValidateNotNullorEmpty()] [Parameter(Mandatory=$True)] [string] $ErrorMessage
    )
    Write-host "<?xml version=`"1.0`" encoding=`"Windows-1252`" ?>"
    write-host "<prtg>"
    Write-Host "<error>1</error>"
    Write-Host "<text>$ErrorMessage</text>"
    write-host "</prtg>"
    Break
    #Exit
}
function Write-PRTGSensor(){
    <#
    .SYNOPSIS
    Returns a PRTG Sensor constructed from channels created using the New-PRTGChannel cmdlet

    .DESCRIPTION
    Long description

    .PARAMETER PRTGChannels
    A collection of strings created using the New-PRTGChannel cmdlet

    .PARAMETER Message
    An option message to display with the channel (eg. "SMTP/tLS connection Successful with 200.")

    .EXAMPLE
    Write-PRTGSensor -PRTGChannels $prtgChannels

    Will output a correctly formed PRTG sensor formed from the PRTG Channels in the String collection $prtgChannels

    .NOTES
	  NAME: Write-PRTGSensor
	  AUTHOR: Adrian Begg
	  LASTEDIT: 2018-02-09
	#>
    #>
    Param(
        [ValidateNotNullOrEmpty()] [Parameter(Mandatory=$true)] [string[]] $PRTGChannels,
        [Parameter(Mandatory=$false)] [string] $Message
    )

    # Write the header for the PRTG sensor
    [string] $strPRTGOutput = "<?xml version=`"1.0`" encoding=`"Windows-1252`" ?>`n<prtg>`n"
    $strPRTGOutput += "<text>$Message</text>`n"

    # Construct from each of the provided channels the output
    foreach($strChannel in $PRTGChannels){
        $strPRTGOutput += $strChannel
    }
    # Write the trailer for the sensor
    $strPRTGOutput += "</prtg>"
    # Outputs the PRTG sensor to the console
    Write-Host $strPRTGOutput
}

function New-PRTGChannel(){
    <#
    .SYNOPSIS
    Returns a channel in XML format for a PRTG Sensor

    .DESCRIPTION
    Creates a channel for a PRTG Advanced XML/EXE sensor with the custom data provided.

    .PARAMETER Name
    The name of the channel

    .PARAMETER Value
    The Interger Value of the channel

    .PARAMETER ValueLookup
    A valid PRTG Lookup Type eg. oid.paessler.custom.windows.scheduledTaskStatus

    .PARAMETER LimitErrorMsg
    The error message to display when the channel exceeds the defined error limits. WARNING: This can not be set dynamically; the first set value is retained in PRTG

    .PARAMETER LimitWarningMsg
    The warning message to display when the channel exceeds the defined warning limits. WARNING: This can not be set dynamically; the first set value is retained in PRTG

    .PARAMETER LimitMaxError
    If the "Value" is higher then the "LimitMaxError" the channel will be marked as in an Error state and the defined LimitErrorMsg will be displayed for this sensor. The parent sensor will also go into an error state.

    NOTE: This value is not dynamic; if this value is provided the first value that PRTG recieves when the channel is created is the value that will persist forever. Generally it is recommended that instead of using these parameters that the channel settings are manually set.

    .PARAMETER LimitMinError
    If the "Value" is lower then the "LimitMinError" the channel will be marked as in an Error state and the defined LimitErrorMsg will be displayed for this sensor. The parent sensor will also go into an error state.

    NOTE: This value is not dynamic; if this value is provided the first value that PRTG recieves when the channel is created is the value that will persist forever. Generally it is recommended that instead of using these parameters that the channel settings are manually set.

    .PARAMETER LimitMaxWarn
    If the "Value" is higher then the "LimitMaxWarn" the channel will be marked as in an Warning state and the defined LimitWarningMsg will be displayed for this sensor. The parent sensor will also go into an Warning state.

    NOTE: This value is not dynamic; if this value is provided the first value that PRTG recieves when the channel is created is the value that will persist forever. Generally it is recommended that instead of using these parameters that the channel settings are manually set.

    .PARAMETER LimitMinWarn
    If the "Value" is lower then the "LimitMinWarn" the channel will be marked as in an Warning state and the defined LimitWarningMsg will be displayed for this sensor. The parent sensor will also go into an Warning state.

    NOTE: This value is not dynamic; if this value is provided the first value that PRTG recieves when the channel is created is the value that will persist forever. Generally it is recommended that instead of using these parameters that the channel settings are manually set.

    .EXAMPLE
    New-PRTGChannel -Name "Disk Status" -Value 20 -ValueLookup "oid.paessler.custom.hardware.diskstatus"

    Returns a PRTG Channel named "Disk Status" with a custom lookup type of "oid.paessler.custom.hardware.diskstatus" and a value of 20.

   .EXAMPLE
    New-PRTGChannel -Name "Disk Status" -Value 20 -ValueLookup "oid.paessler.custom.hardware.diskstatus" -LimitErrorMsg "The disk status is bad." -LimitWarningMsg "The disk status is getting bad." -LimitMaxError 25 -LimitMinError -1 -LimitMaxWarn 21 -LimitMinWarn 0

    Returns a PRTG Channel named "Disk Status" with a custom lookup type of "oid.paessler.custom.hardware.diskstatus" and a value of 20. The channel also has the channel Warning/Error limits set. These will be addative with the limits defined in the Custom Lookup. It is not recommended that these are defined unless required; the Error/Warning state can be controlled using the Custom Lookup type metadata.

    .EXAMPLE
    New-PRTGChannel -Name "Disk Status" -Value 10
    Returns a PRTG Channel named "Disk Status" with a value of 20.

    .EXAMPLE
    New-PRTGChannel -Name "Disk Status" -Value 10
    Returns a PRTG Channel named "Disk Status" with a value of 20.

    .NOTES
	  NAME: New-PRTGChannel
	  AUTHOR: Adrian Begg
	  LASTEDIT: 2018-02-09
	#>
    Param(
		[Parameter(Mandatory=$True,ParameterSetName = "ValueLookup")]
        [Parameter(Mandatory=$True,ParameterSetName = "Default")]
            [ValidateNotNullorEmpty()] [string] $Name,
            [ValidateRange(0,2147483647)] [int] $Value,
        [Parameter(Mandatory=$True,ParameterSetName = "ValueLookup")]
            [ValidateNotNullorEmpty()] [string] $ValueLookup,
        [Parameter(Mandatory=$False,ParameterSetName = "Default")]
            [ValidateNotNullorEmpty()] [string] $LimitErrorMsg,
        [Parameter(Mandatory=$False,ParameterSetName = "Default")]
            [ValidateNotNullorEmpty()] [string] $LimitWarningMsg,
        [Parameter(Mandatory=$False,ParameterSetName = "Default")]
            [ValidateRange(0,2147483647)] [int] $LimitMaxError,
        [Parameter(Mandatory=$False,ParameterSetName = "Default")]
            [ValidateRange(0,2147483647)] [int] $LimitMinError,
        [Parameter(Mandatory=$False,ParameterSetName = "Default")]
            [ValidateRange(0,2147483647)] [int] $LimitMaxWarn,
        [Parameter(Mandatory=$False,ParameterSetName = "Default")]
            [ValidateRange(0,2147483647)] [int] $LimitMinWarn
    )
    # Initalise the XML
    [string] $strPRTGChannel += "<result>`n<channel>$Name</channel>`n<unit>Custom</unit>`n<showChart>1</showChart>`n<showTable>1</showTable>"
    if($PSCmdlet.ParameterSetName -in ("ValueLookup")){
        $strPRTGChannel += "<value>$Value</value>`n<ValueLookup>$ValueLookup</ValueLookup>`n"
    } else {
        if($PSBoundParameters.ContainsKey("LimitMaxError")){
            $strPRTGChannel += "<LimitMaxError>$LimitMaxError</LimitMaxError>`n"
        }
        if ($PSBoundParameters.ContainsKey("LimitMinError")){
            $strPRTGChannel += "<LimitMinError>$LimitMinError</LimitMinError>`n"
        }
        if ($PSBoundParameters.ContainsKey("LimitMaxWarn")){
            $strPRTGChannel += "<LimitMaxWarning>$LimitMaxWarn</LimitMaxWarning>`n"
        }
        if ($PSBoundParameters.ContainsKey("LimitMinWarn")){
            $strPRTGChannel += "<LimitMinWarning>$LimitMinWarn</LimitMinWarning>`n"
        }
        if(!([string]::IsNullOrEmpty($LimitErrorMsg))){
            $strPRTGChannel += "<LimitErrorMsg>$LimitErrorMsg</LimitErrorMsg>`n"
        }
        if(!([string]::IsNullOrEmpty($LimitWarningMsg))){
            $strPRTGChannel += "<LimitWarningMsg>$LimitWarningMsg</LimitWarningMsg>`n"
        }
        # Add the values
        $strPRTGChannel += "<float>0</float>`n<value>$Value</value>`n"
    }
    # Write the trailer and return the string
    $strPRTGChannel += "</result>"
    $strPRTGChannel
}
Function Main{
    # Decalre a Hashtable for the Lookup Table Translations
    [HashTable] $prtgStatus = @{
        Green = 1
        Yellow  = 2
        Red = 3
        Unknown = 0
    }
    # Check if PowerCLI is installed on the machine running the cmdlet
    try {
        #Check installedmodule
        If ((Get-module -Name VMware.PowerCLI -ErrorAction SilentlyContinue) -eq $null){
            Import-Module VMware.PowerCLI -ErrorAction Stop
        }
    } catch {
        Write-PRTGError -ErrorMessage "Unable to load PowerCLI Modules. Please ensure PowerCLI is installed on the Probe running the sensor."
    }
        # Check if the VSAN Modile is installed in the current directory
    try {
        Import-Module "$PSScriptRoot\VSAN.psm1" -ErrorAction Stop
    } catch {
        Write-PRTGError -ErrorMessage "Unable to load Roman Gelman's VSAN Module. Please ensure that the file is in the working directory of the script."
    }

    # Attempt the connect to vCenter, uses the account of the Windows Credentials running the cmdlet
    try {
        Connect-VIServer $vCenterServer -WarningAction SilentlyContinue -ErrorAction Stop | out-null
    } catch {
        Write-PRTGError -ErrorMessage "Failed to connect to vCentre server $($vCenterServer)"
    }

    # Next try and query the vCenter for the VSAN Cluster
    try {
        $objCluser = Get-Cluster -Name $vSANCluster
    } catch {
        Write-PRTGError -ErrorMessage "An error occured when querying the Cluster $($vSANCluster) on vCenter $($server)"
    }
    try{
        # Get the Health Summary
        $objvSANSummary = Get-VSANHealthSummary -Cluster $objCluser
        $colVSANHealthTest = Invoke-VSANHealthCheck -Cluster $objCluser -Level "Test"
        $colVSANHealthOverview = Invoke-VSANHealthCheck -Cluster $objCluser
        $colvSANDisks = Get-VsanDiskGroup -Cluster $objCluser
        $vSANFreeSpace = Get-VsanSpaceUsage -Cluster $objCluser
    } catch {
        Write-PRTGError -ErrorMessage "An error occured when querying the VSAN Objects for Health Status"
    }

    # Construct the Channels for the cluster
    [System.Collections.ArrayList] $arrChannels = New-object System.Collections.Arraylist
    [string] $strSensorMessage = ""

    $channelFreeDiskSpace = New-PRTGChannel -Name "$($objvSANSummary.Cluster) - Free Disk Space (GB)" -Value $vSANFreeSpace.FreeSpaceGB
    $arrChannels.Add($channelFreeDiskSpace) > $null
    $channelDiskTotal = New-PRTGChannel -Name "$($objvSANSummary.Cluster) - VSAN Capacity (GB)" -Value $vSANFreeSpace.CapacityGB
    $arrChannels.Add($channelDiskTotal) > $null
    $channelOverallHealth = New-PRTGChannel -Name "$($objvSANSummary.Cluster) - Overall Health" -Value ($prtgStatus.($objvSANSummary.OverallHealth)) -ValueLookup "prtg.customlookups.vsan.status"
    $arrChannels.Add($channelOverallHealth) > $null

    foreach($objGroup in $colVSANHealthOverview){
        if($objGroup.TestGroup.StartsWith("Online health")){
            $strTestName = "Online health"
        } else {
            $strTestName = $objGroup.TestGroup
        }
        $channelHealthOverview = New-PRTGChannel -Name "$($objGroup.Cluster) - $strTestName" -Value ($prtgStatus.($($objGroup.Health))) -ValueLookup "prtg.customlookups.vsan.status"
        $arrChannels.Add($channelHealthOverview)  > $null
    }

    # Now get the messagses for any tests that failed
    $colFailedChecks = $colVSANHealthTest | ?{$_.Health -notin ("Green","Skipped")}
    foreach($objTest in $colFailedChecks){
        $strSensorMessage += "[VSAN Cluster:$($objTest.Cluster) - $($objTest.Test):$($objTest.Health)] "
    }

    # Write a channel for each disk in the vSAN Cluster
    foreach($objVSANDiskGroup in $colvSANDisks){
        # Report the status of the Capacity Tier Disks
        foreach($objCapacityDisk in $objVSANDiskGroup.ExtensionData.NonSsd){
            # Need to Sanitise the DG name to reduce the size of the channel name
            $strChannelName = "[$($objVSANDiskGroup.VMHost.Name)] VSAN Disk Status (UUID: $($objCapacityDisk.VSANDiskInfo.VSAnUuid))"
            $intDiskStatus = 0
            if($objCapacityDisk.OperationalState -eq "ok"){
                $intDiskStatus = 1
            } elseif($objCapacityDisk.OperationalState -eq "degraded") {
                $intDiskStatus = 3
            }
            $channelDiskHealth = New-PRTGChannel -Name $strChannelName -Value $intDiskStatus -ValueLookup "prtg.customlookups.vsan.status"
            $arrChannels.Add($channelDiskHealth)  > $null

            $prtgStatus.($objCapacityDisk.OperationalState)
        }
        # Report the status of the Flash Tier Disks
        foreach($objFlashCacheDisk in $objVSANDiskGroup.ExtensionData.Ssd){
            $strChannelName = "[$($objVSANDiskGroup.VMHost.Name)] VSAN Disk Status (UUID: $($objFlashCacheDisk.VSANDiskInfo.VSAnUuid))"
            $intDiskStatus = 0
            if($objFlashCacheDisk.OperationalState -eq "ok"){
                $intDiskStatus = 1
            } elseif($objFlashCacheDisk.OperationalState -eq "degraded") {
                $intDiskStatus = 3
            }
            $channelDiskHealth = New-PRTGChannel -Name $strChannelName -Value $intDiskStatus -ValueLookup "prtg.customlookups.vsan.status"
            $arrChannels.Add($channelDiskHealth)  > $null
        }
    }
    # Trim the trailing space
    $strSensorMessage = $strSensorMessage.TrimEnd(" ")
    Write-PRTGSensor -PRTGChannels $arrChannels -Message $strSensorMessage
    Disconnect-VIServer -Confirm:$false
}

# Call the Main Method
Main

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

###############################################################################################

# Name: PRTG-vSphere-vSANealth.ps1

# Author: Adrian Begg (adrian.begg@ehloworld.com.au)

# Date: 03/03/2018

# Purpose: The purpose of the script is to provide a simple VSAN Health Check sensor

# for PRTG Network Monitoring.

# Requires: Roman Gelman (@rgelman75) VSAN.psm1 available at https://github.com/rgel/PowerCLi

###############################################################################################

[CmdletBinding()]

Param(

[ValidateNotNullorEmpty()] [Parameter(Mandatory=$True)] [string] $vCenterServer,

[ValidateNotNullorEmpty()] [Parameter(Mandatory=$True)] [string] $vSANCluster

)

#Functions

Function Write-PRTGError{

.SYNOPSIS

Returns an error which can be read by PRTG.

.DESCRIPTION

Returns an error which can be read by PRTG.

.PARAMETER ErrorMessage

A string which will be displayed to the user as an error message in PRTG.

.EXAMPLE

Write-PRTGError -ErrorMessage "An error occured running the sensor against the machine LABADDS1."

Returns XML formated as requried by PRTG with the error message "An error occured running the sensor against the machine LABADDS1."

.NOTES

NAME: Write-PRTGError

AUTHOR: Adrian Begg

LASTEDIT: 2018-01-22

Param(

[ValidateNotNullorEmpty()] [Parameter(Mandatory=$True)] [string] $ErrorMessage

)

Write-host "<?xml version=`"1.0`" encoding=`"Windows-1252`" ?>"

write-host "<prtg>"

Write-Host "<error>1</error>"

Write-Host "<text>$ErrorMessage</text>"

write-host "</prtg>"

Break

#Exit

}

function Write-PRTGSensor(){

.SYNOPSIS

Returns a PRTG Sensor constructed from channels created using the New-PRTGChannel cmdlet

.DESCRIPTION

Long description

.PARAMETER PRTGChannels

A collection of strings created using the New-PRTGChannel cmdlet

.PARAMETER Message

An option message to display with the channel (eg. "SMTP/tLS connection Successful with 200.")

.EXAMPLE

Write-PRTGSensor -PRTGChannels $prtgChannels

Will output a correctly formed PRTG sensor formed from the PRTG Channels in the String collection $prtgChannels

.NOTES

NAME: Write-PRTGSensor

AUTHOR: Adrian Begg

LASTEDIT: 2018-02-09

Param(

[ValidateNotNullOrEmpty()] [Parameter(Mandatory=$true)] [string[]] $PRTGChannels,

[Parameter(Mandatory=$false)] [string] $Message

)

# Write the header for the PRTG sensor

[string] $strPRTGOutput = "<?xml version=`"1.0`" encoding=`"Windows-1252`" ?>`n<prtg>`n"

$strPRTGOutput += "<text>$Message</text>`n"

# Construct from each of the provided channels the output

foreach($strChannel in $PRTGChannels){

$strPRTGOutput += $strChannel

}

# Write the trailer for the sensor

$strPRTGOutput += "</prtg>"

# Outputs the PRTG sensor to the console

Write-Host $strPRTGOutput

}

function New-PRTGChannel(){

.SYNOPSIS

Returns a channel in XML format for a PRTG Sensor

.DESCRIPTION

Creates a channel for a PRTG Advanced XML/EXE sensor with the custom data provided.

.PARAMETER Name

The name of the channel

.PARAMETER Value

The Interger Value of the channel

.PARAMETER ValueLookup

A valid PRTG Lookup Type eg. oid.paessler.custom.windows.scheduledTaskStatus

.PARAMETER LimitErrorMsg

The error message to display when the channel exceeds the defined error limits. WARNING: This can not be set dynamically; the first set value is retained in PRTG

.PARAMETER LimitWarningMsg

The warning message to display when the channel exceeds the defined warning limits. WARNING: This can not be set dynamically; the first set value is retained in PRTG

.PARAMETER LimitMaxError

If the "Value" is higher then the "LimitMaxError" the channel will be marked as in an Error state and the defined LimitErrorMsg will be displayed for this sensor. The parent sensor will also go into an error state.

NOTE: This value is not dynamic; if this value is provided the first value that PRTG recieves when the channel is created is the value that will persist forever. Generally it is recommended that instead of using these parameters that the channel settings are manually set.

.PARAMETER LimitMinError

If the "Value" is lower then the "LimitMinError" the channel will be marked as in an Error state and the defined LimitErrorMsg will be displayed for this sensor. The parent sensor will also go into an error state.

.PARAMETER LimitMaxWarn

If the "Value" is higher then the "LimitMaxWarn" the channel will be marked as in an Warning state and the defined LimitWarningMsg will be displayed for this sensor. The parent sensor will also go into an Warning state.

.PARAMETER LimitMinWarn

If the "Value" is lower then the "LimitMinWarn" the channel will be marked as in an Warning state and the defined LimitWarningMsg will be displayed for this sensor. The parent sensor will also go into an Warning state.

.EXAMPLE

New-PRTGChannel -Name "Disk Status" -Value 20 -ValueLookup "oid.paessler.custom.hardware.diskstatus"

Returns a PRTG Channel named "Disk Status" with a custom lookup type of "oid.paessler.custom.hardware.diskstatus" and a value of 20.

.EXAMPLE

New-PRTGChannel -Name "Disk Status" -Value 20 -ValueLookup "oid.paessler.custom.hardware.diskstatus" -LimitErrorMsg "The disk status is bad." -LimitWarningMsg "The disk status is getting bad." -LimitMaxError 25 -LimitMinError -1 -LimitMaxWarn 21 -LimitMinWarn 0

Returns a PRTG Channel named "Disk Status" with a custom lookup type of "oid.paessler.custom.hardware.diskstatus" and a value of 20. The channel also has the channel Warning/Error limits set. These will be addative with the limits defined in the Custom Lookup. It is not recommended that these are defined unless required; the Error/Warning state can be controlled using the Custom Lookup type metadata.

.EXAMPLE

New-PRTGChannel -Name "Disk Status" -Value 10

Returns a PRTG Channel named "Disk Status" with a value of 20.

.EXAMPLE

New-PRTGChannel -Name "Disk Status" -Value 10

Returns a PRTG Channel named "Disk Status" with a value of 20.

.NOTES

NAME: New-PRTGChannel

AUTHOR: Adrian Begg

LASTEDIT: 2018-02-09

Param(

[Parameter(Mandatory=$True,ParameterSetName = "ValueLookup")]

[Parameter(Mandatory=$True,ParameterSetName = "Default")]

[ValidateNotNullorEmpty()] [string] $Name,

[ValidateRange(0,2147483647)] [int] $Value,

[Parameter(Mandatory=$True,ParameterSetName = "ValueLookup")]

[ValidateNotNullorEmpty()] [string] $ValueLookup,