You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/cumulus-netq-51/Installation-Management/Backup-and-Restore-NetQ.md
+42-6Lines changed: 42 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,16 @@ The following sections describe how to back up and restore your NetQ data and VM
9
9
10
10
{{%notice note%}}
11
11
- You must run backup and restore scripts with sudo privileges.
12
-
- NetQ does not retain custom-signed certificates during the backup and restore process. If your deployment uses a custom-signed certificate, you must {{<linktitle="Install a Custom Signed Certificate"text="reconfigure the certificate">}} after you restore it on a new NetQ VM.
13
-
- The backup and restore process does not retain several configurations necessary for the Grafana integration, including switch TLS certificates, authentication tokens (vm-tokens), OpenTelemetry configurations, and external time-series database configurations. After reinstalling NetQ, you must {{<linktitle="Integrate NetQ with Grafana"text="reconfigure these components">}}. Grafana will not display data from previous NetQ versions.
12
+
- NetQ does not retain custom-signed certificates during the backup and restore process. If your deployment uses a custom-signed certificate, you must {{<linktitle="Install a Custom Signed Certificate"text="reconfigure the certificate">}} after you restore it on a new NetQ VM.*This caveat does not apply to NVLink clusters.*
13
+
- The backup and restore process does not retain several configurations necessary for the Grafana integration, including switch TLS certificates, authentication tokens (vm-tokens), OpenTelemetry configurations, and external time-series database configurations. After reinstalling NetQ, you must {{<linktitle="Integrate NetQ with Grafana"text="reconfigure these components">}}. Grafana will not display data from previous NetQ versions.*This caveat does not apply to NVLink clusters.*
14
14
{{%/notice%}}
15
15
16
16
## Back Up Your NetQ Data
17
17
18
-
Follow the process below for your deployment type to back up your NetQ data:
18
+
Follow the process below for your deployment type to back up your NetQ data.
To restore your NetQ data, perform a {{<linktitle="Install the NetQ System"text="new NetQ VM installation">}} and follow the steps to restore your NetQ data when you run the `netq install` command. You will use the `restore` option, referencing the path where the backup file resides.
131
+
{{<tabs "TabID129" >}}
132
+
{{<tab "Other Deployments" >}}
133
+
134
+
To restore your NetQ data, perform a {{<linktitle="Install the NetQ System"text="new NetQ VM installation">}} and follow the steps to restore your NetQ data when you run the `netq install` command. You will use the `restore` option, referencing the path where the backup file resides.
135
+
136
+
{{</tab>}}
137
+
{{<tab "NVLink Clusters" >}}
138
+
139
+
1. Restore your data by running the {{<linktitle="nvl/#netq-nvl-cluster-restore"text="netq nvl cluster restore">}} command with the `drop-mongo-collections` option. This option prevents NetQ from re-installing duplicate data.
Copy file name to clipboardExpand all lines: content/cumulus-netq-51/Installation-Management/Install-NetQ/Install-NetQ-System.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ toc: 3
7
7
8
8
## NetQ for Ethernet
9
9
10
+
The following deployment models use NetQ to monitor Ethernet-only networks.
11
+
10
12
{{<tabs "TabID11" >}}
11
13
12
14
{{<tab "On-premises" >}}
@@ -23,6 +25,8 @@ toc: 3
23
25
24
26
## NetQ for NVLink
25
27
28
+
The following deployment model uses NetQ to monitor NVLink-only networks.
29
+
26
30
{{<tabs "TabID35" >}}
27
31
28
32
{{<tab "On-premises" >}}
@@ -38,14 +42,16 @@ toc: 3
38
42
39
43
## NetQ for Ethernet and NVLink
40
44
45
+
The following deployment models use NetQ to monitor networks that use both Ethernet and NVLink. NetQ 5.1 introduces a new option that lets you deploy NetQ on as many nodes as you wish to include in your server cluster. This deployment option is in beta and will require a fresh installation upon subsequent NetQ releases.
46
+
41
47
{{<tabs "TabID56" >}}
42
48
43
49
{{<tab "On-premises" >}}
44
50
45
51
| Server Arrangement | Hypervisor | Requirements & Installation |
46
52
| :--- | --- | :---: |
47
53
| High-availability scale cluster: three-nodes | KVM or VMware | {{<linktitle="Install NetQ for Ethernet and NVLink"text="Start install">}} |
48
-
| High-availability scale cluster: unlimited nodes (beta)| KVM or VMware | {{<linktitle="Install NetQ for Ethernet and NVLink (Beta)"text="Start install">}} |
54
+
| High-availability scale cluster: user-defined nodes | KVM or VMware | {{<linktitle="Install NetQ for Ethernet and NVLink (Beta)"text="Start install">}} |
Copy file name to clipboardExpand all lines: content/cumulus-netq-51/Installation-Management/Install-NetQ/Setup-NVLink-Cluster.md
-44Lines changed: 0 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,55 +242,11 @@ nvidia@netq-server:~$ vim /tmp/nvl-cluster-config.json
242
242
243
243
12. Run the installation command on your master node using the JSON configuration file that you created in the previous step. Specify the passwords for the read-write user and the read-only user in the `rw-password` and `ro-password` fields, respectively. The passwords must each include a minimum of eight characters.
<divclass=“noticestip”><p>If this step fails for any reason, run <code>netq bootstrap reset</code> and then try again.</p></div>
252
249
253
-
{{< /tab >}}
254
-
{{< tab "Restore Data and New Install">}}
255
-
<!--need to check this with QA-->
256
-
1. Add the `config-key` parameter to the JSON template from step 11 using the key created during the {{<linktitle="Back Up and Restore NetQ"text="backup process">}}. Edit the file with values for each attribute.
257
-
258
-
```
259
-
nvidia@netq-server:~$ vim /tmp/nvl-cluster-config.json
260
-
{
261
-
"version": "v2.0",
262
-
"interface": "<INPUT>",
263
-
"config-key": "<INPUT>",
264
-
"cluster-vip": "<INPUT>",
265
-
"servers": [
266
-
{
267
-
"ip": "<INPUT>"
268
-
"description": "<SERVER1>"
269
-
},
270
-
{
271
-
"ip": "<INPUT>"
272
-
"description": "<SERVER2>"
273
-
},
274
-
{
275
-
"ip": "<INPUT>"
276
-
"description": "<SERVER3>"
277
-
},
278
-
],
279
-
"storage-path": "/var/lib/longhorn",
280
-
"alertmanager_webhook_url": "<INPUT>"
281
-
}
282
-
```
283
-
284
-
2. Run the following command on your master node, using the JSON configuration file from the previous step. Include the restore option referencing the path where the backup file resides:
<divclass="notices tip"><p><ul><li>If this step fails for any reason, run <code>netq bootstrap reset</code> and then try again.</li><li>If you restore NetQ data to a server with an IP address that is different from the one used to back up the data, you must <ahref="https://docs.nvidia.com/networking-ethernet-software/cumulus-netq/Installation-Management/Install-NetQ/Install-NetQ-Agents/#configure-netq-agents">reconfigure the agents</a> on each switch as a final step.</li></ul></p></div>
291
-
{{< /tab >}}
292
-
{{< /tabs >}}
293
-
294
250
## Verify Installation Status
295
251
296
252
To view the status of the installation, use the `netq show status [verbose]` command. The following example shows a successful 3-node installation:
Copy file name to clipboardExpand all lines: content/cumulus-netq-51/Installation-Management/Install-NetQ/Setup-NVLink-Ethernet-Combined-Cluster-Beta.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ bookhidden: true
7
7
---
8
8
Follow these steps to set up and configure your VMs in a cluster of servers. First configure the VM on the master node, and then configure the VM on each additional node. NVIDIA recommends installing the virtual machines on different servers to increase redundancy in the event of a hardware failure.
9
9
{{<noticeinfo>}}
10
-
This deployment type is currently in beta, and installations with more than five nodes will not support upgrades to future NetQ versions.
10
+
This deployment type is currently in beta and will require a fresh installation upon subsequent NetQ releases.
0 commit comments