×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

SRP547W dropping ADSL every minute

Unanswered Question
Feb 23rd, 2012
User Badges:

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
JossEllis Thu, 02/23/2012 - 20:01
User Badges:

On further investigation, it seems more like the LAN ports are getting reset rather than the ADSL. My ISP reports no issues on the line and losing the web interface also suggests that's what's happening.


Maybe this error has something to do with it?

check_interface_usage: brdige(br4088) port state wrong?

egotechsupport Wed, 03/21/2012 - 02:20
User Badges:

I have the SRP541W and get exactly the same errors in the log.

I can go for days with rock solid connection to my ISP (microwave link) then suddenly no internet and have to reboot to get it back. THe internal router traffic is fine just the WAN dies.

My ISP can detect no problems.

We need help.

Any CISCO technical staff reading this????


--


Mar 21 19:56:51 SRP541W daemon.emerg system[1073]: check_interface_usage: brdige(br4088) port state wrong?

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:           br4088

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            bridge id                    8000.1cdf0fd26c1e

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            designated root          8000.1cdf0fd26c1e

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            root port                       0                              path cost                       0

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            max age                       2.00                              bridge max age                      20.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            hello time                       2.00                              bridge hello time            20.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            forward delay                      20.00                              bridge forward delay             2.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            ageing time                     300.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            hello timer                       0.94                              tcn timer                       0.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            topology change timer             0.00                              gc timer                       2.94

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            flags

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:           eth2 (1)

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            port id                    8001                              state                           disabled

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            designated root          8000.1cdf0fd26c1e          path cost                     100

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            designated bridge          8000.1cdf0fd26c1e          message age timer             0.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            designated port          8001                              forward delay timer             0.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            designated cost             0                              hold timer                       0.00

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:            flags

Mar 21 19:56:51 SRP541W daemon.emerg system[1073]:

chidcp999 Mon, 11/12/2012 - 04:31
User Badges:

Did you ever get this resolved? I've just started getting the same problem on an SRP547W, that was rock solid until yesterday. Now getting the same problem every minute, with br4088 being reset.


Thanks

Clive

egotechsupport Mon, 11/12/2012 - 05:15
User Badges:

I bought a new identical unit, upgraded the firmware to the then latest, imported the settings from the original one, and made the primary DNS the secondary, and vice versa, ie swapped them.

Not sure if it was a DNS issue or the hardware (now have a spare), but it may have been the firmware upgrade too.

ENZO BASTIANELLO Mon, 02/04/2013 - 13:35
User Badges:

I have the same problem with SRP527W with firmware 1.01.27(007). This problem happens randomly after few hours.

It blocks inbound connection. I believe that it's a switching STP (Spanning Tree Protocol) problem . I'll check further..

osekavage Wed, 03/06/2013 - 09:44
User Badges:

Sorry, no solution here but I can verify that this is happening on my SRP541W once a day with firmware 1.2.5.

Web traffice still works but VPN tunnels go down and we cannot ping URLs.

Cisco tech thought it was related to communication to DNS servers.  Changed them to Google and OpenDNS addresses and still experienced the same issues.


The kicker is that I cannot access the routers web interface during this time to check the logs.  Once I restart it, the logs are cleared.

GLAXUS_IT Tue, 05/14/2013 - 07:16
User Badges:

Having the same problem with a CISCO SRP547W.

I've been trying to troubleshoot this situation for 3 days.  Any answer? Any lucky solving this?

We had a Draytek Vigor 2820 before cisco (never had a problem), replaced it with the CISCO SRP and the problem you described ocurrs.



"Sorry, no solution here but I can verify that this is happening on my SRP541W once a day with firmware 1.2.5.

Web traffice still works but VPN tunnels go down and we cannot ping URLs.

Cisco tech thought it was related to communication to DNS servers.  Changed them to Google and OpenDNS addresses and still experienced the same issues."



Model:SRP547W, ADSL2+ AnnexA, 802.11n ETSI, 4FXS/1FXO
Version ID:V02
Hardware Version:3.1.0
Boot Version:1.1.19 (Aug 24 2010 - 20:50:42)
Firmware Version:1.2.5 (001) Nov 8 2012
ADSL Firmware Version:1.01.6
Recovery Firmware:1.2.5 (000)
WAN MAC Address:1C:DF:0F:D3:07:34
Current Time:Tue, 14 May 2013 15:10:44
Wireless:1 SSID Enabled
leeclout82 Mon, 04/15/2013 - 07:13
User Badges:

Hi All,


I'm getting similar errors too, shame there was no solution here, running latest firmware


Model:SRP541W, GE WAN, 802.11n ETSI, 4FXS/1FXO
Version ID:V01
Hardware Version:3.0.0
Boot Version:1.1.19 (Aug 24 2010 - 20:50:42)
Firmware Version:1.2.5 (001) Nov 8 2012
Recovery Firmware:1.2.5 (000)


Current Time:Tue, 16 Apr 2013 00:12:07
Wireless:1 SSID Enabled




<24>Apr 15 23:47:03 SRP541W system[935]:           eth2 (1)

10.1.254.1          15/04 23:43:51.897

<24>Apr 15 23:47:03 SRP541W system[935]:            port id                    8001                              state                           disabled

10.1.254.1          15/04 23:43:51.898

<24>Apr 15 23:47:03 SRP541W system[935]:            designated root          8000.1cdf0fd2ebd2          path cost                     100

10.1.254.1          15/04 23:43:51.899

<24>Apr 15 23:47:03 SRP541W system[935]:            designated bridge          8000.1cdf0fd2ebd2          message age timer             0.00

10.1.254.1          15/04 23:43:51.899

