Showing posts with label Solaris 10. Show all posts
Showing posts with label Solaris 10. Show all posts

Wednesday, September 10, 2014

Solaris : How To Find Fiber Host Bus Adapter (Fiber HBA) WWN

see also link

# luxadm -e port
/devices/pci@300/pci@1/pci@0/pci@4/SUNW,emlxs@0/fp@0,0:devctl      CONNECTED
/devices/pci@300/pci@1/pci@0/pci@4/SUNW,emlxs@0,1/fp@0,0:devctl    CONNECTED

# fcinfo hba-port
HBA Port WWN: 10000090fa72ac46
        Port Mode: Initiator
        Port ID: 210760
        OS Device Name: /dev/cfg/c5
        Manufacturer: Emulex
        Model: LPe12002-S
        Firmware Version: LPe12002-S 1.00a12
        FCode/BIOS Version: Boot:5.03a0 Fcode:3.01a1
        Serial Number: 4925382+1422000085
        Driver Name: emlxs
        Driver Version: 2.90.15.0 (2014.01.22.14.50)
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb
        Current Speed: 8Gb
        Node WWN: 20000090fa72ac46
        NPIV Not Supported
HBA Port WWN: 10000090fa72ac47
        Port Mode: Initiator
        Port ID: 210680
        OS Device Name: /dev/cfg/c6
        Manufacturer: Emulex
        Model: LPe12002-S
        Firmware Version: LPe12002-S 1.00a12
        FCode/BIOS Version: Boot:5.03a0 Fcode:3.01a1
        Serial Number: 4925382+1422000085
        Driver Name: emlxs
        Driver Version: 2.90.15.0 (2014.01.22.14.50)
        Type: N-port
        State: online
        Supported Speeds: 2Gb 4Gb 8Gb
        Current Speed: 8Gb
        Node WWN: 20000090fa72ac47
        NPIV Not Supported

Wednesday, April 23, 2014

Configure 2-node Veritas Cluster Server on Solaris 10 (no I/O fencing)

# /opt/VRTS/install/installsfha601 -configure

    Veritas Storage Foundation and High Availability 6.0.1 Configure 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/installsfha601-201404231512rwa while
installsfha601 is in progress.

Enter the Solaris x64 system names separated by spaces: [q,?] sol2 sol3

    Veritas Storage Foundation and High Availability 6.0.1 Configure Program
                                    sol2 sol3

Logs are being written to /var/tmp/installsfha601-201404231512rwa while
installsfha601 is in progress

    Verifying systems: 100%

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

    Checking system communication ..................................... Done
    Checking release compatibility .................................... Done
    Checking installed product ........................................ Done
    Checking platform version ......................................... Done
    Performing product prechecks ...................................... Done

System verification checks completed successfully

I/O Fencing

It needs to be determined at this time if you plan to configure I/O Fencing in
enabled or disabled mode, as well as help in determining the number of network
interconnects (NICS) required on your systems. If you configure I/O Fencing in
enabled mode, only a single NIC is required, though at least two are
recommended.

A split brain can occur if servers within the cluster become unable to
communicate for any number of reasons. If I/O Fencing is not enabled, you run
the risk of data corruption should a split brain occur. Therefore, to avoid data
corruption due to split brain in CFS environments, I/O Fencing has to be
enabled.

If you do not enable I/O Fencing, you do so at your own risk

See the Administrator's Guide for more information on I/O Fencing

Do you want to configure I/O Fencing in enabled mode? [y,n,q,?] (y)

To configure VCS, answer the set of questions on the next screen.

When [b] is presented after a question, 'b' may be entered to go back to the
first question of the configuration set.

When [?] is presented after a question, '?' may be entered for help or
additional information about the question.

Following each set of questions, the information you have entered will be
presented for confirmation.  To repeat the set of questions and correct any
previous errors, enter 'n' at the confirmation prompt.

No configuration changes are made to the systems until all configuration
questions are completed and confirmed.

Press [Enter] to continue:

To configure VCS for SFHA the following information is required:

        A unique cluster name
        One or more NICs per system used for heartbeat links
        A unique cluster ID number between 0-65535

        One or more heartbeat links are configured as private links
        You can configure one heartbeat link as a low-priority link

All systems are being configured to create one cluster.

Enter the unique cluster name: [q,?] sol


     1)  Configure heartbeat links using LLT over Ethernet
     2)  Configure heartbeat links using LLT over UDP
     3)  Automatically detect configuration for LLT over Ethernet
     b)  Back to previous menu

How would you like to configure heartbeat links? [1-3,b,q,?] (1)


    Discovering NICs on sol2 .................... Discovered e1000g0 e1000g1

Enter the NIC for the first private heartbeat link on sol2: [b,q,?] (e1000g1)
Would you like to configure a second private heartbeat link? [y,n,q,b,?] (n)

Do you want to configure an additional low-priority heartbeat link? [y,n,q,b,?]
(n) y

Enter the NIC for the low-priority heartbeat link on sol2: [b,q,?] (e1000g0)

Are you using the same NICs for private heartbeat links on all systems?
[y,n,q,b,?] (y)

    Checking media speed for e1000g1 on sol2 ..................... 1000 Mbps
    Checking media speed for e1000g1 on sol3 ..................... 1000 Mbps

