Installation of SFHA 6.0.1

Here is the procedure for installation of Storage Foundation High Availability 6.0.1.
Download the SFHA from Symantec website and copy it to the server.

Extract the file and you can find the installer file in the below location.
VCS_6.0.1/dvd1-sol_sparc/sol11_sparc

bash-4.1# ./installer

    Storage Foundation and High Availability Solutions 6.0.1 Install Program

Copyright (c) 2012 Symantec Corporation. All rights reserved.  Symantec, the
Symantec Logo are trademarks or registered trademarks of Symantec Corporation or
its affiliates in the U.S. and other countries. Other names may be trademarks of
their respective owners.

The Licensed Software and Documentation are deemed to be "commercial computer
software" and "commercial computer software documentation" as defined in FAR
Sections 12.212 and DFARS Section 227.7202.

Logs are being written to /var/tmp/installer-201402070235GdI while installer is
in progress.


    Storage Foundation and High Availability Solutions 6.0.1 Install Program

Symantec Product                                   Version Installed    Licensed
================================================================================
Symantec Licensing Utilities (VRTSvlic) are not installed due to which products
and licenses are not discovered.
Use the menu below to continue.


Task Menu:

    P) Perform a Pre-Installation Check       I) Install a Product
    C) Configure an Installed Product         G) Upgrade a Product
    O) Perform a Post-Installation Check      U) Uninstall a Product
    L) License a Product                      S) Start a Product
    D) View Product Descriptions              X) Stop a Product
    R) View Product Requirements              ?) Help

Enter a Task: [P,I,C,G,O,U,L,S,D,X,R,?]

Select I from the above list of options. And select 4th option to install SFHA from the below options.

    Storage Foundation and High Availability Solutions 6.0.1 Install Program

     1)  Veritas Dynamic Multi-Pathing (DMP)
     2)  Veritas Cluster Server (VCS)
     3)  Veritas Storage Foundation (SF)
     4)  Veritas Storage Foundation and High Availability (SFHA)
     5)  Veritas Storage Foundation Cluster File System HA (SFCFSHA)
     6)  Symantec VirtualStore (SVS)
     7)  Veritas Storage Foundation for Oracle RAC (SF Oracle RAC)
     b)  Back to previous menu

Select a product to install: [1-7,b,q] 4

Press y to accept the license agreement.

 
Do you agree with the terms of the End User License Agreement as specified in
the storage_foundation_high_availability/EULA/en/EULA_SFHA_Ux_6.0.1.pdf file
present on media? [y,n,q,?]y


     Veritas Storage Foundation and High Availability 6.0.1 Install Program

     1)  Install minimal required packages - 567 MB required
     2)  Install recommended packages - 798 MB required
     3)  Install all packages - 827 MB required
     4)  Display packages to be installed for each option

Select the packages to be installed on all systems? [1-4,q,?] (2) 3

Select 3rd option to install all the packages.
Provide the server name which you want to install it.

Enter the Solaris Sparc system names separated by spaces: [q,?] (planet01) planet01


     Veritas Storage Foundation and High Availability 6.0.1 Install Program
                                    planet01

Logs are being written to /var/tmp/installer-201402070235GdI while installer is
in progress

    Verifying systems: 100%

    Estimated time remaining: (mm:ss) 0:00                            8 of 8

    Checking system communication ..................................... Done
    Checking release compatibility .................................... Done
    Checking installed product ........................................ Done
    Checking prerequisite patches and packages ........................ Done
    Checking platform version ......................................... Done
    Checking file system free space ................................... Done
    Checking product licensing ........................................ Done
    Performing product prechecks ...................................... Done

System verification checks completed successfully



     Veritas Storage Foundation and High Availability 6.0.1 Install Program
                                    planet01

The following Veritas Storage Foundation and High Availability packages will be
installed on all systems:

Package           Package Description

