CalgaryCR9
Technical User
Our site is running NB 6.0 on Solaris 9. Please note I can't blow away path_to_inst and do a reboot, or do a reconfig reboot (production servers).
I have one master and thirteen clients. Of those 13 clients approximately 50% of them are missing the med-changer from cfgadm -al. Listed below is the med-changer on the 'working' 50%. WWN is the same on the working one.
c4::500104f00045e1c1 med-changer connected configured unknown
I went into path_to_inst on the non-working 50% and they are all missing the med-changer 500104f00045e1c1 entry. In a non-production environment I'd do a reconfiguration boot and hope it would discover it. I do not have that luxury.
I tried a /opt/openv/volmgr/bin/scan -changer but had no success...it found nothing. devfs doesn't seem to find it either.
How can I force the systems to add the med-changer 500104f00045e1c1 to the config files? Backups are obviously failing as a result. It's an L700.
I have one master and thirteen clients. Of those 13 clients approximately 50% of them are missing the med-changer from cfgadm -al. Listed below is the med-changer on the 'working' 50%. WWN is the same on the working one.
c4::500104f00045e1c1 med-changer connected configured unknown
I went into path_to_inst on the non-working 50% and they are all missing the med-changer 500104f00045e1c1 entry. In a non-production environment I'd do a reconfiguration boot and hope it would discover it. I do not have that luxury.
I tried a /opt/openv/volmgr/bin/scan -changer but had no success...it found nothing. devfs doesn't seem to find it either.
How can I force the systems to add the med-changer 500104f00045e1c1 to the config files? Backups are obviously failing as a result. It's an L700.