Open with this. The ticket names the rack but gives no IP for the rack manager, and the SCHIE Lab Portal does not list it either. The partner who raised it is offline. You are standing in front of the rack with no address to connect to.

1. Two ways in, one prompt

The Rack Manager CLI is reachable two ways, and both land at the same RScmCli# prompt. Serial is the reliable fallback when the network is down or you do not yet know the Rack Manager's IP address.

2. Over serial (UART)

1. Plug a console (serial) cable from your laptop into the Rack Manager's serial UART port.
2. Open a terminal program such as PuTTY and select the correct serial COM port.
3. Connect, then press Enter to bring up the logon prompt.
4. Log in with your assigned lab credentials.

3. Over SSH (Ethernet)

1. Find the Rack Manager's IP address: check with the partner, the ticket, or the SCHIE Lab Portal, or connect once over serial and run show network.
2. From a machine on the same lab network, open an SSH session to that address.
3. Enter your password when prompted.

The guide's example, as the pattern:

ssh labtech@172.29.60.222

4. Where the serial link runs

Three connections matter on every Rack Manager: NIC1 to the rack network, NIC2 to management switch port 25, and a serial console link to the management switch. The serial link is the one this lesson needs.

[Image: Rack_Manager_Onboarding_SCHIE_v4, Figure 4 - front view of the PMDU with the Rack Manager installed: blue serial cable in the RJ4 / MGMT Console port, white cable in NIC1, orange cable in NIC2]

[Image: Rack_Manager_Onboarding_SCHIE_v4, Figure 7 - standalone Rack Manager at U24 beneath the management switch at U25, showing the white NIC1, orange NIC2 and blue MGMT SW cables]

Key takeaway. The colours are consistent across both layouts - white for NIC1 and the server BMC links, orange for NIC2, blue for the serial console - so when you trace a connection in an unfamiliar rack, start with the cable colour.

5. You are in: first moves

Every command starts from RScmCli#. A good first move is to confirm you are on the right system and that it is healthy:

RScmCli# show system report

The full rack health, version and status come from:

RScmCli# show manager info

Key takeaway. Every successful command ends with Completion Code: Success. That line confirms the CLI accepted and ran the command. An error line means the change did not take.

The opening situation, resolved. No IP is not a blocker, it is what the serial console is for. Connect over serial with a console cable to the UART port, log in with your assigned lab credentials, and run show network to read the address. Then continue over SSH from a machine on the same lab network.

Keep this. Serial and SSH both land at RScmCli#. Serial is the fallback when the network is down or the IP is unknown: console cable to the UART port, terminal program on the correct COM port, Enter for the logon prompt, assigned lab credentials. The IP comes from the partner, the ticket, the SCHIE Lab Portal, or serial plus show network. Trace cabling by colour: blue is the serial console. First moves: show system report, then show manager info. Completion Code: Success means the command ran; an error line means the change did not take.

Source: Rack_Manager_Onboarding_SCHIE_v4.docx, Sections 2, 2.1, 2.2, 2.3, 3.1 and 3.2, and Appendix C.