op - Open Ports on a System

This small shell script shows all the open ports on a system
as well as some information about the port.

##############################################################################
##############################################################################


#!/usr/bin/sh
#
# This utility is used to list all of the open ports on a Solaris UNIX
# based machine. It relies heavily on tools that are used to read through
# the /proc directory so it needs to be run as root or as a root equivalent.
#
# The pathname for all executables should reside in root's path statement
# for ldd to work correctly with this script
#
# Originally posted at: http://www.ilkda.com/op.htm
# Submitter: Alan Pae
#
# nmap is a great tool that will show you what is listening on each port
# of a given machine.
#
# nmap tries to give you some information about each port that it finds.
# It does not assume that any service is listening on any port number and
# it will tell you what is listening on the port if it is told to do so
# and it is able to do so.
#
# However, I felt that the information that was given to me via nmap still
# left a lot of research to do on each port so I threw a script together
# to tell you what process is listening on each port and to give you some
# more information about the process so you can tell at a glance what is
# happening on the system that you are responsible for.
#
# Enjoy the script.
#
#
# Sample output:
#
# -----------------------------------------------------
# Process ID #: 154
#
# Ports used:
# sockname: AF_INET 0.0.0.0 port: 68
# sockname: AF_INET6 :: port: 546
# sockname: AF_INET 127.0.0.1 port: 4999
# sockname: AF_INET 127.0.0.1 port: 4999
# sockname: AF_INET 10.0.0.64 port: 68
#
# COMMAND
# /sbin/dhcpagent
#
# Command Line #2: /sbin/dhcpagent
#
# Environment Variables: 154: /sbin/dhcpagent
# envp[0]: LANG=C
# envp[1]: LD_LIBRARY_PATH=/lib
# envp[2]: PATH=/usr/sbin:/usr/bin
# envp[3]: SMF_FMRI=svc:/network/physical:default
# envp[4]: SMF_METHOD=start
# envp[5]: SMF_RESTARTER=svc:/system/svc/restarter:default
# envp[6]: SMF_ZONENAME=global
# envp[7]: SUNW_NO_MPATHD=
# envp[8]: TZ=US/Pacific
# envp[9]: _INIT_NET_STRATEGY=none
#
# Libraries used: /sbin/dhcpagent
# libxnet.so.1 => /lib/libxnet.so.1
# libnvpair.so.1 => /lib/libnvpair.so.1
# libdhcpagent.so.1 => /lib/libdhcpagent.so.1
# libdhcputil.so.1 => /lib/libdhcputil.so.1
# libinetutil.so.1 => /lib/libinetutil.so.1
# libdevinfo.so.1 => /lib/libdevinfo.so.1
# libdlpi.so.1 => /lib/libdlpi.so.1
# libc.so.1 => /lib/libc.so.1
# libnsl.so.1 => /lib/libnsl.so.1
# libsocket.so.1 => /lib/libsocket.so.1
# libuuid.so.1 => /lib/libuuid.so.1
# libgen.so.1 => /lib/libgen.so.1
# libsec.so.1 => /lib/libsec.so.1
# libdladm.so.1 => /lib/libdladm.so.1
# libmp.so.2 => /lib/libmp.so.2
# libmd.so.1 => /lib/libmd.so.1
# libscf.so.1 => /lib/libscf.so.1
# libavl.so.1 => /lib/libavl.so.1
# librcm.so.1 => /lib/librcm.so.1
# libkstat.so.1 => /lib/libkstat.so.1
# libuutil.so.1 => /lib/libuutil.so.1
# libm.so.2 => /lib/libm.so.2
#
# Maximum number of file descriptors = unlimited file descriptors
#
# Effective Real Effective Real
# User User Group Group
#
# root root root root
#
# Current Working Directory: /
#
# elfsign: verification of /sbin/dhcpagent passed.
#
# -----------------------------------------------------
#
#
for i in `ls /proc`
do
openport=`pfiles $i 2> /dev/null |grep "port:"`
if [ ! -z "$openport" ]; then
echo "Process ID #: $i"
echo ""
echo "Ports used: \n $openport"
echo ""
commandline=`/usr/ucb/ps awwx $i | awk '{print $5,$6,$7,$8,$9,$10,$11,$12,$13,$14,$15,$16,$17,$18,$19,$20,$21,$22,$23,$24,$25}'`
echo "$commandline"
echo ""
commandline2=`pargs -l $i`
echo "Command Line #2: $commandline2"
echo ""
eco=`pargs -e $i`
echo "Environment Variables: $eco"
echo ""
deps=`pldd $i`
echo "Libraries used: $deps"
echo ""
filedescriptors=`pfiles $i | grep rlimit | awk '{print $3,$4,$5}'`
echo "Maximum number of file descriptors = $filedescriptors"
echo ""
eu=`ps -o user -p $i`
ru=`ps -o ruser -p $i`
eg=`ps -o group -p $i`
rg=`ps -o rgroup -p $i`
effectiveuser=`echo $eu | awk '{print $2}'`
realuser=`echo $ru | awk '{print $2}'`
effectivegroup=`echo $eg | awk '{print $2}'`
realgroup=`echo $rg | awk '{print $2}'`
echo "Effective Real Effective Real"
echo "User User Group Group"
echo ""
echo "$effectiveuser \t\t $realuser \t $effectivegroup \t\t $realgroup"
echo ""
current=`pwdx $i | awk '{print $2}'`
echo "Current Working Directory: $current"
echo ""
elves=`pldd $i | awk '{print $2}'`
elfsign verify -e $elves
echo ""
echo "-----------------------------------------------------"
fi
done




