ap won't book becuase of console

[nw-netadmin]

Hello,

I have an issue that I'd like some input on. I have 6 CW9164I running firmware MR 31.1.6. They are connected to 2 MS130-24P running firmware MS 17.2.1.

This is a new installation for new office currently under construction. Before we installed in the ceiling, I connected them all the same switches with the same switch ports and the booted and connected to the cloud without issue.

When I had them installed, I had the electricians run 2 cat6 cables to each. I connected one to the network/poe port and the other to the console cable. For about 3 weeks, we've been troubleshooting a weird issue where the AP boots to solid orange.

Switch - 3' Patch - AP - no problem

Switch - 3' Patch - 26' in wall cable - AP - stays solid orange.

We tried various patch cables, switch ports, and cables. Today, I figured out that if I simply unplugged the 2nd cable from the console port, the AP boots up fine and is connected to the cloud. So, now I am trying to figure out if there is something wrong with the in-wall cabling.

Here is the question: is there anything about this access point that would keep it from fully booting when there is an open cable connected to the console port? To be clear, there is not a PC or anything on the other end of that console-connected cat6 cable. It's just an open cable, terminated in a patch panel.

I am going to do a desk level test, but was hoping to put this out there in the meantime. Maybe there is something about the AP and it's boot up process that I don't understand.

Thank you

[alemabrahao]

It is not likely to cause any problems, there is a high probability that there is a problem with the cable that was installed.

[alemabrahao]

What you can do is take the AP and do a bench test.

[nw-netadmin]

yeah, I did a bench test and it came up just fine with an open cable in the console port.

[alemabrahao · Accepted solution]

Perfect, so everything leads us to believe that there is probably some problem with the cable that was passed, perhaps the color sequence.

[nw-netadmin]

Here is a more specific result of the test:

scenario 1

AP Network Port <-> 6' patch cable <-> in wall cable - patch panel <-> 6' patch cable - poe switch

AP Console Port <-> 6' patch cable

result: boots to solid green.

scenario 2

AP Network Port <-> 6' patch cable <-> in wall cable - patch panel <-> 6' patch cable - poe switch

AP Console Port <-> 6' patch cable <-> in wall cable - patch panel

result: solid orange.

Conclusion: it isn't the patch cable in the console port that is causing the problem. It's the cable in the wall that is connected to the console port that is causing the problem. Perhaps it is picking up enough noise so that the AP thinks there is input and doesn't know what to do with it.

[Mloraditch]

I'm struggling to find the reference info or perhaps it was just another post somewhere, but Im pretty sure I have heard of this and it is related to a boot sequence thing. Considering Meraki APs don't support console use, I would leave it unplugged.

[nw-netadmin]

yeah, that's what we are doing for now. I think this particular model is kind of a hybrid cisco/meraki ap and this why it has a console port. But, to your point, I am using it as meraki.

[Mloraditch]

Yes CW aps (and all new Meraki aps from here on out) can operate in either mode but with Meraki console is disabled.

[cmr]

@Mloraditch I remembered the same, as you said leave it unplugged as it has no use in Meraki mode.

[PhilipDAth]

What does the switch say if you ask it to test the cable?

https://documentation.meraki.com/MS/Monitoring_and_Reporting/Using_the_Cable_Test_Live_tool

[nw-netadmin]

At one point, it said that there were open wires and the cable length was wrong. However, since then they re-terminated and certified the cable.

[PhilipDAth]

Is the AP behaving now?

[nw-netadmin]

it is fine now

[nw-netadmin]

Thanks to everyone for participating in this conversation.

I am just trying to understand if there is an identifiable function on the AP that would explain this behavior. ie - some specific element that says, "hold on, there is a cable in my console port" and prevents it from fully booting or connecting to the meraki cloud.