Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Netgear m5300 health sensors #9744

merged 8 commits into from Feb 18, 2019


None yet
4 participants
Copy link

commented Jan 26, 2019

newdevice: Added support for Netgear M5300 (GS724Tv4)


Please note

Please read this information carefully. You can run ./scripts/pre-commit.php to check your code before submitting.


If you would like to test this pull request then please run: ./scripts/github-apply <pr_id>, i.e ./scripts/github-apply 5926
After you are done testing, you can remove the changes with ./scripts/github-remove. If there are schema changes, you can ask on discord how to revert.

cppmonkey added some commits Dec 29, 2018

ZyXEL XGS4600-32F
- Added mib for diagnostics
    - CPU/Mem
    - Temp/Fan/Voltage
- Updated zyxel group mempools
- Updated test data
    - snmprec
    - json
- Altered ZyWall
    - To exclude XGS switches
Netgear M5300
- Added mibs for diagnostics
    - CPU/Mem
    - Temp/Fan/Voltage
Netgear M5300
- Added mibs for diagnostics
    - CPU/Mem
    - Temp/Fan/Voltage

This comment has been minimized.

Copy link
Contributor Author

commented Feb 2, 2019

Currently testing this on our 34x M5300 stacks
Prominently M5300-28GF3 running
And odd few M5300-28G-POE+ and M5300-28G3

Applying the changes, I see that I've added a few whitespace errors.
Will sort those

@murrant murrant changed the title Netgear m5300 Netgear m5300 health sensors Feb 7, 2019

@murrant murrant merged commit 9dba9f6 into librenms:master Feb 18, 2019

6 checks passed

Inspection Summary
Node: analysis
Travis CI - Pull Request Build Passed
WIP Ready for review
codeclimate All good!
license/cla Contributor License Agreement is signed.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 19, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.