Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1885

June 13th, 2013 13:00

Classic Symconfigure and Symaccess ran on the same tdev

Does anyone know the repercussions of running symconfigure and running symaccess to map the same tdev?

286 Posts

June 13th, 2013 13:00

Not a problem to do. If symaccess detects that the device is already mapped to the ports it will skip mapping it to the port(s) that the device(s) are mapped to. If you remove the devices from the SG and add -unmap it will unmap the device(s) regardless to whether or not they were mapped with symaccess.

Using both can lead to mapping devices to ports that they are not masked to but wont really cause any problems other than excess mappings.

286 Posts

June 13th, 2013 13:00

Symaccess will only unmap the devices from the ports listed in the port group in the masking view. So if it was mapped to other ports manually that symaccess is unaware of manual cleanup will be required.

2.2K Posts

June 13th, 2013 13:00

If you are manually mapping a device to one set of FA ports, then using a Masking View to map/mask the device to another set of FA ports, then yes you are unnecesarily mapping devices to FA ports.

Why are you manually mapping devices?

19 Posts

June 13th, 2013 13:00

What if the FAs used with the "classic" symconfigure mapping is different from the port groups in the symaccess view creation?  Will it entail manual cleanup later?

19 Posts

June 13th, 2013 14:00

A VMAX noob thought that he had to manually map and use Virtual Provisioning as well.  I may have to test with unused devices.

286 Posts

June 13th, 2013 14:00


Easy mistake to make if you arent familiar with symacces or just used to symmask. With the VMAX the only times (for the most part) you need to map with symconfigure are for certain ORS operations and to remove the ACLX device from view

No Events found!

Top