Thanks Wes! It would be easier to just add the new string to the existing traps, and indicate that the original value is simply an index into the device table, and no longer represents what it did before. And fortunately, the piece in the table that needs to go away isn't the index, so we're good there.
Wendy -----Original Message----- From: Wes Hardaker [mailto:[email protected]] Sent: Thursday, June 23, 2011 6:44 PM To: Wendy McGowen Cc: [email protected] Subject: Re: MIB change questions >>>>> On Wed, 22 Jun 2011 08:38:18 -0500, Wendy McGowen <[email protected]> >>>>> said: WM> We have a set of traps that include a field indicating the location of WM> the device as an integer(currently slot); in the next release, the WM> location will be need to be returned as a string. So I'm guessing that WM> we need to mark the old traps as deprecated, and create new traps that WM> include the string instead of the integer value. Is that the correct WM> way to do this? Yes-ish. You can add new data to notifications without a problem [just don't expect old agents to send it], but to remove the older one you need to deprecate the entire notification, yes. WM> Also, it's okay to add a new "location" field to the existing device WM> table and mark the original "slot" table entry as deprecated, as WM> opposed to creating a whole new table, right? But then do I still WM> populate it with a value, or does that leave a "gap" in the table when WM> someone walks the entire table? You can deprecate a column that isn't an index without recreating the table, yes. If it's an index this won't work, however. And yes, if a manager walks a table where a column doesn't have any values, it'll get "holes". Most managers these days deal with this ok, but in the way distant past there was fears this would cause some managers problems. -- Wes Hardaker Cobham Analytic Solutions ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