VRTSperl          Veritas Perl 5.14.2 Redistribution
VRTSvlic          Veritas Licensing
VRTSspt           Veritas Software Support Tools by Symantec
VRTSvxvm          Veritas Volume Manager Binaries
VRTSaslapm        Veritas Volume Manager - ASL/APM
VRTSvxfs          Veritas File System
VRTSfsadv         Veritas File System Advanced Solutions by Symantec
VRTSfssdk         Veritas File System Software Developer Kit
VRTSllt           Veritas Low Latency Transport
VRTSgab           Veritas Group Membership and Atomic Broadcast
VRTSvxfen         Veritas I/O Fencing by Symantec
VRTSamf           Veritas Asynchronous Monitoring Framework by Symantec
VRTSvcs           Veritas Cluster Server
VRTScps           Veritas Cluster Server - Coordinated Point Server
VRTSvcsag         Veritas Cluster Server Bundled Agents by Symantec
VRTSvcsea         Veritas Cluster Server Enterprise Agents by Symantec
VRTSdbed          Veritas Storage Foundation Databases
VRTSodm           Veritas Oracle Disk Manager
VRTSsfmh          Veritas Storage Foundation Managed Host by Symantec
VRTSvbs           Veritas Virtual Business Service
VRTSsfcpi601      Veritas Storage Foundation Installer

Press [Enter] to continue:


     Veritas Storage Foundation and High Availability 6.0.1 Install Program
                                    planet01

Logs are being written to /var/tmp/installer-201402070235GdI while installer is
in progress

    Installing SFHA: 100%

    Estimated time remaining: (mm:ss) 0:00                            3 of 3

    Performing SFHA preinstall tasks .................................. Done
    Installing SFHA packages .......................................... Done
    Performing SFHA postinstall tasks ................................. Done

Veritas Storage Foundation and High Availability Install completed successfully

     Veritas Storage Foundation and High Availability 6.0.1 Install Program
                                    planet01

To comply with the terms of Symantec's End User License Agreement, you have 60
days to either:

 * Enter a valid license key matching the functionality in use on the systems
 * Enable keyless licensing and manage the systems with a Management Server. For
more details visit http://go.symantec.com/sfhakeyless. The product is fully
functional during these 60 days.

     1)  Enter a valid license key
     2)  Enable keyless licensing and complete system licensing later

How would you like to license the systems? [1-2,q] (2)

Here you enter a license key, otherwise it will work for only 60 days.

     Veritas Storage Foundation and High Availability 6.0.1 Install Program
                                    planet01

     1)  SF Standard HA
     2)  SF Enterprise HA
     b)  Back to previous menu

Select product mode to license: [1-2,b,q,?] (1)
Would you like to enable replication? [y,n,q] (n)
Would you like to configure SFHA on planet01? [y,n,q] (n)

Here I selected ‘n’ to configure SFHA. I will show in next post how to configure SFHA.

How to configure SAMBA in RHEL

Below are the steps to configure SAMBA in RedHat Linux server.
First download and install the required SAMBA packages on server.
If you have yum configured you can install it by using yum otherwise download the packages and install them with rpm command.
Here I am using yum to install these packages.

[root@adminsplanet ~]# yum install samba
Loaded plugins: product-id, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
rhel-x86_64-server-6                                                                                                                             | 1.8 kB     00:00
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package samba.x86_64 0:3.6.9-168.el6_5 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================================================
Package                          Arch                              Version                                       Repository                                       Size
================================================================================================================
Installing:
samba                            x86_64                            3.6.9-168.el6_5                               rhel-x86_64-server-6                            5.0 M

Transaction Summary
================================================================================================================
Install       1 Package(s)

Total download size: 5.0 M
Installed size: 0
Is this ok [y/N]: y
Downloading Packages:
samba-3.6.9-168.el6_5.x86_64.rpm                                                                                                                 | 5.0 MB     00:06
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : samba-3.6.9-168.el6_5.x86_64                                                                                                                         1/1
  Verifying  : samba-3.6.9-168.el6_5.x86_64                                                                                                                         1/1

Installed:
  samba.x86_64 0:3.6.9-168.el6_5

Complete!

Verify the installed samba rpms.

[root@adminsplanet ~]# rpm -qa | grep -i samba
samba-winbind-3.6.9-168.el6_5.x86_64
samba-winbind-clients-3.6.9-168.el6_5.x86_64
samba4-libs-4.0.0-61.el6_5.rc4.x86_64
samba-3.6.9-168.el6_5.x86_64
samba-client-3.6.9-168.el6_5.x86_64
samba-common-3.6.9-168.el6_5.x86_64

Enable the samba service to start in server boot.

# chkconfig smb on

Verify that the service is set to start on boot:

# chkconfig smb --list
smb 0:off 1:off 2:on 3:on 4:on 5:on 6:off

