AIR CAP 3602I-E-K9 configur

[tony99982]

Hello,

Im having problems configuring my access point AIR CAP 3602I-E-K9.

I connected the AP with a POE (one connection 'TO AP' and other one 'TO SWITCH') to a switch which is connected to the main internet.

I can see the AP's IP address in terminal, but when I try to access that IP address in a webbrowser I can't get access.

My question is: How can I configure the AP?

I have an iMac.

Thanks in advance!

Tony

[patoberli]

Sorry for my wording, Console = Serial in Cisco terms.

[tony99982]

---

@patoberli wrote:
You use some console program. OS X probably has one included, but I don't work with Apple. In any case, there are many, Putty for example. When you start it, you don't enter the IP address, you enter the Serial Port (often the number 1 or COM1). After that it works exactly like an SSH connection, albeit a bit slower. The other end of the serial cable comes into the AP serial port.

The Ethernet socket should also be connected, as you have now, for power reasons. It will also allow you to directly test the configuration.



Here an old configuration guide: https://www.cisco.com/c/en/us/support/docs/interfaces-modules/security-modules-routers-switches/116586-config-ap-00.html

Or this one: https://rscciew.wordpress.com/2014/05/24/single-ssid-configuration-on-autonomous-ap/

---

I've come so far to get the cables and after entering these commands

'cd /dev^

'ls -ltr /dev/*usb*'

I found out what the port name is, then I type 'screen /dev/tty.NAME OF THE PORT'

A window opens called 'Terminal - screen/dev/name of the port'

But it's empty and nothing is happening....I don't know what I have to do next....

[patoberli]

So you have now a serial/console adapter connected to the mac?



Here is a manual, replace the 115200 with 9600. 9600 is the speed of the serial/console port. Cisco defaults this to 9600 on (nearly) all of their devices. Other settings: Data bits 8, Parity None, Stop bits 1, flow control disabled.



https://software.intel.com/en-us/setting-up-serial-terminal-on-system-with-mac-os-x



Not sure if your USB-Serial adapter is also named cu.usbserial-whatever or if it has a different name. I guess that is written in the manual of your adapter.



Here an alternative, graphical program: https://www.decisivetactics.com/products/serial/



Much more info here: https://apple.stackexchange.com/questions/32834/is-there-an-os-x-terminal-program-that-can-access-serial-ports

[tony99982]

---

@patoberli wrote:
So you have now a serial/console adapter connected to the mac?



Here is a manual, replace the 115200 with 9600. 9600 is the speed of the serial/console port. Cisco defaults this to 9600 on (nearly) all of their devices. Other settings: Data bits 8, Parity None, Stop bits 1, flow control disabled.



https://software.intel.com/en-us/setting-up-serial-terminal-on-system-with-mac-os-x



Not sure if your USB-Serial adapter is also named cu.usbserial-whatever or if it has a different name. I guess that is written in the manual of your adapter.



Here an alternative, graphical program: https://www.decisivetactics.com/products/serial/



Much more info here: https://apple.stackexchange.com/questions/32834/is-there-an-os-x-terminal-program-that-can-access-serial-ports

---

Hi, Yes, so what I have done is the following

Installed the serial cable to my iMac.

Connected the usb to the serial cable and to my mac, the serial cable is in the 'console' port of the AP and the ethernet is connected to the PTY to have power.

Then I follow all the commands in terminal, putty, serial, but connection is always refused, serial app keeps 'connecting', SSH in terminal doesn't work, I don't know what to do now....Im not sure if it was you or some else told me to make it autonmous, but I have no clue how to do that.....I can't believe Cisco makes it so comlicated to simply access an AP to change SSID etc.....

[patoberli]

The thing is, you probably don't have such a model. I assume you have a company model that requires a wireless-controller (WLC) to work with. 

In a typical company, with a working WLC, you would simply put that AP into the same VLAN as all the other APs, power it on and it works. Nothing to configure, because the WLC will push the configuration. That's it, it works. All the configuration is done on the WLC, you never ever connect to the individual AP (besides very rare debugging reasons).

That functionality uses the protocol CAPWAP (earlier called LWAPP). In this case the AP has a very small operating system (also named "image") without most administrative functions (as that is done on the WLC). 

The alternative is the same AP, but with the Autonomous image. An Autonomous AP works without a WLC and offers full management functionality. 

Here you find more details (the manual for the 2600 series should be identical to your 3600 model):

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/15_2_4_JB/configuration/guide/scg15-2-4-Book/scg15-2-4-chap4-first.html#44264

Now the thing is, if the AP was ever used together with a WLC and the software was at least once updated (which is nearly guaranteed), it now has only the CAPWAP image. That image requires the use of a working console connection to get access (if no WLC is available). Once that connection works, you can simply download a new Autonomous image via TFTP (or maybe FTP) onto the AP and reload it.

[tony99982]

---

@patoberli wrote:

The thing is, you probably don't have such a model. I assume you have a company model that requires a wireless-controller (WLC) to work with. 

