Operating notes
Tunneled node profile may be created using CLI and SNMP.
- The tunneled node profile supports configuring of:
Primary controller (IPv4 only).
Backup controller (IPv4 only).
Heartbeat keepalive timeout – range 1-8 seconds.
Only one tunneled node profile may be created.
The tunneled-node profile may be applied to a physical port only via CLI and SNMP.
The configuration related to the tunneled node profile will be stored in the flash and restored after a boot.
High availability (HA) will be supported for the tunneled-node related configuration.
- A tunnel, associated with a port, is "up" when both 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 has failed when the controller does not respond after five attempts. All tunnels are brought down with a heartbeat failure.
A tunnel "up or down" status will be 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 tunneled-node can fallback to local switching in the event of a tunnel failure.