11.07.2015 Views

PDF user manual for CopperEdge 150

PDF user manual for CopperEdge 150

PDF user manual for CopperEdge 150

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7UDSVIn the CE<strong>150</strong>, every internal event generates an SNMP trap. Atrap is a record of the event that is captured and sent to theconfigured trap destinations <strong>for</strong> the system; it contains thesame in<strong>for</strong>mation as the event. For a listing of all currently supportedtraps associated with each event, see Appendix C.There is no one-to-one mapping between events and traps. Becauseof the way alarms are cleared internally, one or moreevents may translate into the same trap. In these cases, one ormore data fields can be used to distinguish the traps. For example,both the DLCIStateDisabled and DLCIStateEnabled eventsresult in a frDLCIStatusChange trap being generated.To view a chronological list of the 1,000 most recent traps(events) you can use the elog or cmTrapEvent group as describedabove. The same in<strong>for</strong>mation is also available sorted bythe type of trap or event. To access this list, use the cmTrap-Type group as described in the <strong>CopperEdge</strong> <strong>150</strong> CopperCraftReference and MIB Definitions <strong>manual</strong>.Traps can be sent to as many as ten different SNMP managers.The list of those designated to receive traps is contained in thecmTrapDestination table in the <strong>CopperEdge</strong> <strong>150</strong> CopperCraftReference and MIB Definitions <strong>manual</strong>.$ODUPVAlarms constitute one subset of events. When generated, analarm message contains the following in<strong>for</strong>mation:• Name of the alarm (such as FanFailure)• Source (module, port, link)• Severity (Critical, Major, Minor)• Time the event occurred• Other event-specific in<strong>for</strong>mationAlarm SeverityAlarms are divided into three levels of severity:• Critical—A service-affecting condition that requiresimmediate corrective action. Used when the entity istotally out of service and its capability must be restored.• Major—A service-affecting condition that requires urgentcorrective action. Used when there is a severedegradation of the entity’s capability, which must berestored.• Minor—An event or condition that does not affect service,but corrective action should be taken to prevent a moreserious fault.&RSSHU(GJH,QVWDOODWLRQDQG2SHUDWLQJ*XLGH

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!