Configuring SAMBA

Below are the SAMBA configuration files.

/etc/samba/smb.conf Contains the main config file
/etc/samba/smbusers Maps Samba and Red Hat users
/etc/samba/smbpasswd Contains Samba user passwords

Add the values for below parameters in smb.conf as below. Here in this example I am sharing /home/ap directory for the user called ‘user1′.

[root@adminsplanet ~]# cat /etc/samba/smb.conf
[homeshare]
comment = MyShare
path = /home/ap
valid users = user1
read only = yes
public = yes
browseable = yes

After adding the values in above file save the file and exit. Now check the config file with testparam command to confirm no syntax errors in the above configuration file.

[root@adminsplanet ~]#testparam
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[homes]"
Processing section "[printers]"
Processing section "[homeshare]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[homeshare]
comment = MyShare
path = /home/ap
valid users = user1
guest ok = Yes

Create a SAMBA user now with below command.

[root@adminsplanet ~]# smbpasswd -a user1
New SMB password:
Retype new SMB password:
Added user user1.

Restart the SAMBA service after adding user.

[root@adminsplanet ~]#service smb restart
Shutting down SMB services:                                [  OK  ]
Starting SMB services:                                     [  OK  ]

Verify that the user id is created successfully or not with the below command.

# pdbedit -L

Add the below lines to the /etc/sysconfig/iptables for firewall rules.
-A INPUT -m state –state NEW -m tcp -p tcp –dport 137 -j ACCEPT
-A INPUT -m state –state NEW -m udp -p udp –dport 138 -j ACCEPT
-A INPUT -m state –state NEW -m udp -p udp –dport 139 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 445 -j ACCEPT

Restart the iptables service once the above entries are added.

[root@adminsplanet ~]# service iptables restart
iptables: Setting chains to policy ACCEPT: filter          [  OK  ]
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Unloading modules:                               [  OK  ]
iptables: Applying firewall rules:                         [  OK  ]

Finally restart the SMB service once.

# service smb restart
Shutting down SMB services:                                [  OK  ]
Starting SMB services:                                     [  OK  ]

How to install Curl on Solaris server.

Download the curl package from below website.

http://curl.haxx.se/download.html

Set the path variable for below path (if already not set).
/usr/xpg4/bin

Add your proxy in /etc/profile file to connect internet.
http_proxy=”xxxxxxx”
export http_proxy

Note: GCC is required for Curl. So we need to install it if it is not already installed. Here in this case it is already installed so I am not going to install it.
Copy the curl package to your server and extract it. Now go to the package location and execute the configure script.

[root@adminsplanet]#cd /tmp/curl-7.37.0
[root@adminsplanet]#
[root@adminsplanet]# ./configure
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether to enable debug build options... no
checking whether to enable compiler optimizer... (assumed) yes
checking whether to enable strict compiler warnings... no
checking whether to enable compiler warnings as errors... no
checking whether to enable curl debug memory tracking... no
checking whether to enable hiding of library internal symbols... yes
checking whether to enable c-ares for DNS lookups... no
checking for path separator... :
checking for sed... /usr/bin/sed
checking for grep... /usr/bin/grep
checking for egrep... /usr/bin/egrep
checking for ar... /usr/ccs/bin/ar
checking for a BSD-compatible install... ./install-sh -c
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
Output truncated..
Final Output:
  curl version:     7.37.0
  Host setup:       sparc-sun-solaris2.10
  Install prefix:   /usr/local
  Compiler:         gcc
  SSL support:      enabled (OpenSSL)
  SSH support:      no      (--with-libssh2)
  zlib support:     enabled
  GSS-API support:  no      (--with-gssapi)
  SPNEGO support:   no      (--with-spnego)
  TLS-SRP support:  no      (--enable-tls-srp)
  resolver:         default (--enable-ares / --enable-threaded-resolver)
  ipv6 support:     enabled
  IDN support:      no      (--with-{libidn,winidn})
  Build libcurl:    Shared=yes, Static=yes
  Built-in manual:  enabled
  --libcurl option: enabled (--disable-libcurl-option)
  Verbose errors:   enabled (--disable-verbose)
  SSPI support:     no      (--enable-sspi)
  ca cert bundle:   no
  ca cert path:     no
  LDAP support:     enabled (OpenLDAP)
  LDAPS support:    enabled
  RTSP support:     enabled
  RTMP support:     no      (--with-librtmp)
  metalink support: no      (--with-libmetalink)
  HTTP2 support:    disabled (--with-nghttp2)
  Protocols:        DICT FILE FTP FTPS GOPHER HTTP HTTPS IMAP IMAPS LDAP LDAPS POP3 POP3S RTSP SMTP SMTPS TELNET TFTP

