aLTeReGo ✭✭✭✭✭

The ability to monitor highly available Exchange 2010/2013 Database Availability Groups (DAG) is natively included as part of AppInsight for Exchange, which is available in the SAM 6.1 release, currently in beta.

And/or a TCP port monitor for port 3389

SAM already collects disk performance metrics for volumes and mount points from WMI managed nodes, as well as hardware health of Windows, Linux, and ESX/ESXi hosts.

You were certainly on the right path with the script you referenced above. The WMI Monitor will not work for your needs since your query returns a string value, not a numeric value. I would recommend posting this script to the Script Lab‌ where the community script gurus generally frequent. They may be able to identify the…

Some DBAs go so far as to disable memory-optimized tables. Another possibility is that the SQL Server you're migrating to is SQL 2014, which does not support in-memory tables. My recommendation is to work with your DBA to determine why you are unable to create in-memory tables as this is a performance-enhancing feature…

Your case has just been transferred to one of our best Applications Engineers.

Thanks justin.alcorta​. We're looking into it now.

We are tracking this issue internally as a bug under 'WPM-184'.

graham.leiker wrote: 1.3.6.1.4.1.9.1.2391 = C9800_IOSXE-K9 - Cisco vWLC Captured under DC-2870

sja wrote: C9300L-48P-4X 1.3.6.1.4.1.9.1.2804 Cisco Catalyst C9200-48P 1.3.6.1.4.1.9.1.2695 Macine type is "Cisco" ... Tracking internally under DC-3118

mburns34 wrote: 1.3.6.1.4.1.705.1 - Eaton 5PX 2200 Have you verified this SysObjectID against different modules of Eaton UPSs? The OID you posted is too generic for that specific make & model device. This appears to be a root OID.

The link below should take you to the appropriate section of the online Administrators Guide, which covers template assignment to nodes, etc. http://www.solarwinds.com/NetPerfMon/SolarWinds/OrionAPMAGManagingTemplates.htm

Tracking internally under DC-2919

sploy wrote: 1.2.826.0.1.4616240.1.1.4520 = Cisco TelePresence MCU 4520 Tracking internally under DC-2919

Wingren wrote: Here are some more Fortinet products... 1.3.6.1.4.1.12356.101.1.2009 = Fortigate 200E 1.3.6.1.4.1.12356.103.3.4005 = FortiAnalyzer 400E 1.3.6.1.4.1.12356.118.1.10004 = FortiSandbox 1000D 1.3.6.1.4.1.12356.101.1.1004 = Fortigate 100D 1.3.6.1.4.1.12356.106.1.2244 = FortiSwitch 224E-POE…

hendershotn wrote: 1.3.6.1.4.1.9.1.2391 = Cisco C9800-CL-K9 1.3.6.1.4.1.9.1.2572 = Cisco ASR9906 1.3.6.1.4.1.6527.6.2.1.2.8.2 = Alcatel 7210 1.3.6.1.4.1.6486.800.1.1.2.1.11.1.1 = Alcatel OS6250-8M 1.3.6.1.4.1.6141.1.99 = Ciena 3903 1.3.6.1.4.1.6141.1.100 = Ciena 3904 1.3.6.1.4.1.6141.1.101 = Ciena 3905…

1.3.6.1.4.1.8072.3.2.10 is actually any NET-SNMP device The other two Cisco device models, I am tracking internally under DC-2870

wrote: 1.3.6.1.4.1.9.1.2694 - Cisco 9200L I am tracking this internally under DC-2870.

cnorborg wrote: 1.3.6.1.4.1.30065.1.3011.7050.1958.48 - Arista DCS-7050TX-48-F 1.3.6.1.4.1.30065.1.3011.7050.3741.2.72.2512 - Arista DCS-7050SX2-72Q-R 1.3.6.1.4.1.30065.1.3011.7280.3101.2878.36 - Arista DCS-7280QR-C36-F 1.3.6.1.4.1.30065.1.3011.7020.1964.48 - Arista DCS-7020TR-48-R 1.3.6.1.4.1.30065.1.3011.7280.3714.72 -…

extrands wrote: 1.3.6.1.4.1.9.1.2668 = Cisco C1111X-8P 1.3.6.1.4.1.9.9.168.1.2.1.1.8 = Cisco ASR1001-X 1.3.6.1.4.1.9.12.3.1.3.1856 = Cisco C92300YC 1.3.6.1.4.1.9.12.3.1.3.1850 = Cisco C93180YC-FX 1.3.6.1.4.1.9.1.2688 = Cisco C9500-48Y4C 1.3.6.1.4.1.9.1.2494 = Cisco C9300-24U It looks like '1.3.6.1.4.1.9.9.168.1.2.1.1.8'…

david.wild wrote: 1.3.6.1.4.1.476.1.42 Liebert/Vertiv GXT4 are new to our network and not correctly identified yet. a bit new to this, is this the correct way to add "Unknown" Regards. In Orion Platform 2019.2 these devices should be recognized as 'Veritiv/Emerson/Liebert'

ictservicedesk@shetland.gov.uk wrote: 1.3.6.1.4.1.9.1.2694 - Cisco 9200L Logged internally under DC-2627

frankmuhlstadt wrote: 1.3.6.1.4.1.9.1.1348 - ciscoUCVirtualMachine This SysObjectID should already be included in the latest Orion Platform version 2019.2.

pgaryga wrote: OID: 1.3.6.1.2.1.33 CS121 SNMP Card This is an OEM interface card added to an industrial UPS, ours are badged Piller Power Systems, however, I think same OID is quite generic and is used for other makes. I created a SAM template a while ago which is here: Piller UPS Pete. This is not a SysObjectID. All…

jpar345 wrote: 1.3.6.1.4.1.9.1.2593 = Cisco C9500-40X model switch (only shows up as "Cisco" under machine type) This SysObjectID and most others posted here have been added to Orion Platform 2019.2 included in NPM 12.5, available now from your Customer Portal.

badger_442 wrote: 1.3.6.1.4.1.8072.3.2.10 = checkpoint Firewall appliance 1490 (seems to be used for different model numbers?) '1.3.6.1.4.1.8072.3.2.10' is a generic SysObjectID for NET-SNMP. To learn more about this, click the link below.…

frankmuhlstadt wrote: 1.3.6.1.4.1.12356.101.1.2010 = Fortigate 201E Captured under DC-1990

frankmuhlstadt wrote: 1.3.6.1.4.1.12356.101.1.306 = Fortigate 30E Captured under DC-1990

frankmuhlstadt wrote: 1.3.6.1.4.1.12356.101.1.1041 = Fortigate 100E Captured under DC-1990

sum_giais wrote: Hey aLTeReGo ! Is it possible to update this existing SysObjectID in the database? We have a couple Brocade MLXe-16 chassis' that show up as Brocade FCX648's. 1.3.6.1.4.1.1991.1.3.55.1.2 = Brocade NetIron MLXe-16 Thoughts on getting this, and DC-1603 implemented in the next release of NPM / Orion Core?…