Discovery Classification Error

[csatish]

Hi Folks,
Can someone please guide me on the steps to troubleshoot incorrect CI classification during Discovery?

Scenarios:

1. While discovering a Windows Server, the CI is getting populated in cmdb_ci_computer instead of cmdb_ci_win_server.

2. While discovering a Router, the CI is getting populated in the Netgear table. In this case, which OID values should be verified to ensure correct classification?
   
   

Thanks

[SIVASANKARIS · Accepted solution]

Hi @csatish ,

CAUSE: SNMP OID of that Router device is not present in snmp oid table which is causing to trigger the different pattern and getting classified as different device.

RESOLUTION:

Step1: Found the SNMP OID, Manufacturer, Model from the discovery sensor payload.

• Navigate to All > Discovery Status > open our discovery status > ECC Queue> Open our SNMP classify input payload.

• Open that payload note the oid, manufacture, model present in it.

Model=value present in between the sysDescr tag.

SNMP OID=value present between sysObjectID tag(ignore the fullstop in front of the snmp oid number).

  Manufacture= value present in between the entPhysicalMfgName tag

Step 2: Create the SNMP OID in snmp oid classifications (discovery_snmp_oid)

• Navigate to All > discovery_snmp_oid.LIST > click new
• Fill all the details

Oid,manufacturer,model =obtained from payload.

Table = which cmdb ci table your data needs to settle down (based on this pattern will trigger) cmdb_ci_router

Classifier=which classifier we have to use

Then again run discovery it will work fine.

Please mark this as helpeful and accept my solution... if it solves your issue

[pavani_paluri]

Hi @csatish 

Windows Server showing up as just a "Computer"
To fix this:
Check what OS name Discovery is actually pulling back.
Make sure the rule that says “Windows Server goes into the Windows Server table” matches that OS name.
If the rule is too loose or doesn’t match the exact wording, adjust it.

Router showing up as Netgear
For network gear, Discovery relies on special ID numbers called **OIDs** (like fingerprints).
The key ones are:
**sysObjectID** → tells Discovery the vendor (Cisco, Juniper, Netgear, etc.).
**sysDescr** → gives a text description of the device.
If your router’s sysObjectID matches Netgear’s range, Discovery thinks it’s Netgear.
To fix this:
Look at the sysObjectID returned during discovery.
Compare it with the vendor’s official OID list.
Update the classification rules so the right OID maps to the right router type.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[pavani_paluri · Accepted solution]

Hi @csatish ,

Could you Please accept the solution if that solves your problem.

Kind Regards,

Pavani P

[SIVASANKARIS · Accepted solution]

Hi @csatish ,

CAUSE: SNMP OID of that Router device is not present in snmp oid table which is causing to trigger the different pattern and getting classified as different device.

RESOLUTION:

Step1: Found the SNMP OID, Manufacturer, Model from the discovery sensor payload.

• Navigate to All > Discovery Status > open our discovery status > ECC Queue> Open our SNMP classify input payload.

• Open that payload note the oid, manufacture, model present in it.

Model=value present in between the sysDescr tag.

SNMP OID=value present between sysObjectID tag(ignore the fullstop in front of the snmp oid number).

  Manufacture= value present in between the entPhysicalMfgName tag

Step 2: Create the SNMP OID in snmp oid classifications (discovery_snmp_oid)

• Navigate to All > discovery_snmp_oid.LIST > click new
• Fill all the details

Oid,manufacturer,model =obtained from payload.

Table = which cmdb ci table your data needs to settle down (based on this pattern will trigger) cmdb_ci_router

Classifier=which classifier we have to use

Then again run discovery it will work fine.

Please mark this as helpeful and accept my solution... if it solves your issue