Enter a unique cluster ID number between 0-65535: [b,q,?] (27375)

The cluster cannot be configured if the cluster ID 27375 is in use by another
cluster. Installer can perform a check to determine if the cluster ID is
duplicate. The check will take less than a minute to complete.

Would you like to check if the cluster ID is in use by another cluster? [y,n,q]
(y)


    Checking cluster ID ............................................... Done

Duplicated cluster ID detection passed. The cluster ID 27375 can be used for the
cluster.

Press [Enter] to continue:


Cluster information verification:

        Cluster Name:      sol
        Cluster ID Number: 27375
        Private Heartbeat NICs for sol2:
                link1=e1000g1
        Low-Priority Heartbeat NIC for sol2:
                link-lowpri1=e1000g0
        Private Heartbeat NICs for sol3:
                link1=e1000g1
        Low-Priority Heartbeat NIC for sol3:
                link-lowpri1=e1000g0

Is this information correct? [y,n,q,?] (y)


The following data is required to configure the Virtual IP of the Cluster:

        A public NIC used by each system in the cluster
        A Virtual IP address and netmask

Do you want to configure the Virtual IP? [y,n,q,?] (n) y


Active NIC devices discovered on sol2: e1000g0

Enter the NIC for Virtual IP of the Cluster to use on sol2: [b,q,?] (e1000g0)

Is e1000g0 to be the public NIC used by all systems? [y,n,q,b,?] (y)

Enter the Virtual IP address for the Cluster: [b,q,?] 192.168.1.189
Enter the NetMask for IP 192.168.1.189: [b,q,?] (255.255.255.0)

Cluster Virtual IP verification:

        NIC: e1000g0
        IP: 192.168.1.189
        NetMask: 255.255.255.0

Is this information correct? [y,n,q] (y)


Veritas Cluster Server can be configured in secure mode

Running VCS in Secure Mode guarantees that all inter-system communication is
encrypted, and users are verified with security credentials.

When running VCS in Secure Mode, NIS and system usernames and passwords are used
to verify identity. VCS usernames and passwords are no longer utilized when a
cluster is running in Secure Mode.

Would you like to configure the VCS cluster in secure mode? [y,n,q,?] (n)

The following information is required to add VCS users:

        A user name
        A password for the user
        User privileges (Administrator, Operator, or Guest)

Do you wish to accept the default cluster credentials of 'admin/password'?
[y,n,q] (y)


Do you want to add another user to the cluster? [y,n,q] (n)

VCS User verification:

        User: admin     Privilege: Administrators

        Passwords are not displayed

Is this information correct? [y,n,q] (y)

The following information is required to configure SMTP notification:

        The domain-based hostname of the SMTP server
        The email address of each SMTP recipient
        A minimum severity level of messages to send to each recipient

Do you want to configure SMTP notification? [y,n,q,?] (n)

The following information is required to configure SNMP notification:

        System names of SNMP consoles to receive VCS trap messages
        SNMP trap daemon port numbers for each console
        A minimum severity level of messages to send to each console

Do you want to configure SNMP notification? [y,n,q,?] (n)

All SFHA processes that are currently running must be stopped

Do you want to stop SFHA processes now? [y,n,q,?] (y)

Logs are being written to /var/tmp/installsfha601-201404231512rwa while
installsfha601 is in progress

    Starting SFHA: 100%

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

    Starting vxesd .................................................... Done
    Starting vxrelocd ................................................. Done
    Starting vxconfigbackupd .......................................... Done
    Starting vxportal ................................................. Done
    Starting fdd ...................................................... Done
    Starting llt ...................................................... Done
    Starting gab ...................................................... Done
    Starting amf ...................................................... Done
    Starting had ...................................................... Done
    Starting CmdServer ................................................ Done
    Starting vxdbd .................................................... Done
    Starting odm ...................................................... Done
    Performing SFHA poststart tasks ................................... Done

Veritas Storage Foundation and High Availability Startup completed successfully



    Veritas Storage Foundation and High Availability 6.0.1 Configure Program
                                    sol2 sol3

Fencing configuration
     1)  Configure Coordination Point client based fencing
     2)  Configure disk based fencing

Select the fencing mechanism to be configured in this Application Cluster:
[1-2,q] 2

This fencing configuration option requires a restart of VCS. Installer will stop
VCS at a later stage in this run. Do you want to continue? [y,n,q,b,?] y

Do you have SCSI3 PR enabled disks? [y,n,q,b] (y) n

Since you don't have SCSI3 PR enabled disks, you cannot configure disk based
fencing but you can use Coordination Point client based fencing

Do you want to retry fencing configuration? [y,n,q,b] (n)

The updates to VRTSaslapm package are released via the Symantec SORT web page:
https://sort.symantec.com/asl. To make sure you have the latest version of
VRTSaslapm (for up to date ASLs and APMs), download and install the latest
package from the SORT web page.

installsfha601 log files, summary file, and response file are saved at:

        /opt/VRTS/install/logs/installsfha601-201404231512rwa

Would you like to view the summary file? [y,n,q] (n) n

# /opt/VRTSvcs/bin/hastatus -sum

-- SYSTEM STATE
-- System               State                Frozen

A  sol2                 RUNNING              0
A  sol3                 RUNNING              0

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State        

