Environment : This article applies to all Aruba Access Points running Aruba InstantOS version 126.96.36.199-188.8.131.52 or higher.
Aruba InstantOS 184.108.40.206-220.127.116.11 comes up with support for hierarchical deployment, which basically means that IAP can form Wi-Fi or 3G uplink and its ethernet ports can be made as downlink to which additional IAP's or wired network can be connected. Such deployment topologies are much useful in scenarios where wired infrastructure from customer is not readily available (or) it is temporarily down.
- IAP with more than one wired port can now be connected to another IAP with single ethernet port (with Eh0 bridging enabled) and Wi-Fi/3G as uplink.
- For IAP's with dual downlink ports, one port can be configured on a private VLAN without authentication to connect slave IAPs. This port should not be used for any wired client connections. However, the other port can be configured with authentication connecting wired clients.
- Only one AP in the network uses its downlink port to connect to the other IAPs. This AP (called as the root AP) acts as the wired device for the network, provides DHCP service and an L3 connection to the ISP uplink with NAT funtionality. The root AP is always the master of the Instant network.
Below shown are the different network topologies of hierarchical deployment:
In the above topology, IAP gets an IP from the uplink Wi-Fi router or 3G Internet Service Provider and acts as wired device for the network providing DHCP service and as a edge router with NAT funtionality.
In this topology, IAP gets an IP from the uplink Wi-Fi router or 3G Internet Service Provider and acts as wired device for the network providing DHCP service and as a edge router with NAT funtionality. This root AP is always the master of the Instant network.
Eth0 port configured on a private VLAN without authentication, for connecting to slave APs and Eth1 with authentication configured for connecting to wired clients.