Unable to Connect to the Master Service Processors (MSPs) Over a Low-Level Link

D. Verify the cable connections from the system console through the LAN
hub to the PMF CRU. Make sure that the correct dedicated LAN
Ethernet cable is connected to the Ethernet port of the PMF CRU, not
to the Serial Console port. See Step E and General Tips.
E. Verify that the LAN hubs on the dedicated LAN are operating correctly.
Check to see that the green Link OK lights of the hubs are lit a
continuous green for each Ethernet cable connected to a live device.
Notes: One port on a hub (often port 8) can be configured in two
different ways, depending on whether or not a port connects to a node
on the LAN, or to another hub in a daisy-chain. If this setting (usually a
physical switch) is incorrect, at least part of your customer's dedicated
LAN won't work.
F. Check the subnet mask, and IP address, and ping the IP address for
the SPs in order from the system console.
To Ping an SP:
For Windows NT, select Start> Programs>
Command Prompt
●
For Windows 2000 and Windows XP, select Start>
Programs> Accessories> Command Prompt
●
A DOS command prompt appears. Type ping followed by
the IP address:
>ping 192.231.36.2
The ping command sends echo packets to which the
response from the remote end is received within a few
milliseconds (5 to 30) in a successfully configured topology.
If results of the ping indicate a less than desirable
responsiveness, you might have used an invalid IP
address, or there might be a problem with the physical
connection (check cables and hubs on the dedicated LAN),
a problem with the TCP/IP configuration or LAN adapter on
the PC, or a problem with the PMF CRU.
A ping result of "Request timed out" means that no device
answered to that address. Ping tries several times and
records the time required for a response, in case there is
an intermittent problem.