B  ClusterService  sol2                 Y          N               ONLINE       
B  ClusterService  sol3                 Y          N               OFFLINE      

# cat /etc/llthosts
0 sol2
1 sol3
# cat /etc/llttab
set-node sol2
set-cluster 27375
link e1000g1 /dev/e1000g:1 - ether - -
link-lowpri e1000g0 /dev/e1000g:0 - ether - -

# cat /etc/gabtab
/sbin/gabconfig -c -n2


# cat /etc/VRTSvcs/conf/config/main.cf
include "OracleASMTypes.cf"
include "types.cf"
include "Db2udbTypes.cf"
include "OracleTypes.cf"
include "SybaseTypes.cf"

cluster sol (
        UserNames = { admin = anoGniNkoJooMwoInl }
        ClusterAddress = "192.168.1.189"
        Administrators = { admin }
        )

system sol2 (
        )

system sol3 (
        )

group ClusterService (
        SystemList = { sol2 = 0, sol3 = 1 }
        AutoStartList = { sol2, sol3 }
        OnlineRetryLimit = 3
        OnlineRetryInterval = 120
        )

        IP webip (
                Device = e1000g0
                Address = "192.168.1.189"
                NetMask = "255.255.255.0"
                )

        NIC csgnic (
                Device = e1000g0
                )

        webip requires csgnic


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

# ping 192.168.1.189 (virtual IP)
192.168.1.189 is alive

# netstat -anp
Net to Media Table: IPv4
Device   IP Address               Mask      Flags      Phys Addr
------ -------------------- --------------- -------- ---------------
e1000g0 192.168.1.190        255.255.255.255 o        08:00:27:66:02:a4
e1000g0 192.168.1.102        255.255.255.255          7c:e9:d3:86:3e:12
e1000g0 192.168.1.104        255.255.255.255 o        7c:e9:d3:f7:ac:9b
e1000g0 192.168.1.189        255.255.255.255 SPLA     08:00:27:9a:15:5a
e1000g0 192.168.1.191        255.255.255.255 SPLA     08:00:27:9a:15:5a
e1000g0 224.0.0.0            240.0.0.0       SM       01:00:5e:00:00:00




Install Veritas Storage Foundation and High Availability (SFHA) on Solaris 10

Veritas Storage Foundation and High Availability (SFHA) is VxVM and VCS

# uname -a
SunOS sol2 5.10 Generic_147148-26 i86pc i386 i86pc

# cd dvd2-sol_x64/sol10_x64
# ./installer

    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,?] I

    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


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


     1)  Install minimal required packages - 650 MB required
     2)  Install recommended packages - 1116 MB required
     3)  Install all packages - 1153 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


Enter the Solaris x64 system names separated by spaces: [q,?] sol2 sol3

Logs are being written to /var/tmp/installer-201404231324onc 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

The following warnings were discovered on the systems:

CPI WARNING V-9-40-4970 To avoid a potential reboot after installation, you
should modify the /etc/system file on sol2 with the appropriate values, and
reboot prior to package installation.

Appropriate /etc/system file entries are shown below:
        set lwp_default_stksize=0x6000
        set rpcmod:svc_default_stksize=0x6000

CPI WARNING V-9-40-4970 To avoid a potential reboot after installation, you
should modify the /etc/system file on sol3 with the appropriate values, and
reboot prior to package installation.

Appropriate /etc/system file entries are shown below:
        set lwp_default_stksize=0x6000
        set rpcmod:svc_default_stksize=0x6000

Do you want to continue? [y,n,q] (y)

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
VRTSob            Veritas Enterprise Administrator Service by Symantec
VRTSvxfs          Veritas File System
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

Press [Enter] to continue:

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:


Logs are being written to /var/tmp/installer-201404231324onc while installer is
in progress

    Installing SFHA: 100%

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

    Installing VRTSgab package ........................................ Done
    Installing VRTSvxfen package ...................................... Done
    Installing VRTSamf package ........................................ Done
    Installing VRTSvcs package ........................................ Done
    Installing VRTScps package ........................................ Done
    Installing VRTSvcsag package ...................................... Done
    Installing VRTSvcsea package ...................................... Done
    Installing VRTSdbed package ....................................... Done
    Installing VRTSodm package ........................................ Done
    Installing VRTSsfmh package ....................................... Done
    Installing VRTSvbs package ........................................ Done
    Installing VRTSsfcpi601 package ................................... Done
    Performing SFHA postinstall tasks ................................. Done

Veritas Storage Foundation and High Availability Install completed successfully


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)

     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)

Registering SFHA license
SFHA vxkeyless key (SFHASTD) successfully registered on sol2
SFHA vxkeyless key (SFHASTD) successfully registered on sol3

The updates to VRTSaslapm package are released via the Symantec SORT web page:
https://sort.symantec.com/asl. To make sure you have the latest version of
VRTSaslapm (for up to date ASLs and APMs), download and install the latest
package from the SORT web page.

Veritas Storage Foundation and High Availability cannot be started without
configuration.

Run the '/opt/VRTS/install/installsfha601 -configure' command when you are ready
to configure Veritas Storage Foundation and High Availability.

Checking online updates for Veritas Storage Foundation and High Availability
6.0.1

        Attempted to connect to https://sort.symantec.com to check for product
