VNX: Changing SP name causes SP reboot

Article Number: 482960 Article Version: 3 Article Type: Break Fix



Unisphere Service Manager,VNX1 Series,VNX2 Series

User was not aware that someone had changed the SP name awhen he noticed that the SP rebooted.

By checking the log, it looks like SP reboot was requested from itself. The IP address is SPA/SPB itself.

A 04/07/16 18:13:39 NaviAgent 1 RebootSP requested from IP 1X2.2X.X.X4.

A 04/07/16 18:14:26 NaviAgent 1 WARNING: Reboot requested. SP(s) going down. SP type=4 (this)

B 04/07/16 18:14:33 NaviAgent 1 RebootSP requested from IP 1X2.2X.X.X5.

A 04/07/16 18:14:39 NaviCimom 79XXX000 Reboot: 50XXX160-bea069fa; 0

B 04/07/16 18:15:01 NaviAgent 1 WARNING: Reboot requested. SP(s) going down. SP type=4 (this)

Similar to Windows, changing a SP name requires a reboot.

A 04/07/16 18:16:45 EventLog 177b The NetBIOS name and DNS host name of this machine have been changed from RXXX to OXXXNX400–SPA.

B 04/07/16 18:17:52 EventLog 177b The NetBIOS name and DNS host name of this machine have been changed from BXXXAGE to OXXXNX400-SPB.

SP name is changed.

SP reboot after changing SP name works as designed.

In this case, have the user confer with his team members and confirm if someone else changed the SP name.

Related:

  • No Related Posts

Re: Strange behavior on files and dir created from Windows.

Hi all,

first post here so apologize for every error I could make.

I have an isilon cluster where I’m studying and I’ve noticed a very strange thing ( in respect to what I see on some “made by other” isilon clusters).

When looking at files created by windows on a SMB share here is the output:

IsilonTest-1# ls -l

total 68

-rwxrwx— + 1 1000006 1000008 9 Apr 9 14:46 New Text Document (2).txt

-rwxrwx— + 1 1000006 1000002 49 Apr 9 14:41 New Text Document.txt

As you can see, the UID and GID is numeric, while I have seen this in other cluster with their original names.

If I look at my authentication providers everithing seems fine, but eventually is not:

IsilonTest-1# isi auth status

ID Active Server Status

—————————————————————-

lsa-activedirectory-provider:PIGI.PRIV Pigi-AD.PIGI.PRIV online

lsa-local-provider:System – active

lsa-local-provider:TestAccessZone – active

lsa-local-provider:pippo – active

lsa-local-provider:ThirdAccessZone – active

lsa-file-provider:System – active

—————————————————————-

Total: 6

IsilonTest-1# isi auth ads view PIGI.PRIV

Name: PIGI.PRIV

Status: online

Primary Domain: PIGI.PRIV

Forest: PIGI.PRIV

Site: Default-First-Site-Name

NetBIOS Domain: PIGI

Hostname: isilontest.pigi.priv

Controller Time: 2018-04-09T17:36:52

Machine Account: ISILONTEST$

Groupnet: groupnet0

I have some suspect, but would like to initially discuss about this without talking of it, just to not give false ideas .

What, in your experience, could cause such behavior ?

Thanks in advance

Pierluigi

Related:

  • No Related Posts

Re: Error 0x6702173 trying to join AD domain

We are currently evaluating the unity and training on it using the community unityVSA.

I was able to setup an NFS nas and now I’m trying to setup the CIFS one. Everytime it was failing using the gui so to be able to try multiple different syntax I’m now using command line it is a lot faster.

The nas is created and now I’m trying to create the cifs server and every time we are getting the same errror. 0x6702173

Our AD domain is corp.transcontinental.ca and there is a container name Computers or an ou name New-Computers at the top level in which the account has right to add servers in them. Just in case there was a permission problem we have also tested with a Domain Admin account.

Here is the syntax we have used :

uemcli -d 172.25.3.8 /net/nas/cifs create -server nas_6 -netbiosName idsunivsmb01 -username svc_netapp_ad -passwd xxxx -orgUnit “OU=New-Computers,DC=corp,DC=transcontinental,DC=ca” -domain corp.transcontinental.ca

uemcli -d 172.25.3.8 /net/nas/cifs create -server nas_6 -netbiosName idsunivsmb01 -username svc_netapp_ad -passwd xxxx -orgUnit “CN=Computers,DC=corp,DC=transcontinental,DC=ca” -domain corp.transcontinental.ca

For all the test the result is :

Storage system address: 172.25.3.8

Storage system port: 443

HTTPS connection

Operation failed. Error code: 0x6702173