Execute the “Make” Command.

[root@adminsplanet]# make
Making all in lib
make  all-am
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H   -I../include/curl -I../include  -I../include -I../lib  -I../lib  -DBUILDING_LIBCURL   -I/usr/sfw/include   -O2 -Wno-system-headers -MT libcurl_la-file.lo -MD -MP -MF .deps/libcurl_la-file.Tpo -c -o libcurl_la-file.lo `test -f 'file.c' || echo './'`file.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I../include/curl -I../include -I../include -I../lib -I../lib -DBUILDING_LIBCURL -I/usr/sfw/include -O2 -Wno-system-headers -MT libcurl_la-file.lo -MD -MP -MF .deps/libcurl_la-file.Tpo -c file.c  -fPIC -DPIC -o .libs/libcurl_la-file.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I../include/curl -I../include -I../include -I../lib -I../lib -DBUILDING_LIBCURL -I/usr/sfw/include -O2 -Wno-system-headers -MT libcurl_la-file.lo -MD -MP -MF .deps/libcurl_la-file.Tpo -c file.c -o libcurl_la-file.o >/dev/null 2>&1
mv -f .deps/libcurl_la-file.Tpo .deps/libcurl_la-file.Plo
Output truncated…
Execute “Make test” command to test.
 [root@adminsplanet]# make test
Making all in certs
Making all in scripts
Making all in data
Making all in server
gcc -DHAVE_CONFIG_H   -I../../include/curl  -I../../include  -I../../include  -I../../lib  -I../../lib  -I/usr/sfw/include  -O2 -Wno-system-headers -MT ../../lib/getpart-mprintf.o -MD -MP -MF ../../lib/.deps/getpart-mprintf.Tpo -c -o ../../lib/getpart-mprintf.o `test -f '../../lib/mprintf.c' || echo './'`../../lib/mprintf.c
mv -f ../../lib/.deps/getpart-mprintf.Tpo ../../lib/.deps/getpart-mprintf.Po
Output truncated…

Finally execute “Make install” command.

[root@adminsplanet]# make install

Usage: For example if you want to download a file from internet

[root@adminsplanet]# curl -O http://abcd.com/files/file.tar.gz

Installation of VMware tools in RHEL server.

Below are the steps to install vm tools in a RHEL server.

Insert the vm tools CD/DVD into the drive.

Create a directory called ‘vmtools’

[root@adminsplanet ~]# mkdir /vmtools Mount the cdrom into the vmtools directory.

[root@adminsplanet ~]# mount /dev/cdrom /vmtools
mount: block device /dev/cdrom is write-protected, mounting read-only
Go to the vmtools direcotry and check the list of files.

[root@adminsplanet ~]# cd /vmtools
[root@adminsplanet ISO]# ls -l
total 63165
-r–r–r– 1 root root 1998 Feb 15 2012 manifest.txt
-r–r–r– 1 root root 64678021 Feb 15 2012 VMwareTools-8.6.5-621624.tar.gz
Copy the vmwaretools file to some other location like /tmp or /var/tmp.
And unzip the gz file.

[root@adminsplanet tmp]# gunzip VMwareTools-8.6.5-621624.tar.gz Now extract the tar file.

[root@adminsplanet tmp]#ls -l
-r–r–r– 1 root root 192266240 Nov 6 08:36 VMwareTools-8.6.5-621624.tar
[root@adminsplanet tmp]# tar -xvf VMwareTools-8.6.5-621624.tar
Execute the vmware-install.pl script file and provide the answers. This will install the vmware tools.

[root@adminsplanet vmware-tools-distrib]# ./vmware-install.pl
Creating a new VMware Tools installer database using the tar4 format.

Installing VMware Tools.

In which directory do you want to install the binary files?
[/usr/bin]

What is the directory that contains the init directories (rc0.d/ to rc6.d/)?
[/etc/rc.d]

What is the directory that contains the init scripts?
[/etc/rc.d/init.d]

