I can see that it talks about running powervxvm if you using VxVM 4.0, but under VxVM 4.1 it never mentions powervxm? So that could be interpreted to mean you don't need powervxvm for VxVM 4.1? I am not sure if this is the case or not, will try and find out.
MarcT2
2 Intern
•
131 Posts
0
January 26th, 2007 03:00
You could also try "vxdctl disable" followed by "vxdctl enable", which might provoke VM into building the missing /dev entries.
Regards,
Marc
JasonBailey
147 Posts
0
January 28th, 2007 17:00
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-002-909_a01_elccnt_0.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tDb250ZW50RXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwMTMyNTUzLG5hdmVOb2RlPVNvZndhcmVEb3dubG9hZHM
I can see that it talks about running powervxvm if you using VxVM 4.0, but under VxVM 4.1 it never mentions powervxm? So that could be interpreted to mean you don't need powervxvm for VxVM 4.1? I am not sure if this is the case or not, will try and find out.
JasonBailey
147 Posts
0
February 8th, 2007 22:00
Yes, it's correct that 'powervxvm' is not required starting with VxVM 4.1
Symantec introduced the TPD ASL for PowerPath pseudo devices in VxVM 4.1. That removes the need to use 'powervxvm'.