Skip to content

Commit 8d08fa4

Browse files
authored
Merge pull request #472 from ritza-co/19.07.03
Docs 19.07.03 release (Week 36, 2025)
2 parents 63db602 + f978242 commit 8d08fa4

File tree

55 files changed

+182
-104
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

55 files changed

+182
-104
lines changed

docs/apps/business-services/building-business-services-in-device42.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ Applications Groups are enabled by default in Device42, but you can disable the
116116
/>
117117

118118

119-
### (Legacy) Pinning, Starring, and Hiding Services
119+
### For versions prior to 19.05: Pinning, Starring, and Hiding Services
120120

121121
Now that we have enabled Application Groups, we must identify which services we want to Pin, Star, and Hide to continue to build out our Application Groups. 
122122

@@ -172,7 +172,7 @@ Hovering over the timeline above the view will allow you to identify changes to
172172

173173
![](/assets/images/WEB-519_bus-apps-13-Affinity-Group-Chart-Timeline.png)
174174

175-
### (Legacy) Refactoring Application Groups
175+
### For versions prior to 19.05: Refactoring Application Groups
176176

177177
- There are times when choosing a different query to generate your Application Groups may be better suited for your environment. Navigate to **Tools > Integrations > Saved DOQL Queries**.
178178

docs/auto-discovery/linux-unix-server-auto-discovery.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -179,11 +179,11 @@ Specify the timeout range between 10 to 600 seconds in the **Timeout** field to
179179
}}
180180
/>
181181

182-
When discovery switches between *nix users, the triggered banner text messages may disrupt database discovery and Application Component creation, resulting in discovery errors or incomplete data collection.
182+
If you experience unexplainable issues during discovery that you suspect are due to banner text interfering with parsing, enable the **Check for Banner** option for discovery to detect and remove banner messages. The **Check for Banner** option is also available via API.
183183

184-
To ensure full data collection when switching users, enable the **Check for Banner** option for discovery to detect and remove banner messages.
184+
When discovery switches between *nix users, the triggered banner text messages may disrupt database discovery and Application Component creation, resulting in discovery errors or incomplete data collection.
185185

186-
The **Check for Banner** option is also available via API.
186+
Note that banner text interference can't be directly determined from Device42. You require a power user with system access to the target machine to detect interference by switching users. Device42 support may advise you to select the banner option if they suspect banner text interference.
187187

188188
<ThemedImage
189189
alt="Check for Banner option"

docs/getstarted/discovery-hub.mdx

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Discovery Hub: scoping and onboarding"
2+
title: "Discovery Hub: Scoping and Onboarding"
33
sidebar_position: 3.5
44
---
55

@@ -31,7 +31,7 @@ Log in to the Device42 UI and navigate to **Discovery > Discovery Hub**.
3131

3232
To set up a Discovery Hub scan, name the scan and select the [Remote Collector](getstarted/installation/remote-collector-rc-installation.mdx) to use. You need to know the IPs, IP ranges, or CIDR blocks for your target environment.
3333

34-
Enter the IP information in the box highlighted in the image below and click on the **+** button. You can enter as many targets as you like but the more targets included, the longer the scan will likely take.
34+
Enter the IP information in the box highlighted in the image below and click on the **up arrow** button. You can enter as many targets as you like, but the more targets you include, the longer the scan will likely take.
3535

3636
<ThemedImage
3737
alt="Discovery Hub menu"
@@ -42,7 +42,7 @@ Enter the IP information in the box highlighted in the image below and click on
4242
/>
4343
<br/><br/>
4444

45-
After you have entered the information, click the bright green **Start** button.
45+
After you have entered the IP address, named the scan, and selected at least one RC, click the green **Start** button.
4646

4747
The scan will start immediately. You'll see the green start notification, a percentage ticker showing your completion status, and information on the six categories of assets: **Windows**, **Nix**, **Network Devices**, **Hypervisors**, **Other/Unknown**, and **Unreachable**.
4848

@@ -104,8 +104,8 @@ The scans you have created will be displayed in the left-hand column. Once start
104104
<ThemedImage
105105
alt="Scan results with settings button"
106106
sources={{
107-
light: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-outcome-light.png'),
108-
dark: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-outcome-dark.png'),
107+
light: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-settings-button-light.png'),
108+
dark: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-settings-button-dark.png'),
109109
}}
110110
/>
111111
<br/><br/>
@@ -162,7 +162,9 @@ The **One-time discovery** and **Continuous discovery** options are recommended
162162
light: useBaseUrl('/assets/images/discovery-hub-onboarding/discovery-job-window-cidr-light.png'),
163163
dark: useBaseUrl('/assets/images/discovery-hub-onboarding/discovery-job-window-cidr-dark.png'),
164164
}}
165+
style={{ width: '70%' }}
165166
/>
167+
166168
<br/><br/>
167169

