Skip to content

Commit

Permalink
Merge pull request #364 from ritza-co/docs-19.01.12
Browse files Browse the repository at this point in the history
Docs 19.01.12 release (Week 36, 2024)
  • Loading branch information
sixhobbits authored Sep 27, 2024
2 parents 89ac0b2 + 2d37584 commit 6fcc78f
Show file tree
Hide file tree
Showing 70 changed files with 454 additions and 197 deletions.
550 changes: 396 additions & 154 deletions docs/auto-discovery/database-discovery/index.mdx

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion docs/auto-discovery/load-balancer-f5-autodiscovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ For F5 discovery, ensure you have a **local username** with access to the F5 API

If you're discovering an F5, do the following. You'll want to scan your F5 pool members via either SSH or the API, depending on the device's OS.

1. Start by scanning an F5 device via SNMP. Do this by adding a job under _Discovery → SNMP_ (Make sure you configure SNMP on your F5!), and input the correct (matching) community string. See the [Load Balancers](auto-discovery/load-balancers.md) page for more information about SNMP discovery.
1. Start by scanning an F5 device via SNMP. Do this by adding a job under _Discovery → SNMP_ (Make sure you configure SNMP on your F5!), and input the correct (matching) community string. See the [Load Balancers](auto-discovery/load-balancers.mdx) page for more information about SNMP discovery.
2. After you've discovered via SNMP, go ahead and scan the F5 with the native F5 interface that can be found in _Discovery -> _UCS/ACI/Load Balancers_._ _(Note: This requires an account w/ F5 API permissions!)_.

- For other load balancer types, select the _Platform_ for that type from the drop-down menu.
Expand Down
42 changes: 0 additions & 42 deletions docs/auto-discovery/load-balancers.md

This file was deleted.

57 changes: 57 additions & 0 deletions docs/auto-discovery/load-balancers.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,57 @@
---
title: "Load Balancers"
sidebar_position: 18
---

import ThemedImage from '@theme/ThemedImage'
import useBaseUrl from '@docusaurus/useBaseUrl'

## Introduction

The Device42 Simple Network Management Protocol (SNMP) autodiscovery provides a new option for F5 load balancer discovery that returns discovered load balancers as both devices and managed resources. Discovering F5 load balancers as managed resources provides you with additional details about the load balancers and their related resources, including resource maps that visually represent the relationships between load balancers and resources, and simplifies the Affinity Groups chart view by placing the servers beneath a load balancer.

The recommended best practice for Load balancer discovery is to first identify the devices using SNMP. This will identify the devices and associated resources. Next perform a Windows/*nix discovery of the back end resources to get more detailed inforamtion. Once you have the devices discovered you can then perform the API based "Load Balancer" discovery to link the devices correctly.

## Managed Resources Views

Discovered F5 load balancers are included in the **Resources** list. Navigate to **Resources > All Resources** from the Device42 menu to display the list page. You can consult the Device42 [Managed Resources](resources/index.mdx) documentation for more information.

Click the **Vendor Resource Type** dropdown and check "F5" to filter the list for load balancer resources.

<ThemedImage
alt="Resources list page"
sources={{
light: useBaseUrl('/assets/images/load-balancers/resources-f5-light.png'),
dark: useBaseUrl('/assets/images/load-balancers/resources-f5-dark.png'),
}}
/>

Click on a load balancer in the **Resource Name** column to view more details about that load balancer. You can use the links in the right-hand panel to see details about related resources.

<ThemedImage
alt="View load balancer details"
sources={{
light: useBaseUrl('/assets/images/load-balancers/load-balancer-details-light.png'),
dark: useBaseUrl('/assets/images/load-balancers/load-balancer-details-dark.png'),
}}
/>

Click **Resource Map** on the top left of the load balancer details page to view the topography map for the resource. In the **Tools & Breakdown** section of the left-hand panel, you can view, add, highlight, and search items to include in the map according to their resource type.

The image below shows an example resource map for clustered load balancers.

<ThemedImage
alt="View resource map"
sources={{
light: useBaseUrl('/assets/images/load-balancers/f5-resource-map-light.png'),
dark: useBaseUrl('/assets/images/load-balancers/f5-resource-map-dark.png'),
}}
/>

The chart views for affinity groups are now much simpler and easier to understand. Navigate to **Applications > Affinity Groups** from the Device42 main menu to display the **Affinity Groups** list page.

![](/assets/images/Load-Balancers_AG-list.png)

Click on **Chart** to view the chart for an affinity group with a load balancer.

![](/assets/images/Load-Balancers_AG-chart.png)
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 6fcc78f

Please sign in to comment.