02-23-2012 04:53 PM
We installed one of these devices as our gateway a couple of weeks ago, flashed the firmware to 1.2.4(003) and it worked perfectly until this morning where it keeps resetting the ADSL every minute and losing the web interface to the unit.
The log endlessly reports this:
Feb 24 11:26:00 SRP547W cron.info cron[8779]: (root) CMD (/sbin/check_gn)
Feb 24 11:26:00 SRP547W cron.info cron[8781]: (root) CMD (/sbin/check_ps)
Feb 24 11:26:00 SRP547W daemon.warning system[8787]: Maybe udhcpd died or got problems, we need to re-exec it
Feb 24 11:26:01 SRP547W daemon.warning system[8787]: Maybe cy_gn_srv died or got problems, we need to re-exec it
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: check_interface_usage: brdige(br4088) port state wrong?
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: br4088
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: bridge id 8000.1cdf0fd2453c
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: designated root 8000.1cdf0fd2453c
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: root port 0
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: max age 2
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: hello time 2
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: forward delay 20
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: ageing time 300
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: hello timer 1.76
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: topology change timer 0 gc timer
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: flags
Feb 24 11:26:49 SRP547W daemon.emerg system[982]:
Feb 24 11:26:49 SRP547W daemon.emerg system[982]:
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: eth2 (1)
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: port id 8001
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: designated root 8000.1cdf0fd2453c path cost 100
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: designated bridge 8000.1cdf0fd2453c message age timer 0
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: designated port 8001 forward delay timer
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: designated cost 0 hold timer
Feb 24 11:26:49 SRP547W daemon.emerg system[982]: flags
Feb 24 11:26:49 SRP547W daemon.emerg system[982]:
We don't have the voice stuff enabled,and have 1 SSID enabled.
it reports version ID V02, Hardware 3.1.0 ADSL firmware 0.76.0
It's connection is PPoE (LLC)
DHCP is disabled, its own IP is static as is the ADSL line.
it has 10 port forwarding rules enabled
We're in Melbourne Australia connected to Internode
That's about it .. any help would be appreciated as our internet connection is going up and down every minute!
Joss
05-06-2013 04:21 AM
I am waiting for a telephone contact by an engineer.
They told me they would call back in an hour, for now I have not heard no ring.
Even in my case I think the warranty expires, but it is unthinkable that a product of this type do not offer solutions for its customers once past this period.
I will keep you informed.
Bye bye
05-15-2013 08:03 AM
Hi,
Have you gotten a response? Judging by the amount of comments in this post this issue looks like a manufacturers defect. I have the same issue and thought it was our IP phone system. After swapping out the original then working directly with Cisco engineers on the second one they were not able to come up with a solution even after supplying them with log files and having them see the issue for themselves.
I was hoping for a firmware release by now that would remedy this, but no dice.
05-15-2013 09:03 AM
I had telephone contact in the early days very technical, all the tests they require have been carried out but the problem stay.
At the moment the ticket is passed to the technicians of the second level.
:)(
07-04-2013 03:31 AM
Just in case no solution had been found till now, I explain my solution to the same identical problem you blaimed.
My SRP547W has two vlans, one of them is the data one, working on something like 192.168.1.0/24 or whatever you configured.
The second vlan is the voice vlan, by default working on 192.168.100.1/24.
Unfortunately, and this was my problem, few ISP use 192.168.100.1 as default gateway for the wan connection.
This creates a strange behavior of the router, that, in a certain sense, is not able to properly route packets when it has to decide which route has to be used.
By simply changing the dhcp rule regarding this vlan to a different subent, like 192.168.99.1/24, put the router in a "properly working" mode.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide