Physical/Cloud Server List Guide

Learn how to check and filter the inventory of all servers (Physical IDC servers and Public Cloud VMs) managed on the GIIP platform.

🏢 Go to Server List →

📋 Overview

The Server List screen provides a unified view of all your computing assets. Here, you can check the operating status of each server in real-time, search for necessary assets quickly, and navigate to detailed pages.

🔍 Key Features & Screen Composition

1. Integrated Filters & Search

• Project Filter: View only servers belonging to a specific project.
• Status Filter: Filtering is possible by Running, Stopped, Warning, and Unknown statuses.
• Search Bar: Search immediately by Hostname or IP address.

2. Agent Status (Agent Icon)

Intuitively grasp agent connection status through icon colors in the server list.

• 🟢 Green: Normal connection and metric collection in progress.
• 🟡 Yellow: Latency detected (unstable network).
• 🔴 Red: Connection lost (Agent restart required).

3. Asset Attribute Summary

Instantly check core specifications such as OS version, number of CPU cores, and Uptime in each row.

🛠️ Action Bar

• Bulk Execution: Select multiple servers and click the [Execute Command] button at the top to update packages or restart services simultaneously.
• Excel Download: Export the currently filtered server list to a CSV or Excel file.

💡 Tips

• Using Tags: Assign tags like Web, DB, or Staging to servers to categorize them much faster by purpose in the list.

API Reference

For detailed API specifications of this feature, refer to the separate guide.

📘 Infrastructure Management API Guide

Troubleshooting

Symptom	Cause	Solution
Server icon appears 🔴 red	Agent connection lost	Restart the agent on the affected server
Server icon appears 🟡 yellow	Latency due to an unstable network	Check the network status and re-check after a moment
The server you are looking for is not in the list	A Project/Status filter or search term is applied	Reset the filters or search by Hostname/IP address
Bulk commands are not applied to some servers	The agent on the target server is disconnected	Select only servers with a 🟢 green agent icon and run again

🤖 How to Register an AI Agent as an lsvr

This section is a complete, ready-to-execute procedure so that an AI agent can register itself into this server list (lsvr) using only this document. Copy and run the commands below as-is — no additional judgment or research is required.

Prerequisites

• You must have the SK (Secret Key) for the target csn (project). Registration is impossible without it — obtain/confirm it first at /svclist (project settings screen, requires login). Issuing the SK itself is out of scope for this guide; see the Agent Registration & Queue API Specification for details.

Execute — curl

curl -X POST "https://giipfaw.azurewebsites.net/api/giipApiSk2" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-urlencode "text=AgentAutoRegister hostname jsondata" \
  --data-urlencode "jsondata={\"hostname\":\"<unique hostname of the server>\",\"os\":\"<OS description>\",\"agent_version\":\"<version>\"}" \
  --data-urlencode "token=<SK>"

Execute — PowerShell

$jsonData = '{"hostname": "<unique hostname of the server>", "os": "<OS description>", "agent_version": "<version>"}'
$form = New-Object System.Collections.Specialized.NameValueCollection
$form.Add('text', 'AgentAutoRegister hostname jsondata')
$form.Add('token', '<SK>')
$form.Add('jsondata', $jsonData)
$wc = New-Object System.Net.WebClient
$wc.Encoding = [System.Text.Encoding]::UTF8
$resp = $wc.UploadValues('https://giipfaw.azurewebsites.net/api/giipApiSk2', 'POST', $form)
[System.Text.Encoding]::UTF8.GetString($resp)

Replace <unique hostname of the server>, <OS description>, <version>, and <SK> with actual values. hostname is required and must be unique within this csn.

Interpreting the Response

The HTTP status is always 200, so you must judge success solely from data[0].RstVal in the response JSON.

