This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SFOS 16.05.6 MR-6 Broken STAS?

Hi All,

 

We have an XG 230 that I upgraded the firmware on. Since then users are getting the authentication pop up from the XG where others are fine.

Rebooting their PC fixes some so it might lead to a fresh login event fixing it. The Firewall shows them logging in but then logging out and then I get a Authentication fail.

Seems STAS is working for many but randomly fails others since the Firmware update.

I run two DCs with STAS enabled (Latest version of STAS) and I can see live users active yet others not. The inactivity time outs are set high so they would need to walk away for a few hours to be timed out.

EDIT: I disabled the Inactivity time out but still have the issue.

  

The logs just show NTML Client failed to Authenticate

Anyone else having this issue?

 

 

Edit: I can see a few others having the same since the update so I will roll back my Firmware for now until a fix is released.



This thread was automatically locked due to age.
Parents
  • Development Team found an issue that was introduced with MR6. The fix will be merged as soon as possible. Tests are still going on.

    Sorry about that. Please be patient.

    Update: NC-21538 is used to track this issue

  • dna said:
    The fix will be merged as soon as possible

     

    Awesome - I am still on MR-5 since 6 broke the STAS

     

    Will the fix be merged to MR-6 or MR-7 or a separate hotfix?

     

    Do you know what the actual issue was as some reported issues whilst others were fine - was is a config thing?

Reply
  • dna said:
    The fix will be merged as soon as possible

     

    Awesome - I am still on MR-5 since 6 broke the STAS

     

    Will the fix be merged to MR-6 or MR-7 or a separate hotfix?

     

    Do you know what the actual issue was as some reported issues whilst others were fine - was is a config thing?

Children
  • The fix won't go into MR-7 but is planned for the next possible release which is either v17 beta and/or another maintenance release.

    Chances are higher to trigger the problem in setups where allot of users login simultaneously. This explains why everything is fine for some customers.

    Furthermore there is a chance to provoke the problem by misconfiguration (e.g. by having 2 STAS collectors which are both feeded from the same STAS agent and configuring both STAS collector in different collector groups on SFOS. Thus every login event will be reported twice, almost at the same time).