One more thought... The hard-coded OID tree is sort of what we're doing. Each 'type' of module has it's own tree. For instance, there is a mib tree called 'packetFluxPowerControl' which is for things like PoE injectors, PDU boards, etc.. There's also a packetFluxGNSS for GPS receivers and the 1PPS which comes from them. And a packetFluxSensors table for things like voltage readings on the device itself, or temperatures, etc.
Each tree has a table which contains 'columns' for each of the things you will find on that type of port, such as power consumption, voltage, control for the power, etc. We'll add additional columns as needed. You have to index this column in some way in SNMP. Based on past experience, doing it in a way which is dependent on what else is in the system causes problems as you add/remove things from the system. So we decided to go with a two level 'slot' and 'port' index for each of the columns. So 'slot' could actually be re-named to be 'device' as well. On Tue, Oct 8, 2019 at 4:51 PM Jesse DuPont <jesse.dup...@celeritycorp.net> wrote: > This will be really helpful for users of LibreNMS, thank you for doing > that. > > I was thinking that each module could just have a hard-coded OID subtree > that was the same regardless of the serial slot order, but user-definable > should do the trick, too. > > *Jesse DuPont* > > Network Architect > email: jesse.dup...@celeritycorp.net > Celerity Networks LLC > > Celerity Broadband LLC > Like us! facebook.com/celeritynetworksllc > > Like us! facebook.com/celeritybroadband > > On 10/8/19 4:38 PM, Forrest Christian (List Account) wrote: > > No, the SNMP MIB won't be the same. > > The way we support SNMP in the Base II is one of the gripes we hear a > lot. So, we changed it. > > The Base 3 first of all actually has a MIB. It's also identical MIB-wise > to the one for the RackInjector. > > Secondly, the MIB has specific tables for different types of values. So > you actually go after something called 'voltage' for an input voltage. > And most SNMP tools should put the decimal in the right spot. > > It's also set up such that one should be able to use a consistent > monitoring system setup regardless of what is attached. With the caveat > that you can't monitor something which isn't attached. The base II was so > dynamic that upgrading the firmware in an expansion module could change all > of your OID numbering. The new one doesn't do that since it actually uses > 'slot' as part of the OID. And the 'slot' number is user assigned. So as > an example, you can monitor the tripped-status of a port with something > like: > > portPowerTripped.1.4 > > which gives you the tripped status of the port in slot 1, port 4. Like > I said, the slots are user-assigned (in most cases, the rackinjector ones > are fixed), so you could 'reserve' 1-10 for your PoE devices and put > monitoring for solar charge controllers at 11 and 12, and something else at > 100, so it's consistent across your network. You don't have to be > contiguous or fill all the holes. > > Oh, and MIB file contains hopefully useful descriptions such as for > portPowerTripped: > > "Whether the power has been shut down due to the detection of an > overcurrent or other faults. This value overrides the powerEnabled value > when true, ensuring that a port is shut down on fault. Write a '0'(false) > to this OID to reset the trip." > > > > On Tue, Oct 8, 2019 at 7:57 AM Josh Luthman <j...@imaginenetworksllc.com> > wrote: > >> +1 for keeping SiteMonitor base 2 but I would like to see what base 3 >> looks like in Vegas. >> >> Hopefully you have the SNMP MIB match? >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> >> On Tue, Oct 8, 2019 at 12:55 AM Forrest Christian (List Account) < >> li...@packetflux.com> wrote: >> >>> Sorry for the non-Friday marketing, I'm trying to get out of town headed >>> toward WISPAPALOOZA with a few meetings and family visits along the way. >>> But figured several of you would be interested in the following. >>> >>> (The following is a mostly-duplicate of an email I sent out to customers >>> who asked to be notified of new product announcements). >>> >>> At WISPAPALOOZA next week, we’ll be showcasing the SiteMonitor Base 3 >>> Classic Edition. >>> >>> The Base 3 is the successor of the current Base Unit II product. It’s >>> designed with an easy to use and mobile-friendly web interface virtually >>> identical to the one in our RackInjector product. Gone are the 1’s and 0’s >>> of the old SNMP-based web interface. Instead, everything is easy to >>> understand and much more intuitive. If you’re at WISPAPALOOZA, stop by and >>> take a look (and tell your friends too). >>> >>> In addition, the Base 3 is designed with the future in mind. The >>> existing Base Unit II product reached a point where there wasn’t any room >>> in the internal program memory to add more functionality. In contrast, >>> we’ve just barely touched the surface of what the Base 3 is capable of. >>> We’ll be adding more and more features as time goes on. >>> >>> The Classic Edition retains the existing form factor and maintains >>> electrical compatibility with the existing product line. It is designed as >>> a drop-in replacement for the older Base Units. At most sites, you’ll be >>> able to simply swap out a Base Unit II for a Base 3 and gain all of the >>> functionality of the newer Base 3. >>> >>> For those of you who have expansion modules (such as SyncInjectors, >>> PowerInjectors, additional I/O and/or other interfaces), our intent is to >>> support most expansion modules that have shipped. At release, you’ll be >>> able to manage the Base 3 and Revision H or later SyncInjectors and >>> PowerInjectors. Others will be added quickly afterward. The only possible >>> exception is some of the very first modules we shipped well over 7 years >>> ago – we’re still assessing the earliest modules to determine what’s needed >>> to support them. If we can support them, we will. >>> >>> For many of the expansion modules, you’ll instantly gain much more >>> functionality than was possible to accomplish with the previous Base Unit. >>> As a specific example, the SyncInjectors and PowerInjectors are gaining >>> greatly improved GPS and 1PPS status information, to help troubleshoot any >>> GPS receiver problems one might have. In addition, port descriptions are >>> now long enough to store pretty much any information and are set on a >>> per-port, not per-item basis. >>> >>> We’ll be taking pre-orders for the new Base 3 shortly, with units >>> hopefully shipping around the end of the year. Initially, pre-orders will >>> be limited to 2 per customer, primarily for in-network testing. The >>> pre-order price will be the same as the existing Base Unit II’s at $99.95. >>> We are still working on setting the final price, but it will be most likely >>> to be somewhat higher due to increased product costs. >>> >>> Although we feel that many of our customers will switch over to the Base >>> 3, we also know that some people will want to continue to deploy the Base >>> Unit II product to maintain consistency across their network. We currently >>> have no definite plans to discontinue the Base Unit II. We will continue to >>> stock it as long as customers continue to buy it fairly regularly. After >>> that, we will likely keep it available for purchase on a build to order >>> basis as long as it is economically feasible to do so. >>> >>> As always, if you have any questions, feel free to email us at >>> cust...@packetflux.com >>> >>> -- >>> - Forrest >>> -- >>> AF mailing list >>> AF@af.afmug.com >>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >>> >> -- >> AF mailing list >> AF@af.afmug.com >> http://af.afmug.com/mailman/listinfo/af_af.afmug.com >> > > > -- > - Forrest > > > -- - Forrest
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
