Collect Cambium Networks logs

Supported in:

This document explains how to ingest Cambium Networks logs to Google Security Operations using the Bindplane agent.

Cambium Networks switches and wireless devices generate syslog messages for network events, IDS alerts, and station activity. The parser extracts key-value pairs from syslog messages and maps them to the Unified Data Model (UDM).

Before you begin

Make sure you have the following prerequisites:

  • A Google SecOps instance
  • Windows Server 2016 or later, or Linux host with systemd
  • Network connectivity between the Bindplane agent and the Cambium Networks devices
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Administrative access to the Cambium Networks devices

Get Google SecOps ingestion authentication file

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Collection Agents.
  3. Download the Ingestion Authentication File

  4. Save the file securely on the system where the Bindplane agent will be installed.

Get Google SecOps customer ID

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Profile.

  3. Copy and save the Customer ID from the Organization Details section.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

  1. Open Command Prompt or PowerShell as an administrator.

  2. Run the following command:

    msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet

  3. Wait for the installation to complete.

  4. Verify the installation by running:

    sc query observiq-otel-collector

    The service should show as RUNNING.

Linux installation

  1. Open a terminal with root or sudo privileges.

  2. Run the following command:

    sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh

  3. Wait for the installation to complete.

  4. Verify the installation by running:

    sudo systemctl status observiq-otel-collector

    The service should show as active (running).

Additional installation resources

For additional installation options and troubleshooting, see Bindplane agent installation guide.

Configure the Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

  • Linux:

    sudo nano /etc/bindplane-agent/config.yaml

  • Windows:

    notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"

Edit the configuration file

  • Replace the entire contents of config.yaml with the following configuration:

    receivers:
    udplog:
        listen_address: "0.0.0.0:514"

exporters:
    chronicle/cambium_networks:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: CAMBIUM_NETWORKS
        raw_log_field: body

service:
    pipelines:
        logs/cambium_networks_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/cambium_networks

Configuration parameters

Replace the following placeholders:

  • Receiver configuration:

    • listen_address: IP address and port to listen on:
      • 0.0.0.0 to listen on all interfaces (recommended)
      • Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)

  • Exporter configuration:

    • creds_file_path: Full path to ingestion authentication file:
      • Linux: /etc/bindplane-agent/ingestion-auth.json
      • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
    • customer_id: Customer ID copied from the Google SecOps console
    • endpoint: Regional endpoint URL:
      • US: malachiteingestion-pa.googleapis.com
      • Europe: europe-malachiteingestion-pa.googleapis.com
      • Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
      • See Regional Endpoints for complete list

Save the configuration file

  • After editing, save the file:
    • Linux: Press Ctrl+O, then Enter, then Ctrl+X
    • Windows: Click File > Save

Restart the Bindplane agent to apply the changes

  • To restart the Bindplane agent in Linux, run the following command:

    sudo systemctl restart observiq-otel-collector

    1. Verify the service is running:

      sudo systemctl status observiq-otel-collector

    2. Check logs for errors:

      sudo journalctl -u observiq-otel-collector -f

  • To restart the Bindplane agent in Windows, choose one of the following options:

    • Command Prompt or PowerShell as administrator:

      net stop observiq-otel-collector && net start observiq-otel-collector

    • Services console:

      1. Press Win+R, type services.msc, and press Enter.
      2. Locate observIQ OpenTelemetry Collector.
      3. Right-click and select Restart.

      4. Verify the service is running:

        sc query observiq-otel-collector

      5. Check logs for errors:

        type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"

Configure syslog export from Cambium Networks devices

Cambium Networks has multiple device families, each with a different syslog configuration path.

ePMP 1000/2000/Force 180/200 and ePMP Elevate

  1. Sign in to the Cambium Networks GUI.
  2. Go to Configure > System > Syslog Logging.
  3. Configure the following settings:
    • Syslog Mask: Click Select All.
    • Server 1: Enter the Bindplane agent IP address.
  4. Click Save.

