newer hh3c mibs from #70 , also add README with update instructions - #110
Open
inphobia wants to merge 97 commits into
Open
newer hh3c mibs from #70 , also add README with update instructions#110inphobia wants to merge 97 commits into
inphobia wants to merge 97 commits into
Conversation
Added Lancom MIBS
Update Mikrotik
Update Cisco
File was probably added by accident
This reverts commit f4de9e0.
The contents of this readme are outdated, the procedure for MIB updates has changed several times. After discussion on IRC, verdict was to drop this file.
* Updating F10 MIBs for new products * rebuild metadata with updated force10 - looks sane
commit 80c6146 Author: Oliver Gorwits <oliver@cpan.org> Date: Sat Mar 17 15:30:31 2018 +0000 update aerohive MIBs
Update 4.008
Added Nateks MIB
* part 1: ieee updates * part 2: rfc updates * part: faulting mibs * readd rfc1213 changes
Accept most changes from HP/Aruba, including dropped objects for products that have never been released. Couple of minor consistency fixes in object names for E3800 (adding back "A" suffix to model numbers).
* update a few cisco mibs also readd cevChassisC385048 to CISCO-ENTITY-VENDORTYPE-OID-MIB.my * work in progress README documenting local changes
Update some mibs needed for the Layer3 class in snmp-info
audiocodes briefly had it's own snmp.conf entry and mibs dir, but was moved to the mediant dir in commit 81e54e0
actual mibs submitted in netdisco#97 by @fragfutter but something went wrong there with reports/all.
see netdisco/snmp-info c73bc0ca2c43017382af3b14b0010f67f3fd8901 should not matter since this file is not used by snmp::info or netdisco directly
* fix some typos * remove $Id strings from previous rcs systems * remove backslash before ampersand, not done anywhere else * variable shadowing in old scripts
Member
Author
|
has been open for quite some time, i'll be merging this in a few weeks if noone objects. don't have any of the devices to test against. |
Member
|
not sure this PR can be salvaged, sorry. |
Member
Author
that does indeed seem to be the case, gonna rebase my clone & hope this doesn't wipe out anything, mmight come back to a few vendors |
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
10 participants
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.
a few changes in oid object definitions, but after cross referencing with layer3/h3c.pm none of them are relevant.
no idea if this influences huawei things, but it does not seem so.