9300 to Meraki Mgmt IP address on 198.18.0.0/28 range

[NetEngJH]

I have a very strange issue after converting a Catalyst 9300 to a 9300-M (non native beta).  During the conversion the switches never contacted the Dashboard and had a management IP address of 198.18.0.0/28 range.  I could see this from a connected router cdp neighbor details.  I couldn't manage via the front ports on this range, or use the console port so ended up factory resetting by holding down the mode button for 21s.  When the switches booted back up they successfully got DHCP address on private range, but then rebooted after a period of time, am guessing after downloading firmware, and now back to a management IP address within 198.18.0.0/28 and unable to reach the Dashboard.

Anyone any thoughts on this or experienced this before?  I know this range is used for local device management on 9300 switches.  But what I don't understand is why when DHCP is available it is defaulting to this as a management IP.

[Holli69]

Hi,

look at this document:

https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Me...

[PhilipDAth]

I had an issue recently like this upgrading a C9300-M to the IOS-Native beta.  My management interface was also using a 198.18.0.x address.

I'm not sure how to progress your issue though.  I think this'll need the help of support.

[NetEngJH]

Thanks.  Did a factory reset by holding the mode button down for 21s.  Came back online with a private IP address on VLAN1.  I can see successful DNS and SSL traffic going to Meraki public IPs but still can't get to a local status page.  Rebooted many times now and left for hours at a time to register but still showing as offline in the Dashboard.  Console port shows nothing, management port nothing.  The lack of visibility here is quite frustrating.  I have now a quite expensive switch door stop!