Lenovo Flex System EN4093R switch not identified properly #5894

Closed
towster opened this Issue Feb 14, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@towster
Contributor

towster commented Feb 14, 2017

DO NOT DELETE THIS INFORMATION.

Please read this information carefully.

GitHub issues is for bugs, please do not post issues asking for help or how to do X, Y or Z.
You can use our irc channel ##librenms on freenode to ask questions or our community site.
If you have a feature request please post this on our community site.

Please confirm each of the sections below by putting an x in the box like [x].

  • [x ] Is your install up to date? Updating your install
    Please do not submit an issue if your install is not up to date within the last 24 hours or on a stable monthly release.
  • [x ] Please include all of the information between the ==================================== section of ./validate.php which you can run from the cli.
  • [x ] Please provide ALL info asked for here.
  • [x ] Please provide as much detail as possible.
  • [x ] Please do NOT post more than 10 lines of debug information here, use a pastebin service or GitHub Gists.

IBM sold their Flex chassis system to Lenovo. The IBM branded Flex switches are detected fine but the Lenovo branded ones appear as generic devices.
capture

poller.10.180.150.213.txt
snmpbulkwalk.10.180.150.213.txt
discovery.10.180.150.213.txt

@towster

This comment has been minimized.

Show comment
Hide comment
@towster

towster Feb 14, 2017

Contributor

Forgot to include screenshot of the (identical) IBM branded switch:
capture

Contributor

towster commented Feb 14, 2017

Forgot to include screenshot of the (identical) IBM branded switch:
capture

@lock

This comment has been minimized.

Show comment
Hide comment
@lock

lock bot May 17, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

lock bot commented May 17, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed.

@librenms librenms locked as resolved and limited conversation to collaborators May 17, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.