checkInfra command help output

Last Updated : Jul 21, 2022 |

You can use the checkInfra command to verify your cluster runtime configuration and the optional vCenter DRS rule when credentials are provided.

Usage: checkInfra [-C] [ -n ] [ -t ] [ -ha [-vu -va -vd -vc] ] [ -s ] [ -h ] [-S] [-Sd] [-p [-nl -nb -io] [-cn] ] ]
 -C|--connectivity : Perform a connectivity check between CCM and cluster nodes
 -cr|--credentials : Validate the vCenter user account in the CSP cluster
 -n|--ntpservers : Check to see if configured NTP servers are reachable and responsive
 -t|--timezone : Check to see if configured timezone is set on CCM and cluster nodes
 -l|--license : Check to see if configured license server is reachable. Also shows the current license Status
 -d|--dns : Check to see if configured servers are reachable and responsive.
 -L|--ext-logserver : Check to see if configured external log server is reachable.
 -a|--archive : Check to see if configured archive server is reachable.
 -S|--storage : Show overall status of storage services of the cluster.
 -Sd|--storage-details : Show current status of each storage component.
 -s|--show : Show current CSP Cluster configuration. If this option is given, the rest of the options are ignored
 -ha|--high-availability : Check to see if node anti-afinity is set.
 -vu|--vcenter-user : vCenter user ID created for CSP use
 -va|--vcenter-address : vCenter IP address or FQDN
 -vd|--vcenter-datacenter : vCenter datacenter name
 -vc|--vcenter-cluster : vCenter cluster name within the given datacenter
 -cc|--cluster-config : fullpatch to cluster-config.yaml file
 -p|--performance : Check to see if environment's IOPs, network laterncy, and network bandwidth meet the minimum requirement
 -nl|--network-laterncy : Sub-option of '-p|--performance' for checking network laterncy
 -nb|--network-bandwidth : Sub-option of '-p|--performance' for checking network bandwidth
 -io|--iops : Sub-option of '-p|--performance' for checking iops
 -cn|--cluster-nodes : Comma-seperated cluster node IPs or FQDNs
 -h|--help : Print this help message. If this option is given, the rest of the options are ignored
Examples:
checkInfra -C
 checkInfra -C -n
 checkInfra
 Note
 If no specific options are given, it assumes all options are set except for -s and -h

Example uses of checkInfra

  • Validate the stored HA audit credentials:

    $ checkInfra -cr

credentialsCheck:
  vCenter credentials validation for user=[nbo-local@vsphere.local]: Success

  • Validate the HA DRS rule:

    $ checkInfra -va 192.0.2.215 -ha -vu readOnly@vsphere.local -vd testDatacenter -vc testCluster 
  vCenter credentials validation for user=[readOnly@vsphere.local]: Success
  Check if cluster has 3 masters: Success
  Check if all cluster VMs all have the same DRS anti-affinity rule: Success
    DRS anti-afinity rule set for cluster nodes:
          ClusterNode245-1.3.0.0.144001: 240-rule
          ClusterNode244-1.3.0.0.144001: 240-rule
          ClusterNode246-1.3.0.0.144001: 240-rule

  • Default when no options are specified:

    $ checkInfra

connectivityCheck:
  Cluster Control Manager ---> ClusterNodes: Success
  Cluster Control Manager ---> Cluster K8APIServer: Success

ntpServersCheck:
  ClusterControlManager   ---> ntpServer[198.152.8.11]: Success
  ClusterControlManager   ---> ntpServer[timeServer.dr.example.com]: Success
timezoneCheck:
  ClusterNodes timezone [America/Denver]: Success

licenseCheck:
  ClusterNodes:           ---> licenseServer[licenseServer.dr.example.com]: Success

  Cluster License status: NORMAL

archiveCheck:
  Archive server is not configured
  Run 'ccm archive config help ' to find out how to configure archive server

externalLogServerCheck:
  external log server is not configured

dnsCheck:
  ClusterControlManager dns server: Success
  ClusterNodes dns server configuration: Success

storageCheck:
Cluster Storage overall status: Success
highAvailabilityCheck:
  vCenter credentials validation for user=[readOnly@vsphere.local]: Success
  Check if cluster has 3 masters: Success
  Check if all cluster VMs all have the same DRS anti-affinity rule: Success
    DRS anti-afinity rule set for cluster nodes:
          ClusterNode245-1.3.0.0.144001: 240-rule
          ClusterNode244-1.3.0.0.144001: 240-rule
          ClusterNode246-1.3.0.0.144001: 240-rule

  • Performance check where the cluster environment meets the requirements.

    $ checkInfra -p -cn 192.0.2.200,192.0.2.201,192.0.2.202
performanceCheck:
  checkNodesReachable:
      192.0.2.200: Success
      192.0.2.201: Success
      192.0.2.202: Success
  networkLatencyCheck:
      Max RTT 192.0.2.200 to 192.0.2.201: 0.323 ms
      Max RTT 192.0.2.200 to 192.0.2.202: 1.190 ms
      Max RTT 192.0.2.201 to 192.0.2.202: 0.357 ms
    Max rtt is within the max allowed network latency of 25ms.
  networkBandwidthCheck:
      Network bandwidth 192.0.2.201 to 192.0.2.200: 27.1 Gbits/sec
      Network bandwidth 192.0.2.202 to 192.0.2.200: 26.0 Gbits/sec
      Network bandwidth 192.0.2.202 to 192.0.2.201: 17.4 Gbits/sec
    Network bandwidth meet the minimum required network bandwidth of 1 Gbits/sec.
  iopsCheck:
    Checking node with SDS Disk[192.0.2.200]:
      This check will take at least 4 minutes....
          Testing Read IOPS...
          Testing Write IOPS...
          Random Read/Write IOPS: 41.1k/19.3k
    Checking node without SDS Disk[192.0.2.202]:
      This check will take at least 4 minutes....
          Testing Read IOPS...
          Testing Write IOPS...
          Random Read/Write IOPS: 38.2k/17.9k
    Random Read/Write IOPS meet the minimum required IOPS of 500.  Performance check completed.