Cisco Catalyst 9300-M – Unable to Access CLI in Device Configuration Mode

[CSanghavi]

Hello Team,

We recently purchased Cisco Catalyst 9300-M series switches. Initially, we were unable to access the CLI for these switches and understood that this series is primarily designed for management via the Meraki Dashboard.

We created an account on the Meraki Dashboard and onboarded the devices. During the onboarding process, we were presented with two options (screenshots attached):

• Cloud Configuration

• Device Configuration

Since we wanted to configure the switches via CLI, we selected Device Configuration. However, even after applying this mode, we were unable to access CLI. The console session remains stuck at the login screen, prompting us to manage the switch only from the Meraki Dashboard, without allowing us to press any keys.

After opening a TAC case, we were advised to first roll back to Cloud Configuration mode and upgrade the switches. We followed this, successfully upgraded the devices, and then reverted back to Device Configuration mode. Unfortunately, the issue remains the same — no CLI access locally.

Request:
Could you please suggest what exact steps are required to enable CLI access in Device Configuration mode for 9300-M switches? Is there any additional configuration or upgrade path required to unlock CLI?

I’ve attached snapshots for reference.

Thanks in advance for your support.

[alemabrahao]

The full CLI access does not always get unlocked even when “Device Configuration” is selected, in some cases, you must involve Meraki support (you have already done that).

So I think the best option for you is to call Metaki support.

[CSanghavi]

Can we convert the IOS from Meraki to Catalyst??

[rhbirkelund]

You will likely need to engage Meraki Support. in order to convert the switch from Cloud Configuration to Device Configuration ( => Meraki to Catalyst).

[GIdenJoe]

Dashboard usually tells you that some telemetry subscriptions are missing to be able to enter conf t mode from dashboard.

When you enter the CLI, do you get a # symbol or a > symbol?

[CSanghavi]

No, we are not able to enter into the CLI, attached error already mentioned in snapshots