Considerations for configuring AD/LDAP
Consider the following while configuring AD/LDAP in your NetBackup Flex Scale cluster:
In a deployment with both primary and media servers:
Domain users should use the [<AD/LDAP_serverIP/FQDN>\username] to login to NetBackup UI.
Domain user login to the management IP of the node and console IP over SSH is not supported.
Domain user login to the public Appliance/Infrastructure APIs is not supported.
AD/LDAP domains can be added using FQDN as well as IP addresses.
AD/LDAP servers should be reachable through the data network.
In a deployment with only media servers:
Domain users should use the [<AD/LDAP_serverIP/FQDN>\username] to login to Appliance UI.
AD/LDAP users should use only the [username@< AD/LDAP_serverIP/FQDN>] to login to public Appliance/Infrastructure APIs.
AD/LDAP domains can be added using FQDN as well as IP addresses.
AD/LDAP users should use only the AD/LDAP username to log on to the management IP of the node and console IP using SSH.
AD/LDAP servers should be reachable through the management network.
In a non-DNS environment:
If you want to add a domain using FQDN, the IP to FQDN mapping for that domain should be added using the option in the Appliance UI. If multiple VLANs are configured on the cluster, AD/LDAP servers should be configured with the correct VLAN. Only then the AD/LDAP servers can communicate with the multi-VLAN cluster.
When configuring AD/LDAP servers for NetBackup Services on a deployment with both NetBackup primary and media servers, the custom hosts entries must be applied to .
When configuring AD/LDAP servers for NetBackup Services on a deployment with only media servers, the custom hosts entries must be applied to .
When configuring AD/LDAP servers for Universal share/Instant Access, the custom hosts entries must be applied to .