Bare Metal Instances

The Bare Metal Instances page is used to view allocated physical servers, manage login credentials, and perform operations such as power control/release. After logging into the console, click "Bare Metal Instances" in the left navigation to enter this page.

Page Structure

• Top Filter: Supports filtering by instance name/ID, status, availability zone, and provides a refresh button to get the latest status.
• Instance Card: Each card displays host location information (e.g., tianjin / 10.0.20.9), instance name, accelerator card specifications (e.g., 8 × TPU), expiration time, and allocation status.
• Resource Specifications: Lists CPU/Memory/Storage, e.g., CPU: 144C, Memory: 1TB, Storage: 16TB, facilitating quick hardware verification.
• Login Information: Contains SSH account (e.g., jinni@10.0.20.9) and a Web Terminal one-click entry button, allowing you to copy the address or open it directly as needed.
• Credential Management: The page provides an entry to view/edit passwords, supporting quick rotation or copying to the clipboard. Password updates take effect immediately.

Tip: Bare metal instances are physically exclusive resources. If they are not used for the time being after debugging is completed, please shut them down or release them in time to reduce costs.

Common Operations

1. Login to Instance

   • Copy the SSH address and log in directly via the intranet jump server or dedicated line.
   • Click Web Terminal to enter the command line or visual workbench in the browser, suitable for temporary operation and maintenance.

2. Power Control

   • In the "More" menu at the bottom right of the card, you can perform Power On / Power Off / Release on the instance.
   • Releasing will recycle the entire machine and clear all local data. Be sure to complete the backup before execution.

3. Status Confirmation

   • The power indicator on the right shows the current running status (green dot is running, gray is shutdown).
   • Click the refresh button to re-pull the BMC status to eliminate information lag caused by long-term operations.

4. Credential Maintenance

   • Use "Edit" next to the password field to quickly reset the login password.
   • After resetting, relevant operation and maintenance members need to be notified synchronously to avoid login failures due to key expiration.

Management Suggestions

• Reasonably Plan Expiration Time: The page will display the specific expiration time (e.g., 2026/11/26 17:05:19). It is recommended to renew or release 3–5 days in advance to avoid task interruption.
• Distinguish Business Uses: Include project or environment information when naming instances (e.g., prod-llm-tianjin-01) to facilitate team collaboration.
• Audit and Alert: If connected to a monitoring system, you can combine the instance ID (e.g., 594950814582177793) to establish alerts and quickly locate abnormalities.
• Password and Key Tiered Management: It is recommended to use key login for production environments. Passwords are only used as an emergency means and rotated regularly.

If you encounter problems such as inability to refresh instance status, password reset failure, or Web Terminal unable to open, please record the instance ID and contact technical support for troubleshooting.