Network Management
Incorrect Machine Type Detected for Cisco IronPort Devices in SolarWinds Platform
This article provides information about an issue where the SolarWinds Platform detects Cisco IronPort devices with an incorrect Machine Type (for example, reporting all devices as IronPort C370), even though the actual hardware models differ (such as C695, C100V, or M695).
First published date
Last published date
Overview
Customers may observe that multiple Cisco IronPort devices are displayed with the same Machine Type in the SolarWinds Platform, despite being different physical or virtual models.
This behavior typically occurs during Node Details polling, where the platform determines Vendor and Machine Type based on SNMP information.
Observed Symptoms
- Different Cisco IronPort models appear with the same Machine Type
- The Machine Type does not match the actual hardware model
- Device details (Node Description / sysDescr) correctly show the model, but the Machine Type does not update accordingly
Example Scenario
Multiple devices report the same SNMP sysObjectID, but their descriptions indicate different models:
|
Vendor |
SysObjectID |
Description (sysDescr) |
Machine Type |
|
IronPort Systems, Inc. |
1.3.6.1.4.1.15497.1.1 |
Cisco IronPort Model C100V, AsyncOS Version X.Y.Z |
IronPort C370 |
|
IronPort Systems, Inc. |
1.3.6.1.4.1.15497.1.1 |
Cisco IronPort Model C695, AsyncOS Version X.Y.Z |
IronPort C370 |
|
IronPort Systems, Inc. |
1.3.6.1.4.1.15497.1.1 |
Cisco IronPort Model M695, AsyncOS Version X.Y.Z |
IronPort C370 |
Product section
Cause
The SolarWinds Platform currently relies heavily on the SNMP sysObjectID during Node Details polling to determine Machine Type.
In some vendor implementations (including Cisco IronPort):
- Multiple device models share the same sysObjectID
- Vendors reuse or overload sysObjectID values across different hardware, virtual, or generation variants
- sysObjectID granularity is not guaranteed to uniquely identify a specific model
Because of this, the platform applies a 1:1 mapping between sysObjectID and Machine Type, which can result in incorrect identification when different models report the same OID.
Resolution
There is currently no automatic correction available for this behavior, as it is considered a product limitation.
Workaround
You can manually override the detected Machine Type by creating a Custom Node Details Poller using Device Studio.
High-level steps
- Navigate to Settings > All Settings > Manage Pollers
- Click Add New Poller
- Select Node Details
- Define a fixed value or SNMP-based value for the Machine Type
- Assign the poller to the affected node(s)
Reference KB
Configure Vendor / Machine Type when SolarWinds is unable to detect it