> Source: [sk115516](https://support.checkpoint.com/results/sk/sk115516)

# sk115516 - Cluster member is down due to different Aggregator IDs on the Bond slave interfaces

| Property | Value |
|----------|-------|
| Solution ID | sk115516 |
| Date Created | 2017-01-16 |
| Last Modified | 2023-06-14 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.10 (EOS) |
| OS | Gaia |

## Symptoms

- * Output of "`cphaprob state`" command shows the State of a member is "Down".

* Output of "`cphaprob list`" command on the problematic cluster member shows the Critical Device "Interface Active Check" reports its state as "problem".

* Output of "`cphaprob -a if`" command on the problematic cluster member shows a Bond interface as "DOWN".

* Bond interface is shown as "Up" in Gaia Portal ("Network Management" section - "Network Interfaces" page - "Link Status" column shows "Up").

* Output of "`cphaconf show_bond -a`" command in R77.x or "`cphaprob show_bond`" command in R80.20 on the problematic cluster member shows a Bond interface as "DOWN" and that the number of its "Slaves in use" is less than the "Slaves configured".

  *Example* :

  ```
  
  [Expert@HostName:0]# cphaconf show_bond -a
  
                                        |Slaves     |Slaves |Slaves
  Bond name  |Mode               |State |configured |in use |required
  -----------+-------------------+------+-----------+-------+--------
  bond0      | Load Sharing      | DOWN | 2         | 1     | 1      
  ```

* Output of "`ifconfig -a`" command on the problematic cluster member shows that the relevant slave interface are "UP".

* Output of "`cat /proc/net/bonding/bond<N>`" command on the problematic cluster member shows that the Aggregator ID is different on the slave interface.

  *Example* :

  ```
  
  [Expert@HostName:0]# cat /proc/net/bonding/bond0
  Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)
  
  Bonding Mode: IEEE 802.3ad Dynamic link aggregation
  ...
  
  802.3ad info
  LACP rate: slow
  Active Aggregator Info:
          Aggregator ID: 1
          Number of ports: 1
          ...
  
  Slave Interface: eth0
  MII Status: up
  Link Failure Count: 3
  Permanent HW addr: ...
  Aggregator ID: 2
  
  Slave Interface: eth1
  MII Status: up
  Link Failure Count: 4
  Permanent HW addr: ...
  Aggregator ID: 1
  ```

* Following [sk92712](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92712) shows that the configurations on the Switch and the cluster member seems to be fine.

* The Bond physical slave interfaces have an identical speed set for them

## Cause

This may be due to one or more processes being down on the Orchestrator.   

OR  

The negotiation between the two Bond peers has been corrupted, so there has been reselection of the Aggregator ID on one of the slave interfaces.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content