The system encountered an unexpected error. Search for the error code on the support website or product forums, or contact your service provider, if available. (Error Code:0x6702173)

Job ID = N-85

Currently it is hard to troubleshoot because we don’t know which DC server was pick by the Unity we have a lot…

here is some questions now ::

  1. Is there some detailled/debug log on the Unity so I can see was is happening in the AD communication?
  2. Is there a way to test the DNS resolution in a NAS server to make sure it picks a valid DC?
  3. Is there a way to force a specific DC server?
  4. Is it possible to do a packet capture on the Unity and to transfer it to a server so we can analyze it?

Thanks for helping

Related:

Re: Re: Error 0x6702173 trying to join AD domain

We are currently evaluating the unity and training on it using the community unityVSA.

I was able to setup an NFS nas and now I’m trying to setup the CIFS one. Everytime it was failing using the gui so to be able to try multiple different syntax I’m now using command line it is a lot faster.

The nas is created and now I’m trying to create the cifs server and every time we are getting the same errror. 0x6702173

Our AD domain is corp.transcontinental.ca and there is a container name Computers or an ou name New-Computers at the top level in which the account has right to add servers in them. Just in case there was a permission problem we have also tested with a Domain Admin account.

Here is the syntax we have used :

uemcli -d 172.25.3.8 /net/nas/cifs create -server nas_6 -netbiosName idsunivsmb01 -username svc_netapp_ad -passwd xxxx -orgUnit “OU=New-Computers,DC=corp,DC=transcontinental,DC=ca” -domain corp.transcontinental.ca

uemcli -d 172.25.3.8 /net/nas/cifs create -server nas_6 -netbiosName idsunivsmb01 -username svc_netapp_ad -passwd xxxx -orgUnit “CN=Computers,DC=corp,DC=transcontinental,DC=ca” -domain corp.transcontinental.ca

For all the test the result is :

Storage system address: 172.25.3.8

Storage system port: 443

HTTPS connection

Operation failed. Error code: 0x6702173

The system encountered an unexpected error. Search for the error code on the support website or product forums, or contact your service provider, if available. (Error Code:0x6702173)

Job ID = N-85

Currently it is hard to troubleshoot because we don’t know which DC server was pick by the Unity we have a lot…

here is some questions now ::

  1. Is there some detailled/debug log on the Unity so I can see was is happening in the AD communication?
  2. Is there a way to test the DNS resolution in a NAS server to make sure it picks a valid DC?
  3. Is there a way to force a specific DC server?
  4. Is it possible to do a packet capture on the Unity and to transfer it to a server so we can analyze it?

Thanks for helping

Related:

Re: Data migration from VNX to Unity using lgdup/sharedup/emcopy tools

Hi,

I’m using lgdup/sharedup/emcopy tools for data migration of CIFS shares from VNX to Unity systems.

I have created NAS server on Unity system, joined it to domain, created file systems and shares and performed initial migration. I have used lgdup (for local users/groups), sharedup to recreate shares and emcopy to perform initial and subsequent migrations.

For the final incremental migration I plan following:

1. To backup all CIFS shares security permissions using emcopy /restoreSD option to folders on local server/PC

2. To put CIFS shares on VNX in “read only” mode, using “unexport”/”export” command with “ro” option

3. To restore CIFS shares permissions using sharedup from Unity to VNX system (as with previous command security ACLs are lost)

4. To restore CIFS security permissions (if not created properly with previous step) using emcopy /restoreSD from Unity to VNX

5. To perform final emcopy migration from VNX to Unity

6. To unjoin VNX from domain, and join-it again in domain using different netbios/computername/IP address

7. To unjoin Unity from domain (for this step I need to delete SMB/CIFS shares), and join-it again using previous IP/hostname of VNX system (before step 5)

8. To recreate local users/groups from VNX to Unity, to recreate shares again using sharedup from VNX to Unity, and restore security permissions using emcopy /restoreSD from VNX to Unity …

9. To check if everything is working as expected

Are this steps correct to perform this type of migration or I’m missing something?

Thanks,

Danail Popovski

Related:

Error 0x6702173 trying to join AD domain

We are currently evaluating the unity and training on it using the community unityVSA.

I was able to setup an NFS nas and now I’m trying to setup the CIFS one. Everytime it was failing using the gui so to be able to try multiple different syntax I’m now using command line it is a lot faster.

The nas is created and now I’m trying to create the cifs server and every time we are getting the same errror. 0x6702173

Our AD domain is corp.transcontinental.ca and there is a container name Computers or an ou name New-Computers at the top level in which the account has right to add servers in them. Just in case there was a permission problem we have also tested with a Domain Admin account.

