Monitoring the status of the CRs
You can view the status and other details of the primary server and media server CRs using the following commands:
kubectl get <PrimaryServer/MediaServer> -n <namespace> or
kubectl describe <PrimaryServer/MediaServer> <CR name> -n <namespace>
Following table describes the primary server CR and media server CR status fields:
Table:
Section | Field / Value | Description |
|---|---|---|
Primary Server Details Only one hostname and IP address for the respective primary server. | Host Name | Name of the primary server that should be used to access the web UI. |
IP | IP address to access the primary server. | |
Media Server Details Number of hostname and IP address is equal to the replica count mentioned CR spec. | Host Name | Name of the media server. |
IP | IP address to access the media server. | |
Attributes | Resource Name | Statefulset name of the respective server. |
Primary/Media server name | Name of the primary server or media server deployed. | |
Config checker status | Indicates the status of the config checker as passed, failed, or skipped. For more information on the Config-Checker, seeHow does the Config-Checker utility work. | |
SHA Fingerprint | Represents the SHA key fingerprint of the NetBackup primary server. Note: SHAFingerprint represents the SHA256 CA certificate fingerprint of the primary server. | |
Error Details | Code | A code assigned to an error encountered during the CR deployment or during the config-check operation. For more information on the error, refer to the NetBackup Status Code Reference Guide. |
Message | Message that describes the respective error code. | |
State | Success /Paused /Failed /Running | Current state of the custom resource, from one of the following:
|