SRP 527W - problems connecting Sierra 312U USB modem to Telstra

[halcomsystems]

The router recognizes the Sierra 312U modem but does not connect to Telstra.  The modem is on a monthly plan (not pre-paid) and I have tried APN settings such as internet.telstra and internet.bigpond. The configuration is set to manual and the correct user id and password have been entered.

Can someone explain the "daemon.err rc: start -1 port.... fail (-8)" in the log?

312U sierra model  supposed to be compatible with SRP500s. Any other settings I should try?

Cheers

Paul

Jul 13 17:59:09 SRP527W daemon.notice rc: 3G WAN is unplug

Jul 13 17:59:09 SRP527W daemon.notice rc: killall -TERM igmprt

Jul 13 17:59:10 SRP527W daemon.notice rc: igmprt -f -i br4080 -w 0 -c 5

Jul 13 17:59:12 SRP527W daemon.info 3G[354]: init 3G card phase get card info

Jul 13 17:59:13 SRP527W daemon.info 3G[354]: init 3G card phase verify pincode

Jul 13 17:59:13 SRP527W daemon.info 3G[354]: init 3G card phase check card lock

Jul 13 17:59:13 SRP527W daemon.info 3G[354]: init 3G card phase set service

Jul 13 17:59:15 SRP527W daemon.info 3G[354]: init 3G card phase get signal

Jul 13 17:59:16 SRP527W daemon.info 3G[354]: init 3G card phase get reg network

Jul 13 17:59:17 SRP527W daemon.info 3G[354]: init 3G card phase get cimi

Jul 13 17:59:18 SRP527W daemon.info 3G[354]: init 3G card phase set apn

Jul 13 17:59:18 SRP527W daemon.notice 3G[354]: USB 3G card SIERRA_U306 initialized

Jul 13 17:59:19 SRP527W daemon.err rc: start -1 port.... fail (-8)

Jul 13 17:59:19 SRP527W daemon.notice rc: 3G WAN is ready

[Andrew Hickman]

Hi Paul,

Was the ADSL connection disconnected when you tried this? 

By default, the SRP527 is configured for failover mode - this means that under normal circumstances, the modem will be detected, but not connected.

Are you saying that your modem won't connect when the connection attempts to fail over?

Andy

[halcomsystems]

Hi Andy

Thanks for your quick response. I took the Cisco modem out of service and tested it separately from the rest of the network. When I plugged in the USB modem, it found it immediately and it connected without any problems.

When I first did the test, the SRP527 was already operational and connetced via the ADSL. I just plugged in the USB Modem. At that time the SRP527 did not even detect the USB modem, I am not sure why.

I can only think that the SRP527 needed to be turned off and restarted.

Cheers

Paul

[Andrew Hickman]

Hi Paul,

Thanks for the response.  Could you let me know which firmware version you are using please?

Also when you tested away from the network, did you connect the modem before or after powering up the SRP?

Many thanks

Andy

[halcomsystems]

Hi Andy

I am using firmware  Version SRP520W-1.1.23

.

I have tested both ways and USB modem was detected and connected each time:

1. USB modem plugged in then power on the router

2. Power on router first then when its ready plug in the USB modem.

There was no ADSL connection both of these cases. I will put the router back into service and will try again.

Cheers

Paul

[Andrew Hickman]

Thanks Paul,

Please let me know how it goes.  (Please capture logs as before when you try)

Andy

[halcomsystems]

Hello Andy

I have put the SRP527W back into service and tested the failover. The connection correctly changes to the USB modem each time the ADSL connection drops. I have tested with two different USB modems, both work well: ZTE MF626i and

Sierra 312U.

However, there is now another issue with port forwarding. We have a number of port forwarding configurations for mail, web, RDP etc... Whenever the failover occurs to the USB modem the port forwarding stops functioning. I have tested it from an outside connection using the new IP address allocated to the USB modem.

I have noticed that the Port forwarding configuration allows he selction of WAN Interface but only the ADSL connections can be selected (ie PVC0). Is there anything I missed in the settings?

Cheers

Paul

[Andrew Hickman]

Hi Paul,

BTW - the error message that you saw is not related to the 3G function.  I understand from engineering that the message relates to a legacy condition and can safely be ignored.

Regards,

Andy