Controllerless Networks

Reply
Valued Contributor II

Re: Add IAP to existing VC

Hi friend,

 

Let me get some clarity on this.

 

do you have IAP 105 as a master already ? or trying to bring up both IAPs ?

 

If you have Master already, please enable Auto join in the master.

 

please share the output of the following, run these commands on IAP 103

 

1. show election

2. debug-master-beacon

 

we can fix this issue once we go through the above out puts

Cheers,
Venu Puduchery,
[Is my post helped you ? Give Kudos :) ]
Occasional Contributor II

Re: Add IAP to existing VC

Hello,

 

Thanks for your help.

 

The IAP 105 is set as Master and it is configured as Enabled in "System -> Auto join mode".

I just reset the IAP 103 device.

 

Access to the "instant" SSID, change the Country Code (same as the IAP 105).

 

I see the IP address that it takes from DHCP (same range as the IAP 105).

 

Connect again to the IAP 105 (master) SSID and access to the IAP 103 from console:

 

# show election
State        : Master

master_beacon   : sent=492 rcvd=0
hierarchy_beacon: sent=0 rcvd=0
hierarchy_ack   : sent=0 rcvd=0
beacon_req      : sent=0 rcvd=0
beacon_resp     : sent=0 rcvd=0

election wait   : 0
timer slow      : 0
master high cpu : 0
ap cpu usage    : 0
Slave->Pot-Master : 0 time
Pot-master->Master: 0 time
Pot-master->Slave : 0 time

last spoof arp rcvd: 0
last spoof mac: 00:00:00:00:00:00
last beacon received ticks: 0
uplink flap count         : 0
max beacon miss ticks     : 0

hierarchy mode            : 0
last hierarchy beacon received ticks: 0
provisioned master denied : 0

 

# debug-master-beacon
(nothin in the output)

 The IAP 103 can ping to IAP 105:

 

# ping 192.168.2.232
Press 'q' to abort.
PING 192.168.2.232 (192.168.2.232): 56 data bytes
64 bytes from 192.168.2.232: icmp_seq=0 ttl=64 time=2.0 ms
64 bytes from 192.168.2.232: icmp_seq=1 ttl=64 time=0.5 ms
64 bytes from 192.168.2.232: icmp_seq=2 ttl=64 time=0.5 ms
64 bytes from 192.168.2.232: icmp_seq=3 ttl=64 time=0.5 ms
64 bytes from 192.168.2.232: icmp_seq=4 ttl=64 time=0.5 ms

--- 192.168.2.232 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.5/0.8/2.0 ms

 And to the VC:

 

# ping 192.168.2.239
Press 'q' to abort.
PING 192.168.2.239 (192.168.2.239): 56 data bytes
64 bytes from 192.168.2.239: icmp_seq=0 ttl=64 time=2.1 ms
64 bytes from 192.168.2.239: icmp_seq=1 ttl=64 time=0.5 ms
64 bytes from 192.168.2.239: icmp_seq=2 ttl=64 time=0.5 ms
64 bytes from 192.168.2.239: icmp_seq=3 ttl=64 time=0.5 ms
64 bytes from 192.168.2.239: icmp_seq=4 ttl=64 time=0.5 ms

--- 192.168.2.239 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.5/0.8/2.1 ms

 

Need I configure something else?

 

Thanks and best regards.

Valued Contributor II

Re: Add IAP to existing VC

Hi,

 

The output clearly saying that. IAP 103 is not receiving Master beacons hence it is assuming itself as the Master. we have figure out why it is not able to receive the Master beacon from IAP 105.

 

Master beacon traffic is L2 traffic hence we have to find the reason why L2 traffic is not getting exchanged.

 

Console IAP 105 (MAster) and run the same commands and see if you get some hint.

 

If not, please open a case with TAC.

 

 

Cheers,
Venu Puduchery,
[Is my post helped you ? Give Kudos :) ]
Occasional Contributor II

Re: Add IAP to existing VC

Thanks again,

 

This is the commands in the IAP 105:

 

# show election
State        : Master

master_beacon   : sent=0 rcvd=542220
hierarchy_beacon: sent=0 rcvd=0
hierarchy_ack   : sent=0 rcvd=0
beacon_req      : sent=0 rcvd=0
beacon_resp     : sent=0 rcvd=0

election wait   : 0
timer slow      : 0
master high cpu : 0
ap cpu usage    : 9
Slave->Pot-Master : 0 time
Pot-master->Master: 0 time
Pot-master->Slave : 0 time

last spoof arp rcvd: 0
last spoof mac: 00:00:00:00:00:00
last beacon received ticks: 0
uplink flap count         : 0
max beacon miss ticks     : 0

hierarchy mode            : 0
last hierarchy beacon received ticks: 0
provisioned master denied : 0

 

# debug-master-beacon
(nothin in the output)

Need I force the IAP 103 to be slave device?

 

Thansk for you help.

 

Regards.

Trusted Contributor I

Re: Add IAP to existing VC

in principle you should have to.

 

if you can i would save the config, reset both devices to factory default and start from there.

 

if you can't then again go over the basics, firmware version, l2 connectivity, auto add members, no fixed master, ...

Occasional Contributor II

Re: Add IAP to existing VC

Thanks!

 

I did it and it works.

 

I reset the IAP105 device, configure the IAP 103 as master, and when I connect the reseted 105 it join automatically.

 

Thanks for your help.

 

Regards.

Aruba Employee

Re: Add IAP to existing VC

What is the version running on the 105?

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: