Controllerless Networks

Hi Guy's

 

Has anybody els had this issue, the IAP picks up a IP address but will not join the cluster. I connected to the console and when the AP boots i get a "Warning: CLI module is running in a degraded state." so i took it out the production network and created a seperate network. the unit get's a IP address however if you enter the default admin credentials it comes back saying they are incorrect.

Did you try resetting it on the new network and upgrading it to the code of the existing cluster?

 

Hi cjoseph,

 

I bought the AP-135 for home purpose, and I don't have controller and confiured cluster. When I connect it trough serial console, I saw device was empty and I flash it with software Release_6.4.4.4-4.2.3.2 through tftp. But after reboot CLI is running in degraded mode and Web UI does not allow login. May I do manual provisioning with flashing some default image on second partition, or something else.

Are you putting the IAP-135 on a subnet with dhcp?

Can the IAP get out to the internet so it can contact a time server? (type "show clock" to see if the date is correct).

Yes, and device get address. And has following ports:

PORT     STATE SERVICE
22/tcp   open  ssh
80/tcp   open  http
443/tcp  open  https
4343/tcp open  unicall
8080/tcp open  http-proxy

 

Trought ssh I can login with admin/admin but shows messgae:

Warning: CLI module is running in a degraded state.  Configuration, write memory, and support command are disabled; please debug with caution.

show tech-support and show tech-support supplemental are the two most useful outputs to collect for any kind of troubleshooting session.

 

On web I'm not be able to login with admin/admin nor admin/forgetme!

And on web page I saw following status:

Internet: Unreachable

Active uplink: N/A

Celullar Provider: No module installed

Celullar Signal: No module installed

Primary VPN: Not configured

Secondary VPN: Not configured

AirWave: Not configured

 

I also have serial port to this device. And I can download any file trough tftp.

 

Thanks a lot in advance,

~Dinko

Can you ping an internet address from the CLI?

you should only use admin/admin  "forgetme" no longer works for instant.

Hi,

 

Yes, I can do ping in both direction. From and to the IAP.

 

6c:f3:7f:c3:07:0e# ping 172.16.0.1
Press 'q' to abort.
PING 172.16.0.1 (172.16.0.1): 56 data bytes
64 bytes from 172.16.0.1: icmp_seq=0 ttl=64 time=1.9 ms
64 bytes from 172.16.0.1: icmp_seq=1 ttl=64 time=0.8 ms
64 bytes from 172.16.0.1: icmp_seq=2 ttl=64 time=0.7 ms
64 bytes from 172.16.0.1: icmp_seq=3 ttl=64 time=0.6 ms

--- 172.16.0.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.6/1.0/1.9 ms

 

The result of CLI command of "show tech-support" is attached to this post.

 

Sorry for my delay, thanks a lot in advance,

~Dinko

Hi cjoseph,

 

Do you need more information?

What I need to do to switch off this degraded mode?

I honestly cannot tell from that log.  Let me get someone else to look at it.

 

It seems like you are trying to join the IAP-135 to an existing cluster?

Please define what means "existing cluster". The IAP is connected in my private network based on local Asus router WL-500gP V2 with started DHCP, nothing more.

CLI in a degraded state typically means there is an existing cluster on the network and the new AP Cannot join the cluster.  Can you boot the access point up and PM me the tech support?

I did not understand the last one, please give me more instructions what I need to do.

Is there a sticker on the AP that says IAP-135 or AP-135?

 

Yes, has such sticket. Please see the attachment file.

Has also:

barcode: 171648

SN: AX0129512

MAC: 6CF37FC3070E

That access point is an AP, which requires a hardware controller and NOT an IAP-135 which can operate by itself.  It will let you attempt Aruba Instant firmware but it should not work, unfortunately.

Upsss, Now I understand what stupid mistake I did. I have no idea that AP and IAP are different things. I thought that it was just a configuration. Sorry it's totaly my mistake.

 

Please accept my apologies,

~Dinko

Hi cjoseph,

 

Four months ago, here I discussed here in this forum a problem with my AP-135. The problem was entirely my because I had only AP-135 instead of IAP-135. Now I have both, I haven't problems with the new IAP-135 and configured it very quickly. Not completely but the main one is done. Thank you very much for the useful information, this is my little but my main pass.

So, now I'm trying to connect my old AP-135 to the new IAP-135. This message for "CLI module is running in a degraded state" dissapear. But unfortunately:
  - I do not see it on the IAP-135 website.
  - I can not enter my page because admin / admin is not working. My admin accounts too.

 

Current Facts:

 - My IAP-135 is already configured with the "iap-master" command in its CLI.

 - The AP-135 is attached both directly to the local network and as chain via ETH1 port of the IAP-135's.

 - MAC address of both devices is configured in my DHCP server and they take their IP-ta desired by me. (172.16.0.20 анд 172.16.0.21)

 - I did factory reset.

 - Both devices IAP-135 and AP-135 has same version of firmware:

     ArubaOS Version 6.4.4.4-4.2.3.2 (build 54910 / label #54910)

 

None of the above hasn't helped.

 

Something I miss and do not know what, can you help me?

Log of my serial console is attached to this post.

 

Thanks a lot in advance.

~Dinko

 

You cannot load IAP firmware on an AP-135, otherwise you will get a "turn of mobility" message and it will not work, period.  The AP-135 will never be able to form a cluster with an IAP-135

From where I can get firmware for AP-135?

 

I'm looking here: http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/EntryId/21998/Default.aspx

 

And here I see only this casiopea if suitable for this device.

---

@dmironov wrote:

From where I can get firmware for AP-135?

 

I'm looking here: http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/EntryId/21998/Default.aspx

 

And here I see only this casiopea if suitable for this device.

---

The AP-135 is not capable of running the Instant firmware; only the IAP-135 is.

 

For an AP-135, it gets it's firmware downloaded from the hardware Mobility Controller to manages it. It is unable to join an Instant Virtual Controller.

if you already have an access point running on a lower code, it will try to get in sync with existing APs and will give you a similar error. 

The solution would be to configure the access point to receive an IP address from DHCP ( other than your wireless subnet) and access it via GUI. Match the code on the new same as the existing one and now you can bring the new ap into up to join the existing cluster.
Original Message:
Sent: Nov 05, 2015 01:04 AM
From: Hayden Anderson
Subject: Warning: CLI module is running in a degraded state.

Hi Guy's

 

Has anybody els had this issue, the IAP picks up a IP address but will not join the cluster. I connected to the console and when the AP boots i get a "Warning: CLI module is running in a degraded state." so i took it out the production network and created a seperate network. the unit get's a IP address however if you enter the default admin credentials it comes back saying they are incorrect.