Troubleshoot the cluster

Use these methods to troubleshoot the devices and clusters:

• Use Logs to generates troubleshooting files for all nodes in the cluster. Use this option when you need one cluster-level collection instead of generating troubleshooting files from each node separately.

• Use CLI to run a predefined set of cluster diagnostic commands and displays the output. Use this option to check cluster configuration, member state, cluster health, control-plane transport statistics, packet drops, interface status, CPU usage, memory buffers, ARP entries, and reachability. The CLI option displays command output; it does not open an interactive CLI session.

  Commands
  show running-config cluster : Review the cluster group configuration, local unit, cluster interface, priority, health-check, auto-rejoin, and cLACP settings.
  show cluster info : Confirm that clustering is enabled and identify the control node, member state, software version, serial number, CCL IP address, CCL MAC address, and last join or leave state.
  show cluster info health: Check unit, interface, service, and overall cluster health.
  show cluster info transport cp : Review control-plane transport counters, including reliable and unreliable message counters, errors, retransmits, drops, and buffer conditions.
  show version : Capture platform, software, build, UUID, LSP, VDB, uptime, resource, and license context.
  show asp drop : Identify accelerated security path packet or flow drop reasons and counters.
  show counters : Review protocol, feature, and cluster CCL counters.
  show arp : Verify ARP entries for interfaces that participate in cluster communication.
  show int ip brief : Check interface IP addresses and administrative and line protocol status.
  show blocks : Check buffer availability and failed allocations.
  show cpu detailed : Check data path, control point, and total CPU usage.
  show interface ccl_interface: Review interface state, MTU, MAC address, IP address, traffic counters, errors, and drops for the cluster-related interface.
  ping ccl_ip size ccl_mtu repeat 2 : Test reachability to a cluster peer by using the packet size selected by the tool.

• Use the CCL Ping when you need to test cluster control link connectivity between joined cluster nodes.

• Troubleshooting files—If a node fails to join the cluster, a troubleshooting file is automatically generated. You can also generate and download troubleshooting files from the Devices > Device Management and then choose Add, ClusterGeneral area. For more information, refer to Generate troubleshooting files.

  You can also generate files from the Device Management page. Click More () and choose Troubleshoot Files.

• CLI output—Choose Devices > Device Management and then choose Add, ClusterGeneral area, you can view a set of pre-defined CLI outputs that can help you troubleshoot the cluster. These commands are automatically run for the cluster:

  You can also enter any show command in the Command field.