Users Guide

674 | IPv6 Support Dell PowerConnect W-Series ArubaOS 6.1 | User Guide
Viewing Datapath Statistics for IPv6 Sessions
To view datapath session statistics for individual IPv6 sessions, access the command-line interface in enable mode
and issue the command show datapath session ipv6. To display the user entries in the datapath, access the
command-line interface in enable mode, and issue the command show datapath user ipv6. For details on each of
these commands and the output they display, see the ArubaOS CLI Reference Guide.
Important Points to Remember
This ArubaOS release does not support the following functions for IPv6 clients:
 Do not use VLAN pooling if you enable IPv6 forwarding on the controller, as VLAN pooling will flood IPv6
multicast packets for all VLANs that are part of the VLAN pool. This can cause autoconfigured clients to
acquire multiple IPv6 addresses (one for each vlan in the pool) making those clients behave unpredictably. If
you need to work around this limitation, you can unicast BC/MC traffic to every station. To enable this
workaround, you must enable the wlan ssid-profile battery-boost option, and install a Policy Enforcement
Firewall Next Generation (PEFNG) license.
 The controller offers limited routing services to IPv6 clients. It is highly recommended to use an external IPv6
router for a complete routing experience (dynamic routing and router advertisements).
 The controller does not perform network address translation on IPv6 addresses.
 The controller does not generate any IPv6 ICMP messages.
 Voice over IP is not supported for IPv6 clients.
 Remote AP supports IPv6 clients in tunnel forwarding mode only. The Remote AP bridge and split-tunnel
forwarding modes do not support IPv6 clients. Secure Thin Remote Access Point (STRAP) cannot support
IPv6 clients.
 The controller cannot terminate VPNs for IPv6 clients.
 VPN authentication cannot be performed for IPv6 clients.
 ArubaOS does not support RADIUS over IPv6 as an authentication protocol.
 Authentication of management users on IPv6 clients is not supported.
 The controller does not access the flow information field in IPv6 packet headers. (This field can be used by
IPv6 routers to identify the sequence of packets and to facilitate routing decisions.)
 A client can have an both IPv4 address and an IPv6 address, but the controller does not relate the states of the
IPv4 and IPv6 addresses on the same client. For example, if an IPv6 user session is active on a client, an IPv4
user session on the same client will be deleted if the idle timeout for the IPv4 session is reached.