EMC VCM DB

[Apricot]

Hi

When a Symmetrix unit is configured, a special device called the VCM device must be created. The size of the Symmetrix device designated as the Volume Logix database device ist 16 Symmetrix cylinders (approximately 7.5MB). All space on this device is reserved for current and future Volume Logix functions.
When we make a #format or boot, then we have allways the following messages:

WARNING: /sbus@12,0/fcaw@1,0/sd@0,0 (sd60):

This message came from the Volume Logix database device.

My question: How can I disable this messages?

regards ph

 

[barye]

You can not disable this message. This volume(VLD) is labeled before. To do this, you must format this volume. You can not format this volume because you lost configuration. This message is standart EMC message.

 

[Apricot]

i have found something:

Solution ID: emc39258 Date Created: 01/15/2002 Last Modified Date:
07/04/2002


Solution: How do I prevent 'corrupt label - wrong magic number' messages appearing from the VCMDB on a Solaris host during reboot?

To avoid this error message, you can use what are known as persistent binding in the HBA configuration file. By using persistent bindings each HBA instance can be assigned a target other than target 0.
This is because target 0 is normally used by the the Solaris host for its internal disk devices.

Thus a mapping for "target=0 lun=0" already exists on a host for the local disks. Since this can also be the mapping used for the VCMDB, it can result in Solaris probing the VCMDB on every reboot leading to the 'corrupt label -wrong magic number' warning message since the VCMDB does not have a Solaris disk label.

Once persistent bindings have been implemented, move the disk devices on the HBA to a target other than 0. Do not put a mapping in for the VCMDB LUN address. Now a reboot does not produce the warning message as the VCMDB is no longer visible to the host.

Primus Knowledge
To setup explicit bindings for the Emulex HBAs, the following changes must be made to the /kernel/drv/lpfc.conf:

fcp-bind-

http://WWWPN="500604843d48b9d3:lpfc0t2",

"500604843d48b9c4:lpfc1t1";
automap=0;
And the /kernel/drv/sd.conf should be set up as follows:

name="sd" class="scsi" target=0 lun=0;
name="sd" parent="lpfc" target="1" lun=1 hba="lpfc1";
name="sd" parent="lpfc" target="1" lun=2 hba="lpfc1";
name="sd" parent="lpfc" target="1" lun=3 hba="lpfc1";
name="sd" parent="lpfc" target="2" lun=1 hba="lpfc0";
name="sd" parent="lpfc" target="2" lun=2 hba="lpfc0";
name="sd" parent="lpfc" target="2" lun=3 hba="lpfc0";

regards ph