Hi Mark Alleyne,

The output as you asked


test01-ap: find /etc -name "*llt*"
/etc/init.d/llt.rc
/etc/rc2.d/S70llt
/etc/gconf/gconf.xml.defaults/desktop/gnome/url-handlers/callto
/etc/gconf/gconf.xml.defaults/schemas/desktop/gnome/url-handlers/callto
/etc/llttab
/etc/llttab.init41
/etc/llthosts
/etc/llthosts.init41



test02-ap:find /etc -name "*llt*"
/etc/init.d/llt.rc
/etc/rc2.d/S70llt
/etc/gconf/gconf.xml.defaults/desktop/gnome/url-handlers/callto
/etc/gconf/gconf.xml.defaults/schemas/desktop/gnome/url-handlers/callto
/etc/llttab
/etc/llttab.init41
/etc/llthosts
/etc/llthosts.init41

******************************************************************************************************
I have  uninstalled vcs 4.1 from test 01-ap machine and installed vcs 4.1 
on test02-ap.  Here also cluster worked fine in both the servers.
But after reboot the cluster is working fine on test02-ap machine only.
Not able to start llt on test01-ap server and its giving 

test01-ap: ./lltping -c test02-ap
lltping: cannot ioctl(LLT_SETPORT): I/O error

Why the LLT is started on both the servers(test01-ap,test02-ap)before 
reboot and not starting LLT particularly on test01-ap after reboot ? .
 Is any patch is required to solve this issue ? or  any scripts / any NIC 
registeration is required on the test01-ap server ? .Please help in this


Note :test01-ap is jumpstarted(installed) from jumstart server.But 
test02-ap is installed from solaris 10 server.


After reboot the status was showing

test02-ap:           lltstat -nvv
LLT node information:
    Node                 State    Link  Status  Address
     0 test01-ap      CONNWAIT
                                  qfe7   DOWN
                                  qfe2   DOWN
   * 1 test02-ap      OPEN
                                  qfe7   UP      08:00:20:E9:D1:9F
                                  qfe2   UP      00:03:BA:35:29:DE

Thanks
Damodharan K




"Mark Alleyne" <[EMAIL PROTECTED]> 
06/26/2007 07:29 PM

To
"Damodharan K" <[EMAIL PROTECTED]>
cc

Subject
RE: [Veritas-vx] [Veritas-ha]LLT error not starting after first reboot






Hello Damodharan,
 
As previously requested, can you confirm that the llt and gab scripts are 
configured to be started at system boot?
 
Can you supply me with the output from ?find /etc -name "*llt*"
 
Thanks
 
Mark
 
 

From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Damodharan 
K
Sent: 26 June 2007 14:42
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [Veritas-vx] [Veritas-ha]LLT error not starting after first 
reboot
 
Hi, 
Iam having V480 2 sun solaris 10 servers with storage foundation for 
oracle with vcs 4.1 and vxvm 4.1

Iam newly building two node cluster. After installation and
configuration the cluster worked fine and able to switch the CVM.

But after the reboot, the LLT , GAB is not running and not able to start
Cluster service .Please help to slove this issue .I am sending
configuration and the engine log with this 
  
Please guide me is NIC has to be registered in solaris, Why the VCS was 
not working after the first reboot when installation and configuration got 
completed . Any valuable inputs to resolve this isssue will be 
appreciated.


Before reboot - when veritas installation configured automatically 

#: lltstat -nvv 
LLT node information: 
    Node                 State    Link  Status  Address 
   * 0 test01-ap      OPEN 
                                  qfe7   UP      00:03:BA:35:22:3C 
                                  qfe2   UP      00:03:BA:36:72:DE 
     1 test02-ap      OPEN 
                                  qfe7   UP      08:00:20:E9:D1:9F 
                                  qfe2   UP      00:03:BA:35:29:DE 


#: ./lltping -c test02-ap 
Node 0 is alive 
Node                 State    Link  Status  Address 
     0 osp2dev01-ap OPEN 
                            qfe7           UP      00:03:BA:35:22:3C 
                            qfe2           UP      00:03:BA:36:72:DE 






