Summary: Step-by-step procedure for forming an LACP port-channel between a Cisco Catalyst 9300 running IOS-XE and a Catalyst 9200 in Meraki cloud-managed mode. The sequence is order-sensitive: the Meraki LAG is configured in the dashboard first, which causes a brief connectivity drop, and the IOS-XE LACP configuration must follow immediately to restore the link.
Forming a port-channel between a 9300 (IOS-XE) and a 9200 (Meraki managed) requires a specific sequence because the Meraki 9200 begins negotiating LACP as soon as the LAG is saved in the dashboard. This causes the active physical link to drop. The IOS-XE side must respond with LACP active immediately to bring the port-channel up and restore connectivity.
⚠️ Sequence Is Critical
Do not apply LACP on the 9300 before configuring the LAG in the Meraki dashboard — and do not configure the dashboard LAG until you are ready to apply the IOS-XE changes immediately after. The window between Step 2 and Step 3 is a live outage. The longer it takes to complete Step 3, the longer the disruption.
Remove any existing channel-group configuration from both 9300 ports. Shut down one of the two ports so only a single link is active. This gives a clean starting point and ensures that connectivity is maintained through the remaining active port while the Meraki dashboard is configured.
interface GigabitEthernet1/0/1
no channel-group
no shutdown
interface GigabitEthernet1/0/2
no channel-group
shutdown
Confirm the active port has an established link before proceeding.
In the Meraki dashboard, navigate to Switch → Configure → Link aggregation.
⚠️ Connectivity Drops Here
As soon as the configuration is saved, the 9200 begins negotiating LACP and the active physical link drops. Move to Step 3 immediately.
Immediately after saving the Meraki dashboard configuration, configure the Port-channel interface with the required L2 settings, bring it up, and add the active physical port to the channel-group. This restores connectivity.
interface Port-channel1
switchport mode trunk
switchport trunk native vlan <native-vlan-id>
switchport trunk allowed vlan <vlan-list>
no shutdown
interface GigabitEthernet1/0/1
channel-group 1 mode active
Once LACP negotiates between the 9300 and the 9200, the Port-channel comes up and connectivity is restored via the single active link.
With the port-channel up and connectivity restored, add the second 9300 port to the channel-group and bring it up.
interface GigabitEthernet1/0/2
channel-group 1 mode active
no shutdown
The second link joins the bundle via LACP negotiation. Both physical ports should now be active members of the port-channel.
show etherchannel summary
show lacp neighbor detail
In show etherchannel summary, confirm:
In show lacp neighbor detail, confirm:
LACP_Activity: Active on the Meraki side