##############################################################################
### This script is submitted to BigAdmin by a user of the BigAdmin community.
### Sun Microsystems, Inc. is not responsible for the
### contents or the code enclosed.
###
###
### Copyright Sun Microsystems, Inc. ALL RIGHTS RESERVED
### Use of this software is authorized pursuant to the
### terms of the license found at
### http://www.sun.com/bigadmin/common/berkeley_license.jsp
##############################################################################

runqueue.d

The minimal interval for which sar is able to collect statistics
is one second. If a system has many processes that take a couple
of milliseconds to run, sar will not know that they are in the
run queue.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

#!/usr/sbin/dtrace -s

#
# Used for automating checks of CPU, memory, I/O, and network TCP performance.
#
# This script is described and explained in the BigAdmin Tech Tip:
# Automating a System Performance Check Using the checkperf Utility
# http://www.sun.com/bigadmin/content/submitted/perf_check.jsp
#

#pragma D option quiet

profile-1000hz
/curthread->t_cpu->cpu_disp->disp_nrunnable/
{
@runq = sum(curthread->t_cpu->cpu_disp->disp_nrunnable);
}

profile:::tick-30sec
{
normalize(@runq, 3000);
printa("%@8d", @runq);
exit(0);
}


##############################################################################
### This script is submitted to BigAdmin by a user of the BigAdmin community.
### Sun Microsystems, Inc. is not responsible for the
### contents or the code enclosed.
###
###
### Copyright Sun Microsystems, Inc. ALL RIGHTS RESERVED
### Use of this software is authorized pursuant to the
### terms of the license found at
### http://www.sun.com/bigadmin/common/berkeley_license.jsp
##############################################################################

grep

#!/bin/sh -x
# name: checkmessages_net
#
#

MAIL_RECEIVER=jbatu@p1mh01.amkor.com
today=`date|cut -c10-15`
PATH=/usr/bin; export PATH
Host=`hostname`
# Check host01.
# Check today's message above the level of warning.
GREP="grep "\($today\)" /var/adm/messages | egrep "emerg|alert|crit|err|warning" | grep -v "forceload of misc/md\" | grep -v "No proxy found""

# The messages to be ignored
FILTER="| grep -v \"forceload of misc/md\""
FILTER="$FILTER | grep -v \"No proxy found\""

GREP="$GREP$FILTER"
if eval "$GREP" > /tmp/seriousmessages.txt
then
mailx -s "$Host Serious Message" $MAIL_RECEIVER < /tmp/seriousmessages.txt
fi

disk mirror

#!/bin/sh

BOOT_DISK=c1t0d0
MIRROR_DISK=c1t1d0
METAINIT=/usr/sbin/metainit
METAROOT=/usr/sbin/metaroot

# Slice 0 (root slice)
$METAINIT -f d10 1 1 ${BOOT_DISK}s0
$METAINIT -f d20 1 1 ${MIRROR_DISK}s0
$METAINIT d30 -m d10
$METAROOT d30

# Slice 1
$METAINIT -f d11 1 1 ${BOOT_DISK}s1
$METAINIT -f d21 1 1 ${MIRROR_DISK}s1
$METAINIT d31 -m d11

