| Asset ID: |
1-72-2081534.1 |
| Update Date: | 2017-06-12 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2081534.1
:
Exalogic ZFS Storage Heads Can Not Join AD Domain
| Related Items |
- Exalogic Elastic Cloud X4-2 Hardware
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS-ES
|
In this Document
Created from <SR 3-11630179699>
Applies to:
Exalogic Elastic Cloud X4-2 Hardware - Version X4 to X5 [Release X4 to X5]
7000 Appliance OS (Fishworks)
Symptoms
ZFS Storage Appliance heads contained within an Exalogic Engineering System can not join an Active Directory domain.
Cause
DNS or AKD issue
Solution
Troubleshooting
1. Checked debug.sys.
Found errors
--------------
Oct 30 09:23:36 exlogic1-sn01 smbd[4544]: [ID 702911 daemon.error] smbd: failed locating domain controller for hebgt.com
Oct 30 09:23:59 exlogic1-sn01 smbd[4544]: [ID 649633 daemon.notice] ndr_rpc_bind[tid=7]: \\ad01ex1cn12.hebgt.com\PIPE\srvsvc: Network is unreachable (128)
Oct 30 09:24:09 exlogic1-sn01 smbd[4544]: [ID 830222 daemon.notice] ndr_rpc_uncgen: \srvsvc: no server
Oct 30 09:24:14 exlogic1-sn01 smbd[4544]: [ID 649633 daemon.notice] ndr_rpc_bind[tid=7]: \\.\PIPE\srvsvc: unable to resolve server name (61)
Oct 30 09:24:14 exlogic1-sn01 smbd[4544]: [ID 830222 daemon.notice] ndr_rpc_uncgen: \lsarpc: no server
Oct 30 09:24:19 exlogic1-sn01 smbd[4544]: [ID 649633 daemon.notice] ndr_rpc_bind[tid=7]: \\.\PIPE\lsarpc: unable to resolve server name (61)
Oct 30 09:24:29 exlogic1-sn01 smbd[4544]: [ID 702911 daemon.error] smbd: failed locating domain controller for hebgt.com
Oct 30 09:26:07 exlogic1-sn01 smbd[4544]: [ID 649633 daemon.notice] ndr_rpc_bind[tid=7]: \\ad01ex1cn12.hebgt.com\PIPE\srvsvc: Network is unreachable (128)
Oct 30 09:26:17 exlogic1-sn01 smbd[4544]: [ID 830222 daemon.notice] ndr_rpc_uncgen: \srvsvc: no server
Oct 30 09:26:22 exlogic1-sn01 smbd[4544]: [ID 649633 daemon.notice] ndr_rpc_bind[tid=7]: \\.\PIPE\srvsvc: unable to resolve server name (61)
Oct 30 09:26:22 exlogic1-sn01 smbd[4544]: [ID 830222 daemon.notice] ndr_rpc_uncgen: \lsarpc: no server
Oct 30 09:26:27 exlogic1-sn01 smbd[4544]: [ID 649633 daemon.notice] ndr_rpc_bind[tid=7]: \\.\PIPE\lsarpc: unable to resolve server name (61)
Oct 30 09:26:37 exlogic1-sn01 smbd[4544]: [ID 702911 daemon.error] smbd: failed locating domain controller for hebgt.com
From command line, the ping and nslookup was working fine, checked the DNS records by logging to domain controller and all the records were found.
Only when BUI/CLI was used to join, we had this errors.
2. Collected the snoop output
Other problem seem to be that there was nothing in snoop going from storage to AD/DNS server (snoop collected during the joining the storage to AD)
3. Checked the flow diagram for joining the AD.
Found no problem all the prerequisites were met.
SOLUTION
Rebooted both the appliance and DNS/AD server and then AD join worked.
Problem seemed to be AKD or DNS server.
Attachments
This solution has no attachment
