Catalyst → Meraki Onboarding — Device Config Mode

00

Before you begin

Supported platform & release: Catalyst 9200 / 9300 / 9500 running IOS-XE 17.09.08 or later. Older releases don't offer the built-in cloud-registration path used here.
Four free consecutive VTY lines in the 16–98 range — Meraki provisions its secure access over them. Step 1 clears this.
Privilege-15 SSH credentials for the switch — you enter them in the dashboard during the claim (Step 3).
NETCONF-YANG available on the switch — Meraki drives configuration through it. Step 2 confirms/enables it.
Reachability to the Meraki cloud from the switch so cloud registration can complete.
Per-device registration: every switch — including each member of a stack — has its own Cloud ID and must be claimed individually.

1

Prepare the VTY lines

Why it's needed

Meraki needs at least four unused, consecutive VTY lines (numbered 16–98) to provision its secure access for cloud monitoring. This block leaves the higher VTY range free while keeping your normal admin access intact.

config · line vty

line vty 0 4
 exec-timeout 5 0
 privilege level 15
 transport input ssh
line vty 5 31
 exec-timeout 5 0
 privilege level 15
 transport input ssh
no line vty 32 98

Confirm the change

You shouldn't see anything past line 31.

verify

sh run | sec vty
line vty 0 4
 exec-timeout 5 0
 privilege level 15
 transport input ssh
line vty 5 31
 exec-timeout 5 0
 privilege level 15
 transport input ssh

Save it

exec

copy running-config startup-config

2

Register the switch to the Meraki cloud

What it does

Initiates cloud registration on the switch, makes sure the management API Meraki uses is on, then reads back the Cloud ID you'll claim with.

Initiate cloud registration

config

configure terminal
service meraki connect
end

Ensure NETCONF-YANG is enabled

exec

show netconf-yang status

If it isn't enabled, turn it on from global config:

config

configure terminal
netconf-yang
end

Save, then read the Cloud ID

exec

copy running-config startup-config
show meraki connect

Note

Every switch has its own Cloud ID — even members within the same stack. Each device has to be claimed individually in the dashboard, so record the Cloud ID from every switch you're onboarding.

3

Claim the switch in the Meraki dashboard

In the dashboard

Organization ▸ Inventory.
Claim Devices → Claim Individual Devices.
Enter the Cloud ID you read from show meraki connect.
Select the switch, then choose a Dashboard network.
Select Device configuration mode.
Enter the privilege-15 SSH credentials for the switch.
Confirm and complete the claim.

4

Verify

Go to Switching ▸ Switches in the dashboard.
The switch should appear — allow up to 15 minutes for setup to finalize.

Done

Once it shows up under Switches, cloud monitoring is live. Repeat Steps 2–4 for every additional switch (and every stack member), each with its own Cloud ID.

5

Troubleshooting

5.1 — "No 4 Consecutive VTY on the Device"

Error

The Catalyst switch lacks four unused, consecutive VTY line numbers between 16 and 98 inclusive — the range Meraki requires to provision secure access for cloud monitoring.

Fix

Run Step 1 of this document to free the higher VTY range, then retry the claim. That clears the error.

5.2 — The switch is auto-consolidating your VTY lines

Cause

On IOS-XE 17.4+, line auto-consolidation is on by default — it merges contiguous VTY blocks that share identical config back into one range, which can undo the split from Step 1.

Disable auto-consolidation, then split the block:

config

conf t
no line auto-consolidation

Then

Re-apply the VTY split from Step 1 so the 16–31 range stays separated, and save with copy running-config startup-config.