Merge pull request #225 from device42/version-18-12

Version 18 12

docs/administration/auto-clean-feature.md

@@ -11,13 +11,15 @@ The rules for when a particular type of object should be considered and the rule
 
 Device42 includes several system-defined disabled Auto Clean rules (related to ADM data) as suggested examples you can use to base your own rules on. You can also enable these example rules to keep your ADM data cleaner.
 
-Select _Tools > Auto Clean Rules_ and then click _Add Auto Clean Rule_ on the rules list page.
+Select **Tools > Auto Clean Rules** and then click **Add Auto Clean Rule** on the rules list page.
 
 ![](/assets/images/AutoClean-menu-item.png)
 
 ## Auto Clean Supported CIs
 
-Auto Clean rules can target a wide variety of CIs _(Configuration Items)_ in Device42, including everything from Assets to users to VLANs, and everything in between. The following images list the objects supported as Auto Clean rule targets. ![](/assets/images/AutoClean-object-type-drop-down.png)
+Auto Clean rules can target a wide variety of CIs _(Configuration Items)_ in Device42, including everything from Assets to users to VLANs, and everything in between. The following images list the objects supported as Auto Clean rule targets. 
+
+![](/assets/images/AutoClean-object-type-drop-down.png)
 
 The available object types are:
 
@@ -39,7 +41,9 @@ The available object types are:
 - Scheduled Task
 - Service Communication
 - Service Instance
+- Software Component
 - Software In Use
+- Subnet
 - VLAN
 
 ## Creating Auto Clean Rules
@@ -78,6 +82,8 @@ The available Auto Clean Rule Action options vary depending on which _Object ty
 - **Send email to**: send notification when the rule is triggered. 
 - **Webhook AutoClean Endpoints**: add or delete webhooks to send when the rule is triggered.
 
-**Note:** The Auto Clean rules run once per day. If only an email or webhook is sent but no action is taken, the email or webhook will repeat each day until an action is taken that deletes or changes the object record.
+:::info 
+The Auto Clean rules run once per day. If only an email or webhook is sent but no action is taken, the email or webhook will repeat each day until an action is taken that deletes or changes the object record.
+:::
 
 ![](/assets/images/AutoClean-device-webhook-section.png)

docs/apps/enterprise-application-dependency-mapping/index.md

@@ -2,18 +2,11 @@
 title: "Application Dependency Mapping"
 ---
 
-_The Application Dependency Mapping module allows Device42 to autodiscover application dependencies and service dependencies on a deeper level throughout your network._
+The Application Dependency Mapping module allows Device42 to autodiscover application dependencies and service dependencies on a deeper level throughout your network.
 
 ## **ADM Module Features include:**
 
 - **Discover services to services mappings**: Device42 can show you which service on a machine/instance is connected to what other service(s) on other machines.
 - **Automatic app component grouping**: auto-add application components based on groupings of services on a server. For example, once we discover different Oracle services running on a machine, those will be automatically grouped together as an Oracle application.
 - **Grab the configuration data for major applications**: e.g. Oracle, Microsoft SQL, MongoDB, PostgreSQL, MySQL, Cold Fusion, IIS and Apache httpd, etc. With this, you are able to see config details (and for some software, the actual configuration file contents) for the applications from within Device42.
-
-
-
-## Table of contents
-
-- [ADM Detected Applications](apps/enterprise-application-dependency-mapping/adm-supported-applications.md)
-- [Cloud Application Dependency Mapping](apps/enterprise-application-dependency-mapping/cloud-application-dependency-mapping.md)
-- [Configure Application Dependency Mapping](apps/enterprise-application-dependency-mapping/configure-application-dependency-mapping.md)
+- **Automatic Periodic Sampling Jobs** for both Ports and Database Connections gives a comprehensive view of applications using these resources over time.  This will enhance the discovery beyond a point-in-time usage.

docs/auto-discovery/cisco-ucs-auto-discovery.mdx

