Monitoring the deployment subdomain
You can monitor the deployment subdomain in a multisystem environment.
The deployment subdomain, locations in the subdomain, and associated tiebreaker system can each be in one of several different states.
As you monitor the status of your multisystem environment, objects that are associated with the deployment subdomain can be in various states, depending on certain environmental conditions that can affect the high availability status of the deployment subdomain.
- Available
- The deployment subdomain, location, or tiebreaker is functioning normally.
- Degraded
- This state applies only to deployment subdomains and locations, and signifies that a problem has been detected with the deployment subdomain or the location. It can continue to function normally, but if the problem is not corrected, the state could change to Unavailable.
- Repairing
- A problem has been detected with the object and an attempt to repair the problem is underway. This state is transient. If the problem is repaired, the state transitions to Available. If the problem cannot be repaired, the state transitions to Degraded or Unavailable, depending on the severity of the problem.
- Unavailable
- The deployment subdomain, location, or tiebreaker can no longer function normally. Typically, you cannot deploy to a location that is unavailable.
- Unknown
- The state of the object cannot be determined. This state applies only to locations in a different subdomain from the local system location, or to subdomains that do not include the local system location.
When an object becomes degraded or unavailable, there might be a problem with the internal file system. In this situation, Cloud Pak System Software attempts to correct the problem automatically. You should monitor the situation and contact IBM® Software Support if the problem persists.