-
Notifications
You must be signed in to change notification settings - Fork 10
DEM_Installation_Daemons
To start using the DEM Management Suite, start the daemons.
- start the DEM Endpoint Manager (DEM-EM) daemon if you want to remotely manage configuration of a given Target system.
- Start the DEM Discovery controller (DEM) to enable web-based or command-line-interface management for managing remote targets.
- Optionally start the DEM Host Auto Connect (DEM-AC) to enable Hosts to discovery their provisioned remote resources and auto-connect to each of those provisioned remote subsystems.
- Optionally start the DEM Monitor Utility (DEM-DM) to enable monitoring on each Host for updates to Discovery Log-pages and changes to provisioned resources.
Optional mechanism for In-band or out-of-band configuration of each Target.
Only needed if a systems administrator will be remotely managing remote NVMe resources.
Configure fabric interface(s) the Endpoint Manager will report to the DEM (Discovery Controller).
This is the fabric interface the DEM will use for NVMe-oF.
This is done via files ifcfg-like files under /etc/nvme/nvmeof-dem (file ‘config’ and ‘signature’ are reserved).
Example RDMA interface on IP-Address “192.168.22.1”. Note: The specification of a TRSVCID is an indication that the DEM should use this transport for Hosts to connect for retrieval of Discovery Log pages. The TRSVCID is only used by the DEM daemon. The TRSVCID in the example below is not used by the Endpoint Manager - TRSVCID used by Target drivers are assigned by administrator through DEM configuration.
#This is a comment
TRTYPE=rdma
ADRFAM=ipv4
TRADDR=192.168.22.1
TRSVCID=4422
Start Target Endpoint Manager specifying ‘management mode’
This is the mechanism the DEM will use to communicate to the DEM-EM
This is only used for configuration purposes.
Out-of-Band management mode specifying RESTful interfaces on port 22334
# dem-em -p 22334
In-Band management mode on rdma ipv4 address “192.168.22.1” The Service ID is definable, but cannot be “4420”
# dem-em -t rdma -f ipv4 -a 192.168.22.1 -s 4423
Starting either in-band or out-of-band DEM-EM reports enumerated devices and interfaces
If run in debug-mode the DEM-EM will not start as a daemon, and all output will be sent to stdout rather than to /var/log/…
Configure fabric interface(s) for Host communication to the DEM Discovery Controller.
This is the fabric interface DEM listens on for Hosts to connect and request Discovery Log Pages.
This is done via ifcfg-like files under /etc/nvme/nvmeof-dem (file ‘config’ and ‘signature’ are reserved).
Example RDMA interface on IP-Address “192.168.22.2”. If the TRSVCID is not present in a given configuration file, the default TRSVCID for that interface is the pre-assigned NVMe-oF ID "4420".
Note: TRSVCID “4420” is the pre-assigned NVMe-oF ID and may only be used if the DEM Discovery Controller is not co-located with an NVMe-oF Target driver.
#This is a comment
TRTYPE=rdma
ADRFAM=ipv4
TRADDR=192.168.22.2
TRSVCID=4422
Starting DEM Discovery Controller specifying RESTful interfaces on a port.
Default HTTP port is 22345
# dem –p <HTTP port id>
Starting either in-band or out-of-band DEM reports enumerated devices and interfaces
If run in debug-mode the DEM will not start as a daemon, and all output will be sent to stdout rather than to /var/log/…
Optional component to enable Hosts to connect to DEM and automatically connect to provisioned NVMe resources as defined by Discovery Log Pages
Starting Auto Connect to address of the Discovery Controller
# dem-ac -t rdma -f ipv4 -a 192.168.22.2 -s 4422
Starting either in-band or out-of-band DEM-AC reports enumerated devices and interfaces
If run in debug-mode the DEM-AC will not start as a daemon, and all output will be sent to stdout rather than to /var/log/…
Optional component to enable Hosts to monitor DEM-DM and report provisioned NVMe resources as defined by Discovery Log Pages
Starting Monitor and point it to the address of the DEM Discovery Controller
# dem-dm -t rdma -f ipv4 -a 192.168.22.2 -s 4422