RstVal	Meaning	Example response
200 (new)	Registered as a new server, action: "new"	{"data":[{"Proc_MSG":"200|Server auto-registered successfully","lssn":71290,"action":"new","RstVal":200,"RstMsg":"Server auto-registered successfully"}]}
200 (existing)	Existing hostname → treated as a heartbeat update, action: "update"	{"data":[{"Proc_MSG":"200|Server updated successfully (heartbeat)","lssn":71290,"action":"update","RstVal":200,"RstMsg":"Server updated successfully (heartbeat)"}]}
400	hostname missing	{"data":[{"Proc_MSG":"400|Hostname required","RstVal":400,"RstMsg":"Hostname required"}]}
401	Invalid SK	{"data":[{"Proc_MSG":"401|Unauthorized - Invalid SK","RstVal":401,"RstMsg":"Unauthorized - Invalid Secret Key"}]}

On success, the lssn in the response is this server's unique identifier — you can use it afterward to call other giip APIs (e.g., queue polling) for this server.

Idempotent (safe to call repeatedly)

Calling the same request (same hostname, same SK) repeatedly is safe — the first call creates a new record (INSERT), and every subsequent call is treated as a heartbeat (UPDATE, refreshing the last-checked timestamp). You can reuse this same call as a periodic health check/heartbeat.

Optional Fields (for a richer inventory display)

You may add the following fields to jsondata (all optional; registration succeeds without them):

Field	Type	Description
os	string	OS description
kernel	string	Kernel version
cpu	string	CPU model name
cpu_cores	number	Number of CPU cores
memory_gb	number	Memory (GB)
disk_gb	number	Disk (GB)
agent_version	string	Agent/client version string
ipv4_global	string	Public IPv4
ipv4_local	string	Private IPv4
network	array	[{"name":"eth0","ipv4":"...","mac":"..."}]
software	array	[{"name":"nginx","version":"1.18.0","vendor":"Ubuntu","type":"DEB"}]
services	array	[{"name":"nginx","status":"running","start_type":"enabled","port":80}]

Agent-Type Display & Naming Rules (Self-Registration Convention)

lsvrlist now shows more than just the physical giipAgent — it displays several agent types together. When an AI self-registers using only this document, following the convention below makes it possible to read, from hostname and agent_version alone, "which machine · which tool (model/version) · in which run mode" is running.

Agent types (3)

Type	Applies to	Example agent_version
giipAgentWin	Windows physical/VM agent	giipAgentWin 5.3.1
giipAgentLinux	Linux physical/VM agent	giipAgentLinux 2.4.0
AI	AI coding/work agent (Claude Code, GPT, etc.)	claude-opus-4-8 (model ID)

hostname naming rule — <machine>-<tool-slug>[-<run-mode>]

• machine: the actual host/PC name (e.g. Lowy-DP01)
• tool-slug: a lowercase-hyphen slug identifying the agent (e.g. claude-code, giipagentwin, gissue-hourly-scheduler)
• run-mode (optional): console (persistent console session) · scheduler (cron/scheduler-driven) · service (OS service/daemon)
• Observed examples: Lowy-DP01-claude-code (AI running in console), Lowy-DP01-gissue-hourly-scheduler (AI running as a scheduler)

Recommended "model - version - run mode" notation per type

Item	giipAgentWin / giipAgentLinux	AI
agent_version	"<type> <version>" (e.g. giipAgentWin 5.3.1)	model ID (e.g. claude-opus-4-8, gpt-5)
os	actual OS (e.g. Windows Server 2022, Ubuntu 22.04)	host OS + tool (e.g. Windows 10 / Claude Code)
run mode	hostname suffix (e.g. -service)	hostname suffix (e.g. -console, -scheduler)

Registering per this convention lets each row's type, model/version, and run mode be read from hostname and agent_version alone — e.g. AI · claude-opus-4-8 · scheduler, giipAgentWin · 5.3.1 · service.

AI self-registration example (Claude Code running as a scheduler)

{"hostname":"Lowy-DP01-claude-code-scheduler","os":"Windows 10 / Claude Code","agent_version":"claude-opus-4-8"}

After registering, search for the hostname you just registered on the 🏢 Server List page — it will appear as a new lsvr.

For the full flow (register → poll queue → report result), see the Agent Registration & Queue API Specification.

---

Version: 1.1 Last Updated: 2026-09-10 Source: giipv3/public/help/lsvrlist.en.md