User`s guide

184 Implementing an Open IBM SAN
Leaving all IP settings as a private network
For using the IN-VSN software from this local private network, the supplied
3Com/US Robotics hub is sufficient enough. To enable all IP based components
to talk together, plug in the Management PC and both INRANGE IP ports to this
3Com Hub. So initially, our network setup looks like that shown in Figure 3-4.
Figure 3-4 Private IP network for initial IN-VSN management ability
Enabling IN-VSN access from a corporate network
To exploit the remote management capabilities of the IN-VSN management
software, we recommend that you connect this network as a subnet to the
corporate LAN.
Before actually changing any parameters, it is important to obtain all the
information you will need in advance, such as:
򐂰 Available IP addresses
򐂰 Valid subnet mask
򐂰 Default gateway
To connect the INRANGE subnet to your corporate LAN, follow these steps:
1. Change the IP setting of the primary FCM blade using the RS232 Interface
(this should be done by INRANGE or IBM Customer Engineers).
2. Change the IP setting of the secondary FCM blade using the RS232 interface
(this should be done by INRANGE or IBM Customer Engineers).
3. Change the IP settings of the management PC using the common Windows
Control Panel tools. Reboot the Windows server.
4. From the management PC, ping both IP addresses of the director to ensure
that everything is set properly (provided that all components are still
connected to the 3Com IP-Hub).
5. Then attach all required ports to a switch or hub that is actually connected to
the corporate network. You could still use the 3Com Hub as a connecting
device.
Ethernet-Hub
64
Management PC FC/9000