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

If more than one system console is present on the dedicated LAN,

try to connect from all other system consoles. Record the IP

addresses configured for the Low-Level Link as found on each

system console. One of these system consoles may currently have

a correct IP address for the particular service processor you need to

reach. If you can connect from one system console, but not from

others, you can rule out some potential causes for the problem.

●

Make sure that the dedicated LAN Ethernet cables are connected to

the Ethernet port on the PMF CRU. It is physically possible to

connect an Ethernet cable to the serial console port, but it won't be

functional.

●

Try to connect twice, especially if you have recently restarted your

system console. Sometimes the first connection attempt after you

restart your system console fails, but later attempts succeed.

●

Physical cabling defects might be rare in original equipment, but

cables are always at risk of being disconnected or damaged.

●

Ping Commands

Use the ping command from the MS-DOS command prompt, especially if

you suspect cable failures or miscabled systems. If you have multiple

S-series servers on the same dedicated LAN, or if you have multiple

system consoles on that dedicated LAN, you can ping each one individually

from a given system console to narrow down a connectivity problem.

At the MS-DOS command prompt, use this command to determine a

system console's IP address, subnet mask, and default gateway.

>ipconfig

To perform a loopback ping from your system console to itself (helping to

test your system console's Ethernet card), enter this command:

>ping 127.0.0.1

Reference

Low-Level Link dialog box messages:

Both MSPx and MSPy are not responding. LLL logon to <system>

failed.

REASON: Low-Level Link used the IP addresses configured for

the master service processors (MSPs) on your system

console's system list under the system name <system>.

Nothing responded to basic TCP/IP commands (ping), not even

a non-MSP device.