Configuring NPF VPN for VIPA
You can allow No Policy Filter (NPF) VPN connections to be applied automatically as preferred interfaces for Virtual Ip addresses (VIPA).
Prior to IBM i 7.2, the NPF connection would only be loaded against the one line description currently indicated as the local choice for the next hop given a route to the desired destination. This causes problems if the Virtual IP addresses are configured, which could allow for multiple paths to a particular destination.
If a NPF connection is being loaded and the local IP address is determined to be a VIPA address, the connection will be loaded against any additional line description that is included in the IP address preferred local interface list.
If the VPN configured for NPF does not work with a particular VIPA address, perform one of the follow 3 options:
NOTE: the following example is specifically for VPN configurations for IBM Universal Care connectivity. In this example the Ip address to the IBM Gateway is 129.42.160.16.