Unable to discover SNMP Devices running classification for Unix and Http

Prahlad Kumar
Tera Guru

 

Hello Everyone,

 

I'm facing an issue when running discovery for SNMP devices Nokia Switch - Model(SR Linux).

 

A) SNMP credentials are validated
B) Firewall opened
C) Open 161 is opened

PrahladKumar_0-1723550901125.png

 

Now the issue here is SNMP not classified properly and, it is again running classification for Unix and Http as attached and ended up with Active, Couldn't classify error. Could you please assist me with what might be the issue?

 

Discovery Log:

Short MessageSource
Active, couldn't classify, now finishedUnix Classify
Active, couldn't classify, now finished
SNMP

 

PrahladKumar_1-1723551815898.png

ECC Queue:

PrahladKumar_2-1723551852972.png

 

Could you please assist me with what might be the issue?

 

 

Thanks

Prahlad Kumar

 

#discovery #itom #cmdb #ServiceNow 

 

6 REPLIES 6

Aneesh-D
Tera Guru
Tera Guru

Dear @Prahlad Kumar - 

 

1) The reason why Discovery try to run SNMP, UNIX and HTTP is because the corresponding port status is "Open" in Shazzam response. Since you have set up only SNMP credentials, the other two classify could not proceed any further.

 

2) Why SNMP is not able to classify: 

--> Most likely - The System Object ID is not available in the SNMP OID Classification table.

You can try this: As I can see you already have 603 OIDs returned, open the ecc input message for SNMP Classify and search for sysObjectID in the payload xml. You are likely to find something like below. 

 

<sysObjectID oid="1.3.6.1.2.1.1.2" type="SnmpObjectId">.1.3.6.1.4.1.xx.xx.xx.xx</sysObjectID>

 

 

Take this value from this tag (in this example .1.3.6.1.4.1.xx.x.xx.xx) and create a new record in the SNMP OID Classification table 

AneeshD_1-1723559841108.png

 

 

AneeshD_0-1723559797804.png

 

Then re-run the discovery. 

Let me know if you need further assistance. 

 

thanks,

Aneesh D

Please press thumps up if this reply helped and Accept as Solution if it solved your problem.

AneeshD_2-1723560154581.png

 

 

VedantJ
Tera Contributor

@Aneesh-D, I am also facing same issue, I have added the OID and CI(nokia sr linux switch) is getting discovered , but the necessary attributes are not getting captured like serial no, location,port etc.

VedantJ_0-1724070870027.png

VedantJ_1-1724070965093.png

 

Aneesh-D
Tera Guru
Tera Guru

Dear @VedantJ  - In the above given example, i have used a standard Network Router classifier which in turn use a generic Network Router pattern. This otb pattern is mainly focusses on Cisco snmp implementation and might not be working for Nokia snmp implementation.

eg: for Cisco- OID for serial number is 1.3.6.1.4.1.9.5.1.2.19 , but Nokia might have a different one.

 

You will have to create a custom pattern for Nokia (you can duplicate Network pattern and use that as a template).

Create a new classifier to link this pattern and use that classifier in the SNMP oID Classification entry record that you have created for Nokia SR.

 

Let me know if further help required.

Thanks,

Aneesh D

I am facing similar issue while trying to discovery SNMP devices. I created a new classifier but while linking it to OID I got an error message stating cannot enter the OID. It seems ServiceNow has an OOB Business Rule which restricts entry of certain OIDs. Could you please let me know if there is any other way to trigger classifier apart from linking it to OID classification?