Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 18 replies
  • Subscribers 29 subscribers
  • Views 6524 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

APX 320 and Home XG

Wilk4013

Does the APX320 work with XG Home? I purchased the APX and it cannot connect to my XG Home. It gets a dhcp address but does not show up as a pending AP.



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    which version of XG are you running? APXs support was added at least two MRs ago.

    Ian

  • 0 in reply to rfcat_vk

    Ian,

    I am running version 17.5.5 MR-5.

  • 0 in reply to Wilk4013

    Maybe your APX is somehow "old".
    So the firmware on your APX does not know, there "can be" a XG.

    Please start a Central Trial (without any charge), connect your APX to Central, let him update and remove him from Central. It should connect now with XG. 

    https://central.sophos.com/manage/login

  • 0 in reply to LuCar Toni

    Hello,

    I have a Sophos Central account and added a trial Wireless license. When running the wizard it does not see the serial number of the APX. I see DNS traffic going thru my XG successfully to my internal DNS server and then I see traffic from the APX going to address 52.5.76.173 on destination port 2713. But I never see the apx in Sophos Central. Thank you for your reply but this did not seem to work for me.

  • 0 in reply to Wilk4013

    This should help you.

    https://community.sophos.com/kb/en-us/133505

    You have to add the Serialnumber of APX in Central and "wait" until the APX reboot. 

  • 0 in reply to LuCar Toni

    Thank you for your reply. I have attempted the suggested method but it does not work for me. I get a solid red led after about a 10 minute wait and I know my internet connectivity is up because I am making this post :) Just tried again same result.

  • 0 in reply to Wilk4013

    Can you please create a Rule, LAN with APX Ip to WAN allow any Services? 

    Just in case, Xg is blocking something. NTP for example. 

  • 0 in reply to LuCar Toni

    Thank you. I have the APX on a separate interface from the LAN network. I cut my ruleset down to one rule allowing my wifi and lan zone and wifi and lan subnets to the WAN zone to any network with any service all allowed. Still unable to see AP using Sophos Central wizard. Again thank you very much for your input and suggestions. Still trying to make it work. And back to my original question are we sure that XG Home is supported?

  • 0 in reply to Wilk4013

    Hi,

    I know of one home user that has an APX on his network.

    Ian

  • 0 in reply to rfcat_vk

    Yes, me

     

    I Have a XG135 and APX320 at home

     

     

    Works fine

  • 0 in reply to LuCar Toni

    LuCar Toni,

    Just looked at the awed.log and I don't see any indication that the XG sees the APX 320. This is what I see:

    2019-05-08 08:50:46 1 (eval)
    2019-05-08 08:50:46 2 JSON::Parse::valid_json
    2019-05-08 08:50:46 3 CSC::API::exec_opcode
    2019-05-08 08:50:46 4 main::get_firmware_versions
    2019-05-08 08:50:46 [MASTER] AP firmware info updated successfully in DB.
    2019-05-08 08:50:46 [MASTER] start processing configuration change
    2019-05-08 08:50:59 [MASTER] end processing configuration change
    2019-05-08 10:47:24 [MASTER] SIGTERM received, sending SIGTERM to siblings, exiting
    2019-05-08 10:49:25 [MASTER] awed_ng starting
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP10: 9500-wifi-971af07-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP100: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP100C: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP100X: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP15: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP15C: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP30: 9500-wifi-971af07-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP50: 9500-wifi-971af07-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP55: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP55C: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX320: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX530: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX740: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX120: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for RED15w: 1
    2019-05-08 10:49:25 [MASTER] access point firmware available: APX120:11.0.007-1 AP15C:9500-wifi-11838aaf-c2ec208 AP10:9500-wifi-971af07-c2ec208 AP55C:9500-wifi-11838aaf-c2ec208 RED15w:1 APX320:11.0.007-1 APX740:11.0.007-1 APX530:11.0.007-1 AP30:9500-wifi-971af07-c2ec208 AP100C:9500-wifi-11838aaf-c2ec208 AP100X:9500-wifi-11838aaf-c2ec208 AP50:9500-wifi-971af07-c2ec208 AP55:9500-wifi-11838aaf-c2ec208 AP15:9500-wifi-11838aaf-c2ec208 AP100:9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:26 DIE --------------------------------------------------------
    2019-05-08 10:49:26 JSON error at line 1, byte 1/44: Unexpected character 'A' parsing initial state: expecting whitespace: '\n', '\r', '\t', ' ' or start of string: '"' or digit: '0-9' or minus: '-' or start of an array or object: '{', '[' or start of literal: 't', 'f', 'n' at /</bin/awed>JSON/Parse.pm line 69.
    2019-05-08 10:49:26 1 (eval)
    2019-05-08 10:49:26 2 JSON::Parse::valid_json
    2019-05-08 10:49:26 3 CSC::API::exec_opcode
    2019-05-08 10:49:26 4 main::get_firmware_versions
    2019-05-08 10:49:26 [MASTER] AP firmware info updated successfully in DB.
    2019-05-08 10:49:26 [MASTER] start processing configuration change
    2019-05-08 10:49:39 [MASTER] end processing configuration change
    2019-05-08 15:22:10 [MASTER] start processing configuration change
    2019-05-08 15:22:15 [MASTER] end processing configuration change
    2019-05-08 15:23:13 [MASTER] start processing configuration change
    2019-05-08 15:23:18 [MASTER] end processing configuration change
    2019-05-08 17:49:42 [MASTER] start processing configuration change
    2019-05-08 17:49:46 [MASTER] end processing configuration change
    2019-05-08 18:02:55 [MASTER] start processing configuration change
    2019-05-08 18:03:00 [MASTER] end processing configuration change
    2019-05-08 20:36:38 [MASTER] start processing configuration change
    2019-05-08 20:36:43 [MASTER] end processing configuration change
    2019-05-08 21:17:34 [MASTER] start processing configuration change
    2019-05-08 21:17:39 [MASTER] end processing configuration change
    2019-05-08 21:18:22 [MASTER] start processing configuration change
    2019-05-08 21:18:27 [MASTER] end processing configuration change
    2019-05-08 21:35:49 [MASTER] start processing configuration change
    2019-05-08 21:35:55 [MASTER] end processing configuration change
    2019-05-19 07:49:39 [MASTER] start processing configuration change
    2019-05-19 07:49:44 [MASTER] end processing configuration change

    I also ran awetool and I am unable to connect to the APX. Still working on this and thanks for the help. I am trying to replace an AIMeshed pair of Asus routers because I want to manage my network from 1 console but looks like I may have to return the APX 320 if I can get it working this week.