In which directory do you want to install the daemon files?
[/usr/sbin]

In which directory do you want to install the library files?
[/usr/lib/vmware-tools]

The path “/usr/lib/vmware-tools” does not exist currently. This program is
going to create it, including needed parent directories. Is this what you want?
[yes]

In which directory do you want to install the documentation files?
[/usr/share/doc/vmware-tools]

The path “/usr/share/doc/vmware-tools” does not exist currently. This program
is going to create it, including needed parent directories. Is this what you
want? [yes]

The installation of VMware Tools 8.6.5 build-621624 for Linux completed
successfully. You can decide to remove this software from your system at any
time by invoking the following command: “/usr/bin/vmware-uninstall-tools.pl”.

Before running VMware Tools for the first time, you need to configure it by
invoking the following command: “/usr/bin/vmware-config-tools.pl”. Do you want
this program to invoke the command for you now? [yes]

Initializing…

Making sure services for VMware Tools are stopped.

Stopping VMware Tools services in the virtual machine:
Guest operating system daemon: [ OK ]
Unmounting HGFS shares: [ OK ]
Guest filesystem driver: [ OK ]

[EXPERIMENTAL] The VMware FileSystem Sync Driver (vmsync) is a new
feature that creates backups of virtual machines. Please refer to
the VMware Knowledge Base for more details on this capability.
Do you wish to enable this feature?
[no]

Found a compatible pre-built module for vmci. Installing it…
Found a compatible pre-built module for vsock. Installing it…
Found a compatible pre-built module for vmxnet3. Installing it…
Found a compatible pre-built module for pvscsi. Installing it…
Found a compatible pre-built module for vmmemctl. Installing it…

The VMware Host-Guest Filesystem allows for shared folders between
the host OS and the guest OS in a Fusion or Workstation virtual
environment. Do you wish to enable this feature? [no]

Found a compatible pre-built module for vmxnet. Installing it…

The vmblock enables dragging or copying files between host and guest
in a Fusion or Workstation virtual environment.
Do you wish to enable this feature?
[no]

Detected X version 7.1

Please choose one of the following display sizes that X will start with:

[1] “320×200″
[2] “320×240″
[3] “400×300″
[4] “512×384″
[5] “640×400″
[6] “640×480″
[7] “720×480″
[8] “800×480″
[9] “854×480″
[10] “720×576″
[11] “800×600″
[12] “1024×768″
[13] “1280×720″
[14] “1280×768″
[15] “1152×864″
[16] “1280×800″
[17] “1366×768″
[18] “1280×960″
[19] “1440×900″
[20] “1280×1024″
[21] “1400×1050″
[22] “1680×1050″
[23] “1600×1200″
[24] “1920×1080″
[25] “1920×1200″
[26] “1920×1440″
[27] “2048×1536″
[28] “2560×1600″
[29] “2560×1920″
Please enter a number between 1 and 29:

[3]

_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/adminsplanet.com:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: Linux 2.6.18-194.8.1.el5 i686 Red Hat, Inc.
Current Operating System: Linux adminsplanet.com 2.6.18-238.el5 #1
SMP Sun Dec 19 14:24:47 EST 2010 i686
Build Date: 01 September 2010
Build ID: xorg-x11-server 1.1.1-48.76.el5_5.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (–) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: “/tmp/vmware-config0/XF86ConfigLog.5380″, Time: Tue Nov 6 08:45:07 2012
(++) Using config file: “/tmp/vmware-config0/XF86Config.5380″
(EE) Failed to load module “vmwgfx” (module does not exist, 0)
(EE) vmware: Please ignore the above warnings about not being able to to load module/driver vmwgfx
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Multiple symbols for level 1/group 1 on key
> Using XF86Sleep, ignoring XF86Standby
> Warning: Symbol map for key redefined
> Using last definition for conflicting fields
Errors from xkbcomp are not fatal to the X server

X is running fine with the new config file.

FreeFontPath: FPE “unix/:7100″ refcount is 2, should be 1; fixing.
Creating a new initrd boot image for the kernel.
Starting VMware Tools services in the virtual machine:
Switching to guest configuration: [ OK ]
Paravirtual SCSI module: [ OK ]
Guest memory manager: [ OK ]
VM communication interface: [ OK ]
VM communication interface socket family: [ OK ]
File system sync driver: [ OK ]
Guest operating system daemon: [ OK ]
The configuration of VMware Tools 8.6.5 build-621624 for Linux for this running
kernel completed successfully.

