9 pvenode - Proxmox VE Node Management
14 include::pvenode.1-synopsis.adoc[]
20 Proxmox Node Management
21 -----------------------
27 The {PVE} node management tool (`pvenode`) allows to control node specific
28 settings and resources.
30 Currently `pvenode` allows to set a node's description and to manage
31 the node's SSL certificates used for the API and the web GUI through `pveproxy`.
34 include::output-format.adoc[]
39 .Install an externally provided certificate
41 `pvenode cert set certificate.crt certificate.key -force`
43 Both files need to be PEM encoded. `certificate.key` contains the private key
44 and `certificate.crt` contains the whole certificate chain.
46 .Setup ACME account and order a certificate for local node.
49 pvenode acme account register default mail@example.invalid
50 pvenode config set --acme domains=example.invalid
51 pvenode acme cert order
52 systemctl restart pveproxy
59 Wake-on-LAN (WoL) allows to switch on a sleeping computer in the network by
60 sending a magic packet. At least one NIC must support this feature and the
61 respective option needs to be enabled in the computers firmware (BIOS/UEFI)
62 configuration. The option name can vary from 'Enable Wake-on-Lan' to
63 'Power On By PCIE Device', check your motherboards vendor manual, if unsure.
64 `ethtool` can be used to check the WoL configuration of `<interface>` by
68 ethtool <interface> | grep Wake-on
71 `pvenode` allows to wake sleeping members of a cluster via WoL using the
75 pvenode wakeonlan <node>
78 This broadcasts the WoL magic packet on UDP port 9, containing the MAC address
79 of `<node>` obtained from the `wakeonlan` property. The node specific
80 `wakeonlan` property can be set by the following command:
83 pvenode config set -wakeonlan XX:XX:XX:XX:XX:XX
86 // TODO: extend and improve chapter!
89 include::pve-copyright.adoc[]