Link to home
Start Free TrialLog in
Avatar of silvercas
silvercas

asked on

Meru Controller Replacing Offline Unit

Hello,

I am working with a meru controller.  One of our access points was damaged by water and is now showing as offline.  To replace an access point is it simply going to the controller entering the old mac and new mac into replacement?

Thanks
Avatar of jburgaard
jburgaard

As far as I remember , yes.
What ver. of director are you on?
Avatar of silvercas

ASKER

software version of the controller is
Software Version                                      : 4.0-131
ASKER CERTIFIED SOLUTION
Avatar of jburgaard
jburgaard

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
will give this a try
I actually tried this, this morning and it said mac address couldnt be changed.  So I just deleted the old ap and connected the new one.  The new one is saying enabled and online but will not accept connections.

Any tips?
I would simply check config of this AP relative to a working AP and change the missing setting acordingly.
question see the connectivity on this one is L2.  the others are set at l2-preffered but getting l3
Wonder if you have an old DHCP reservation, that should be changed.
i thought about that.  looking at the ap's they are dhcp but in DHCP i do not see any leases on them.
in "...enabled and online but will not accept connections..."
does "accept connections" mean no cliets will associate or you cannot manage this AP at all?
In case you prefer L2 & get L2 but no client-connectivity then I would focus on other config settings.
no client can get associated with the ap.  I am able to manage it

just found something interesting.  yes the ap is getting a DHCP address but for some reason not getting dns servers from the dhcp lease.  the other aps are

after getting the renew dhcp with dns still not able to connect

exact message is unable to connect to "<essid>"

im also seeing the below when I do a connect ap 35

ap 35> [02/06 09:55:09.280] *****ERROR***** SEC: Sec802_1xPacketToClient: STA[bc:52:b7:XX:25:fa] BSSID[12:06:XX:6a:25:fa] lookup error
[02/06 09:55:09.980] *****ERROR***** SEC: Sec802_1xPacketToClient: STA[bc:52:b7:XX:25:fa] BSSID[12:06:XX:6a:25:fa] lookup error
[02/06 09:55:11.524] *****ERROR***** SEC: Sec802_1xPacketToClient: STA[bc:52:b7:XX:25:fa] BSSID[12:06:XX:6a:25:fa] lookup error
[02/06 09:55:18.485] *****ERROR***** SEC: Sec802_1xPacketToClient: STA[00:27:10:49:4a:90] BSSID[06:06:XX:49:4a:90] lookup error
[02/06 09:55:22.803] *****ERROR***** SEC: Sec802_1xPacketToClient: STA[bc:52:b7:XX:25:fa] BSSID[12:06:XX:6a:25:fa] lookup error
[02/06 09:55:25.088] *****ERROR***** SEC: Sec802_1xPacketToClient: STA[bc:52:b7:XX:25:fa] BSSID[12:06:XX:6a:25:fa] lookup error