VxVM controller based ignite_ux error

[MikeL_4]

Received make_net_recovery error stating VXVM was using enclosure based and must be controller based.

Following message and output from vxdiskadm shows that we are setup for controller based. How do I get around this error, or what make_net_recovery thinks is an error???

* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
0306E4B2895/recovery/2004-11-21,06:30/system_cfg rootdg
vxvm:vxdmpadm: ERROR: - is not a valid dmp node name
save_config: error - /dev/dsk/- not found.
Enclosure based names for VxVM disks are not supported.
Use the vxdiskadm command to change to controller based names.
======= 11/21/04 06:30:07 EST make_net_recovery completed unsuccessfully

vxdiskadm
Volume Manager is currently using the c#t#d# naming format to name
disks on the system.
Do you want to change the naming scheme ? [y,n,q,?] (default: n) n

[Steven E. Protter]

I just read up on VXVM

save_config: error - /dev/dsk/- not found.

There needs to be a /dev/dsk

What procedure did you use to set up vxvm?

SEP

[MikeL_4]

This make_net_recovery has been running twice a week for over 4 weeks now and Sunday mornings run returns this error????

VxVM was setup with HP's instructions to do the setup.

What within save_config isn't working right now ??

[Steven E. Protter · Accepted solution]

Was the vxvm change done since the last good make_tape_recovery?

What has happened to this system since the last good make_tape_recovery backup?

Anything that could have broken it, bad patch whatever should be suspect.

One little detail in that vxvm setup procedure, or an error in the doc could cause this problem.

When something works and stops, the question always has to be. What changed?

Also, if a disk has failed, Ignite won't work. cstm mstm or X Windows xstm, run the excercize function on all disks.

dmesg

Please report back. This is fascinating.

SEP

[MikeL_4]

I went into the Veritas GUI and found a failed disk used for rootdg. Thanks for your help.