Assessed for the following products and versions:
- Steelhead 9.15.0 and 9.15.1
- SCC 9.15.0 and 9.15.1
- Interceptor 8.1.2 and 8.1.3
Feature Area |
Caveats/Comments |
Management connectivity to Pri and Aux | |
Static IP Addressing | |
DHCP IP Addressing |
|
Stateless Address Autoconfiguration |
|
DNS Server Lookup | |
Optimization: Enhanced Ipv6 Auto Discovery | It is required to enable enhanced auto-discovery for both ipv4 and ipv6 on the UI peering rules page. All Steelheads in the path of an IPv6 connection should have enhanced auto-discovery enabled. |
In-Path Rules | Correct Addressing only (Full and Port transparency are not supported. No bug exists – need a KB (there is no bug for this). |
Hardware Assist Rules | |
Protocol Optimization : MAPI |
|
Protocol Optimization : SSL, TLS |
|
Protocol Optimization : Signed SMB 2/3 |
|
Protocol Optimization : HTTP |
|
Protocol Optimization : FTP |
(KBA S38053) |
Net Flow | |
Domain Join / Domain Auth |
(KBA S38054) |
SSL Secure Peering | |
802.1Q Vlan tags on in-path interfaces | |
GRE tunneling | |
Packet Mode Optimization | |
Server Side Out-of-Path | |
Virtual In-Path with Policy Based Routing | |
Feature Area | IPv6 (Can I enable IPv6 for this line item, or does this support IPv6) | Single Stack IPv6 only (Does the feature work in Pure IPv6 environment) | Dual Stack - IPv6 + IPv4 (Does the feature work in dual stack environment) |
Connection Forwarding | Yes | No | Yes |
IPv6 Feature Support Single Stack and Dual Stack |
Comments |
DNS Caching | |
CIFS Prepopulation | |
WinSec Controller Connectivity | |
IPSec Secure Peering | |
Sites and networks | |
Path Selection | |
WebProxy | |
IPv6 QoS | |
Custom Applications | |
Management ACL | |
Auto Discovery Protocol | “Auto discovery Protocol” will be used if “Enhanced Auto Ipv6 Auto-Discovery” is not enabled. Always run with the “Enable Enhanced IPv4 Auto-Discovery" and “Enable Enhanced IPv6 Auto-Discovery" enabled in the UI’s peering table rules page. |
In-Path Rule Full Transparency | |
In-Path Rule Port Transparency | |
Host Labels | |
Domain Labels | |
Protocol Optimization: NFS | |
Virtual In-Path with WCCP IPv6 | |
Segstore (Datastore) Syncing | |
Serial Failover cluster | |
REST API (including SCC access) | The Steelhead REST API cannot service any requests when the Steelhead is configured for Single Stack IPv6. This includes SCC configuration. |
LACP (Link Aggregation) | |
BMC / IPMI access | |
IPv6 wizard after manufacture | |
VCX Steelhead-V Provisioning | The Steelhead-V Provisioning script can be used to provision the Steelhead initially but avoid using it to set Ipv6 addresses. Set an Ipv4 address first, then configure an Ipv6 address in the VM once it is up. |
Feature | Comment |
Management connectivity | |
Steelhead Policy Push | Only Dual Stack IPv4/Ipv6 is supported: Single Stack Ipv6 is not supported. |
Configuration | |
Snapshots | |
Stats |
Feature |
NFS Mount for Configuration Backups |
Anything not listed in the explicitly supported list may not be supported. |
IPv6 Feature Support |
Redirection |
In-Path Rules |
Load Balancing Rules |
Xbridge |
Connection Tracing |
Fair-peering V2 |
IPv6 Connection Forwarding |
HAP Rules |
Net Flow |
VLAN Tag |
VLAN Segregation |
Feature |
Controller Management Access |
Cluster config sync Cluster Join |
CA Generate TCP trace |
In-Path rule statistics |
Report filters |
Source labels |
Auto Discovery Relay (DaaS) |
Correct Addressing |
Enhanced Auto Discovery |
Fixed Target Rules |
In-Path Rules Policy config |
Domain Labels (HNBI) |
Feature |
In-Path Rules - Full Transparency |
In-Path Rules - Port Transparency |
Enhanced Auto Discovery |
Branch Mode |
Branch Warming |
CA Detected Steelhead |
DNS Proxy |
Host Labels |
CA Controller Web and FTP proxy (Host Settings) |