<24>Apr 15 23:47:03 SRP541W system[935]:            designated port          8001                              forward delay timer             0.00

10.1.254.1          15/04 23:43:51.900

<24>Apr 15 23:47:03 SRP541W system[935]:            designated cost             0                              hold timer                       0.00

10.1.254.1          15/04 23:43:51.900

<24>Apr 15 23:47:03 SRP541W system[935]:            flags

10.1.254.1          15/04 23:43:51.901

<24>Apr 15 23:47:03 SRP541W system[935]:

10.1.254.1          15/04 23:43:51.901

<24>Apr 15 23:48:04 SRP541W system[935]: check_interface_usage: brdige(br4088) port state wrong?

10.1.254.1          15/04 23:44:53.041

<24>Apr 15 23:48:04 SRP541W system[935]:           br4088

10.1.254.1          15/04 23:44:53.049

<24>Apr 15 23:48:04 SRP541W system[935]:            bridge id                    8000.1cdf0fd2ebd2

10.1.254.1          15/04 23:44:53.049

<24>Apr 15 23:48:04 SRP541W system[935]:            designated root          8000.1cdf0fd2ebd2

10.1.254.1          15/04 23:44:53.050

<24>Apr 15 23:48:04 SRP541W system[935]:            root port                       0                              path cost                       0

10.1.254.1          15/04 23:44:53.051

<24>Apr 15 23:48:04 SRP541W system[935]:            max age                       2.00                              bridge max age                      20.00

10.1.254.1          15/04 23:44:53.052

<24>Apr 15 23:48:04 SRP541W system[935]:            hello time                       2.00                              bridge hello time            20.00

10.1.254.1          15/04 23:44:53.052

<24>Apr 15 23:48:04 SRP541W system[935]:            forward delay                      20.00                              bridge forward delay             2.00

10.1.254.1          15/04 23:44:53.053

<24>Apr 15 23:48:04 SRP541W system[935]:            ageing time                     300.00

10.1.254.1          15/04 23:44:53.063

<24>Apr 15 23:48:04 SRP541W system[935]:            hello timer                       1.41                              tcn timer                       0.00

10.1.254.1          15/04 23:44:53.064

<24>Apr 15 23:48:04 SRP541W system[935]:            topology change timer             0.00                              gc timer                       1.41

10.1.254.1          15/04 23:44:53.065

<24>Apr 15 23:48:04 SRP541W system[935]:            flags

10.1.254.1          15/04 23:44:53.065

<24>Apr 15 23:48:04 SRP541W system[935]:

10.1.254.1          15/04 23:44:53.066

<24>Apr 15 23:48:04 SRP541W system[935]:

10.1.254.1          15/04 23:44:53.067


Message was edited by: Lee Clout

leeclout82 Mon, 04/15/2013 - 08:21
User Badges:

After looking at it some more, seems spanning tree is active on the WAN2 port (which has no connection in my case).  Disabling STP doesn't affect the messages, I assume because this setting is aimed at LAN1 thru 4 not the WAN interfaces.


Also tried making my switch the root bridge, but the error message keep coming through with the bridge id of the WAN2 interface. Switch is connected to LAN port so no big surprise there.


I'm getting the error message every 61 seconds.


Love to hear any ideas on this one! It's got me stuffed

Andrew Hickman Tue, 04/16/2013 - 03:01
User Badges:
  • Cisco Employee,

Hi All,


If you see this issue again and you are using an SRP520W-U or SRP540W running 1.2.x code, can you please grab a debug file as soon as possible after the interruption.


To grab the file, log in to the SRP, then Adminstration > Remote Support > Collect Device Status Information.


Please then open a support case and provide this file to the support engineer.  Hopefully we can use this to diagnose a root cause.


Regards,


Andy

leeclout82 Tue, 04/16/2013 - 05:47
User Badges:

Thanks Andy,


I'm quite new to the cisco world, so appeciate your guidance.  Do I understand correctly that I would require a support contract to be able to open a support case? Is there more of a community support route that I might be able to utilise?


Hardware is the SRP541W (not the 520W-U/540W you mentioned), but this discussion was only one of two that I found referencing the br4088 interface, except my issue isn't ADSL related.  I've been through all the FW release notes etc, spent some considerable time testing if various features affect the problem and concluded there is no GUI option to resolve the issue (like shutdown the unused port at the most basic level).


I mainly noticed the issue when I added a syslog server to my network and found that I was getting the posted error so often.  I guess my issue is more that I cannot do effective monitoring when the logs are filled with junk. The WAN2 isn't utilized in this network anyway.


I have the debug_info.tgz but not too sure about opening a support case.


Appreciate your help,


Lee

adelano Tue, 04/16/2013 - 10:19
User Badges:

Hi Lee,


The SRP series devices are covered under warranty so they do not require a support contract. Please use the link below to locate the Small Business Support number in your region.


http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html


Please contact the Small Business Support Center and open a Service Request so we can address this issue.


Kind regards,


Alex Delano

Support Engineer

Cisco Systems Inc.

leeclout82 Mon, 05/06/2013 - 03:50
User Badges:

Hi Luca,  hope you have more luck opening a service request, I purchased my unit 2nd Hand and seeing it was originally purchased through a local ISP I can't get support.  Cisco and Telstra (AUS) have a contract saying Telstra would support the products they sell but.... Telstra aren't technically savvy :-(


Please post any progress you make, good luck

Luca Pieroni Mon, 05/06/2013 - 04:21
User Badges:

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

osekavage Wed, 05/15/2013 - 08:03
User Badges:

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.

Luca Pieroni Wed, 05/15/2013 - 09:03
User Badges:

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.



:)(

vaccari01 Thu, 07/04/2013 - 03:31
User Badges:

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.