updates, but connection failed.
        Please visit https://sort.symantec.com to check for available product
updates and information.


The following packages require reboot while installing them on sol2:
        VRTSvxfs

The following packages require reboot while installing them on sol3:
        VRTSvxfs

It is strongly recommended to reboot the following systems:
        sol2
        sol3

Execute '/usr/sbin/shutdown -y -i6 -g0' to properly restart your systems

installer log files, summary file, and response file are saved at:

        /opt/VRTS/install/logs/installer-201404231324onc

Would you like to view the summary file? [y,n,q] (n)




Tuesday, April 22, 2014

How to restart sshd in Solaris 10

# svcadm restart ssh

NAME
     svcadm - manipulate service instances

SYNOPSIS
     /usr/sbin/svcadm [-v] enable [-rst] {FMRI | pattern}...

     /usr/sbin/svcadm [-v] disable [-st] {FMRI | pattern}...

     /usr/sbin/svcadm [-v] restart {FMRI | pattern}...

     /usr/sbin/svcadm [-v] refresh {FMRI | pattern}...

     /usr/sbin/svcadm [-v] clear {FMRI | pattern}...

     /usr/sbin/svcadm [-v] mark [-It] instance_state
         {FMRI | pattern}...

     /usr/sbin/svcadm [-v] milestone [-d] milestone_FMRI

Install Veritas Cluster Server on Solaris 10

# uname -a
SunOS sol1 5.10 Generic_147148-26 i86pc i386 i86pc

# cd dvd2-sol_x64/sol10_x64/cluster_server

# ls
EULA          copyright     installvcs    tools         uninstallvcs

# ./installvcs

Enter y to agree to the End User License Agreement (EULA).

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

                  Veritas Cluster Server 6.0.1 Install Program

     1)  Install minimal required packages - 374 MB required
     2)  Install recommended packages - 628 MB required
     3)  Install all packages - 663 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

Enter the Solaris x64 system names separated by spaces: [q,?] sol1

                  Veritas Cluster Server 6.0.1 Install Program
                                      sol1

Logs are being written to /var/tmp/installvcs-201404221225Cml while installvcs
is in progress

    Verifying systems: 87%                                           _______

    Estimated time remaining: (mm:ss) 0:05                            7 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 /


The following Veritas Cluster Server packages will be installed on all systems:

Package           Package Description

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
VRTSvbs           Veritas Virtual Business Service

Press [Enter] to continue:


Logs are being written to /var/tmp/installvcs-201404221225Cml while installvcs
is in progress

    Installing VCS: 100%

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

    Performing VCS preinstall tasks ................................... Done
    Installing VRTSllt package ........................................ Done
    Installing VRTSgab package ........................................ Done
    Installing VRTSvxfen package ...................................... Done
    Installing VRTSamf package ........................................ Done
    Installing VRTSvcs package ........................................ Done
    Installing VRTScps package ........................................ Done
    Installing VRTSvcsag package ...................................... Done
    Installing VRTSvcsea package ...................................... Done
    Installing VRTSvbs package ........................................ Done
    Performing VCS postinstall tasks .................................. Done

Veritas Cluster Server Install completed successfully

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) 2

Would you like to enable the Global Cluster Option? [y,n,q] (n) n

Registering VCS license
VCS vxkeyless key (VCS) successfully registered on sol1

Would you like to configure VCS on sol1? [y,n,q] (n) n

Veritas Cluster Server cannot be started without configuration.

Run the '/opt/VRTS/install/installvcs601 -configure' command when you are ready
to configure Veritas Cluster Server.

Checking online updates for Veritas Cluster Server 6.0.1

        Attempted to connect to https://sort.symantec.com to check for product
updates, but connection failed.
        Please visit https://sort.symantec.com to check for available product
updates and information.


installvcs log files, summary file, and response file are saved at:

        /opt/VRTS/install/logs/installvcs-201404221225Cml

Would you like to view the summary file? [y,n,q] (n)

# pkginfo | grep -i vrts
system      VRTSamf                          Veritas Asynchronous Monitoring Framework Module
system      VRTSaslapm                       Array Support Libraries and Array Policy Modules for Veritas Volume Manager
optional    VRTScps                          Veritas Co-ordination Point Server by Symantec
application VRTSdbed                         Veritas Storage Foundation for Databases by Symantec
system      VRTSgab                          Veritas Group Membership and Atomic Broadcast by Symantec
system      VRTSllt                          Veritas Low Latency Transport by Symantec
application VRTSob                           Veritas Enterprise Administrator Service by Symantec
system      VRTSodm                          Veritas Oracle Disk Manager by Symantec
optional    VRTSperl                         Perl 5.14.2 for Veritas
optional    VRTSsfcpi601                     Veritas Storage Foundation Installer
application VRTSsfmh                         Veritas Operations Manager Managed Host by Symantec
application VRTSspt                          Veritas Software Support Tools by Symantec
optional    VRTSvbs                          Virtual Business Services by Symantec
system      VRTSvcs                          Veritas Cluster Server by Symantec
system      VRTSvcsag                        Veritas Cluster Server Bundled Agents by Symantec
system      VRTSvcsea                        Veritas High Availability Enterprise Agents by Symantec
application VRTSvlic                         Symantec License Utilities
system      VRTSvxfen                        Veritas I/O Fencing by Symantec
system      VRTSvxfs                         Veritas File System by Symantec
system      VRTSvxvm                         Binaries for VERITAS Volume Manager by Symantec




