The most recent content from our members.
The network discovery page (/Orion/Discovery/Default.Aspx) is super outdated. The page really, really needs an update. What I'd like to see is: Customizable fields of display data (such as displaying information from the Orion.DiscoveryProfiles table), including things like: # of nodes found, # of nodes changed, # of…
I have an environment that is very segmented, requiring multiple PEs to reach the various networks. I would like to be able to select "All Pollers" when doing a network discovery. If my IP doesn't respond using poller01, try with poller02, then 03. I have 7 pollers, and have to run a different discovery for each PE to go…
When we auto-discover Linux systems we have both shared memory and cached memory disks in the device; however, we do not want to discover these components. At the moment we can only select the options listed under Auto discovery -> volumes tab ( choose what to monitor). Currently the auto-discovery feature allows a user to…
What I'd like to propose is that we are able to do a list resources for similar hardware at the same time, so that we can add a checkbox for a particular type of resource to be enabled across all of that hardware. Example: Say you are intending to do list resources for 8 Windows 2008 servers, or 8 Colubris controllers.…
I'd like to be able to discover security groups within an OU. It's still something AD based, but something that we can't do if we're solely looking for computer objects within an OU itself. So because I have a group that looks like this, the native discovery client cannot see any of the items I'd like to turn into nodes…
Within Network Discovery there is an option to customize what types of objects are monitored automatically within the nodes you're discovery. When you get to interface selection, you can choose advanced regex matching options such as: However, you are unable to checkbox flags such as context insensitivity (/i) or…
Hello Everyone, Is there an elegant way to detect and manage interfaces that have become active after the node initially was discovered? We don't have the hardware resources to manage all interfaces, so we routinely omit administratively down interfaces during discovery. Often these interfaces subsequently go 'green', but…
I think this one is probably self explanatory: I'd like to be able to ignore all the printers in a specific discovery even if they're within a subnet I'd normally scan. I think the easiest way is to have a checkbox for vendors to ignore. Or, an option of "do not include" with options such as: workstations / printers /…
It looks like you're new here. Sign in or register to get started.