Alarm Messages - 300sΒΆ
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 Overview.
In the following tables, the severity of the alarms is represented by one or more letters, as follows:
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 documentations:
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 ID: 300.003 |
Networking Agent not responding. |
Entity Instance |
host=<hostname>.agent=<agent-uuid> |
Severity: |
M* |
Proposed Repair Action |
If condition persists, attempt to clear issue by administratively locking and unlocking the Host. |
Alarm ID: 300.004 |
No enabled compute host with connectivity to provider network. |
Entity Instance |
host=<hostname>.providernet=<pnet-uuid> |
Severity: |
M* |
Proposed Repair Action |
Enable compute hosts with required provider network connectivity. |
Alarm ID: 300.005 |
Communication failure detected over provider network x% for ranges y% on host z%. or Communication failure detected over provider network x% on host z%. |
Entity Instance |
providernet=<pnet-uuid>.host=<hostname> |
Severity: |
M* |
Proposed Repair Action |
Check neighbor switch port VLAN assignments. |
Alarm ID: 300.010 |
ML2 Driver Agent non-reachable or ML2 Driver Agent reachable but non-responsive or ML2 Driver Agent authentication failure or ML2 Driver Agent is unable to sync Neutron database |
Entity Instance |
host=<hostname>.ml2driver=<driver> |
Severity: |
M* |
Proposed Repair Action |
Monitor and if condition persists, contact next level of support. |
Alarm ID: 300.012 |
Openflow Controller connection failed. |
Entity Instance |
host=<hostname>.openflow-controller=<uri> |
Severity: |
M* |
Proposed Repair Action |
Check cabling and far-end port configuration and status on adjacent equipment. |
Alarm ID: 300.013 |
No active Openflow controller connections found for this network. or One or more Openflow controller connections in disconnected state for this network. |
Entity Instance |
host=<hostname>.openflow-network=<name> |
Severity: |
C, M* |
Proposed Repair Action |
host=<hostname>.openflow-network=<name> |
Alarm ID: 300.015 |
No active OVSDB connections found. |
Entity Instance |
host=<hostname> |
Severity: |
C* |
Proposed Repair Action |
Check cabling and far-end port configuration and status on adjacent equipment. |
Alarm ID: 300.016 |
Dynamic routing agent x% lost connectivity to peer y% |
Entity Instance |
host=<hostname>,agent=<agent-uuid>,bgp-peer=<bgp-peer> |
Severity: |
M* |
Proposed Repair Action |
If condition persists, fix connectivity to peer. |