168170
When the job is created successfully, you will see the screen below. You can close the window and go back to your scans or click the link to be taken to the job page to edit the job settings.
@@ -176,9 +178,7 @@ When the job is created successfully, you will see the screen below. You can clo
176178
/>
177179
<br/><br/>
178180

179-
From the **Settings** tab of completed Discovery Hub scans, you can see the linked jobs that were created based on those results.
180-
181-
Click on the **+ Add schedule button** to schedule the scan.
181+
From the **Settings** tab of completed Discovery Hub scans, you can see the linked jobs that were created based on those results. Click on the **+ Add schedule button** to schedule the scan.
182182

183183
<ThemedImage
184184
alt="Network scan settings"

docs/getstarted/faqs/index.mdx

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -18,12 +18,7 @@ With a default configuration, visit `https://IP_or_fqdn_for_device42_vm` in your
1818

1919
## Which Browser Should I Use?
2020

21-
Device42 recommends using the web browsers (or more recent versions) listed below.
22-
23-
- Chrome — 88.0.4324.150
24-
- Edge — 88.0.705.63
25-
- Firefox — 72.0.1
26-
- Safari — 13.1.2 (13609.3.5.1.5)
21+
Device42 recommends using the latest version of Chrome, Firefox, Edge, or Safari.
2722

2823
## How Do I Get My Current Data Into Device42?
2924

@@ -37,7 +32,7 @@ You can use any of the following tools to import your data to Device42:
3732

3833
- [**Microsoft Excel / CSV (spreadsheet) import**](integration/imports/index.mdx): The **Tools > Imports/Exports (xls)** page outlines your options for importing MS Excel spreadsheets to Device42 and provides sample Excel sheets to help you format your existing spreadsheets so that uploading your existing data is as easy as possible.
3934
- [**Device42 generic import tool**](https://www.device42.com/blog/2018/06/19/new-features-added-to-the-generic-import-tool/): You can use the Device42 generic import tool to add and map fields for existing data from most spreadsheet formats. Learn more about formatting best practices in the Device42 walkthrough for manually [Importing Data From Existing Spreadsheets](getstarted/importing-data-from-existing-spreadsheets.mdx).
40-
- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as single source of truth for systems such as provisioning and monitoring.
35+
- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as a single source of truth for systems such as provisioning and monitoring.
4136
- **Device42 web UI**: You can use the Device42 web interface to import your data.
4237
- **Templates/bulk operations**: Certain object types are easier to add using templates or models. For example, it is easier to use [PDU models](infrastructure-management/power-units/defining-pdu-models.mdx) to create PDUs, [switch port templates](infrastructure-management/ipam/switch-templates.mdx) to create switches and ports, and [patch panel models](infrastructure-management/power-units/defining-pdu-models.mdx) to create patch panel ports and bulk backport connectivity for patch panels.
4338

@@ -65,7 +60,7 @@ Current releases of Device42 support **all** discovery jobs, including WMI and P
6560

6661
:::note
6762
RCs will only automatically update when an RC update coincides with an MA update.
68-
::
63+
:::
6964

7065
## How Do I Migrate Existing Power Appliance Jobs to a Remote Collector?
7166

@@ -109,7 +104,7 @@ Data can be exported in Excel or CSV format by downloading current data from the
109104

110105
## How Do I Back Up My Data?
111106

112-
Log in to the Device42 appliance manager at `https://your\_device42\_ip\_or\_FQDN:4242/` using the following default credentials:
107+
Log in to the Device42 appliance manager at `https://your_device42_ip_or_FQDN:4242/` using the following default credentials:
113108

114109
- Username:`d42admin`
115110
- Password: `default`

docs/getstarted/index.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,22 @@
11
---
22
title: "The Hitchhiker's Guide to Device42"
3-
sidebar_postion: 1
3+
sidebar_position: 1
44
---
55

6-
Welcome to **The Hitchhiker's Guide to Device42**, AKA the Device42 docs site.
6+
Welcome to **The Hitchhiker's Guide to Device42**, AKA the Device42 docs site!
77

8-
The following pages contain answers to the ultimate questions about infrastructure, the data center, and everything _(and the answers to many common Device42 questions, too)_.
8+
The following pages contain answers to the ultimate questions about infrastructure, the data center, and many common Device42 questions, too.
99

1010
Navigate through the Device42 documentation topics using the left-hand navigation bar or the search box found hanging out at the top right of the page - in much the same way that bricks don't.
1111

12-
* * *
13-
1412
## What is Device42?
1513

14+
We've got a whole [What is Device42](/what-is-device42.mdx) page with all the details, but here's a summary:
15+
1616
Device42 is a comprehensive IT infrastructure management software suite with powerful, agentless autodiscovery and application dependency mapping tools, a configuration management database (CMDB), a complete data center infrastructure management (DCIM) suite, full IT asset and inventory management (ITAM) functionality, plus IP address management (IPAM), password management and lots more - all in a single tool.
1717

18-
* * *
18+
## Getting Answers
1919

20-
If you don't find an answer to your question in the menu or using search, click  [here](https://support.device42.com) to open a support ticket or send us a note at [[email protected]](mailto:[email protected]). Our support team _loves_ hearing from customers, and they're all especially fond of a good challenge!
20+
If you don't find an answer to your question in the menu or using search, [open a support ticket](https://support.device42.com) or send us a note at [[email protected]](mailto:[email protected]). Our support team loves hearing from customers, and they're all especially fond of a good challenge!
2121

2222

Lines changed: 24 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,34 @@
11
---
22
title: "Environmental Monitoring"
3-
sidebar_position: 1
3+
sidebar_position: 2
44
---
55

6-
## Discovering Environmental Sensors
6+
import ThemedImage from '@theme/ThemedImage';
7+
import useBaseUrl from '@docusaurus/useBaseUrl';
78

8-
The PDU Discovery process will automatically find any environmental sensors that are attached to your PDUs, including heat, temperature, and humidity sensors. Power units are discovered via the SNMP Discovery option in the Discovery menu; See the 'Power Unit Autodiscovery' section of [Getting started with Power & Environmental Monitoring"](infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx) to learn how to discover power units/PDUs! ![Add SNMP discovery job Power PDU](/assets/images/add_SNMP_discovery_MENU-hl.png)
99

10-
* * *
10+
The PDU discovery process automatically finds any environmental sensors attached to your PDUs, including heat, temperature, and humidity sensors.
1111

12-
## Viewing Discovered Sensors
12+
## Discovering Environmental Sensors via PDUs
13+
14+
Power units are discovered via the SNMP Discovery option in the Discovery menu. See the **Power Unit Autodiscovery** section of [Getting started with Power and Environmental Monitoring](infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx) to learn how to discover power units or PDUs.
1315

14-
When sensors are discovered, they are created along with an asset record in Device42. To view all discovered sensors, simply head to the main menu, _Devices -> Assets_ and filter by "Type" = Sensor: ![View discovered PDU Sensors ](/assets/images/view_all_sensors.png)
16+
<ThemedImage
17+
alt="Add SNMP discovery menu"
18+
sources={{
19+
light: useBaseUrl('/assets/images/environmental-monitoring/add-snmp-discovery-menu-light.png'),
20+
dark: useBaseUrl('/assets/images/environmental-monitoring/add-snmp-discovery-menu-dark.png'),
21+
}}
22+
/>
23+
24+
## Viewing Discovered Sensors
1525

16-
* * *
26+
When sensors are discovered, they are created along with an asset record in Device42. To view all discovered sensors, head to the main menu, navigate to **Resources > All Assets**, and filter the **Type** by **Sensor**:
1727

28+
<ThemedImage
29+
alt="View discovered sensors"
30+
sources={{
31+
light: useBaseUrl('/assets/images/environmental-monitoring/view-discovered-sensors-light.png'),
32+
dark: useBaseUrl('/assets/images/environmental-monitoring/view-discovered-sensors-dark.png'),
33+
}}
34+
/>
Lines changed: 38 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,60 @@
11
---
22
title: "Getting Started with Power and Environmental Monitoring"
3-
sidebar_position: 2
3+
sidebar_position: 1
44
---
55

6-
## The Power and Environmental Monitoring Add-ons
6+
import ThemedImage from '@theme/ThemedImage';
7+
import useBaseUrl from '@docusaurus/useBaseUrl';
78

9+
:::note
810
To access the functionality described in this section, you need a **Power and Environmental Monitoring** license. Visit the [Device42 pricing page](https://www.device42.com/pricing/) to request a pricing quote based on your needs.
9-
10-
* * *
11+
:::
1112

1213
## Power Unit Autodiscovery
1314

14-
The process of autodiscovering power-enabled PDUs is similar to [Device42 Network Autodiscovery.](auto-discovery/network-auto-discovery.mdx) Begin by navigating to the Device42 main menu, **Discovery > SNMP**. You can then enter an IP address range, a port if not using the default 161, and any SNMP authentication information depending on if you are using v1, v2c, or v3:
15+
Install and set up a [Remote Collector](https://www.device42.com/autodiscovery/) if you have not already done so. See the [Remote Collector page](/auto-discovery/remote-collector-rc/#installation-and-configuration) for information.
1516

16-
![Add Power SNMP discovery job](/assets/images/add_power_SNMP_discovery.png)
17+
The process of discovering power-enabled PDUs is similar to [Device42 Network Autodiscovery](auto-discovery/network-auto-discovery.mdx). Begin by navigating to **Discovery > SNMP**. You can then enter an IP address range and a port if not using the default `161`.
1718

18-
Install and set up a [Remote Collector](https://www.device42.com/autodiscovery/) if you have not already done so. See the [Remote Collector page](/auto-discovery/remote-collector-rc/#installation-and-configuration) for information.
19+
<ThemedImage
20+
alt="Add SNMP discovery job"
21+
sources={{
22+
light: useBaseUrl('/assets/images/getting-started-with-power-and-environmental-monitoring/add-snmp-discovery-job-light.png'),
23+
dark: useBaseUrl('/assets/images/getting-started-with-power-and-environmental-monitoring/add-snmp-discovery-job-dark.png'),
24+
}}
25+
/>
26+
27+
Add any SNMP authentication information, depending on whether you are using v1, v2c, or v3:
28+
29+
<ThemedImage
30+
alt="Add credentials"
31+
sources={{
32+
light: useBaseUrl('/assets/images/getting-started-with-power-and-environmental-monitoring/add-snmp-community-string-light.png'),
33+
dark: useBaseUrl('/assets/images/getting-started-with-power-and-environmental-monitoring/add-snmp-community-string-dark.png'),
34+
}}
35+
/>
36+
37+
### Power Monitoring Options
1938

20-
**NOTE** that the Power (SNMP) discovery options will not be visible if the power module is not licensed, or if no Remote Collector is available to collect data. Once these are registered in Device42, these option will be visible:
39+
The Power (SNMP) discovery options will not be visible if the power module is not licensed or if no Remote Collector is available to collect data. Once these are registered in Device42, the **Power/Environmental options** section will be visible:
2140

22-
![Enable power monitoring for discovered PDU devices](/assets/images/power_options_enable_monitoring-HL.png)
41+
<ThemedImage
42+
alt="Power monitoring options"
43+
sources={{
44+
light: useBaseUrl('/assets/images/getting-started-with-power-and-environmental-monitoring/power-monitoring-options-light.png'),
45+
dark: useBaseUrl('/assets/images/getting-started-with-power-and-environmental-monitoring/power-monitoring-options-dark.png'),
46+
}}
47+
/>
2348

24-
You'll see these options towards the bottom of the SNMP discovery job setup screen. **Be sure to check enable monitoring for discovered PDUs**, and you may also set the polling interval for any PDUs discovered by this job by choosing the appropriate value from the Polling Interval drop-down. This value controls the frequency at which monitoring will poll each PDU.
49+
You'll see these options towards the bottom of the SNMP discovery job setup screen. Be sure to check ***Enable monitoring for discovered PDU devices**, and you may also set the polling interval for any PDUs discovered by this job by choosing the appropriate value from the Polling Interval dropdown. This value controls the frequency at which monitoring will poll each PDU.
2550

2651

2752
### Viewing Discovered Sensors
2853

29-
When sensors are discovered, they are created with Asset records in Device42. Navigate to **Resources > Assets > All Assets** to see a list of all assets. Filter the list by `Type="Sensor"` to see a list of all PDU attached sensors discovered.
54+
When sensors are discovered, they are created with Asset records in Device42. Navigate to **Resources > Assets > All Assets** to see a list of all assets. Filter the list by `Type="Sensor"` to see a list of all the PDU-attached sensors discovered.
3055

3156
## Capacity Considerations
3257

33-
Monitoring is a fairly resource-intensive process and as a result, each individual monitoring appliance is limited in the number of PDUs, infeeds, and outlets it can handle. When you set up each autodiscovery job, you will choose a polling interval. The primary resource limitation is the number of SNMP polls that can be done in the selected polling. So, if you select a 5-minute polling intervals, you monitor 5x the number of PDUs in one monitoring appliance as you can if you select 1-minute polling intervals.
58+
Monitoring is a fairly resource-intensive process, and as a result, each individual monitoring appliance is limited in the number of PDUs, infeeds, and outlets it can handle. When you set up each autodiscovery job, you will choose a polling interval. The primary resource limitation is the number of SNMP polls that can be done in the selected polling. So, if you select 5-minute polling intervals, you monitor 5x the number of PDUs in one monitoring appliance that you could if you selected 1-minute polling intervals.
3459

35-
At 5-minute intervals (default), Device42 recommends that you have one monitoring appliance per 200 PDUs. At 1-minute intervals, assume 40 PDUs. If your network is at all sluggish, reduce the number of PDUs per monitoring appliance. Remember, you can deploy as many monitoring appliances as you need with no additional license cost.
60+
At 5-minute intervals (default), Device42 recommends having one monitoring appliance per 200 PDUs. At 1-minute intervals, assume 40 PDUs. If your network is at all sluggish, reduce the number of PDUs per monitoring appliance. Remember, you can deploy as many monitoring appliances as you need with no additional license cost.

0 commit comments

Comments
 (0)