---
title: "✅ Deployment Checklist: Basking Connector for Cisco Catalyst Center"
description: Connector Submitter Run test logs through the Connector to validate its output (no data will be sent):
---

[Skip to content](https://support.basking.io/deployment-checklist-basking-connector-for-cisco-catalyst-center#main-content)

![logo-basking-white](https://support.basking.io/hs-fs/hubfs/logo-basking-white-2.png?width=180&height=31&name=logo-basking-white-2.png)

Open main navigation

Close main navigation

- [Login into Basking](https://app.basking.io/)

[Login into Basking](https://app.basking.io/)

 Hello. How can we help you?

- There are no suggestions because the search field is empty.

1. [Documentation](https://support.basking.io/?hsLang=en)
2. [Technical Documentation](https://support.basking.io/technical-documentation?hsLang=en)

# ✅ Deployment Checklist: Basking Connector for Cisco Catalyst Center

### **1. Preparation**

- **Confirm Access to Catalyst Center Logs**   
  Ensure logs (especially roaming events and device registrations) can be accessed or exported from Cisco Catalyst Center. See our guide on Basking WLAN Controller [here](https://support.basking.io/how-do-i-use-basking-wlan-connector?hsLang=en) for a detailed overview of the data architecture.
- **Provision a Linux Host Machine** 
    - Ensure network access between the Catalyst Center (or its log-exporting machine) and the Connector host.
    - Ensure network access between the Connector host and Basking servers (\*.connect.basking.io)
    - Requirements: 1Gi RAM, x86 Machine (additional architectures may be supported on request)

- **Pre-deployment checklist**:  
    - Provide Basking with a sample of log output from Cisco Catalyst

- - Receive a **Connector binary** from Basking
    - Verify the included **configuration file**

- - Receive ORG\_SECRET environment variable and configure it on the Connector host machine

- - Receive a **Customer-specific encryption key** for shared double-encryption

---

### **3. Log Transmission Setup**

- **Enable Logs in Logging Settings in Catalyst Center** 
    - The Basking Connector requires the following log message types: 
          - Roaming
          - Device registration
          - Device deregistration
- **Ensure logs can be sent to the Connector via HTTP/HTTPS**
- **Ensure the Submitter can reach basking servers (\*.connect.basking.io)**
- **\[optional\] Manual log stream example:**$\> cat latest.log | grep ‘ROAMING|REGISTRATION|DEREGISTRATION’ | curl -XPOST -H 'content-type:text/plain' --data-binary @- http://\<connector-host\>:8081
- **\[optional\] Automate with Cron Job** Add a cron job (e.g., /etc/crontab) to execute the above every 5 minutes:  
  \*/5 \* \* \* \* root /opt/basking/send\_logs.sh

---

### **4. Deployment Checks**

**Connector**

1. Create a configuration file from the provided example:  
   $\> cp connector.yml.wlc.example connector.yml
2. Modify the configuration file to your needs (connector.yml)
3. Ensure the Connector is operational (no data will be sent):  
   $\> ./connector  
   \[INFO\]: 2025/01/01 00:00:00.314159 listening on port 4431
4. Ensure the connector is reachable from the log machine:  
   $\> curl -i basking-connector.my-network.com:4431  
   HTTP/1.1 204 No Content

**Submitter**

1. Create a configuration file from the provided example:  
   $\> cp submitter.yml.example submitter.yml
2. Modify the configuration file to your needs (submitter.yml)
3. Ensure the submitter is operational and Basking servers are reachable:  
   $\> ./submitter  
   \[INFO\]: 2025/01/01 00:00:00.314159 submitting data

---

### **5. Data Auditing & Validation**

Run test logs through the Connector to validate its output (no data will be sent):

1. Run the Connector in DEBUG mode:  
   $\> LOG\_LEVEL=DEBUG ./connector &
2. Submit test logs via the Connector:  
   $\> cat wlc.log | curl -XPOST -H'content-type:text/plain' --data-binary @- localhost:4431
3. Review console output to verify data extraction and anonymization.

---

### **6. Go-Live**

- Ensure the host machine contains: 
    - Connector binary *(connector*)
    - Submitter (*submitter*)
    - Connector configuration (connector.yml)
    - Submitter configuration (submitter.yml)

- Ensure the host machine can be reached by the log emitter
- Ensure the host machine can reach Basking servers (\*.connect.basking.io)
- Configure ORG\_SECRET environment variable on the host machine
- Inform Basking support for final validation & calibration at team@basking.io

- [Using the app](https://support.basking.io/using-the-app?hsLang=en#main-content)

    - [User Management](https://support.basking.io/using-the-app?hsLang=en#user-management)
    - [Organization Settings](https://support.basking.io/using-the-app?hsLang=en#organization-settings)
    - [Instant Insights](https://support.basking.io/using-the-app?hsLang=en#instant-insights)
    - [Live Feed](https://support.basking.io/using-the-app?hsLang=en#live-feed)
    - [LeaseOps](https://support.basking.io/using-the-app?hsLang=en#leaseops)
- [FAQ](https://support.basking.io/faq?hsLang=en#main-content)

    - [API](https://support.basking.io/faq?hsLang=en#api)
- [Technical Documentation](https://support.basking.io/technical-documentation?hsLang=en)
- [Glossary](https://support.basking.io/glossary?hsLang=en)

[![Chill listening crop-3](https://support.basking.io/hs-fs/hubfs/logo-basking-1.png?width=141&height=24&name=logo-basking-1.png "Chill listening crop-3")](http://basking.io)

basking.io Help Center

<https://twitter.com/basking_io> <https://www.linkedin.com/company/basking-workplace-analytics>

Copyright © 2026, Basking.io