Host mode option in xp24000 for Veritas cluster server

[raunaz]

Hi All, 

I just want to confirm which option should be better option for the Host mode option for my VCS. 

I read one documentation that i should choose option (9) for solaris. But, there is another option (22) for veritas cluster server.

Currently we use option (9) for solaris. And we saw some errors on the servers when we run format command.

The current rpm value 0 is invalid, adjusting it to 3600
The current rpm value 0 is invalid, adjusting it to 3600
The current rpm value 0 is invalid, adjusting it to 3600

I have checked the Hardware technote the xp24000 is supported for solaris 10. 

So, i'm thinking of changing the option to (22) would solve the issue, anyone can confirm ?

DESC:  Veritas Cluster Server by Symantec

    PSTAMP:  5.1.002.000-5.1RP2-2010-08-26_19.00.00

DESC:  VERITAS File System    

   PSTAMP:  5.1.002.000-5.1RP2-2010-08-17-VERITAS-FS-142634-03

bash-3.00# modinfo | egrep -i "vx|llt|gab"

 36  1354270  4db00 324   1  vxdmp (VxVM 5.1RP2 DMP Driver)

 38 7be00000 1fabe8 325   1  vxio (VxVM 5.1RP2 I/O driver)

 40 7bfdc660    d40 326   1  vxspec (VxVM 5.1RP2 control/status driv)

227 7ba31308    be8 327   1  vxportal (VxFS 5.1_RP2.f portal driver)

228 7a600000 1cba60  21   1  vxfs (VxFS 5.1_RP2.f SunOS 5.10)

229 7afbc000  2ad88 329   1  llt (LLT 5.1RP2)

230 7aa8a000  56260 330   1  gab (GAB device 5.1RP2)

231 7aac6000  64ce8 331   1  vxfen (VRTS Fence 5.1RP2)

246 7a7c6000   b5a8 328   1  fdd (VxQIO 5.1_RP2.f Quick I/O drive)

bash-3.00#

thanks a lot for the help.

[Marianne · Accepted solution]

Correct. Host Mode 09. System Options: 22

I read these as two different settings.

As per the HW TechNote:

Minimum Firmware : 60-01-31-00 (XP20000/24000)
Host Mode : 09
System Options : 22
DMP Failover mode : A/A

[Har-D]

Hi,

As Marianne said, Host Mode and System Option are two different things.

The Host Mode provides enhanced compatibility with supported platforms (OS) i.e. Solaris/HP/AIX etc.
Whereas, System Option is more particular to sofware configuration.

You'll need to set both the things correctly. i.e. Host Mode as 9 (for Solaris) plus System Option: 22 (for VCS) or 02 (for SFRAC).

Now, about the error that you are getting :
>> The current rpm value 0 is invalid, adjusting it to 3600

There are two ways Solaris discovers the disk characteristics.

- The first way is to query the disk (to see if the firmware got the disk info already)

- The second one is by reading a label on the disk.

There is a possibility that the geometry/rpm was not set properly in the current disk VTOC. If the setup is new or if you can manage a new test LUN, you can try to run format to relabel it to update the VTOC with correct information.

(Before relabeling, make sure that the LUNs are discovered/configured on the host after you have set the correct host-mode and system-option. If not, re-discover/re-config them after setting the Array options)

[raunaz]

Hi Har-D

Here are the format output. 

bash-3.00# format c3t50060E80056F1178d9s2

The current rpm value 0 is invalid, adjusting it to 3600

format> cur

Current Disk = c3t50060E80056F1178d9

<HP-OPEN-V-SUN-6006 cyl 6525 alt 2 hd 255 sec 63>

/pci@13,700000/SUNW,qlc@0/fp@0,0/ssd@w50060e80056f1178,9

Disk not labeled.  Label it now? y

Warning: error setting drive geometry.

Warning: error writing VTOC.

Warning: no backup labels

Write label failed

partition> p

Current partition table (default):

Total disk cylinders available: 6525 + 2 (reserved cylinders)

Part      Tag    Flag     Cylinders        Size            Blocks

  0       root    wm       0               0         (0/0/0)            0

  1       swap    wu       0               0         (0/0/0)            0

  2     backup    wu       0 - 6524       49.98GB    (6525/0/0) 104824125

  3 unassigned    wm       0               0         (0/0/0)            0

  4 unassigned    wm       0               0         (0/0/0)            0

  5 unassigned    wm       0               0         (0/0/0)            0

  6        usr    wm       0 - 6524       49.98GB    (6525/0/0) 104824125

  7 unassigned    wm       0               0         (0/0/0)            0

########################

From google found 

Root Cause: This will happen when taking a disk from a Windows host and placing it on a Solaris 10 x86 host without erasing the VTOC prior to decommisioning the disk from Windows

I know this is not Veritas issue, Is there anyways i can label the disk without destroying all the data. 

Thanks 

[raunaz]

Hi Marianne, 

the firmware version is 60-06-10. I need to reconfirm back the system options was configured or not. 

If it was not configured, Will it be any problem ?

[Har-D]

*** Try this only if you have a spare disk or a test LUN or a good backup handy (and you have your midset prepared for restore, if anything goes wrong)***

The VTOC is on the first sector of the disk i.e. on initial 512 bytes.

You can try erasing first 512 bytes using 'dd' command and then re-label.

Before erasing, take a backup of existing vtoc. (prtvtoc)

Now populate the label on the LUN using old VTOC. (fmthard).

*** Little risk is involved in this method, so be careful when specifying the counts/block-size