Port Channel

Location in GUI: Provision » SD-Access » Fabric Sites » [Site Name] » Port Channel

Diagram

Classes

devices (catalyst_center.inventory)

Name	Type	Constraint	Mandatory	Default Value
port_channels	List	[port_channels]	No

port_channels (catalyst_center.inventory.devices)

Name	Type	Constraint	Mandatory	Default Value
id	Integer		Yes
connected_device_type	Choice	TRUNK, EXTENDED_NODE	Yes
protocol	Choice	ON, LACP, PAGP	No
description	String		No
interface_names	List	String	Yes
native_vlan_id	Integer	min: 1, max: 4094	No
allowed_vlan_ranges	String		No

Port Channels bundle multiple physical interfaces on a fabric edge node into a single logical link, providing increased bandwidth and redundancy for connections to downstream devices such as Extended Nodes or trunked switches. Each port channel specifies the connected device type, negotiation protocol, member interfaces, and optional description. Port channels are configured per device within a Fabric Site. This resource is SDA fabric only.

The id field is a module-local identifier used to uniquely track each port channel per device. It is not sent to Catalyst Center. Catalyst Center controller auto-assigns the GUI name (e.g. Port-channel1, Port-channel2) based on the order requests arrive at the backend. Two port channels on the same device must have distinct id values.

Examples

Example-1: Extended Node Port Channel with PAgP

This example demonstrates how to configure a port channel that bundles three physical interfaces on an edge node to connect a downstream Extended Node. PAgP (Port Aggregation Protocol) is Cisco’s proprietary link aggregation negotiation protocol and is required when connecting Extended Nodes.

---
catalyst_center:
  inventory:
    devices:
      - name: EDGE02
        fqdn_name: EDGE02.cisco.eu
        device_ip: 198.18.130.2
        pid: C9KV-UADP-8P
        state: PROVISION
        device_role: ACCESS
        site: Global/Poland/Krakow/Bld A
        fabric_site: Global/Poland/Krakow
        fabric_roles:
          - EDGE_NODE
        port_channels:
          - id: 1
            connected_device_type: EXTENDED_NODE
            protocol: PAGP
            description: "EXTENDED NODE PORT-CHANNEL"
            interface_names:
              - GigabitEthernet1/0/15
              - GigabitEthernet1/0/16
              - GigabitEthernet1/0/17

Example-2: Trunk Port Channel with LACP

This example shows a port channel configured as a trunk link using LACP (Link Aggregation Control Protocol, IEEE 802.3ad) for negotiation with a standards-compliant downstream switch. Trunk port channels carry multiple VLANs and can optionally restrict the allowed VLAN range and define a native (untagged) VLAN.

---
catalyst_center:
  inventory:
    devices:
      - name: EDGE03
        fqdn_name: EDGE03.cisco.eu
        device_ip: 198.18.130.3
        pid: C9KV-UADP-8P
        state: PROVISION
        device_role: ACCESS
        site: Global/Poland/Krakow/Bld A
        fabric_site: Global/Poland/Krakow
        fabric_roles:
          - EDGE_NODE
        port_channels:
          - id: 1
            connected_device_type: TRUNK
            protocol: LACP
            description: "Uplink to distribution switch"
            interface_names:
              - GigabitEthernet1/0/23
              - GigabitEthernet1/0/24

Example-3: Multiple Port Channels per Device

This example demonstrates configuring several port channels on a single edge device with different id values, different protocols, and different connected device types. Each id produces a distinct Terraform resource instance, allowing all port channels to be managed independently.

The id is a module-local discriminator only — the actual GUI label (Port-channel1, Port-channel2, …) is assigned by Catalyst Center based on backend processing order, not by the value of id.

---
catalyst_center:
  inventory:
    devices:
      - name: EDGE04
        fqdn_name: EDGE04.cisco.eu
        device_ip: 198.18.130.4
        state: PROVISION
        device_role: ACCESS
        site: Global/Enterprise/Building_C
        fabric_site: Global/Enterprise
        fabric_roles:
          - EDGE_NODE
        port_channels:
          # Extended Node bundle - PAgP required
          - id: 1
            connected_device_type: EXTENDED_NODE
            protocol: PAGP
            description: "Extended Node - Floor 1 closet"
            interface_names:
              - GigabitEthernet1/0/1
              - GigabitEthernet1/0/2
          # Trunk uplink to legacy switch - static (no negotiation)
          - id: 2
            connected_device_type: TRUNK
            protocol: ON
            description: "Static trunk to legacy IDF switch"
            interface_names:
              - GigabitEthernet1/0/47
              - GigabitEthernet1/0/48
          # Trunk to standards-based partner switch
          - id: 3
            connected_device_type: TRUNK
            protocol: LACP
            description: "LACP trunk to partner DC switch"
            interface_names:
              - TenGigabitEthernet1/1/1
              - TenGigabitEthernet1/1/2