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
+28-8Lines changed: 28 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,26 +3,46 @@ title: "Collecting SNMP Walk Output"
3
3
sidebar_position: 4
4
4
---
5
5
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.
6
+
You can collect SNMP walk output for a network device or PDU right from the GUI. Then, you can download the output and send it to us for further troubleshooting.
7
7
8
-
### Collect SNMP Walk Output
8
+
From the Appliance Manager, go to **Application > Generate SNMP Output**.
9
9
10
-
From the Appliance Manager, go to **Application > Generate SNMP Output**.
10
+
### Simple SNMP Walk Output
11
11
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.
12
+
If this is not a new device, select the **No: Simple walk** option.
13
13
14
-

14
+
Add your target switch or other SNMP target device info, click **Submit**, and please be patient as it might take a few minutes. Download the generated file and send it to support.
15
15
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:
16
+

17
+
18
+
### MIB Browser-Based Walk
19
+
20
+
For new devices, select **Yes: MIB browser based walk**.
21
+
22
+
- Select your **RC** and enter the required fields: **FQDN or IP Address**, **Community String**, and MIB file upload.
- Click **Download Archive File** and save the file to attach to an existing support ticket. If needed, [create a new ticket](https://support.device42.com/hc/en-us/requests/new) or [email support](mailto:support@device42.com).
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 for SNMP v2:
17
37
18
38
```
19
39
snmpbulkwalk -Cc -ObentU -v2c -c COMMUNITY DEVICE > output_file_name
20
40
snmpbulkwalk -ObentU -v 2c -c COMMUNITY DEVICE .1.3.6.1.4.1 >> output_file_name
21
41
```
22
42
23
-
Also, the current setup has a bug for v3, so please use the following for any system using SNMP v3:
43
+
You can use the following for any system using SNMP v3:
24
44
25
45
```
26
46
snmpbulkwalk -Cc -ObentU -v 3 -u user_name -l authNoPriv -a MD5 -A auth_pass DEVICE > output_file_name
27
47
snmpbulkwalk -Cc -ObentU -v 3 -u user_name -l authNoPriv -a MD5 -A auth_pass DEVICE .1.3.6.1.4.1 >> output_file_name
Copy file name to clipboardExpand all lines: docs/administration/passwords/password-security-and-permissions.mdx
+28-8Lines changed: 28 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,15 +77,35 @@ If no permissions are entered, the User who created the Secret will have **view/
77
77
78
78
### Bulk Permissions Change
79
79
80
-
From the Secrets list page, you can edit the group permissions of many Secrets at once by selecting **Change group permissions for selected passwords** from the **Actions** dropdown menu.
80
+
-From the Secrets list page, you can edit the group permissions of many Secrets at once by selecting **Change group permissions for selected passwords** from the **Actions** dropdown menu.
Copy file name to clipboardExpand all lines: docs/apps/application-groups/index.mdx
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,9 +171,9 @@ Edit a rule or create a new rule and [select **Fixed** as the **Starting Point**
171
171
172
172

173
173
174
-
## Impact Charts
174
+
## Charts
175
175
176
-
- Under the **My Application Groups** tab, click on the **Chart** link next to an Application Group name to view the Application Group Impact Chart.
176
+
- Under the **My Application Groups** tab, click on the **Chart** link next to an Application Group name to view the Application Group chart.
177
177
178
178
<ThemedImage
179
179
alt="Chart links"
@@ -183,7 +183,7 @@ Edit a rule or create a new rule and [select **Fixed** as the **Starting Point**
183
183
}}
184
184
/>
185
185
186
-
The Application Group Impact Chart displays the relationships between Application Components, Services, and Devices.
186
+
The Application Group chart displays the relationships between Application Components, Services, and Devices.
187
187
188
188
<ThemedImage
189
189
alt="Application Group Impact Chart"
@@ -226,6 +226,22 @@ If you don't see this historical communication metadata, make sure you have the
226
226
227
227
You can also run a **Service Dependencies Report** from the chart view page. The Services Dependencies report details all the communications for devices within an Application Group.
228
228
229
+
### Chart List View
230
+
231
+
You can view the devices and root resources displayed in the chart in a handy, tabulated list view. Note that this chart list view is only available via the **Chart** tab, and not via the **Breakdown** panel on the AG main page.
- Click the **list icon** button to the right of the chart.
238
+
239
+

240
+
241
+
- You can use the links in the list view to navigate to the details page of the listed items and toggle back to the chart view.
242
+
243
+

244
+
229
245
## Application Group Timelines
230
246
231
247
Application Group timelines make it easy to see how a given group has changed over time. Changes to services and resources are marked along the timeline, indicating when they were added or removed from the group.
Copy file name to clipboardExpand all lines: docs/apps/business-services/building-business-services-in-device42.mdx
+7-30Lines changed: 7 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
13
13
14
14
## Overview
15
15
16
-
This is a technical guide that will walk you through a step-by-step process of building Business Services within Device42. [Once you have successfully performed discovery,](auto-discovery) apply the methods outlined below to create Application Groups and then leverage these groups to facilitate the process of building your Business Applications.
16
+
This is a technical guide that will walk you through a step-by-step process of building Business Services within Device42. [Once you have successfully performed discovery,](auto-discovery) apply the methods outlined below to create Application Groups and then leverage these groups to facilitate the process of building your Business Services.
17
17
18
18
## Viewing Discovery Data
19
19
@@ -187,36 +187,29 @@ To choose one of these queries to generate your Application Groups, navigate to
187
187
188
188
## Building Business Services
189
189
190
-
To build a Business Service, navigate to **Applications > Business Applications**, and then click **Create** in the top right of the page.
190
+
To build a Business Service, navigate to **Applications > Business Services**, and then click **Create** in the top right of the page.
After naming and saving your new Business Service, click the **View Application** button and toggle on the **Edit** mode. You'll see a blank canvas. Drag items from the left panel to start building the Business Service.
201
+
After naming and saving your new Business Service, click the **Application Layout** button and toggle on the **Edit** mode. You'll see a blank canvas. Drag items from the left panel to start building the Business Service.
202
202
203
-
Select **Application Group** and drag it onto the canvas.
204
-
205
-
You have several options to search for existing Application Groups. In the example, we searched for part of a server name (`server`) that we know is within the AppFocus group of the Application Group we're looking for. The AppFocus group is the focus point for the Application Group and is defined as the group's [Starting Point](/apps/application-groups/calculation-rules).
206
-
207
-
You'll see that we found two Application Groups that had items containing the word `server` as their focus points.
203
+
Select **Application Group** and drag it onto the canvas and choose the group(s) you want to add and click **Add** to include it on the canvas.
Select the group you want to add and click **Add** to include it on the canvas. Repeat this process if there are any other Application Groups, Components, Resources, or Devices that you need to add to the Business Service.
219
-
220
213
Once you have successfully imported everything, use the toolbars at the top right of the screen to label and color-code the objects.
221
214
222
215
Select a box with a device name, then use the **Style** tab on the right to change the color of this box.
@@ -237,20 +230,4 @@ Double-click a line or another area of the canvas to add text. Use this to repre
237
230
Congratulations! You have now built a Business Service by leveraging Device42's discovery and Application Group capabilities.
238
231
239
232

240
-
241
-
242
-
## Tips and Tricks: Use Tags
243
-
244
-
In the add or edit mode of the **Hypervisors/\*nix/win for Autodiscovery** job pages, you can expand the **Miscellaneous** section to apply **Tags for discovered devices**.
245
233
246
-
- If you know which servers are part of your Business Service, you can tag them with the Business Service name, then easily search and filter devices by this tag when you are building your Business Service.
247
-
248
-
- When creating a Business Service, drag the **Device** icon on the left, and then search for the tag to choose the devices you previously tagged in the discovery job.
Copy file name to clipboardExpand all lines: docs/apps/business-services/index.mdx
+38-4Lines changed: 38 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ import ThemedImage from '@theme/ThemedImage';
6
6
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
7
7
8
8
:::info
9
-
Business Applications are now named **Business Services**. Affinity Groups have also been renamed as **Application Groups**. See [**Calculation Rules**](/apps/application-groups/calculation-rules) (previously AppFocus Filters) for details on the new ADM flow.
9
+
Business Applications are now named **Business Services**. Affinity Groups have also been renamed **Application Groups**. See [**Calculation Rules**](/apps/application-groups/calculation-rules) (previously AppFocus Filters) for details on the new ADM flow.
10
10
:::
11
11
12
12
## Overview
@@ -79,9 +79,33 @@ Select **Applications > Business Services** from the Device42 menu to display
79
79
- Select or enter the **Migration Group** and **Criticality**, and add any **Notes** or **Tags** you want.
80
80
- Click **Save** at the bottom right of the page to save the Business Service and add it to the applications list page.
81
81
82
-
You'll be directed to a summary page for the new Business Service. Now it's time to work from the visualization canvas to add Devices, Application Groups, and Application Components to your new Business Service.
82
+
You'll be directed to a summary page for the new Business Service. Now it's time to work from the visualization canvas to add items to your new Business Service.
83
83
84
-
### Visualizations
84
+
### Adding and Removing Items
85
+
86
+
There are two methods of adding items to Business Services: inline and via the Application Layout canvas. Currently, Application Groups can only be added using the canvas. See the [Add Application Groups](#add-application-groups) section below.
87
+
88
+
You can add, edit, and remove devices, resources, and application components as inline items from a Business Service details view page.
Remove inline items by clicking the **Tashcan** icon. The item to be removed will be grayed out, giving you the option to restore the item in this session by clicking the **Restore** icon.
Click the **Application Layout** button from the Business Services details page to display the visualization canvas.
87
111
@@ -105,6 +129,8 @@ Click the **Edit** button on the top right of the canvas to activate the **Edit*
105
129
106
130
From the left panel, drag the **Device**, **Resource**, **Application Group**, and **Application Component** boxes onto the canvas to open the dialog that allows you to search for specific items to add to the canvas.
107
131
132
+
For efficiency, you can add multiple items of each item type at a time.
133
+
108
134
<ThemedImage
109
135
alt="Add Device button"
110
136
sources={{
@@ -322,6 +348,14 @@ As you construct your alert, Device42 displays the alert definition based on the
322
348
323
349
> When the individual Business Service Jupiter service app has reported New Application Group Dependency Found then send notification to users assigned to Main profile.
324
350
351
+
### Auto Apply Changes
352
+
353
+
Make maintaining Business Services easier by automatically adding and removing connections. Check the **Auto Apply changes** box when configuring the alert. Connections to a newly found AG dependency will be made automatically, and if an AG dependency is removed, the Business Service connection will be automatically removed. You will receive a notification of these events as part of the alert.
354
+
355
+
The **Auto Apply changes** option is unchecked by default. If left disabled, you'll receive a notification with the Add or Remove connection option for manually making changes to the Business Service.
356
+
357
+
### Apply To Selected Objects
358
+
325
359
Depending on which alert Rule Type you select, you may also see an **Apply To:** option, which you will use to select the objects you want to apply the alert to. Use the **Available objects** list on the left to select the objects you want to add to the **Chosen objects** list on the right.
326
360
327
361
<ThemedImage
@@ -332,7 +366,7 @@ Depending on which alert Rule Type you select, you may also see an **Apply To:**
332
366
}}
333
367
/>
334
368
335
-
**Additional Options**
369
+
### More Alert Options
336
370
337
371
-**Priority**: Choose between Critical, High Priority, Medium Priority, and Low Priority.
338
372
-**Resend Notification**: Number of seconds to wait before sending an email notification for the alert. Leave this field blank to send the email only once.
Select **OpenStack** from the **Type** dropdown menu, and fill in the **User** name, **Password**, and **Project name** fields.
214
214
215
+
If you disable **Discover all projects/tenants**, then the **Project Name** is required. When **Discover all projects/tenants** is enabled, Device42 will discover resources across all available projects, making the specific project name unnecessary.
Copy file name to clipboardExpand all lines: docs/auto-discovery/network-auto-discovery.mdx
+35-9Lines changed: 35 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -214,17 +214,43 @@ If you keep **Get all switch ports** selected, you will see extra form items:
214
214
215
215
## Globally Exclude OIDs
216
216
217
-
You can set certain OIDs to be ignored globally to prevent them from being collected during SNMP discovery.
217
+
You can set certain OIDs to be ignored globally to prevent them from being collected during SNMP discovery. Navigate to **Tools > Global Settings** and scroll down to the **Ignore OID(s):** field.
218
218
219
-
Navigate to **Tools > Global Settings** and scroll down to the **Ignore OID(s):** field. Add an individual OID or a group of OIDs using dot notation. For documentation purposes, you can optionally include a comment in text notation on the same line as the OID(s).
219
+
Device42 supports two methods of exclusion: Use a trailing dot (`.`) to ignore entire categories of data, or omit it to ignore specific OIDs.
- For an exact OID match, include the full OID without a dot at the end. For documentation purposes, you can optionally include a comment in text notation on the same line as the OID(s).
When OIDs are set to be ignored globally, existing discovery jobs will not automatically inherit these ignored OIDs. To apply the ignored OIDs to existing discovery jobs, a new discovery job must be created.
0 commit comments