[NEBULA] AP name changes when moved between Sites

HealthByRo
HealthByRo Posts: 28  Freshman Member
edited April 14 in Nebula
Why does the custom name of the AP change back to the MAC address when moved between Sites?

We setup new APs (firmware updates, etc.) in a "Staging" site so it doesn't interfere with the production WiFi environment in the room (aka, no SSIDs enabled) and then move it to the actual Site that it is deployed in (so it will have the desired SSIDs of the deployment site). 

However, ever AP that we've moved, the name of the AP gets reset to the MAC address.  Why?

All Replies

  • RUnglaube
    RUnglaube Posts: 135  Ally Member
    Seems like the AP name and some other parameters you set for specific device will only apply to the site where you configure it.
    "You will never walk along"
  • Zyxel_Freda
    Zyxel_Freda Posts: 397  Zyxel Employee
    Hi @HealthByRo ,
    Because the AP's name is recorded per site but not in AP, when the AP is moved to the other site, the AP will show the MAC in the other site.
    For example, if an AP is changed the name as AP01 in site A and then moved to site B, the AP shows its MAC as the name if it never changed the name in site B before. Once the AP is moved back to site A again, the AP's name shows AP01 but not its MAC.
    Thanks.
  • HealthByRo
    HealthByRo Posts: 28  Freshman Member
    IMHO that is a bug, not a feature.   When we are pre-configuring a dozen APs for a remote office, we cannot set them up ahead of time and then move them into the proper Site once a contractor installs them physically.
  • Jon_Snow
    Jon_Snow Posts: 3  Freshman Member
    Do you mean that you move the APs for physical sites but not sites on NCC?
    And, the APs are in the same site and the names are changed back to their MAC? 
  • HealthByRo
    HealthByRo Posts: 28  Freshman Member
    Jon_Snow said:
    Do you mean that you move the APs for physical sites but not sites on NCC?
    And, the APs are in the same site and the names are changed back to their MAC? 

    No.  We configure and test them at one office.  Then move them, physically, to the location that it is going to be used AND we moved them in NCC.   Problem is ... once we move them in NCC, all of the AP names gets changed back to MAC addresses (not matching the names that we physically labelled on the APs for physical installation)
  • RUnglaube
    RUnglaube Posts: 135  Ally Member
    Jon_Snow said:
    Do you mean that you move the APs for physical sites but not sites on NCC?
    And, the APs are in the same site and the names are changed back to their MAC? 

    No.  We configure and test them at one office.  Then move them, physically, to the location that it is going to be used AND we moved them in NCC.   Problem is ... once we move them in NCC, all of the AP names gets changed back to MAC addresses (not matching the names that we physically labelled on the APs for physical installation)
    Just curious, why don't you install the devices in the final NCC site from the very beginning and still do the test at the office? 
    Again, seems like all the device settings you configure on NCC (name, description, address, etc) are per-site based and it's not saved in the device itself.
    "You will never walk along"
  • HealthByRo
    HealthByRo Posts: 28  Freshman Member
    RUnglaube said:
    Jon_Snow said:
    Do you mean that you move the APs for physical sites but not sites on NCC?
    And, the APs are in the same site and the names are changed back to their MAC? 

    No.  We configure and test them at one office.  Then move them, physically, to the location that it is going to be used AND we moved them in NCC.   Problem is ... once we move them in NCC, all of the AP names gets changed back to MAC addresses (not matching the names that we physically labelled on the APs for physical installation)
    Just curious, why don't you install the devices in the final NCC site from the very beginning and still do the test at the office? 
    Again, seems like all the device settings you configure on NCC (name, description, address, etc) are per-site based and it's not saved in the device itself.
    We could do that but it gives a false alert to the team responsible for that site (which could be an outside consulting group) that something is down.

    I really think that Zyxel should give us an option to move a device from one Site to another with the option of keeping the device names/settings instead of resetting them to defaults only.
  • Zyxel_Freda
    Zyxel_Freda Posts: 397  Zyxel Employee
    Hi @HealthByRo

    Thanks for your suggestion, I'll help to add it as an idea for assessing the feasibility.

  • CrazyTacos
    CrazyTacos Posts: 53  Ally Member
    @HealthByRo I agree that maintaining device description should be optional.

    We should also consider organizations where sharing any information between sites are prohibited.

Nebula Tips & Tricks