Configuration Procedures

The section below details different configuration procedures related to tunneled-node configuration:

ArubaOS does not allow a tunneled-node client and tunneled-node server to co-exist on the same managed device at the same time. The managed device must be configured as either a tunneled-node client or a tunneled-node server. By default, the managed device behaves as a tunneled-node server. However, once tunneled-node-server xxx.xxx.xxx.xxx is configured on the managed device, the managed device 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 managed device.

Configuring a Wired Tunneled Node Client

This section describes the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. procedures to configure a tunneled node client.

  1. Access the Wired tunneled node CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. according to the instructions provided in the installation guide that shipped with your tunneled node. Console access (9600 8N1) and SSH Secure Shell. SSH is a network protocol that provides secure access to a remote device. access are supported.
  2. Specify the IP address of the managed device and specify tunnel loop prevention.

    (host)(mynode)(config) #tunneled-node-address <tnode-ip-address>

    (host)(mynode)(config) #tunnel-loop-prevention

  3. Access each interface that you want to use and assign it as a tunneled node port.

    (host)[mynode](config) #interface gigabitethernet <slot/module/port>

    (host)[mynode](config-submode) #tunneled-node-port

  4. Verify the configuration.

    (host)[mynode](config-submode) #exit

    (host)[mynode](config) #show tunneled-node config

Configuring an Access Port as a Tunneled Node Port

You can configure any port on any managed device as a tunneled node port using the tunneled-node-port command. Set the tunneled-node-address as the managed device to act as the tunneled node termination point. The tunneled-node-port command tells the physical interface to tunnel that traffic on the managed device.

  1. Enable portfast on the wired tunneled node.

    (host)(mynode)(config) #interface gigabitethernet <slot/module/port>

    (host)(mynode)(config) #spanning-tree portfast

  2. Assign a VLAN Virtual Local Area Network. In computer networking, a single Layer 2 network may be partitioned to create multiple distinct broadcast domains, which are mutually isolated so that packets can only pass between them through one or more routers; such a domain is referred to as a Virtual Local Area Network, Virtual LAN, or VLAN. to the tunneled node port.

    (host)[mynode](config-submode) #switchport mode access

    (host)[mynode](config-submode) #switchport access vlan <id>

Configuring a Trunk Port as a Tunneled Node Port

  • To enable switchport on the wired tunneled node execute the following commands:

    (host)[mynode](config-submode) #switchport mode trunk

    (host)[mynode](config-submode) #switchport trunk allowed vlan <WORD>

  • To verify the status of the wired tunneled node execute the following commands:

    (host)[mynode](config-submode) #show tunneled-node state

    (host)[mynode](config-submode) #show tunneled-node config

  • To check the current usage on the managed device execute the following command:

    (host)[mynode] #show license-usage ap

Each tunneled-node client uses one AP license. Attaching an additional wired client on the tunneled node client does not increment the AP license usage on the managed device.