Forum Discussion

Pranav_Tyagi's avatar
Pranav_Tyagi
Level 2
10 years ago

LUNs are not coming automatically under veritas after reboot

Hi Community, I have installed SFCFSHA cluster solution on RHEL 1.6, storage is connected through Fiber Channel Over Ethernet (FCoE) interace and dmp is used as multipathing solution. The issue...
business continuity
Cluster Server
Error messages
Linux
Troubleshooting
  • mikebounds's avatar
    mikebounds
    10 years ago

    Are you saying that if you run a "vxdisk list" after booting you don't see disks and so you have to scan disks to see disks and then start fencing - is so then I would guess your FCoE drivers are starting after vxvm, so you will need to move starting of FCoE drivers to earlier on in the boot process.  If I have misunderstood your issue, then please describe what what you are missing after boot up and what you run to fix.

    Mike

Marianne's avatar
Marianne
Level 6
10 years ago

Sure about RHEL 1.6 version? Which SFCFSHA version?

Have you confirmed HCL/array compatibility before installing SFCFSHA ?
Compatibility lists can be found over here: https://sort.symantec.com/documents  
HCL for SF 6.1 and 6.2: http://www.symantec.com/docs/TECH211575  
(I can see only a small amount of Array models supported with FCoE)

Also see the Hardware TN for array-specific configuration requirements:  http://www.symantec.com/docs/TECH47728 

(Use the 'Attachments' link in both URLs to open the pdf's.)

You need to confirm at OS level that disks/luns are visible before SF/fencing/HA starts up.

If there are any delays at OS level at boot time, you need will need to modify startup scripts to scan device earlier in the boot process and check that luns are visible before Veritas startup scripts are initiated.