Operating notes

  • Tunneled node profile can be created using CLI and SNMP.

  • The tunneled node profile supports configuring of:

    • Primary controller (both IPv4 and IPv6).

    • Backup controller (both IPv4 and IPv6).

    • Heartbeat keepalive timeout – range 1-40 seconds.

  • Only one tunneled node profile can be created.

  • The tunneled-node profile can be applied to a physical port only via CLI and SNMP.

  • The maximum number of physical ports to which the profile may be applied is:

    • Aruba 5400R Switch Series (non-VSF): 256

    • Aruba 5400R Switch Series (VSF): 512

  • High availability (HA) will be supported for the tunneled node related configuration.

  • A tunnel, associated with a port, is "up" when the following conditions are met. A tunnel is "down" when either of the conditions are not met.

    • Either the primary or backup controller is reachable.

    • A boot strap message response is received from the controller.

  • Heartbeat between the switch and controller fails when the controller does not respond after five attempts. All tunnels are brought down with a heartbeat failure.

  • A tunnel "up or down" status is logged for each tunnel node port in the event log.

  • The show tech command dumps all user-mode and test-mode command outputs.

  • To reach the Aruba controller, the VLAN must have a manual IP configured.

  • With the exception of the 802.1x BPDU, the switch consumes all other BPDUs.

  • The controller cluster cannot have mix of IPv4 and IPv6 nodes.

  • IPv6 addresses are not allowed for both Primary and Backup controllers when in Port-Based Tunnels.