Saturday, April 19, 2014

Management of iSCSI initiators : Connect to a iSCSI target on Solaris 10

Add the target to a list of discovery addresses.
The IP address is the server where we have the iscsi target :

iscsiadm add discovery-address IP_ADDRESS

This command won't produce any output.

# iscsiadm add discovery-address 192.168.1.192

To see if the server has any iscsi device available for others, let's do :
# iscsiadm list discovery-address -v

the output  :
Discovery Address: 192.168.1.192:3260
        Target name: iqn.2006-01.com.openfiler:tsn.24def7fd4a0a
                Target address:   192.168.1.192:3260, 1


To use the iSCSI target :

# iscsiadm add static-config NAME_OF_ISCSI_TARGET,IP_ADDRESS_OF_ISCSI_TARGET;

example :
# iscsiadm add static-config iqn.2006-01.com.openfiler:tsn.24def7fd4a0a,192.168.1.192

We have to check if static-config service is enable. Check this out with :
# iscsiadm list discovery

Our output  :
Discovery:
        Static: disabled
        Send Targets: disabled
        iSNS: disabled

We won't be able to see the iSCSI drive. 
To be able to use it, we have to enable the static service :
# iscsiadm modify discovery --static enable

and the ouput  :
Discovery:
        Static: enabled
        Send Targets: disabled
        iSNS: disabled

now, we can see the new iSCSI drive, check it out with format if the new drive shows up

# format
:
:
       3. c2t1d0 <OPNFILE-VIRTUAL-DISK   -0    cyl 1021 alt 2 hd 64 sec 32>
          /iscsi/disk@0000iqn.2006-01.com.openfiler%3Atsn.24def7fd4a0a0001,0
:
:




Veritas Volume Manager VxVM not started after reboot Solaris 10

The presence of /etc/vx/reconfig.d/state.d/install-db will prevent Volume Manager from starting up. This is a flag file and is only checked by vxvm-recover, vxvm-startup1, vxvm-startup2 and vxvm-sysboot scripts. On Solaris 10 these files can be found in /lib/svc/method.

To correct this problem, remove the follwing file:

rm /etc/vx/reconfig.d/state.d/install-db

and then reboot the system. VxVM should start now.


Tuesday, April 15, 2014

Use ZFS snapshot and rollback file system with snapshot on Solaris 10

# zfs snapshot -r labpool/zman@snap1
# zfs list -r -t all labpool
NAME                 USED  AVAIL  REFER  MOUNTPOINT
labpool             2.82M  1.11G  46.4K  /labpool
labpool/zman        2.71M  1.11G  2.71M  /labpool/zman
labpool/zman@snap1      0      -  2.71M  -
# ls -al /labpool/zman/man1/zip.1
-r--r--r--   1 root     bin        85963 Feb 29  2012 /labpool/zman/man1/zip.1

Now we delete this file

# rm /labpool/zman/man1/zip.1
# ls -al /labpool/zman/man1/zip.1
/labpool/zman/man1/zip.1: No such file or directory

Now we rollback

# zfs rollback labpool/zman@snap1
# ls -al /labpool/zman/man1/zip.1
-r--r--r--   1 root     bin        85963 Feb 29  2012 /labpool/zman/man1/zip.1

Now we create a clone

# zfs clone labpool/zman@snap1 labpool/zmanclone
# zfs list -r -t all labpool
NAME                 USED  AVAIL  REFER  MOUNTPOINT
labpool             2.87M  1.11G  46.4K  /labpool
labpool/zman        2.71M  1.11G  2.71M  /labpool/zman
labpool/zman@snap1  1.50K      -  2.71M  -
labpool/zmanclone   1.50K  1.11G  2.71M  /labpool/zmanclone

Create ZFS file system on Solaris 10

Now we try create ZFS file system

# uname -a
SunOS sol1 5.10 Generic_147148-26 i86pc i386 i86pc

# mkfile 200m disk0
# mkfile 200m disk1
# mkfile 200m disk2
# mkfile 200m disk3

# zpool create labpool raidz disk0 disk1 disk2 disk3
# zpool list
NAME      SIZE  ALLOC   FREE  CAP  HEALTH  ALTROOT
labpool   780M   120K   780M   0%  ONLINE  -
rpool    31.8G  10.3G  21.4G  32%  ONLINE  -

# mkfile 200m disk4
# mkfile 200m disk5
# mkfile 200m disk6
# mkfile 200m disk7

# zpool add labpool raidz disk4 disk5 disk6 disk7
# zpool list
NAME      SIZE  ALLOC   FREE  CAP  HEALTH  ALTROOT
labpool  1.52G   168K  1.52G   0%  ONLINE  -
rpool    31.8G  11.1G  20.6G  35%  ONLINE  -

# zfs list labpool
NAME      USED  AVAIL  REFER  MOUNTPOINT
labpool  97.2K  1.11G  44.9K  /labpool

# df -h /labpool
Filesystem             size   used  avail capacity  Mounted on
labpool                1.1G    45K   1.1G     1%    /labpool

Now we try file system compression

