FSN DNS Issue, Unable to configure Active Directory

[B_Venkatesh]

I was unable to join to AD, and getting the FSN DSN (Temporary failuer in name resolutio)...all parameters were correct...and cross verified...earlier configured to AD...and wowking fine...after recent file persona patch update to resolve the null pointer exception error while creating NFS shares. 

One more observation that both VFS and FP node IP's  are able to reachable from Windows / Linux /AIX. only VFS IP not reachable from AIX / Linux systems... 

All these were working before the Patch update, this is peculiar and not able to resolve, i had tried to stop / start the FP Nodes

3par20K8 cli% showversion
Release version 3.3.1 (MU2)
Patches: P32,P34,P40,P45,P51,P52,P76,P80,P90,P93,P96,P111,P113,P115

Component Name Version
CLI Server 3.3.1 (P113)
CLI Client 3.3.1
System Manager 3.3.1 (P113)
Kernel 3.3.1 (MU2)
TPD Kernel Code 3.3.1 (MU2)
TPD Kernel Patch 3.3.1 (P113)

3par20K8 cli%
3par20K8 cli% shownet
IP Address Netmask/PrefixLen Nodes Active Speed Duplex AutoNeg Status
172.16.100.26 255.255.0.0 01 1 1000 Full Yes Active

Default IPv4 route : 172.16.200.2
Default IPv6 route : None
NTP server : 172.16.100.4
DNS server : 172.16.100.2
3par20K8 cli%

3par20K8 cli% setfs ad admin848 ada.net
Please enter admin848's password:
Failed to join domain ada.net . Reason: MemberCallableTaskOperation failed to complete within 35 SECONDS. Invocation{op=com.hazelcast.executor.impl.operations.MemberCallableTaskOperation{serviceName='hz:impl:executorService', identityHash=1093285580, partitionId=-1, replicaIndex=0, callId=1279, invocationTime=1585936158099 (2020-04-03 17:49:18.099), waitTimeout=-1, callTimeout=60000, name=RESOLVE_AD_DOMAIN}, tryCount=250, tryPauseMillis=500, invokeCount=1, callTimeoutMillis=60000, firstInvocationTimeMs=1585936158197, firstInvocationTime='2020-04-03 17:49:18.197', lastHeartbeatMillis=1585936183181, lastHeartbeatTime='2020-04-03 17:49:43.181', target=[127.127.0.12]:5701, pendingResponse={VOID}, backupsAcksExpected=0, backupsAcksReceived=0, connection=null}
Node [node0fs] cannot resolve ada.net [ada.net: Temporary failure in name resolution] ". Please check / correct FSN DNS configuration.

3par20K8 cli%
3par20K8 cli% setnet dns -add 172.16.100.1
DNS server successfully updated.
3par20K8 cli%
3par20K8 cli%
3par20K8 cli%
3par20K8 cli% shownet
IP Address Netmask/PrefixLen Nodes Active Speed Duplex AutoNeg Status
172.16.100.26 255.255.0.0 01 1 1000 Full Yes Active

Default IPv4 route : 172.16.200.2
Default IPv6 route : None
NTP server : 172.16.100.4
DNS server : 172.16.100.2 172.16.100.1
3par20K8 cli%
3par20K8 cli%

Thankyou 

Buddala Venkatesh

[Mahesh202 · Accepted solution]

Hi Buddala Venkatesh

Thank you for coming on HPE Community Forums.

I will start with pinging all the servers involved from 3PAR and outside 3par
First Anything else changed before or during the patch update?
Check network connection  from 3par and from servers using ping
Other than that we need to know more about this 3par as in the serial number hence I would suggest you to get in touch with the technical support and log a case for further troubleshooting.

Regards
Mahesh202

[B_Venkatesh]

Thanks, Mr. Mahesh for your help, due to covid i am out of office. the issue was resolved by our team with the hep of HPE support team.

[rianui]

Hello Mahesh,

I am setting up 3PAR File Persona and I have similar errors. The network settings are correct;

3PAR cli% shownet
IP Address Netmask/PrefixLen Nodes Active Speed Duplex AutoNeg Status
172.16.x.x 255.255.254.0 01 0 1000 Full Yes Active

Default IPv4 route : 172.16.x.x
Default IPv6 route : None
NTP server : 172.16.x.x
DNS server : 172.16.x.x

What could I be missing?

3PAR cli% setfs ad hpe3par domain.com
Please enter hpe3par's password:
Node [node1fs] had already joined the domain [DOMAIN.COM] Error trying to CREATE AD configuration on node [node0fs]auth_lsaclient_LsaAdJoinDomain status:121 reason:No Message for status code.

3PAR cli% setfs ad hpe3par domain.com
Please enter hpe3par's password:
Failed to join domain domain.com . Reason: Node [node1fs] cannot resolve domain.com [domain.com: Temporary failure in name resolution] ". Please check / correct FSN DNS configuration.

Rianui