Known limitations in NetApp Console local deployment
Suggest changes
PDFs
Known limitations identify platforms, devices, or functions that are not supported by this release of the product, or that do not interoperate correctly with it. Review these limitations carefully.
Console VM limitations
Possible conflict with IP addresses in the 10.42.0.0/16 and 10.43.0.0/16 ranges
NetApp Console local deployment uses fixed address space for inter-service communication. The IP range 10.42.0.0/16 and 10.43.0.0/16 are used for the internal network. Before deploying Console local deployment, ensure these IP ranges are not assigned to other VMs, DHCP scopes, DNS records, or load balancer VIP pools on the VLANs made available to the Console local deployment.
See Knowledge Base article Agent IP conflict with existing network for instructions on how to change the IP address of the agent’s interfaces.
Shared Linux hosts are not supported
NetApp Console local deployment isn't supported on a VM that is shared with other applications. The VM must be dedicated to the NetApp Console local deployment.
Third-party agents and extensions
Third-party agents or VM extensions are not supported on the NetApp Console local deployment VM.
Identity and access limitations
| Area | Limitation |
|---|---|
Local user onboarding and account recovery |
An SMTP email server must be configured before you can invite local users or use password reset for local users. |
Active Directory integration |
Duplicate email addresses are not supported across local users and Active Directory users. For example, if the initial local organization admin later adds themselves as an Active Directory user, they must use a different email address. |