IBM System x3550 M3 Management Node with Software Preload Quick Start Guide - v1.72
IBM Confidential 06/21/2012 Page 6 of 9
4. Go back to Windows Server, and refresh the Network Connections Screen. Notice in our
example below, the Windows Enumeration is not the same as the Physical NIC
numeration on the back of the x3550. Physical NIC 1 is Windows #3.
5. In
6. Table 2, record what the Physical to Windows Enumeration is for NIC 1. This is very
important. Problems will arise if you do not reference this table in your setup.
Repeat for remaining NICs.
Physical NIC Enumeration
(on back of x3550)
Windows Enumeration (Network Connections)
Table 2 – Physical to Windows NIC Enumeration
Caution
The hostname of the x3550 M3 Management Node with Software Preload is defined in
manufacturing. A malfunction may occur if the hostname is changed at the site of installation
without using the proper procedure.
If the hostname of the x3550 M3 Management Node with Software Preload requires modification
at the site of installation, refer to the IBM Retain TIP document at the following location:
http://www-304.ibm.com/support/docview.wss?uid=swg21258834
Validate Configuration and Setup
Use the following steps to confirm that the x3550 M3 Management Node with Software Preload
has been setup and configured properly:
1. Use the Ping command to and from a known host to ensure that network connectivity is
operational
2. Check to make sure DB2 is started and set to automatic (i.e., Start-> Administrative
Tools-> Services -> DIRINST1-0)
3. Check to make sure you can log into Director (i.e., Start->All Programs -> IBM Systems
Director Console
To Next Page
Loading...
