Force a custom property to auto set to a default level

Question

Background : We have an interface priority custom property to allow differing types of interface or based on clients whims, to alert into our ITSM at the assigned level. 
 The Issue : we need to find a way to automate interfaces being added as a P4, whether it's a brand new piece of kit or just an extra interface on a single device being enabled. 
 The problem : I don't know how best to automate this. 
 
 I can easily set up a report to send me any interfaces that aren't assigned to P2, P3 or P4 but that's manual and reactive, and relies on me being in. 
 
 Ideally I'd like to have a job ( ?I guess? ) run that finds any interface that doesn't have a priority assigned and change it to P4. This job would run daily in the small hours, as it is rare an interface added today will be in support the same day or even less likely that it will alert. 
 But I have no idea where to start building a script that would do this for me, or even if a job is the right approach. An alert might be a better approach and it 'fixes' the issue within minutes - but it is still the issue of how to do the fix that I don't have a clue about. 
 Suggestions? Anybody already done this on another CP that I can edit to our needs?

stuartd · Accepted Answer

Thank you jm_sysadmin and christopher.t.jones123 for your advice, help and suggestions. I truly appreciate you've taken time out of your day to help this old IT plodder. The Good News: I have it all up and working. 
 The Even Better News: I didn't have to touch a single bit of scripting 
 I discovered the solution whilst working on an alert for something else. It's the old "the name will come to me" and then at 3am several weeks later you wake and yell out 'John Smith' and your partner looks at you like you're a madman feeling :) 
 Anyway, for the benefit of others that may come this way. 
 Build a new alert and set the trigger condition like this: 
 
 Yes, you could get all fancy and build in a 'is not equal to' and add in each of your priorities, but we don't care about that bit and just need it set to a value which is one of our pre-determined ones. [the reason for the priority being so important is that it is one of the variables that gets pushed in to BMC to raise an Incident. If the variables are in the wrong order or blank, then BMC silently drops the alert and does nothing - erm, not good] 
 Anyway, set your time constraints as desired - I left mine for testing purposes at 1m but have now set it to evaluate every 1hr but could even change that to daily. 
 Zip through to the the trigger actions and 'add a new action' and THERE, right at the top of the list is: "Change Custom Property" = WT Actual ... why have I never spotted that before. anyway, select and configure thus: 
 
 Before committing this to be let loose I checked in SWQL (using the code that the trigger condition generated) which advised 59 interfaces added overnight had no priority and manage custom properties also confirmed that same number. I also checked a couple of the interfaces and sure enough none of them had the priority set. So to make sure the code was seeing the right interfaces, I manually set one to reduce my number to 58 and sure enough the SWQL query, manage CP's box and the alert summary all confirmed 58. 
 Commit and wait a minute or so and re-check. Happy days, I have no interfaces without a priority set. 
 RESULT . 
 Final edit of the alert was to add a netperfmon entry trigger for auditability purposes and set the evaluate condition to 60m.

jm_sysadmin · Answer

Yes, we do a fair amount of this. I didn't have any on the interfaces, so I modified a script I had for servers. That means I didn't test it, so please do that, and shout at me if you get stuck making it work. Update the parts for your server and your property name, and I hope its close to what you need. 
 
 $SwisServer = 'orion.yourdomain.com'
$CustomPropertyName = 'Severity'
Try {
	Import-Module SwisPowerShell
} Catch {
	Write-Host "Message: $($Error[0])";
	Exit 1;
}
Try {
	$swis = Connect-Swis -Certificate
} Catch {
	$Creds = Get-Credential
	$Swis = Connect-Swis $SwisServer -Credential $Creds
}

$queryInterfacesWithNoSysID = "SELECT ICP.$CustomPropertyName, ICP.Uri FROM Orion.NPM.InterfacesCustomProperties ICP Where ICP.$CustomPropertyName is Null or ICP.$CustomPropertyName not like 'P2' or ICP.$CustomPropertyName not like 'P3' or ICP.$CustomPropertyName not like 'P4'"
$InterfacesWithNoProperty = Get-SwisData $swis -query $queryInterfacesWithNoSysID

ForEach ($Interface In $InterfacesWithNoProperty) {
	$uri = $Interface.uri
	$CustomProps = @{
 $CustomPropertyName = 'P4';
	}
	Set-SwisObject $swis -Uri $uri -Properties $CustomProps
}

Force a custom property to auto set to a default level

Top Replies