> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myrmex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Ruckus Switch

> Connect a Ruckus ICX (FastIron) switch to Myrmex over SSH — create the CLI account and add the integration.

import { Note, Steps, Step, CardGroup, Card, Tip } from '@mintlify/components';

Connect your **Ruckus ICX** switch (FastIron) so Myrmex can read the running configuration, document the device, and — with approval — run CLI operations. Myrmex reaches the switch over **SSH** through a [Collector](/documentation/agent-endpoint-security/collector-mode) on your network and queries it in real time.

## What Myrmex Can Do

<CardGroup cols={2}>
  <Card title="Read & document" icon="magnifying-glass">
    Run show commands to inspect ports, VLANs, and the running configuration — read on demand.
  </Card>

  <Card title="Run CLI commands" icon="terminal">
    Execute operational and configuration commands, with changes applied on approval.
  </Card>

  <Card title="Inventory" icon="network-wired">
    Track the ICX model, firmware version, and interfaces — nothing stored on the Myrmex side.
  </Card>
</CardGroup>

## Before You Start

* A **Collector** that can reach the switch's management IP over SSH. See [Deploying the agent](/documentation/agent-endpoint-security/installation) and [Collector mode](/documentation/agent-endpoint-security/collector-mode).
* An **account with CLI access** to the device — read-only is enough for analysis; read-write is required to run configuration changes.

## Step 1 — Create the Credential in Ruckus

<Steps>
  <Step title="Enable SSH">
    Generate the RSA host keys with `crypto key generate rsa`; FastIron enables SSH once host keys exist. Optionally disable Telnet to require SSH.
  </Step>

  <Step title="Create a user">
    Create a local user for Myrmex with a strong password and a privilege level — `0` (super-user) for read-write, or `5` (read-only) for analysis. Note the username and password.
  </Step>
</Steps>

<Tip>
  Prefer least privilege: start with a read-only account, and grant super-user access only when you want the agents to run changes for you.
</Tip>

## Step 2 — Add the Integration in Myrmex

From the [Directory](/documentation/ai-workspace/overview#the-directory), choose **Add Integration → Ruckus Switch**, then fill in:

| Field           | Description                                                                                           |
| --------------- | ----------------------------------------------------------------------------------------------------- |
| **Name**        | A unique name for this switch.                                                                        |
| **Description** | Optional note to identify the device.                                                                 |
| **IP**          | The switch management IP or hostname the Collector can reach.                                         |
| **SSH Port**    | The SSH port (default `22`).                                                                          |
| **Username**    | The CLI account created in Step 1.                                                                    |
| **Password**    | That account's password.                                                                              |
| **Model**       | Your Ruckus ICX model series.                                                                         |
| **Version**     | The FastIron firmware version running on the device, or **Other**.                                    |
| **Collector**   | The [Collector](/documentation/agent-endpoint-security/collector-mode) that opens the SSH connection. |

## Connect

Click **Connect** to validate the SSH connection and finish. The switch then appears under **Environment → Integrations**, and you can ask the [Integration Specialist](/documentation/multi-agent-system/integration-specialist-agent) about it in the Workspace.

<Note>
  Myrmex queries the switch in real time over SSH and acts only on approval. It does not store or retain the device's configuration or data on the Myrmex side.
</Note>