# zfs create labpool/zman

# df -h /labpool/zman
Filesystem             size   used  avail capacity  Mounted on
labpool/zman           1.1G    45K   1.1G     1%    /labpool/zman

# zfs set compression=gzip labpool/zman

# cp -rp /usr/share/man/man1 /labpool/zman
# du -sh /usr/share/man/man1 /labpool/zman
 6.7M   /usr/share/man/man1
 785K   /labpool/zman


# zfs get all labpool
NAME     PROPERTY              VALUE                  SOURCE
labpool  type                  filesystem             -
labpool  creation              Tue Apr 15  9:53 2014  -
labpool  used                  2.82M                  -
labpool  available             1.11G                  -
labpool  referenced            46.4K                  -
labpool  compressratio         2.80x                  -
labpool  mounted               yes                    -
labpool  quota                 none                   default
labpool  reservation           none                   default
labpool  recordsize            128K                   default
labpool  mountpoint            /labpool               default
labpool  sharenfs              off                    default
labpool  checksum              on                     default
labpool  compression           off                    default
labpool  atime                 on                     default
labpool  devices               on                     default
labpool  exec                  on                     default
labpool  setuid                on                     default
labpool  readonly              off                    default
labpool  zoned                 off                    default
labpool  snapdir               hidden                 default
labpool  aclmode               discard                default
labpool  aclinherit            restricted             default
labpool  canmount              on                     default
labpool  shareiscsi            off                    default
labpool  xattr                 on                     default
labpool  copies                1                      default
labpool  version               5                      -
labpool  utf8only              off                    -
labpool  normalization         none                   -
labpool  casesensitivity       mixed                  -
labpool  vscan                 off                    default
labpool  nbmand                off                    default
labpool  sharesmb              off                    default
labpool  refquota              none                   default
labpool  refreservation        none                   default
labpool  primarycache          all                    default
labpool  secondarycache        all                    default
labpool  usedbysnapshots       0                      -
labpool  usedbydataset         46.4K                  -
labpool  usedbychildren        2.77M                  -
labpool  usedbyrefreservation  0                      -
labpool  logbias               latency                default
labpool  sync                  standard               default
labpool  rekeydate             -                      default
labpool  rstchown              on                     default


Thursday, April 3, 2014

Setup Static IP on Solaris 10


# ls -ld /etc/host*
-rw-r--r--   1 root     root           5 Apr  2 19:14 /etc/hostname.e1000g0
lrwxrwxrwx   1 root     root          12 Jan 22  2013 /etc/hosts -> ./inet/hosts
-rw-r--r--   1 root     root           5 Apr  2 19:14 hostname.e1000g0
lrwxrwxrwx   1 root     root          12 Jan 22  2013 hosts -> ./inet/hosts
# ifconfig e1000g0
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
        inet 192.168.1.195 netmask ffffff00 broadcast 192.168.1.255
        ether 8:0:27:13:f7:38

# cat /etc/hostname.e1000g0
sol1
# ls -ld /etc/defaul*
drwxr-xr-x   2 root     sys           31 Apr  2 23:53 /etc/default
-rw-r--r--   1 root     root          12 Apr  2 19:14 /etc/defaultrouter
# cat /etc/defaultrouter
192.168.1.1
# cat /etc/inet/hosts
#
# Internet host table
#
127.0.0.1       localhost
::1     localhost
192.168.1.195   sol1    loghost

Wednesday, April 2, 2014

Install Veritas Volume Manager on Solaris 10


# uname -a

SunOS sol1 5.10 Generic_147148-26 i86pc i386 i86pc
# cd dvd2-sol_x64/sol10_x64
# ./installer

    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,?] I

     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] 3

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


     1)  Install minimal required packages - 379 MB required
     2)  Install recommended packages - 728 MB required
     3)  Install all packages - 730 MB required
     4)  Display packages to be installed for each option

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

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

Logs are being written to /var/tmp/installer-201404022341tms 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

The following warnings were discovered on the systems:

CPI WARNING V-9-30-1997 The swap size on sol1 is 970 megabytes, the minimal swap
size required by product SF is 1024 megabytes

CPI WARNING V-9-40-4970 To avoid a potential reboot after installation, you
should modify the /etc/system file on sol1 with the appropriate values, and
reboot prior to package installation.

Appropriate /etc/system file entries are shown below:
        set lwp_default_stksize=0x6000
        set rpcmod:svc_default_stksize=0x6000

Do you want to continue? [y,n,q] (y)

The following Veritas Storage Foundation 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
VRTSob            Veritas Enterprise Administrator Service by Symantec
VRTSvxfs          Veritas File System
VRTSdbed          Veritas Storage Foundation Databases
VRTSodm           Veritas Oracle Disk Manager
VRTSsfmh          Veritas Storage Foundation Managed Host by Symantec
VRTSsfcpi601      Veritas Storage Foundation Installer

Press [Enter] to continue:

