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

CAUSES: B-G in the Problem list.

Unable to create LLL session42.

Invalid MSP IP Address specified.1.

Invalid userid/password specified.2.

REASON: Low-Level Link obtained a TCP/IP response (ping)

but could not establish the protocol used for communication

between the Low-Level Link and a service processor.

CAUSES:

You might have attempted to connect to a valid TCP/IP

address on the dedicated LAN that was not a master

service processor (MSP) IP address.

The logon to (both) master service processors failed.2.

INITIAL TROUBLESHOOTING:

Examine the configured Low-Level Link TCP/IP

addresses for the S-series system on the system console

you are using. Confirm them with the customer carefully.

●

Make certain that a system console or other TCP/IP

address was not accidentally configured in place of a

service processor TCP/IP address.

●

Make certain that correct updates on one system console

were entered on all others.

●

Caution: Before changing anything, write down

every TCP/IP address you find configured on any

system console set up to manage an S-series

server. Losing track of TCP/IP addresses for the

master service processors is one of the worst

problems that can occur.