> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/devicelink/basic/rockwell/rockwell-stratix-switches.md).

# Rockwell Stratix Switches

## Overview

This page provides step-by-step instructions for setting up a Rockwell Stratix Switch backup within Copia's DeviceLink platform, using Copia's [Scripting](https://docs.copia.io/docs/devicelink/basic/copia-scripting.md) integration. This is based on a Rockwell recommended process.

The Stratix Switch runs an FTP Client, so it is able to "push" a backup over FTP to an FTP Server on a schedule. This means you need an FTP server running on the Agent or on a PC on the network that can receive the files from the switch.

The Stratix Switch will be configured to push **both its running configuration (.cfg) and its VLAN database (vlan.dat)** to the FTP server using Kron (*the internal Cisco scheduler*). Both files are required to successfully restore a switch, so both backups must be scheduled. A Copia Scripting project then pulls those files into the Copia repository.

## Requirements

The full procedure is documented in Rockwell KB article 595646 ("Disaster Recovery for Stratix Switches"). Page 7 begins the *Stratix Switch Configuration* section (prerequisites + Telnet/config-mode entry); the specific Kron command set is on page 9 under *Create Stratix Switch Backup Policy*.

Prerequisites:

* Console access to the switch — physically via cable, or remotely via Telnet
* The administrator password for privileged-mode access
* A reachable FTP server, plus the credentials and target path
* A Copia Agent that has access to the FTP server's target directory&#x20;

## FTP Server Setup

The Stratix Switch will push its backup files to an FTP server. Set up an FTP server on the Copia Agent machine or on another PC on the same network that the switch can reach.

#### Choose and install an FTP server

1. Any standard FTP server will work. A common choice is **IIS with the FTP role**, which is available on Windows 10 / Windows 11 / Windows Server.
2. For a simple Windows 11 IIS FTP example, see this tutorial: <https://www.youtube.com/watch?v=tTjUVNM6Iec>

#### Create an FTP user and target directory

1. Create a dedicated user account that the switch will use to authenticate to the FTP server.
2. Create a target directory on the FTP server where the switch will deposit its backup files (for example, `C:\StratixBackups\`). This directory will also be referenced by the Copia Scripting project later.
3. Grant the FTP user read/write access to the target directory.

#### Verify FTP connectivity

1. From the switch's network, confirm the FTP server is reachable on TCP port 21 (or whichever port you configured).
2. Confirm the FTP user can log in and place a file in the target directory before configuring the switch.

## Stratix Switch Configuration

#### Open a Telnet session and enter configuration mode

1. From a PC with network access to the switch, open a Telnet session: `telnet <IP Address>`
2. Enter the administrator password and press Enter.
3. Type `Enable` and press Enter — re-enter the admin password if prompted. The prompt changes from `>` to `#`.
4. Type `config t` and press Enter to enter configuration mode.

#### Create the Kron backup policy

Enter each line below via the Telnet session. Replace the FTP IP and Switch\_Name placeholders with your values. The `in 2` interval is in minutes; adjust using the `ddd:hhh:mmm` syntax (for example, `in 1:0:0` for once per day).

Running-config backup:

```
kron occurrence auto_backup in 2 recurring
policy-list auto_backup
kron policy-list auto_backup
cli sh run | redirect ftp://<FTP_IP>/pub/Switch_Name.cfg
```

VLAN database backup:

```
kron occurrence vlan_backup in 2 recurring
policy-list vlan_backup
kron policy-list vlan_backup
cli copy flash:vlan.dat ftp://<FTP_IP>/pub/Switch_Name_vlan.dat
```

Save the switch configuration so the Kron schedule persists across reboots.

#### Verify the scheduled backup

1. In the Telnet session, type `do show run` and press Enter. Scroll near the end of the running configuration and confirm the `kron occurrence` and `policy-list` entries are present.
2. After the next scheduled run, confirm that both the `.cfg` file and the `_vlan.dat` file appear in the FTP server's target directory.

## Project Configuration

Once the switch is reliably depositing backup files on the FTP server, configure a Copia Scripting project to pull those files into the Copia repository.

Click either of the *Add a Project* buttons in the Projects tab.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FnLMRaGaEvPzFA6CGv4qX%2Fimage.png?alt=media&amp;token=471c56f8-04af-4671-a6a2-e21c8c094f45" alt=""><figcaption></figcaption></figure>

The *Add a new project* configuration dialog will appear which allows you to fully configure the project, devices and job for the project.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FPy5h6amh9V4UEbexLJ4F%2Fimage.png?alt=media&amp;token=627821a0-494a-4dfb-bda9-55ba83718b20" alt=""><figcaption></figcaption></figure>

#### Define the Project

1. Choose **Scripting** as the *Project Type*.
2. Assign an **Agent** that has access to the FTP server's target directory. See more about this in the [Agents ](https://docs.copia.io/docs/devicelink/sitesandagents/agents.md)section of the documentation.
3. Set the Project Path to the repository and branch where the switch backups should be committed.
4. Enter a Project Name and optional Description, then click *Save and Continue*.

Configure the project script to copy the latest backup files (`.cfg` and `_vlan.dat`) from the FTP target directory into the Copia working directory so they can be committed to the repository.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FvcM2Z4Fo43UOIDFf3Xq7%2Fimage.png?alt=media&amp;token=174d7762-58dd-4958-b885-8258952ea312" alt=""><figcaption></figcaption></figure>

#### Define the Device

Since the Script exists on the Agent, there is no need to define a Device for Projects that use a Script during setup. You can skip to the Job section.

#### Define the Job

Creating Jobs is similar for all vendor types, and is described in the [Creating Jobs](https://docs.copia.io/docs/devicelink/jobs/creating-jobs.md) section.

1. Set the project **Schedule** to run shortly after the switch Kron schedule (for example, 30 minutes later) to ensure the freshly delivered file is captured.
2. Enable **Auto-Commit** and select the branch the backups should be committed to.
3. Click *Save Job*.

#### Submit the Configuration

Once complete, press *Submit Project Setup* to create the Project, Device(s) and Job(s).

By completing these steps, your Stratix Switch will be set up to push scheduled backups to an FTP server, and Copia will automatically commit those backups to the repository for change detection and version history.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FZbRnJBPYF3Ba9Kwj2iI3%2Fimage.png?alt=media&amp;token=f4369c82-201f-4fca-a0d7-57e2661ba83f" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.copia.io/docs/devicelink/basic/rockwell/rockwell-stratix-switches.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