You must restart your X session before any mouse or graphics changes take
effect.

You can now run VMware Tools by invoking “/usr/bin/vmware-toolbox-cmd” from the
command line or by invoking “/usr/bin/vmware-toolbox” from the command line
during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and
file and text copy/paste), you will need to do one (or more) of the following:
1. Manually start /usr/bin/vmware-user
2. Log out and log back into your desktop session; and,
3. Restart your X session.

Enjoy,

–the VMware team

Found VMware Tools CDROM mounted at /ISO. Ejecting device /dev/cdrom …

Install and enable ftp on Linux Server

Download the vsftpd rpm from RHN or online and copy it to the server.
Install the rpm with the below command.

[root@adminsplanet tmp]# rpm -ivh vsftpd-2.0.5-24.el5.i386.rpm
warning: vsftpd-2.0.5-24.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID e8                                                            562897
Preparing...                ############################## [100%]
   1:vsftpd                 ############################## [100%]
[root@adminsplanet tmp]#

Check the status. Now the service is not running.

[root@adminsplanet tmp]# service vsftpd status
vsftpd is stopped

Start the service.

[root@adminsplanet tmp]# /etc/init.d/vsftpd start
Starting vsftpd for vsftpd:                     [  OK  ]
[root@adminsplanet tmp]#

Check the status

[root@adminsplanet tmp]# service vsftpd status
vsftpd (pid 26434) is running...

Configure this service to start automatically during the start up.
Here the service is in off state in all the run levels.

[root@adminsplanet tmp]#  chkconfig --list | grep -i sftp
vsftpd          0:off   1:off   2:off   3:off   4:off   5:off   6:off
        gssftp:         off
        tftp:           off
[root@adminsplanet tmp]#

Start the service during the server startup with the below command.

[root@adminsplanet tmp]# chkconfig vsftpd on
[root@adminsplanet tmp]#  chkconfig --list | grep -i sftp
vsftpd          0:off   1:off   2:on    3:on    4:on    5:on    6:off
        gssftp:         off
        tftp:           off

SSH login without password in Linux

Below are the steps to login with SSH to another server without the password.
1.ssh-keygen – Generates the SSH public and private keys.
2.ssh-copy-id – Copies the keys from local server to remote server’s authorized keys_file
3. Login to the remote server without the password.

Example:

1. Create the SSH keys with ssh-keygen command.

[user1@serv1 ~]$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/user1/.ssh/id_rsa):  [press Enter]
Created directory '/home/user1/.ssh'.
Enter passphrase (empty for no passphrase): [press Enter]
Enter same passphrase again: [press Enter]
Your identification has been saved in /home/user1/.ssh/id_rsa.
Your public key has been saved in /home/user1/.ssh/id_rsa.pub.
The key fingerprint is:
d3:55:50:96:60:68:35:e6:85:39:a3:e4:9a:83:1d:67 user1@serv1

The keys will store in your home directory as above (/home/user1/.ssh)

2. Go to the ssh directory in home on serv1 and copy the public key to the remote server(serv2)

[use1@serv1 ~]$ cd .ssh
[user1@serv1 .ssh]$ ls -l
total 16
-rw------- 1 user1 user1 1675 Jul 20 02:40 id_rsa
-rw-r--r-- 1 user1 user1  399 Jul 20 02:40 id_rsa.pub

Copy the public key to the serv2.

[user1@serv1 .ssh]$ ssh-copy-id -i id_rsa.pub serv2
10
The authenticity of host 'serv2 (xx.xx.xx.xxx)' can't be established.
RSA key fingerprint is 7b:fd:7c:ea:51:69:df:6c:c8:30:e3:01:c7:ba:29:37.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'uapit011,xx.xx.xx.xxx' (RSA) to the list of known hosts.
Password:
Now try logging into the machine, with "ssh 'serv2'", and check in:

  .ssh/authorized_keys
to make sure we haven't added extra keys that you weren't expecting.

3. SSH to serv2 from serv1.

[user1@serv1 .ssh]$ ssh serv2
You will logging in to serv2 without entering password.

If the VRTSexplorer hung?

It can sometimes take the VRTSexplorer a long time to gather data and thus appear to be hung. On a complicated system it can sometimes take several hours for the VRTSexplorer to complete.

