XorMon, open source under GPL v3, monitors Dell EMC storage: PowerMax and VMAX, PowerStore, Unity, XtremIO, VPLEX, Metro node, Data Domain, PowerScale (Isilon), ECS, PowerFlex, ME4/ME5 and SC series (Compellent). It collects data through each system's API, CLI or management server with a xormon user, and graphs IO, throughput, latency and capacity.
Which Dell EMC storage systems does XorMon monitor?
XorMon covers Dell EMC block, file, object and backup storage, from PowerMax, XtremIO, VPLEX and Metro node to PowerScale (Isilon), ECS and Data Domain, each with its own installation tab on this page; VNX, VNXe, CLARiiON and Celerra are the exceptions.
The storage monitoring page lists Dell EMC among the supported vendors, and each family is read through its own interface: REST API for XtremIO, PowerStore, PowerScale (Isilon), ECS and PowerFlex, Dell EMC Unisphere or the storage itself for PowerMax and VMAX, the Unisphere CLI for Unity and the CLI over SSH for Data Domain. The feature matrix marks performance and hardware event alerting for the supported Dell EMC families except ECS, and storage data is kept up to 3 years as daily averages.
Does XorMon monitor EMC VNX, VNXe, CLARiiON and Celerra?
Not yet: Dell EMC VNX, VNX file, VNXe, Celerra and CLARiiON CX4 are on the list of technologies not implemented in XorMon so far; their monitoring is supported by STOR2RRD, a legacy tool.
XorMon is the full-stack successor of STOR2RRD, and all new development goes into XorMon. Users can vote for missing device support, and both tools can run simultaneously on the same devices, with STOR2RRD device definitions exported and imported into XorMon.
XorMon reads XtremIO data through the REST API of the XMS management module, on port 443 (HTTPS), with a read-only xormon user.
The feature matrix marks IO, data throughput, latency and block size per pool, volume, host and host group, plus pool capacity and health status. XtremIO is one of the storage systems that provide real per-host performance statistics, rather than host data aggregated from volumes.
What does XorMon collect from PowerMax, VMAX and Data Domain?
On PowerMax and VMAX, XorMon graphs pools, tiers, service level objectives, volumes and storage groups, ports, hosts and directors; on Data Domain, it reads the CLI over SSH and graphs MTrees, DD Boost and replication.
PowerMax and VMAX data comes from Dell EMC Unisphere or from the storage itself on port 8443, with a monitoring user; both arrays provide real per-host statistics and are covered by Copy Services monitoring. Data Domain is read over SSH on port 22, and its MTree metrics include data, capacity and compression.
VPLEX 5 non storage UI neither VPLEXcli access
This kind of access requires only ssh access to VPLEX management host to get files with perf data.
This will miss in data then:
Host section
Host mapping (HOST vrs Volume relationship)
Host TOP
Health status
Capacity
VPLEX 6 access under vplexuser role
Prerequisites
Allow access from the XorMon host to the VPLEX on ports 22 & 443 (TCP).
Create user xormon on the VPLEX host under "users" group and exchange ssh-keys.
This will allow download perfromance data and some basic configuration.
Use vplexuser role on VPLEX 6.
You can also use user/password ssh credentials in XorMon UI instead of ssh-keys.
Create ssh keys if it does not exist yet in /home/xormon/.ssh/id_rsa (type enter instead of passphrase)
$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/xormon/.ssh/id_rsa):
...
New storage devices might require stronger key, use this one instead of above 'RSA'
$ ssh-keygen -t ecdsa -b 521 -N ""
Create xormon user via VPlexcli under admin priviliges
# ssh service@VPLEX01
service@VPLEX01:~> vplexcli
Trying ::1...
Connected to localhost.
Escape character is '^]'.
Enter User Name: admin
Password:
VPLEX6
User creation with role assigment
VPlexcli:/> user add -r vplexuser -u xormon
Enter admin password:
Enter password for xormon:
Confirm password for xormon:
Allow shell access
VPlexcli:/> cd /management-server/users/local/xormon/
VPlexcli:/management-server/users/local/xormon> set shell-access true
Enter admin password:
user rights
VPlexcli:/> ll /management-server/users/local/xormon
Name Value
------------ --------
role-name vplexuser
shell-access true
user-name xormon
VPLEX 6.2
Connect as user "admin" to the VPLEX-V6.2 Box, because user "service" wasn't able to create the "xormon" user under the vplexcli:
Under "admin" the creation was OK, but the next stop was here:
set shell-access true
>> Enter admin password:
>> set: Evaluation of <<set shell-access true>> failed.
>> cause: Failed to update value of 'shell-access'.
>> cause: Error committing shell-access.
Exit the "vplexcli" shell and entered the following commands:
grep xormon /etc/passwd
>> xormon:x:1002:100::/home/xormon:/bin/bash
su - xormon
>> You are required to change your password immediately (administrator enforced)
It forces me to change my password NOW...
Afterwards, you are able to create your own .ssh directory, and add XorMon PubKey:
mkdir .ssh
chmod 700 .ssh
cd .ssh
vi authorized_keys
Exchange ssh keys
$ ssh-copy-id xormon@vplex01
Test connection, you should login without typing of password:
$ ssh vplex01 -l xormon
xormon@VPLEX01:~> exit
You have to end up in shell! If you end up in VPLEX CLI then it is wrong, use above "set shell-access true" cmd.
UI access to https://vplex01 as xormon does not work
Allow access to the storage UI (via REST API) under admin priviliges on VPLEX 5
If you do want to allow it then it will work but without this data:
Host section
Host mapping (HOST vrs Volume relationship)
Host TOP
Health status
Capacity
VPLEX 6 apparently starts VPLEXcli automatically after log on.
This must be disabled to allow login only to operating system.
There is a way (perhaps commenting out starting VPLEXcli in .bash_profile or something like that), not sure here as for now.
Make sure that all monitors we use are running (collecting data), they are all default monitors and should run:
VPlexcli:/> ll /monitoring/directors/*/monitors/
/monitoring/directors/director-1-1-A/monitors:
Name Ownership Collecting Period Average Idle Bucket Bucket Bucket Bucket
-------------------------------------------------------------- --------- Data ------ Period For Min Max Width Count
-------------------------------------------------------------- --------- ---------- ------ ------- ----- ------ ------ ------ ------
director-1-1-A_PERPETUAL_vplex_sys_perf_mon_v19 true true 5s 4.97s 2s - - - 64
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR true true 1min 1min 33s - - - 64
/monitoring/directors/director-1-1-B/monitors:
Name Ownership Collecting Period Average Idle Bucket Bucket Bucket Bucket
------------------------------------------------ --------- Data ------ Period For Min Max Width Count
------------------------------------------------ --------- ---------- ------ ------- ---- ------ ------ ------ ------
director-1-1-B_PERPETUAL_vplex_sys_perf_mon_v19 true true 5s 5.05s 4s - - - 64
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR true true 1min 60s 33s - - - 64
...
If some do not running then use this procedure to enable it.
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI ➡ Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ EMC VPLEX
Run "Test" for configured device, it must show "OK"
Wait about 1 hour, then reload the web browser, you should see it in XorMon UI
Note: Dell EMC Metro Node 8.x+ does not support capacity data due to a change in its API, it will be re-implemented.
XorMon storage agent uses these EMC Metro node APIs:
Performance data via SSH: default Metro node data collectors available through SSH (port 22) : read only access
Configuration data via REST API: Metro node Element Manager API (port 443)
Note: for getting capacity data from the storage follow this docu
Prerequisites
Enable access from the XorMon host to the Dell EMC Metro node on ports 22 & 443 (TCP).
Create the xormon account to the first node of your MN cluster:
Switch to the root context with with this special command:
sudo /usr/sbin/service-maintenance-window -f
Create the xormon account with the useradd command:
SSH user access (select one of below methods during storage configuration in XorMon UI)
User/Password
SSH keys
Create SSH keys if it does not exist yet in /home/xormon/.ssh/id_rsa (type enter instead of passphrase)
$ ssh-keygen -t rsa -N ""
Generating public/private rsa key pair.
Enter file in which to save the key (/home/xormon/.ssh/id_rsa):
...
New storage devices might require stronger key, use this one instead of above 'RSA'
$ ssh-keygen -t ecdsa -b 521 -N ""
Assign password to the user
admin@MN01:~> su - xormon
Password:
Password change requested. Choose a new password.
Old Password:
New Password:
Reenter New Password:
Exchange ssh keys
$ ssh-copy-id xormon@mn01
Test connection, you should login without typing of password:
$ ssh mn01 -l xormon
xormon@MN01:~> exit
You have to end up in shell!
If you end up in Metro node CLI then it is wrong, use above "set shell-access true" cmd.
UI access to https://mn01 as xormon does not work
Dell EMC Metro node apparently starts VPLEXcli automatically after log on.
This must be disabled to allow login only to operating system.
There is a way (perhaps commenting out starting VPLEXcli in .bash_profile or something like that), not sure here as for now.
Make sure that all monitors we use are running (collecting data), they are all default monitors and should run:
VPlexcli:/> ll /monitoring/directors/*/monitors/
/monitoring/directors/director-1-1-A/monitors:
Name Ownership Collecting Period Average Idle Bucket Bucket Bucket Bucket
-------------------------------------------------------------- --------- Data ------ Period For Min Max Width Count
-------------------------------------------------------------- --------- ---------- ------ ------- ----- ------ ------ ------ ------
director-1-1-A_PERPETUAL_vplex_sys_perf_mon_v19 true true 5s 4.97s 2s - - - 64
director-1-1-A_VIRTUAL_VOLUMES_PERPETUAL_MONITOR true true 1min 1min 33s - - - 64
/monitoring/directors/director-1-1-B/monitors:
Name Ownership Collecting Period Average Idle Bucket Bucket Bucket Bucket
------------------------------------------------ --------- Data ------ Period For Min Max Width Count
------------------------------------------------ --------- ---------- ------ ------- ---- ------ ------ ------ ------
director-1-1-B_PERPETUAL_vplex_sys_perf_mon_v19 true true 5s 5.05s 4s - - - 64
director-1-1-B_VIRTUAL_VOLUMES_PERPETUAL_MONITOR true true 1min 60s 33s - - - 64
...
If some do not running then use this procedure to enable it.
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI ➡ Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC Metro node
Run "Test" for configured device, it must show "OK"
Wait about 1 hour, then reload the web browser, you should see it in XorMon UI
The product uses storage CLI connected via Dell EMC Unisphere UEM CLI client to get all necessary data.
Prerequisites
Dell EMC Unity Unisphere UEM CLI download https://www.dell.com/support/home/
Download binaries is available for signed users ONLY. BTW no active support is needed.
Setting security level under root user:
Note: The path has changed in recent UnisphereCLI, at least for UnisphereCLI-Linux-64-x86-en_US-5.2.1.1730628-1.x86_64.rpm:
The installation is now under "/opt/dellemc", change bellow cmds accordingly
You can even use "medium" level, then you have to accept and store certificate at the first connection.
under root:
# /opt/emc/uemcli/bin/setlevel.sh medium
Setting medium verifying level.....
under xormon user:
# su - xormon
$ uemcli -d 192.168.1.1 -u Local/admin -p "XXXXXX" /user/account show
Remote certificate:
Issuer: CN=EMC-Unity
Subject: CN=EMC-Unity
Valid from: 2016-07-15 09:54:57 Z
Valid to: 2019-07-15 09:54:57 Z
Serial: 0094aea927526b466e
Id: 2595584890
Would you like to:
[1] Accept the certificate for this session
[2] Reject the certificate
[3] Accept and store
Please input your selection (The default selection is [1]): 3
Storage system address: 192.168.1.1
Storage system port: 443
HTTPS connection
1: ID = user_admin
Name = admin
Role = administrator
Type = local
If the option "[3] Accept and store" is missing
$ uemcli -d 192.168.1.1 -u Local/admin -p "XXXXXX" /user/account show
Remote certificate:
Issuer: CN=EMC-Unity
Subject: CN=EMC-Unity
Valid from: 2016-07-15 09:54:57 Z
Valid to: 2019-07-15 09:54:57 Z
Serial: 0094aea927526b466e
Id: 2595584890
Would you like to:
[1] Accept the certificate for this session
[2] Reject the certificate
Please input your selection (The default selection is [1]):
It's necessary to set SecurityLevel to low
There should be file /etc/uemcli_security.conf readable for root probably with "medium" security.
SecurityLevel = medium
Changing to low level should resolve it.
SecurityLevel = low
Then option "[3] Accept and store" should appear in the selection.
Storage connectivity
Allow access from the XorMon host to the Unity storage on port 443 (https)
create user xormon under operator role on the storage.
You might skip it and use already existing account with minimal rights.
Do not use shell special characters like #!?|$*[]\{}`"'& in the password, use ;:.+-%@ instead.
Cmd returns "Error code: 0x6000068" if you do not pass them.
Do not use directly /opt/emc/uemcli/bin/uemcli, use always /usr/bin/uemcli.
If the package was converted with "alien", and after installation "/usr/bin/uemcli" - which should be a softlink - could not be found, you should create it manually
$ uemcli -d 192.168.1.1 -u Local/admin -p "XXXXXX" /user/account show
Storage system address: 192.168.1.1
Storage system port: 443
HTTPS connection
1: ID = user_admin
Name = admin
Role = administrator
Type = local
...
$ uemcli -d 192.168.1.1 -u Local/admin -p "XXXXXX" /user/account create -name xormon -role operator -type local -passwd "Test2test_"
Storage system address: 192.168.1.1
Storage system port: 443
HTTPS connection
ID = user_xormon
Operation completed successfully.
Test storage connection for xormon account:
$ /usr/bin/uemcli -d 192.168.1.1 -u Local/xormon -p "XXXXXX" /sys/general show -detail
Storage system address: 192.168.1.1
Storage system port: 443
HTTPS connection
1: System name = EMC-Unity
Model = UnityVSA
Platform type = EMC Storage System
System UUID = 420FFE1D-0234-FD02-976E-9217DC6135ED
License activation key = ELMEUV0716HN0K
Product serial number = VIRT162859DQXZ
Health state = OK (5)
Health details = "The system is operating normally."
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI ➡ Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ EMC XtremIO
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
VNX monitoring is supported by STOR2RRD, a legacy tool, only so far.
Do you want to let us know your priorities? Vote for your missing features and device support. More votes, bigger priority for us. List of not supported technologies yet
VNX file monitoring is supported by STOR2RRD, a legacy tool, only so far.
Do you want to let us know your priorities? Vote for your missing features and device support. More votes, bigger priority for us. List of not supported technologies yet
VNXe monitoring is supported by STOR2RRD, a legacy tool, only so far.
Do you want to let us know your priorities? Vote for your missing features and device support. More votes, bigger priority for us. List of not supported technologies yet
Source of performance data are not storage devices themself but REST API of one of these:
Dell Storage Enterprise Manager
Dell Storage Manager Data Collector
Connection directly to the storage will not work, use one of above options.
User rights options
Create user xormon under admin role or use already existing admin account.
Admin rights give you visibility of the whole storage include items not being under any folder and system subsystems like:
Node (controller): CPU, IO, data, response time
Port: IO, data, response time
Create user xormon under Reporter role and assign him rights to all or specific:
volume folders
server folders
disk folders
In this case will be reported utilization only for assigned folders and their items.
You can whenever switch from Reporter access to admin one and vice versa.
Note: the latest DSM and Data Collector versions enabled getting all data via Reporter role.
In both cases you have to create a user on all storage and on Enterprise Manager/Data collector where you have to attach those storage under that Reporter or admin account.
Storage connectivity
Install the Enterprise Manager or DSM Data Collector and attach there your Compellent boxes.
Create user xormon on the Enterprise Manager or DSM Data Collector under admin role.
Unfortunatelly admin role is only the role which can get all performance data from the storage.
If you use web tool Unisphere central for SC series then registration there is not enough.
You have to register storage for user in Enterprise Manager or DSM Data Collector.
Allow access from the XorMon host to the Enterprise Manager on port 3033 (HTTPS).
Set "Report gathering settings" of IO usage to 5 minutes.
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI ➡ Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell SC series
On the picture you can see 3 compellent storage in the Enterprise Manager.
Configure every storage you want to monitor, use same storage name alias as you see in the Enterprise Manager.
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
Storage agent uses either the Dell EMC Unisphere as data source, or the storage itself (that method works at least on 5978_711/0365 storage firmware and newer, most probaly even on olders)
Dell EMC Unisphere 1.6.x, 8.x, 9.x and 10.x are supported.
Read why TDEVs are not monitored.
Prerequisites
Allow access from the XorMon host to the EMC Unisphere or to the storage itself depends on mode you use on port 8443 (TCP).
EMC Configuration
Unisphere (scenario 1)
Create user xormon under "PerfMonitor" role on Unisphere (example uses 'stor2rrd' user but use 'xormon' preferable).
Allow statistics logging on the EMC Unisphere
UI ➡ Performance ➡ Settings ➡ System Registrations ➡ Diagnostics ➡ On (Diagnostics interval 5 minutes)
EMC Unisphere 1.6
EMC Unisphere 8+
Set sample rate to 5 minutes:
Direct storage attachment (scenario 2)
Connect on one of both PMAX e-management port and on the wheel on the top right corner
Click “users and groups”, then “local users”, and then the “create” button
Enter: The account name, description and Password 2 times (warning: both PMAX and XorMon have forbidden special characters and they are not the same)
Choose the “perfmonitor” role
Keep right access as “read only”
XorMon storage configuration
Add storage into configuration from the UI, fill in Symmetrix ID for both scenarios
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC VMAX
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
Storage agent uses EMC Data Domain CLI accessed via ssh to get all necessary data from the storage.
EMC DataDomain firmware versions 6.x and 7.x are supported.
EMC DataDomain firmware versions 5.5 is supported only in STOR2RRD.
EMC DataDomain 6.0.2.50+ and 6.1.2.40+ (6.2 is not affected) do not provide disk stats community.emc.com/docs/DOC-78887
Prerequisites
Allow access from the XorMon host to the EMC storage on port 22 (TCP).
Create user xormon under user role on the storage (example uses 'stor2rrd' user but use 'xormon' preferable)
$ ssh <data domain host> -l xormon
xormon@data_domain_host> adminaccess add ssh-keys
Enter the key and then press Control-D, or press Control-C to cancel.
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDPpQlm0Z/x1X4txd2GgZgvg1Fm7QHeusQ6LqBp/Sb1doAoiDmXErk+lNY27aJAqb4YiGnqejioqCJ9N93NiKpffxH+L3
Test connection:
$ ssh <data domain host> -l xormon
EMC Data Domain Virtual Edition
Welcome to Data Domain OS 6.1.0.11-571028
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC DataDomain
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
DD refuses some ssh sessions, you can find in XorMon log (~/xormon-ng/server-nest/log/datadomain) this:
Error: Unable to connect to remote machine (dd01) : No such file or directory
Error: Error command: ssh login failed unable to load Perl module IO::Pty: Can't locate IO/Pty.pm ...
Increase DataDomain parameter login-max-active, xormon ssh sessions are in conjuction with normal backup sessions.
sysadmin@dd(active:0)# adminaccess option show login-max-active.
Adminaccess option "login-max-active" set to "150".
sysadmin@dd(active:0)# adminaccess option set login-max-active 500
Adminaccess option "login-max-active" set to "500".
Isilon v7.x, v8.x and v9.x firmwares are supported.
When you use Isilon v9.x then just use one Management IP Address from the Cluster (do not use direct Node's IPs).
The product uses EMC Isilon REST API interface natively provided by the storage to get all necessary data.
Storage connectivity
Allow access from the XorMon host to the EMC storage on port 8080.
Create user xormon on the storage with new read-only role called xormon.
Add storage into configuration from the UI:
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC Isilon
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
The product uses EMC ME4 SMI-S and WBI API interfaces natively provided by the storage.
Note: storage firmware GT280R010-01 does not provide data via SMI-S (up to GT280R009-02 it is fine), it is a confirmed issue in the storage firmware (SR #14853424). Upgrade to GT280R011-01 or use WBI access method.
Storage connectivity
Allow access from the XorMon host to the storage on ports 80 (WBI) and 5988 (SMI-S).
If you use https and secure SMI-S then test ports 443 and 5989 instead.
If you use storage cmd line configuration like in examples below (you can use the storage UI instead) then port 22 (ssh) must be open.
Make sure that secure SMI-S (port 5989) and WBI HTTPS (port 443) protocols are enabled on the storage
CMD line:
$ ssh -l manage <storage_hostname>
# show protocols
Service and Security Protocols
------------------------------
Web Browser Interface (HTTP): Enabled
Secure Web Browser Interface (HTTPS): Enabled
Command Line Interface (Telnet): Disabled
Secure Command Line Interface (SSH): Enabled
Storage Management Initiative Specification (SMI-S): Enabled
Unsecure Storage Management Initiative Specification (SMI-S 5988): Disabled
...
If secure SMI-S or WBI HTTPS are not enabled:
# set protocols smis enabled
# set protocols https enabled
UI:
Create user xormon on the storage with monitor and standard roles, allow SMI-S and WBI.
CMD line method:
Adjust password to your preferred one from used Test1234.
$ ssh -l manage <storage_hostname>
# create user interfaces smis,wbi locale English password Test1234 roles monitor,standard xormon
UI:
(example uses 'stor2rrd' user but use 'xormon' preferable)
Note for newer firmwares role "standard" is necessary for WBI access.
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI: Settings icon ➡ Device ➡Storage ➡ New ➡ Vendor:device ➡ Dell EMC ➡ PowerVault ME4 ➡ SMI-S
If you set https in above storage properties then this must be enabled on the storage:
Do not use shell special characters like @:;#!?|$*[]\{}`"'& in the password, use rather .+-=_% instead.
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
Data is obtained from the EMC ECS Rest API, from VDC nodes.
Allow access from the XorMon host to each EMC ECS VDC node on port 4443
Create Storage Management user "xormon" with System Monitor role on each monitored VDC.
Add storage into configuration from the UI:
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC : Elastic Cloud Storage
The addition of a VDC to ECS configuration is intended as choosing specific VDC you want to display in the XorMon UI.
To monitor your chosen VDC, just set one or two nodes which are management EndPoint for a given VDC.
No need to add every node in VDC
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
The product uses REST API natively provided by EMC PowerStore storage.
Note the issue with PowerStore firmware 3.0.0.1, upgrade to 3.2.1.0.
Storage connectivity
Allow access from the XorMon host to the EMC storage on port 443 (https)
Add storage to the configuration:
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC : PowerFlex
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
The product uses storage WBI API interfaces natively provided by the storage.
WBI access must be used on new storage models which do not support SMI-S protocol.
Storage connectivity
Allow access from the XorMon host to the storage on ports 443.
Make sure that secure and WBI HTTPS (port 443) protocol is enabled on the storage
CMD line:
$ ssh -l manage <storage_hostname>
# show protocols
Service and Security Protocols
------------------------------
...
Secure Web Browser Interface (HTTPS): Enabled
...
If secure WBI HTTPS is not enabled:
# set protocols https enabled
UI:
Create user xormon on the storage with monitor and standard roles, allow WBI.
CMD line method:
Adjust password to your preferred one from used Test1234.
$ ssh -l manage <storage_hostname>
# create user interfaces wbi locale English password Test1234 roles monitor,standard xormon
UI:
(example uses 'stor2rrd' user but use 'xormon' preferable)
Note for some newer firmwares role "standard" is necessary for WBI access.
XorMon storage configuration
Add storage into configuration from the UI:
XorMon UI: Settings icon ➡ Device ➡ Storage ➡ New ➡ Vendor:device ➡ Dell EMC ➡ PowerVault ME4 ➡ WBI
If you set https in above storage properties then this must be enabled on the storage:
$ ssh -l manage <storage_hostname>
# show protocols
...
Secure Web Browser Interface (HTTPS): Enabled
...
If you use http then this:
Web Browser Interface (HTTP): Enabled
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