cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
554
Views
5
Helpful
5
Replies

PPPoA Reconnect Issue for SRP527

pmoore
Level 1
Level 1

Hi Guys,

One more issue, current GA release of has an issue for the 527 for PPPoA connections, we encountered this with a planned network outage on our BRAS, this caused all of our DSL connections to be disconnected, once the BRAS was back online most customer modems auto reconnected, what we saw was the 527's did not come back online, some testing then showed if there is a break in the  PPPoA connection or no response the unit does not retry and needs to be repowered or manually forced to be reconnected.

We reproduced this by manually disabling an account and then reenabling it, what we saw in the radius side was the rejection and the unit, we then enabled the account at radius however the unit does not even retry until manual intervention.

Attached is the screen shot of the radius interaction, note the time at the top , 13:48 the account was reenabled at about 13:44 4 minutes later and no access attempts.

1 Accepted Solution

Accepted Solutions

Hi Phil,

Not sure if you got an answer on this one via other channels, but for the benefit of anyone else who happens across this thread, this problem should be resolved in the current beta image - 1.01.18(001).

Cheers,

Dave.

View solution in original post

5 Replies 5

Andrew Hickman
Cisco Employee
Cisco Employee

Thanks for the feedback Phil,

We have engineering looking at this now, so hopefully we'll have some feedback for you shortly.

Cheers

Andy

Hi Andy,

Any updates on how this is progessing , not being able to re-establish PPPoA after any loss of connectivity is not good for a SMB router.

Regards

Phil

Hi Andy,

Chasing up on this here as well, really need to get an answer on whats happening with a fix for this.

Regards

Phil

Hi Phil,

Not sure if you got an answer on this one via other channels, but for the benefit of anyone else who happens across this thread, this problem should be resolved in the current beta image - 1.01.18(001).

Cheers,

Dave.

Since this build this issue seems to be resolved, thanks Gents