Inspur AS monitoring

XorMon, open source under GPL v3, monitors Inspur AS storage arrays over SSH on port 22, reading data through the SVC CLI with a dedicated xormon user on the storage. It tracks capacity per storage total, pool and tier, including snapshot, deduplication and compressed capacity, and monitors copy services with alerts when anything goes wrong.

Which Inspur systems does XorMon monitor?

XorMon monitors Inspur AS storage arrays; the storage monitoring list names the AS5500, AS5300, AS2600 and AS2200 series.

The capacity monitoring and Copy Services monitoring pages name the AS5600, AS5500, AS2600 and AS2200. Inspur AS is in the full list of supported storage systems on the storage monitoring page.

Sources: Storage monitoring, updated 2026-11-06, Capacity monitoring, updated 2026-11-05, and Copy Services monitoring, updated 2026-10-13.

What does XorMon monitor on Inspur AS storage?

On Inspur AS, XorMon tracks capacity per storage total, pool and tier, and monitors the status of copy services, with alerts when anything goes wrong.

Capacity monitoring covers formatted, raw, replication, snapshot, virtual, deduplication, compressed and spare capacity for the storage total, each storage pool and each tier. It uses smart trending graphs, a basis for capacity planning, and the same view exists for IBM Storwize, SVC and FlashSystem and for Lenovo V Series.

Sources: Capacity monitoring, Capacity planning and Glossary, all updated 2026-11-05, and Copy Services monitoring, updated 2026-10-13.

How does XorMon connect to Inspur AS storage?

XorMon connects from the XorMon host to the Inspur AS storage over SSH on port 22 and reads the data through the SVC CLI, with a dedicated xormon user that logs in with a password or an SSH key.

The dedicated user follows the IBM FlashSystem user roles page.

Sources: installation steps below, updated 2026-11-07, XorMon deployment, and IBM FlashSystem user roles, updated 2026-05-04.

Key points

Monitors Inspur AS storage arrays over SSH on port 22 through the SVC CLI.
Dedicated xormon user on the storage, with a password or an SSH key.
Capacity per storage total, pool and tier, with smart trending graphs.
Copy services status monitoring, with alerts when anything goes wrong.
Open source license (GPL v3).

Installation and configuration for Inspur

Prerequisites

Allow access from the XorMon host to the Inspur AS storage on port 22 (ssh).

Storage access

There are 2 possibilities how to connect the storage:

Use user/password
Create new user "xormon" on the storage

Storage firmware 8.3.1.2+: use "Monitor" role

$ ssh superuser@<storage control enclosure IP address> "svctask mkuser -name xormon -usergrp "Monitor"

Storage firmware 8+ up to 8.3.1.2: use "Restricted Administrator"

$ ssh superuser@<storage control enclosure IP address> "svctask mkuser -name xormon -usergrp RestrictedAdmin"

Older firmwares: use "Administrator" role.
It is the lowest role which allows retrieve of statistics data from the storage. Read this for explanation.
```
$ ssh superuser@<storage control enclosure IP address> "svctask mkuser -name xormon -usergrp Administrator"
```

SSH-keys

Create SSH-keys on XorMon host under xormon user if do not exist yet.
Type enter instead of passphrase

# su - xormon
$ ls -l ~/.ssh/id_rsa.pub
$ ssh-keygen -t rsa -N ""
  Generating public/private rsa key pair.
  Enter file in which to save the key (/home/xormon/.ssh/id_rsa):
  ...
$ ls -l ~/.ssh/id_rsa.pub
  -rw-r--r-- 1 xormon xormon 382 Jun  1 12:47 /home/xormon/.ssh/id_rsa.pub

You might need to add this into your SSH cfg in case of rsa using on OpenSSH 8.8+ especially in case ssh connection fails with: "no matching host key type found. Their offer: ssh-rsa"

vi ~/.ssh/config
Host *
    HostKeyAlgorithms=+ssh-rsa
    PubkeyAcceptedAlgorithms=+ssh-rsa

New storage devices might require stronger key, use this one instead of above 'RSA'

$ ssh-keygen -t ecdsa -b 521 -N ""

Copy ssh-key into the storage under storage superuser
In case of IBM Storwize V7000 Unified use one of "Control Enclosure" IPs (definitely not "File Module" IP).
Detailed description of IBM Storwize V7000 Unified.
```
$ scp ~/.ssh/id_rsa.pub superuser@<storage control enclosure IP address>:/tmp/123tmp
```

Create new user "xormon" on the storage

Storage firmware 8.3.1.2+: use "Monitor" role

$ ssh superuser@<storage control enclosure IP address> "svctask mkuser -name xormon -usergrp Monitor -keyfile /tmp/123tmp"

Storage firmware 8+ up to 8.3.1.2: use "Restricted Administrator"

$ ssh superuser@<storage control enclosure IP address> "svctask mkuser -name xormon -usergrp RestrictedAdmin -keyfile /tmp/123tmp"

Older firmwares: use "Administrator" role.
It is the lowest role which allows retrieve of statistics data from the storage. Read this for explanation.
```
$ ssh superuser@<storage control enclosure IP address> "svctask mkuser -name xormon -usergrp Administrator -keyfile /tmp/123tmp"  
```

If xormon user already exists on the storage then assign him new ssh-keys:

$ ssh superuser@<storage control enclosure IP address> "svctask chuser -keyfile /tmp/123tmp xormon"

Check if that works:

$ ssh -i ~/.ssh/id_rsa xormon@<storage control enclosure IP address> "svcinfo lssystem"
  id 00000100C0906BAA
  name SVC
  location local
  partnership
  bandwidth
  ...

XorMon storage configuration

Add storage into configuration from the UI:
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Inspur AS
Run "Test" for configured storage device, it must show "OK"
Wait about 1 hour, then reload the web browser, you should see it in XorMon UI

Troubleshooting

Storwize 8.5.0+ and support for multi-factor user authentication (REMOTE account usage)
There is a bug in Storwize code which does not allow to use REMOTE account for xormon ssh access.
Upgrade to Inspur AS code versions 8.5.0.10 (Q3-Q4 2023) or use LOCAL account

The full list of supported storage systems is on one page.

Dernière mise à jour : 2026-11-07