@@ -0,0 +1,117 @@
+---
+title: "Cisco UCS Cluster / ACI Fabric Autodiscovery"
+sidebar_position: 9
+---
+
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
+
+:::info
+Load balancers share the discovery job page of the Main Appliance. See the [F5/Load balancer discovery](load-balancer-f5-autodiscovery.md) page if you are looking for load balancer discovery information.
+:::
+
+Device42 will poll your Cisco UCS (Unified Computing System) Manager to discover cluster device information or ACI (Application Centric Infrastructure) Fabric to discover your SDN (software-defined networks).
+
+From version 18.12, UCS discovery jobs have been expanded to include network connectivity information beyond the original Chassis and Blade relationship data for UCS clusters. You'll now have a comprehensive overview of your entire cluster's connectivity, complete with port-channel aggregation information.
+
+![UCS network discovery map](/assets/images/ucs-network-discovery-map.png)
+
+## Setting up a Cisco UCS Cluster or ACI Fabric Discovery
+
+Create a job by navigating to **Discovery > UCS/ACI/Load Balancers** to add and edit Cisco UCS manager information.
+
+<ThemedImage
+  alt="The UCS/ACI/Load Balancers menu"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/UCS-ACI-Load-Balancers-menu-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/UCS-ACI-Load-Balancers-menu-dark.png'),
+  }}
+/>
+<br/><br/>
+
+Add your Cisco UCS Manager or ACI Fabric discovery job by entering one or more IPs or FQDNs, and scroll down to enter your username and password (with permissions) on the device.
+
+<ThemedImage
+  alt="Add Cisco UCS job"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/ucs-select-platform-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/ucs-select-platform-dark.png'),
+  }}
+/>
+<br/><br/>
+
+### **Scheduling UCS Cluster or ACI Fabric Discovery Jobs**
+
+Schedule your autodiscovery job to run regularly on certain days and at specific times.
+
+<ThemedImage
+  alt="schedule an UCS or ACI discovery job"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/autodiscovery-schedule-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/autodiscovery-schedule-dark.png'),
+  }}
+/>
+
+## UCS Cluster / ACI Fabric Discovery Option Definitions
+
+:::note
+The following options only exist for UCS and ACI devices.
+:::
+
+**Hostname to use**: Choose the discovered Name or Serial # hostname format to use for newly discovered devices.  
+**Give precedence to hostname**: Select to force overwrite the existing hostname for devices that already exist using the hostname option.  
+**VRF Group for discovered devices**: Place discovered devices into the following VRF group.  
+**Object Category for discovered devices**: Place discovered objects into the chosen category in Device42.  
+**Overwrite existing object categories**: Select to force overwrite of category on devices that already exist in Device42.
+
+### Device and Chassis Names
+
+If an existing device is not found for the Chassis or the Blade based on the serial number, Device42 will add a new device. The **Name** will be derived from the DN and the serial # of the device.
+
+Check the **Give precedence to hostname** option to use the discovered name for the device instead of its given name.
+
+<ThemedImage
+  alt="UCS ACI hostname to use"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/hostname-to-use-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/hostname-to-use-dark.png'),
+  }}
+/>
+
+### Service Profiles
+
+Navigate to **Infrastructure > UCS Service Profiles** to see a list of discovered service profiles. You can view the **Name**, **DN**, **UCSManager**, and **Device** information for each job. Search for specific profiles using the search bar on the **Service Profile** page or the main dashboard.
+
+<ThemedImage
+  alt="Service profile list"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/service-profile-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/service-profile-dark.png'),
+  }}
+/>
+
+## Run Now or Schedule
+
+Newly created jobs will not run on the first day of their creation to prevent a large number of unintended jobs from running. To run a job after its initial creation, click on the **Run Now** button next to the job after creating the job.
+
+<ThemedImage
+  alt="Run now button"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/run-now-button-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/run-now-button-dark.png'),
+  }}
+/>
+<br/><br/>
+
+Create a run schedule for the job by clicking on the **Add another Autodiscovery Schedule** button when in the job edit mode.
+
+<ThemedImage
+  alt="Add another Auto Discovery Schedule button"
+  sources={{
+    light: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/add-autodiscovery-schedule-light.png'),
+    dark: useBaseUrl('/assets/images/cisco-ucs-auto-discovery/add-autodiscovery-schedule-dark.png'),
+  }}
+/>
+
+
+

docs/auto-discovery/cloud-auto-discovery/other-cloud-autodiscoveries.md

@@ -53,7 +53,7 @@ From here, you can create your API Key that Device42 needs to gain access.
 
 Optionally, you can also:
 
-- Choose the vendor. Please note that all vendors are user-defined. Device42 does not ship with a list of vendors.
+- Choose the vendor. Vendors can be user-defined or may be populated by the EnrichAI feature as part of discovery.
 - Choose a VRF Group. If you select a VRF Group, then all IPs found will be placed in subnets in that VRF Group. This is useful if you have duplicate IPs in your internal network.
 - Check the “Remove unfound instances from Device42″ box. If you check this box, then each time this autodiscovery job is run, any devices that were previously created for this account but were not found by the autodiscovery job will be deleted. By checking this box, you can ensure that Device42 will remain in sync with Linode. If you leave it unchecked, then you may end up with Device42 Cloud Instances (cloud devices) that no longer exist in Linode.
 
@@ -83,7 +83,7 @@ Next, you should "Save and Continue". Then you can click 'Run' to run the job im
 
 **Optionally, you can also:**
 
-- Choose the vendor. Please note that all vendors are user-defined. Device42 does not ship with a list of vendors.
+- Choose the vendor. Vendors can be user-defined or may be populated by the EnrichAI feature as part of discovery.
 - Choose a VRF Group. If you select a VRF Group, then all IPs found will be placed in subnets in that VRF Group. This is useful if you have duplicate IPs in your internal network.
 - Check the “Remove unfound instances from Device42″ box. If you check this box, then each time this autodiscovery job is run, any devices that were previously created for this account but were not found by the autodiscovery job will be deleted. By checking this box, you can ensure that Device42 will remain in sync with OpenStack. If you leave it unchecked, then you may end up with Device42 Cloud Instances (cloud devices) that no longer exist in OpenStack.
 
@@ -112,7 +112,7 @@ Enter the following information:
 
 You can also:
 
-- Choose the vendor. Please note that all vendors are user-defined. Device42 does not ship with a list of vendors.
+- Choose the vendor. Vendors can be user-defined or may be populated by the EnrichAI feature as part of discovery.
 - Choose a VRF Group. If you select a VRF Group, then all IPs found will be placed in subnets in that VRF Group.
 - Select a Remote Collector.