The VRTSExplorer script appears to be hung because the command it is running to collect information hangs.
For Example, one of the things that VRTSExplorer collects is df -k output, but if a filesystem is hung, df -k command hangs. As a result, the VRTSExplorer hangs while collecting the command’s output.

The solution is to find out what the VRTSExplorer is collecting and kill that unresponsive command.

Here is how you can do that on a Solaris machine:

1. Find the VRTSExplorer process id with below command.

# ps -ef | grep VRTSExplorer
root 26281 25990   0 08:25:34 pts/5       0:00 grep -i VRTSexplorer
root  3068 21882   0 07:38:51 pts/2       0:01 /bin/sh -- /opt/VRTSspt/VRTSexplorer/./vxvm
root 21882 21712   0 07:34:10 pts/2       0:01 /bin/sh -- /opt/VRTSspt/VRTSexplorer/./main.SunOS
root 21712 21097   0 07:34:01 pts/2       0:00 /bin/sh -- ./VRTSexplorer
root  7461  3068   0 07:41:08 pts/2       0:00 /bin/sh -- /opt/VRTSspt/VRTSexplorer/./bin.SunOS/dmpinfo

2. Find the hanging processes’s PID (The process that appears at the end of ptree output)

# ptree 21712
18273 /usr/share/centrifydc/sbin/sshd
  20753 /usr/share/centrifydc/sbin/sshd -R
    20958 /usr/share/centrifydc/sbin/sshd -R
      21057 -sh
        21097 -sh
          21712 /bin/sh -- ./VRTSexplorer
            21882 /bin/sh -- /opt/VRTSspt/VRTSexplorer/./main.SunOS
              3068  /bin/sh -- /opt/VRTSspt/VRTSexplorer/./vxvm
                7461  /bin/sh -- /opt/VRTSspt/VRTSexplorer/./bin.SunOS/dmpinfo
                  7535  /usr/lib/vxvm/diag.d/vxcheckhbaapi

3. Kill the hanging process so that the VRTSExplorer script can collect the rest of the output.

# kill -9 7535

How to take Veritas Explorer?

This tool is used for gathering the some important data from the server. Symantec support team may require this output file to troubleshoot the issue when you open a case with them. Below is the procedure to get the explorer output and transfer the file to Symantec support.

1. On your server, go to the following location

#cd /opt/VRTSspt/VRTSexplorer

2. Execute the following Script.

#./VRTSexplorer

It will ask some information, so provide the required information like file name, location etc… After entering above details, it will take some time to prepare the report. After finishing the report, transfer this output file from your server to ftp.veritas.com using with ftp. Provide the following information while you are doing ftp.

# ftp ftp.veritas.com
Name: symsupport@ftp.veritas.com
Password: iS*pp8rT1
use bin for binary transfer
>bin
go to the following directory.
>cd /incoming	
Upload the output file.
>put filename.gz
>bye

After transferring this file to Symantec support, inform them via mail or phone.

How to change a heartbeat link in VCS without downtime.

First make the configuration file as read and write.

#haconf -makerw

Freeze all the service groups.

#hagrp -freeze (group name) -persistent

Make the configuration file as read only.

#haconf -dump -makero

Stop the cluster with the below command. It will stop HAD but will keep the services running.

#hastop -force -all

Un-configure the GAB.

#gabconfig -U

Un-configure the LLT.

#lltconfig -U

Check for LLT and GAB modules information.

#modinfo |egrep "gab|llt"

Unload the GAB module first and then unload the LLT module.

#modunload -i 

Check for the modules again.

#modinfo |egrep "gab|llt"

After unloading the modules, you need to make changes to /etc/llttab file. Means you need to change the NIC name which you want to change. After making changes, run the following commands:

#lltconfig -c
#gabconfig -cx

Check the gabconfig output if it lists for port “a”.

#gabconfig -a 

Check the lltstat output if it is reflecting the LLT changes.

#lltstat -nvv|more

Start the cluster.

#hastart

Make the configuration file read and write.

#haconf -makerw

Un-freeze the service groups.

#hagrp -unfreeze (group name) -persistent 

Dump and make the configuration file as read-only.

#haconf -dump -makero

NOTE: Changes can be performed online but it is recommended to perform these changes in a scheduled downtime.

1 2 3