diff --git a/docs/infrastructure-management/buildings-rooms-and-racks/auditing-racks.mdx b/docs/infrastructure-management/buildings-rooms-and-racks/auditing-racks.mdx index b20550f21..49ec3cbe5 100644 --- a/docs/infrastructure-management/buildings-rooms-and-racks/auditing-racks.mdx +++ b/docs/infrastructure-management/buildings-rooms-and-racks/auditing-racks.mdx @@ -3,16 +3,43 @@ title: "Auditing Racks" sidebar_position: 1 --- -To create a list of all devices on a number of racks in Device42 to allow easy auditing, we will first browse to the Racks list view in Device42: +import ThemedImage from '@theme/ThemedImage' +import useBaseUrl from '@docusaurus/useBaseUrl' -![Browse to Racks](/assets/images/2016-02-26-rack-audit-01.png) +You can export rack data from Device42 to an Excel spreadsheet and use a barcode reader to audit physical devices against the records in Device42. -From the Racks list view we will pick the racks we would like to audit against the actual equipment, and from the Action dropdown menu, select "Audit Export for Selected Racks": +1. Navigate to **Infrastructure > DataCenter > Racks**: -![Audit Export Racks](/assets/images/2016-02-26-rack-audit-03.png) + -Save the spreadsheet when prompted and open in Excel. +2. Select the racks you want to audit, then choose **Export Selected Items** from the **Actions** menu: + + + +3. Select **Audit Export for Selected Racks** and click **Export**: + + + +4. Save the spreadsheet when prompted and open it in Excel. ![Audit Spreadsheet](/assets/images/2016-02-26-rack-audit-04.png) -With this spreadsheet open, you will be able to use a barcode reader and scan the devices in a rack by asset tag and compare to the information you have in Device42, updating to reflect changes as you move through the racks! +5. With the spreadsheet open, use a barcode reader to scan devices in the rack by asset tag. Compare the scanned data to the records in Device42 and update the spreadsheet to reflect any changes as you move through the racks. diff --git a/docs/infrastructure-management/buildings-rooms-and-racks/buildings-and-rooms.mdx b/docs/infrastructure-management/buildings-rooms-and-racks/buildings-and-rooms.mdx index a8b36ba21..e9adb4b1f 100644 --- a/docs/infrastructure-management/buildings-rooms-and-racks/buildings-and-rooms.mdx +++ b/docs/infrastructure-management/buildings-rooms-and-racks/buildings-and-rooms.mdx @@ -6,9 +6,9 @@ sidebar_position: 2 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -From the main menu, navigate to the Buildings list page under **Infrastructure > DataCenter > Buildings** to view and enter information about the buildings that house your data centers. In Device42, a room is part of a building. You can add rooms, racks, and other asset details to a building's information. +Device42 lets you model your physical infrastructure by organizing devices and assets into buildings, rooms, and racks. In Device42, a room is part of a building, and racks are part of a room. You can add rooms, racks, and other asset details to a building's record. -Users with the [necessary permissions](/administration/role-based-access-control/index.mdx) can access the [Room Layout View](#room-layout-view) to see how the room layout represents a room and its objects. +Navigate to **Infrastructure > DataCenter > Buildings** to view and manage buildings. Users with the [necessary permissions](/administration/role-based-access-control/index.mdx) can access the [Room Layout View](#room-layout-view) to see a visual representation of a room and its objects. ## Buildings List Page @@ -48,7 +48,7 @@ Click the **Impact Chart** button on the view page to open the chart in a new ta }} /> -The Rooms associated with the Building are clickable links in the room layout view. You can click **Edit** to add or remove Rooms from a building. +Rooms associated with the building are clickable links in the room layout view. Click **Edit** to add or remove rooms from a building. DataCenter > Rooms**, click the **Show** link under the **Layout** column, and select **Turn ON** from the layout view. @@ -228,9 +228,9 @@ You can add any asset type to the room and are not confined to the template obje Racks and other objects can be added via the API or from the **Tools > Imports/Exports** menu. -### Mouse-Over Options +### Hover Options -If you hover over an object, you will see a popup with detailed information about the object. +Hover over an object to see a popup with detailed information about the object. -- **View [name] Power Unit Map:** +- **View [name] Power Unit Map:** Click this link to display a map of the power units in the rack. + /> - **Power/Utilization Charts:** Click this link to display the power history for each input and output. Note that this link is only available if you have the Power Monitoring option. -- **View Connections:** Mouse over the rack displayed in the object popup panel to find this link. Click the link to display a visualization of the PDU connections in the rack. +- **View Connections:** Hover over the rack in the object popup panel to find this link. Click the link to display a visualization of the PDU connections in the rack. -In addition, you can choose to **Show temperature bubbles** or turn it off. +You can also toggle the **Show temperature bubbles** option on or off. -These options are saved in cookies, so you don't have to reselect the combination of options that works best for you when revisiting the page. +These options are saved in cookies, so your preferred settings are restored when you revisit the page. **Usage Heatmap Legend** @@ -354,9 +354,9 @@ In rooms that have temperature information, halo temperature shading around rack The default color value is based on the maximum temperature of the rack and corresponds to the following temperatures: -- **Green:** \<\= 75°F (23.88°C) -- **Yellow:** Between > 75°F (23.88°C) and \<\= 90°F (32.22°C) -- **Red:** > 90°F (32.22°C) +- **Green:** \<\= 75°F (23.88°C) +- **Yellow:** Between > 75°F (23.88°C) and \<\= 90°F (32.22°C) +- **Red:** > 90°F (32.22°C) You can update the high and moderate temperature values from the Racks section under **Tools > Settings > Global Settings**. The room rack view updates accordingly. @@ -370,7 +370,7 @@ You can update the high and moderate temperature values from the Racks section u ### PDU Power Monitoring -If you have the Power Monitoring option, you will see a rectangular bar for each input of every PDU in the rack. These bars are color-coded for power usage and represent the amount of power currently in use divided by the power capacity of the input. Green is high, and red is low. You can change the percentages in **Tools > Settings > Global Settings**. +If you have the Power Monitoring option, you will see a rectangular bar for each input of every PDU in the rack. These bars are color-coded for power usage and represent the amount of power currently in use divided by the power capacity of the input. Green indicates high available capacity, and red indicates low available capacity. You can change the percentages in **Tools > Settings > Global Settings**. ![Heat Maps](/assets/images/wpid6004-media_1424515509781.png) @@ -398,4 +398,3 @@ The following operations are available from the **Actions** dropdown menu on the - **Add Groups**: Select and add a permission group to the selected buildings or rooms. - **Delete Groups**: Select and remove a permission group from the selected buildings or rooms. - **Set Custom Field Value**: Add a populated custom field parameter to the selected buildings or rooms. - diff --git a/docs/infrastructure-management/buildings-rooms-and-racks/impact-charts.mdx b/docs/infrastructure-management/buildings-rooms-and-racks/impact-charts.mdx index 09524c50d..a010423a3 100644 --- a/docs/infrastructure-management/buildings-rooms-and-racks/impact-charts.mdx +++ b/docs/infrastructure-management/buildings-rooms-and-racks/impact-charts.mdx @@ -18,7 +18,9 @@ Click the **Impact Chart** button at the top of the screen: }} /> -Device42's powerful, agentless autodiscovery uses native WMI and SSH in combination with other platform-dependent technologies to identify the details of running services and listening ports, and the relationships between those services and ports or executables and ports. This provides a clear picture of exactly which services or executables are listening on which ports on a machine. Device42 also goes on to capture a point-in-time snapshot of the IP addresses that are connected to each listening port. Should these communicating IP addresses already exist in Device42 and be mapped to a device, the system automatically shows that device when drawing the dynamic impact charts. +Device42's agentless discovery uses native WMI and SSH, along with other platform-dependent technologies, to identify running services, listening ports, and the relationships between them. This provides a clear picture of which services or executables are listening on which ports on a machine. + +Device42 also captures a point-in-time snapshot of the IP addresses connected to each listening port. If those IP addresses already exist in Device42 and are mapped to a device, the system automatically includes that device when drawing impact charts. ## Impact Charts for Buildings, Rooms, and Racks @@ -46,7 +48,7 @@ The following is a sample room impact chart: Looking at the impact chart for a room, from left to right, you see the room itself, the list of racks (with one rack selected), and all the servers that are located in the selected rack. You can view a legend via the **Legend** button above. -Now, let's gather more information about one of the servers. You can do this easily by hovering over it (or any item in the chart) as such: +To get more information about a server, hover over it (or any item in the chart): -### Topology Element Overview: +### Topology Element Overview **Global View** is a simplified view of device-to-device directionality in relationship. No details of the relationship are viewable here, except the hostnames that have interactions with each other. Any type of device can be visible here. If there is any relationship of services, applications, hypervisor, or virtual, it will be represented in the **Global View**. @@ -139,7 +141,7 @@ The device topology chart has its own legend: style={{ width: '50%' }} /> -The **Display Options** are used to manipulate current in-view objects based on the below criteria: +Use the **Display Options** to filter the objects currently shown in the topology: - **Hide services without connections:** This shows any service objects that have been discovered on an in-view and associated device, but with no connections yet discovered or added. (By default, this box is checked.) - **Hide client IP addresses with no Device/Managed Resources:** This shows IP addresses for any remote connections that were found in the netstat table of the in-view discovered devices. These are not yet considered **Device** objects in the database and are classified as clients or remote connections of the service objects. (By default, this box is checked). @@ -230,7 +232,7 @@ Most impact and topology screens have a **Create Image** button that allows you }} /> -The **Create Image** button allows you to choose from two layout options: You may choose the Global or the Local view pane, and can also choose either **PNG** format or **SVG** (vector) image format. Simply click the **Download** button to choose your save location, and save the file wherever is convenient for you. +The **Create Image** button lets you choose between the Global and Local view panes, and either **PNG** or **SVG** (vector) image format. Click the **Download** button to save the file. **Service Dependencies Report Download** @@ -260,7 +262,7 @@ An impact list is simply a list version of an impact graph. Impact lists are typ }} /> -The full impact list for a device. Sometimes, it is useful to hide services without connections, which significantly reduces clutter by hiding services you may not be concerned with (many services that fit this criteria are standard operating-system components). See the example following the full list for more details: +The full impact list for a device is shown below. You can hide services without connections to reduce clutter — many such services are standard operating system components. DataCenter > Racks** to display the Racks list page. +Device42 lets you track the physical location of devices by assigning them to racks within rooms. This page covers how to create and manage racks, add devices and assets to racks, visualize rack layouts, and perform bulk operations. + +Navigate to **Infrastructure > DataCenter > Racks** to view the Racks list page. DataCenter > Racks** to di }} /> -Like the list view pages for other objects, you'll see your racks and several sortable columns of information. Use the available filters and search box to narrow down the list of racks displayed. +The list displays your racks with sortable columns. Use the available filters and search box to narrow down the list. Get a quick look at where there is available space in the racks with the **Available Us** column that displays the availability heatmap of each rack. @@ -52,7 +54,7 @@ The **Details** section includes the following fields: style={{ width: '80%' }} /> -- **Row**: If you have a name for the row, put it here. Please note that the row name is for information only and won't affect the layout of the room. In the visual room layout, rows are initially created automatically and won't use this setting. You can then drag and drop racks to create rows. If all racks in a given row in the visual layout have the same **Row** value, the value will appear to the left of the row. The same applies to columns in the visual layout – if all the racks in a given column have the same **Row** value, the value will appear at the top of the column. +- **Row**: Enter a name for the row if you have one. The row name is for informational purposes only and does not affect the room layout. In the visual room layout, rows are created automatically — this setting is not used initially. You can drag and drop racks to arrange them into rows. If all racks in a row share the same **Row** value, that value appears to the left of the row. The same applies to columns: if all racks in a column share the same **Row** value, the value appears at the top of the column. - **Room**: The Room the rack belongs to is displayed on the Rack view page and is a clickable link. You can assign an existing Room, or create a new Room from this page by clicking **+** (the plus sign icon). Racked ### Rack Elevations: Physical Connections With Drag-and-Drop +From the Rack Layout page, you can go to **Physical Connections** to visualize power and network connectivity. + ![Rack elevations physical connections with drag and drop](/assets/images/wpid6444-media_1424466162974.png) -From the Rack Layout page, you can go to **Physical Connections** and visualize power and network connectivity from this page. You can optionally turn off either of the connections to see only the power cables or only the network cables. In edit mode, drag-and-drop is also available for PDU ports and network ports (between patch panel ports or switch ports). + You can optionally turn off either of the connections to see only the power cables or only the network cables. In edit mode, drag-and-drop is also available for PDU ports and network ports (between patch panel ports or switch ports). ![](/assets/images/wpid6447-media_1424515989100.png) @@ -225,9 +229,9 @@ When you view the physical connections, you will see outlets that resemble the o ### Highlighted Paths and Port Label Display -![Selected/highlighted paths and port label display in physical connectivity layouts](/assets/images/wpid6452-media_1424517266968.png) +In the physical connection layout, you can select a port for a device to highlight the full path. -In the physical connection layout, you can select a port for a device, and the display will highlight the path. +![Selected/highlighted paths and port label display in physical connectivity layouts](/assets/images/wpid6452-media_1424517266968.png) ### Add PDUs to the Rack @@ -303,7 +307,9 @@ Choose the **Clone selected Racks** action to clone the selected racks as well a You can choose which room the cloned racks go to, select a device naming profile, specify a prefix for rack and PDU names, and fill in some other optional fields, as shown below. -Note: The **Rack name prefix** will be prepended to each rack name, whereas the **Rack name prefix to ignore** will be removed from the rack name. +:::note +The **Rack name prefix** is prepended to each rack name. The **Rack name prefix to ignore** is removed from the rack name. +::: Cables**. +Navigate to **Infrastructure > Connectivity > Cables** to view and add cables. Cables**. }} /> -Cables also have their own unique properties. In addition to length, connector type, and location, cables support [custom fields](../../administration/custom-key-value-pairs-explained.mdx). +Cables also have their own unique properties. In addition to length, connector type, and location, cables support [custom fields](/administration/custom-key-value-pairs-explained.mdx). ## Drag-and-Drop Cabling From the Rack View -From the rack view under **Data Center > Racks > Your Rack > View Rack Layout**, you can create, move, edit, and trace cables visually via the drag-and-drop functionality, in addition to the above method. +From the rack layout view under **Infrastructure > DataCenter > Racks**, open a rack and select **View Rack Layout** to create, move, edit, and trace cables visually using drag-and-drop. You can also view or add a cable connection by clicking **Physical Connections** under **Rack Details** on the left and enabling edit mode: diff --git a/docs/infrastructure-management/connectivity/circuits.mdx b/docs/infrastructure-management/connectivity/circuits.mdx index 9b60c1123..272a6fcf8 100644 --- a/docs/infrastructure-management/connectivity/circuits.mdx +++ b/docs/infrastructure-management/connectivity/circuits.mdx @@ -6,9 +6,9 @@ sidebar_position: 2 import ThemedImage from '@theme/ThemedImage'; import useBaseUrl from '@docusaurus/useBaseUrl' -The Device42 circuits module enables you to manage and tack the **Circuit ID**, **Vendor**, **Customer** who owns the circuit, and more. +The Device42 circuits module lets you manage circuits, tracking the **Circuit ID**, **Vendor**, **Customer**, and connection endpoints for each circuit. -The circuits module tracks both **Origin** and **End Point** connections. The **Origin Type** and **Endpoint Type** includes panel ports, switch ports, devices, or other circuits. +The module tracks both **Origin** and **End Point** connections. The **Origin Type** and **Endpoint Type** can be panel ports, switch ports, devices, or other circuits. Navigate to **Infrastructure > Hardware > Circuits** and click the **Create** button. @@ -46,4 +46,4 @@ Navigate to **Infrastructure > Hardware > Circuits** and click the **Create** bu The module also tracks the **Order Date**, **Provision Date**, **Turn on Date**, and **Expiration Date** on contracts. -Fields to upload **File Attachments**, enter **Custom Fields** and **Purchase/Support** details are also available on this screen. +The form also includes fields for **File Attachments**, **Custom Fields**, and **Purchase/Support** details. diff --git a/docs/infrastructure-management/connectivity/creating-wall-jacks.mdx b/docs/infrastructure-management/connectivity/creating-wall-jacks.mdx index ce8147d46..053897b01 100644 --- a/docs/infrastructure-management/connectivity/creating-wall-jacks.mdx +++ b/docs/infrastructure-management/connectivity/creating-wall-jacks.mdx @@ -1,12 +1,12 @@ --- -title: "Creating Wall Jacks" +title: "Create Wall Jacks" sidebar_position: 3 --- import ThemedImage from '@theme/ThemedImage'; import useBaseUrl from '@docusaurus/useBaseUrl' -One method for documenting the connections and the patch from a patch panel to a wall jack, to a switch, to devices is to create a **patch panel model** for wall jacks. +To document the connection path from a patch panel to a wall jack to a switch and its devices, create a **patch panel model** for the wall jack. Navigate to **Resources > Assets > Patch Panel Models** and create a model with the appropriate **Port Type** and desired **Number of ports** on the panel of the wall jack. @@ -19,17 +19,17 @@ Navigate to **Resources > Assets > Patch Panel Models** and create a model with style={{ width: '80%' }} /> -Once you've created the model, make specific assets for the wall jacks via **Resources > All Assets > Create**. When creating the asset, select the type **Patch Panel**, then select the wall jack model for the patch panel model and the **Back connection** type, which can be either **Patch Panel** or **Switch**, and can go to the patch panel or the unmanaged switch you are documenting. +Once you've created the model, create assets for the wall jacks via **Resources > All Assets > Create**. When creating the asset, select the type **Patch Panel**, then select the wall jack model as the patch panel model. Set the **Back connection** type to either **Patch Panel** or **Switch**, depending on whether it connects to the patch panel or the unmanaged switch you are documenting. -You will then want to create an unmanaged switch: +Next, create an unmanaged switch: -- Do this by going to **Tools > Templates & Bulk Operations > Switch Templates**, then create a template that reflects the switches that are part of this connectivity by selecting a switch type and adding a ports switch template with the desired ports prefix and a template that includes the type and number of ports. +- Navigate to **Tools > Templates & Bulk Operations > Switch Templates** and create a template that reflects your switches. Select a switch type and add a ports switch template with the desired ports prefix, type, and number of ports. - Once you've created the switch template, select the template and click the **Create/Edit** option under the **Ellipsis menu** in the top right corner of the template's details page. Here, you can add the desired amount of unmanaged switches needed. Once you've created assets for the wall jacks and created switches from the template, you can start creating the connections: -- Go to the desired wall jack asset you want to work with and open the edit details page of the asset. There will be a section for patch panel ports on this details page, with a line for each port contained on the wall jack panel (defined by the previously created patch panel model). +- Open the wall jack asset and go to its edit details page. The page includes a patch panel ports section with a line for each port on the wall jack panel, as defined by the patch panel model you created earlier. - First, define the front connection as either the patch panel or the switch, whichever is desired. - Define the **Connection Type**, then enter the **Object** ID or search for and select the switch port or the patch panel port for the connection. - You can also enter a **Label** for the connection that corresponds with the wall jack label in the room (if it is labeled). Then, define the **Back connection**, which can also be the patch panel port or the switch port (whichever you did not use for the front connection). diff --git a/docs/infrastructure-management/connectivity/index.mdx b/docs/infrastructure-management/connectivity/index.mdx index 1f788b0d3..b4127e9dc 100644 --- a/docs/infrastructure-management/connectivity/index.mdx +++ b/docs/infrastructure-management/connectivity/index.mdx @@ -1,18 +1,5 @@ --- -title: "Patch Panels" -created: 2013-03-06 -authors: - - d42docadmin +title: "Connectivity" --- -You can manage structured cabling. In this section, would discuss following topics: - - - -## Table of contents - -- [Cables](infrastructure-management/connectivity/cables.mdx) -- [Circuits](infrastructure-management/connectivity/circuits.mdx) -- [Creating Wall Jacks](infrastructure-management/connectivity/creating-wall-jacks.mdx) -- [Patch panels and cable management](infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx) -- [Creating patch panels from scratch in Device42: an example](infrastructure-management/connectivity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx) +Device42 lets you document and manage your physical network infrastructure, including cables, circuits, wall jacks, and patch panels. Use the sidebar to navigate to specific topics. diff --git a/docs/infrastructure-management/connectivity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx b/docs/infrastructure-management/connectivity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx index a1d298abd..4bf95b78b 100644 --- a/docs/infrastructure-management/connectivity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx +++ b/docs/infrastructure-management/connectivity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx @@ -1,5 +1,5 @@ --- -title: "Creating patch panels from scratch in Device42: an example" +title: "Create Patch Panels From Scratch: An Example" --- import ThemedImage from '@theme/ThemedImage'; @@ -17,7 +17,7 @@ The end goal is: 2. Patch `Panel A` is patched to `switch-01`. 3. Patch `Panel B` is patched to devices in the same rack as patch `Panel B`. -This will provide our devices with connectivity to switch ports. +This provides devices with connectivity to switch ports. ### Create Patch Panel Models @@ -29,11 +29,11 @@ This will provide our devices with connectivity to switch ports. }} /> -Before we add the patch panel, we need to create the template. In this example, this is a single patch panel with 48 RJ-45 ports. +Before adding the patch panel, create the model template. In this example, this is a single patch panel with 48 RJ-45 ports. -- Go to **Resources > Assets > Patch Panel Models > Create**. +- Go to **Resources > Assets > Patch Panel Models > Create**. - Enter the details for the model, including a name, port type, and number of ports. -- **Save** the patch panel model. +- **Save** the patch panel model. ### Create Patch Panels @@ -69,9 +69,9 @@ Before we add the patch panel, we need to create the template. In this example, }} /> -1. Go to **Resources > All Assets > Create**. +1. Go to **Resources > All Assets > Create**. 2. **Name** it `Panel A`, select **Patch Panel** as its **Type**, and choose the model created above. -3. Click **Save**. +3. Click **Save**. Repeat the same steps for `Panel B`, changing only the name to `Panel B` in Step 2. @@ -126,12 +126,12 @@ Now, `Panel A` and `Panel B` are connected to each other. ![wpid3707-patch_panel_switchport_excel.png](/assets/images/wpid3707-patch_panel_switchport_excel.png) -In this example, ports from switch-01 are patched to Panel A. (You can create switch ports in bulk using switch templates, as discussed under [Switch Templates](infrastructure-management/ipam/switch-templates.mdx).) +In this example, ports from switch-01 are patched to Panel A. (You can create switch ports in bulk using switch templates, as discussed under [Switch Templates](/infrastructure-management/ipam/switch-templates.mdx).) -The tedious way to do this is to add each switch port to each panel port. Instead, use the recommended API Excel import option as follows: +You could add each switch port to each panel port manually, but the recommended approach is to use the API Excel import as follows: 1. Download the sample Excel file from **Create/update Patch Panel Ports** on that page. -2. Check that the columns look like this: **number  |  patch_panel_id  |  switch  |  switchport** +2. Check that the columns look like this: **number | patch_panel_id | switch | switchport** 3. Add the rows for the panel port number, panel ID (retrieved from the Asset list view, from APIs, or from hovering over the status bar), switch name, and switch port name. 4. Import the XLS sheet. @@ -151,7 +151,7 @@ Upon import, you can see the switch ports' connections on Panel A. In this step, use the same sample Excel sheet downloaded in the step above. -The column layout is a little different and looks like this: **number  |  patch_panel_id  |  device  |  obj_label1** +The column layout is a little different and looks like this: **number | patch_panel_id | device | obj_label1** Once you've added the values to Excel and imported the sheet, `Panel B` will show the following. @@ -173,7 +173,7 @@ Once you've added the values to Excel and imported the sheet, `Panel B` will sho }} /> -Now, if you go to `Panel B`'s patch panel layout and hover over any port or device, you will see the full visual path for that port. +In `Panel B`'s patch panel layout, hover over any port or device to see the full visual path for that port. ### Switch Port Level Connectivity @@ -185,7 +185,7 @@ Now, if you go to `Panel B`'s patch panel layout and hover over any port or devi }} /> -You will see the patch panel connectivity from each switch port view as well. +Patch panel connectivity is also visible from each switch port view. ### Device Level Connectivity diff --git a/docs/infrastructure-management/connectivity/patch-panels/index.mdx b/docs/infrastructure-management/connectivity/patch-panels/index.mdx index ae93e9fae..01990262e 100644 --- a/docs/infrastructure-management/connectivity/patch-panels/index.mdx +++ b/docs/infrastructure-management/connectivity/patch-panels/index.mdx @@ -1,15 +1,5 @@ --- title: "Patch Panels" -created: 2013-03-06 -authors: - - d42docadmin --- -You can manage structured cabling. In this section, would discuss following topics: - - - -## Table of contents - -- [Patch panels and cable management](infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx) -- [Creating patch panels from scratch in Device42: an example](infrastructure-management/connectivity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx) +Device42 lets you document and manage patch panel ports and their cable connections. Use the sidebar to navigate to specific topics. diff --git a/docs/infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx b/docs/infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx index 38be33543..9ab11e97c 100644 --- a/docs/infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx +++ b/docs/infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx @@ -58,7 +58,7 @@ If you have different cable types in the same patch panel, you should use **Modu }} /> -You can add modules to your patch panels and configure different port types or just modules. For a modular patch panel, you have the option to add modules. Ports for each module are created based on **patch panel module models**. All the module ports will appear in the original patch panel view. +For a modular patch panel, you can add modules and configure different port types. Ports for each module are created based on **patch panel module models** and appear in the original patch panel view. -You can choose the individual **Back connection** per port and add a **Back cable** type for back connectivity with this option. You can add cable speed and other attributes for back connectivity for each port. In addition to the edit screens above, there are RESTful APIs and spreadsheet imports available for doing this more easily. There is also a bulk operations option for provisioning back connectivity, as discussed below. +You can set the **Back connection** and **Back cable** type individually for each port, including cable speed and other attributes. RESTful APIs and spreadsheet imports are also available for bulk updates. A bulk operations option for provisioning back connectivity is discussed below. ### Bulk Back Ports Connectivity @@ -134,7 +134,7 @@ View full connection paths and patch panel layouts. style={{ width: '70%' }} /> -You can get full path details visualized in this table. +The table displays full path details for each connection. ### Patch Panel Layout @@ -147,7 +147,7 @@ You can get full path details visualized in this table. style={{ width: '40%' }} /> -The view or edit page of that asset (the patch panel) adds a new **View Patch Panel Layout** button. +The patch panel's view or edit page includes a **View Patch Panel Layout** button. -From the Patch Panel Layout page, you can turn on the edit mode and connect patch panel ports to other devices or switch ports by dragging a port to a device or another port. This makes it very easy to manage your patch panel connectivity and keep information up to date. +From the Patch Panel Layout page, enable edit mode and connect patch panel ports to devices or switch ports by dragging a port to its destination. ### Drag-and-Drop for Switch Port @@ -187,7 +187,7 @@ From the Patch Panel Layout page, you can turn on the edit mode and connect patc style={{ width: '80%' }} /> -From the Patch Panel Layout page, you can also drag-and-drop switch ports to devices or to patch panel ports. When you do so, a popup appears, giving you the opportunity to enter a port label. +From the Patch Panel Layout page, you can also drag switch ports to devices or patch panel ports. A popup appears where you can enter a port label. ### Direct Patch Panel Port to Patch Panel Ports Connections @@ -215,7 +215,7 @@ Handle devices outside the rack, half-depth devices, and multi-hop connections. }} /> -By default, only the devices in the same rack as the asset would show up. You can reset the filter by clicking on total devices, as shown above, and choose a device outside the rack. These are displayed on the left side of the patch panel, as shown below. +By default, only devices in the same rack as the patch panel are shown. You can reset the filter by clicking on total devices, as shown above, to select a device outside the rack. These are displayed on the left side of the patch panel, as shown below. ![](/assets/images/wpid5717-media_1355834288356.png) diff --git a/docs/infrastructure-management/power-units/adding-atss.mdx b/docs/infrastructure-management/power-units/adding-atss.mdx index 802d2b9d4..23a623550 100644 --- a/docs/infrastructure-management/power-units/adding-atss.mdx +++ b/docs/infrastructure-management/power-units/adding-atss.mdx @@ -1,20 +1,30 @@ --- -title: "Adding ATSs" +title: "Add ATSs" sidebar_position: 1 --- import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -Intelligent ATSs will be automatically discovered through power autodiscovery in Device42. You will be able to see incoming PDU connections to ATSs and visualize your whole power chain, from UPS to PDU to ATS to device. +Device42 automatically discovers intelligent ATSs through power discovery. You can view incoming PDU connections to ATSs and visualize your full power chain, from UPS to PDU to ATS to device. + +This page explains how to create ATSs manually, connect them to PDUs, view power connection maps, and map ATSs to a device for detailed asset tracking. ## Create an ATS -You can create an ATS in Device42 by going to **Infrastructure > Power Units > Power Units**. Click **Create** at the top right of the Power Units list page. On the new screen, name your ATS and select ATS as the power unit type. +Navigate to **Infrastructure > Power Units > Power Units** and click **Create** at the top right of the list page. Name your ATS and select **ATS** as the power unit type. + + ## Connect ATSs to PDUs -To connect an ATS to a PDU, browse to the PDU you would like to connect to the ATS and, in Edit mode, change the **Content Type** of the port to which you are connecting to **Power Unit**. Then, using the Object ID **plus icon**, select the ATS you would like to connect to the PDU. +To connect an ATS to a PDU, open the PDU in edit mode and change the **Content Type** of the connecting port to **Power Unit**. Then use the **plus icon** next to the Object ID field to select the ATS. -Once you click **Save**, the connection will be displayed as seen below. +Once you click **Save**, the connection is displayed on the PDU page. +The PDU detail view also shows the connected ATS in the port listing. + Power Units**. -2. Select the PDU that you would like to see connections for. +2. Select the PDU whose connections you want to view. 3. Click the **Connections** link in the ellipsis menu in the top-right corner. Power Units > Power Units**. Relevant PDU-related fields are listed and defined below. +Use this page to add a new PDU in Device42 and understand the fields available during setup. -Note that PDUs (like almost all Device42 CIs) can also be added and manipulated [via the API](https://api.device42.com/#pdu). +The sections below explain the main PDU fields, show how automatic port creation works, and outline how to map a PDU to a device when you want to track asset and lifecycle details. You can also add and manage PDUs [via the API](https://api.device42.com/#pdu). + +To add a PDU from the UI, go to **DataCenter > Power Units > Power Units**. Settings > Global Settings**. +- **Power Unit Model:** Select the PDU model. This field is required if the PDU is rack-mounted or if you want to track individual PDU ports. +- **Is Device42 PDU Monitoring Enabled:** Enable this option to have Device42 monitor the PDU. +- **Storage Room:** If the power unit is not stored in a rack or server room, specify the storage room where it is located. Selecting a storage room removes any existing rack and server room information. +- **Object Category:** Select the object category for this PDU. This field is visible only if **Role-Based Access Control** (RBAC) is enabled under **Tools > Settings > Global Settings**. :::note The **Set Object Category** option on the **Actions** menu of the Power Units list page is only visible if RBAC is enabled. ::: - **Tags:** Include a comma-separated list of tags to categorize this power unit. -- **Notes:** Optionally add notes regarding this power unit. +- **Notes:** Optionally add notes about this power unit. -## Device Mapping Section +## Configure Device Mapping -**Device:** Associating your PDU with a device is required only if you want to track IP address, life cycle, or other asset information for the PDU; IP and asset info is tracked via the chosen device (optional). +Use the Device Mapping section when you want to track IP address, lifecycle, or other asset details for the PDU through an associated device. -- **Serial #:** If PDU is mapped to a device, the serial number of the mapped device is shown here. -- **Asset #:** If PDU is mapped to a device, the asset number of the mapped device is shown here. +- **Device:** Associate the PDU with a device. This is optional unless you want to track IP address, lifecycle, or other asset information for the PDU. +- **Serial #:** If the PDU is mapped to a device, the mapped device's serial number appears here. +- **Asset #:** If the PDU is mapped to a device, the mapped device's asset number appears here. -## Gateway PDU Mapping Section +## Configure Gateway PDU and Other Fields -**Gateway PDU:** If this PDU is plugged into another PDU (aka daisy chained), identify the "Gateway PDU" it is plugged in to, if any (optional). +These additional fields appear in the lower part of the form: -**Infeeds:** Power infeed information will display here (n/a; auto-discovered). +- **Gateway PDU:** If this PDU is plugged into another PDU, identify the gateway PDU it is connected to. Use this field for daisy-chained PDUs. +- **Infeeds:** Power infeed information appears here when available. This information is auto-discovered. +- **Custom Fields:** Any custom fields you created for PDUs appear here. -**Custom Fields:** Any custom fields you have created for PDUs will display here (optional). - -Upon saving your new PDU, Device42 will automatically add ports based on the selected PDU model. **Note that ports can only be added at the time of PDU creation and cannot be altered later!** +When you save the new PDU, Device42 automatically adds ports based on the selected PDU model. Ports can be added only during PDU creation and cannot be changed later. * * * ## Automatically Created Ports -When you click **Save**, the new PDU is created and PDU ports are automatically generated based on the port layout defined by the chosen PDU model. For information on defining your PDU model(s), see the [Defining PDU Models](infrastructure-management/power-units/defining-pdu-models.mdx) section of the Device42 Docs. +When you click **Save**, Device42 creates the new PDU and automatically generates ports based on the layout defined by the selected PDU model. For information about defining PDU models, see [Defining PDU Models](defining-pdu-models.mdx). -## Map PDUs to a Device +## Map a PDU to a Device +To track details such as the PDU's serial number, asset number, IP address, purchase information, and lifecycle information, map the PDU to a device. Create a device for PDU mapping as follows: -To track details about a PDU (for example, its serial number, asset number, IP address, purchase information, and life-cycle management), map the PDU to a device. Create a device for the purpose of PDU mapping as follows: - -1. Create a new device, setting its **Type** to **unknown** (see image above). For better organization, we recommend (but do not require) that you give the device the same name as the PDU that you will be mapping it to. -2. Set the new device's subtype to **PDU** (see the above image). There is no need to define hardware, and all other fields are optional. +1. Create a new device and set its **Type** to **unknown** (see the image above). For easier organization, you can give the device the same name as the PDU you plan to map. +2. Set the new device's subtype to **PDU** (see the image above). You do not need to define hardware, and all other fields are optional. 3. **Save** the new device. -4. Head back to the PDU CI that will be linked to the device you just created. Edit the PDU by clicking the edit button, and click the magnifying glass on the Device Mapping option (see the image below). Choose the device you created in Steps 1-3 by clicking on its name in the **Select Device** popup. +4. Return to the PDU CI that will be linked to the device you just created. Edit the PDU, then click the magnifying glass next to **Device** in the Device Mapping section (see the image below). In the **Select Device** window, click the device you created in steps 1 through 3. 5. **Save** the changes to the PDU. Power Units > Power Unit Models**. +PDU models are optional in some cases, but they are required if the PDU is rack-mounted or if you want to track its individual ports. To manage PDU models, go to **Data Center > Power Units > Power Unit Models**. -## Adding a PDU Model +## Add a PDU Model Power Units > Power Unit Models* style={{ width: '80%' }} /> -### PDU Model Field Definitions +### PDU Model Fields -- **Name:** Define the model name. Choose a descriptive but understandable name, so it's easy for you to differentiate between the different PDU models when defining your PDUs. - -- **Size:** Define your PDU's size (in rack Units) if it is going to be rack-mounted, or define the size of your left- or right-mounted PDUs (for example, 10U or 20U). If not specified, the PDU will be assumed to be a rack-displayed PDU, either left-side or right-side mounted, of the default size, 20U. - -- **Depth:** Define whether the PDU is half-depth or full-depth. The default is half-depth. - -- **Front / Back Image:** Use the front and back image fields to specify your own custom images to represent the front and back of your PDU on the rack display screen. - -- **Manufacturer:** Specify the PDU manufacturer. - +Use these fields when creating the model: -## Adding Ports to a PDU Model +- **Name:** Enter the model name. Use a clear, descriptive name so you can easily distinguish it from other PDU models. +- **Size:** Enter the PDU size in rack units if it will be rack-mounted, or define the size for left-mounted or right-mounted PDUs, such as `10U` or `20U`. If you do not specify a size, the PDU is treated as a rack-displayed left-side or right-side mounted PDU with the default size of `20U`. +- **Depth:** Specify whether the PDU is half-depth or full-depth. The default is half-depth. +- **Front / Back Image:** Use these fields to upload custom front and back images for the PDU on the rack display screen. +- **Manufacturer:** Specify the PDU manufacturer. -Ports should be added during the creation of a new **PDU model**, which is essentially a template. All PDUs that are assigned a given model will inherit their configuration from that PDU model. Ports (power outlets) are added to a model to match their physical layout, and individual PDUs inherit this configuration based on the PDU model that each is assigned. +## Add Ports to a PDU Model -### Adding Ports to a PDU Model +Add ports while creating the PDU model. The model serves as a template, and every PDU assigned to that model inherits its port configuration. Define the ports to match the physical outlet layout of the real PDU. Ports can be added either in bulk or one at a time: @@ -51,14 +46,14 @@ Ports can be added either in bulk or one at a time: style={{ width: '80%' }} /> -This step is critical if you want to define ports for your PDUs! +You cannot add ports directly to an existing PDU. -It is important to emphasize that the PDU model acts as a template for the ports in the PDU. You cannot directly add ports to the PDU. **PDU ports for a PDU can only be created based on PDU models.** +PDU ports are created from the assigned PDU model, so the model must be configured correctly before you create the PDU. -### Note: PDU Models Are Templates! +### Example Port Definition -A PDU model is primarily a set of output connection types and a port count. Take, for example, an APC PDU with (16) NEMA 5-20R ports. To create this PDU: +A PDU model is primarily defined by its output connection types and port counts. For example, to create an APC PDU with 16 `NEMA 5-20R` ports: -1. Add 16 for the port count and NEMA 5-20R for the port type. -2. If necessary, add your own port types (multiple types of ports with varying numbers of port counts are allowed). -3. Finally, ensure you double-check your port layouts. Making changes to the port layout of an existing PDU model will not change any existing PDUs defined based on this model. Only new PDUs will be affected! +1. Enter `16` as the port count and `NEMA 5-20R` as the port type. +2. Add additional port types if needed. A single model can include multiple port types with different port counts. +3. Review the port layout carefully before saving. Changes to an existing PDU model do not update existing PDUs that already use that model. Only newly created PDUs are affected. diff --git a/docs/infrastructure-management/power-units/index.mdx b/docs/infrastructure-management/power-units/index.mdx index 063bb40f3..75297007f 100644 --- a/docs/infrastructure-management/power-units/index.mdx +++ b/docs/infrastructure-management/power-units/index.mdx @@ -2,15 +2,4 @@ title: "PDUs" --- -You can define PDU, PDU ports and do basic rack display for the PDUs. In this section, we will discuss following topics: - - - -## Table of contents - -- [Adding ATSs](infrastructure-management/power-units/adding-atss.mdx) -- [Adding PDUs](infrastructure-management/power-units/adding-pdus.mdx) -- [Defining PDU Models](infrastructure-management/power-units/defining-pdu-models.mdx) -- [PDU ports](infrastructure-management/power-units/pdu-ports.mdx) -- [PDU rack display](infrastructure-management/power-units/pdu-rack-display.mdx) -- [Supported PDU Vendors](infrastructure-management/power-units/supported-pdu-vendors.mdx) \ No newline at end of file +Device42 lets you define PDUs, PDU ports, and PDU models, and view PDUs in rack display. Use the sidebar to navigate to specific topics. \ No newline at end of file diff --git a/docs/infrastructure-management/power-units/pdu-ports.mdx b/docs/infrastructure-management/power-units/pdu-ports.mdx index ba9199b71..e745f02c8 100644 --- a/docs/infrastructure-management/power-units/pdu-ports.mdx +++ b/docs/infrastructure-management/power-units/pdu-ports.mdx @@ -6,7 +6,9 @@ sidebar_position: 4 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -In this section, we will discuss Power Distribution Unit (PDU) ports. To edit PDU ports, open any PDU CI and enter **Edit** mode via the main menu: **Infrastructure > Power Units > Power Units**. +This page describes PDU port connectivity, where PDU port and power information appears in Device42, and how Override Watts affects power estimates. + +To edit PDU ports, open a PDU CI and enter **Edit** mode from **Infrastructure > Power Units > Power Units**. -## Power Unit and PDU Port Connectivity +## Configure PDU Port Connectivity -PDU ports can be connected to a device, an asset (such as a modem), or another PDU. Set the **Connection Type** via the **Content Type** pulldown. +PDU ports can be connected to a device, an asset such as a modem, or another PDU. Set the connection by using the **Content Type** list. -The **Object ID** is the ID of the **Content Type** (the device, asset, or PDU) object. Set the ID, and click on the lookup icon. You will then see a list of existing objects that have the selected content type, and you should select the device, asset, or PDU that connects to this port. +The **Object ID** identifies the selected **Content Type** object. Enter the ID or use the lookup icon to find and select the device, asset, or PDU connected to the port. -**Field Definitions:** +Use these fields when reviewing or editing a port connection: - **Outlet Name:** The outlet name or number on the PDU. - **Port Number:** The outlet or port number, as labeled on the PDU. -- **Object Name:** The object name is auto-generated (after saving) based on the selected **Content Type** and **Object ID**, and provides a link to the device, asset, or PDU that is connected to the port. -- **Object PSU label:** The label of the power supply on the device/asset side. +- **Object Name:** This value is auto-generated after saving, based on the selected **Content Type** and **Object ID**. It links to the connected device, asset, or PDU. +- **Object PSU Label:** The label of the power supply on the device or asset side. - **Override Watts:** Enter a value, in Watts, to override the wattage detected from hardware (optional). -- **Bootstrap Power:** This field shows the peak power draw from this outlet at device boot time; empty if no device is connected. -- **Power Draw:** This field shows the _actual power \[aka true power\]_ draw as measured from this outlet the last time it was polled; it is empty if no device is connected. -- **Active Power:** This field shows the _active power_ \[aka reactive power: power absorbed then returned by the load\] draw as measured from this outlet; it is empty if no device is connected. -- **Apparent Power:** This field shows _apparent power \[aka true power\]_ draw, a combination of _active \[reactive\] power and true power_ measurements; it is empty if no device is connected. -- **Power Factor:** This field shows _calculated power factor_ \[PF = true power / apparent power\]; it is empty if no device is connected. +- **Bootstrap Power:** Shows the peak power draw from this outlet at device boot time. This field is empty if no device is connected. +- **Power Draw:** This field shows the actual power, also called true power, drawn from this outlet the last time it was polled. It is empty if no device is connected. +- **Active Power:** This field shows the active power drawn from this outlet, also described here as reactive power, meaning power absorbed and then returned by the load. It is empty if no device is connected. +- **Apparent Power:** This field shows the apparent power draw, described here as a combination of active power and true power measurements. It is empty if no device is connected. +- **Power Factor:** This field shows the calculated power factor, where `PF = true power / apparent power`. It is empty if no device is connected. -### PDU Ports Viewed From the Device Perspective +### View PDU Ports from the Device -When viewing a PDU-connected device, the **Info** tab shows the PDU port connections and power information (with the Power Monitoring license for that device). +When you view a device connected to a PDU, the **Info** tab shows its PDU port connections and power information if the device has a Power Monitoring license. -Only the **PSU object label** is editable from a physical device's edit screen. All other PDU-related edits must be made on the PDU's edit page. +Only the **PSU Object Label** can be edited from the device edit screen. All other PDU-related changes must be made on the PDU edit page. -### PDU List View +### View the PDU List -To see the PDU list view and a high-level overview of the PDUs you have discovered in Device42, navigate to **Infrastructure > Power Units > Power Units** from the main menu. +To view the PDU list and a high-level overview of your PDUs, go to **Infrastructure > Power Units > Power Units**. -### Infeed Power +### View Infeed Power -The **Infeeds** section will show the **Power Draw Per Phase**, including both the **Rated Power** and **Actual Power Draw** as measured. If your particular PDU supports it, **Apparent Power**, **Power Factor**, **Voltage**, and **Active Power** will also be displayed: +The **Infeeds** section shows **Power Draw Per Phase**, including **Rated Power** and **Actual Power Draw**. If the PDU supports these values, Device42 also displays **Apparent Power**, **Power Factor**, **Voltage**, and **Active Power**: -## PDUs and Available Ports Visible on the Rack View +## View PDUs and Ports in the Rack View -Power units will also be found in the Rack View, which can be found by navigating to **Infrastructure > Racks** from the main menu: +Power units also appear in the Rack View. To open it, go to **Infrastructure > Racks**: -The PDU watts sum will also be visible on the rack layout page as shown below. Click **Power Details** in the left pane to see the PDU power details. +The total PDU wattage also appears on the rack layout page, as shown below. Click **Power Details** in the left pane to view the PDU power details. -### Understanding Power per PDU Port and Override Values +### Understand Override Watts -The **Override Watts** field can be used for PDU port power estimations. By default, the watts value will be the device hardware value as measured _(if a device is connected to that port)_; however, you can enter any value to override the default. +Use **Override Watts** to estimate power at the PDU port level. By default, Device42 uses the measured hardware value when a device is connected to the port, but you can enter a different value to override it. -If there is no default value (for example, an asset connected to a PDU port would not have a default power value), you may use this field to enter the value manually. Overridden and default values will be used by Device42 to estimate the total power for that PDU. The sum is visible on all the PDU pages _(the list, view, and change pages)_. +If there is no default value, such as when an asset is connected to a PDU port, you can enter the value manually. Device42 uses both default and overridden values to estimate total power for the PDU. That total appears on the PDU list, view, and edit pages. diff --git a/docs/infrastructure-management/power-units/pdu-rack-display.mdx b/docs/infrastructure-management/power-units/pdu-rack-display.mdx index efe73778d..d8af43f19 100644 --- a/docs/infrastructure-management/power-units/pdu-rack-display.mdx +++ b/docs/infrastructure-management/power-units/pdu-rack-display.mdx @@ -6,81 +6,75 @@ sidebar_position: 5 import ThemedImage from '@theme/ThemedImage' import useBaseUrl from '@docusaurus/useBaseUrl' -In this section, we will cover the basics of entering information that tells Device42 where the PDU is mounted (that is, to the left, to the right, above, below, or in the rack). PDUs above and below the rack are displayed using an icon. Other locations are displayed using images. +This page explains how to set PDU mount location in Device42 and how PDUs appear in the rack display depending on where they are mounted. PDUs above and below the rack are shown using icons, while other locations use images. ## PDU Location - - -When you choose a PDU from the lookup icon (or search icon), the following options can be defined: - -**Where:** Choose the location of the PDU from **Left**, **Right**, **Above**, **Below**, or **Rack Mounted**. +When editing a rack and selecting a PDU, you can configure the following location fields: -**Start at:** A starting location is required for rack-mounted PDUs. -It is optional for PDUs that are to the left or right of the rack. However, if you choose a starting location, it will use that as its starting location. The only time the starting location is ignored is if the starting location and size of the PDU entered combine to overshoot the rack. -This field is not required or used for PDUs that are mounted above or below the rack. + -**Orientation:** PDUs are only displayed in their respective orientations. For example, for a **Front** orientation with the PDU on the top, the rack layout view only displays the PDU in the front of the rack and not in the back of the rack. +- **Where:** The mount location of the PDU. Choose from **Left**, **Right**, **Above**, **Below**, or **Rack Mounted**. +- **Start at:** Required for rack-mounted PDUs. Optional for left or right PDUs — if set, Device42 uses it as the starting position unless the PDU's size would overshoot the rack. Not used for PDUs mounted above or below the rack. +- **Orientation:** PDUs are displayed only for their set orientation. For example, a PDU with **Front** orientation appears only in the front rack view, not the back. ## Rack-Mounted PDUs - +Rack-mounted PDUs display like any other device in the rack. Half-depth PDUs are greyed out on the other side of the rack unless another device is mounted there, in which case the PDU is not visible. -Rack-mounted PDUs display like any other device in the rack. Half-depth PDUs are greyed out on the other side of the rack in the rack display (unless you have another device mounted; then the PDU is not visible). + ## PDUs on the Left or Right Side of the Rack - +Left or right PDUs are displayed only for their set orientation. Click the PDU to open its details page. -Left or right PDUs are only displayed for the respective orientation, as shown in the image above. You can click on the PDU to open its details page. + ## PDUs Above or Below the Rack - +PDUs above or below the rack are shown using power point icons. Each icon represents a single PDU. Click an icon to open the PDU's details page. -PDUs above or below the rack are shown using power point icons. Each icon represents a single PDU and can be clicked to open the PDU's details page. + ## PDU Display in Multi-Rack Views -When looking at PDUs in multiple rack views, only rack-mounted PDUs are displayed. +In multi-rack views, only rack-mounted PDUs are shown. -## Visually Adding PDUs to the Rack From the Rack Layout Screen +## Add PDUs to the Rack From the Rack Layout Screen -From the rack layout screen, you will see the option to add a PDU: +From the rack layout screen, you can add a PDU directly. Choose a name and a PDU model — a template object appears. Drag the template object to a rack slot to place the PDU. - - -Choose a name and a PDU model, and a template object will appear. Drag the template object to a rack slot, and the move is complete. diff --git a/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx b/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx index b098bd821..ddef7a0c3 100644 --- a/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx +++ b/docs/infrastructure-management/power-units/supported-pdu-vendors.mdx @@ -3,11 +3,9 @@ title: "Supported PDU Vendors" sidebar_position: 6 --- -Below is a brief list of Intelligent Power Distribution Unit (iPDU) vendors supported by Device42. For the most part, we cover all major vendors - however, should your device not be listed or discovered properly, please reach out to [Device42 Support](mailto:support@device42.com) and let us know. +This page lists the Intelligent Power Distribution Unit (iPDU) vendors supported by Device42. Most major vendors are covered. If your device is not listed or is not discovered properly, contact [Device42 Support](mailto:support@device42.com). -**Supported PDU Vendors List:** - -Please note that we may not support all models from each listed vendor. We recommend you verify compatibility with your specific model before assuming support. +Not all models from each vendor are guaranteed to be supported. Verify compatibility with your specific model before assuming support. @@ -52,7 +50,4 @@ 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!). - -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!)_. +Device42 can add support for additional PDU makes and models. To request support, [generate an SNMPWALK](/administration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx) for your device model and send it to [Device42 Support](mailto:support@device42.com) along with your request. Support is typically added within the next few releases. diff --git a/static/assets/images/auditing-racks/audit-export-dark.png b/static/assets/images/auditing-racks/audit-export-dark.png new file mode 100644 index 000000000..c27a8c6c8 Binary files /dev/null and b/static/assets/images/auditing-racks/audit-export-dark.png differ diff --git a/static/assets/images/auditing-racks/audit-export-light.png b/static/assets/images/auditing-racks/audit-export-light.png new file mode 100644 index 000000000..91423ebf1 Binary files /dev/null and b/static/assets/images/auditing-racks/audit-export-light.png differ diff --git a/static/assets/images/auditing-racks/export-action-dark.png b/static/assets/images/auditing-racks/export-action-dark.png new file mode 100644 index 000000000..a8e018606 Binary files /dev/null and b/static/assets/images/auditing-racks/export-action-dark.png differ diff --git a/static/assets/images/auditing-racks/export-action-light.png b/static/assets/images/auditing-racks/export-action-light.png new file mode 100644 index 000000000..5e71171d7 Binary files /dev/null and b/static/assets/images/auditing-racks/export-action-light.png differ diff --git a/static/assets/images/auditing-racks/racks-menu-dark.png b/static/assets/images/auditing-racks/racks-menu-dark.png new file mode 100644 index 000000000..1b79349d7 Binary files /dev/null and b/static/assets/images/auditing-racks/racks-menu-dark.png differ diff --git a/static/assets/images/auditing-racks/racks-menu-light.png b/static/assets/images/auditing-racks/racks-menu-light.png new file mode 100644 index 000000000..f94e866ef Binary files /dev/null and b/static/assets/images/auditing-racks/racks-menu-light.png differ diff --git a/static/assets/images/power-units/ats-type-dark.png b/static/assets/images/power-units/ats-type-dark.png new file mode 100644 index 000000000..ac768e211 Binary files /dev/null and b/static/assets/images/power-units/ats-type-dark.png differ diff --git a/static/assets/images/power-units/ats-type-light.png b/static/assets/images/power-units/ats-type-light.png new file mode 100644 index 000000000..a85d9b630 Binary files /dev/null and b/static/assets/images/power-units/ats-type-light.png differ