ncompass_control_interface_down_alarms
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ncompass_control_interface_down_alarms [2023/11/10 14:54] – walkeradmin | ncompass_control_interface_down_alarms [2023/11/21 12:05] (current) – [Resolve Alarm on Device (Preferred)] walkeradmin | ||
---|---|---|---|
Line 29: | Line 29: | ||
{{ : | {{ : | ||
\\ | \\ | ||
+ | This will bring up a second window called 'Alarm Overrides' | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | From here we can set the Severity to say Ignore, this alarm would then disappear from nCC ESM (it will still be visible on the actual hardware device UI if it has one). | ||
+ | \\ | ||
+ | \\ | ||
+ | The issue with this method is that nCompass will ignore any ' | ||
+ | \\ | ||
+ | \\ | ||
+ | ---- | ||
+ | ==== Resolve Alarm on Device (Preferred) ==== | ||
+ | The second (and better) way to deal with this is to deal with the alarm on the hardware so that nCompass Control ESM never sees the alarm. | ||
+ | \\ | ||
+ | \\ | ||
+ | In the example of say an Encoding Live or a Multiplexer, | ||
+ | \\ | ||
+ | \\ | ||
+ | First SSH in to the device and login. | ||
+ | \\ | ||
+ | \\ | ||
+ | For CentOS/Alma Linux navigate to the / | ||
+ | \\ | ||
+ | < | ||
+ | ll | ||
+ | |||
+ | -rw-r--r--. 1 root root 280 Aug 7 12:16 ifcfg-eno1 | ||
+ | -rw-r--r--. 1 root root 272 Aug 7 11:04 ifcfg-eno2 | ||
+ | -rw-r--r--. 1 root root 272 Aug 7 11:04 ifcfg-eno3 | ||
+ | -rw-r--r--. 1 root root 263 Nov 10 14:24 ifcfg-eno4 | ||
+ | </ | ||
+ | |||
+ | Here we can see the configuration file for eno4 - <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | We can see the contents of the file using the <color # | ||
+ | \\ | ||
+ | < | ||
+ | cat ifcfg-eno4 | ||
+ | |||
+ | TYPE=Ethernet | ||
+ | PROXY_METHOD=none | ||
+ | BROWSER_ONLY=no | ||
+ | BOOTPROTO=static | ||
+ | DEFROUTE=no | ||
+ | IPV4_FAILURE_FATAL=no | ||
+ | IPV6INIT=yes | ||
+ | IPV6_AUTOCONF=yes | ||
+ | IPV6_DEFROUTE=yes | ||
+ | IPV6_FAILURE_FATAL=no | ||
+ | NAME=eno4 | ||
+ | UUID=f6354b95-a63e-4f4c-aee9-e43e29537fe2 | ||
+ | DEVICE=eno4 | ||
+ | ONBOOT=yes | ||
+ | NM_CONTROLLED=yes | ||
+ | </ | ||
+ | |||
+ | Depending on your device, the default config may differ, but the two lines we are interested in are: | ||
+ | \\ | ||
+ | < | ||
+ | ONBOOT=yes | ||
+ | NM_CONTROLLED=yes | ||
+ | </ | ||
+ | |||
+ | Edit the <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | ONBOOT=< | ||
+ | \\ | ||
+ | NM_CONTROLLED=< | ||
+ | \\ | ||
+ | \\ | ||
+ | Save the configuration file and reboot the server. | ||
+ | \\ | ||
+ | \\ | ||
+ | After the reboot, the active alarm in nCC will disappear, although this might take a minute or so. | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
ncompass_control_interface_down_alarms.txt · Last modified: 2023/11/21 12:05 by walkeradmin