6.2.2.2. Clusters

6.2.2.2.1. Introduction

The clusters command of the set subgroup enables the aggregation to be configured on the GCap capture interfaces.
For more information on aggregation, see the paragraph Capture and Monitoring Interfaces monx between TAP and GCap: Aggregation Capability.
This command enables defining which interfaces are connected to the same TAP in order to ensure a correct flow interpretation.

Note

This functionality is necessary if the qualified Test Access Port (TAP) present in the architecture does not provide the interface aggregation functionality.

The cluster automatically inherits the MTU of the interface with the highest MTU in the grouping.

Aggregation has an Impact on the other functionalities.

---

6.2.2.2.2. Prerequisites

• User: setup

• Dependencies: activate at least two capture interfaces

---

6.2.2.2.3. Commands

6.2.2.2.3.1. Command to add an interface aggregation

(gcap-cli) set clusters add interfaces {mon0|mon1|mon2|mon3} {mon0|mon1|mon2|mon3} description DESCRIPTION

---

6.2.2.2.3.2. Command to activate or deactivate an interface aggregation

(gcap-cli) set clusters {enable|disable} NAME

The NAME field can be viewed by using the show clusters command.

---

6.2.2.2.3.3. Command to delete an interface aggregation

(gcap-cli) set clusters delete NAME

---

6.2.2.2.4. Example to create an aggregation of the interfaces mon0 and mon1 with the description test.

• Enter the following command.

  (gcap-cli) set clusters add interfaces mon0 mon1 description `test`
  

• Validate.
  The system displays the result.

  Creating cluster test with interfaces mon0, mon1
  Successfully created cluster `test`
  

---