A virtual network based on Destination Network Address Translation (DNAT) may be defined in the following cases:
• To hide the addresses of the connected devices from users by the use of virtual IP addresses.Caution! When an authorized user has service processor access, device console access, or native IP access, there is no way to prevent that user from seeing the IP address of the device while the user is connected.It is possible and desirable to hide devices’ real IP addresses from users who are authorized to access all other device management capabilities other than native IP, service processor console, or device console.
• When multiple private subnets must be supported by a single network route, and you do not want to require authorized users to configure routes to each network.For example, if three connected devices have addresses 192.168.0.1, 10.0.25, and 17.10.11.12, three private subnets could be defined. A virtual network would map the IP addresses from the three private subnets to virtual IP addresses in the same virtual network range.
IP address to assign to the OnBoard from the virtual network address range. For example, if the virtual IP address of the network is 10.0.0.0, 10.0.0.254 would be a valid IP address that could be assigned to the OnBoard. The administrator would then have all the other addresses to assign to devices, except for 10.0.0.0 and 10.0.0.255. Netmask (which is used in combination with the network address portion of the “Address” above to define the address range of the virtual network.Note: Some service processors do not work with virtual network (DNAT) addresses.