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

ManualsBrandsHP ManualsServerHP Integrity NonStop Troubleshooting Tips

Unable to Connect to the Master Service

Processors (MSPs) Over a Low-Level Link

Symptom

Unable to connect to a master service processor (MSP) using either the

OSM or TSM Low-Level Link, or the TSM Configuration Application.

Version

All: OSM or TSM Low-Level Link.

TSM client software Version 5.0 and earlier: TSM Configuration

Application.

Problem

This can be caused by one of the following:

You have entered an incorrect Low-Level Link user name or

password for the system.

An incorrect Low-Level Link IP address is configured in the system

list.

You have lost, or never knew, the IP addresses for the SPs as they

are configured in the enclosure backplanes.

An Ethernet cable is disconnected, is connected to the wrong port, or

is bad.

A hardware or configuration problem exists on a hub on the dedicated

LAN.

There is a problem with the system console TCP/IP or LAN

configuration.

The SP is experiencing a software or hardware problem.G.

Too many simultaneous sessions are connected to the same SP,

possibly from different system consoles. (This is an unlikely cause.)

Fix

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.

For each problem described above, try the related fix or workaround:

Summary of content (6 pages)

PAGE 1
Unable to Connect to the Master Service Processors (MSPs) Over a Low-Level Link Symptom Unable to connect to a master service processor (MSP) using either the OSM or TSM Low-Level Link, or the TSM Configuration Application. Version All: OSM or TSM Low-Level Link. TSM client software Version 5.0 and earlier: TSM Configuration Application. Problem This can be caused by one of the following: A. You have entered an incorrect Low-Level Link user name or password for the system. B.
PAGE 2
A. Verify that the Low-Level Link user name and password are correct for the system. If passwords are unknown, try the default user ID and password from the OSM User's Guide or the TSM Configuration Guide. If this fails, an authorized service provider can use the NSK SPTOOL resetuser command to reset the MSP password files to the factory default setting. The SPTOOL is available from the Intranet version of the CSSI Web. Notes: ● SPTOOL is intended for use only by service providers trained by HP.
PAGE 3
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.
PAGE 4
G. If you think the SP is experiencing problems, try the following: If the NonStop Kernel operating system is running, look in $ZLOG for reoccurring SPR subsystem events related to SP state changes for the SPs in Group 01 and for SPAR dumps. Contact the GCSC and provide them with a tape copy of the $SYSTEM.ZSERVICE subvolume, as well as the version of the SP firmware (if possible). Notes: If OSM or TSM cannot connect to the first SP it tries, it will attempt to connect to the peer SP.
PAGE 5
● ● ● ● 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.
PAGE 6
CAUSES: B-G in the Problem list. 2. Unable to create LLL session4 1. Invalid MSP IP Address specified. 2. Invalid userid/password specified. 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: 1. 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. 2.