Unsolved
This post is more than 5 years old
8 Posts
0
5808
Data Mover one (1) in Reset State
hi all, please I need help:
I have 1 Data Mover in Reset State:
Storage: NAS EMC Celerra NX4, Software Version 6.0.40-8
/nas/sbin/getreason ==>
10 - slot_0 primary control station
5 - slot_2 contacted
0 - slot_3 reset
server_2 :
threads runnable = 14
threads blocked = 3447
threads I/J/Z = 1
memory free(kB) = 3157361
cpu idle_% = 98
server_3 :
Error 4000: server_3 : unable to connect to host
===================================================
nas_server -list - ==>
1=nas, 2=unused, 3=unused, 4=standby, 5=unused, 6=rdf
id type acl slot groupID state name
1 1 0 2 0 server_2
2 4 0 3 0 server_3
===============================================================================
Component =>
DME 0 Data Mover 3 Data Mover This system has error al+ Celerra NX4 SL7E91009000710000 system:NX4:SL7E91009000710000|enclosure:xpe:0|mover:Unknown:3
============================================================================================
nas_checkup -=>
Check Version: 6.0.40.8
Check Command: /nas/bin/nas_checkup
Check Log : /nas/log/checkup-run.140513-065610.log
-------------------------------------Checks-------------------------------------
Control Station: Checking statistics groups database....................... Pass
Control Station: Checking if file system usage is under limit.............. Pass
Control Station: Checking if NAS Storage API is installed correctly........ Pass
Control Station: Checking if NAS Storage APIs match........................ N/A
Control Station: Checking if NBS clients are started....................... Pass
Control Station: Checking if NBS configuration exists...................... Pass
Control Station: Checking if NBS devices are accessible.................... Pass
Control Station: Checking if NBS service is started........................ Pass
Control Station: Checking if PXE service is stopped........................ Pass
Control Station: Checking if standby is up................................. N/A
Control Station: Checking if Symapi data is present........................ Pass
Control Station: Checking if Symapi is synced with Storage System.......... Pass
Control Station: Checking integrity of NASDB............................... Warn
Control Station: Checking if primary is active............................. Pass
Control Station: Checking all callhome files delivered..................... Warn
Control Station: Checking resolv conf...................................... Pass
Control Station: Checking if NAS partitions are mounted.................... Pass
Control Station: Checking ipmi connection.................................. Pass
Control Station: Checking nas site eventlog configuration.................. Pass
Control Station: Checking nas sys mcd configuration........................ Pass
Control Station: Checking nas sys eventlog configuration................... Pass
Control Station: Checking logical volume status............................ Pass
Control Station: Checking valid nasdb backup files......................... Pass
Control Station: Checking root disk reserved region........................ Pass
Control Station: Checking if RDF configuration is valid.................... N/A
Control Station: Checking if fstab contains duplicate entries.............. Pass
Control Station: Checking if sufficient swap memory available.............. Pass
Control Station: Checking for IP and subnet configuration.................. Pass
Control Station: Checking auto transfer status............................. Warn
Control Station: Checking for invalid entries in etc hosts................. Pass
Control Station: Checking the hard drive in the control station............ Pass
Blades : Checking boot files....................................... Pass
Blades : Checking if primary is active............................. ?
Blades : Checking if root filesystem is too large.................. ?
Blades : Checking if root filesystem has enough free space......... ?
Blades : Checking if using standard DART image..................... ?
Blades : Checking network connectivity............................. ?
Blades : Checking status........................................... Warn
Blades : Checking dart release compatibility....................... ?
Blades : Checking dart version compatibility....................... ?
Blades : Checking server name...................................... ?
Blades : Checking unique id........................................ ?
Blades : Checking CIFS file server configuration................... Pass
Blades : Checking domain controller connectivity and configuration. Pass
Blades : Checking DNS connectivity and configuration............... Warn
Blades : Checking connectivity to WINS servers..................... Pass
Blades : Checking I18N mode and unicode translation tables......... Pass
Blades : Checking connectivity to NTP servers...................... Pass
Blades : Checking connectivity to NIS servers...................... Pass
Blades : Checking virus checker server configuration............... Pass
Blades : Checking if workpart is OK................................ Pass
Blades : Checking if free full dump is available................... Pass
Blades : Checking if each primary Blade has standby................ Pass
Blades : Checking if Blade parameters use EMC default values....... Pass
Blades : Checking VDM root filesystem space usage.................. N/A
Blades : Checking if file system usage is under limit.............. Pass
Blades : Checking for excessive memory utilization................. Fail
Blades : Checking for REPV2 component configuration................ Fail
Storage System : Checking disk emulation type.............................. Pass
Storage System : Checking disk high availability access.................... Pass
Storage System : Checking disks read cache enabled......................... Pass
Storage System : Checking disks and storage processors write cache enabled. Pass
Storage System : Checking if FLARE is committed............................ Pass
Storage System : Checking if FLARE is supported............................ Pass
Storage System : Checking array model...................................... Pass
Storage System : Checking if microcode is supported........................ N/A
Storage System : Checking no disks or storage processors are failed over... Warn
Storage System : Checking that no disks or storage processors are faulted.. Pass
Storage System : Checking that no hot spares are in use.................... Pass
Storage System : Checking that no hot spares are rebuilding................ Pass
Storage System : Checking minimum control lun size......................... Pass
Storage System : Checking maximum control lun size......................... Pass
Storage System : Checking system lun configuration......................... Pass
Storage System : Checking if storage processors are read cache enabled..... Pass
Storage System : Checking if auto assign are disabled for all luns......... Pass
Storage System : Checking if auto trespass are disabled for all luns....... Pass
Storage System : Checking storage processor connectivity................... Pass
Storage System : Checking control lun ownership............................ Fail
Storage System : Checking if Fibre Channel zone checker is set up.......... N/A
Storage System : Checking if Fibre Channel zoning is OK.................... N/A
Storage System : Checking if proxy arp is setup............................ Pass
Storage System : Checking SPA SPB communication............................ Pass
Storage System : Checking for unsupported storage profile.................. Pass
Storage System : Checking if Clariion security is enabled.................. Pass
Storage System : Checking if backend has mixed disk types.................. Pass
--------------------------------------------------------------------------------
jithin
91 Posts
1
May 14th, 2014 02:00
Hi,
I think its a secondary(standby DM). You may have to manually reboot the Datamover and monitor the status. You can also check the server_log entries at this time. I would suggest you to open a service request with EMC support.
Jithin
Vipin VK
812 Posts
1
May 14th, 2014 02:00
Server_3 is a standby DM and the primary is in good state. But I wonder about the nas_checkup warnings (Blades : Checking if primary is active............................. ?). I believe you are not having any issue in accessing the CIFS/NFS shares. Please raise an SR with EMC. As it is a standby DM, there will be no interruption to services during replacement.
niko791
8 Posts
0
May 19th, 2014 10:00
I'll run the reboot in the server 3, this reboot can generate any problem or issue in the storage box?
Rainer_EMC
8.6K Posts
1
May 21st, 2014 13:00
Rebooting a standby data mover shouldnt cause a problem
niko791
8 Posts
0
May 21st, 2014 13:00
I'll run the reboot in the server 3, this reboot can generate any problem or issue in the storage box?