# Slice 2 will not be mirrored (represents entire disk)

# Slice 3 is initially commented out; slice containing DiskSuite
# database replicas in our environment
#$METAINIT -f d13 1 1 ${BOOT_DISK}s3
#$METAINIT -f d23 1 1 ${MIRROR_DISK}s3
#$METAINIT d33 -m d13

# Slice 4
$METAINIT -f d14 1 1 ${BOOT_DISK}s4
$METAINIT -f d24 1 1 ${MIRROR_DISK}s4
$METAINIT d34 -m d14

# Slice 5
$METAINIT -f d15 1 1 ${BOOT_DISK}s5
$METAINIT -f d25 1 1 ${MIRROR_DISK}s5
$METAINIT d35 -m d15

# Slice 6
$METAINIT -f d16 1 1 ${BOOT_DISK}s6
$METAINIT -f d26 1 1 ${MIRROR_DISK}s6
$METAINIT d36 -m d16

# Slice 7
#$METAINIT -f d17 1 1 ${BOOT_DISK}s7
#$METAINIT -f d27 1 1 ${MIRROR_DISK}s7
#$METAINIT d37 -m d17

# Make the mirror disk bootable
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/${MIRROR_DISK}s0

create ISO on solaris

./iso.sh -l sol10_1106 -o /export/home/iso/sol10_1106.iso


#!/bin/sh
#
# =head1 NAME
#
# mkiso - construct an ISO9660 CD image for burning a data CD
#
# =head1 SYNOPSIS
#
# mkiso [-l label] [-o image.iso] directory
#
# =head1 DESCRIPTION
#
# I embodies my usual incantation
# for constructing an ISO9660 image for a CDROM.
# It is partner to mkcd(1cs), a program to burn data CDs.
# I makes plain vanilla data CDs, not bootable or audio CDs.
#
# =head1 OPTIONS
#
# =over 4
#
# =item B<-l> I
#
# The default Volume identifier for the image
# is normally taken from the file B in the top of the I.
# (This is because I like my data sets self describing,
# an having such a file is the simplest method not needing any metadata).
# Alternatively you may supply the Volume Identifier
# on the command line with this option.
#
# =item B<-o> B.iso>
#
# Specify the location of the resulting ISO9660 image.
# By default this is a file in the current directory
# called B.iso>, where I is the basename
# of the I named on the command line.
#
# =back
#
# =head1 FILES
#
# The B (publisher) and B (preparer) values
# come from the B<$HOME/.mkisofsrc> file.
# See mkisofs(1) for more information.
#
# =head1 SEE ALSO
#
# mkcd(1cs), mkisofs(1), cdrecord(1)
#
# =head1 CREDITS
#
# I is really just a wrapper for the mkisofs(1) command
# by Joerg Schilling.
#
# =head1 AUTHOR
#
# Cameron Simpson 12jul2000
#

cmd=`basename "$0"`
usage="Usage: $cmd [-l label] [-o image.iso] directory
-l label Label string (VOLI field, up to 32 bytes).
Default: the contents of the top level
LABEL file, or the directory
basename plus ISO date.
-o image.iso Specify output file.
Default: directory.iso"

out=
volid=
label=
iso=
badopts=
while :
do case $1 in
-l) label=$2; shift ;;
-o) out=$2; shift ;;
--) shift; break ;;
-?*) echo "$cmd: unrecognised option: $1" >&2
badopts=1
;;
*) break ;;
esac
shift
done