#:more /etc/gabtab 
/sbin/gabconfig -c -n2 


#:more /etc/llttab 
set-node test02-ap 
set-cluster 27 
link qfe7 /dev/qfe:7 - ether - - 
link qfe2 /dev/qfe:2 - ether - - 


After reboot 


#./lltping -c test01-ap 

giving 
cannot ioctl(LLT_SETPORT): I/O error
llt/gab modules are loaded.

modinfo|egrep "llt|gab"
214 7ab88000  230a8 288   1  llt (LLT 4.1MP1)
215 7aba4000  47598 289   1  gab (GAB device 4.1MP1)


LLT node information:
Node                 State    Link  Status  Address
 0 test01-ap      IDLE
 1 test02-ap      IDLE
 2                   IDLE
 3                   IDLE
 4                   IDLE


Engine_A.log

2007/04/18 14:13:44 VCS INFO V-16-1-10125 GAB timeout set to 15000 ms
2007/04/18 14:13:44 VCS ERROR V-16-1-10116 GabHandle::open failed errno
=
261
2007/04/18 14:13:44 VCS ERROR V-16-1-11033 GAB open failed. Exiting
2007/04/18 14:13:54 VCS NOTICE V-16-1-11022 VCS engine (had) started
2007/04/18 14:13:54 VCS NOTICE V-16-1-11027 VCS engine startup
arguments=-restart

Configurations

test02-ap: gabconfig -l
GAB Driver Configuration
Driver state         : Unconfigured
Partition arbitration: Disabled
Control port seed    : Enabled
Halt on process death: Disabled
Missed heartbeat halt: Disabled
Halt on rejoin       : Disabled
Keep on killing      : Disabled
Quorum flag          : Disabled
Restart              : Disabled
Node count           : 2
Disk HB interval (ms): 1000
Disk HB miss count   : 4
IOFENCE timeout (ms) : 15000
Stable timeout (ms)  : 5000



test02-ap:  more /etc/llttab
set-node test02-ap
set-cluster 70
link qfe2 /dev/qfe:2 - ether - -
link qfe7 /dev/qfe:7 - ether - -

test02-ap: more /etc/gabtab
/sbin/gabconfig -c -n2

test02-ap: gabconfig -a
GAB Port Memberships
===============================================================

test02-ap: more /etc/gabtab
/sbin/gabconfig -c -n2


test02-ap: more main.cf
include "types.cf"

cluster vcsdev-ap (
   UserNames = { admin = bopHojOlpKppNxpJom }
   ClusterAddress = "172.25.7.98 "
   Administrators = { admin }
   CredRenewFrequency = 0
   UseFence = SCSI3
   CounterInterval = 5
   )

system test01-ap (
   Limits = { Processors = 4 }
   )

system test02-ap (
   Limits = { Processors = 4 }
   )

group ClusterService (
   SystemList = { test01-ap = 0, test02-ap = 1 }
   AutoStartList = { test01-ap, test02-ap }
   FailOverPolicy = Load
   AutoStartPolicy = Load
   OnlineRetryLimit = 3
   OnlineRetryInterval = 120
   Load = 4
   )

   IP webip (
           Device = ce0
           Address = " 172.25.7.98"
           NetMask = "255.255.255.248"
           )

   NIC csgnic (
           Device = ce0
           )

   VRTSWebApp VCSweb (
           Critical = 0
           AppName = vcs
           InstallDir = "/opt/VRTSweb/VERITAS"
           TimeForOnline = 5
           RestartLimit = 3
           )

   VCSweb requires webip
   webip requires csgnic


   // resource dependency tree
   //
   //      group ClusterService
   //      {
   //      VRTSWebApp VCSweb
   //          {
   //          IP webip
   //              {
   //              NIC csgnic
   //              }
   //          }
   //      }



Note: hacf -verify main.cf also verified(its ok) and copied below



Many thanks in advance
Damodharan K

ForwardSourceID:NT00009422 
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you
 
 
ForwardSourceID:NT00009436 
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


_______________________________________________
Veritas-ha maillist  -  Veritas-ha@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-ha

Reply via email to