Download here - Fognet Consulting
Transcript
9. Interpreting Events SN MP agents are typ ically very qu iet by d efau lt in term s of trap generation. Most events that are typ ically seen in the N N M alarm brow ser are generated by N N M itself. These are the Op enView enterp rise events. Mostly, these are N N M‟s p oller resu lts. N ote that all p oller resu lts in the alarm brow ser s how the nod e affected as the sou rce, bu t all p oll resu lts are in fact generated by the Op enView server itself. This can be m islead ing as there is no w ay to know that the actu al sou rce of the event w as the Op enView server versu s the nod e sou rce d isp layed in the alarm brow ser. N N M’s handling of generic and specific traps The SN MPv1 p rotocol d efines seven Generic SN MP trap s as follow s: 0 1 2 3 4 5 6 Cold Start Warm Start Link Up Link Dow n EGP N eighbor Loss Authentication Failure Enterprise The Enterp rise generic is sp ecial becau se it allow s for the u se of the “sp ecific” trap field to accom m od ate vend or extensions via variable bind ings (varbind s), so the Op enView Enterp rise N od e_d ow n event, w hich is generated by N N M, is conveyed w ith the follow ing SN MP d ata: Enterprise: Generic: Specific: Varbind s: .1.3.6.1.4.1.11.2.17.1 6 58916865 1,2,3…n Generic traps and origin event OID s SN MPv2 introd u ced the concep t of an event OID, so generic trap s (like au thentication failu res or link u p / d ow n trap s) w ou ld fall u nd er enterp rise .1.3.6.1.6.3.1.1.5.1 in the MIB tree. The old m ethod w as for 107