Dell MIBs

[Tom Haddon]

So just to confirm, Patrick, if I delete one of the items from one MIB
but leave it in the other MIB do I risk missing any events, or are they
in fact the same events, and so there is no possibility of missing an
event?

So, for instance, if I delete the event below from the Dell Storage MIB,
is it possible that there could be an event generated on a Storage
Device that would not be caught by the entry in the Dell Open Manage MIB
with the same specific event number?

<event>
         <mask>
                 <maskelement>
                         <mename>id</mename>
 
 <mevalue>.1.3.6.1.4.1.674.10893.1.20.200</mevalue>
                 </maskelement>
                 <maskelement>
                         <mename>generic</mename>
                         <mevalue>6</mevalue>
                 </maskelement>
                 <maskelement>
                         <mename>specific</mename>
                         <mevalue>1306</mevalue>
                 </maskelement>
         </mask>
         <uei>uei.opennms.org/mib2opennms/alertRedundancyLost</uei>
         <event-label>StorageManagement-MIB defined trap event:
 alertRedundancyLost</event-label>

Thanks, Tom


On Thu, 2006-10-05 at 10:19 -0500, Patrick_Boyd at Dell.com wrote:
> As long as you pay attention to the alert and trace it back to the
> actual cause of the trap (it could be a power supply failure in the
> server or a disk failure in an external enclosure for example) and take
> the appropriate action then yes you can safely ignore the duplicate. 
> 
> -----Original Message-----
> From: Tom Haddon [mailto:tom at greenleaftech.net] 
> Sent: Thursday, October 05, 2006 10:18 AM
> To: Boyd, Patrick
> Cc: linux-poweredge-Lists
> Subject: RE: Dell MIBs
> 
> Thanks, Patrick.
> 
> So is it safe to purge any duplicates between the two MIBs based on the
> specific event number?
> 
> Thanks, Tom
> 
> On Thu, 2006-10-05 at 10:15 -0500, Patrick_Boyd at Dell.com wrote:
> > Ok, So you can have OMSA with out instrumentation services or with out
> 
> > storage management. And since we both have a redundacy lost alert we 
> > had to each include one in our MIB.
> > 
> > Hope that answers your question,
> > Patrick Boyd
> > Dell Storage Software Engineer
> > (512)728-3182
> >  
> > 
> > -----Original Message-----
> > From: linux-poweredge-bounces at dell.com 
> > [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Tom Haddon
> > Sent: Thursday, October 05, 2006 9:31 AM
> > To: linux-poweredge-Lists
> > Subject: Dell MIBs
> > 
> > Hi Folks,
> > 
> > I have an issue where I have two separate MIBs that seem to have 
> > overlaps in the events in them:
> > 
> > Dell Open Manage MIB:
> > 
> > <event>
> >         <mask>
> >                 <maskelement>
> >                         <mename>id</mename>
> >                         <mevalue>.1.3.6.1.4.1.674.10892.1</mevalue>
> >                 </maskelement>
> >                 <maskelement>
> >                         <mename>generic</mename>
> >                         <mevalue>6</mevalue>
> >                 </maskelement>
> >                 <maskelement>
> >                         <mename>specific</mename>
> >                         <mevalue>1306</mevalue>
> >                 </maskelement>
> >         </mask>
> >         <uei>uei.opennms.org/mib2opennms/alertRedundancyLost</uei>
> >         <event-label>MIB-Dell-10892 defined trap event:
> > alertRedundancyLost</event-label>
> > 
> > 
> > Dell Storage MIB:
> > 
> > <event>
> >         <mask>
> >                 <maskelement>
> >                         <mename>id</mename>
> > 
> > <mevalue>.1.3.6.1.4.1.674.10893.1.20.200</mevalue>
> >                 </maskelement>
> >                 <maskelement>
> >                         <mename>generic</mename>
> >                         <mevalue>6</mevalue>
> >                 </maskelement>
> >                 <maskelement>
> >                         <mename>specific</mename>
> >                         <mevalue>1306</mevalue>
> >                 </maskelement>
> >         </mask>
> >         <uei>uei.opennms.org/mib2opennms/alertRedundancyLost</uei>
> >         <event-label>StorageManagement-MIB defined trap event:
> > alertRedundancyLost</event-label>
> > 
> > As you can see the "id" field is different, but the "specific" value 
> > is the same. When I get an event from a server with the specific event
> 
> > of
> > 1306 per that server's event logs (in this case, pulling one of two 
> > power supplies), it is flagged as both events in my SNMP trap alerting
> 
> > software (I'm using OpenNMS).
> > 
> > Can anyone explain why these two MIBs have the same specific values? 
> > 
> > Thanks, Tom
> > 
> > --
> > Tom Haddon <tom at greenleaftech.net>
> > 
> > _______________________________________________
> > Linux-PowerEdge mailing list
> > Linux-PowerEdge at dell.com
> > http://lists.us.dell.com/mailman/listinfo/linux-poweredge
> > Please read the FAQ at http://lists.us.dell.com/faq
> --
> Tom Haddon <tom at greenleaftech.net>
-- 
Tom Haddon <tom at greenleaftech.net>