derhally

In your snippet, the xmlns is being added to the "AlertInfo" element. my $node_alerts = \SOAP::Data->name('ArrayOfAlertInfo')->value( SOAP::Data->name('AlertInfo')->attr({xmlns=>'http://schemas.solarwinds.com/2008/Orion'})->value( SOAP::Data->name('DefinitionId')->type('')->value($alertDefId),…

Do you have SNMP enabled on the CUCM server?

Can you try to use Fiddler to get diagnostics of the communication between the client and server. That should show us were the time is being spent.

The Global Events Summary doesn't currently let you filter by Node info. I would suggest you open a ticket for that to be added. You can however filter by event type. For example, Event.EventType > 0 AND Event.EventType < 212 which should give you node, volume, interface events. If you want to get the list of EventType…

Nothing in the logs you provided show anything that would cause the issue you are seeing. Is the Orion website still working? Where are you seeing the 403 forbidden error?

Looks like there was a disconnect between the default settings and the docs as you have noticed. Both are ok. Looks like the defaults in VoIP 2.1 are a bit more lenient than the docs.

I apologize but I'm not familiar with the python interface. If an entry didn't already exist you would have to call Create on e.g. props = { 'Instance': 'Orion.Nodes', 'InstanceId': 343, 'Latitude': 38.889963929167, 'Longitude': -77.027206420898 } results = swis.create('Orion.WorldMap.Point', **props) If a record exists,…

You can find the DB Maintenance app Start Menu -> Programs -> SolarWinds Orion -> Advanced Features or on disk at "C:\Program Files (x86)\SolarWinds\Orion\Database-Maint.exe" . Run that and check if the pollers get purged. I've asked a dev to take a look at this issue you are experiencing and see if they can reproduce it.…

Hi James, Just to be clear, you are saying the powershell script is not returning the same data as running the query in SWQL studio? Have you tried calling the PollNow verb after you create the application. The PollNow takes the application ID (integer) of the application as an argument. Zeid

Also make sure that you are using an Orion account that has the report settings properly set on the Orion side.

1) For other modules you need to join against their respective object entities. For example, with SAM you would need to join against the Oroin.APM.Application entity. Groups you would need to join against Orion.Groups entity. 2) This is something that is on our list of things to look into.

Yo won't be able to get the alert reset info since it doesn't remain in the database long enough. The alert engine will remove the record from the database immediately. If you query for an alert and it doesn't exist you can assume it has been reset.

I just spoke to the support guy and he explained to me the issue. The issue you are having with the runtime error is not fixed in the hotfix, but is definately fixed in the next release of EOC.

The status of an Orion map is determined whether EOC was able to communicate with it. It is not based on status of the nodes on that Orion server.

What account is the website running as? That should the account specified in that security policy.

What version of SAM are you using? Can you provide the values that you are passing to the SAM Unmanage verb?

Sorry, I did not realize what the MCS7828H device was refering to and I thought you were trying to add a device for IP SLA. What call manager software and version are you running on the device?

You can get a list of the verbs available by running the following SWQL query in SWQLStudio SELECT EntityName, Name AS VerbNameFROM Metadata.VerbORDER BY EntityName, VerbName In SWQL Studio verbs have the "pink cube" icon next to the names. Your call $swis Orion.NodesCustomProperties CreateCustomPropertyWithValue can be…

The Orion.ResponseTime exposes all the response time data for you. It includes daily, hourly and detail data which has not been summarized yet.

There is an issue with how the proxy is generated when using svcutil or VisualStudio that makes it not compatible with the service. You have two options to work around this issue You can either use the powershell snap-in to use the Create, Update, Delete methods or you can reference the assembly from "C:\Program…

The SWIS v3 endpoint has "v3" in the uri. Try https://<host>:17778/SolarWinds/InformationService/v3

We found an issue with the way domain accounts are handled by the powershell commandlet in the way you are using. A workaround is to use the -Trusted switch with Connect-Swis. This will authenticate with SWIS as the current logged in user.

Is the service that EOC is reporting as down, the one running on your main Orion poller? Did you have at one point additional VoIP Monitor installations when you installed IP SLA Manager?

Under the Orion Servers tab, it should show you the time when the server was last polled. This differences should never be less than the polling interval specified for that Orion server. If they are it might be that a poll is taking a long time. Does that server have a lot of Traps, Syslogs, or events?

You are referring to the ROLLUP functionality and we currently do not support that in SWQL.

You will need to import your Orion Network Atlas maps into EOC. You can find the necessary application called "Network Atlas to EOC Converter" in your Customer Portal under the "Additional Components" under the link titled "Download Orion NPM Components". The maps will show up in Network Atlas after they have been…

At this time VoIP 2.0.2 doesn't work with CUCM 6.1 and there is no workaround at the moment. We are looking into the issue.

This article should help you deal with storing/retrieving the encrypted password. http://powershell.org/wp/2013/11/24/saving-passwords-and-preventing-other-processes-from-decrypting-them/

EOC will handle unmanaged nodes in the next release. Until then you can either remove the nodes from your EOC maps or ignore them.

For alerts you can specify that the alert is only triggered if the condition exists for a certain amount of time. Setting is on the Trigger Condition page in the alert viewer. So the value of 1 means that the Alert trigger condition has been evaluated to true and that we need to wait the amount specified to check again to…