Repository navigation
docs(snmp): the iLO's SNMPv1 is off, and four documents stop pointing at the issue for it - #585
Merged
Merged
Conversation
… at the issue for it §4.5 ran on `shiva` today: *SNMPv1 Request* disabled, and `snmp-verify.sh --old` returned `rejected` — the iLO no longer answers its own former community over v2c. Until now the documents claimed the v3 poll and deferred the v1 half to #85, which was right while it was unproved and is understating the estate now that it is not. `SECURITY.md`'s known-exposure row, `docs/security.md`'s SNMPv2c section, `docs/hardware.md`'s Management row and the roadmap's #85 bullet all say it instead. The roadmap bullet also carries the scrape cost ADR-0036 asked to be measured rather than assumed: 12.09 s averaged over the hour after the move against 12.05 s over the day before it, 60 samples and no gaps. The v3 discovery round trip is not visible against a 12-second walk. `mjolnir` is still open, so #85 is not. Refs #85 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #581, which moved
shivato SNMPv3 authPriv but deliberately claimed nothing about SNMPv1: that half was unproved at the time, so the documents pointed at #85 for it. It is proved now.What happened on the device
SNMPv1 Request off on the iLO, then
./scripts/snmp-verify.sh --old→rejectedforshiva. That probe is always v2c whatever the device speaks now, so it is precisely the check that v1/v2c access is gone. A second--device shivaafterwards, because disabling v1 is another save of the same page:What changed here
Documentation only — four passages that asserted less than what is true:
SECURITY.mdknown-exposure row: the BMC answers no community at all now.docs/security.mdSNMPv2c section: the lab-segment poll is not readable from the lab segment any more.docs/hardware.mdManagement row.docs/roadmap.mdMove the iLO and the UPS card to SNMPv3 authPriv (ADR-0036) #85 bullet, which also gains the scrape measurement ADR-0036 asked for rather than assumed:scrape_duration_secondsonshiva60 samples in that hour, no gaps,
min_over_time(up{job="snmp"}[30m])= 1 on all four devices.Verified
make validateclean. The first local run failedobservability: promtool check configwith a spurious "file_sd target file does not exist" against a file that is present and tracked — the known local flake under a busy docker daemon; the rerun passed it, and this change is four markdown files.#85 stays open:
mjolnirhas not moved yet.🤖 Generated with Claude Code