
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday - last edited Tuesday
Hello Lansweeper Community,
I'm currently evaluating Lansweeper during the trial period, focusing on its capability to retrieve the current software/firmware versions of our network switches (e.g., Aruba, Cisco) to monitor for vulnerabilities and CVEs.
Despite configuring SNMP (v2c and v3) and SSH credentials, the "Software Version" field for our switches remains empty in the asset details. Interestingly, when I perform local scans using custom OIDs, I can retrieve the software version information. However, these custom OID results don't appear in the cloud dashboard and aren't linked to the standard "Software Version" field.
I've ensured that SNMP is correctly set up on the devices and that Lansweeper has the necessary access. Still, the issue persists.
Questions:
1. Are there specific configurations or best practices to ensure that switch software versions are accurately detected and displayed without any custom OIDs?
2. Is there a method to map custom OID results to the standard "Software Version" field in Lansweeper?
Retrieving and monitoring switch software versions is a critical feature for our operations. Any guidance or suggestions would be greatly appreciated.
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Wednesday
Hi ,
The SNMP frequently provides Lansweeper with the most comprehensive device details, hence its inclusion as a key scanning method. While Lansweeper collects the most info from network devices using the SNMP protocol, the ability to discover specific information ultimately hinges on how and where the device manufacturer decided to expose that data. To address this, the custom OID scanning feature allows Lansweeper to collect additional information that might not be captured during the standard SNMP scan. You are correct that currently this information is not synced to cloud as of now.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Hey,
so this means also that CVE's of custom OID's can't be checked against either, correct?
Best Regards,
Tim