Reply
  • 0 in reply to LuCar Toni

    LuCar Toni,

    Just looked at the awed.log and I don't see any indication that the XG sees the APX 320. This is what I see:

    2019-05-08 08:50:46 1 (eval)
    2019-05-08 08:50:46 2 JSON::Parse::valid_json
    2019-05-08 08:50:46 3 CSC::API::exec_opcode
    2019-05-08 08:50:46 4 main::get_firmware_versions
    2019-05-08 08:50:46 [MASTER] AP firmware info updated successfully in DB.
    2019-05-08 08:50:46 [MASTER] start processing configuration change
    2019-05-08 08:50:59 [MASTER] end processing configuration change
    2019-05-08 10:47:24 [MASTER] SIGTERM received, sending SIGTERM to siblings, exiting
    2019-05-08 10:49:25 [MASTER] awed_ng starting
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP10: 9500-wifi-971af07-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP100: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP100C: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP100X: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP15: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP15C: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP30: 9500-wifi-971af07-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP50: 9500-wifi-971af07-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP55: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for AP55C: 9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX320: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX530: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX740: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for APX120: 11.0.007-1
    2019-05-08 10:49:25 [MASTER] new firmware detected for RED15w: 1
    2019-05-08 10:49:25 [MASTER] access point firmware available: APX120:11.0.007-1 AP15C:9500-wifi-11838aaf-c2ec208 AP10:9500-wifi-971af07-c2ec208 AP55C:9500-wifi-11838aaf-c2ec208 RED15w:1 APX320:11.0.007-1 APX740:11.0.007-1 APX530:11.0.007-1 AP30:9500-wifi-971af07-c2ec208 AP100C:9500-wifi-11838aaf-c2ec208 AP100X:9500-wifi-11838aaf-c2ec208 AP50:9500-wifi-971af07-c2ec208 AP55:9500-wifi-11838aaf-c2ec208 AP15:9500-wifi-11838aaf-c2ec208 AP100:9500-wifi-11838aaf-c2ec208
    2019-05-08 10:49:26 DIE --------------------------------------------------------
    2019-05-08 10:49:26 JSON error at line 1, byte 1/44: Unexpected character 'A' parsing initial state: expecting whitespace: '\n', '\r', '\t', ' ' or start of string: '"' or digit: '0-9' or minus: '-' or start of an array or object: '{', '[' or start of literal: 't', 'f', 'n' at /</bin/awed>JSON/Parse.pm line 69.
    2019-05-08 10:49:26 1 (eval)
    2019-05-08 10:49:26 2 JSON::Parse::valid_json
    2019-05-08 10:49:26 3 CSC::API::exec_opcode
    2019-05-08 10:49:26 4 main::get_firmware_versions
    2019-05-08 10:49:26 [MASTER] AP firmware info updated successfully in DB.
    2019-05-08 10:49:26 [MASTER] start processing configuration change
    2019-05-08 10:49:39 [MASTER] end processing configuration change
    2019-05-08 15:22:10 [MASTER] start processing configuration change
    2019-05-08 15:22:15 [MASTER] end processing configuration change
    2019-05-08 15:23:13 [MASTER] start processing configuration change
    2019-05-08 15:23:18 [MASTER] end processing configuration change
    2019-05-08 17:49:42 [MASTER] start processing configuration change
    2019-05-08 17:49:46 [MASTER] end processing configuration change
    2019-05-08 18:02:55 [MASTER] start processing configuration change
    2019-05-08 18:03:00 [MASTER] end processing configuration change
    2019-05-08 20:36:38 [MASTER] start processing configuration change
    2019-05-08 20:36:43 [MASTER] end processing configuration change
    2019-05-08 21:17:34 [MASTER] start processing configuration change
    2019-05-08 21:17:39 [MASTER] end processing configuration change
    2019-05-08 21:18:22 [MASTER] start processing configuration change
    2019-05-08 21:18:27 [MASTER] end processing configuration change
    2019-05-08 21:35:49 [MASTER] start processing configuration change
    2019-05-08 21:35:55 [MASTER] end processing configuration change
    2019-05-19 07:49:39 [MASTER] start processing configuration change
    2019-05-19 07:49:44 [MASTER] end processing configuration change

    I also ran awetool and I am unable to connect to the APX. Still working on this and thanks for the help. I am trying to replace an AIMeshed pair of Asus routers because I want to manage my network from 1 console but looks like I may have to return the APX 320 if I can get it working this week.

Children
No Data