Hi - To make what the other folks have been saying more concrete:
Submit an internet draft. The draft would contain a MIB module. That MIB module would contain two definitions. The first would be for a "conceptual row" containing a single object (which you defined as "hrStorageAvail" below) with an AUGMENTS clause referring to the base conceptual row in the Host Resources MIB. The second would be the definition you proposed below. Including boilerplate and your explanation of the rationale, the whole thing should weigh in at about seven pages. Randy ----- Original Message ----- From: "Sheppy Reno" <[email protected]> To: <[email protected]> Sent: Tuesday, September 11, 2012 8:48 AM Subject: [OPSAWG] Addition of Available Space to Host-Resources-MIB After working with SNMP for quite a while we’ve repeatedly run into issues where monitoring software is unable to accurately determine the utilization of volumes on some Linux partitions due to regular processes being unable to access the reserved file space. I believe that the best way to correct this issue is to include an additional data point in the Host Resources MIB (RFC2790) that will return available space. This should have no negative impact on systems that do not utilization reserved space, but will allow for a much more accurate picture of the space that is truly available on those partitions using reserved space. I’ve been reading through the IETF site a bit, but I’m still not sure as to the best process to get this implemented. I was hoping someone on here could give me some tips on proceeding with this. From what I can see, I just need to update RFC2790 with the below information and resubmit. RFC 2790 Add: hrStorageAvail OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION “The amount of the storage represented by this entry that is available to non-superusers, in units of hrStorageAllocationUnits.” ::= { hrStorageEntry 8 } Thanks, Sheppy Reno -------------------------------------------------------------------------------- > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg > _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
