Reply
Member
Posts: 1
Registered: ‎04-02-2018
0

Re: OpenRG will go down for reboot in 5 seconds

I am a new member and have the following issue that I am hoping someone can help with.

 

I have BT Business Infinity Unlimited (Fibre to Cabinet)

 

I started getting drop outs about a month a go.

 

Had 3 visits from Open Reach. New Pair to the cabinet. New Port at exchange, 1 new BH 5.

 

Here is the Helpd desk page

 

1. Product name: BT Business Hub
2. Serial number: +076399+NQ70705276
3. Firmware version: Software version 4.7.5.1.83.8.256 (Type A) Last updated 04/02/18
4. Board version: BT Hub 5A
5. Broadband connection: Connected
6. Mobile connection: Not connected
7. Connection uptime : 0 days, 00:06:14
8. Data rate: 18169 / 57363
9. Maximum data rate: 22534 / 70464
10. Noise margin: 7.7 / 8.7
11. Line attenuation: 22.7 / 18.3
12. Signal attenuation: 22.3 / 18.3
13. Data sent/received: 2.1 MB / 16.3 MB
14. Broadband username: M036242@hg7.btclick.com
15. Public Wi-fi: Yes
16. Static IP: 81.150.33.72 / 29
17. 2.4 GHz Wireless network/SSID: Tomahawk
18. 2.4 GHz Wireless connections: Enabled (802.11 b/g/n (up to 144 Mb/s))
19. 2.4 GHz Wireless security: WPA2
20. 2.4 GHz Wireless channel: Automatic (Smart Wireless)
21. 5 GHz Wireless network/SSID: Tomahawk
22. 5 GHz Wireless connections: Enabled (802.11 a/n/ac (up to 1300 Mb/s))
23. 5 GHz Wireless security: WPA2
24. 5 GHz Wireless channel: Automatic (Smart Wireless)
25. Firewall: Default
26. MAC Address: a4:08:f5:ac:08:38
27. Modulation: G.993.2 Annex B
28. Software variant: AA
29. Boot loader: 1.0.0

I am getting dropouts every 15 mins

 

 

Here is the system event log

 

20:45:38, 04 Feb. ( 841.810000) The system is going DOWN for reboot.
20:45:38, 04 Feb. ( 841.810000) OpenRG is going for reboot by IPC command
20:45:33, 04 Feb. ( 836.800000) OpenRG will go down for reboot in 5 seconds
20:32:26, 04 Feb. STP Alert: Port eth0 leaving blocking state.
20:31:02, 04 Feb. ( 852.700000) The system is going DOWN for reboot.
20:31:02, 04 Feb. ( 852.700000) OpenRG is going for reboot by IPC command
20:30:57, 04 Feb. ( 847.700000) OpenRG will go down for reboot in 5 seconds
20:16:15, 04 Feb. ( 885.660000) The system is going DOWN for reboot.
20:16:15, 04 Feb. ( 885.660000) OpenRG is going for reboot by IPC command
20:16:10, 04 Feb. ( 880.660000) OpenRG will go down for reboot in 5 seconds
20:00:57, 04 Feb. ( 853.970000) The system is going DOWN for reboot.
20:00:57, 04 Feb. ( 853.970000) OpenRG is going for reboot by IPC command
20:00:52, 04 Feb. ( 848.970000) OpenRG will go down for reboot in 5 seconds
19:46:05, 04 Feb. ( 854.920000) The system is going DOWN for reboot.
19:46:05, 04 Feb. ( 854.920000) OpenRG is going for reboot by IPC command
19:46:00, 04 Feb. ( 849.920000) OpenRG will go down for reboot in 5 seconds
19:31:16, 04 Feb. ( 1053.420000) The system is going DOWN for reboot.
19:31:16, 04 Feb. ( 1053.420000) OpenRG is going for reboot by IPC command
19:31:11, 04 Feb. ( 1048.420000) OpenRG will go down for reboot in 5 seconds
19:13:08, 04 Feb. ( 975.010000) The system is going DOWN for reboot.
19:13:08, 04 Feb. ( 975.010000) OpenRG is going for reboot by IPC command
19:13:03, 04 Feb. ( 970.010000) OpenRG will go down for reboot in 5 seconds
18:56:19, 04 Feb. ( 962.520000) The system is going DOWN for reboot.
18:56:19, 04 Feb. ( 962.520000) OpenRG is going for reboot by IPC command
18:56:14, 04 Feb. ( 957.520000) OpenRG will go down for reboot in 5 seconds

 

Can anyone point me in the right direction as it is now affecting my business.

 

A lot of googling points at firmware ?

 

PLEASE HELP

Grand Guru
Posts: 1,122
Registered: ‎15-03-2011
0

Re: OpenRG will go down for reboot in 5 seconds

Hi there tomahawk

 

The hub team have provided me with an explanation about the OpenRG entries on the event log.  OpenRG is the base firmware the Hub is built on.  When you see this message on the Hub event log it is merely recording the event in time where your connection has dropped.  Much like the LCP PPP message, OpenRG is not causing your connection to drop, but rather the message is the result of your connection dropping.

 

The gist of it is that this entry simply means that the hub is dropping connection,  the drop causes this message to appear on the event log,  not the other way round.

 

Have you been in contact with the helpdesk to get the line checked?

 

 

Markp

/* /