You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. Click the **+ Add Active Directory / LDAP Settings** button and enter values specific to your Active Directory (or LDAP) domain. Refer to the explanation of the fields below the image.
2. Click the **Create** button and enter values specific to your Active Directory (or LDAP) domain.
42
34
43
35
**Explanation of the fields**
36
+
44
37
-**LDAP Type**: Choose either **Active Directory** or **Open LDAP** for Lightweight directory access protocol for non-Microsoft directory servers.
45
38
-**Server**: Enter the AD or LDAP server IP address. Only use FQDN if your DNS can resolve it. Rather enter an IP address if your Device42 server doesn't use AD-Aware DNS servers, as it may not be able to resolve your domain name if it hasn't been configured across all your DNS servers
46
39
-**Backup Server**: Add a secondary AD or LDAP server to use if the primary one isn't available.
-**Port**: Port for auth requests to your LDAP or Active Directory server. Note that **389** is the non-SSL default and **636** is the default SSL port. Ensure you change the port if you decide to enable SSL or run a non-standard port.
48
50
-**Base**: Enter the Base DN that points to your users.
-**SSL**: Check this box if you want to query AD or LDAP using SSL. Please change the port to **636** or your configured SSL port if you check this box.
50
61
-**Username/Password**: This is the username a password that will be used for authentication against AD.
51
-
-**Username login Style**: Choose how Device42 accounts created for AD users will be formatted both in Device42 and for login.
62
+
-**Username login style**: Choose how Device42 accounts created for AD users will be formatted both in Device42 and for login.
52
63
53
64
:::caution
54
65
Changes to this setting only affects users imported after the change. To change the account and login format for all users, delete the existing Device42 accounts, change the login style setting, and then re-sync the accounts from AD.
55
66
:::
56
67
57
68
-**Netbios name**: NetBIOS name is an up-to-15-character representation of your domain name, and may actually be entirely different from the domain name. Visit the [Microsoft Disjoint namespace scenarios](https://learn.microsoft.com/en-us/exchange/disjoint-namespace-scenarios-exchange-2013-help) article for help locating domain NetBIOS names.
When you've configured the AD/LDAP settings, create an AD/LDAP sync job. From the main menu, go to **Discovery > AD/LDAP Users** and click **Add AD/LDAP Sync**.
79
+
When you've configured the AD/LDAP settings, create an AD/LDAP sync job. From the main menu, go to **Discovery > AD/LDAP Users** and click **Create**.
62
80
63
81
### Choose User Type
64
82
@@ -67,8 +85,8 @@ Name the AD/LDAP sync job. Then choose the Device42 user **Type** to create from
Copy file name to clipboardExpand all lines: docs/auto-discovery/blade-systems-auto-discovery.mdx
+26-24Lines changed: 26 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ sidebar_position: 7
6
6
importThemedImagefrom'@theme/ThemedImage'
7
7
importuseBaseUrlfrom'@docusaurus/useBaseUrl'
8
8
9
-
The Blade Systems autodiscovery method discovers HP and IBM blade systems, including the IBM BladeCenter. Cisco UCS is also supported but in a separate menu entry.
9
+
The Blade Systems autodiscovery method discovers HP and IBM blade systems, including the IBM BladeCenter. Cisco UCS is also supported, but in a separate menu entry.
10
10
11
11
If you would like to see other vendors, please email [support@device42.comt](mailto:support@device42.com).
12
12
@@ -17,13 +17,13 @@ Blade server discovery gets the following information:
17
17
18
18
## Add a Blade System Autodiscovery Job
19
19
20
-
Navigate to **Discovery > SNMP > Add SNMP Autodiscovery Job** and click **+ Add Jobs**.
20
+
Navigate to **Discovery > SNMP** and click the **Create** button.
1. Choose the **Name to use for newly discovered module or IPMI**. Select **Serial #** to avoid duplicate names for newly discovered items.
51
-
- Serial #
58
+
1. Choose the **Name to use for newly discovered module or IPMI**. Select **Serial #**from the following list of options to avoid creating duplicate names for newly discovered items.
59
+
- Serial #
52
60
- Try name from SNMP, otherwise use serial #
53
61
- Append serial # to name
54
62
2. Deselect **Toggle in service on module power state** to prevent the system from automatically changing the service status of the module based on its power state.
@@ -61,30 +69,24 @@ Scroll down to the **Enclosure/blade system options** section and click **Show**
61
69
62
70
**Save** the blade autodiscovery job.
63
71
64
-
:::note
65
-
Newly created jobs will not run on the first day they are created to prevent an unintentionally large amount of jobs from initially running. If you would like to run a job after its initial creation, select the **Run Now** button next to the job after creation.
66
-
:::
67
-
68
-
### Schedule the Job
69
-
70
-
Scroll down to create a run schedule for the job. Create multiple schedules for the job with the **+ Add another Autodiscovery Schedule** button.
72
+
Newly created jobs will not run on the first day they are created to prevent an unintentionally large number of jobs from initially running. If you would like to run a job after its initial creation, click the **Run Now** button on the job details page or on the SNMP Autodiscovery list page.
**Save** the blade autodiscovery job to return to the SNMP autodiscovery list page, and click **Run Now**.
84
+
On the add or edit modes of the SNMP discovery job page, scroll down to create a run schedule for the job. Create multiple schedules for the job with the **+ Add another Autodiscovery Schedule** button.
0 commit comments