Skip to main content

FAQs

General help​

  • How to get into the ordering process: Order Management
  • Switches and access points require Internet access in two cases: Initial bootstrap and download of the firmware upgrade.
  • If you want to restrict access in a firewall, the restrictions below can be applied.
  • However, we recommend permitting an Internet connection for the switches.

evice.arubanetworks.com​

  • This is the rendez-vous server for the access points and switches which must connect there once and are then routed to the Swisscom-hosted platform.
  • The only data on this server indicates that it relates to a Swisscom BNS / Enterprise Connect device

http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html​

  • FW downloads are distributed via Amazon AWS (Amazon Web Service).
  • For the managed LAN devices to function correctly, the DHCP server of the Cloud Gateway must be used.

Swisscom devices (such as the Swisscom TV Box or VoIP telephones) must not be connected in groups other than the corp default group.​

  • Otherwise the Quality of Service cannot be guaranteed and functions are limited.

After a change to the LAN-IP network, the switches/access points must be rebooted so that the IP address is updated.​

At the moment, this is only possible with the “corp” default group, not with another VLAN/group:​

  • LAN routing
  • BNS – DCS / Enterprise Connect – LAN-I connection

Even if you connect VLAN/group A with the corp default group, it has no connection to DCS/LAN-I will be possible soon.​

A maximum of 6 groups (plus DMZ and corp default group) is possible.​

  • In the case of public WLAN, two of these groups are needed for PWLAN.
  • If 6 groups are already set up, two must be deleted before PWLAN can be set up.

At the moment, you can only configure LAN Routes and Service Connections for the corp default group.​

  • This will be extended in the future.

It is possible to ping the Cloud Gateway IP address of another VLAN, even if these are not connected.​

  • The following characters are permitted for managed LAN passwords/labels:
  • Letters: ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
    • Numbers: 0123456789
    • Special characters
      • A password must be at least 10 characters long.
      • At least one letter of the password must be upper-case, at least one lower-case.
  • The password must also contain at least one number and one special character.

How are managed LAN devices addressed in the network?​

  • Managed LAN devices (switches and access points) have assigned IP addresses from the corp LAN network configured on the website.
  • To ensure that the same IP addresses are not assigned to a new access point/switch, they are inventoried and displayed together with all the terminal devices connected to the network under Devices in the Enterprise Connect Dashboard.

802.1X​

  • All access points are assigned an IP address from the DHCP range of the “corp” default group. In the case of 802.1X, a fixed IP address is required for the virtual controller (usually .3, or the lowest free IP address from the “corp” default group at this location).
  • This fixed address is used by the access points as the source IP for the 802.1X queries to the Radius server. This IP address must also be configured on the Radius server.

Switch​

  • As the switch IP address has to be configured for the Radius server for 802.1X, it would not be advisable for the IP address to change.
  • Therefore, immediately after the pairing of the switch, a static IP address is assigned, starting with the second-lowest free IP address from the corp default group (e.g. 4, it does not belong to the configurable DHCP range defined for a VLAN and is also not virtual controller [.3] or CPE IP [.2]).

Non 802.1X​

  • Access points: All access points are assigned an IP address from the DHCP range configured for every VLAN.
  • Switch: Assigned one of the first IP addresses from the VLAN range (e.g. 5, does not belong to the DHCP range defined for a VLAN).

Frequently asked questions​

Which IP address does my switch have if it has not yet been paired in the Dashboard?​

  • In this case, the switch has an IP address from the DHCP range of the Corp VLAN of the corresponding location.

How can you change the IP address of a switches?​

  • It is not possible to change it from the Dashboard, but this should be possible in the future.

What does “free IP address” mean?​

  • All IP addresses except the network address (e.g. 0 for /24), Broadcast address (.255 for /24), all IP addresses that were configured as servers in the Dashboard, the cloud router IP address and CPE IP address are free.
  • In particular, during the definition of the static switch IP address or virtual controller IP address for IAP, an ARP check is NOT carried out to detect any duplicated P addresses.

How is the IP address assigned to the switch?​

  • It is assigned via DHCP with static DHCP assignment (based on the switch MAC address) outside the DHCP range.

Why is it not taken from the DHCP range?​

  • An IP address (of the virtual controller) is needed to manage access points, and an IP per switch is needed to manage switches.
  • Use outside the DHCP range causes fewer problems and avoids conflicts.

How does the switch solve an IP conflict problem?​

  • If the switch IP address displayed in the Dashboard was already manually assigned to another device, the switch cannot resolve the conflict.
  • In the Dashboard inventory, a check is carried out to ensure that new devices are not assigned used IP address (see definition of free IP address above).
  • If there are manually configured IP addresses in the network that are not entered as servers in the Dashboard, conflicts can only be avoided by orderly network planning.

It is possible that the switch IP address on the Dashboard does not correspond to reality?​

  • Yes, in some cases this is possible; usually, when two switches are activated in the Dashboard but only one physically exists.
  • In these cases, you are advised to carry out pairing of the physically existent switch again.
  • If you address your LAN in a completely static manner and do NOT want to activate DHCP on the Cloud Gateway: does LAN management still work? Or how can the switches be assigned the IP address?
  • Managed LAN devices are assigned IP addresses from the Corp network and DHCP should be activated in this network, otherwise the devices cannot be assigned IP addresses.
  • If you want to use your own DHCP server, it will work, but you are advised to create a static DHCP assignment as soon as 802.1X is used
  • If you want a network to be manually addressed (via fixed IP addresses), you are advised to use a separate group (e.g. GOI1 or VLAN1).
  • In this case, the “corp” default group should be used to manage the network components where the internal DHCP server is activated. Example for “corp” default group:
  • .1 is the Cloud Gateway
  • .2 is the Centro Business CPE
  • .3 is the virtual controller (for 802.1X)
  • .4, .5, .6 etc. for switches Access points take addresses from the DHCP range

What should you do in the event of problems with Enterprise Connect?​

If you experience problems with Enterprise Connect, you can proceed as follows:

  1. Verify the technical configurations in the Enterprise Connect Dashboard:
    • Is the network configured correctly (LAN IP addresses, default gateway = cloud gateway)?
  2. Perform a reboot/reset of the CPE (via EC Dashboard or directly on the device).
    • If you still experience problems, please call us:
      • In the event of commissioning and configuration problems, on Tel.: 0800 800 900
      • Or in the event of technical faults on a service that was previously working, on Tel.: 0800 724 724