Unsolved
This post is more than 5 years old
4 Posts
0
736
VCM as first device found with Linux?
Good morning,
We recently moved a host from one blade to another (HP BL25p). It was a boot- from-SAN host and still should be. I did all the zoning, mapping, etc needed and as far as ECC is concerned everything "looks" good. When attempting to boot it fails. Our Linux admin installed a stand alone drive in the blade to boot the host. Now when we boot and look at the devices we see this:
ora9db:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
LUN 254 is the VCM and for some reason it is listed as Id:00 and appears to be the first device found. The boot device is LUN 00 but it is listed as Id:01.
I have a DMX1000 at 5671.75. Qlogic HBAs on the HP host.
Any help with understanding when and how the Id:xx get set would be appreciated.
(I'm new here so if I need to provide more info, please let me know.) Thank you.
Message was edited by: JJR22
JJR22
We recently moved a host from one blade to another (HP BL25p). It was a boot- from-SAN host and still should be. I did all the zoning, mapping, etc needed and as far as ECC is concerned everything "looks" good. When attempting to boot it fails. Our Linux admin installed a stand alone drive in the blade to boot the host. Now when we boot and look at the devices we see this:
ora9db:
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 00 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi1 Channel: 00 Id: 01 Lun: 254
Vendor: EMC Model: SYMMETRIX Rev: 5671
Type: Direct-Access ANSI SCSI revision: 02
LUN 254 is the VCM and for some reason it is listed as Id:00 and appears to be the first device found. The boot device is LUN 00 but it is listed as Id:01.
I have a DMX1000 at 5671.75. Qlogic HBAs on the HP host.
Any help with understanding when and how the Id:xx get set would be appreciated.
(I'm new here so if I need to provide more info, please let me know.) Thank you.
Message was edited by: JJR22
JJR22
Tanwar2
62 Posts
0
July 18th, 2009 22:00
Sanjeev Tanwar
xe2sdc
2 Intern
2 Intern
•
2.8K Posts
0
July 31st, 2009 02:00
For some reason you can unpublic VCM lun from this
channel. On microcode 5671 you can "not public" VCM
on some channels. You have to see it on the cannel
only if you want to make device masking. So the main
idea for my opinion is remove vcm from this channel,
because VCM ALWAYS is zerro lun (LUN 00) on channel.
First of all welcome to our forums .. Don't forget to introduce yourself in our Coffee Break area
Complex question, let's try to identify different points while answering
1) on code 5671 it's better to leave VCM mapped on all VCM_enabled ports.
2) you will always see the VCM as long as the port is VCM_enable (but plese look point 6)
3) the VCM can be mapped as ANY lun. I used to map the VCM as lun 0xf0 (dec 240).
4) with recent codes and symcli you can't map/unmap the VCM, you need a binfile
5) recent boxes (DMX3 and later) don't even have a "real" VCM. They use a VCM flagged gatekeeper.
6) with older boxes (up to DMX2) you can change default behaviour (VCM is always seen by hosts) and remove this special feature from the VCMdb itself.
Master3
2 Posts
0
July 31st, 2009 02:00
For some reason you can unpublic VCM lun from this channel. On microcode 5671 you can "not public" VCM on some channels. You have to see it on the cannel only if you want to make device masking. So the main idea for my opinion is remove vcm from this channel, because VCM ALWAYS is zerro lun (LUN 00) on channel.