mkomeara ✭✭✭✭✭

Negative conditions have been requested since 2010. Is this feature on a roadmap for inclusion in the Dynamic Query? I can select nodes that "Start with" or "Contain" certain values, but can't exclude nodes that "Start with" or "Contain" certain values. Example; Caption Begins with "Widget" Caption Contains "Plastic"…

Or keep using Report Writer. The web reports are too simple and inflexible for many customers.

Does anyone know if this was ever solved? I'm trying to show the status of disk arrays in an email alert based on my UnDP that's interrogating Dell OpenManage for the physical disk array members' status. All the email alert shows me is the status of the first item in the tabular data. It displays correctly in the Tabular…

Where is the documentation?

Is there a document that describes the properties for the different entity types? There is a table in the documentation that describes the properties for the Orion.Nodes entity type, but I don't see one for the Orion.Pollers entity type. I see an entry called Status that's set to 0. If the interface is up, shouldn't that…

I added a Cisco 831 router node with Custom Properties and the Response Time poller (Poller_RT) poller and Cisco Poller (Poller_CR), and added three interfaces each with a Traffic poller (Poller_IT) and an Errors poller (Poller_IE) but it's not working right. If I look at node details, there is a lot of information…

Where does the InterfaceID come from? Is it automatically defined when an interface is added? Do I have to interrogate Orion to get it? If so, how would I do that?

So far so good. That worked. One more question (for now). When adding pollers to the interfaces, what value goes in place of the InterfaceID? # register specific pollers for the node # Interface Traffic $poller = @{ PollerType="Poller_IT"; NetObject="I:"+$ifaceProps["InterfaceID"] } $pollerUri = New-SwisObject $swis…

That was it. I removed the NodeID entry and the DisplayName and Description entries and it ran correctly. Next item - I need to add interfaces, so can I add all three interfaces at once like this; $newIfaceProps = @{ NodeID=$nodeId; # NodeID on which the interface is working on InterfaceName="Ethernet0"; InterfaceIndex=1;…

Here's what I'm seeing; 1. I create an IP Address Groups by filling in the blanks. The web interface times out and I have to log out and log in to see the new group. What can I change so this doesn't happen? 2. In the NetFlow Summary window, I go to Traffic View Builder and select IP Address Group (10.2.52.0-10.2.52.255)…

We need AD integration also. Thanks

We would like to do this as well. Has anyone discovered a way to do it?

Other than having to manually end the NetPerfMon.exe process every time the install process tries to stop it, everything went well. Thanks for the info!

The interface shows up in the Interfaces table. Here is my Powershell code for adding the interface and pollers; # add interface and pollers for Ethernet0 $nodeId = "2395" $newIfaceProps = @{ NodeID=$nodeId; InterfaceName="Ethernet0"; InterfaceIndex=1; ObjectSubType="SNMP"; Status=1; } $newIfaceUri = New-SwisObject $swis…

Here it is. I thought maybe it was rejecting the "True" and "False" values for the Custom Properties, so I changed them to $True and $False, but it didn't change the result.; PS H:\> rver PSMessageDetails : Exception : System.ServiceModel.FaultException: Update failed, check fault information. Server stack trace: at…

I'm using SDK 1.4 and have the same issue. I successfully added the node and five node pollers, then added the Custom Properties. Then I added one interface which shows up in the web interface, but when I query the Pollers table, there aren't any interface pollers listed for that node.

I deleted all my IP Address Groups and added one back in for 10.1.1.0-10.1.1.255. When I go to Database Manager and query entries in the IPAddressGroups table, there is only one entry, but its IPAddressGroupID is 18. When I query the FlowCorrelation table for IP addresses in the same range, those records show an…

The problem is I have about 600 subnets that I may want to pull stats on separately. For example, site A (10.1.1.0/24) complains of slow response across the WAN. So I want to see the NetFlow numbers for the top Bytes sorted descending. Do I have to define all 600 IP Address Groups separately? If so is there a way to do it…

Should I uninstall the current 3.0 version before installing the NetFlow 3.1 software? The only guidance the manual gives is; If you are upgrading from Orion NetFlow Traffic Analyzer version 1.0, you must first uninstall 1.0 before installing the current release.

This would be very useful to us also.

Was there ever a resolution to this problem? I get this error when I log into the Admin account, which displays the Current Top Ten Lists as the Home Page View. Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30;…

Is this on the known roadmap yet? Or we could make better use of the Basic Alerts if it allowed selection of Monitored Network Objects using Custom Properties fields. Thanks!

Following the example in the book for setting the Custom Properties of the node, everything seems to be set correctly. But when I issue the Set-SwisObject command it errors out; PS H:\> $nodeId 2373 PS H:\> $customProps = @{ >> Comments="Franchise Router"; >> NodeID=$nodeId; >> Building="Franchise"; >> Country="USA"; >>…

I'm in agreement with rcahill. For the forseeable future, the box serial number is the only thing of interest. Future interest would be in installable parts such as cards in slots, chassis stack serial numbers, memory and flash size, etc. Right now when I run a Physical Entities (Serial Number) report I get multiple lines…

Is there feature/function information available for the new support?

All this does is slow someone down. The user can still go to the Config Archive and see the passwords and keys in the configurations. The security built into NCM needs to be enhanced. Removing the check box doesn't fix anything.

Is that same capability available for the hover action on a node?

I have three groups defined already; 10.1.1.0-10.1.1.255, 172.0.0.0-172.255.255.255, and 192.168.0.0-192.168.255.255, but when I try to add group 10.1.2.0-10.1.2.255, it says this; * IP address groups may overlap but cannot be nested within another group. An IP address group already exists that is nested with the IP…

Will the node and interface hover capability be added this year or beyond? We are very much interested in being able to get more info on a node by hovering without having to open the node view. This would help our NOC respond more quickly to outages.

Here's what I found about IP Address Groups;