SM registration with AP issue ..

Hi,

We are using ePMP1000 with 90' sector 15dbi antenna at AP and 7'BW 23dbi disc antenna at SM,

1.Running firmware version 2.4.2

2.AP-SM air distance is 500-700 mtrs.

3.Channel BW 20/10MHZ with countyr code=India and tried with diffrent available frequency. 4.SM Target RSSi=-45db,AP TX 21/10db.

Issue:

1.at SM Home page its showing RSSI=-51/-65db and SNR too but still in scanning mode and not able to register with desired AP.

2.AP side showing NO SM registered.

3.Have tried with link alignment,load default and reconfigure but didn't work.

Any Advice.

Rgds,

Naimish Shah‚Äč INDIA\\\

Hi, 

What are the syslogs telling you?

Also, on the SM, when it sees the AP and does not register, is there a reason that is being displayed in the Available APs table under Monitor->Wireless?

Thanks,

Sriram

I am having a similar issue.  It is almost as if the AP is locked in P2P mode even though it is set for TDD.  It has one client registered but won't take any more.  If I (locally) access an SM and go to "Monitor" "Wireless" it shows the AP but under "Meets Network Entry Criteria" it says "No (Capacity is ZERO)".   I am currently updating the FW from 2.4.1 to 2.4.3 and will keep you updated.


@Brad Hagstrom wrote:

I am having a similar issue.  It is almost as if the AP is locked in P2P mode even though it is set for TDD.  It has one client registered but won't take any more.  If I (locally) access an SM and go to "Monitor" "Wireless" it shows the AP but under "Meets Network Entry Criteria" it says "No (Capacity is ZERO)".   I am currently updating the FW from 2.4.1 to 2.4.3 and will keep you updated.


Can you please post a screenshots of your:

1. APs Configuration->Radio page

2. AP's Monitor->Wireless page

3. SM's Monitor->Wireless page

Thanks,

Sriram

The SM Wireless monitor is from an SM that can see the AP that is having the issue but connected to another AP.  It is showing the same "Meets Network Entry Criteria" Status as any SM that I have tried to connect to this AP (on the bottom row).   It does not appear that the FW update helped.

Hi Brad, 

I see from the SM Monitor->Wireless screenshot that the AP in question is arriving at the SM at an RSSI of -93. On the SM's Configuration->Radio page, there is a parameter called "RSSI Threshold" which is by default set to -80 (or -90 depending on which release you are on). This means that the if the SM sees an AP BELOW that threshold it will not register to that AP. I believe this is the reason your SM is not able to connect to the AP in question. 

Thanks,

Sriram

Hello.  This was just a sample SM to show the "capacity is zero" issue.  I have to go to the remote site in order to get to the actual SM.  The "error" is the same though.  The actual SM in question is seeing the AP in the -50's but still gives the "capacity is zero" error.  I have three AP's at this site, two of which can not connect more than one client at a time.  Any clients connected to the third AP that can "see" the other two all show the same "capacity is zero" problem for the other two AP's, no matter how good the signal is.

I have tried several different SM's to try to get them to connect to either of these two AP's with no luck.  At some point I am probably going to have to factory default the AP's then reconfigure them??

I see. Yes, please try factory defaulting them and configure them again.

If you need live support, please don't hesitate to contact our support engineers at http://www.cambiumnetworks.com/support/contact-support

Attached is a SS from a different "live" SM that can see one of the other AP's tha does not seem to be able to connect more than one SM.  The network entry setting on all SM's is -100.

Thanks,

Brad

Will do unless somebody has an "easier" idea !!  Thank you.

So I updated the AP from 2.4.1 to 2.4.3 and not the secont SM is able to connect.  Same SM, same AP and config.

any updates? we have the same problem

I have the same problem as all the above.  So weird can connect some SM's and some will not driving me nuts.


@Mark_Brown wrote:

I have the same problem as all the above.  So weird can connect some SM's and some will not driving me nuts.


Please don't resurrect really old dead threads. This was for people having issues with a super old firmware.

Please start a new thread and outline the issue and please list the firmware versions you're using on the AP and clients. Thanks!

1 Like

@Mark_Brown wrote:

I have the same problem as all the above.  So weird can connect some SM's and some will not driving me nuts.


Hi Mark,
I've noticed that you've made a few posts in the last week or so which say "I'm having problems" and "I'm frustrated", but without a really good description of the problems you're having, the symptoms you're seeing, the versions of hardware and software you're using, and the things you've tried to remedy them. :)  I would encourage you to do exactly what Eric suggested - which is to start your own thread, to describe the problem in as much technical details as you can (technical details, not emotional impact) and with any log files, firmware versions, error reports, or whatever technical info you can provide.

Lots of the community members are really super helpful, and quite knowledgeable too.  Quite often, Eric, Chris, NewKirk, brubble, and dozens of others are often willing to help - if there is a question, a problem, the symptoms, and some good details to start with. :)

4 Likes

@Mark_Brown wrote:

I have the same problem as all the above.  So weird can connect some SM's and some will not driving me nuts.


If you are having the same problem as above from 2015, then you should probably upgrade the firmware to a more recent version. If you are still using 2.4.1 or 2.4.3, that would explain why you are so frustrated.