FIDO: Impact, Time of Day, Hold Down attributes

FIDO: Impact, Time of Day, Hold Down attributes

Alarms will be present in the FIDO database, but may be presented to the user in a different manner.  Optionally, alarms can be auto commented and correlated based on normal FIDO operation [such as topology or comment correlation].

Alarms are matched in many ways, either by the fully qualified alarm name, IP subnet, or alarm attribute.  valid operators are 'defined', 'equal' or 'match' [perl regexp].

You can determine the fully qualified alarm name this for an active alarm by examining the FIDO database, accessible via the web or CLI, or for an old alarm by examining the CLI fido_events log.  Here is an example of how you find the fully qualified alarm name from the fido_events.log file.  The key/value pair of importance is the 'UnmodifiedItem' key/value.

Jan 14 10:35:03 nibbler fido.pl[15107]: {"_log_line":{"parent":"20140114.409","length":19,"unmodified_item":"s-ex4200-lab-24f.wiscnet.net jnxOperatingState Fan 1-jnxOperatingState","item":"s-ex4200-lab-24f.wiscnet.net jnxOperatingState Fan 1","action":"Add","_alarm_data":{"info":null,"failures":1,"test":"jnxOperatingState","event_id":"20140114.410","time":1389717284,"status":"OK","file":"snmp","device":"s-ex4200-lab-24f.wiscnet.net","state":"runningAtFullSpeed","iso":4,"snmp_instance":"4.1.1.1","updated":1,"needed_failures":"1","start":1389717284,"start_text":"2014/01/14 10:34:44"},"event":"20140114.410"}} 
Examples:

* For time of day ignoring, you can list multiple time ranges, comma separated.  The 'ParseDate' module is used.

* Holddown time is in minutes or absolute time.  Absolute time takes priority over a minute based holddown.

* Impact values are:
1 = high priority
2 = normal priority
3 = low priority
4 = informational

for more info on below, see: FIDO: generic alarm matching criteria and examples

RCS/fido_attributes.config,v  -->  standard output

IPs are matched against a trie.  Attributes are matched in numerical order

@netcms1 sitelocal_config]$ cat fido_attributes.yaml 
#
#
# this file is controlled by ns-ansible-uwmadison.git.  Do not edit directly on host
#
#
---
attributes:
  '200':
    fido_holddown:
      reason: power outage
      time: '5'
    fido_impact:
      reason: power failure
      value: '1'
    matches:
      '10':
        key_match: test
        match: upsAdvInputLineVoltage

  '220':
    fido_impact:
      value: '2'
    matches:
      '10':
        key_match: test
        match: panSysHAState

  '1040':
    fido_help_files:
      value: BAN Support Process
    matches:
      '10':
        key_match:
          ___infohash___Descr: ''
          descr: ''
          device: ''
        match: ^fa-.*-ban
        match_re: 'true'

  '1160':
    fido_help_files:
      value: SMKE s-summitmke
    matches:
      '10':
        key_match:
          ___infohash___Descr: ''
          descr: ''
          device: ''
        match: s-summitmke
ip:
  10.151.90.0/24:
    fido_impact:
      value: '1'
  2607:f388:0:2200::/64:
    fido_help_files:
      value: MadIX
    fido_impact:
      reason: madIX peering
      value: '4'
  10.151.13.210:
    fido_help_files:
      value: fp-ctriaurora-3100-1-pri200s 



Keywords:FIDO: Impact, Time of Day, Hold Down attributes   Doc ID:38253
Owner:Michael H.Group:Network Services
Created:2014-03-08 15:16 CSTUpdated:2020-11-01 14:09 CST
Sites:Network Services, Systems & Network Control Center, University of Wisconsin System Network
Feedback:  0   0