This post is more than 5 years old

1 Rookie

 • 

21 Posts

7900

November 13th, 2012 08:00

finding unused devices for cleanup

I was doing some cleanup of unused devices on my array, and came across a batch of TDEVs that were not easy to identify as unused.   I'm wondering if anyone suggestions for an easier way to find some of these space hogs.


It is easy to tell when devices are not mapped to an FA port, you can see that in the "unmapped" folders in the SMC display, or you can run "/usr/symcli/bin/symdev list -noport"

But, if you have some devices that were removed from a storage group, and you didn't check the "unmap" box in the SMC, or didn't include "-unmap" in the symaccess command, then you can have devices that are mapped to an FA port, but not masked to a system.

What is the easiest way to find devices that are like this?  Ideally, you shouldn't end up with any devices like that, because you will have correctly unmapped devices and kept your array nice and neat and tidy.  But I think most of us probably have accumulated a little trash on their array over time.  Most of mine were from when we first implemented our VMax and were still learning our way around.

What I did was do a symdev list and got a list of all my TDEVs (no including meta members), then I looped through those devices and did a "symaccess list -type storage -dev " for each device, and flagged devices that were not in a storage group and masking view.  What complicated things a little more for me is that we have a Celerra gateway, and we use our VMax thin pools for back end storage for the Celerra, so we have TDEVs that are mapped to the Celerra FA ports, but not masked to a host with Masking views.   So I had to know enough to omit those from my cleanup.

Anyone have any better suggestions for how to do this?  Am I missing something easy like "symdev list -nomask"?

49 Posts

November 14th, 2012 12:00

Andy,

On a VMAX, you can use the following command to display the devices that are mapped but not part of a masking view.

symaccess list no_assignmnets -dirport all:all

You could then filter your Celerra devices and reclaim the remaining.

Thanks

110 Posts

November 13th, 2012 21:00

Andy,

Yes it’s a painful job when the array is not maintained in proper way. It’s a very bad situation when your leads asks for capacity report to prepare their future plan.

May be below list of commands would help you to figure out them.

To list those TDEVs which were removed from thin pool and not removed

Symdev –sid xxx list –tdev –unbound

Obviously the Unbound devices would not be allocated to servers.

To list those TDEVs which were unmapped but and not removed from thin pool and deleted

Symdev –sid xxxx list –tdev –noport –bound

To list those devices which don’t have masking record

On dmx à symmaskdb –sid xxx list no_assignment –dir all –p all

On VMAX à you may have to do little extra work, or you can use the SMC for easy job

symdev –sid xxxx list -noport

symaccess –sid xxx list –type storage –dev xxxx

Regards,

Periyakaruppan N (Peri),

SAN Administrator

ETF | SCSP 2008 |EMCSA - CX | EMCIE - Celerra |

EMCTA - Symm

NetBackup 6.5

ITIL v3

The Commercial Bank of Qatar

P.O Box 3232, Doha, State of Qatar.

Office Tel : (+974) 4449 5951

Mobile: (+974)77762963

Mail: Periyakaruppan.Neelamegam@cbq.com.qa

Group ID: infra-san-support@cbq.com.qa

1 Rookie

 • 

21 Posts

November 14th, 2012 12:00

Perfect Sanquest.  Thats exactly the command I was looking for.


Thanks.

110 Posts

November 15th, 2012 13:00

That still you need to do some rework. This will list the devices which are not mapped on a port, but its mapped on other ports.

That’s why I was saying that you may have to do some little extra work.

e.g.

Director Identification : FA-9H

Director Port : 0

ACLX Enabled : Yes

Devices not yet assigned :

054

48C

490

494

4E6

503

812

No Events found!

Top