We have the following hardware:
Our ISP parameters are :
We have not been able to get the 4G connection working and would therefor be very grateful for any inputs as to what the appropriate USB parameters would be for the above combination.
Thank you in advance.
Thanks for the response kdisc98.
I have now tried the settings you recommended, but could not get the 4G connection up.
I also tried with Dial Strings: ATD*99# and ATDT*99# since our ISP's Access Number is *99#
Any more ideas on what I could try or troubleshoot?
Many thanks in advance!
You may try setting additional modem parameters to:
Device Type: huawei-cdc
Device Identifier: 0x12d11506
Also, remove PIN from your SIM-card; if you have it working without PIN, you may try to put CPIN=<PIN> in your dialer string:
I have seen issues with the E3272s where PIN was not supported.
Thanks for your response hrobers,
I have tried the suggested settings, with and without the PIN, but have not succeeded in getting up the connection.
I would be grateful for further setting suggestions to try out.
I wonder if there is any way of debugging to try and find out what is going wrong during the connection sequence?
Please work with your partner, open a TAC case, or work with your local Aruba SE to get help on this.
Few things if you want to find out youself:
Convert the RAP to a controller RAP before checking the USB 4G connection. Converting the RAP over USB 4G requires configuration on Instant first, and then also on your controller.
The boot process of your AP should show the dongle present, the modeswitch (if applicable), and the USB modem detected as a modem. To get access to the RAP-155 console, you will need a special console cable:
If you have another AP, like AP-225, AP-115, RAP-109, there is a RJ45 serial console port on the AP, as well there is an USB port for the dongle.
Fully un-powering the AP after configuration has been needed for me few times to get the dongle working. That has to do with the mode switching, and rebooting was not enough in those cases, unplug and replug the AP after a config change.
This E3276 requires AOS 6.4 or Instant 4.1 as a minimum. Please also doublecheck your versions.
Again, work with your partner, TAC, Aruba SE (in that order) to get you going.
To configure Huawei E3276 you only need to do this. You should not need to configure dialstrings etc.
Thanks for your response.
Sorry for the delay in replying, just back from vacation.
I have tried the configurations you sent, but to no avail.
We have TDC as our carrier, but I do not think this ought to be the problem.
I have however noted that there are many flavours of Huawei E3276 modems, and on checking closer, the recommended type of modem for this purpose is the Huawei E3276-150 modem.
I wonder if this is the specific E3276 modem you are using, (before I order it and make a last effort).
I have noticed that with some of the ISPs we need to add the APN information as well i.e. I have tested with Tele2 and DGC and got them up and running if i added this line and change to correct APN adress in it.
I have used the Huawei E3276-150 for this so it should work.
Thanks for your response!
Vi have placed an order for the Huwaie E3276-150 4G modem, and once we receive it, will give it another try, as per your suggestion.
I will post back on here whatever the outcome.
Best regards Peter
We received the Huwaei E3276-150 4G modem last week, and began testing with the RAP-155 yesterday, and started with base settings.
The base settings worked at once, connecting sucesfully to our carriers 4G connection - TDC .
Following are the settings that worked for us with TDC's 4G carrier net:
conf tprovision-apread-bootinfo ap-name Testusb-type huawei-cdcusb-dev 0x12d11506cellular_nw_peference autolink-priority-cellular 8link-priority-ethernet 1reprovision ap-name Test
So I wish to thank you all for your time rendered.
We have however noticed a new problem now that the 4G uplink is working, and that is when the RAP-155 has the 4G uplink active, then clients cannot connect to the WLAN in about 4 out of 5 attempts. In many cases the client computer freezes and the only way out is to switch the computer off. But when the RAP-155 uplink goes via the Ethernet port (via ADSL instead of 4G connection) then there are no issues whatsoever.
Has anyone experienced the cleint connectivity issue? Or any clue on where to start troubleshoting?
Thanks in advance.
I haven¨t seen this issue before, can you please chech the auth-trace for the client on the controller and see whats happening there, if you can see anyting out of the normal.
show auth-tracebuf mac <client mac>
Another thing to check is the latancy, sometimes radius issues can be seen if their is to much latancy.
How is the SSID configured? tunnel mode, bridge mode or splitt-tunnel?
The three 3 SSIDs are all in Tunnel mode.
The Guest WLAN (with unprotected SSID) does not have this problem however, as do the other two WPA2 Enterprise SSIDs .
Latency should not be a problem, and is certainly higher via the ADSL uplink (which works well) , than through the 4G link.
I will troubleshoot as per your suggestion, later when I get home, where I have the RAP-155.
I would like to correct my previous alleging lower latency via TDC's 4G uplink on the RAP-155 USB port. There is certainly higher latency via the 4G uplink than when the RAP-155 is connected via an ADSL (Ethernet Port 0) uplink.
When Pinging a target via 4G the response is around 80ms verses approximately 40ms via ADSL for the same target.
So probably latency could be the cause, as you suspected?
In that case how would one circumvent the problem?
NB: The throughput (and bandwidth) via the 4G uplink is higher that through the ADSL uplink.
Can you mail me your contact information.. My email is firstname.lastname@example.org
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.