Logs are being written to /var/tmp/installer-201404022341tms while installer is
in progress

    Installing SF: 100%

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

    Performing SF preinstall tasks .................................... Done
    Installing VRTSperl package ....................................... Done
    Installing VRTSvlic package ....................................... Done
    Installing VRTSspt package ........................................ Done
    Installing VRTSvxvm package ....................................... Done
    Installing VRTSaslapm package ..................................... Done
    Installing VRTSob package ......................................... Done
    Installing VRTSvxfs package ....................................... Done
    Installing VRTSdbed package ....................................... Done
    Installing VRTSodm package ........................................ Done
    Installing VRTSsfmh package ....................................... Done
    Installing VRTSsfcpi601 package ................................... Done
    Performing SF postinstall tasks ................................... Done

Veritas Storage Foundation Install completed successfully

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)

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

Select product mode to license: [1-2,b,q,?] (2)

Would you like to enable the Veritas Volume Replicator? [y,n,q] (n)

Would you like to enable the Veritas Volume Replicator? [y,n,q] (n)

Registering SF license
SF vxkeyless key (SFENT) successfully registered on sol1

The updates to VRTSaslapm package are released via the Symantec SORT web page:
https://sort.symantec.com/asl. To make sure you have the latest version of
VRTSaslapm (for up to date ASLs and APMs), download and install the latest
package from the SORT web page.

Veritas Storage Foundation cannot be started without configuration.

Run the '/opt/VRTS/install/installsf601 -configure' command when you are ready
to configure Veritas Storage Foundation.

Checking online updates for Veritas Storage Foundation 6.0.1

        Attempted to connect to https://sort.symantec.com to check for product
updates, but connection failed.
        Please visit https://sort.symantec.com to check for available product
updates and information.

The following packages require reboot while installing them on sol1:
        VRTSvxfs

It is strongly recommended to reboot the following systems:
        sol1

Execute '/usr/sbin/shutdown -y -i6 -g0' to properly restart your systems

installer log files, summary file, and response file are saved at:

        /opt/VRTS/install/logs/installer-201404022341tms

Would you like to view the summary file? [y,n,q] (n)

shutdown -y -i6 -g0


after reboot :

# vxdisk list
VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
# vxconfigd
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
# vxdctl init
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
# vxdctl enable
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS

Please note that only after running vxdctl enable then vxdisk list will show output

Now 2 more disks are added 

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1t0d0s2     auto:none       -            -            online invalid

c1t1d0s2     auto:none       -            -            online invalid

# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
usb0/1                         usb-input    connected    configured   ok
usb0/2                         unknown      empty        unconfigured ok
:
:

# /usr/sbin/devfsadm -Cvc disk
devfsadm[3767]: verbose: symlink /dev/dsk/c1d0s0 -> ../../devices/pci@0,0/pci-ide@1,1/ide@1/cmdk@0,0:a
devfsadm[3767]: verbose: symlink /dev/dsk/c1d0s1 -> ../../devices/pci@0,0/pci-ide@1,1/ide@1/cmdk@0,0:b
devfsadm[3767]: verbose: symlink /dev/dsk/c1d0s2 -> ../../devices/pci@0,0/pci-ide@1,1/ide@1/cmdk@0,0:c
devfsadm[3767]: verbose: symlink /dev/dsk/c1d0s3 -> ../../devices/pci@0,0/pci-ide@1,1/ide@1/cmdk@0,0:d
:
:


# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:none       -            -            online invalid
c1d1s2       auto:none       -            -            online invalid
# vxddladm assign names

# vxddladm set namingscheme=ebn
# vxddladm assign names

vxdisksetup command  brings the disks in to veritas volume manager control. By default this will format the disk in CDS(Cross Data platform Sharing ). Other formats are sliced and simple. sliced will be used for boot disks. In this case, we are using virtual disk, so we have to use format=simple, otherwise, we will get the following error :

# /etc/vx/bin/vxdisksetup -i c1d0

VxVM vxdisksetup ERROR V-5-2-1814 c1d0: Invalid disk device for 'cdsdisk' format

# /etc/vx/bin/vxdisksetup -i c1d0 format=simple
# vxdisk -e list
DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
c0d0s2       auto:ZFS       -            -           ZFS                  c0d0s2           -
c1d0s2       auto:simple    -            -           online               c1d0s2           -
c1d1s2       auto:none      -            -           online invalid       c1d1s2           -

# /etc/vx/bin/vxdisksetup -i c1d1 format=simple

# vxdisk -e list
DEVICE       TYPE           DISK        GROUP        STATUS               OS_NATIVE_NAME   ATTR
c0d0s2       auto:ZFS       -            -           ZFS                  c0d0s2           -
c1d0s2       auto:simple    -            -           online               c1d0s2           -
c1d1s2       auto:simple    -            -           online               c1d1s2           -


Now we create a disk group called appdg 

# vxdg init appdg appdisk0=c1d0s2
VxVM vxdg ERROR V-5-1-6478 Device c1d0s2 cannot be added to a CDS disk group

To solve the above error. I checked the options in vxdg :


init groupname [[disk=]device ...] [nconfig=default|all|ncopies] [nlog=default|all|ncopies] [cds=on|off] [minor=base-minor]


# vxdg init appdg appdisk0=c1d0s2 cds=off


Add disk to existing disk group


# vxdg -g appdg adddisk appdisk1=c1d1s2

# vxdg list
NAME         STATE           ID
appdg        enabled              1396545212.14.sol1

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:simple     appdisk0     appdg        online
c1d1s2       auto:simple     appdisk1     appdg        online

