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 27922 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.
  • 0

    Hi,

    Please send me the case#.

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0 in reply to sachingurung

    Hello,


    the case is: Support Case 5955351

    best regards

    michael

  • 0 in reply to ex-cạthedra

    Hi Michael,

    I went through the logs you posted, there is a known bug on this issue. Issue may persist as a result of large number of connected client over AP. But this is not tested yet.

    I am curious to know what happens when we restart "awed" services. For this, take SSH to UTM with root login and run the command: /var/mdw/scripts/awed restart.

    Awaiting update.

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0 in reply to sachingurung

    Hello Sachin,


    this was the first time we installed an AP at that location.

    >I am curious to know what happens when we restart "awed" services. For this, take SSH to UTM with root login and run the command: /var/mdw/scripts/awed restart.

    here the logs after that:

    2016:05:24-10:09:48 astaro-cx awed[14264]: [MASTER] SIGTERM received, sending SIGTERM to siblings, exiting
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] awed_ng starting
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP10: 9400-6f160bc
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP100: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP100C: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP100X: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP15: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP15C: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP30: 9400-6f160bc
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP5: 1
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP50: 9400-6f160bc
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP55: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for AP55C: 9400-f9147ed
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] new firmware detected for RED15w: 1
    2016:05:24-10:09:52 astaro-cx awed[14692]: [MASTER] access point firmware available: AP15C:9400-f9147ed AP10:9400-6f160bc AP55C:9400-f9147ed RED15w:1 AP5:1 AP30:9400-6f160bc AP100C:9400-f9147ed AP100X:9400-f9147ed AP50:9400-6f160bc AP55:9400-f9147ed AP15:9400-f9147ed AP100:9400-f9147ed
    2016:05:24-10:09:58 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35419
    2016:05:24-10:09:58 astaro-cx awed[14692]: [MASTER] we have a *.pid file and no corresponding temporary PID.
    2016:05:24-10:09:58 astaro-cx awed[14714]: [A40031D269797B2] AP15 from 192.168.131.107:35419 identified as A40031D269797B2
    2016:05:24-10:09:58 astaro-cx awed[14714]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:09:58 astaro-cx awed[14714]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:09:59 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35420
    2016:05:24-10:09:59 astaro-cx awed[14716]: [A40031D269797B2] AP15 from 192.168.131.107:35420 identified as A40031D269797B2
    2016:05:24-10:09:59 astaro-cx awed[14716]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:09:59 astaro-cx awed[14716]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:03 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35421
    2016:05:24-10:10:03 astaro-cx awed[14739]: [A40031D269797B2] AP15 from 192.168.131.107:35421 identified as A40031D269797B2
    2016:05:24-10:10:04 astaro-cx awed[14739]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:04 astaro-cx awed[14739]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:17 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35422
    2016:05:24-10:10:17 astaro-cx awed[14757]: [A40031D269797B2] AP15 from 192.168.131.107:35422 identified as A40031D269797B2
    2016:05:24-10:10:17 astaro-cx awed[14757]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:17 astaro-cx awed[14757]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:19 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35423
    2016:05:24-10:10:19 astaro-cx awed[14776]: [A40031D269797B2] AP15 from 192.168.131.107:35423 identified as A40031D269797B2
    2016:05:24-10:10:20 astaro-cx awed[14776]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:20 astaro-cx awed[14776]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:20 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35424
    2016:05:24-10:10:20 astaro-cx awed[14782]: [A40031D269797B2] AP15 from 192.168.131.107:35424 identified as A40031D269797B2
    2016:05:24-10:10:20 astaro-cx awed[14782]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:20 astaro-cx awed[14782]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:23 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35425
    2016:05:24-10:10:23 astaro-cx awed[14794]: [A40031D269797B2] AP15 from 192.168.131.107:35425 identified as A40031D269797B2
    2016:05:24-10:10:23 astaro-cx awed[14794]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:23 astaro-cx awed[14794]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:28 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35426
    2016:05:24-10:10:28 astaro-cx awed[14798]: [A40031D269797B2] AP15 from 192.168.131.107:35426 identified as A40031D269797B2
    2016:05:24-10:10:28 astaro-cx awed[14798]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:28 astaro-cx awed[14798]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:10:33 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:35427
    2016:05:24-10:10:33 astaro-cx awed[14816]: [A40031D269797B2] AP15 from 192.168.131.107:35427 identified as A40031D269797B2
    2016:05:24-10:10:33 astaro-cx awed[14816]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:10:33 astaro-cx awed[14816]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:05 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40101
    2016:05:24-10:11:05 astaro-cx awed[14849]: [A40031D269797B2] AP15 from 192.168.131.107:40101 identified as A40031D269797B2
    2016:05:24-10:11:05 astaro-cx awed[14849]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:06 astaro-cx awed[14849]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:10 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40102
    2016:05:24-10:11:10 astaro-cx awed[14853]: [A40031D269797B2] AP15 from 192.168.131.107:40102 identified as A40031D269797B2
    2016:05:24-10:11:11 astaro-cx awed[14853]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:11 astaro-cx awed[14853]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:15 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40103
    2016:05:24-10:11:16 astaro-cx awed[14858]: [A40031D269797B2] AP15 from 192.168.131.107:40103 identified as A40031D269797B2
    2016:05:24-10:11:16 astaro-cx awed[14858]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:16 astaro-cx awed[14858]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:20 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40104
    2016:05:24-10:11:21 astaro-cx awed[14861]: [A40031D269797B2] AP15 from 192.168.131.107:40104 identified as A40031D269797B2
    2016:05:24-10:11:21 astaro-cx awed[14861]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:21 astaro-cx awed[14861]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:26 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40105
    2016:05:24-10:11:26 astaro-cx awed[14866]: [A40031D269797B2] AP15 from 192.168.131.107:40105 identified as A40031D269797B2
    2016:05:24-10:11:26 astaro-cx awed[14866]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:26 astaro-cx awed[14866]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:31 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40106
    2016:05:24-10:11:32 astaro-cx awed[14871]: 1
    2016:05:24-10:11:36 astaro-cx awed[14692]: [MASTER] new AP with ID A40031D269797B2
    2016:05:24-10:11:38 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40107
    2016:05:24-10:11:40 astaro-cx awed[14692]: [MASTER] AP A40031D269797B2: Local metadata updated
    2016:05:24-10:11:40 astaro-cx awed[14692]: [MASTER] AP A40031D269797B2: Configuration change detected
    2016:05:24-10:11:52 astaro-cx awed[14692]: [MASTER] AP A40031D269797B2: Local metadata updated
    2016:05:24-10:11:52 astaro-cx awed[14692]: [MASTER] AP A40031D269797B2: Configuration change detected
    2016:05:24-10:11:54 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40108
    2016:05:24-10:11:54 astaro-cx awed[14926]: [A40031D269797B2] AP15 from 192.168.131.107:40108 identified as A40031D269797B2
    2016:05:24-10:11:54 astaro-cx awed[14926]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:54 astaro-cx awed[14926]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.
    2016:05:24-10:11:59 astaro-cx awed[14692]: [MASTER] new connection from 192.168.131.107:40109
    2016:05:24-10:11:59 astaro-cx awed[14938]: [A40031D269797B2] AP15 from 192.168.131.107:40109 identified as A40031D269797B2
    2016:05:24-10:11:59 astaro-cx awed[14938]: [A40031D269797B2] (Re-)loaded identity and/or configuration
    2016:05:24-10:11:59 astaro-cx awed[14938]: [A40031D269797B2] device sends DEV2ASG_INITIALCONTACT twice, dropping.[st]

    Same state after delete and activate the AP after restarting awed.

    best regards

    michael

  • 0 in reply to ex-cạthedra

    At the ssh-console it appears nl80211 not found

  • 0 in reply to ex-cạthedra

    Hi Michael,

    There is a known bug [NUTML-11110] related to this issue. Please contact support so that they can co-ordinate with the dev team for an update.

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0 in reply to sachingurung

    Hello,

    "Please contact support so that they can co-ordinate with the dev team for an update."

    In what way can I contact the dev team and whats with the open ticket?

    best regards

    Michael

  • 0 in reply to ex-cạthedra

    Hi Michael,

    If you have a valid support subscription, please drop a support request at support@sophos.com.

    Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • +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

  • 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