Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 3850 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

AP's inactive after 17.5.1MR3 and AP 11.0.006 f/w updates

Martin Meerman

Today I updated by XG125 to 17.5.1 MR3 plus updated the AP firmware to 11.0.006 for the XG. Now my AP55's have turned all in to inactive. When I added a new AP to have at least something, it was available at first, but then also became inactive.

As the AP cannot directly be accessed to verify its status, does anyone have a suggestion on how to find a solution (or cause)?



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

    I had a similar problem that I hadn't attributed to this update (does applying this [or any] update return DHCP options and bindings to defaults?), and in the process of troubleshooting, discovered that my XG wasn't providing DHCP option 234 (AP_Config) information any more.
    Because the default XG configuration denies traffic in protected nets to 1.2.3.4, the AP configuration process may fail and leave the AP inactive (or it may take a very long to to become active).

    If your XG is also your DHCP server, open a console and type:
    console> system dhcp dhcp-options binding show dhcpname DHCP_Scope_Name

    ..you should see something like this:
    Options Configured from GUI
    ---------------------------
    Domain_Name                                                 f.q.d.n
    Subnetmask                                                  255.255.255.0
    Default_Gateway                                             10.10.1.1
    Domain_Name_Servers                                         10.10.1.1
    NTP_Servers(42)                                             35.171.237.77,64.113.44.54,192.150.
    149.245,208.75.89.4

    Options Configured from CLI
    ---------------------------

    If you want to add the AP config parameter, you have to:
    1. define it in the admin console
    console> system dhcp dhcp-options add optioncode 234 optionname AP_Config optiontype ipaddress
    ..you should see: DHCP option successfully added.


    2. bind it to the DHCP scope
    console> system dhcp dhcp-options binding add dhcpname DHCP_Scope_Name optionname AP_Config(234) value ip.add.re.ss
    (where ip.add.re.ss is the XG DHCP server listener IP)
    ..you should see: DHCP option AP_Config(234) added for DHCP Server DHCP_Scope_Name.

    3. verify your changes
    console> system dhcp dhcp-options binding show dhcpname DHCP_Scope_Name
    ..you should see something like this:
    Options Configured from GUI
    ---------------------------
    Domain_Name                                                 f.q.d.n
    Subnetmask                                                  255.255.255.0
    Default_Gateway                                             10.10.1.1
    Domain_Name_Servers                                         10.10.1.1
    NTP_Servers(42)                                             35.171.237.77,64.113.44.54,192.150.
    149.245,208.75.89.4

    Options Configured from CLI
    ---------------------------
    AP_Config(234)                                              10.10.1.1

    You may have to restart your DHCP service in order for it to use the changes (I've had varying results).

    HTH,

    Jim

Reply
  • +1

    I had a similar problem that I hadn't attributed to this update (does applying this [or any] update return DHCP options and bindings to defaults?), and in the process of troubleshooting, discovered that my XG wasn't providing DHCP option 234 (AP_Config) information any more.
    Because the default XG configuration denies traffic in protected nets to 1.2.3.4, the AP configuration process may fail and leave the AP inactive (or it may take a very long to to become active).

    If your XG is also your DHCP server, open a console and type:
    console> system dhcp dhcp-options binding show dhcpname DHCP_Scope_Name

    ..you should see something like this:
    Options Configured from GUI
    ---------------------------
    Domain_Name                                                 f.q.d.n
    Subnetmask                                                  255.255.255.0
    Default_Gateway                                             10.10.1.1
    Domain_Name_Servers                                         10.10.1.1
    NTP_Servers(42)                                             35.171.237.77,64.113.44.54,192.150.
    149.245,208.75.89.4

    Options Configured from CLI
    ---------------------------

    If you want to add the AP config parameter, you have to:
    1. define it in the admin console
    console> system dhcp dhcp-options add optioncode 234 optionname AP_Config optiontype ipaddress
    ..you should see: DHCP option successfully added.


    2. bind it to the DHCP scope
    console> system dhcp dhcp-options binding add dhcpname DHCP_Scope_Name optionname AP_Config(234) value ip.add.re.ss
    (where ip.add.re.ss is the XG DHCP server listener IP)
    ..you should see: DHCP option AP_Config(234) added for DHCP Server DHCP_Scope_Name.

    3. verify your changes
    console> system dhcp dhcp-options binding show dhcpname DHCP_Scope_Name
    ..you should see something like this:
    Options Configured from GUI
    ---------------------------
    Domain_Name                                                 f.q.d.n
    Subnetmask                                                  255.255.255.0
    Default_Gateway                                             10.10.1.1
    Domain_Name_Servers                                         10.10.1.1
    NTP_Servers(42)                                             35.171.237.77,64.113.44.54,192.150.
    149.245,208.75.89.4

    Options Configured from CLI
    ---------------------------
    AP_Config(234)                                              10.10.1.1

    You may have to restart your DHCP service in order for it to use the changes (I've had varying results).

    HTH,

    Jim

Children
No Data