Start a Conversation

Unsolved

M

1 Rookie

 • 

8 Posts

57

July 23rd, 2024 10:55

Data Mover Greyed out

Unable to access file share and unable to reach data mover they are greyed color

EMC NAS Service is not running due to one of the following reasons:
  1. EMC NAS Service is still starting or there was an error during
     service start-up.
       Please logout and try logging in after 5 minutes. It can take up to
       15 minutes after Control Station boot for EMC NAS Service to start.
       If the problem persists after 3 login retries, please reboot the
       Control Station and try again. If this message is still displayed,
       contact EMC Customer Support.
  2. EMC NAS Software upgrade is in progress, which required stopping
     the Service temporarily.
       Please DO NOT use the administrative interface while EMC NAS Software
       upgrade is in progress. EMC NAS Service starts automatically after
       the upgrade finishes.

Until EMC NAS Service starts, administrative commands and interfaces
will not operate.

1 Rookie

 • 

8 Posts

July 23rd, 2024 12:08

[nasadmin@RDDR-0A-CS-MG-0 ~]$ /nas/bin/nas_server -info server_3
id        = 2
name      = server_3
acl       = 0
type      = standby
slot      = 3
member_of =
standbyfor= server_2
status    :
  defined = enabled
   actual = online, ready

1 Rookie

 • 

8 Posts

July 23rd, 2024 12:08

[nasadmin@RDDR-0A-CS-MG-0 ~]$ /nas/bin/nas_server -list -all

id      type  acl  slot groupID  state  name
1        1    0     2              0    server_2
2        4    0     3              0    server_3

id       acl  server    mountedfs       rootfs  name
1        0    1         14,15,16        13      VDM1

1 Rookie

 • 

8 Posts

July 23rd, 2024 12:10


[nasadmin@RDDR-0A-CS-MG-0 ~]$  /nas/bin/nas_server -info -all
id        = 1
name      = server_2
acl       = 0
type      = nas
slot      = 2
member_of =
standby   = server_3, policy=auto
status    :
  defined = enabled
   actual = unknown

id        = 2
name      = server_3
acl       = 0
type      = standby
slot      = 3
member_of =
standbyfor= server_2
status    :
  defined = enabled
   actual = online, ready

1 Rookie

 • 

8 Posts

July 23rd, 2024 12:30

Can anyone help me to resolve the issue we don't have any support its end of sale and support.

Moderator

 • 

7.5K Posts

July 23rd, 2024 17:15

Hello mzameer,

Which VNX system do you have? What is your current OE on your VNX? What is the current version of Unisphere are you using?

1 Rookie

 • 

8 Posts

July 24th, 2024 06:20

@DELL-Sam L​ Hello,

We are using VNX5400.Version 05.33009.5.218.

1 Rookie

 • 

8 Posts

July 24th, 2024 06:57

EMC VNX Control Station Linux release 3.0 (NAS 8.1.9)
End of banner message from server
root@10.97.1.60's password:
Last login: Tue Jul 23 16:05:34 2024 from 10.0.1.88
EMC VNX Control Station Linux Wed Feb 12 00:58:16 EST 2014
[root@RDDR-0A-CS-MG-0 ~]# /nas/bin/nas_checkup -s
Check Version:  8.1.9.217
Check Command:  /nas/bin/nas_checkup


Check Log    :  /nas/log/checkup-run.240724-092249.log

-------------------------------------Checks-------------------------------------
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.................... Fail
Control Station: Checking if NBS service is started........................ Pass
Control Station: Checking if NAS partitions are mounted.................... Pass
Blades         : Checking status........................................... Warn
--------------------------------------------------------------------------------

One or more errors have occurred. Follow the instructions provided to correct
the problem and try again.

------------------------------------Warnings------------------------------------
Blades : Check status
Warning HC_DM_18800115763: The following Blades returned an unexpected
         reason code value:

         * server_2

         Because of this, several other Blade checks may return a
         question mark "?".
Action : Use the /nasmcd/sbin/getreason command to obtain the reason
         code. If the reason code shows the Blades to be in a normal state
         (reason code 4 or 5), re-run nas_checkup so that all Blade checks can
         be completed. If the Blade(s) is still not in a normal state, use
         server_log to check for errors on the Blade(s). Escalate this issue
         through your support organization if necessary. Provide this output
         and any output or errors received from running these commands in the
         escalation.

--------------------------------------------------------------------------------

-------------------------------------Errors-------------------------------------
Control Station: Check if NBS devices are accessible
Error HC_CS_14505082914: Failed NBS (nd-clnt processes) devices
         access check

         NOTE: Several checks depend on NBS device access to run. These checks
               were not run.
Action :

         1. This may occur if NBS is not configured correctly or if the NBS
            service is not started. Look in the "Checks" section to see if the
            following checks passed:

            * Control Station: Check if NBS configuration exists
            * Control Station: Check if NBS service is started
            * Control Station: Check if NBS clients are started

         If either of those checks did not pass, follow the instructions for
         that check to correct the problem, then rerun nas_checkup to verify
         that the NBS devices can now be accessed.
         2. This may also occur if Blades are powered down or pulled out. If
            you are on the primary Control Station, look in the "Checks"
            section to see if the following check passed:

            * Blades: Check status

         If this check failed, follow its instructions to correct the
         problem, then rerun nas_checkup to verify that the NBS devices can
         now be accessed.
         3. If the problem persists, escalate this issue through your support
            organization. Provide this output and any errors or output that
            occurred running the commands in this procedure in the escalation.

--------------------------------------------------------------------------------

Moderator

 • 

7.5K Posts

July 24th, 2024 13:00

Hello mzameer,

Have you removed any blades from your VNX? If you failover to your secondary control station, are you getting the same errors?

1 Rookie

 • 

8 Posts

July 28th, 2024 09:56

No we didnt remove any blades from the VNX .

Moderator

 • 

7.5K Posts

July 29th, 2024 17:58

Hello mzameer,

Have you tried the steps in this KB? https://dell.to/3Stza4r

No Events found!

Top