cancel
Showing results for 
Search instead for 
Did you mean: 

BT Business Smart Hub 6: "a device reset was performed. Reason SAAF(5)"

praful
Dabbler
Posts: 22
Thanks: 5
Registered: ‎05-12-2019

BT Business Smart Hub 6: "a device reset was performed. Reason SAAF(5)"

I've been using a BT Business Smart Hub 6. The WiFi signal is much improved over the PlusNet One Hub router. I'm also getting slightly faster WiFi and wired speeds (71 vs 74) but the speeds with the One Hub were fine. 

I've seen reports of the router restarting or or losing connection without warning. I've had two issues.

The first occurred five days after installing the router:

dsl:VDSL Link Down: duration was 38957 seconds

I did a line test (17070, option 2) but all was quiet.

Early this morning (three days after the above event), I had a soft reset. Here's an extract of the event log (most recent events first, so start from bottom for chronological order):

08:41:15 03 Jun. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed
08:41:15 03 Jun. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated
08:41:15 03 Jun. ppp1:TR69 receiving InformResponse message
08:41:14 03 Jun. ppp1:TR69 event found : 4 VALUE CHANGE
08:41:13 03 Jun. ppp1:TR69 sending Inform message
08:41:12 03 Jun. ppp1:TR69 event found : 4 VALUE CHANGE
08:41:11 03 Jun. ppp1:TR69 sending Inform message
08:41:11 03 Jun. ppp1:TR69 creating new session with ACS
08:41:05 03 Jun. ppp1:PPP: PPP INFO 212.159.6.10 212.159.6.9
08:41:05 03 Jun. ppp:PPP: IPCP_NAK
08:41:05 03 Jun. ppp:PPP: CHAP_SUCCESS
08:41:05 03 Jun. ppp:PPP: CHAP_RESPONSE
08:41:05 03 Jun. ppp:PPP: LCP_GOOD_ACK
08:41:05 03 Jun. ppp:PPP: LCP_REQUEST
08:41:05 03 Jun. ppp:PPP: CHAP_RESPONSE
08:41:05 03 Jun. ppp:PPP: LCP_GOOD_ACK
08:41:05 03 Jun. ppp:PPP: LCP_REQUEST
08:41:04 03 Jun. :PPPoE error: timeout
08:40:48 03 Jun. :PPPoE error: timeout
08:40:40 03 Jun. :PPPoE error: timeout
08:40:36 03 Jun. :PPPoE error: timeout
08:40:09 03 Jun. :Connection to the Internet has been terminated.(Reboot Reconfiguration forced termination)
07:19:47 03 Jun. ppp1:Request for a new authenticated connection
07:19:47 03 Jun. ppp1:TR69 ConnectionRequest: processing request from ACS
05:38:55 03 Jun. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed
05:38:54 03 Jun. ppp1:TR69 sending GetParameterValuesResponse message
05:38:54 03 Jun. ppp1:TR69 receiving GetParameterValues message
05:38:54 03 Jun. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated
05:38:54 03 Jun. ppp1:TR69 receiving InformResponse message
05:38:52 03 Jun. ppp1:TR69 event found : 6 CONNECTION REQUEST
05:38:52 03 Jun. ppp1:TR69 event found : 4 VALUE CHANGE
05:38:51 03 Jun. ppp1:TR69 sending Inform message
05:38:50 03 Jun. ppp1:TR69 event found : 6 CONNECTION REQUEST
05:38:50 03 Jun. ppp1:TR69 event found : 4 VALUE CHANGE
05:38:49 03 Jun. ppp1:TR69 sending Inform message
05:38:49 03 Jun. ppp1:TR69 creating new session with ACS
05:38:46 03 Jun. ppp1:TR69 ConnectionRequest: processing request from ACS
05:38:46 03 Jun. ppp1:Request for a new authenticated connection
05:38:46 03 Jun. ppp1:TR69 ConnectionRequest: processing request from ACS
05:35:23 03 Jun. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed
05:35:22 03 Jun. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated
05:35:22 03 Jun. ppp1:TR69 receiving InformResponse message
05:35:22 03 Jun. ppp1:TR69 event found : 4 VALUE CHANGE
05:35:21 03 Jun. ppp1:TR69 sending Inform message
05:35:20 03 Jun. ppp1:TR69 event found : 4 VALUE CHANGE
05:35:19 03 Jun. ppp1:TR69 sending Inform message
05:35:18 03 Jun. ppp1:TR69 creating new session with ACS
00:01:55 01 Jan. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed
00:01:54 01 Jan. ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated
00:01:54 01 Jan. ppp1:TR69 receiving InformResponse message
00:01:53 01 Jan. ppp1:TR69 event found : 4 VALUE CHANGE
00:01:53 01 Jan. ppp1:TR69 event found : 1 BOOT
00:01:52 01 Jan. ppp1:TR69 sending Inform message
00:01:51 01 Jan. ppp1:TR69 event found : 4 VALUE CHANGE
00:01:51 01 Jan. ppp1:TR69 event found : 1 BOOT
00:01:49 01 Jan. ppp1:TR69 sending Inform message
00:01:49 01 Jan. ppp1:TR69 creating new session with ACS
00:01:42 01 Jan. ppp1:PPP: PPP INFO 212.159.6.10 212.159.6.9
00:01:41 01 Jan. ppp:PPP: IPCP_NAK
00:01:41 01 Jan. ppp:PPP: CHAP_SUCCESS
00:01:41 01 Jan. ppp:PPP: CHAP_RESPONSE
00:01:41 01 Jan. ppp:PPP: LCP_GOOD_ACK
00:01:41 01 Jan. ppp:PPP: LCP_REQUEST
00:01:41 01 Jan. ppp:PPP: CHAP_RESPONSE
00:01:41 01 Jan. ppp:PPP: LCP_GOOD_ACK
00:01:41 01 Jan. ppp:PPP: LCP_REQUEST
00:01:41 01 Jan. :PPPoE error: timeout
00:01:33 01 Jan. :PPPoE error: timeout
00:01:28 01 Jan. :PPPoE error: timeout
00:00:38 01 Jan. :The Modem has successfully powered up
00:00:38 01 Jan. :WDG Laststatus:: # Current boot was caused by Soft Reset (SAAF)
00:00:30 01 Jan. :The Modem underwent a warm reset
05:32:41 03 Jun. :Connection to the Internet has been terminated.(Reboot Reconfiguration forced termination)
05:32:39 03 Jun. :A device reset was performed. Reason SAAF(5)
03:30:21 03 Jun. ppp1:Request for a new authenticated connection
03:30:21 03 Jun. ppp1:TR69 ConnectionRequest: processing request from ACS

If this sort of thing happens outside of normal hours, I can live with it but it seems unpredictable.

Can someone please shed some light on this? What is the solution?

Thanks

Praful

 

3 REPLIES 3
Baldrick1
Seasoned Hero
Posts: 6,524
Thanks: 2,941
Fixes: 191
Registered: ‎30-06-2016

Re: BT Business Smart Hub 6: "a device reset was performed. Reason SAAF(5)"

@praful 

I suspect that these are two unrelated issues.

The first I imagine is a line drop, which occured nearly 11 days after the last drop. This sort of thing happens from time to time, 10 days without a drop on broadband is pretty good, several times a day is bad.

The second as shown in your event log looks like the warm reset all Smarthub 6s go through every two weeks. This is normal.

I strongly suspect that they occured three days apart is pure coincidence.

Baldrick1
Seasoned Hero
Posts: 6,524
Thanks: 2,941
Fixes: 191
Registered: ‎30-06-2016

Re: BT Business Smart Hub 6: "a device reset was performed. Reason SAAF(5)"

@praful 

 My apologies, I have got hours and days mixed up.

This first drop is the one that you should keep an eye on, I assume that you had two drops about 11 hours apart (or is it just one drop 10 hours after you installed it? If so it could have been a firmware update.. As I suggested before I doubt this is anything to do with the warm reset or indeed the hub. 
If you start getting regular disconnects I suggest that you raise a new topic on the fibre/ADSL board as appropriate, asking for a Plusnet staffer to generate a radius chart. This will show us the number of line drops that you are getting.

praful
Dabbler
Posts: 22
Thanks: 5
Registered: ‎05-12-2019

Re: BT Business Smart Hub 6: "a device reset was performed. Reason SAAF(5)"

@Baldrick1 thank you for replying. I had read about the fortnightly BTBHub6 reset and thought nine days was too soon after installation. But maybe it's on a different schedule.


 My apologies, I have got hours and days mixed up.

I was just replying to your previous message, asking how you deduced the "nearly 11 days" Smiley

The most recent VDSL drop, which is not in the above log extract, occurred at reset:

05:32:42 03 Jun. dsl:VDSL Link Down: duration was 376555 seconds

So that's a reasonably healthy 4 days.


If you start getting regular disconnects I suggest that you raise a new topic on the fibre/ADSL board as appropriate, asking for a Plusnet staffer to generate a radius chart. This will show us the number of line drops that you are getting.

Thanks - will do.

Praful