User Tools
Writing /app/www/public/data/meta/onboarding/snmpmanager/trap_override_intro.meta failed
onboarding:snmpmanager:trap_override_intro
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| onboarding:snmpmanager:trap_override_intro [2017/02/13 23:11] – dmcgee | onboarding:snmpmanager:trap_override_intro [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Trap Override Intro ====== | ||
| + | |||
| + | Author: David McGee | ||
| + | |||
| + | Trap overrides are put in place to manually override the severity of an active alarm. By default, informational alarms are not ticketed. Begin by selecting a particular MIB. This will then populate the next step which is to filter for text or to select a trap from the Trap Select dropdown menu. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | A number of common severities exist in the IDMS SNMP Manager. The standard conventions usually follow: Informational, | ||
| + | |||
| + | As an exercise, you should check out the Trap Knowledge over-ride configurations (Using the trap_knowledge table) on the QA systems for ExteNet Systems. Please exercise caution and consult a colleague before doing so. Identify a number of trap overrides that are currently in place. | ||
| + | |||
| + | In layman' | ||
| + | |||
| + | For **<Trap X>** received from **< | ||
| + | |||
| + | Examples of Trap Override scenarios/ | ||
| + | |||
| + | * For fanAlarm SNMP traps received from Mobile Access (MA_EVENTS_MIB), | ||
| + | * For doorOpen SNMP traps received from BTI (BTI_MIB), set the severity to be WARNING instead of MINOR | ||
| + | * For voltageLow SNMP traps received from VoltServer (VOLTSERVE_MGT100_MIB), | ||
| + | |||
Page Tools
