aLTeReGo ✭✭✭✭✭

robert.dimov wrote: 1.2.826.0.1.4616240.1.3.3241 CISCO ISDN GW 32411.2.826.0.1.4616240.1.7.8050 Cisco Supervisor MSE 8050 1.2.826.0.1.4616240.1.1.4501 cisco MCU 4501 1.2.826.0.1.4616240.1.1.4205 cisco MCU 42051.2.826.0.1.4616240.1.1.4510 cisco MCU 451 Tracking internally under DC-1988

frankmuhlstadt wrote: .1.3.6.1.4.1.9.12.3.1.3.1850 cevChassisN9KC93180YCFX OBJECT IDENTIFIER ::= { cevChassis 1850 } -- Nexus 9300 series chassis 48x10/25G (SFP28) and 6x40/100G (QSFP28) We are tracking this internally under DC-1313.

frankmuhlstadt wrote: 1.3.6.1.4.1.45.3.72.2 ERS-2500-26T-PWR This SysObjectID should already be included in Orion Platform 2018.4

frankmuhlstadt wrote: ciscoUCSC220M5 .1.3.6.1.4.1.9.1.2492 Tracking this internally under DC-1015.

rachit.mathur wrote: F5 Load Balancer SysObjectID: 1.3.6.1.4.1.3375.2.1.3.4.1000 Vendor: F5 LTM Model: i2800 The device is showing up as "unknown" I checked the database and 1.3.6.1.4.1.3375.2.1.3.4.1000 is properly associated with F5 in the latest release. Unfortunately that SysObjectID isn't unique to any one particular…

Unfortunately Liebert does not have specific SysObjectIDs for different makes/models. That OID in particular is still classified under Emerson Power > Free LIEBERT-GP-POWER-MIB SNMP MIB Download - Free MIB Download - Search MIBs - OiDViEW

bps wrote: 1.3.6.1.4.1.9.1.2560 = Cisco IR807G-LTE Tracked internally under DC-1683

bps wrote: .1.3.6.1.4.1.21638 = Selex ECOS-D RBS 4000 (DMR RBS 4000) That OID represents an entire company (PROD-EL PRODOTTI ELETTRONICI S.P.A), not a specific device type or model.

Thanks sum_giais​! I've got these all logged internally under DC-1603.

sja wrote: I sure like to see those nodes MACHINE TYPE like it's should be "Juniper ACX5048 Router" Now it's "Juniper Networks, Inc." Juniper acx5096 1.3.6.1.4.1.2636.1.1.1.2.127 Juniper acx5048 1.3.6.1.4.1.2636.1.1.1.2.126 Tracking internally under DC-1463.

Deltona wrote: Vendor: Tenable Machine Type: Core OID: 1.3.6.1.4.1.8072.3.2.10 As stated above, SysObjectID 1.3.6.1.4.1.8072.3.2.10 is NET-SNMP.

MathieuJM wrote: Cisco Nexus 9K 1.3.6.1.4.1.9.12.3.1.3.1921 cevchassis Nexus 9K C9348GCFXP 1.3.6.1.4.1.9.12.3.1.3.1850 cevChassis Nexus 9K C93180YCFX 1.3.6.1.4.1.9.12.3.1.3.1954 cevChassis Nexus 9K C9364C Tracked internally under DC-1313 MathieuJM wrote: 1.3.6.1.4.1.9.12.3.1.3.1843 cevChassis Nexus 9K C93180LCEX Already…

dsimpkins wrote: Have posted a seperate question but can we fix: .1.3.6.1.4.1.2620.1.6.16.7.0 = STRING: "Check Point 5600" Shows up as just 5600 in the Description and in the "Views By Device Type" Logged internally under DC-1312

bps wrote: here a other ODI for the ISR 1100-8P 1.3.6.1.4.1.9.1.2443 = NAME: "Chassis", DESCR: "Cisco C1111-8P Chassis" / cisco C1111-8P (1RU) processor Cisco ISR 1100 Series the the IR807 1.3.6.1.4.1.9.1.2560 = Cisco IR807 Industrial Integrated Service Router * small brother of IR809, this one is all-ready integrated....…

You can vote for this idea here >

agrandaw wrote: Cisco NCS-5501 and 5502 The NCS-5501 should already be included in NPM 12.4 with Orion Platform 2018.4. What is the SysObjectID for the 5502?

joelvs wrote: 1.3.6.1.4.1.9.1.2456 = Cisco 1100-8P ISR Tracking internally as CORE-11867

rlsmith999 wrote: Pulse Secure, PSA-3000 1.3.6.1.2.1.1.2.0 sysObjectID.0 OBJECT-IDENTIFIER 1.3.6.1.4.1.12532.256.2.1 1.3.6.1.2.1.1.1.0 sysDescr.0 DisplayString "Pulse Secure, LLC,Pulse Connect Secure,PSA-3000,9.0R2.1 (build 63975)" We are tracking this internally under CORE-11761.

ptspts wrote: Please add Cisco SX80 to the list, it is curently shown under "Unknown" Machine Type. Can you provide the SysObjectID for the Cisco SX80?

Thanks mbuzard. We are tracking this internally under DC-676.

velin.georgiev , most of the SysObjectIDs you listed are already included in the latest release. The ones that were not, I included with ben.seward​'s one above and am tracking internally under CORE-11585.

wrote: 1.3.6.1.4.1.9.1.2492 = Cisco UCS C220 M5 Rack Server Cisco Integrated Management Controller(Cisco IMC) [ ], Firmware Version 3.1(2g) Copyright (c) 2008-2017, Cisco Systems, Inc. Tracked internally under DC-1015.

I'm somewhat confused, as EMC"s own documentation lists '1.3.6.1.4.1.12325.1.1.2.1.1' as an iPrism which is what Orion should be reporting. https://russia.emc.com/collateral/TechnicalDocument/docu61689.xlsx https://japan.emc.com/collateral/TechnicalDocument/docu89354.xlsx

Logged internally under CORE-11471.

Thanks, wfriesn1 . I have logged these internally under CORE-11381.

Thanks matt-atl. We are tracking this internally under CORE-11364.

You are correct that SysObjectID 1.3.6.1.4.1.9.12.3.1.3.1507 is incorrectly mapped. I have logged this as a bug we are tracking internally under CORE-11306. The others I am tracking under CORE-11307.

frankmuhlstadt wrote: 1.3.6.1.4.1.4329.15.1.1.10 = Extreme Networks Wireless Controller - C5110-2 Tracking internally under CORE-11092.

It's likely the device doesn't support one or more of the three required OIDs necessary to add the node. Minimum OID to add a device as an SNMP node - SolarWinds Worldwide, LLC. Help and Support

bhazelba wrote: 1.3.6.1.4.1.9.1.2406 = Cisco FirePOWER FPR-2130 Security Appliance Tracking this internally under CORE-11026 When this has been incorporated onto the SolarWinds database, will I be able to poll the interfaces on this device? Currently it does not discover the pyhsical interfaces. It returns a wierd list of…