Unsolved

This post is more than 5 years old

1 Rookie

 • 

3 Posts

3440

March 3rd, 2014 09:00

Datamovers problem. Unable to start NAS service.

Hi,

We are tring to solve some issue with one of ours VNX5600 unified. The problem is with Datamovers. The Backend is ok, we have some hosts connected and working to SP's without problem.

The problem is that Datamovers are in a booting loop. From CS with "getreason" i have "reset status" in both datamovers. Also I verified all FC and ethernet connections.

Any sugestions? How can I get again our NAS Service working?

Thanks you,

6 Operator

 • 

8.6K Posts

March 3rd, 2014 12:00

Please work with EMC customer service about this

You can either call or use customer support live chat

6 Operator

 • 

1.1K Posts

March 4th, 2014 18:00

1. Verify that there is no connectivity from the customer environment to the shared data on the Data Mover.

2.If all Data Movers are in reset, you will have no access to the NBS devices served by the Data Mover. Verify this as follows:

$ su       <<< Switch user to root

# /sbin/fdisk -l        <<< List the disks seen by the Control Station. (You will see the IDE devices /dev/hdXN -X=letter, N=number)

Note: The "nd" devices will not be present if all the Data Movers are reset. If any one Data Mover is up, you should have access to the "nd" devices unless there are issues accessing the LUNs on the array.

3.Having confirmed that the state of "reset" in the /nasmcd/getreason output is valid, do a PXE boot of the Data Mover that is in the reset state

4.Once the Data Mover has booted check connectivity with the following:

Use /nasmcd/sbin/t2tty to send the camshowconfig command to the PXE booted Mover.

5.With the LUN connectivity status now in hand the following are what you need to look at to remediate the connectivity to the control LUNs.

With the connectivity to the array LUNs corrected you must reboot the affected Mover(s) with the PXE services stopped.

Always start with a standby Mover where possible. It is best to bring the Movers up one at a time and check connectivity and the server_log messages from the boot as well as client access.

2 Posts

August 28th, 2019 08:00

Thank you for this clear steps.

I have a similar issue, but in camshowconfig output, i see:

TID 00: 0:d0= 1:d1= 2:d2* 3:d3* 4:d4= 5:d5=

4 of 6  control disk for data mover are in ALUA path. ¿What do i need to check now?

I've been trying sending a camtrespass to data mover with no success.

Any idea?

Thank you in advance.

No Events found!

Top