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: docs/administration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,26 +1,26 @@
1
1
---
2
-
title: "Collecting SNMPWALK Output"
2
+
title: "Collecting SNMP Walk Output"
3
3
sidebar_position: 4
4
4
---
5
5
6
-
You can collect SNMP walk's output for a network device or a PDU right from the GUI, and can send the output to us for further troubleshooting or for adding a specific device into discovery.
6
+
You can collect SNMP walk output for a network device or PDU right from the GUI. Then, you can send the output to us for further troubleshooting or to add a specific device to discovery.
From the Appliance Manager, go to **Application > Generate SNMP Output**.
11
11
12
-
**Go to:** Application > Generate SNMPWALK output
12
+
Add your target switch or other SNMP target device info, click **Submit**, and please be patient as it might take a few minutes. Please send us the file that is generated.
13
13
14
-
Add your target switch \[or other SNMP target device\] info, click generate, and please be patient as it might take few minutes. Please send us the file that is generated.
14
+
15
15
16
-
If there is an issue, the network is not reachable, or if you simply prefer using the terminal, you can alternatively run the following from any machine which has 'snmpwalk' installed:
16
+
If there is an issue, the network is not reachable, or you simply prefer using the terminal, you can instead run the following from any machine that has 'snmpwalk' installed:
17
17
18
18
```
19
19
snmpbulkwalk -Cc -ObentU -v2c -c COMMUNITY DEVICE > output_file_name
20
20
snmpbulkwalk -ObentU -v 2c -c COMMUNITY DEVICE .1.3.6.1.4.1 >> output_file_name
21
21
```
22
22
23
-
Also, the current setup has a bug for v3, so please use following for any system using SNMP v3:
23
+
Also, the current setup has a bug for v3, so please use the following for any system using SNMP v3:
24
24
25
25
```
26
26
snmpbulkwalk -Cc -ObentU -v 3 -u user_name -l authNoPriv -a MD5 -A auth_pass DEVICE > output_file_name
title: "Enable or Disable TLS versions from Appliance Manager"
2
+
title: "Enable or Disable TLS Versions from Appliance Manager"
3
3
sidebar_position: 8
4
4
---
5
5
6
-
# Disabling or Enabling TLS versions from the Appliance Manager
6
+
# Disabling or Enabling TLS Versions From the Appliance Manager
7
7
8
8
Device42 allows you to restrict TLS versions for Appliance Manager Access. The radio buttons shown below control this feature.
9
9
10
10
:::note
11
-
The appliance manager now defaults to **Enable TLS v1.2 only**. You an change the TLS settings in the appliance manager to **Enable TLS v.1.1 and v1.2** or **Enable All TLS**.
11
+
The Appliance Manager now defaults to **Enable TLS v1.2 only**. You can change the TLS settings in the Appliance Manager to **Enable TLS v.1.1 and v1.2** or **Enable All TLS**.
12
12
:::
13
13
14
-
- To apply TLS version restrictions, log into the Device42 Appliance Manager by clicking the link at the bottom of the main login page, and enter your Device42 Appliance Manager credentials. The default username and password for the Appliance Manager is `d42admin/default`.
15
-
16
-
14
+
- To apply TLS version restrictions, log in to the Device42 Appliance Manager. See [Device42 Appliance Manager Login](device42-appliance-manager-login.mdx) for more details about accessing and logging in to the Appliance Manager.
17
15
- From the main menu on the left side of the Appliance Manager, select **Global Settings** and then **TLS versions for Web Console** or **TLS versions for Appliance Manager**.
18
16
- Select the appropriate radio button and click **Submit** to apply your changes.
Copy file name to clipboardExpand all lines: docs/administration/generating-csrs.mdx
+20-7Lines changed: 20 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,36 +3,49 @@ title: "Generating CSRs"
3
3
sidebar_position: 10
4
4
---
5
5
6
-
## Generating a certificate via OpenSSL
6
+
## Generating a Certificate Via OpenSSL
7
7
8
8
Instructions to generate certificates with openSSL can also be found [documented here, on our support site.](https://support.device42.com/hc/en-us/articles/222221348-My-demo-certificate-for-https-expired-how-can-I-add-a-new-one-)
9
9
10
-
To generate a CSR (Certificate Signing Request), open a terminal that has the _openssl_ package installed. The following commands will generate a (self-signed) SSL certificate from a new or existing OpenSSL installation:
10
+
To generate a CSR (Certificate Signing Request), open a terminal that has the **openssl** package installed. The following commands will generate a (self-signed) SSL certificate from a new or existing OpenSSL installation:
11
+
11
12
12
-
```
13
13
1. Generate a **private** key for your server CA (Certificate Authority):
14
+
```bash
14
15
$ openssl genrsa -des3 -out ca.key 4096
16
+
```
15
17
16
18
2. Create a certificate file using the generated CA private key:
Adding a new certificate is easy; See [add a new certificate via appliance manager instructions here](appliance-manager/set-up-https-cert.mdx).
33
44
34
-
## Generating non-production CSRs
45
+
## Generating Non-Production CSRs
35
46
36
-
**WARNING! You should most likely use the OpenSSL method outlined ABOVE! Use the following online generator at your own risk, and ONLY for NON-PRODUCTION purposes. A 'Private' key generated by this link [or any third party] is, by definition, NOT private!!**
47
+
:::caution
48
+
We recommend using the OpenSSL method outlined above. Use the following online generator at your own risk, and only for non-production purposes. A 'private' key generated by this link (or any third party) is unlikely to be truly private.
49
+
:::
37
50
38
-
If you need to quickly generate a non-production Certificate Signing Request (CSR), you can use this online CSR generator at your own risk: [CSR Generator](https://csrgenerator.com)
51
+
If you need to quickly generate a non-production Certificate Signing Request (CSR), you can use this online CSR generator at your own risk: [CSR Generator](https://csrgenerator.com).
Copy file name to clipboardExpand all lines: docs/administration/setting-time-zone-and-ntp.mdx
+23-24Lines changed: 23 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,42 +3,41 @@ title: "Setting Time Zone and NTP"
3
3
sidebar_position: 14
4
4
---
5
5
6
-
Here is brief run down on setting or changing your time zone in Device42. This is probably one of the first steps you should take so that autodiscovery scheduling and log history work correctly. The virtual appliance takes the clock from virtual host, so make sure the time is correct on the host and it's not a bad idea to set up an NTP time source to ensure the time stays correct.
6
+
importThemedImagefrom'@theme/ThemedImage'
7
+
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
7
8
8
-
## Set time Zone
9
+
Here is a brief run-down on setting or changing your time zone in Device42. This is probably one of the first steps you should take so that autodiscovery scheduling and log history work correctly. The virtual appliance takes the clock from the virtual host, so make sure the time is correct on the host. It's also a good idea to set up an NTP time source to ensure the time stays correct.
9
10
10
-
11
+
## Set the Time Zone
11
12
12
-
In the Device42 main menu, go to _Tools > Settings > Time Settings_.
13
+
In the Device42 main menu, go to **Tools > Settings > Time Settings**.
13
14
14
-
Here, you can select the correct time zone for your location and click Apply.
15
+
Here, you can select the correct time zone for your location and click **Apply**.
25
+
## OS-Level Time Settings
19
26
20
-
After you've selected the correct new time zone and received confirmation it's been applied, go to the Device42 console and restart the Device42 application\[Option #2\]. When it restarts, it will have the new time zone.
27
+
After you've selected the correct new time zone and received confirmation that it has been applied, go to the Device42 console and restart the Device42 application. When it restarts, the console menu will show the new time zone.
21
28
22
-
## OS Level Time Settings
29
+
- Use the VM console menu options, **NTP Settings** and **Set Timezone**, to set time at the OS level.
23
30
24
-
31
+
25
32
26
-
Use VM console menu options 6 & 7 to set time at the OS level. Here is a example of how to setup NTP.
33
+
- Select **NTP Settings** from the main menu and enter the IP or FQDN of the NTP server. Toggle on the **Daily sync** option to add the NTP server to the daily scheduled jobs.
27
34
28
-
35
+
29
36
30
-
First, enter the IP or FQDN of the NTP server. Then select 'y' to add the NTP server to the daily scheduled jobs.
37
+
- Go back to the main menu and select **Set Timezone** to set the time zone on the OS level. If you don't see your exact location, choose the location closest to you:
31
38
32
-
39
+
33
40
34
-
Use option 7 to set the time zone on the OS level. If you don't see your exact location, choose the location closest to you:
41
+
- Select **Restart Services** for the new time zone settings to take effect immediately.
35
42
36
-
37
-
38
-
Once you've completed the TZ settings, you'll be able to see your new Time Zone at the top of the Device42 Console Menu:
39
-
40
-
41
-
42
-
### Restart Application from console.
43
-
44
-
**After changing your time settings, select Option 2 to restart the application** and the new time zone settings will take effect immediately.
43
+
0 commit comments