03-04-2016 10:10 AM - edited 07-05-2021 04:43 AM
Hi all,
I am at a loss here...hoping someone can help.
I am in the the process of doing a network refresh and we have bought a number of 3650 IP Base 24port and 48port switches and 2602 APs.
I have configured a core switch stack (4 x 48 port stacked) as the mobility controller with all other 24\48 port switches connected directly or indirectly via either ethernet or fiber trunk ports and all set as management agents and added to a default switch peer group, with centralized management enabled.
All the switches are running 3.07.03E IOS and have identical configs... literally copied and pasted just with the hostname and VLAN1 IP address changed.
First few switches are fine... they joined the switch peer group, Data and Control link show as up, after they detected the MC they rebooted to upload the MC config... The APs that are connected to them register and work fine.
But 2 switches, for some reason only the Data link shows as up - the control link shows as down. These have identical config as other switches that are working fine. There are even other switches connected back to the MC via trunk ports on these 2 switches so its not a connectivity issue. The MC can ping them, they can ping the MC - nothing between them except a fibre connected trunk port.
When I connect them I see "%MM-6-MEMBER_UP: 1 wcm: Data path to mobility member X.X.X.X is UP" message on the MC but I don't get the follow up Control Path message.
I am really stuck here... I have reloaded them and the core MC switches several times, I have reinstalled the Config and the IOS (even tried downgrading to 3.6.4E) but to no avail.
Any ideas?
03-04-2016 11:09 AM
To follow on from this.... I have just opened Cisco Network assistant and ran a discovery on my network - the 2 switches in question are showing up with the below host names - everything else is showing the normal hostname I have set for them.
BOOTLDR: MD0002R01.0112182013"hostname"
I am guessing something must be corrupt with the IOS?
11-29-2016 05:24 AM
Hi,
Have you found a solution to fix the "possible" corrupt bootloader? We are experiencing also some problems with the wireless controller and the bootloader version is also the MD0002R01.0112182013.
Thank you
07-12-2019 01:34 PM
Did anyone figure out what was going on with this? I have a 3650 that is showing the same way in CNA and can't figure it out. Please help!!
Thanks
Jonathan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide