Troubleshooting Bonded Interfaces

Troubleshooting Workflow

1. Connect to the command line.

2. Log in to the Expert mode.

3. Check the status of the bond:

   cat /proc/net/bonding/<bond id>

4. If there is a problem, check if the physical link is down, as follows:

   1. Execute the following command:

      • In Gaia Clish The name of the default command line shell in Check Point Gaia operating system. This is a restricted shell (role-based administration controls the number of commands available in the shell).:

        show cluster bond name <bond_name>

      • In the Expert mode:

        cphaprob show_bond <bond_name>

   2. Look for a subordinate interface that reports the status of the link as no.

   3. Check the cable connections and other hardware.

   4. Check the port configuration on the switch.

5. Check if a VSX Virtual System Extension. Check Point virtual networking solution, hosted on a computer or cluster with virtual abstractions of Check Point Security Gateways and other network devices. These Virtual Devices provide the same functionality as their physical counterparts. Cluster Member Security Gateway that is part of a cluster. is down, by running:

   • In Gaia Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. Clish:

     show cluster state

   • In the Expert mode:

     cphaprob state

   If any of the VSX Cluster Two or more Security Gateways that work together in a redundant configuration - High Availability, or Load Sharing. Members has a State other than Active, see the R81 ClusterXL Administration Guide - Chapter Monitoring and Troubleshooting Clusters.

On a VSX Cluster Member, reboot is needed after the following actions on a bond interface:

1. Changing a bond mode.

2. Adding a subordinate interface into a bond

   Note - Removing a subordinate interface does not require reboot.

For further information regarding bond status and failovers, view logs in the Logs & Monitor view. Any interface bond status change is logged and can be viewed in Logs & Monitor.