Don’t Restart Or Shutdown Because Data Mover Do Not Failover Like That

VNX data movers are not failover if such conditions are not occurred (You can expect in many situation but not ! )

• Failure of both internal Ethernets …
• Data Mover internal power failure
• Manually failover with the server_standby command
• Data Mover panic
• Lost of SCSI connection
• Lost of Fiber connection
• Memory errors

Otherwise do not wait something like me , right clicked on data mover server_2 and shut it down and wait for server_3 will take off but it was a dream 🙂

VM

Don’t Wait L3 Redundancy From You VNX Data Movers

EMC and File Services …..

When i heard that multiple data movers can run on blade and if you need a additional performance and capacity ( because of data mover are limited to serve a space ) you can add move. I’m really impressed

Today i’m thinking again that how EMC developers can’t or why do not implement Layer3 redundancy in to data mover or that environment ….
Also more funny thing is this movers can not failover if Control Station is not available 😦

You should care about L3 yourself , you do not have to chance to made a mistake, you can not set wrong vlan id to switch port (of course you did not but we are human and can make a mistake)? also you should always watch you switch uplinks which data mover are connected that switch 🙂 Where is the real redundancy ? Okay, there is Fail Safe configuration but does it understand your switch uplink problem ?

Redhat Cluster Suite and NFS/CIFS , Netapp , GlusterFS , Object Storages and all other vendors almost have such option but EMC not …

Think Again ..
VM

VNX Disk Fails Couse IBM SVC Cluster Error

Yesterday we saw that disk failures on VNX side are effecting IBM SVC.

Yes very interesting but it is. You can find out  related explanation below (pls check number 4 because until that step you believe the its a controller issue why disk). I believe that this is really hard issue for storage admins which try to fix both side, first fix the VNX second fix the IBM SVC. The same issue is not available on DS series storages.

Error ID = 10011 : Remote Port excluded for a specific Managed Disk
Error Code = 1220 : Remote FC port excluded

THIS IS AN EXTERNAL ISSUE REPORTED BY THE SVC. NOT AN SVC FAULT

Possible Cause: A remote fibre-channel port has been excluded.

SAN Volume Controller 2145-8G4: N/A

SAN Volume Controller 2145-8F4: N/A

SAN Volume Controller 2145-8F2: N/A

SAN Volume Controller 2145-4F2: N/A

Other: Enclosure/controller fault (50%); Fibre-channel network fabric (50%)
Action:
1. View the error log. Note the MDisk ID associated with the error code.
2. From the MDisk, determine the failing disk controller ID.
3. Refer to the service documentation for the disk controller and the fibre-channel network to resolve the reported problem.
4. After the disk drive is repaired, start a cluster discovery operation to recover the excluded fibre-channel port by rescanning the fibre-channel network.
5. To restore MDisk online status, include the managed disk that you noted in step 1.
6. Check the status of the disk controller. If all disk controllers show a ″good″ status, mark the error that you have just repaired, ″fixed.″
7. If all disk controllers do not show a good status, contact your support center to resolve the problem with the disk controller.
8. Go to repair verification MAP.

VM