if [ $# = 0 ]
then
echo "$cmd: missing directory" >&2
badopts=1
else
dir=$1; shift
[ $# = 0 ] || { echo "$cmd: extra arguments: $*" >&2
badopts=1
}
fi

[ $badopts ] && { echo "$usage" >&2; exit 2; }

ok=1

if [ ! -d "$dir/." ]
then
echo "$cmd: not a directory: $dir" >&2
ok=
fi

if [ -z "$out" ]
then
out=`basename "$dir"`.iso
echo "iso=$out"
fi

if [ -z "$label" ]
then
lfile=$dir/LABEL
if [ ! -s "$lfile" ]
then
label=`basename "$dir"`" - "`date '+%Y-%m-%d'`
echo "$cmd: no label file: $lfile" >&2
echo " using \"$label\""
else
label=`cat <"$lfile"`
if [ $? != 0 ]
then
echo "$cmd: problems reading label file $lfile" >&2
ok=
else
if [ -z "$label" ]
then
echo "$cmd: empty label from $lfile" >&2
ok=
else
echo "VOLI=$label"
fi
fi
fi
fi

if [ -s "$iso" ]
then
echo "$cmd: existing file: $iso" >&2
ok=
fi

[ $ok ] || exit 1

set -x
exec mkisofs -D -J -allow-leading-dots -N -r -T -v -V "$label" -o "$out" "$dir"
## old mkisofs ## exec mkisofs -D -J -L -N -r -T -v -V "$label" -o "$out" "$dir"

Symantec Storage Foundation

Symantec Storage Foundation

# /opt/VRTS/bin/vxsvcctrl status -> view VEA service status
# /opt/VRTS/bin/vxsvcctrl stop -> stop VEA service
# /opt/VRTS/bin/vxsvcctrl start -> start VEA service

# vxdg list
# vxdg list diskgroup
# vxdg free
# vxdiskadd c1t0d0
# vxdg init diskgroup [cds=on|off] diskname=devicename
# vxdg init mktdg mktdg01=c1t0d0s2

# vxdiskadd c1t1d0 -> Adding a disk to a disk group

Removing a disk from a disk group
# vxdg [-g diskgroup] rmdisk diskname
# vxdg -g mydg rmdisk mydg02

Once the disk has been removed from its disk group, you can (optionally)
remove it from VxVM control completely, as follows:
# vxdiskunsetup devicename
For example, to remove c1t0d0s2 from VxVM control, use these commands:
# vxdiskunsetup c1t0d0s2

Deporting a disk group
-> Deporting a disk group disables access to a disk group that is currently enabled (imported) by the system.
Deport a disk group if you intend to move the disks in a disk group to another system. Also, deport a disk
group if you want to use all of the disks remaining in a disk group for a new purpose

# vxvol -g diskgroup stopall
# vxdg deport diskgroup
# vxdisk -s list
-> Select menu item 8 (Enable access to (import) a disk group) from the vxdiskadm main menu.
# vxdg import diskgroup

# vxdisk listtag

Renaming a disk group
# vxdg [-t] -n newdg import diskgroup
# vxdg -t -n mytempdg import mydg

To rename a disk group during deport, use the following command:
# vxdg [-h hostname] -n newdg deport diskgroup
# vxdg -h jingo -n myexdg deport mydg


Moving disks between disk groups
# vxdg -g salesdg rmdisk salesdg04
# vxdg -g mktdg adddisk mktdg02=c0t3d0

Handling errors when importing disks
To clear locks on a specific set of devices, use the following command:
# vxdisk clearimport devicename ...
To clear the locks during import, use the following command:
# vxdg -C import diskgroup


If some of the disks in the disk group have failed, you can force the disk group to be
imported by specifying the -f option to the vxdgimport command:
# vxdg -f import diskgroup

set manual dns thru command line

netsh interface ip set dns "Local Area Connection" static 58.71.2.8

Installing or Upgrading the iSCSI Software Initiator

Use this procedure to install or upgrade the Microsoft iSCSI Software Initiator.

Steps

1. Stop the SnapDrive for Windows service.
2. If you are running SnapManager for Microsoft Exchange, stop any application-specific services that have iSCSI dependencies (for example, Microsoft Exchange System Attendant).
   Note: You can also remove iSCSI dependencies using SnapManager for Microsoft Exchange Configuration Wizard; however, this option is not recommended and should only be used if you are unable to stop the application-specific services.
3. Perform the following steps to install the new iSCSI Software Initiator components.

   If you are installing or upgrading a cluster, first close MMC, then install the new iSCSI Software Initiator components on each node, starting with the nodes that do not own the cluster resources and rotating which system is the owner until all nodes in the cluster have the new iSCSI initiator installed.

   1. Download the Microsoft iSCSI Software Initiator from the Microsoft site.
   2. Run the install package executable and proceed through the Installation wizard.
   3. If you are going to use the iSCSI Initiator to create and manage LUNs, make sure that the Initiator Service and Software Initiator check boxes are selected on the Installation Options screen.
      Note: The Virtual Port Driver option is unavailable because it is automatically installed during the Microsoft iSCSI Initiator installation and upgrade.
   4. If you want to use MPIO, check the Microsoft MPIO Multipathing Support for iSCSI check box on the Installation Options screen.
   5. Follow the prompts to complete the installation.

   For more information about installing and configuring the Microsoft iSCSI Initiator, see the iSCSI Microsoft Windows Initiator Support Kit Setup Guide document on the NOW site.

4. Restart the SnapDrive service on the stand-alone host or on each node in the cluster

Establishing an iSCSI session to a target

Before creating a LUN, you need to have an iSCSI session to the target on which you will manage the LUN.

Before You Begin

Verify that the iSCSI service is started.

Steps

1. Perform the following actions to launch the Create iSCSI Session wizard:
   1. In the left MMC pane, select the instance of SnapDrive you want to manage.
   2. Select iSCSI Management.
   3. From the menu choices at the top of MMC, navigate to , Action > Establish Session.
2. In the ISCSI Session wizard, click Next.

   The Provide Storage System Identification panel is displayed.

3. In the Provide Storage System Identification panel, enter the storage system name or IP address of the storage system management port you want to establish the iSCSI session with, and then click Next.
   Note: The IP address you enter is the storage system’s management port IP address, not the target portal IP address to which SnapDrive will establish an iSCSI session. You will select the IP address for establishing an iSCSI session in Step 5.

   The Provide iSCSI HBA panel is displayed.

4. In the upper pane of the Provide iSCSI HBA panel, click the radio button next to an available iSCSI HBA to specifiy the initiator portal you want to use.
5. In the lower pane of the Provide iSCSI HBA panel, perform the following actions:
   1. Select the target portal to which SnapDrive will establish the iSCSI session by clicking the radio button next to the IP address of the target portal you want to use.
   2. If your target requires authentication, select Use CHAP, and then type the user name and password that iSCSI will use to authenticate the initiator to the target. For more information about CHAP, see “Understanding CHAP authentication”.
   3. Click Next.

   The Completing the iSCSI Session Wizard panel is displayed.

6. In the Completing the iSCSI Session Wizard, perform the following actions:
   1. Review the information to make sure it is accurate.
   2. If the information is not accurate, use Back to go back to previous panels of the wizard to modify information.
   3. Click Finish.

Creating a shared LUN

You can use SnapDrive to create FCP- or iSCSI-accessed LUNs that are shared between clustered Windows servers.

Before You Begin

• Verify that the FCP or iSCSI services have been started on the storage system.

Considerations

Keep the following consideration in mind when creating a LUN:

• LUNs should be created using SnapDrive.

Steps

1. Perform the following actions to launch the Create Disk wizard:
   1. Select the SnapDrive instance for which you want to create a disk.
   2. Select Disks.
   3. From the menu choices at the top of MMC, navigate to Action > Create Disk .

   The Create Disk Wizard is launched.

2. In the Create Disk Wizard, click Next.

   The Provide Storage System Name, LUN Path and Name panel is displayed.

3. In the Provide a Storage System Name, LUN Path and Name panel, perform the following actions:
   1. In the “Storage System Name” field, type the storage system name where the LUN will be created or select an existing storage system using the pull-down menu.
   2. In the “LUN Path” field, type the LUN path or select the path on the storage system you added in Step a.
   3. In the "LUN Name" field, enter a name for the LUN and click Next.

   The Select a LUN Type panel is displayed.

4. In the Select a LUN Type panel, select Shared, and then click Next.
5. In the “Information About the Microsoft Cluster Services System” panel, verify that you want the disk to be shared by the nodes listed, and then click Next.

   The Select LUN Properties panel is displayed.

6. In the Select LUN Properties panel, either select a drive letter from the list of available drive letters or enter a volume mount point for the LUN you are creating. When you create a volume mount point, enter the drive path that the mounted drive will use: for example, G:\mount_drive1\.
   Note: The root of the volume mount point must be owned by the node on which you are creating the new disk.
   Note: You can create cascading volume mount points (one mount point mounted on another mount point); however, in the case of a cascading mount point created on an MSCS shared disk, you might receive a system event warning indicating that disk dependencies might not be correctly set. This is not the case, however, as SnapDrive will create the dependencies and the mounted disks will function as expected.
7. While still in the Select LUN Properties panel, complete the following actions:
   1. Click Limit or Do not limit for the option labeled “Do you want to limit the maximum disk size to accommodate at least one snapshot?”

      If you select Limit, the disk size limits displayed are accurate only when they first appear on the Select LUN Properties panel. When this option is selected, the following actions might interfere with the creation of at least one Snapshot copy:

      • The option is changed to Do not limit and SnapDrive is used to create an additional LUN in the same storage system volume.
      • A LUN is created in the same storage system volume without using SnapDrive
      • Data objects other than LUNs are stored on this storage system volume.
   2. Select a LUN size. The size must fall within the minimum and maximum values displayed in the panel.
   3. Click Next.

   If the settings on the storage system volume or qtree on which you are creating the LUN do not allow SnapDrive to proceed with the create operation, the Important Properties of the Storage System Volume panel is displayed, as described in Step 8. Otherwise, Step 8 is skipped.

8. The Important Properties of the Storage System Volume panel displays the settings that will be used for the volume or qtree you specified in Step 4 of this procedure.

   SnapDrive requires the storage system volume containing LUNs to have the following properties:

   • create_ucode = on
   • convert_ucode = on
   • snapshot_schedule = off
   Note: SnapDrive cannot proceed to create a LUN unless these settings are configured as shown. Therefore, you must accept these settings.
9. Click Next.
10. In the Select Initiators panel, perform the following actions:
    1. Double-click the cluster group name to display the hosts that belong to the cluster.
    2. Click the name of a host to select it.

    The available initiators for that host are displayed in the Initiator List in the lower half of the pane.

11. In the Initiator List pane, select an initiator for the LUN you are creating.

    If you select an iSCSI initiator, and an iSCSI connection to the storage system on which you are creating the LUN does not exist, SnapDrive launches the Create iSCSI Session wizard, and you are prompted to select a target portal and initiator. Also, if your target requires authentication of hosts that connect to it, you can type that information here. After you click OK, the iSCSI connection from the Windows host to the storage system is established, even if you do not complete the Create Disk wizard.

    If you have MPIO installed and you are using FCP, you have the option to select several FCP initiators.

12. Repeat Step 10 and Step 11 for all hosts, and then click Next.
    Note: The Next button remains unavailable until initiators for all hosts of a cluster have been selected.

    The Select Initiator Group management panel is displayed.

13. In the Select Initiator Group management panel, specify whether you will use automatic or manual igroup management. If you select automatic igroup management, SnapDrive uses existing igroups or, when necessary, creates new igroups for the initiators you specified in Step 10 through Step 12. If you select manual igroup management, you manually choose existing igroups or create new ones as needed.

    If you specify...	Then...
    Automatic igroup management	Click Next. You are done with igroup management.
    Manual igroup management	Click Next, and then perform the following actions: In the Select igroups panel, select from the list the igroups to which you want the new LUN to belong. Repeat this action for each node in the cluster. Note: A LUN can be mapped to an initiator only once. OR Click Manage igroups and for each new igroup you want to create, type a name in the igroup Name text box, select initiators, click Create, and then click Finish to return to the Select igroups panel. Click Next. Note: The Next button will remain unavailable until the collection of selected igroups contains all the initiators you selected in Step 11.

14. In the Specify Microsoft Cluster Services Group panel, perform the following actions.
    1. From the Group drop-down list, select one of the cluster groups owned by this node to which the newly created LUN will belong.

       OR

       Select Create a New Cluster Group to create a new cluster group and then put the newly created LUN in that group.

       Note: When selecting a cluster group for your LUNs, choose the cluster group your application will use. If you are creating a volume mount point, the cluster group is already selected. This is because the cluster group owns your root volume physical disk cluster resources. It is recommended that you create new shared LUNs outside of the cluster group.
    2. Click Next.

    The Completing the Create Disk Wizard panel is displayed.

15. In the Completing the Create Disk Wizard panel, perform the following actions:
    1. Verify all the settings.

       If you need to change any settings, click Back to go back to the previous wizard panels.

    2. Click Finish.

       Disk creation might take several seconds to complete. SnapDrive displays disk creation status in the lower panel of the center MMC pane.

Creating a storage system volume

You can create a volume on the storage system using the SnapDrive Storage System Management snap-in or FilerView on the storage system.

Considerations

These steps describe how to create a volume using the SnapDrive Storage System Management snap-in.

Steps

1. In the left MMC pane, navigate to SnapDrive > Storage System Management.
2. Click on the storage system where you want to create a volume.
3. Provide login credentials to the storage system when prompted.

   A storage system FilerView session will be displayed in the main MMC pane.

4. Navigate to Volumes > Add.
5. Follow the instructions in the FilerView wizard to add either a traditional or flexible volume.