In a typical company, with a working WLC, you would simply put that AP into the same VLAN as all the other APs, power it on and it works. Nothing to configure, because the WLC will push the configuration. That's it, it works. All the configuration is done on the WLC, you never ever connect to the individual AP (besides very rare debugging reasons).

That functionality uses the protocol CAPWAP (earlier called LWAPP). In this case the AP has a very small operating system (also named "image") without most administrative functions (as that is done on the WLC). 

The alternative is the same AP, but with the Autonomous image. An Autonomous AP works without a WLC and offers full management functionality. 

Here you find more details (the manual for the 2600 series should be identical to your 3600 model):

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/15_2_4_JB/configuration/guide/scg15-2-4-Book/scg15-2-4-chap4-first.html#44264

Now the thing is, if the AP was ever used together with a WLC and the software was at least once updated (which is nearly guaranteed), it now has only the CAPWAP image. That image requires the use of a working console connection to get access (if no WLC is available). Once that connection works, you can simply download a new Autonomous image via TFTP (or maybe FTP) onto the AP and reload it.

---

Yes, but the problem is thatneither connection works...I tried SSH, Putty, Serial, in terminal, etc....putty says that acces was refused, terminal opens a screen window, but I only have an icon blinking...no password request shows up...just a blank screen

So I don't know what to do honestly.....what would you recommend?

[patoberli]

Try a different computer, maybe Windows based. Maybe some Apple security feature is blocking you.

In any case, it's absolutely crucial to use the correct number of the serial port. It tends to vary, depending on which USB port you plugged in the serial adapter. Typically (under Windows) the number is somewhere between 1 and 6 (just try all numbers if unsure).

You should at least get a text output of the AP searching its controller, or while its booting a lot of text.

[tony99982]

---

@patoberli wrote:
Try a different computer, maybe Windows based. Maybe some Apple security feature is blocking you.

In any case, it's absolutely crucial to use the correct number of the serial port. It tends to vary, depending on which USB port you plugged in the serial adapter. Typically (under Windows) the number is somewhere between 1 and 6 (just try all numbers if unsure).

You should at least get a text output of the AP searching its controller, or while its booting a lot of text.

---

I get this:

 ls -ltr /dev/*usb*

crw-rw-rw-  1 root  wheel   18,  13 Jun 21 17:09 /dev/cu.usbserial-1460

crw-rw-rw-  1 root  wheel   18,  12 Jun 21 17:11 /dev/tty.usbserial-1460

So I use this: usbserial-1460 as my serial port setting, that's not correct?

[patoberli]

Try both, but only one at a time.

[tony99982]

---

@patoberli wrote:
Try both, but only one at a time.

---

I tried both...I tried with windoes laptop (putty) same thing...a window opens but stays blank....

I don't know anymore now....

[craig.beck]

You can try using the lightweight recovery process using the Autonomous image. You don't need a console connection for this, unless you want to see the output...

1. Connect the AP to a PC/Laptop with an IP of 10.0.0.2 / 255.255.255.224 (You'll need to use a power injector or DC power brick if you connect straight to the AP, or you can do it via a switch on the same VLAN if using PoE from the switch)
2. Start a TFTP server on the PC/Laptop and put the AP Autonomous image in the TFTPROOT folder.
3. Rename the Autonomous image file to ap3g2-k9w7-tar.default
4. Disconnect the power to the AP, hold the MODE button while reconnecting the power.
5. Hold the MODE button on the AP for at least 20s then let go.

You should see the AP downloading the image from the TFTP server.

After 20 mins or so it should have downloaded, installed and rebooted using the new Autonomous image.

[tony99982]

---

@craig.beck wrote:

You can try using the lightweight recovery process using the Autonomous image. You don't need a console connection for this, unless you want to see the output...

1. Connect the AP to a PC/Laptop with an IP of 10.0.0.2 / 255.255.255.224 (You'll need to use a power injector or DC power brick if you connect straight to the AP, or you can do it via a switch on the same VLAN if using PoE from the switch)
2. Start a TFTP server on the PC/Laptop and put the AP Autonomous image in the TFTPROOT folder.
3. Rename the Autonomous image file to ap3g2-k9w7-tar.default
4. Disconnect the power to the AP, hold the MODE button while reconnecting the power.
5. Hold the MODE button on the AP for at least 20s then let go.

You should see the AP downloading the image from the TFTP server.

After 20 mins or so it should have downloaded, installed and rebooted using the new Autonomous image.

---

Hi Craig,

Thanks, but this is a bit too complicated for me

Firsto of all: How do I do this: 

1. Connect the AP to a PC/Laptop with an IP of 10.0.0.2 / 255.255.255.224

Secondly: Start a TFTP server , I don't know what that is and how to start it

Thirdly:  put the AP Autonomous image in the TFTPROOT folder. 

Where do I get this Autonomous image

So I don't think I will be able to do this, I am not an IT sepcialist :-)

[patoberli]

You can do it, but I guess you first have to learn the IT basics and some advanced skills for this, sorry.