164 | TunneledNodes DellPowerConnectW-SeriesArubaOS6.2 | User Guide
Figure 46: Tunneled node configuration operation
Configuring a Wired Tunneled Node Client
NOTE: ArubaOS does not allow a tunneled-node client and tunneled-node server to co-exist on the same controller at the same
time. The controller must be configured as either a tunneled-node client or a tunneled-node server. By default, the Aruba controller
behaves as a tunneled-node server. However, once tunneled-node-server xxx.xxx.xxx.xxx is configured on the controller, the
controller becomes a tunneled-node client. To remove the tunneled-node client function, use the command tunneled-node-server
0.0.0.0 to disable the tunneled-node client on the controller side.
This section describes how to configure a tunneled node client. You can use the WebUI or the CLI to complete the
configuration steps.
1. Access the Wired tunneled node CLI according to the instructions provided in the installation guide that
shipped with your tunneled node. Console access (9600 8N1) and SSH access are supported.
2. Specify the IP address of the controller and specify tunnel loop prevention.
n CLI:
(host)(config) #tunneled-node-address ipaddress
(host)(config) #tunnel-loop-prevention
For example:
(host (config) # tunneled-node-address 10.10.1.1
(host)(config) #tunnel-loop-prevention
n WebUI
a. Navigate to Configuration>Advanced Services>Wired Access page.
