Symptoms

Virtual Edition (VE) 1NIC provisioning shares the same IP address as both the management IP and self IP address, so VE with 1NIC enabled cannot pass any traffic through the data plane if a different self IP address from the DHCP management IP is assigned.

Impact

The GUI loses its connection. Connectivity is lost until the self-IP address is deleted via ssh/tmsh, or create a virtual server on 443 that points to localhost. Note: This is because creation of a self IP appears to be the trigger that causes uNIC to redirect all 443 traffic to the TMM instead of Linux. However, there is no warning of what will happen, and it is extremely unintuitive.

Conditions

- Log into the GUI and walk through the wizard or go directly to setting a self IP address. - Create a self IP address.

Workaround

Delete the newly created self-IP address to return access, or create a virtual server on 443 that points to localhost. As an alternative, use multi-NIC configurations.

Fix Information

Virtual Edition (VE) 1NIC provisioning shares the same IP address as both the management IP and self IP address, so VE with 1NIC enabled cannot pass any traffic through the data plane if a different self IP address from the DHCP management IP is assigned. The system now provides the following warning: 01071ac6:3: Invalid Self-IP '10.10.10.11/255.255.252.0': it must be the same as the management-IP '10.10.10.10/255.255.252.0' in VE-1NIC.

Behavior Change