Also, if vxiod is not running, run vxiod -set 10.
On 9/19/07, Hafed, Mohammad S (Ghamdi) <[EMAIL PROTECTED]> wrote: > > Vxconfigd –m boot > > > ------------------------------ > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Goutham N > *Sent:* Wednesday, September 19, 2007 7:38 AM > *To:* veritas-vx@mailman.eng.auburn.edu > *Subject:* [Veritas-vx] Veritas doubt > > > > > > Hi All, > > > > I have a Solaris OS 10 server with VXVM 4.1 installed. SAN is connected > from EMC and DGC and once i > > got EMC powerpath and Navisphere installed vxconfigd is not running. Any > suggestions > > > > # pkginfo EMCpower > system EMCpower EMC PowerPath (Patched with 5.0.1_b025) > # uname -a > SunOS usplvelux105 5.10 Generic_118833-33 sun4v sparc SUNW,Sun-Fire-T200 > *# vxdisk list** > VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not > accessible > # vxdg list > VxVM vxdg ERROR V-5-1-684 IPC failure: Configuration daemon is not > accessible > *# pkginfo NAVISCLI > application NAVISCLI Navisphere Disk Array Management Tool (CLI) > # pkginfo NAVIAGENT > application NAVIAGENT Navisphere Disk Array Management Tool (AGENT) > # ps -ef | grep vx > root 175 1 0 Sep 13 ? 0:04 /sbin/vxesd > root 643 1 0 Sep 13 ? 5:03 /opt/VRTSob/bin/vxsvc > -r /opt/VRTSob/config/Registry -e > root 1373 1292 0 04:36:46 pts/2 0:00 grep vx > # modinfo | grep vx > 33 12a5d00 26920 288 1 vxdmp (VxVM 4.1z: DMP Driver) > 34 7be00000 2115c8 289 1 vxio (VxVM 4.1z I/O driver) > 36 12ca308 13f0 290 1 vxspec (VxVM 4.1z control/status driver) > 214 7b36f390 c40 285 1 vxportal (VxFS 4.1_REV-4.1B18_sol_GA_s10b) > 215 7ae00000 1706a8 20 1 vxfs (VxFS 4.1_REV-4.1B18_sol_GA_s10b) > # > > > > > _______________________________________________ > Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx > >
_______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
