diff --git a/docs/administration/updating-device42.mdx b/docs/administration/updating-device42.mdx index a75bd3015..e4b9d2cff 100644 --- a/docs/administration/updating-device42.mdx +++ b/docs/administration/updating-device42.mdx @@ -113,8 +113,3 @@ sources={{ Device42 RCs are updated automatically as long as they are connected to a Device42 MA. Updates to the MA instance include updates to your RC(s), which are pushed out automatically as part of the regular Device42 update process. By keeping your main Device42 instance up to date, you ensure that your RCs are also up to date. -## Migrating Existing Power Appliance Jobs to a Remote Collector - -It is possible to use existing tools to migrate jobs that were created for the original, standalone power appliance to RCs. - -Follow the [Power Job Migration Guide](/infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.mdx) to migrate jobs to your choice of RC(s). diff --git a/docs/getstarted/using-device42/faqs.mdx b/docs/getstarted/using-device42/faqs.mdx index 502ba1fd7..88aabb677 100644 --- a/docs/getstarted/using-device42/faqs.mdx +++ b/docs/getstarted/using-device42/faqs.mdx @@ -63,10 +63,6 @@ Current releases of Device42 support **all** discovery jobs, including WMI and P RCs will only automatically update when an RC update coincides with an MA update. ::: -## How Do I Migrate Existing Power Appliance Jobs to a Remote Collector? - -You can use existing tools to migrate jobs that were created for the original standalone power appliance to a new RC of your choosing. Simply follow the [Power RC Setup and Existing Job Migration](infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.mdx) guide. - ## How Do I Add Blade Servers to Device42? The Device42 Support Portal article, [How to represent blade servers in Device42](https://support.device42.com/hc/en-us/articles/222221468-How-to-represent-blade-servers-in-device42#:~:text=When%20adding%20a%20new%20device,the%20blade%20server%20belongs%20to.), discusses this in detail. diff --git a/docs/infrastructure-management/devices/device-parts-tab.mdx b/docs/infrastructure-management/devices/device-parts-tab.mdx index 0c89df771..78540d83c 100644 --- a/docs/infrastructure-management/devices/device-parts-tab.mdx +++ b/docs/infrastructure-management/devices/device-parts-tab.mdx @@ -26,4 +26,4 @@ Click the **expand icon** to open a list page view of all parts associated with }} /> -See [Managing Spare Parts](../parts-and-parts-slots/managing-spare-parts.mdx) for more information. +See [Manage Parts](../parts-and-parts-slots/managing-spare-parts.mdx) for more information. diff --git a/docs/infrastructure-management/parts-and-parts-slots/importing-part-models.mdx b/docs/infrastructure-management/parts-and-parts-slots/importing-part-models.mdx index 56a8f2d30..d25fadae7 100644 --- a/docs/infrastructure-management/parts-and-parts-slots/importing-part-models.mdx +++ b/docs/infrastructure-management/parts-and-parts-slots/importing-part-models.mdx @@ -1,18 +1,20 @@ --- -title: "Importing Part Models" -sidebar_position: 1 +title: "Import Part Models" +sidebar_position: 3 --- import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -This document explains how to import part models using API Imports. For a detailed explanation of part models and parts, see the [Part Model Templates](infrastructure-management/parts-and-parts-slots/part-model-templates.mdx). +This page explains how to import part models using the spreadsheet import tool under **Tools > Imports/Exports (xls)**. The process involves downloading a sample template, populating it with your data, and uploading it back to Device42. -## Data Example +For information on port layouts and port templates for part models, see [Part Model Templates](/infrastructure-management/parts-and-parts-slots/part-model-templates.mdx). -The sample data in the spreadsheet below is our starting point for this import. This data was exported from a legacy system into CSV format. +## Sample Data -![Sample parts data spreadsheet](/assets/images/importing-part-models/sample-parts-data.png) +The example below shows a spare parts inventory exported from a legacy system into CSV format, including columns for type, part name, quantity, location, and vendor. This is the source data you will map to the Device42 import template. + +![Sample parts data spreadsheet showing spare parts inventory](/assets/images/importing-part-models/sample-parts-data.png) ## Download Sample Spreadsheet @@ -26,7 +28,7 @@ Navigate to **Tools > Imports/Exports (xls)**, find **Part Models - Create/Updat }} /> -## Understanding Column Comments +## Column Comments Hover over the upper-right corner of the heading cell in each column to see details about the field. These tooltips indicate whether fields are required, optional, or provide additional context. @@ -40,9 +42,9 @@ The spreadsheet includes additional part model type parameters specific to CPU, Update the sample spreadsheet with your part model data from the CSV export. Since these are new part models, only the `type` field is required. You can delete unused parameters from the sheet or leave them blank. -![Populated sample spreadsheet with part model data](/assets/images/importing-part-models/populated-sample-sheet.png) +Note the additional parameters added for CPU and RAM models. -Notice the additional parameters that have been added for CPU and RAM models. +![Populated sample spreadsheet with part model data](/assets/images/importing-part-models/populated-sample-sheet.png) ## Choose File and Import @@ -58,7 +60,7 @@ Navigate to **Tools > Imports/Exports (xls)**, browse to your populated file, an ## Import Results -Device42 displays the status of the import. If there are any issues, the results will show "The following were not added..." with specific error details. Review the results carefully, as any problems (such as missing required parameters) are usually clearly stated. +Device42 displays the status of the import. If there are any issues, the results will show `The following were not added...` with specific error details. Review the results carefully, as any problems such as missing required parameters are usually clearly stated. -## Verifying Imported Parts Models +## Verify Imported Part Models -Navigate to **Datacenter > Parts > Model List** to view all the parts models that were imported in the previous step. +Navigate to **Infrastructure > Parts > Model List** to view all the part models that were imported. Parts > Model List** to view all the parts models tha }} /> -To validate the import, examine a few of the imported items: +You can click into individual models to validate the imported data: **Hard Disk Drive (HDD) Model:** @@ -111,3 +113,5 @@ To validate the import, examine a few of the imported items: dark: useBaseUrl('/assets/images/importing-part-models/patch-cable-part-model-detail-dark.png'), }} /> + +To add actual parts to the inventory for these models, see [Import Parts](/infrastructure-management/parts-and-parts-slots/importing-parts.mdx). diff --git a/docs/infrastructure-management/parts-and-parts-slots/importing-parts.mdx b/docs/infrastructure-management/parts-and-parts-slots/importing-parts.mdx index d3652267b..b355c5efd 100644 --- a/docs/infrastructure-management/parts-and-parts-slots/importing-parts.mdx +++ b/docs/infrastructure-management/parts-and-parts-slots/importing-parts.mdx @@ -1,16 +1,14 @@ --- -title: "Importing Parts" -sidebar_position: 2 +title: "Import Parts" +sidebar_position: 4 --- import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -This document explains how to import parts using the Spreadsheets Import tool found under **Tools > Imports/Exports (xls)**. +This page explains how to import parts using the spreadsheet import tool under **Tools > Imports/Exports (xls)**. It builds on the part models imported in [Import Part Models](/infrastructure-management/parts-and-parts-slots/importing-part-models.mdx) and shows how to add parts with serial numbers and room assignments. -## Importing Part Models vs. Importing Parts - -Please see [Managing Spare Parts](infrastructure-management/parts-and-parts-slots/part-model-templates.mdx) for an explanation of part models vs. parts in Device42. +## Import Options Both parts and part models can be created using the **Parts - Create/Update Parts** import, whereas the **Part Models - Create/Update Part Models** import only creates models. @@ -24,9 +22,7 @@ Both parts and part models can be created using the **Parts - Create/Update Part ## Download Current Data -This document demonstrates how to add parts to existing part models, building on the imported models covered in the [Importing Part Models document](infrastructure-management/parts-and-parts-slots/importing-part-models.mdx). - -Go to **Tools > Imports/Exports (xls)** and download the current data for spare part models as highlighted below. +Go to **Tools > Imports/Exports (xls)** and download the current data for spare part models. The export includes the part model IDs you need when creating parts — keep this sheet open to reference them when populating the import file. Imports/Exports (xls)** and download the current data for spare }} /> -A current data export sheet is shown below. Creating parts from existing part models requires the part model ID. Keep this sheet open. - ![Current data export spreadsheet](/assets/images/importing-parts/current-part-model-data-3.png) ## Download Sample File @@ -58,13 +52,13 @@ Use the data from the current data export to help populate the parts import. ## Populate the Sample Sheet -Add a column for `partmodel_id` and populate the sample spreadsheet to add new parts to two of the existing part models you created. Add the serial numbers manually or using a laser handheld scanner (see below). +Add a column for `partmodel_id` and populate the sample spreadsheet to add new parts to existing part models. Add the serial numbers manually or using a handheld scanner (see the [Handheld Scanner](#handheld-scanner) section). -This import creates the following: +For example, this import creates the following: - For `partmodel_id` `211` (name `3.5" 2TB Dell Drives`): Four line items with assignments and serial numbers (unique line items are required to track serial numbers) -- For `partmodel_id` `219` (name `4GB PC3 8500R`): Two line items with assignments (since you don't need to track serial numbers for these items, you are only tracking room assignment and count) +- For `partmodel_id` `219` (name `4GB PC3 8500R`): Two line items with assignments (serial numbers are not tracked for these items — only room assignment and count) Save the file and import it. @@ -72,11 +66,11 @@ Save the file and import it. ## Handheld Scanner -You can use a DBPOWER scanner purchased on Amazon, which works well for this purpose. It comes with a USB receiver and can be programmed to automatically go to the next row in Excel, making it very quick and easy to capture serial numbers or other bar codes. +You can use a barcode scanner with a USB receiver to capture serial numbers directly into the spreadsheet. The scanner can be programmed to automatically advance to the next row in Excel after each scan, making it quick to capture serial numbers or other barcodes. ## Import Results -Go to **Tools > Imports/Exports (.xls)**, choose your file, and click **Import**. The results of the import are shown below. +Go to **Tools > Imports/Exports (xls)**, choose your file, and click **Import**. Imports/Exports (.xls)**, choose your file, and click **Import** }} /> -Let's look at these new parts in the UI. - -The new parts appear on separate line items, as these are the unique line items needed for tracking serial numbers. +The new parts for `partmodel_id` `211` appear on separate line items, as unique line items are required to track serial numbers. -The new parts appear on two lines. Since you're not tracking serial numbers, you only need two lines to track the room assignments for these RAM modules. +The new parts for `partmodel_id` `219` appear on two lines. Since serial numbers are not being tracked, two lines are sufficient to record the room assignments for these RAM modules. -## Parts Model vs. Parts - -**What is a parts model?** - -A parts model is a template that devices are deployed from. Parts model templates hold information that describes each unique part, such as the model number, size, type (for HDD or RAM), and number of cores (for CPU). - -**What is a part?** - -- A part is added as an actual CI created from a parts model (template). - -- A part is a specific instance of a CI, like a hard disk, memory chip, or NIC card. - -- A part may be placed into a **part slot** on a hardware chassis. - -- Part assignments can be tracked. For example, you can track where a part is located or being used. A part can be assigned to a storage room or device, or assigned a status of **In RMA**, **In Transit**, or **Storage Rack (or Cabinet)**. - -- Before an actual part can be added to Device42, a model must first be created. Then, parts can be added as line items. +Part assignments can be tracked so you can record where a part is located or in use. Before adding a part, a part model must exist first. For the full list of assignment options, see [Add Parts to Inventory](#add-parts-to-inventory). ### Parts Counts -Every part has a specific "count" which tracks the part inventory, also known as the number of units of that part "in stock". When assigning parts (or spare parts) to specific devices, each part assigned will subtract one unit (or the number used if greater than 1) from the parts count inventory for that part. Ensure your part has a sufficient parts count inventory (greater than 0) before attempting to assign it. Should you have trouble, verify the part has sufficient inventory, and if needed, increase the inventory as appropriate. +Every part has a **count** that tracks the number of units in stock. When you assign a part to a device, the count decreases by one (or more, if multiple units are used). Before assigning a part, ensure the count is greater than 0. If you have trouble assigning a part, verify the inventory count and increase it if needed. -## Parts Menu +## Add a Part Model -The management features for parts and parts models are located in the Device42 main menu under **Infrastructure > Hardware > Parts**, as shown below. +The management features for parts and parts models are located under **Infrastructure > Hardware > Parts**. -### Adding a Parts Model - -Add a new parts model or type by adding a **Parts Model**. As an example, let's add a new parts model. - -1. From the main menu, navigate to **Infrastructure > Hardware > Parts > Model List** and, at the top right of the list, choose **Create**. +1. From the main menu, navigate to **Infrastructure > Hardware > Parts > Model List** and click **Create** in the top right. -2. Choose a part **Type** or create a custom type by clicking the **plus sign icon** (to the right of the dropdown). The available selections for the **Type** field include **CPU**, **RAM**, **Hard Disk**, **Disk Drive**, **Physical Memory**, **NIC**, **HBA**, **SCSI**, **Serial Bus**, **Riser Card**, **FPGA**, **Cable**, and **PSU**. Options like **CPU**, **RAM**, and **Hard Disk** have custom attributes (see example below), while **NIC**, **HBA**, **SCSI**, **Serial Bus**, and custom types have a **Connectivity** attribute. +2. Choose a part **Type** or create a custom type by clicking the **plus sign icon** (to the right of the dropdown). The available types are **CPU**, **RAM**, **Hard Disk**, **Disk Drive**, **Physical Memory**, **NIC**, **HBA**, **SCSI**, **Serial Bus**, **Riser Card**, **FPGA**, **Cable**, and **PSU**. + + :::note + **CPU**, **RAM**, and **Hard Disk** types have custom type-specific attributes (see [CPU, RAM, and Hard Disk Attributes](#cpu-ram-and-hard-disk-attributes) below). **NIC**, **HBA**, **SCSI**, **Serial Bus**, and custom types have a **Connectivity** attribute. + ::: 3. Give the parts model a **Name** and fill in any appropriate information you have, such as the **Model Number**, the **Part Number**, and the **Manufacturer**. -4. Click **Save** to finish adding your part. If you would like to add inventory of this part type, see the **Adding Parts to Inventory** section below. +4. Click **Save**. To add inventory for this part type, see [Add Parts to Inventory](#add-parts-to-inventory). ### CPU, RAM, and Hard Disk Attributes -It is important to note that each part type contains type-specific attributes. For example, the CPU, RAM, and Hard Disk types each have their own specific attributes: +Each part type has type-specific attributes. The CPU, RAM, and Hard Disk types each have their own fields: **CPU** @@ -125,11 +109,11 @@ It is important to note that each part type contains type-specific attributes. F }} /> -### Adding Parts to Inventory +### Add Parts to Inventory -After creating a parts model, the actual parts can be added via **Add New Part**. +After creating a part model, add parts using the **+ Add New Part** link. -1. From any Parts Model view screen (navigate to **Infrastructure > Hardware > Parts > Model List** and click on an existing part), click the **+ Add New Part** link at the bottom of the screen in the **Parts** section: +1. Navigate to **Infrastructure > Hardware > Parts > Model List** and click an existing part model. At the bottom of the screen, click the **+ Add New Part** link in the **Parts** section. -**A few notes about the Add Part screen:** +Note the following about the **Add Part** form: - Each line item added can contain an inventory of one or more of a given part, and must have an **Assignment** (specifying where the part is checked out or stored). - All the parts in a given line item must share the same **Assignment**. @@ -161,10 +145,10 @@ After creating a parts model, the actual parts can be added via **Add New Part** - **Storage Rack (or Cabinet)** - **Port** - **Asset** -- If you choose **Storage Room** or **Device** assignments, you have the option to choose existing objects (where an object is a Storage Room or Device) or to create new objects. +- If you choose **Storage Room** or **Device** assignments, you can select an existing storage room or device, or create a new one. - If you are tracking serial numbers, you can only have one part per line. -You can also add a part via the Parts List screen. See the section below. +You can also add a part via the Parts List screen. See [The Parts List Screen](#the-parts-list-screen). ## The Parts List Screen @@ -180,13 +164,13 @@ Click any entry to view the details of that part. }} /> -The Parts List can be thought of as the "master inventory", which shows each part being tracked by Device42. The list is similar to other lists in Device42, including an **Actions** menu and the ability to search, sort, and filter for specific list items. +The Parts List is the master inventory view, showing each part being tracked by Device42. The list is similar to other lists in Device42, including an **Actions** menu and the ability to search, sort, and filter for specific list items. You can also add parts from the Parts List by clicking **Create** in the top-right corner. ### Parts Associated With a Device -As shown below, parts associated with a device can be viewed from the **Parts** section of a device record. Here, you have the ability to edit the fields of the part or parts associated with the device, as well as to **Add another Part**. The **Add another Part** link provides an alternate way to add or create a part assigned to a device. +Parts associated with a device can be viewed from the **Parts** section of a device record. From here, you can edit the fields of associated parts and use the **Add another Part** link to add or create a part assigned to the device. -### Setting Up Alerts for Low Inventory Levels +### Set Up Alerts for Low Inventory Levels To set up an alert, navigate to the main menu, **Analytics > Setup Alerts**, and click the **Create** button in the upper right. You can set up alerting rules for either an individual part model (as in the example below) or against any parts model (that is, the rule will trigger if any parts model has an inventory level that meets the rule condition). @@ -208,6 +192,8 @@ To set up an alert, navigate to the main menu, **Analytics > Setup Alerts**, and }} /> -In the example below, the rule will trigger if the inventory count of Intel XEON machines falls below 10. (For rules that apply to parts, leave the **Seconds Before Action** at the default of `0`.) +In the example above, the rule will trigger if the inventory count of Intel XEON machines falls below 10. (For rules that apply to parts, leave the **Seconds Before Action** at the default of `0`.) In this case, an email will be sent to `hal@device42.com` when the rule triggers. You can add multiple emails separated by commas or semicolons. You can also set the rule up so that an email is sent if enough parts are added to bring the inventory count back above the trigger level or so that escalation emails are sent if no one acknowledges the alert. + +To import parts or part models in bulk, see [Import Part Models](/infrastructure-management/parts-and-parts-slots/importing-part-models.mdx) and [Import Parts](/infrastructure-management/parts-and-parts-slots/importing-parts.mdx). diff --git a/docs/infrastructure-management/parts-and-parts-slots/part-model-templates.mdx b/docs/infrastructure-management/parts-and-parts-slots/part-model-templates.mdx index 295e23b9e..97dd7bd19 100644 --- a/docs/infrastructure-management/parts-and-parts-slots/part-model-templates.mdx +++ b/docs/infrastructure-management/parts-and-parts-slots/part-model-templates.mdx @@ -1,18 +1,18 @@ --- title: "Part Model Templates" -sidebar_position: 4 +sidebar_position: 2 --- import ThemedImage from '@theme/ThemedImage'; import useBaseUrl from '@docusaurus/useBaseUrl'; -Device42 supports parts having ports, parts slots, and more. For more information about adding parts slots (or blade slots) to devices, read the [Device - Parts Slots](../devices/device-parts-slots.mdx) documentation. +Part model templates define the structure of a hardware component type and optionally include port layouts and port templates. This page focuses on the port-related aspects of part model templates — how to enable port support, configure port templates, and auto-create ports on new devices. -## Parts Model Templates +For the general workflow of creating part models and adding parts to inventory, see [Manage Parts](/infrastructure-management/parts-and-parts-slots/managing-spare-parts.mdx). For information on adding parts slots or blade slots to devices, see [Device - Parts Slots](/infrastructure-management/devices/device-parts-slots.mdx). -**Parts Models** are templates that define parts. You can create parts templates that optionally include ports. +## Create a Part Model Template -Navigate to **DataCenter > Parts > Model list** and click **Create** in the upper right: +Navigate to **Infrastructure > Hardware > Parts > Model List** and click **Create** in the top right. -From this screen, you can add a new parts model: +Fill in the part model details on the creation screen. -You can add a new part type classification if the type of part you are adding doesn't already exist. Do this by clicking the **plus sign icon** (+) next to **Type**. +If the part type you need doesn't exist, add a new type by clicking the **plus sign icon** next to **Type**. -**The Supports Ports Checkbox** +## Supports Ports -While creating a part type, select the **Supports Ports** checkbox if you'd like to define ports and a port layout. You may set the **Supports Ports** flag while creating a new part or modifying a part. +While creating a part type, select the **Supports Ports** checkbox to define ports and a port layout. You can set the **Supports Ports** flag when creating or editing a part. :::note -You will not find the **Supports Ports** option on parts designated ‘disk drives’ or ‘physical memory’. +The **Supports Ports** option is not available for parts designated as disk drives or physical memory. ::: -Parts (with or without ports), once defined, may optionally be placed into **parts slots**, or if desired, a parts slot may be left empty. +Parts (with or without ports), once defined, may optionally be placed into **parts slots**, or a parts slot may be left empty. +## Port Templates -### Port Templates +A port template may include a name prefix, a naming scheme, and a port type. Ports may also be added in bulk and automatically named based on the template configuration. -A port template may include a name prefix, a name template that configures the port naming scheme, and a port type. Ports may also be added in bulk and automatically named based on information configured in the template. +You can auto-create ports when creating a new device. If the **Add Ports When Creating Device** checkbox is selected on the hardware model template, the new device is created with all its model-defined ports. Following a discovery run, Device42 automatically adds discovered connections to these ports. -You may now elect to **auto-create ports** during the creation of a new device. If the **Add Ports When Creating Device** checkbox is checked on the chosen hardware model template, the new device will be created with all its model-defined ports. Following a discovery run, Device42 automatically adds discovered connections to these ports. +## Edit a Part Model Template -### Edit Parts Model Templates - -Edit any existing parts model by viewing it and choosing the **Edit** button in the upper-right corner: +To edit an existing part model, open it and click the **Edit** button in the upper-right corner. - -## Viewing Discovered Sensors - -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**: - - diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx b/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx index 56763feef..e82e065f8 100644 --- a/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx +++ b/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx @@ -6,15 +6,17 @@ sidebar_position: 1 import ThemedImage from '@theme/ThemedImage'; import useBaseUrl from '@docusaurus/useBaseUrl'; +This page explains how to set up power monitoring for PDUs in Device42 using SNMP discovery. It covers prerequisites, discovery job configuration, and capacity recommendations. + :::note -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. +The features described in this section require a **Power and Environmental Monitoring** license. Visit the [Device42 pricing page](https://www.device42.com/pricing/) to request a quote. ::: -## Power Unit Autodiscovery +## Set Up Power Unit Discovery -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. +Install and configure a Remote Collector before proceeding. See [Remote Collector](/auto-discovery/remote-collector-rc/#installation-and-configuration) for instructions. -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`. +The process of discovering power-enabled PDUs is similar to [Device42 Network Discovery](/auto-discovery/network-auto-discovery.mdx). Navigate to **Discovery > SNMP** and enter an IP address range and a port if not using the default `161`. -Add any SNMP authentication information, depending on whether you are using v1, v2c, or v3: +Add SNMP authentication information depending on whether you are using v1, v2c, or v3. -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. - +Select **Enable monitoring for discovered PDU devices**. You can also set the polling interval for PDUs discovered by this job using the **Polling Interval** dropdown, which controls how frequently monitoring polls each PDU. -### Viewing Discovered Sensors +### View Discovered Sensors -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. +Environmental sensors attached to PDUs are discovered automatically during the SNMP discovery run. When sensors are discovered, they are created with asset records in Device42. Navigate to **Resources > Assets > All Assets** and filter by `Type="Sensor"` to see all PDU-attached sensors. -### Geist Power Unit Serial Number Discovery - -As of version 19.08, Device42 uses a different OID to discover power unit serial numbers for Geist PDUs, which now match the physical serial numbers on the devices. + -If a Geist power unit was discovered before this change and the [device matching level](/auto-discovery/unprocessed-device-records.mdx#device-matching-level) is not set to **Moderate**, a separate device record will be created. If matching is set to **Moderate** and the **Give precedence to hostname** option is not selected, the serial number will be updated but not the name of the device or power unit. ## Capacity Considerations -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. +Monitoring is resource-intensive, and each monitoring appliance is limited in the number of PDUs, infeeds, and outlets it can handle. The primary constraint is the number of SNMP polls that can be completed within the selected polling interval. -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. +For example, at 5-minute intervals (default), Device42 recommends one monitoring appliance per 200 PDUs. At 1-minute intervals, assume 40 PDUs per appliance. If your network is slow, reduce the number of PDUs per appliance. You can deploy as many monitoring appliances as needed with no additional license cost. diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/index.mdx b/docs/infrastructure-management/power-and-environmental-monitoring/index.mdx index 61520bd3c..b0c501e94 100644 --- a/docs/infrastructure-management/power-and-environmental-monitoring/index.mdx +++ b/docs/infrastructure-management/power-and-environmental-monitoring/index.mdx @@ -5,9 +5,11 @@ title: "Power and Environmental Monitoring" import ThemedImage from '@theme/ThemedImage'; import useBaseUrl from '@docusaurus/useBaseUrl'; -In this section, we discuss Power and Environmental Monitoring and Control using Device42. Use the search bar on the left to access specific topics. +Device42's Power and Environmental Monitoring module lets you monitor power consumption and environmental conditions across your PDUs and infrastructure. Use the sidebar to navigate to specific topics. -Please note that these features require the purchase of at least the Power Monitoring module. If you have not purchased this module, you will not see the features described in this section. +:::note +The features described in this section require the **Power Monitoring** module license. If you have not purchased this module, these features will not be visible. +::: - - - diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/manage-monitored-ips.mdx b/docs/infrastructure-management/power-and-environmental-monitoring/manage-monitored-ips.mdx index 64e2c7fb7..252bc4d32 100644 --- a/docs/infrastructure-management/power-and-environmental-monitoring/manage-monitored-ips.mdx +++ b/docs/infrastructure-management/power-and-environmental-monitoring/manage-monitored-ips.mdx @@ -18,9 +18,9 @@ To view all power units, navigate to **Infrastructure > Hardware > Power Units** ## Enable and Disable Monitoring -Select one or more power units that you no longer need to be monitored on the list page. Choose **Disable monitoring for selected devices, but keep data** or **Disable monitoring for selected devices and delete data**, depending on what you want to do with the already-discovered data. +Select one or more power units from the list page and choose **Disable monitoring for selected devices, but keep data** or **Disable monitoring for selected devices and delete data**, depending on what you want to do with the existing data. -Re-enable monitoring with the **Enable monitoring for selected Power Units** bulk action. +To re-enable monitoring, select the **Enable monitoring for selected Power Units** bulk action. -A success popup notification will be displayed; otherwise, you'll see a failure notification with a reason for the failure. +A success notification is displayed on completion, or a failure notification with a reason if the action did not succeed. ![Success message](/assets/images/manage-monitored-power-units/enable-monitoring-success.png) ## View Periodic Jobs -To view a list of all periodic jobs that are configured to run, navigate to **Analytics > Periodic Jobs** from the main menu. Here, you will see a list of all periodic jobs, which can be viewed or easily deleted via the **Action** menu. +To view all periodic jobs configured to run, navigate to **Analytics > Periodic Jobs**. From here, you can view or delete jobs via the **Action** menu. diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/power-monitoring-and-control.mdx b/docs/infrastructure-management/power-and-environmental-monitoring/power-monitoring-and-control.mdx index 49f9a737a..352a3e2e0 100644 --- a/docs/infrastructure-management/power-and-environmental-monitoring/power-monitoring-and-control.mdx +++ b/docs/infrastructure-management/power-and-environmental-monitoring/power-monitoring-and-control.mdx @@ -6,25 +6,25 @@ sidebar_position: 4 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -This section describes Device42's power monitoring capabilities. If you are just getting started, you'll want to first set up one or more [Remote collectors (RCs)](auto-discovery/remote-collector-rc.mdx). +This page describes Device42's power monitoring capabilities, including power heatmaps, rack-level charts, and PDU-level power data. The visualizations on this page are only populated after PDUs have been discovered and monitoring has been enabled. See [Getting Started with Power and Environmental Monitoring](/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.mdx) if you haven't set this up yet. ## Power Heatmaps ![Power Heatmaps](/assets/images/media_1424599764800.png) -When you navigate to a room layout view, for example, by navigating to **DataCenter > Rooms**, choosing a room, and clicking **Show**, the racks are color-coded to show both space and power availability. Each power-enabled rack displays a rectangular bar graph representing each infeed of each PDU in the rack. These bars are color-coded, representing the amount of power currently in use over the infeed divided by the power capacity of that infeed. +When you navigate to a room layout view by going to **Rooms**, selecting a room, and clicking **Show**, the racks are color-coded to show both space and power availability. Each power-enabled rack displays a bar graph representing each infeed of each PDU in the rack. The bars are color-coded to show the amount of power in use on the infeed relative to its capacity. ![](/assets/images/media_1424600582457.png) -If you hover over a rack, you will see a popup. The **Power/Utilization Charts** hyperlink takes you to a display showing the power history for each infeed and outlet. +If you hover over a rack, a popup appears. The **Power/Utilization Charts** link shows the power history for each infeed and outlet. ## Rack-Level Power Visualization -You can view the visualizations under the **Power Charts** tab from any rack with a power unit that has discovered data. +View power visualizations under the **Power Charts** tab from any rack with a power unit that has discovered data. ![Rack-level power visualization](/assets/images/media_1416079634123.png) -Here you can see the last 24 hours of power data for each infeed and outlet for each PDU in the rack. If you want to look at a different time (for example, the last week, month, or year), click the **Show Settings** button. +The chart shows the last 24 hours of power data for each infeed and outlet for each PDU in the rack. To view a different time range (for example, the last week, month, or year), click **Show Settings**. -In the dialog box above, you can move sliders for the period (set for the past day in the example above). +Use the sliders to set the time period and data density. A higher data density returns more data points but may take longer to load. -You can also specify the data density. A higher data density brings back more data points but may also take a little longer to retrieve. +You can also specify the data type. When you configure a discovery job for a set of PDUs, one option is the polling interval. For example, if polling is set to every minute, the database stores minute-by-minute data. When you request a week's worth of data, Device42 aggregates the data points based on the selected type: -Last, you can specify the type of data to retrieve. This option requires some explanation: When you define an autodiscovery spec for a set of PDUs, one option is the polling interval in minutes. For example, if you set it to poll every minute, the database will hold minute-by-minute data. But if you request a week's data, Device42 will not bring back every individual data point; instead, it will aggregate the data points based on the data type. The **Average** setting brings back average data points, the **Maximum** setting brings back the maximum value observed for each set of data points, and the **Minimum** setting brings back the minimum value. +- **Average:** Returns the average value for each set of data points. +- **Maximum:** Returns the maximum value observed for each set of data points. +- **Minimum:** Returns the minimum value observed for each set of data points. ![](/assets/images/media_1416079778471.png) -As you observe the data, you may see spikes or observe other data patterns that cause you to want to inspect the data in more detail. You can do this by highlighting the period you want to investigate. +To inspect a specific period in more detail, click and drag to highlight the time range you want to investigate. ![](/assets/images/media_1416079871175.png) -After you release the mouse button, the view expands to the highlighted period. +After releasing the mouse button, the view expands to the highlighted period. ![](/assets/images/media_1416079930654.png) -Rack-level power charts are also available from the Rack View page if you click the **Power** button at the top right of the page. +Rack-level power charts are also available from the Rack View page by clicking the **Power** button in the top right. ## PDU-Level Power Data @@ -70,7 +72,7 @@ Rack-level power charts are also available from the Rack View page if you click }} /> -When you drill into a PDU, you can see power details for both **Infeeds** and **Ports** (outlets). In the example, the PDU has three infeeds and 24 outlets as visualized under the **Connectivity** tab: +When you open a PDU, you can see power details for both **Infeeds** and **Ports** (outlets), shown under the **Connectivity** tab. -For each infeed and each outlet, you can see a **Power Draw**. This is the amount of power that was drawn by the infeed or outlet the last time the PDU was polled via SNMP. As mentioned earlier, you can set the polling interval via the Device42 main menu, **Discovery > SNMP**. - -For the infeeds, the **Rated Power** is autodiscovered. +For each infeed and outlet, **Power Draw** shows the amount of power drawn the last time the PDU was polled via SNMP. You can set the polling interval under **Discovery > SNMP**. For infeeds, **Rated Power** is discovered automatically. -For each outlet, you can see the **Override Watts** and the **Bootstrap Power**, in addition to the **Power Draw.** The Bootstrap Power column shows the power required for this outlet at boot time. In the PDU header section at the top, the Bootstrap Power for the PDU is the sum of the Bootstrap Power for each of the outlets. +For each outlet, you can also see **Override Watts** and **Bootstrap Power**. **Bootstrap Power** is the power required for the outlet at boot time. The PDU's total Bootstrap Power is the sum of all outlet Bootstrap Power values. -By default, the **Bootstrap Power** column will be empty if there is no device connected. If there is a device connected, by default, the Bootstrap Power will show the nameplate watts of the hardware model of the device. Sometimes, however, you may wish to use a different number for the Bootstrap Power. If so, you would enter that number in the **Override Watts** field. In the example above, the user has entered 30 watts as the Override Watts for each of the outlets above. There are no connected devices in the above example; however, even if there were connected devices, Override Watts would still be the value used for the Bootstrap Power column. You can also have a mix of outlets, where some outlets get their Bootstrap Power from the device hardware model and some have an Override Watts value. +By default, **Bootstrap Power** is empty if no device is connected. If a device is connected, Bootstrap Power defaults to the nameplate watts of the device's hardware model. To use a different value, enter it in the **Override Watts** field — this overrides the hardware model value even if a device is connected. You can have a mix of outlets, where some use the hardware model value and some use an Override Watts value. -If you click the **Power** tab for the PDU, you will see tables and graphs showing the historical power details for the in-feeds and outlets. +Clicking the **Power** tab on a PDU shows tables and graphs of historical power data for infeeds and outlets. ![](/assets/images/media_1416823791271.png) -For the rack detail power page discussed above, you can click **Show Settings** to see historical charts and the minimum, maximum, and average calculations. +From the rack detail power page, click **Show Settings** to view historical charts and minimum, maximum, and average calculations. diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.mdx b/docs/infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.mdx deleted file mode 100644 index bc9e2428a..000000000 --- a/docs/infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.mdx +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: "Power RC Setup and Existing Job Migration" -sidebar_position: 5 ---- - -Converting existing power autodiscovery jobs to the new PowerRC SNMP autodiscovery can be done with the imports/exports tool. - -## Power RC Prerequisite - -First, follow the instructions to setup a Remote Collector (RC) here: [Remote Collector - Installation](/getstarted/deploy-device42/remote-collector-rc-installation.mdx). - -## Migrate Existing Power Appliance Jobs to Power RC - -1. Head to the TOOLS menu --> Import/Export (XLS) - - ![Export current power autodiscovery jobs](/assets/images/import-export-xls.png) -2. Export the current data for “Add Power Autodiscovery Jobs” - - ![Download Current Data](/assets/images/download-current-data.png) -3. Modify the data in cell A1 so that it contains “/api/1.0/auto\_discovery/networks” without the quotes: - - ![Modify data in cell A1](/assets/images/power-xls-config.png) -4. Rename the header in column V from “appliance” to “remote\_collector\_id” - - ![Rename header in column V](/assets/images/power-xls-column-rename.png) -5. Delete all of the data under the column V header and replace them with Remote Collector IDs. The IDs can be found by navigating to Tools > Autodiscovery > Remote Collectors: - - ![Select remote collector to view](/assets/images/select-rc-view.png) -6. Import the file on the same page that it was exported from: - - ![Re-import the modified XLS on the import/export page](/assets/images/import-modified-xls.png) -7. When the data has been imported successfully the jobs will no longer appear under Tools > Autodiscovery > Power (SNMP). The last step is to go to Tools > Autodiscovery > SNMP and edit the jobs to enable monitoring: - - ![Jobs moved after successful import](/assets/images/enable-monitoring-discovered-pdu.png) diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/unit-display-settings.mdx b/docs/infrastructure-management/power-and-environmental-monitoring/unit-display-settings.mdx index 7b77c40bd..732ece6f5 100644 --- a/docs/infrastructure-management/power-and-environmental-monitoring/unit-display-settings.mdx +++ b/docs/infrastructure-management/power-and-environmental-monitoring/unit-display-settings.mdx @@ -24,21 +24,19 @@ The two categories that control unit display are the **Power Conversion Options* ### Power Unit Conversion Options -Changing the selection in the Power Conversion Options dropdown controls how power consumption values are displayed by Device42. +The **Power Conversion Options** dropdown controls how power consumption values are displayed. The available options are: -The available conversion options are: - -- **Do not convert:** This default option displays power values exactly as they were returned via SNMP, without any conversion. -- **Convert Amps to Watts:** Selecting this option causes Device42 to convert and display all returned power values in Watts. -- **Convert Watts to Amps:** Selecting this option causes Device42 to convert and display all returned power values in Amps. +- **Do not convert:** Default. Displays power values exactly as returned via SNMP, without conversion. +- **Convert Amps to Watts:** Converts and displays all power values in Watts. +- **Convert Watts to Amps:** Converts and displays all power values in Amps. ### Default Voltage -The **Default Voltage (integer required)** setting allows you to specify the default voltage for Device42 to use in calculations, **only** if a value is not returned via SNMP. +The **Default Voltage (integer required)** setting lets you specify the default voltage for Device42 to use in calculations, only if a value is not returned via SNMP. ### Display Temperature Values as Centigrade The **Display temperature values as Centigrade** checkbox controls the temperature display: -- **Checked:** Converts all temperature values from Fahrenheit (°F) values to Celsius (°C) values and changes the display units to Celsius. -- **Unchecked (Default):** Displays SI / Imperial units (°F). No unit conversion is performed. +- **Checked:** Converts all temperature values from Fahrenheit (°F) to Celsius (°C). +- **Unchecked:** Default. Displays values in Fahrenheit (°F) with no conversion. diff --git a/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx b/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx index b098bd821..5bad7dfb2 100644 --- a/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx +++ b/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx @@ -53,6 +53,12 @@ Please note that we may not support all models from each listed vendor. We recom -We're always happy to add support for a customer's specific make, model, or iPDU. Simply [generate an SNMPWALK](administration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx) for your particular device model, and send that SNMP walk to us (along with your request is best!). +We're always happy to add support for a customer's specific make, model, or iPDU. Simply [generate an SNMPWALK](/administration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx) for your particular device model and send it to us along with your request. -Our development team is happy to add support to Device42 within the next few releases _(we'll work with you to let you know a specific timeframe, but we release often!)_. +Our development team is happy to add support to Device42 within the next few releases. + +## Geist PDU Serial Number Discovery + +As of version 19.08, Device42 uses a different OID to discover power unit serial numbers for Geist PDUs, which now match the physical serial numbers on the devices. + +If a Geist power unit was discovered before this change and the [device matching level](/auto-discovery/unprocessed-device-records.mdx#device-matching-level) is not set to **Moderate**, a separate device record will be created. If matching is set to **Moderate** and the **Give precedence to hostname** option is not selected, the serial number will be updated but not the name of the device or power unit. diff --git a/docusaurus.config.js b/docusaurus.config.js index 555bf0f00..cbd19060a 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -1078,12 +1078,12 @@ const config = { from: ['/parts-and-parts-slots/part-model-templates/', '/spare-parts-management/models-and-parts/'], }, { - to: '/infrastructure-management/parts-and-parts-slots/parts-slots/', - from: ['/parts-and-parts-slots/parts-slots/'], + to: '/infrastructure-management/parts-and-parts-slots/', + from: ['/parts-and-parts-slots/parts-slots/', '/infrastructure-management/parts-and-parts-slots/parts-slots/'], }, { - to: '/infrastructure-management/power-and-environmental-monitoring/environmental-monitoring/', - from: ['/energy-monitoringmanagement/environmental-monitoring/', '/energy-monitoringmanagement/'], + to: '/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring/', + from: ['/energy-monitoringmanagement/environmental-monitoring/', '/energy-monitoringmanagement/', '/infrastructure-management/power-and-environmental-monitoring/environmental-monitoring/'], }, { to: '/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring/', @@ -1098,8 +1098,8 @@ const config = { from: ['/energy-monitoringmanagement/power-monitoring-and-control/'], }, { - to: '/infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration/', - from: ['/energy-monitoringmanagement/power-rc-setup-job-migration/'], + to: '/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring/', + from: ['/energy-monitoringmanagement/power-rc-setup-job-migration/', '/infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration/'], }, { to: '/infrastructure-management/power-and-environmental-monitoring/unit-display-settings/',