starlingx/docs
Code Issues Proposed changes

Add new alarm (r7, dsR7, dsR6, r5)

Browse Source 
Add 900.006 alarm to listing.
Move 100.105, 100.112, 100.113, 300.001 and 300.002 alarms to openstack
Drop 300 series kubernetes file - now empty.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ibbcd515109540cbb85521332b5ef443c98f69ca5
(cherry picked from commit 7b8b0534c2)
This commit is contained in:
Ron Stone
2023-02-15 11:57:45 -05:00
parent b796cfa746
commit 3708aabfa2
7 changed files with 134 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

60
doc/source/fault-mgmt/kubernetes/100-series-alarm-messages.rst
View File

@@ -86,27 +86,6 @@ health of the system.
* - Proposed Repair Action
- Reduce usage or resize filesystem.
-----
.. list-table::
:widths: 6 25
:header-rows: 0
* - **Alarm ID: 100.105**
- <fs\_name\> filesystem is not added on both controllers and/or does not
have the same size: <hostname\>.
* - Entity Instance
- fs\_name=<image-conversion>
* - Degrade Affecting Severity:
- None
* - Severity:
- C/M\*
* - Proposed Repair Action
- Add image-conversion filesystem on both controllers.
Consult the System Administration Manual for more details.
If problem persists, contact next level of support.
-----
@@ -228,45 +207,6 @@ health of the system.
- Check cabling and far-end port configuration and status on adjacent
equipment.
-----
.. list-table::
:widths: 6 25
:header-rows: 0
* - **Alarm ID: 100.112**
- 'DATA-VRS' Port down.
* - Entity Instance
- host=<hostname>.port=<port-name>
* - Degrade Affecting Severity:
- Major
* - Severity:
- M
* - Proposed Repair Action
- Check cabling and far-end port configuration and status on adjacent
equipment.
-----
.. list-table::
:widths: 6 25
:header-rows: 0
* - **Alarm ID: 100.113**
- 'DATA-VRS' Interface degraded.
or
'DATA-VRS' Interface down.
* - Entity Instance
- host=<hostname>.interface=<if-name>
* - Degrade Affecting Severity:
- Major
* - Severity:
- C or M\*
* - Proposed Repair Action
- Check cabling and far-end port configuration and status on adjacent
equipment.
-----

0
doc/source/fault-mgmt/kubernetes/300-series-alarm-messages.rst → doc/source/fault-mgmt/kubernetes/300-series-alarm-messages.old
View File

53
doc/source/fault-mgmt/kubernetes/900-series-alarm-messages.rst
View File

@@ -99,6 +99,59 @@ health of the system.
-----
.. list-table::
:widths: 6 25
:header-rows: 0
* - **Alarm ID: 900.006**
- Device image update operation in progress.
* - Entity Instance
- host=controller
* - Degrade Affecting Severity:
- None
* - Severity:
- m\*
* - Proposed Repair Action
- Complete reboots of affected hosts.
-----
.. list-table::
:widths: 6 25
:header-rows: 0
* - **Alarm ID: 900.008**
- Kubernetes rootca update in progress.
* - Entity Instance
- host=controller
* - Degrade Affecting Severity:
- None
* - Severity:
- m
* - Proposed Repair Action
- Wait for kubernetes rootca procedure to complete.
-----
.. list-table::
:widths: 6 25
:header-rows: 0
* - **Alarm ID: 900.009**
- Kubernetes root CA update aborted, certificates may not be fully updated.
* - Entity Instance
- host=controller
* - Degrade Affecting Severity:
- None
* - Severity:
- m
* - Management Affecting Severity:
- w
* - Proposed Repair Action
- Fully update certificates by a new root CA update.
-----
.. list-table::
:widths: 6 25
:header-rows: 0

1
doc/source/fault-mgmt/kubernetes/index-fault-kub-f45ef76b6f16.rst
View File

@@ -107,7 +107,6 @@ Alarm messages
100-series-alarm-messages
200-series-alarm-messages
300-series-alarm-messages
400-series-alarm-messages
500-series-alarm-messages
750-series-alarm-messages

1
doc/source/fault-mgmt/openstack/index-fault-os-a1a5cae095b3.rst
View File

@@ -15,6 +15,7 @@ OpenStack alarm messages
.. toctree::
:maxdepth: 1
openstack-alarm-messages-100s
openstack-alarm-messages-300s
openstack-alarm-messages-400s
openstack-alarm-messages-700s

72
doc/source/fault-mgmt/openstack/openstack-alarm-messages-100s.rst Normal file
View File

@@ -0,0 +1,72 @@
.. slf1579788051430
.. _alarm-messages-100s:
=====================
Alarm Messages - 100s
=====================
The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall
health of the system.
For more information, see :ref:`Overview
<openstack-fault-management-overview>`.
In the following tables, the severity of the alarms is represented by one or
more letters, as follows:
.. _alarm-messages-100s-ul-jsd-jkg-vp:
- C: Critical
- M: Major
- m: Minor
- W: Warning
A slash-separated list of letters is used when the alarm can be triggered with
one of several severity levels.
An asterisk \(\*\) indicates the management-affecting severity, if any. A
management-affecting alarm is one that cannot be ignored at the indicated
severity level or higher by using relaxed alarm rules during an orchestrated
patch or upgrade operation.
Differences exist between the terminology emitted by some alarms and that used
in the |CLI|, GUI, and elsewhere in the documentation:
.. _alarm-messages-100s-ul-dsf-dxn-bhb:
- References to provider networks in alarms refer to data networks.
- References to data networks in alarms refer to physical networks.
- References to tenant networks in alarms refer to project networks.
.. _alarm-messages-100s-table-zrd-tg5-v5:
.. table:: Table 1. Alarm Messages
:widths: auto
+----------+-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| Alarm ID | Description | Severity | Proposed Repair Action |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | Entity Instance ID |
+==========+=====================================================================================+==========+===================================================================================================+
| 100.005 | <fs_name> filesystem is not added on both controllers and/or does not have the same | C/M\* | Add image-conversion filesystem on both controllers. |
| | size: <hostname>. | | Consult the System Administration Manual for more details. |
| | | | If problem persists, contact next level of support. |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | fs_name=<image-conversion> |
+----------+-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| 100.012 | 'DATA-VRS' Port down. | M | Check cabling and far-end port configuration and status on adjacent equipment. |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | host=<hostname>.port=<port-name> |
+----------+-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| 100.013 | 'DATA-VRS' Interface degraded OR 'DATA-VRS' Interface down. | C or M\* | Check cabling and far-end port configuration and status on adjacent equipment. |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | host=<hostname>.interface=<if-name> |
+----------+-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+

8
doc/source/fault-mgmt/openstack/openstack-alarm-messages-300s.rst
View File

@@ -58,6 +58,14 @@ patch or upgrade operation.
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | Entity Instance ID |
+==========+=====================================================================================+==========+===================================================================================================+
| 300.001 | 'Data' Port failed. | M\* | Check cabling and far-end port configuration and status on adjacent equipment. |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | host=<hostname>.port=<port-uuid> |
+----------+-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| 300.002 | 'Data' Interface degraded or 'Data' Interface failed. | C/M\* | Check cabling and far-end port configuration and status on adjacent equipment. |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | host=<hostname>.interface=<if-uuid> |
+----------+-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| 300.003 | Networking Agent not responding. | M\* | If condition persists, attempt to clear issue by administratively locking and unlocking the Host. |
+ +-------------------------------------------------------------------------------------+----------+---------------------------------------------------------------------------------------------------+
| | host=<hostname>.agent=<agent-uuid> |