# vxdg -g appdg rmdisk appdisk1
# vxdg list
NAME         STATE           ID
appdg        enabled              1396545212.14.sol1
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:simple     appdisk0     appdg        online
c1d1s2       auto:simple     -            -            online

# vxdg -g appdg adddisk appdisk1=c1d1s2
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:simple     appdisk0     appdg        online
c1d1s2       auto:simple     appdisk1     appdg        online

# vxdg -g appdg free
DISK         DEVICE       TAG          OFFSET    LENGTH    FLAGS
appdisk0     c1d0s2       c1d0         0         2023152   -
appdisk1     c1d1s2       c1d1         0         2023152   -

# vxprint
Disk group: appdg

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
dg appdg        appdg        -        -        -        -        -       -

dm appdisk0     c1d0s2       -        2023152  -        -        -       -
dm appdisk1     c1d1s2       -        2023152  -        -        -       -

# vxdg list
NAME         STATE           ID
appdg        enabled              1396545212.14.sol1

Now we deport the disk group

# vxdg deport appdg
# vxdg list

NAME         STATE           ID

# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:simple     -            -            online
c1d1s2       auto:simple     -            -            online
# vxdisk -o alldgs list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:simple     -            (appdg)      online
c1d1s2       auto:simple     -            (appdg)      online

Now we import the disk group

# vxdg import appdg
# vxdg list
NAME         STATE           ID
appdg        enabled              1396545212.14.sol1
# vxdisk list
DEVICE       TYPE            DISK         GROUP        STATUS
c0d0s2       auto:ZFS        -            -            ZFS
c1d0s2       auto:simple     appdisk0     appdg        online
c1d1s2       auto:simple     appdisk1     appdg        online

# /etc/vx/bin/vxconfigbackup
VxVM vxconfigbackup NOTICE V-5-2-6133 Start backing up diskgroup appdg to /etc/vx/cbr/bk/appdg.1396545212.14.sol1 ...

VxVM  NOTICE V-5-2-3100 Backup complete for diskgroup: appdg

# ls -ltr /etc/vx/cbr/bk
total 3
drwxr-xr-x   2 root     root           6 Apr  3 14:09 appdg.1396545212.14.sol1

Create a mirrored volume

# vxassist -g appdg make lvol1 50m layout=mirror
# vxprint -hvt
Disk group: appdg

V  NAME         RVG/VSET/CO  KSTATE   STATE    LENGTH   READPOL   PREFPLEX UTYPE
PL NAME         VOLUME       KSTATE   STATE    LENGTH   LAYOUT    NCOL/WID MODE
SD NAME         PLEX         DISK     DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
SV NAME         PLEX         VOLNAME  NVOLLAYR LENGTH   [COL/]OFF AM/NM    MODE
SC NAME         PLEX         CACHE    DISKOFFS LENGTH   [COL/]OFF DEVICE   MODE
DC NAME         PARENTVOL    LOGVOL
SP NAME         SNAPVOL      DCO
EX NAME         ASSOC        VC                       PERMS    MODE     STATE

v  lvol1        -            ENABLED  ACTIVE   102400   SELECT    -        fsgen
pl lvol1-01     lvol1        ENABLED  ACTIVE   102400   CONCAT    -        RW
sd appdisk0-01  lvol1-01     appdisk0 0        102400   0         c1d0     ENA
pl lvol1-02     lvol1        ENABLED  ACTIVE   102400   CONCAT    -        RW
sd appdisk1-01  lvol1-02     appdisk1 0        102400   0         c1d1     ENA

# ls -la /dev/vx/rdsk/appdg/lvol1
crw-------   1 root     root     273, 21000 Apr  3 14:17 /dev/vx/rdsk/appdg/lvol1

# mkfs -F vxfs /dev/vx/rdsk/appdg/lvol1
    version 9 layout
    102400 sectors, 51200 blocks of size 1024, log size 1024 blocks
    rcq size 1024 blocks
    largefiles supported

# mkdir /ap1
# vi /etc/vfstab
add the following line
/dev/vx/dsk/appdg/lvol1 -       /ap1            vxfs    -       yes     -

# mount /ap1
# df -h /ap1
Filesystem             size   used  avail capacity  Mounted on
/dev/vx/dsk/appdg/lvol1
                        50M   3.1M    44M     7%    /ap1

Volume resize
Add 10M by vxresize

# vxassist -g appdg maxsize layout=mirror
Maximum volume size: 1918976 (937Mb)
# vxassist -g appdg maxsize
Maximum volume size: 3840000 (1875Mb)
# /etc/vx/bin/vxresize -g appdg lvol1 +10M
# df -h /ap1
Filesystem             size   used  avail capacity  Mounted on
/dev/vx/dsk/appdg/lvol1
                        60M   3.1M    53M     6%    /ap1

Add another 10M by vxassist and fsadm

# vxassist -g appdg growby lvol1 10M
# /usr/lib/fs/vxfs/fsadm -b 70M /ap1
UX:vxfs fsadm: INFO: V-3-25942: /dev/vx/rdsk/appdg/lvol1 size increased from 122880 sectors to 143360 sectors
# df -h /ap1
Filesystem             size   used  avail capacity  Mounted on
/dev/vx/dsk/appdg/lvol1
                        70M   3.1M    63M     5%    /ap1