Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 10 replies
  • Answers 3 answers
  • Subscribers 4 subscribers
  • Views 27918 views
  • Users 0 members are here
Options
Suggested
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

AP15 - device sends DEV2ASG_INITIALCONTACT twice, dropping

ex-cạthedra

Good Morning,

I opened a case in Sophos Ltd myutm - but there seams no reaction. We have "premium" support with a UTM 110.

An Ap15 is allways inactive.

The logs:

2016:05:18-08:14:45 astaro-cx awed_10245_: _MASTER_ new connection from 192.168.131.107:33593
2016:05:18-08:14:45 astaro-cx awed_17728_: _A40031D269797B2_ AP15 from 192.168.131.107:33593 identified as A40031D269797B2
2016:05:18-08:14:45 astaro-cx awed_17728_: _A40031D269797B2_ _Re-_loaded identity and/or configuration
2016:05:18-08:14:45 astaro-cx awed_17728_: _A40031D269797B2_ device sends DEV2ASG_INITIALCONTACT twice, dropping.
2016:05:18-08:14:50 astaro-cx awed_10245_: _MASTER_ new connection from 192.168.131.107:33594
2016:05:18-08:14:50 astaro-cx awed_17743_: _A40031D269797B2_ AP15 from 192.168.131.107:33594 identified as A40031D269797B2
2016:05:18-08:14:50 astaro-cx awed_17743_: _A40031D269797B2_ _Re-_loaded identity and/or configuration
2016:05:18-08:14:50 astaro-cx awed_17743_: _A40031D269797B2_ device sends DEV2ASG_INITIALCONTACT twice, dropping.
2016:05:18-08:14:55 astaro-cx awed_10245_: _MASTER_ new connection from 192.168.131.107:33595
2016:05:18-08:14:55 astaro-cx awed_17756_: _A40031D269797B2_ AP15 from 192.168.131.107:33595 identified as A40031D269797B2
2016:05:18-08:14:55 astaro-cx awed_17756_: _A40031D269797B2_ _Re-_loaded identity and/or configuration
2016:05:18-08:14:55 astaro-cx awed_17756_: _A40031D269797B2_ device sends DEV2ASG_INITIALCONTACT twice, dropping.

One AP15 was replaced - but the now box shows the same error. With the first AP15 a Sophos Technican klicked a while in the web Interface - but the error still persists.

We use the latest 9.4 but there error was at latest 9.3 too.

Any ideas?

best regards



This thread was automatically locked due to age.
Parents
  • +1

    I had a similar issue...

    My fix:

    Delete the "inactive" AP inside Webadmin

    Rejoin the AP without any connected networks and change the object name of the AP. After rejoin the AP was normally visible and active -> Edit AP and select wireless networks for this AP

    This works in my case.

    regards

Reply
  • +1

    I had a similar issue...

    My fix:

    Delete the "inactive" AP inside Webadmin

    Rejoin the AP without any connected networks and change the object name of the AP. After rejoin the AP was normally visible and active -> Edit AP and select wireless networks for this AP

    This works in my case.

    regards

Children
  • 0 in reply to SWeissflog

    Hi Everyone,

    This did work for me.  When accepting the device, I put no networks and renamed the AP to test.  The logs immediately showed new firmware sent to device and then it went online.  I deleted the device and repeated the accept process, this time not changing device's name and adding 2 SSIDs via a group.  It also worked.  Repeated the process again, this time selecting only one SSID, manually and it also worked.  I am using UTM 9.410

Unfiltered HTML