Using the cldisp command

Edit online

The /usr/es/sbin/cluster/utilities/cldisp command provides the application-centric view of the cluster configuration. This utility can be used to display resource groups and their startup, fallover, and fallback policies.

To show cluster applications:

  1. From the command line, enter smit sysmirror.
  2. In SMIT, select Cluster Applications and Resources > Resources > Configure User Applications (Scripts and Monitors) > Show Cluster Applications and press Enter.

    SMIT displays the information as shown in the example:

    #############
APPLICATIONS
#############

 Cluster Test_Cluster_Cities provides the following applications: 
 Application_Server_1 Application_Server_NFS_10
      Application: Application_Server_1 State: {online}

Application 'Application_Server_NFS_10' belongs to a resource group 
which is configured to run on all its nodes simultaneously. No 
fallover will occur.
 This application is part of resource group 'Resource_Group_03'.
  The resource group policies:
     Startup: on all available nodes
    Fallover: bring offline on error node
     Fallback: never
  Nodes configured to provide Application_Server_1: Node_Kiev_1{up} Node_
Minsk_2{up} Node_Moscow_3{up}
  Nodes currently providing Application_Server_1: Node_Kiev_1{up} Node
_Minsk_2{up} Node_Moscow_3{up}
  Application_Server_1 is started by /usr/user1/hacmp/local/ghn_start_4
  Application_Server_1 is stopped by /usr/user1/hacmp/local/ghn_stop_4
  Resources associated with Application_Server_1:
  Concurrent Volume Groups:
Volume_Group_03
  No application monitors are configured for 
Application_Server_1.

      Application: Application_Server_NFS_10 State: {online}
  This application is part of resource group 
'Resource_Group_01'.
  The resource group policies:
     Startup: on home node only
     Fallover: to next priority node in the list
     Fallback: if higher priority node becomes available
  Nodes configured to provide Application_Server_NFS_10: Node_Kiev_1{up}...

Here is an example of the text output from the cldisp command:

app1{online}
This application belongs to the resource group rg1.
Nodes configured to provide app1: unberto{up} lakin{up}
The node currently providing app1 is: unberto {up}
The node that will provide app1 if unberto fails is: lakin
app1 is started by /home/user1/bin/app1_start
app1 is stopped by /home/user1/bin/app1_stop
Resources associated with app1:
srv1(10.10.11.1){online}
Interfaces are configured to provide srv1:
lcl_unberto (en1-10.10.10.1) on unberto{up}
lcl_lakin (en2-10.10.10.2) on lakin{up}
Shared Volume Groups: NONE
Concurrent Volume Groups: NONE
Filesystems: NONE
AIX Fast Connect Services: NONE
Application monitor of app1: app1
Monitor: app1
Type: custom
Monitor method: /home/user1/bin/app1_monitor
Monitor interval: 30 seconds
Hung monitor signal: 9
Stabilization interval: 30 seconds
Retry count: 3 tries
Restart interval: 198 seconds
Failure action: notify
Notify method: /home/user1/bin/app1_monitor_notify
Cleanup method: /home/user1/bin/app1_stop
Restart method: /home/user1/bin/app1_start