Quantcast
Channel: Symantec Connect - Storage and Clustering - Discussions
Viewing all articles
Browse latest Browse all 543

VCS 5.1 - Failing to start a new node after adding it to the cluster

$
0
0
I need a solution

Hi,

I have just added a node to a cluster and during the conf. everything went fine.. Here is a summary of what I did:

root@dp-e9 # cat /etc/llthosts
0 DP-node5
1 DP-node6
2 DP-node4
3 DP-node8
4 dp-node9

root@dp-e9 # cat /etc/gabtab
/sbin/gabconfig -c -n5

root@dp-e9 # cat /etc/llttab
set-node dp-node9
set-cluster 10000
link igb1 /dev/igb1 - ether - -
link igb2 /dev/igb2 - ether - -

 

root@dp-node9 # dladm show-dev
igb0            link: up        speed: 1000  Mbps       duplex: full
igb1            link: up        speed: 1000  Mbps       duplex: full
igb2            link: up        speed: 1000  Mbps       duplex: full
igb3            link: unknown   speed: 0     Mbps       duplex: unknown
usbecm0         link: up        speed: 10    Mbps       duplex: full

 

In the other node I have:

root@DP-e6 # /sbin/gabconfig -a
GAB Port Memberships
================================
Port a gen   406917 membership 01234
Port b gen   406915 membership 0123
Port b gen   406915    visible ;   4
Port h gen   406914 membership 0123
Port h gen   406914    visible ;   4

=============================

After this I followed the manual to add a node:

Enter the command:
# haconf -makerw
2 Add the new system to the cluster:
# hasys -add dp-node9
3 Enter the following command:
# haconf -dump
4 Copy the main.cf file from an existing node to your new node:
# rcp /etc/VRTSvcs/conf/config/main.cf dp-node9:/etc/VRTSvcs/conf/
config/
5 Start VCS on the new node:
# hastart

 

==============================

But I noticed that the state of the new system is FAULTED now.

I have attached the engine_A log.

And the main.cf looks fine.

I have read that the PSSTAMP being different can be a problem... is that it? Pls see below:

dp-node9 # pkginfo  -l VRTSvcs
   PKGINST:  VRTSvcs
      NAME:  Veritas Cluster Server by Symantec
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  5.1
   BASEDIR:  /
    VENDOR:  Symantec Corporation
      DESC:  Veritas Cluster Server by Symantec
    PSTAMP:  Veritas-5.1-10/06/09-14:37:00
  INSTDATE:  Dec 23 2013 13:26
    STATUS:  completely installed
     FILES:      279 installed pathnames
                  25 shared pathnames
                   4 linked files
                  59 directories
                 101 executables
              233702 blocks used (approx)
 

DP-node6 # pkginfo  -l VRTSvcs
   PKGINST:  VRTSvcs
      NAME:  Veritas Cluster Server by Symantec
  CATEGORY:  system
      ARCH:  sparc
   VERSION:  5.1
   BASEDIR:  /
    VENDOR:  Symantec Corporation
      DESC:  Veritas Cluster Server by Symantec
    PSTAMP:  5.1.001.000-5.1RP1-2010-02-24_23:49:00
  INSTDATE:  Jul 05 2011 12:51
    STATUS:  completely installed
     FILES:      280 installed pathnames
                  27 shared pathnames
                   4 linked files
                  59 directories
                 102 executables
              233783 blocks used (approx)
 

===========================

Let me know if any additional info is need and how to clear this faulted state as well.

DP-node6 # hasys -state
#System    Attribute          Value
DP-node4   SysState           RUNNING
DP-node5   SysState           RUNNING
DP-node6   SysState           RUNNING
DP-node8   SysState           RUNNING
dp-node9   SysState           FAULTED
 

Form the new node i cant do nothing:

dp-node9 # hares -clear dp-node9
VCS ERROR V-16-1-10600 Cannot connect to VCS engine
 

Tks,

Joao

 

 

 

 

 

 

 


Viewing all articles
Browse latest Browse all 543

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>