Comment 12 for bug 1834512

Revision history for this message
Elio Martinez (elio1979) wrote :

Using virtual environment, i was able to get the alarm related to the node where i brought down the data interface

+----------+--------------------------------------------------------------------------------------+-----------------------------+----------+---------------------+
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+----------+--------------------------------------------------------------------------------------+-----------------------------+----------+---------------------+
| 300.004 | 'br-phy0' port failed | host=compute-0.port=br-phy0 | critical | 2019-11-30T17:12:55 |
| | | | | .094458 |
Tested on :
###
### StarlingX
### Built from master
###

OS="centos"
SW_VERSION="19.09"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="20191122T023000Z"

JOB="STX_build_master_master"
<email address hidden>"
BUILD_NUMBER="327"
BUILD_HOST="starlingx_mirror"
BUILD_DATE="2019-11-22 02:30:00 +0000"

Can we check that alarm raised in the mtclog as well?