ePMP 1000 HS and cnPilot E400/E500/E501

  1. Sign in to the Cambium Networks GUI.
  2. Go to Configure > System > Event Logging.
  3. Configure the following settings:
    • Syslog Server 1: Enter the Bindplane agent IP address.
  4. Click Save.

  5. Optional: Log in to the device CLI using SSH and enter the following command to enable debug level logging:

    logging cnmaestro 7

  6. Save and Apply the settings.

cnPilot R200/R201/R190

  1. Sign in to the Cambium Networks GUI.
  2. Go to Administration > Management > System Log Settings.
  3. Configure the following settings:
    • Syslog Enable: Select Enable.
    • Syslog Level: Select INFO.
    • Remote Syslog Enable: Select Enable.
    • Remote Syslog Server: Enter the Bindplane agent IP address.
  4. Click Save.

PMP 450/450i/450m AP

  1. Sign in to the Cambium Networks GUI.
  2. Go to Configuration > cnMaestro.
  3. Set cnMaestro Agent Debug Log Level to INFO.
  4. Go to Configuration > Syslog.
  5. Configure the following settings:
    • Syslog DNS Server Usage: Select Disable DNS Domain Name.
    • Syslog Server: Enter the Bindplane agent IP address.
    • Syslog Server Port: Enter the Bindplane agent port number.
    • AP Syslog Transmit: Select Enabled.
    • SM Syslog Transmit: Select Enabled.
    • Syslog Minimum Level: Select info.
  6. Click Save.

PMP 450/450i/450m SM

  1. Sign in to the Cambium Networks GUI.
  2. Go to Configuration > cnMaestro.
  3. Set cnMaestro Agent Debug Log Level to INFO.
  4. Go to Configuration > Syslog.
  5. Configure the following settings:
    • Syslog Configuration Source: Select AP Preferred.
    • Syslog DNS Server Usage: Select Disable DNS Domain Name.
    • Syslog Server: Enter the Bindplane agent IP address.
    • Syslog Server Port: Enter the Bindplane agent port number.
    • Syslog Transmission: Select Obtain from AP.
    • Syslog Minimum Level Source: Select AP Preferred.
    • Syslog Minimum Level: Select info.
  6. Click Save.

UDM mapping table

Log Field UDM Mapping Logic
bssid read_only_udm.principal.mac Extracted from the kv_fields using the key bssid.
channel read_only_udm.security_result.about.resource.attribute.labels.value Extracted from the kv_fields using the key channel. Part of a label.
host_name read_only_udm.principal.hostname Extracted from the log message using the grok pattern.
ids_event read_only_udm.security_result.summary Extracted from the kv_fields using the key ids_event.
ids_status read_only_udm.security_result.description Extracted from the kv_fields using the key ids_status. Used as the description when present.
iap read_only_udm.security_result.about.resource.attribute.labels.value Extracted from the kv_fields using the key iap. Part of a label.
manufacturer read_only_udm.security_result.about.resource.attribute.labels.value Extracted from the kv_fields using the key manufacturer. Part of a label.
rssi read_only_udm.security_result.about.resource.attribute.labels.value Extracted from the kv_fields using the key rssi. Part of a label.
security read_only_udm.security_result.about.resource.attribute.labels.value Extracted from the kv_fields using the key security. Part of a label.
severity read_only_udm.security_result.severity Mapped from the log message using the grok pattern. alert maps to HIGH, warn maps to MEDIUM, everything else maps to LOW.
severity read_only_udm.security_result.severity_details Mapped from the log message using the grok pattern. Preserves the original severity value.
ssid read_only_udm.principal.application Extracted from the kv_fields using the key ssid.
timestamp read_only_udm.metadata.event_timestamp Extracted from the log message using the grok pattern and converted to a timestamp.
read_only_udm.metadata.event_type Determined based on the presence of values in the security_result and host_name fields. If both fields are present, the event type is set to STATUS_UPDATE, otherwise it's GENERIC_EVENT.
read_only_udm.security_result.about.resource.attribute.labels.key The value of this field is determined by the parser logic based on the specific key-value pair being processed. The possible values are: Internet_Access_Provider, manufacturer, channel, received_signal_strength_indicator, and encryption_standard.
read_only_udm.security_result.description If the severity is warn this field takes the value of kv_fields, otherwise it takes the value of ids_status.

Need more help? Get answers from Community members and Google SecOps professionals.