0023 on HMC Console

Resolving The Problem

Console connection gets a 0023 error, No information retrieved - verify configuration.

Fast Path

Access Client Solutions (ACS) 1.1.4 or later configured to use a HMC console "fastpath" connection direct to a specific partition will fail with this error if the server is no longer managed by the HMC. Verify the ACS configuration and that managed server connection state.

Duplicate Connection
One possible cause is duplicate managed system entries for the same system. At restricted shell, run the following command:

lssysconn -r all

Look for two or more entries for the same system MTMS. If there are two or more entries, do the following:

Step 1: Open a restricted shell by right-clicking on the desktop. Then, click Terminals > rshterm

Step 2: Type the lssysconn -r all command; for example:

lssysconn -r all
resource_type=sys,type_model_serial_num=9406-520*103E8FE,sp=primary,sp_phys_loc=unavailable,ipaddr=192.168.255.254,alt_ipaddr=unavailable,state=Connected
resource_type=sys,type_model_serial_num=unavailable,sp=unavailable,sp_phys_loc=unavailable,ipaddr=172.16.255.254,alt_ipaddr=unavailable,state=Connecting,connection_error_code=Connecting 0000-0000-00000000

Step 3: Locate the old address. The old TCP/IP address will appear in an entry with state of Connecting... or No connection.

Attempt to PING the IP address from the HMC. If PING is successful to the IP address from the HMC, contact IBM Support.

If PING to the IP address is not successful, proceed with Step 4.

Step 4: Remove the connecting entry by typing the following command:

rmsysconn --ip <ip> -o remove

where <ip> is the TCP/IP address located in the previous step for the connecting system.

Step 5: Verify that it was removed by running lssysconn -r all. If the connection is no longer there, reboot the HMC.

A 5250 console session should open and not fail with the 0023 error.

Note: At some HMC code levels, the entry is not removed (no error). If this is encountered, contact IBM Support.

HMC Initialization
Another possible cause is the HMC is not fully up and running. If possible, confirm the HMC is up and fully operational. If the HMC is at a pre-initalization screen, it is not fully operational and it is possible to get this error code when attempting to start a remote 5250 session to an i partition.