System information

Appendix A: Advanced Device Configuration 393
Address Configuration for Connected Devices
OR
• In the Web Manager on the OnBoard, clicking the “Service
Processor Console” link on the Access Devices screen.
AND
• Bringing the management application up from the service
processor’s command line.
• The console of the server on which the service processor resides, in one of
the following two ways:.
• Invoking ssh with the devconsole command in the following
format
ssh -t allSPs:sp2@192.168.1.1 devconsole
OR
• In the Web Manager on the OnBoard, clicking the “Device Console”
link on the Access Devices screen.
Why Define Virtual (DNAT) Addresses?
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