Here is the syntax we have used :

uemcli -d 172.25.3.8 /net/nas/cifs create -server nas_6 -netbiosName idsunivsmb01 -username svc_netapp_ad -passwd xxxx -orgUnit “OU=New-Computers,DC=corp,DC=transcontinental,DC=ca” -domain corp.transcontinental.ca

uemcli -d 172.25.3.8 /net/nas/cifs create -server nas_6 -netbiosName idsunivsmb01 -username svc_netapp_ad -passwd xxxx -orgUnit “CN=Computers,DC=corp,DC=transcontinental,DC=ca” -domain corp.transcontinental.ca

For all the test the result is :

Storage system address: 172.25.3.8

Storage system port: 443

HTTPS connection

Operation failed. Error code: 0x6702173

The system encountered an unexpected error. Search for the error code on the support website or product forums, or contact your service provider, if available. (Error Code:0x6702173)

Job ID = N-85

Currently it is hard to troubleshoot because we don’t know which DC server was pick by the Unity we have a lot…

here is some questions now ::

  1. Is there some detailled/debug log on the Unity so I can see was is happening in the AD communication?
  2. Is there a way to test the DNS resolution in a NAS server to make sure it picks a valid DC?
  3. Is there a way to force a specific DC server?
  4. Is it possible to do a packet capture on the Unity and to transfer it to a server so we can analyze it?

Thanks for helping

Related:

Re: Joining VNX 5300 NAS to a samba4 Active directory

Thanks for your response. I’ll try to give you more information.

– make sure you have the latest VNX OE installed.

How I can download latest VNX OE? Thanks!

– check the knowledgebase:

I checked but I didn’t found a problem similar to mine.

I found similar posts and I know I have to activate:

-‘allow pre-Windows 2000 computers to use this account’ checkbox is selected when joining the server to the Windows 2000 domain.

-Created DNS entries and Computer entry.

-Use a user with enough permissions to join the domain (in this case I used Administrator).

Now, I’m stucked.

– look at the DM log files – it should also show whether the join worked or not

The join worked and said the command succeeded, the computer is created and modified by VNX in the AD.

“SMB: 6: New GUID value for compname=paxad@STARK.DomainName: 2fef4bae-c44b-4dff-95fc-XX

SMB: 6: DomainJoin compname=PAXAD domain=DomainName DC=miaja.stark.DomainName IP=X.X.X.X was successful

ADMIN: 6: Command succeeded: domjoin compname=PAXAD domain=DomainName admin=administrator password=******************************************** ou=”ou=Computers” init”

But later there is this error:

“User=STARKPAXAD$ auth(FTP). failed, new attempt using:NTLMV2”

– get more info from server_cifs, server_cifssupport, …

$ server_cifssupport server_2 -pingdc -compname X.X.X.X

server_2 : done

PINGDC GENERAL INFORMATION

DC SERVER:

Netbios name : MIAJA

CIFS SERVER :

Compname : paxad

Domain : DomainName

Error 13160939577: server_2 : compname paxad DC=MIAJA Step=’Lookup privileges’ ‘Cannot lookup privilege’ ntStatus=’NO_SUCH_PRIVILEGE’.

– check DNS and SPN’s

The DNS of the Active directory has the name of the computer and it resolves it.

How can I check SPNs?

Thank you for your collaboration.

Related:

Asset Model Hostname Filter

Hi,
We have some assets with empty DNS and NetBIOS Name fields. We did import names for the assets from the CSV file. These imported names are displayed in the Asset Name field on the Assets page’s table and as given name on the asset details. However the Hostname filter does not match for the imported names.

I check the asset data from API. The Unified Name for the imported asset is correct.

Is this correct behaviour of the Hostname filter? Is there some other way to filter on the Asset Name field content?

We have QRadar v.7.2.8 patch 10 installed

Related:

Moving SEPM from 2008 32bit to 2012 64bit

I need a solution

Hi all,

A question that has been asked a million times, but I cannot see anything that relates to the 32bit to 64bit.

We have a Windows 2008 32bit DC that I am decomissioning that is also our SEPM server.  I am wanting to move SEPM to our Windows 2012 R2 64bit Application server.

I have seen that I can do DR etc, but as the server I want to move it to is already up, has a different NETBIOS name and different IP address, I do not think this will work.

So I looked at replication, but I want to be able to do this again in the future if I need to, and as I will be taking the 2008 machine offline this would pose me an issue, plus would this work replicating from SEPM 32 to 64 and vice-versa?

So which would be the best way to do this with the lease amount of pain?

Thanks.

0

Related: