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/auto-discovery/virtual-machine-auto-discovery.mdx
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,10 @@ From the Device42 main menu, under **Discovery > Hypervisors/\*nix/Windows**, ad
61
61
62
62
**Discovery Target(s):** This is the FQDN or IP of the vCenter server or the ESX server. If using FQDN, set up DNS resolution in the Device42 VM console first.
63
63
64
+
:::note
65
+
You need to add each vCenter server you wish to discover. Device42 does not automatically find or crawl additional vCenter servers linked to your first one.
66
+
:::
67
+
64
68
**Port:** This is 443 by default. Only change if you have changed it.
65
69
66
70
**Enable Resource Utilization Tracking for Device(s):** This option enables the periodic collection and examination of server resource usage metrics. See [Resource Utilization](/auto-discovery/resource-utilization-overview/) for more information.
@@ -202,4 +206,4 @@ Newly created jobs will not run on the first day they are created to prevent an
202
206
203
207
## Under the Hood
204
208
205
-
Device42 uses VMware APIs and the open-source library [pyvmomi](https://github.com/vmware/pyvmomi).
209
+
Device42 uses VMware APIs and the open-source library [pyvmomi](https://github.com/vmware/pyvmomi).
Copy file name to clipboardExpand all lines: docs/infrastructure-management/assets.mdx
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ sidebar_position: 5.5
6
6
importThemedImagefrom"@theme/ThemedImage";
7
7
importuseBaseUrlfrom"@docusaurus/useBaseUrl";
8
8
9
-
Assets are useful for tracking items that may not be directly discoverable. Like devices in Device42, assets can be racked, support lifecycle events, and assigned parts. However, assets do not consume licenses.
9
+
Assets are useful for tracking items that may not be directly discoverable. Like devices in Device42, assets can support lifecycle events, be racked, and be assigned parts. However, assets do not consume licenses.
10
10
11
11
You can search, view, add, and edit assets from the list page under **Resources > All Assets**.
12
12
13
13
## Adding Assets
14
14
15
-
From the assets list page, click the **+ Add Asset** button to create a new asset.
15
+
From the Assets list page, click the **Create** button to create a new asset.
16
16
17
17
<ThemedImage
18
18
alt="Assets list page"
@@ -24,7 +24,7 @@ From the assets list page, click the **+ Add Asset** button to create a new asse
24
24
25
25
### Asset Types
26
26
27
-
Choose an asset **Type** from the dropdown menu or create a custom asset type by clicking **+** to the right. Different options in the add asset form will be available depending on the asset **Type** you select.
27
+
Choose an asset **Type** from the dropdown menu or create a custom asset type by clicking **+** to the right. Different options in the Add Asset form will be available depending on the asset type you select.
28
28
29
29
<ThemedImage
30
30
alt="Assets Types menu"
@@ -34,15 +34,14 @@ Choose an asset **Type** from the dropdown menu or create a custom asset type by
34
34
}}
35
35
/>
36
36
37
-
Name your custom asset type. If you want to associate assets of this new type to devices, check the **Asset Device Relation** checkbox. Designate the types of locations that assets of this type will be assigned to (**Storage Room**, **Server Room**, **Building**, and **Rack**).
37
+
Name your custom asset type. If you want to associate assets of this new type with devices, check the **Asset Device Relation** checkbox. Designate the types of locations (**Storage Room**, **Server Room**, **Building**, and **Rack**) that assets of this type will be assigned to.
@@ -59,7 +58,7 @@ Add the **Date** and choose the lifecycle **Event**. Optionally, add an **End Us
59
58
60
59
### Rack Info
61
60
62
-
Depending on the selected asset **Type**, the **Rack Info**box will be available.
61
+
Show the **Rack Info** section by choosing **ACL** from the **Type**dropdown (or another similarly configured custom asset type).
63
62
64
63
<ThemedImage
65
64
alt="Asset Rack Info box"
@@ -71,15 +70,15 @@ Depending on the selected asset **Type**, the **Rack Info** box will be availabl
71
70
72
71
### Object Category Field
73
72
74
-
In v19.06, the **Object Category** field on the view pages of individual Assets is displayed when **Role-Based Access Control** (RBAC) is enabled globally.
73
+
In v19.06, the **Object Category** field on individual asset view pages is displayed only when **Role-Based Access Control** (RBAC) is enabled globally.
75
74
76
75
A workaround on view pages is to use the **Legacy View** button to see the **Object Category** field.
77
76
78
77
Turn on **Role-Based Access Control** under **Tools > Settings > Global Settings**.
79
78
80
79
## Asset Actions
81
80
82
-
The action menu has options to delete, export, and update assets. You can also **Generate QR/Barcodes for selected Items** for asset management.
81
+
The action menu has options for deleting, exporting, and updating assets. You can also **Generate QR/Barcodes for selected Items** for asset management.
83
82
84
83
Select one or several assets from the table, and select an action from the menu:
85
84
- Delete with Detailed Confirmation
@@ -92,8 +91,7 @@ Select one or several assets from the table, and select an action from the menu:
92
91
- Assign lifecycle state to selected Items
93
92
- Generate QR/Barcodes for selected Items
94
93
- Add tags to selected items
95
-
96
-
Click the **hammer icon** to execute the selected action.
Copy file name to clipboardExpand all lines: docs/infrastructure-management/devices/device-blade-chassis.mdx
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
10
10
11
11
Locate your blade chassis in Device42 by navigating to **Resources > All Devices** and filtering for blade chassis devices:
12
12
13
-
- Click **+ More** and select the **Blade Chassis** checkbox to display its dropdown menu.
13
+
- Click **More Filters** and select the **Blade Chassis** checkbox to display its dropdown menu.
14
14
- Choose **Yes** from the dropdown.
15
15
16
16
<ThemedImage
@@ -23,7 +23,7 @@ Locate your blade chassis in Device42 by navigating to **Resources > All Devices
23
23
24
24
## The Blades Tab
25
25
26
-
Select a blade chassis from the Devices list page. Scroll down to the **Blades**tab, located below the device basic details section.
26
+
Select a blade chassis from the Devices list page and, from the **Breakdown**panel on the right, click **Blades**.
27
27
28
28
The **Blades** tab shows information about each device in the chassis. Blades are sorted by **Slot** number. Each blade has a link to its device page and displays its **Serial #**, **Asset #**, **Slot Location**, and **Hardware Model**.
29
29
@@ -37,7 +37,7 @@ The **Blades** tab shows information about each device in the chassis. Blades ar
37
37
38
38
### Add a New Blade
39
39
40
-
In device **Edit** mode, from the **Blade** tab, you can add blades to a chassis by clicking **+ Add New Blade**. The hardware model for the blade device must exist beforehand.
40
+
In device **Edit** mode, from the **Blade** tab, you can add blades to a chassis by clicking **+ Add New**. The hardware model for the blade device must exist beforehand.
41
41
42
42
<ThemedImage
43
43
alt="Adding a new blade"
@@ -51,7 +51,7 @@ In device **Edit** mode, from the **Blade** tab, you can add blades to a chassis
51
51
52
52
Layouts allow you to visualize blades within their chassis. The overall layout architecture is defined by the chassis [Hardware Model](#editing-hardware-models), which needs to be defined before you add and position specific blades.
53
53
54
-
From the view mode of the [device chassis page](#view-blade-chassis-devices), click the **ellipsis menu** and select **Layout**from the dropdown.
54
+
From the view mode of the [device chassis page](#view-blade-chassis-devices), click the **Layout**button.
55
55
56
56
<ThemedImage
57
57
alt="Device Layout button"
@@ -78,19 +78,17 @@ For blade-specific templating information, see the [Blade Slots documentation](d
78
78
79
79
### Editing Hardware Models
80
80
81
-
To edit the layout of a blade, first define its Hardware Model under **Infrastructure > Hardware Models > + Add Device Hardware Model**.
81
+
To edit the layout of a blade, select its hardware model from the list page under **Infrastructure > Hardware Models** and click the **Model Layout** tab.
Copy file name to clipboardExpand all lines: docs/infrastructure-management/devices/device-cluster.mdx
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ A device cluster can be a server farm, an active-active cluster, an active-passi
12
12
13
13
**Cluster** is one of the available device types, in addition to the **physical**, **virtual**, and **unknown** types.
14
14
15
-
To create a new cluster, navigate to **Resources > All Devices** and click **+ Add New Device**. Select **cluster** as the device **Type** to reveal the cluster-related options.
15
+
To create a new cluster, navigate to **Resources > All Devices** and click **Create**. Select **cluster** as the device **Type** to reveal the cluster-related options.
16
16
17
17
<ThemedImage
18
18
alt="Adding a cluster-type device"
@@ -22,9 +22,7 @@ To create a new cluster, navigate to **Resources > All Devices** and click **+ A
22
22
}}
23
23
/>
24
24
25
-
Search for and select the devices you want to add to the cluster and move them across to the right-hand box using the **right arrow** button.
26
-
27
-
Use the search box to narrow down the list of available devices and make it easy to select one among hundreds or thousands of devices. Add new devices using the **+ (plus sign)** button.
25
+
Start typing in the **Devices in Cluster** field to narrow down the list of available devices and make it easy to select one among hundreds or thousands of devices. Add new devices using the **plus sign** button.
Copy file name to clipboardExpand all lines: docs/infrastructure-management/devices/device-lifecycle-tab.mdx
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,41 +6,43 @@ sidebar_position: 7
6
6
importThemedImagefrom'@theme/ThemedImage'
7
7
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
8
8
9
-
## The LifeCycle Tab
9
+
From version 19.05 of the Device42 UI onward, the **Lifecycle Tab** is only available using the device **Legacy** view.
10
10
11
-
Under the **Lifecycle tab** you can record and track asset lifecycle events, assign an asset QR code or barcode, and add purchasing information for a device. **Purchase/Support Info** includes fields to add **Vendor**, **Cost**, **Contract Type**, and **Service Type** details.
11
+
In the device details view, from version 19.05 and later, the following sections have been moved from the **Lifecycle Tab** to the right-hand **Breakdown** panel:
12
+
-**Asset Lifecycle**
13
+
-**Purchase/Support Info**
14
+
15
+
The **Device QR/Barcode** field is now under the **Details** section of the device details view.
Provide the required details of **Date**, **Time**, and lifecycle **Event** to associate a new lifecycle event to the device. Optionally add an **End User** and related **Notes** and **Tags** to the event. Tags are useful for adding additional categories to manage your devices.
27
+
Provide the required details of **Date**, **Time**, and lifecycle **Event** to associate a new lifecycle event with the device. Optionally add an **End User** and related **Notes** and **Tags** to the event. Tags are useful for adding additional categories to manage your devices.
25
28
26
-
Add a new lifecycle event to the device using the **+ Add another Asset lifecycle** button.
29
+
Add a new lifecycle event to the device using the **+ Add New** button.
Some of the predefined **Events** have logic built-in. For example, you cannot choose **Checked Out** on a device or asset already checked out. Similarly, you can only select **Checked In** if the device is checked out.
39
+
Some of the predefined **Events** have logic builtin. For example, you cannot choose **Checked Out** on a device or asset already checked out. Similarly, you can only select **Checked In** if the device is checked out.
38
40
39
41
To add logic to asset lifecycle **Events**, go to **Tools > Lifecycle Event Actions**.
40
42
41
43
### Add a New LifeCycle Event
42
44
43
-
Define a custom lifecycle **Event** by clicking the **+** button near the **Events** dropdown menu.
45
+
Define a custom lifecycle **Event** by clicking the **plus sign** button near the **Events** dropdown menu and then **Create** on the pop-up window.
44
46
45
47
<ThemedImage
46
48
alt="Add new lifecycle event"
@@ -99,7 +101,7 @@ Enter purchase information related to the device under **Purchase/Support Info**
99
101
}}
100
102
/>
101
103
102
-
Add new **Purchase/Support Info** using the **+ Add New Purchase/Support Info** button.
104
+
Add new **Purchase/Support Info** using the **+ Add New** button.
103
105
104
106
<ThemedImage
105
107
alt="Add new Purchase/Support Info"
@@ -109,4 +111,4 @@ Add new **Purchase/Support Info** using the **+ Add New Purchase/Support Info**
109
111
}}
110
112
/>
111
113
112
-
See [managing purchases](infrastructure-management/accounting/purchases.mdx) for more information.
114
+
See [managing purchases](infrastructure-management/accounting/purchases.mdx) for more information.
0 commit comments