Hello Balakrishnan
I followed the information on this thread and I believe you have been given the proper information to move forward with this. However I will clarify a few points.
#1. new vendor devices may have MIB details which Spectrum is not yet aware.
#2. in cases where certain MIB objects (especially custom mapped MIB objects with codes starting with "0xfff") Spectrum may not be able to poll custom MIBs until they are properly defined in the database for that device model type.
This is the issue that you are facing. You are using a device which Spectrum is not aware, and have a custom mapped MIB object 0xfff00005
You can check if a Device is Certified within Spectrum at this link: https://ehealth-spectrum.broadcom.com/devices/html/search_sp.html
I checked your OID based on the WALK you provided, and 1.3.6.1.4.1.49281 is -not- a Certified device - meaning any non-certified Devices may show unexpected behavior due to Spectrum is not aware of this device until Certified.
From here, you have two options:
option A: Self-Certify the device using Model Type Editor -
note - MTE is an ADVANCED feature of Spectrum and should only be used with CARE and after understanding the documentation on it. Changes in MTE are permanent changes to the Spectrum device catalog and using this feature should only be done by experienced Spectrum users. That said, MTE is very powerful and can allow self-Certification of devices, such as mapping custom Attributes.
For Self-Certification, here is a KB with much information and links to helpful docs on Self-Certification, as well as helpful You-Tube videos:
https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=129149option B: Open a support case, and provide SNMP WALK so that the device can be submitted to official Certification by Spectrum engineers. The device would be available in a future version of Spectrum or Certification Pak , so be sure you have the most current version of Spectrum running
So from here, you have the options to Self-Certify the Device, or to open a Support case to submit the Device for Certification. if you have any questions on Self-Certification, we would recommend a support case. Thus in any event, if you have further questions on this which is not solved by checking suppor.broadcom.com, or by checking the KBs which have been provided to you, then a Support case would be your next step.
------------------------------
Senior Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 08-15-2020 10:59 AM
From: Balakrishnan Kuppuswami
Subject: Device serial number not discover
Hi Team,
Awaiting your reply..
Original Message:
Sent: 08-12-2020 01:23 PM
From: Balakrishnan Kuppuswami
Subject: Device serial number not discover
Hi Silvio/ Brian,
We have tested auto discovery on one location and have following observations :
10.83.103.96 - PL-2418MG-16 P ( Switch IP )
10.83.103.92 - PL-2426MG-24PL ( Switch IP )
NMS Server IP :- 172.18.101.171
10.83.103.97 – Laptop IP
--------------
- The NMS is Using Wrong OID or MIB file to discover Plexonics Switch, That's why the Switch unable to send correct response back to NMS server ( refer the attached snapshots captured from wireshark which clearly explains the issue)
- we believe that our MIB File is not properly updated or recognized by CA Spectrum for which we need to your support to update
- we also believe this can be solved if NMS software can discover the switch using IP address and OID together
- NMS server also send SNMP v1 request even though it was configured as v2c in both NMS software and Switch
- We tested with PRTG NMS software on that we can abel to get correct OID and SNMP Version discovery
Refer all the Snap shot details attached
Awaiting your reply..
Original Message:
Sent: 06-17-2020 04:13 AM
From: Balakrishnan Kuppuswami
Subject: Device serial number not discover
Hi, Silvio,
As our client is Government so we are not allow to testing revised MiB, Request you to please share us CA Demo Link so we can test our Revised MiB at our end.
Thanks.
Original Message:
Sent: 06-14-2020 07:39 PM
From: Silvio Okamoto
Subject: Device serial number not discover
Yes. SNMPv1 uses 32 bits counters and SNMPv2c and SNMPv3 use 64 bits counters.
So for Serial Number, no matter if you are using SNMP v1, v2c, or v3.
------------------------------
Technical Support Engineer IV
Broadcom Inc
Original Message:
Sent: 06-14-2020 01:08 AM
From: Balakrishnan Kuppuswami
Subject: Device serial number not discover
Hi,
Thanks for your reply, In our CA Spectrum we are using SNMP Version 2 , so will your reply will work with same procedure in SNMP V2?
Original Message:
Sent: 06-10-2020 10:58 AM
From: Silvio Okamoto
Subject: Device serial number not discover
Hi Balakrishnan,
Please take a look at these KB articles:
https://knowledge.broadcom.com/external/article?articleId=187041
https://knowledge.broadcom.com/external/article?articleId=50416
------------------------------
Technical Support Engineer IV
Broadcom Inc
Original Message:
Sent: 06-10-2020 10:04 AM
From: Balakrishnan Kuppuswami
Subject: Device serial number not discover
hi
Our Device is reachable and also able to discover device Mac through MiB in CA but not able to get only serial number.
For that we have to manually fetch device serial number and need to add.
In free software ( Mib browser we can get both serial number and Mac ) but not in CA.
Please guide how to get serial number while discovering device.
------------------------------
Thnx.
------------------------------