This post is more than 5 years old
4 Posts
0
1686
March 24th, 2007 09:00
How to remove meta members from VCMDB Database
I need some help with the following scenerio. I had some standard devices configured to Host WWN in VCMDB. EMC was called into reconfigure standard devices and convert to META volumes. Prior to converting the standard devices were not removed/cleaned up from VCMDB. The new META contain the members that were once standard devices. I am trying to remove standard devices what now is meta-members from the Host WWN in VCMDB and I'd like to know what is the command and how it impacts the new members in a META that is in use/production containing data. If I delete the meta-members entries (previously standard volumes) will it affect the meta-members in a META device? I hope you understand what I am asking? If someone could provide the syntax and some explanation to this it would be appreciated. Thank you!
No Events found!


dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
March 24th, 2007 10:00
symmask -sid xxx -wwn 10000000c959151b -dir 8c -p 0 remove devs 45c,45d -force
substitude your host wwn and the port where those devices are mapped to
then run
symmask -sid xxx refresh
this will commit your command to the VCM database.
At this point i would wait and see to make sure nobody is complaining about missing path or anything like that. Just to be on the safe side, then repead the command with the next wwn and port. Once you are done run refresh again to commit changes.
symmask -sid xxx refresh
At the very end you can run
symmaskdb -sid xxx list devs -wwn 10000000c959151b
to make sure that only the META head hyper id's are listed
If you do everything correctly, there should be no impact to production...just make sure you are removing standard hypers and not meta heads ..and do one path wait for 30min (safe side
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
1
March 24th, 2007 09:00
symmaskdb -sid xxx list db
(substitute xxx for your SID number)
next to the host WWN you should see the old hyper id's and the new META id ..please verify that's true and will go from there
USShivas
8 Posts
0
March 26th, 2007 17:00
Siva
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
1
March 26th, 2007 19:00
symmaskdb -sid xxx backup -file filename
ss224
4 Posts
0
March 26th, 2007 22:00
regards,
ss224
4 Posts
0
March 26th, 2007 23:00
vincent_corona
2 Intern
•
146 Posts
0
May 2nd, 2007 20:00
Diwakar1
13 Posts
0
May 3rd, 2007 03:00
1. Remove the LUN masking configuration
# symmask -wwn -dir 13a -p 1 remove devs 4A4
# symmask -wwn -dir 4a -p 1 remove devs 4A4
Note: the wwn are the WWPN's of the host HBA's which you obtain from the server.
Update the VCM database
# symmask refresh -nop
2. offline the volume 4A4
# symdev -sid 056 not_ready 4A4 -nop
Check the configuration
# symdev show 4A4
3. Unmap the meta volume from Front-end directors
# cat unmapfile.cmd
unmap dev 4A4 from dir 4b:1;
unmap dev 4A4 from dir 13b:1;
4. Remove the volume from the VCM database
# symconfigure -f unmapfile.cmd preview -nop
# symconfigure -f unmapfile.cmd prepare -nop
# symconfigure -f unmapfile.cmd commit -nop
Check the configuration
# symdev -sa 4b -p 1 -fibre list
# symdev -sa 13a -p 1 -fibre list
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
May 3rd, 2007 03:00