Performs a set of checks to ensure that the cluster is working correctly.
diagnose cluster
Checks that “mycluster” is working correctly:
diagnose cluster
Cluster name...................mycluster Maximum instances..............4 Cluster node count.............1 Instances defined..............4 Is cluster locked..............Yes JDBC connection available......1 ase1 Yes JDBC connection available......2 ase2 Yes JDBC connection available......3 ase3 Yes JDBC connection available......4 ase4 Yes Instance Public Network........1 ase1 on blade1 (10.22.79.39) Reachable: Yes Instance Public Network........2 ase2 on blade1 (10.22.79.39) Reachable: Yes Instance Public Network........3 ase3 on blade1 (10.22.79.39) Reachable: Yes Instance Public Network........4 ase4 on blade1 (10.22.79.39) Reachable: Yes Has private Primary network.... No Has private Secondary network.. No Network ports required/instance 20 Minimum port allowed........... 1025 Maximum port allowed............65535 Current port strategy........... Public primary and secondary unique. ...The ports are sequenced primary followed by the next instance primary. ...When the primaries are are completed the secondary ports follow the same pattern. Recommended port strategy....... Public primary and secondary unique. ...The ports are sequenced primary followed by the next instance primary. ...When the primaries are are completed the secondary ports follow the same pattern.
diagnose cluster checks that:
A Unified Agent is running on each instance in the cluster.
The number of instances in the cluster does not exceed the value set for maximum number of instances.
The quorum file exists.
All instances are defined in the interfaces file and that port numbers do not conflict.
The primary and secondary protocol specifications do not overlap.
Each of the $SYBASE directories are shared.
