azabielski

Nice write up thank you! Here's hoping for the win!

if i could vote 1000 times for this i would.... i am right now trying to develop a service that will do the DB imports for me however i think its more complicated due to the fact it has to update the fastbit db with the new ip group segment ids once added to any existing traffic .... we need this badly.

WEEEE!!!!!!

Do you have any sort of ETA we are in the middle of cutting over to SW IPAM from an older system and not to have this feature is kind of a deal breaker.

Yeah that's my only issue is that the sam template throws the error that Invoke-Webrequest is not a cmdlet but if the server is psv4 and works locally how come SAM doesn't execute it?

Production is running 11.5.2 and the lab is 11.5.3 that's the only biggest difference

They are not the same version for sure, also looks like the production version was installed on a separate data drive but i don't think that makes much of a difference ? The one on the left is the good working server and the one on the right is not.

Yes works fine but i don't think there is anything in here PSv3 required. I also am not using any dependencies Invoke-Webrequest is a native PSv3 cmdlet

Yeah i want it in v3+ for sure , its a 2012 server so it comes with psv4

tdanner​ I dunno why i didn't think of that thanks that seems to be working now ! But i am just back to my original issue which is the Job Description error when de-serializing on the information service side. A Network Discovery job has failed to complete.\r\nState: Failed\r\nProfile id: 106.\r\nThe Job Scheduler is…

The weird thing is if i un hide it and run through those settings of the failed one but not let it do the discovery then call it from the API again it creates another job and works perfectly fine... Whats the deal here? I feel like i am missing something but it worked in my SW Lab.

NVM i found my issue i just reversed the perl script provided and found where i was formatting wrong thanks for all your help tdanner​

but you can see from the above the main npm/apm server is running PSv4....

Here is another weird issue i moved this to my production SW now and i get the following error from running the discovery any ideas? The description is set in my XML "<d2p1:Description i:nil=\"true\"/>" A Network Discovery job has failed to complete.\r\nState: Failed\r\nProfile id: 106.\r\nThe Job Scheduler is reporting…

So i did that and using the example you gave i checked and its valid json but still having issues with it.

Hey tdanner​ Thanks for jumping in on this here is the exception in that log 016-03-28 11:14:30,273 [68] ERROR SolarWinds.Orion.Core.Common.MessageUtilities - Exception caught in method ProvideFault System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1. at…

Looks like you need to be an admin account to view these resources which is awful ......

ROFL yeahhhh then they will want a legend of what that means

Boo figured as much just wanted to see if anyone had a work around

No you've been awesome thanks for the help its just weird that its only non-admin users getting this response error though

Firewall restrictions

Ok i guess that answers my question because the old Alert Manager doesn't let you get this granular but the new NPM Web Alerting does which you should've clarified. Here is the alert in the old alert manager Here is the view it looks at Here are the columns in that view that match to the above. So the real answer is that i…

aLTeReGo​ So i just tried a psv3 command in SAM and it didn't work The term 'Invoke-WebRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:16 char:25 The main poller…

Hey madhavan​ Any idea's what i could be doing wrong still? Can you provide an example of your xml maybe that i can compare to ?

Yeah i think its the XML because my model is not nullable by default if a value is not specified it will send null so that is OK and only a warning but the XML is all messed up i think that is the issue?

Well that makes more sense then however the API is throwing an error stating : Message\":\"Verb Orion.Discovery.StartDiscovery requires 1 parameters not 0 Here is the post data values changed to security purposes ... "{\"Name\":\"Discovery API…

AH Rob your killing me , upper management likes pretty colors and flashing lights

I like that however it not as flexable as sending trap messages for just specific alerts. Like we have a static down alert that plays the "Red Alert" noise from Star Trek whenever a device goes down Then the trap receiver picks it up on the other side and plays the noise configured as so

My problem is I need to have it on this engine.

Yeah i am just an idiot, but do you know why it shows up with this error when a non-admin user logs in? Report resource failed to properly initialize. »