pacetti

Comments

  • with the exception that the full release steps were omitted Can you tell me more about what you are mentioning here? Thanks,
  • Chris, Depending on the specifics of a given installation, it may be possible to go directly from 9.1 to 10.0 without any concern. It is, however, generally safer to include the intermediate step of upgrading to 9.5.1 to ensure that all essential incremental updates, particularly with respect to the Orion database, are…
  • In the All Nodes - Tree resource, presumably on the Network Summary Home view, there are three buttons at the top right: * Manage Nodes * Edit * Help If this is not what you are seeing, can you provide a screenshot to clarify?
  • Do you have any additional polling engines installed? If not, then all your nodes are assigned to the one, primary polling engine. If you do have additional polling engines installed, you can determine node assignments as in the following procedure. Note: This procedure uses a component of Orion NPM that may be deprecated…
  • If you are running the latest version of APM on Windows Server 2008, you must run Windows Server 2008 R2, as indicated in the Requirements for Orion APM on p.3ff of the SolarWinds Orion APM Administrator Guide: Operating System Windows Server 2003 or Windows Server 2008 R2, with IIS in 32‑bit mode.IIS must be installed.…
  • If your license is valid, you should be able to migrate using License Manager without a problem. For more information, see "Maintaining Licenses with License Manager" in the SolarWinds Orion NPM Admin Guide or see the "Migrating SolarWinds Product Licenses" video. HTH, Andrew Pacetti
  • As a general rule, you can expect improvements in web console and database performance in each successive release. If failover protection is a concern, you should consider an upgrade to the Orion Failover Engine. For more information, see the following resources: * Orion Failover Engine Documentation *…
  • Sol, Unfortunately, currently, selective event display in the web console is an outstanding feature request. I can't say if or when it will be included in a release, but it has been recorded.
  • Basically, as it works now, NPM discovers devices, tells you what it found, and then asks you for direction as to what devices, of all discovered, can/should be ignored in the future. I'll mark this post for our PMs to consider: * adding an additional step to indicate what can be ignored before discovery starts. * adding…
  • No. that will not work. NPM 10.0 requires SQL Server 2005. The Upgrade Instructions (Customer Portal > License Management > Orion Network Performance Monitor vX) will provide guidance on requirements for both your Orion server and you database (SQL) server.
  • WiseAlloys, Thanks for posting your update. I'll look into it.
  • Generally: * Create a backup of your DB. For more information, see "Moving your Orion NPM Database (.pdf)". * Create a backup of your web console configuration. For more information, see "Managing Orion Web Console Configurations" in the SolarWinds Orion NPM Administrator Guide (.pdf). * Reinstalling NPM and NCM followed…
  • bmvernil, The OID you mention is listed within the SolarWinds MIB. For more information about OIDs and how they are used with the Universal Device Poller, see the following sections in the SolarWinds Orion NPM Administrator Guide: * Management Information Base (MIB) * Monitoring MIBs with Universal Device Pollers Open the…
  • I see. I'll make sure the PM sees this as a feature request. You may be able to create a Historical - Custom Pollers report that displays the result of your pollers, and then edit the report's SQL query to sum the poller results as you need in the report itself. Once you have the report, you can then add it to the web…
  • Was it possible that R2 wasn't supported when we installed NPM a couple of years ago? This is indeed possible.
  • Unfortunately for your client, NPM 10.4 requires NTA 3.8 and APM/SAM 5.0. NTA 3.7 is compatible with NPM 10.3.X, but APM 3.5 is limiting your client to NPM 10.2.2.
  • freemen, thank you for pointing out a place where we could add some more info to the Admin Guide. If you are swapping in a new NIC, you will need to add the new interface for monitoring using Web Node Management. Since it has a different MAC address, Orion NPM will view it as a completely new or different device and…
  • You can get the poller results into a transform pretty easily. See the "Transforming Poller Results > Creating a Poller Transformation" section in the same "Monitoring MIBs with Universal Device Pollers" chapter.
  • No, you are reading it correctly. My concern was that it seems not to be compatible with NPM 10.2.1 / Core 2011.2.1, though IPAM 1.7.1 is. Clear as mud, I am sure.
  • mrogers, The following sections of the SolarWinds Orion NPM Administrator Guide may provide some insight: * Managing Dependencies * Viewing Alerts on Child Objects * Creating and Configuring Advanced Alerts HTH,
  • You can upgrade directly. There are Upgrade Instructions in your customer portal, but they have not been updated to include 10 yet. If you use that document, merely substitute your Orion NPM 10 installer where any Orion NPM v9.5.X installer is requested.
    in 10 when? Comment by pacetti April 2010
  • No worries, Goliath...
  • If you've got your groups and dependencies defined correctly for your environment, the individual device alerts will be redundant. You can remove them. 
  • byrona, I am actually updating these docs "as we speak". They should post either later today or on Monday. The long and the short of it is that an upgrade to 10.0 is conducted almost exactly as an upgrade to 9.5.1 would proceed. 10.0 includes a couple of items in the installer that make it a little easier, actually.
  • GonzoUK, Use the MIBs provided by SNMP Informant-MBM to create specific device pollers (Universal Device Pollers) in Orion NPM. For more information, see "Monitoring MIBs with Universal Device Pollers" in the Orion NPM Administrator Guide.
  • Yes, that is my understanding.
  • Dan, If you are on maintenance, you should find an Upgrade Instructions document linked from your licensed products in your Customer Portal. You should be able to use this document to find the older version of Orion NPM that you need to complete your transition. As we generally recommend, and, as you have noted, be sure to…
  • goatman, You may be interested in the Scheduled Discovery feature discussed in this thread.
  • The ciscoCcmMIB branch starts at 1.3.6.1.4.1.9.9.156. * Click Start > All Programs > SolarWinds Orion > Universal Device Poller. * Click New Universal Device Poller. * Enter 1.3.6.1.4.1.9.9.156 in the OID field, and then browse from there.
  • inekam, Here's a direct link to the online doc: "Monitoring MIBs with Universal Device Pollers" in the Orion NPM Administrator Guide.