Powerpath Host Agent Software Utility

powercf

During installation on Solaris hosts, the powercf utility configures PowerPath devices by scanning the host adapter buses for both single-ported and multiported Symmetrix volumes. (A multiported volume shows up on two or more host bus adapters with the same Symmetrix subsystem/device identity. The identity comes from the serial number for the volume.) For each Symmetrix volume found in the scan of the host adapter buses, powercf creates a corresponding emcpower device entry in the emcp.conf file, and saves a primary path and an alternate primary path to that device. The powermt config command, run at boot time by init (1M), adds additional paths to the Symmetrix volume.

After PowerPath is installed, you only need to run the powercf command when the physical configuration of the Symmetrix or the host changes. The configuration changes that require you to reconfigure PowerPath devices include:
• Adding or removing host bus adapters
• Adding, removing, or changing Symmetrix logical devices
• Changing the cabling routes between host bus adapters and Symmetrix ports
• Adding or removing Symmetrix channel directors

powercf -i|p|q

Arguments

-i
Scans the host adapter buses for single-ported and multiported Symmetrix volumes. Compares those volumes with the PowerPath device entries in the emcp.conf file. Prompts you to accept or reject any addition or deletion of Symmetrix devices in the emcp.conf file.

-p
Scans the host adapter buses for single-ported and multiported Symmetrix volumes. Compares those devices with the emcpower entries in the emcp.conf file. Prints information on any inconsistencies.

-q
Scans the host adapter buses for single-ported and multiported Symmetrix volumes. Compares those volumes with the PowerPath device entries in the emcp.conf file. Updates the emcp.conf file by removing PowerPath devices that were not found in the host adapter scan and by adding new PowerPath devices that were found. Saves a primary and an alternate primary path to each PowerPath device.

The powermt Commands

This section describes each powermt command. Refer to the preface of this document for information on the conventions used in the command syntax. You can run powermt commands from either the command line.

Powermt

Displays the syntax for the commands in the powermt management utility.

Syntax
powermt
powermt check
Verifies that all paths are connected to the correct Symmetrix volumes.

Syntax
powermt check [dev=power#|all] [adapter=adapter#|all]

The dev parameter and the adapter parameter are optional. You must, however, specify at least one in the powermt check command.

powermt check_registration

Provides PowerPath license registration information. The powermt check_registration command is available from the command line only. It does not have an equivalent SMIT command.

Syntax
powermt check_registration

powermt config
Configures paths to all known Symmetrix logical devices for maximum accessibility.

Syntax
powermt config

powermt display
Displays a table that shows the state of all host adapters found by PowerPath.

Syntax
powermt display

powermt display dev
Displays a table that shows the state of the specified PowerPath device or all PowerPath devices.

Syntax
powermt display dev=power#|all

powermt restore
Attempts to reopen, or restore to service, all device paths currently marked as Closed.

Syntax
powermt restore

powermt save
Saves changes to the PowerPath devices’ policy and priority attributes to the ODM so that the new values are in effect at system startup.

Syntax
powermt save

powermt set adapter_switch
Enables or disables the specified host adapter.

Syntax
powermt set adapter_switch=disabled|enabled adapter=adapter#

Parameters

disabled
Does not allow the specified host adapter to accept I/O traffic for any device path it serves.

enabled
Allows the specified host adapter to accept I/O traffic for any device path it serves.

adapter#
The host adapter number shown in the ## column in the table displayed when you enter the powermt display dev command.
powermt set mode
Sets device path(s) to either active or standby mode for the specified PowerPath device or for all PowerPath devices on the specified adapter.
Syntax
powermt set mode=active|standby adapter=adapter# [dev=power#|all]
The dev parameter is optional. If you do not include the dev parameter, the powermt set mode command changes the mode of all PowerPath devices on the specified adapter.
powermt set policy
Sets the load balancing policy for the specified PowerPath device or all PowerPath devices.
Syntax
powermt set policy=rr|io|lb|so [dev=power#|all]
The dev parameter is optional. If you do not include the dev parameter, the powermt set policy command changes the policy of all PowerPath devices.
Parameters

Rr Round-robin. Future I/O requests are assigned to each of the available paths in rotation.
Io I/O. Load balance is based on the number of pending I/Os.
Lb Least blocks. Load balance is based on the number of blocks in the pending I/Os.
powermt set priority
Sets the I/O priority for the specified PowerPath device or for all PowerPath devices.
Syntax
powermt set priority= [dev=power#|all]
The dev parameter is optional. If you do not include the dev parameter, the powermt set priority command changes the priority of all PowerPath devices.
The powermt set priority command is only meaningful when the load-balancing policy is Symmetrix optimized (so). This setting allows the I/O performance of a few, individual PowerPath devices to be improved at the expense of the rest of the devices, while otherwise maintaining the best possible load balance across all paths.
powermt validate
Verifies that the primary path opened for each PowerPath device is connected to the correct Symmetrix volume.
Syntax
powermt validate
powermt watch
Displays a table that shows the state of the host adapters for the specified PowerPath device or all PowerPath devices.
Syntax
powermt watch every=#seconds
powermt watch dev
Displays a table that shows the state of the specified PowerPath device or all PowerPath devices.
Syntax
powermt watch dev=power#|all every=#seconds

How to change IP V4 of the Brocade Switch ( or any server ) to your LAN IP v4:(If it have another LAN IP)

Step1:

      Take the Current ip of the Brocade

      Switch

    Ex: 192.168.5.1

Step2: 
       Find the local Ip series you want to

       give to your machine.
   
    Ex: 192.168.0.1

Step3:
    Take one system and prepare it with ip in the same series of your brocade switch (or server).

 Ex: with ip 192.168.5.2

step4:

      Telnet from your server(192.168.5.2) to the brocade switch (or server(192.168.5.1)).

Ex:
In Brocade Switch
     #ifconfig -a

       ip is 192.168.5.2

     #telnet 192.168.5.1

     switch>ipaddrshow

      ip is 192.168.5.1

     switch>ipaddrset
     one interactive session is opened to take the new ip of the switch , subnetmask and default gateway.then give your ip as 192.168.0.1

     switch>ipaddrshow

      ip is 192.168.0.1

     logout the switch.now switch in the same local network lan.


In solaris server

   ##telnet 192.168.5.1

  telnet into the server as like the telnet in the switch.after

    solaris##ifconfig -a

     It gives the ip of the current solaris server with the interface.
  
syntax: solaris##ifconfig interfacename ipaddress plumb

    Solaris##ifconfig eri0 192.168.0.1 plumb

After plumbing up the interface with the new ip address.

    solaris##ifconfig eri0 192.168.0.1 up

    solaris##ifconfig -a

     ip address is 192.168.0.1

    Task is completed, then logout the server.


step5:


  Also change the your console loggedin server ip to your local LAN series IP.
   

CLARIION Features

Data intigrity

-How Clariion keeps data safe ..?

•   Mirrored write cache , Vault ..etc.

Data Availability

-How Ensuring Uninterrupted host access to data..?

• Hardware redundency , Path failover software (Powerpath), Error reporting Capability.

Clariion Performance

-What makes a Clariion a great performer..?

• Cache , Dual SPs ,Dual/Quad Back-end FC Buses

Clariion Storage Objects

-A First look at LUNs, and access to them

• RAID Groups , LUNS, MetaLUNs, StorageGroups.

RAID groups , types

RAID GROUPS and RAID Types

     The above slide illustrates the concept of creating a RAID Group and the supported RAID types of the Clariions.

RAID Groups

   The concept of a RAID Group on a Clariion is to group together a number of disks on the Clariion into one big group. Let’s say that we need a 1 TB LUN. The disks we have a 200 GB in size. We would have to group together five (5) disks to get to the 1 TB size needed for the LUN. I know we haven’t taken into account for parity and what the RAW capacity of a drive is, but that is just a very basic idea of what we mean by a RAID Group. RAID Groups also allow you to configure the Clariion in a way so that you will know what LUNs, Applications, etc…live on what set of disks in the back of the Clariion. For instance, you wouldn’t want an Oracle Database LUN on the same RAID Group (Disks) as a SQL Database running on the same Clariion. This allows you to create a RAID Group of a # of disks for the Oracle Database, and another RAID Group of a different set of disks for the SQL Database.

RAID Types

Above are the supported RAID types of the Clariion.

RAID 0 – Striping Data with NO Data Protection.

    The Clariions Cache will write the data out to disk in blocks (chunks) that we will discuss later. For RAID 0, the Clariion writes/stripes the data across all of the disks in the RAID Group. This is fantastic for performance, but if one of the disks fail in the RAID 0 Group, then the data will be lost because there is no protection of that data (i.e. mirroring, parity).

RAID 1 – Mirroring. 

    The Clariion will write the Data out to the first disk in the RAID Group, and write the exact data to another disk in that RAID 1 Group. This is great in terms of data protection because if you were to lose the data disk, the mirror would have the exact copy of the data disk, allowing the user to access the disk.

RAID 1_0 – Mirroring and Striping Data. 

   This is the best of both worlds if set up properly. This type of RAID Group will allow the Clariion to stripe data and mirror the data onto other disks. However, the illustration above of RAID 1_0, is not the best way of configuring that type of RAID Group. The next slide will go into detail as to why this isn’t the best method of configuring RAID 1_0.

RAID 3 – Striping Data with a Dedicated Parity Drive. 

    This type of RAID Group allows the Clariion to stripe data the first X number of disks in the RAID Group, and dedicate the last disk in the RAID Group for Parity of the data stripe. In the event of a single drive failure in this RAID Group, the failed disk can be rebuilt from the remaining disks in the RAID Group.

RAID 5 – Striping Data with Distributed Parity.

   RAID type 5 allows the Clariion to distribute the Parity information to rebuild a failed disk across the disks that make up the RAID Group. As in RAID 3, in the event of a single drive failure in this RAID Group, the failed disk can be rebuilt from the remaining disks in the RAID Group.

RAID 6 – Striping Data with Double Parity. 

      This is new to Clariion world starting in Flare Code 26 of Navisphere. The simplest explanation of RAID 6 we can use for RAID 6 is the RAID Group uses striping, such as RAID 5, with double the parity. This allows a RAID 6 RAID Group to be able to have two drive failures in the RAID Group, while maintaining access to the LUNs.

HOT SPARE – A Dedicated Single Disk that Acts as a Failed Disk. 

     A Hot Spare is created as a single disk RAID Group, and is bound/created as a HOT SPARE in Navisphere. The purpose of this disk is to act as the failed disk in the event of a drive failure. Once a disk is set as a HOT SPARE, it is always a HOT SPARE, even after the failed disk is replaced. In the slide above, we list the steps of a HOT SPARE taking over in the event of a disk failure in the Clariion. 
1. A disk fails – a disk fails in a RAID Group somewhere in the back of the Clariion.

2. Hot Spare is Invoked – a Clariion dedicated HOT SPARE acts as the failed disk in Navisphere. It will assume the identity of the failed disk’s Bus_Enclosure_Disk Address.

3. Data is REBUILT Completely onto the Hot Spare from the other disks in the RAID Group – The Clariion begins to recalculate and rebuild the failed disk onto the Hot Spare from the other disks in the RAID Group, whether it be copying from the MIRRORed copy of the disk, or through parity and data calculations of a RAID 3 or RAID 5 Group.

4. Disk is replaced – Somewhere throughout the process, the failed drive is replaced.

5. Data is Copied back to new disk – The data is then copied back to the new disk that was replaced. This will take place automatically, and will not begin until the failed disk is completely rebuilt onto the Hot Spare.

6. Hot Spare is back to a Hot Spare – Once the data is written from the Hot Spare back to the failed disk, the Hot Spare goes back to being a Hot Spare waiting for another disk failure.

Hot Spares are going to be size and drive type specific.

Size. 

   The Hot Spare must be at least the same size as the largest size disk in the Clariion. A Hot Spare will replace a drive that is the same size or a smaller size drive. The Clariion does not allow multiple smaller Hot Spares replace a failed disk.

Drive Type Specific.

    If your Clariion has a mixture of Drive Types, such as Fibre and S.ATA disks, you will need Hot Spares of those particular Drive Types. A Fibre Hot Spare will not replace a failed S.ATA disk and vice versa.

Hot Spares are not assigned to any particular RAID Group. They are used by the Clariion in the event of any failure of that Drive Type. The recommendation for Hot Spares is one (1) Hot Spare for every thirty (30) disks.

   There are multiple ways to create a RAID Group. One is via the Navisphere GUI, and the other is through the Command Line Interface. In later slides we will list the commands to create a RAID Group.

Updating the HBA FCode

To update your FCode support, follow these steps:

1. Make sure you have updated the firmware (as described under

2. Copy the appropriate file for Open Boot support from the

CD-ROM or the Emulex website to the appropriate directory,

/usr/sbin/lpfc

:

3. Start the FCode update utility:

./lputil

4. Select option

3 – Firmware Maintenance.

5. Select the adapter number to update.

6. Select the appropriate option:

7. Enter the full file name of the image file.

8. Select option

0 – Return to Main Menu.

9. Repeat steps

Step 4 through Step 8 for any other adapters.

HBA model File

LP8000E-EMC

DOXXX.PRG (where XXX is the version; for example: DO140A0.PRG)

LP9002-E

LP9002C-E

LP9002DC-E

CO

XXX.PRG (where XXX is the version; for example: CO140A0.PRG)

LP9002S-E

TSCXXX.PRG (where XXX is the version; for example: TSC240A0.PRG)

LP9802-E

HOXXX.PRG (where XXX is the version; for example: HO140A0.PRG)

LP10000-E

LP10000DC-E

TO

XXX.PRG (where XXX is the version; for example: TO140A0.PRG)

HBA Bus Select:

PCI

1 – Load Firmware Image

SBus

6 – Load FCode Image

46

EMC Fibre Channel with Emulex Host Bus Adapters in the Solaris Environment

Installing and Configuring the HBA and Driver

10. Type

reboot -- -r and press ENTER to reboot the host with the -r

Note :

Make sure your storage array device path is

/pci/lpfc. If you see that

the path is

/pci/fibre_channel, you must download the Fcode again

and reboot the system with the command reboot -- -rv.

(reconfigure) option.

Updating the HBA firmware

To update your firmware:

1. Copy the appropriate firmware file from the CD-ROM or the

Emulex website to the appropriate directory,

/usr/sbin/lpfc:

2. Start the firmware update utility:

./lputil

3. Select option

3 – Firmware Maintenance.

4. Select the adapter number to update.

5. Select option

1 – Load Firmware Image.

6. Type the full file name of the image file (as shown in the table in

step 1;

cd390a7.awc, for example) and press ENTER.

7. Select option

0 – Return to Main Menu.

8. Repeat

Step 3 through Step 7 for any other adapters.

9. If you are upgrading the firmware on the system that will boot

from the EMC storage array, update the FCode as described

under

“Updating the HBA FCode”

10. If the HBA driver is version 5.x or older, the host must reboot for

the upgrade firmware to take effect.

Solaris Interview Questions

1) What files control user administration?
A) /etc/passwd file: 7 Fields: loginid:x:userid:groupid:comment:homedir:shell
/etc/shadow: 9 Fields: loginid:password:lastchng:min:max:warn:inactive:expire
/etc/group : 4 Fields : groupname:password:groupid:username list)

2) What does the "pwconv" command do?
A) It updates the /etc/shadow file with information from /etc/passwd file.

3) Where are the failed login attemps to system logged?
A) /var/adm/loginlog (We need to create this file as it does not exist by default)

4) Which command shows the users currently logged in to system?
A) who ( It reads the information from /var/adm/utmpx file)

5) Which command will show detailed information about a user?
A) finger –m

6) Which command displays all login and logouts?
A) last (It reads the information from /var/adm/wtmpx file)

7) What is the "StickyBit" file permission?
A) Sticky Bit permission protects the file within a public writable directory.
File set with sticky bit will not allow any user to delete the file except the
Owner of file, owner of the group or the root user.

8) How is ACL (Access Control Lists) implemented?
A) 8.1) "getfacl"command : To display an ACL on file.
Syntax : getfacl

8.2) setfacl command : To set the ACL on file
Syntax : setfacl

8.3) setfacl –m command : To modify ACL entries
Syntax : setfacl –m

8.4) setfacl –s command : Remove old ACL entries and replace with new one.
Syntax : setfacl –s

8.5) setfacl –d command : Delete ACL entry
Syntax : setfacl –d

9) Imp "root(/)" subdirectories and their purpose :
9.1) / : Root of overall file system.
9.2) /bin : Symbolic link to /usr/bin. Stores standard system commands and binary files.
9.3) /dev : Primary location for "logical" device names
9.4) /devices : Primary location for "physical" device names
9.5) /etc : Contains host specific system admin config files
9.6) /export : Default directory for commonly shared filesystems.
9.7) /home : Default directory / mount point for user's home directory
9.8) /kernel : Directory of platform independent loadable kernel file
9.9) /mnt : Temporary mount point for file systems
9.10) /opt : Default directory for add on packages
9.11) /sbin : Executables used in booting process and file recovery
9.12) /tmp : Temporary files
9.13) /usr : Mount point for /usr file system
9.14) /var : Directory for varying files, temporary logging or status files

10) What are the different disk slices?
Slice Name Function
0 / Root's system files
1 swap Swap area
2 Entire Disk
5 /opt Optional Software
6 /usr System Exe's
7 /export/home User's file and directories

11) Which command displays the system configuration information?
A) prtconf

12) Which command is used to configure newly attached hardware ?
A) devfsadm –c where

13) What are the different types of "file systems" in Solaris?
A) There are 3 Types of file system :
13.A.1) Disk based : ufs (standard unix), hsfs (cd-rom), pcfs (Floppy)
Or udf (DVD and CD Rom)
13.A.2) Distributed : NFS (enables sharing of files between many types of n/w)
13.A.3) Pseudo : tmpfs (temporary), swapfs , fdfs, procfs

14) What is a "boot block"?
A) The bootstrap program (bootblk) is found in the next 15 disk sectors. Only the "root" file system has an active boot block, although the space is allocated for boot block at the beginning of each file system.

15) What is "superblock"?
A) The file system is determined by its superblock. It is contained in the 16 disk sectors following the boot block. It contains :
· No. of data blocks
· No.of cylinder groups
· Size of data block fragment
· Description of hardware
· Name of mount point
· File system state flag ( clean , stable , active , logging or unknown)

16) How will you repair the main superblock if it gets corrupted?
A) Every file system has backup superblock at block no.32, which can be given to fsck to repair the main superblock.
# fsck –o b=32 /dev/rdsk/c0t0d0s0

17) How to create new file systems ?
A) newfs /dev/rdsk/c0t0d0s0

18) How will you restore /etc/vfstab file if it gets corrupted?
A) Step 1 : Insert Solaris CD 1 of 2
Step 2 : Go to single user mode : ok boot cdrom –s
Step 3 : Run "fsck" on /(root) partition : # fsck /dev/rdsk/c0t0d0s0
Step 4 : Mount /(root) file system on /a directory to gain access to file system
# mount /dev/dsk/c0t0d0s0 /a
Step 5 : Set & export TERM variable
# TERM=sun
# export TERM
Step 6 : Edit /etc/vfstab file and remove the incorrect entry : # vi /a/etc/vfstab
Step 7 : Unmount the file system : # cd / ; # umount /a and reboot the system.

19) How will you share user's home directory?
A) Step 1 : Login as root and verify mountd daemon is running
# ps –ef grep mountd
Step 2 : If the daemon is not running start it :
# /etc/init.d/nfs.server start
Step 3 : List all shared filesystems
# share
Step 4 : Edit the /etc/dfs/dfstab file and add :
# share –F nfs /export/home
Step 5 : Share the file systems in the /etc/dfs/dfstab file :
# shareall –F nfs
Step 6 : Verify that the home directory is shared.
# share

20) What does /etc/inittab file contain ?
A) The /etc/inittab contains the systems default run level, processes to start/monitor
or restart. It also contains the actions to be taken when run level changes.
/etc/inittab file is in foll format :- id:rstate:action:process

21) How will you use "shutdown" command?
A) # shutdown –i0 –g300 –y

22) How will you check the OBP version of your system ?
A) Use " banner" command at the ok prompt

23) Explain the Solaris Boot process?
A) 23.1 ) Boot Prom Phase : Runs POST to verify system hardware and memory Loads "bootblk" primary boot program.
23.2) Boot Program Phase : "bootblk" loads the finds "ufsboot" and loads it in memory.ufsboot loads the kernel.
23.3) Kernel Initialization Phase : Loads modules using "ufsboot"
Creates user processes and starts /sbin/init process.
23.4) Initialization Phase : Starts "rc" scripts. These scripts check & mounts file System, starts various processes and perform system maintanence tasks

24) Backup And Restore :
Full backup : # ufsdump 0uf /dev/rmt/0 /
Where 0 à indicates full backup f à Path of the backup device u à update the dumpdates file.
Restore : # ufsrestore if /dev/rmt/0

25) How to temporary disable user's login.
A) Log in as "root"
B) Create /etc/nologin file
# vi /etc/nologin
C) Include a message
D) Close and Save the file.

26) What does 'Probe' command do?
A) probe-scsi-all à list all internal and external scsi devices
B) probe-ide-all à List all ide devices

27) How to find whether a system is configured for 32-bit or 64-bit?
A) # isainfo -v

28) How to activate Ethernet card ?
A) # ifconfig qfe0 plumb

29) How will you assign ip address to system?
A) # ifconfig qfe0 192.168.0.1 netmask 255.255.255.0 up

30) How will you check current ip configuration?
A) # ifconfig –a

31) How will you set a default router ?
A) # /etc/defaultrouter

32) How to remove all current routes and assign 192.168.1.100 as default router?
A) # route flush
# route add default 192.168.1.100

33) How to change the network settings ?
A) # sys-unconfig

34) What all does the NVRAM store?
A) Ethernet Address / Host ID / Time of Day (TOD) clock and EEPROM Parameters

35) Where are all the port numbers stored?
A) Port numbers are stored in /etc/services

36) Where are eeprom file stored ?
A) /usr/sbin/eeprom

37) Some important NIS commands :
1) # ypcat hosts à Prints info from hosts database
2) # ypmatch host1 hosts à Match individual host entries
3) # ypmatch user1 passwd
4) # ypwhich à Returns NIS master server.

38) Controlling the tape drive ?
1) mt –f /dev/rmt/0n à 'n' indicates no rewind.

39) What are the network utilities ?
1) snoop à To capture network packets & display contents
2) netstat –i à Displays state of Ethernet address
3) ndd command à Set & examine kernel parameters namely TCP/IP drivers.

40) Network Configuration :
1) /etc/resolv.conf : Contains Internet domain name, name server and search order.
2) /etc/nsswitch.conf : Specifies information source from files, NIS, NIS+ or DNS
3) /etc/hostname.[int](hme0eri0le0] : IP v4 host
4) /etc/nodename : IP v6 host
5) /etc/inet/hosts : Host namefile (/etc/host links to this file)
6) /etc/inet/netmasks : TCP/IP subnet router
7) /etc/inet/protocols : Network protocols
8) /etc/inet/services : Network service name & port numbers
9) /etc/notrouter : Create this file to prevent in.routed or in.rdiscd from starting at boot time
10) /etc/inet/inetd.conf : Internet super daemon config file
11) To change hostname / ip address :

/etc/hostname.{int}(hme0le0)
/etc/nodename
/etc/inet/hosts
/etc/net/*/hosts
/etc/defaultrouter
/etc/resolv.conf

41) How to configure interfaces at boot time>
A) /etc/rcS.d/s30network.sh file à This script is run each time system is booted. It uses ifconfig utility to configure each interface with IP add & other network info.It searches for files called : hostname.xxn in /etc where xx à int type & nà instance of interface

Solaris Administration Part 1

1. System Concepts.

2. Installation.

3. Packages.

4. Patches.

5. Boot Process And RUN Levels.

6. System Security.

7. User Management.

8. Process Management.

9. Disk Management.

10. File System Management.

11. Backup And Recovery.

12. Solaris Volume Manager (SVM)

Different Vendor Worldwide Names WWN Details

          Twenty-four of the sixty-four bit •World Wide Name• must be unique for every vendor. A partial listing of those vendors most familiar to EMC with regard to Symmetrix Fibre Channel connectivity.

       If decoding a HBA WWN, then issue an 8f, command to view the WWN in the FA login table. Bytes 1-3 of the World Wide Names contain the unique vender codes. Note that if there is a switch connected between the FA and the host bus adapter, then the name and fabric servers of the switch will login to the FA. These WWNs can be decoded in the same way as the HBA WWNs.

        In the following example the unique vendor code is 060B00, this indicates that the HBA attached was
supplied by Hewlett Packard.


UTILITY 8F -- SCSI Adapter utility : TIME: APR/23/01 01:23:30

HARD LOOP ID : 000 (ALPA=EF) LINK STATE : ONLINE: LOOP

CHIP TYPE/REV: 00/00 Q RECS TOTAL: 3449 CREDIT: 0 RCV BUFF SZ: 2048

IF FLAGS : 01/ TAGD/NO LINK/NO SYNC/NO WIDE/NO NEGO/NO SOFT/NO ENVT/NO CYLN

IF FLAGS1: 08/NO PBAY/NO H300/NO RORD/ CMSN/NO QERR/NO DQRS/NO DULT/NO SUNP

IF FLAGS2: 00/NO SMNS/NO DFDC/NO DMNQ/NO NFNG/NO ABSY/NO SQNT/NO NRSB/NO

SVAS

IF FLAGS3: 00/NO SCI3/NO ..../NO ..../NO ..../NO ..../NO ..../NO ..../NO ....

FC FLAGS : 57/ ARRY/ VOLS/ HDAD/NO HDNP/ GTLO/NO PTOP/ WWN /NO VSA

FC FLAGS1: 00/NO VCM /NO CLS2/NO OVMS/NO ..../NO ..../NO ..../NO ..../NO ....

FC FLAGS2: 00/NO ..../NO ..../NO ..../NO ..../NO ..../NO ..../NO ..../NO ....

FC FLAGS3: 00/NO ..../NO ..../NO ..../NO ..../NO ..../NO ..../NO ..../NO ....

HOST SID PORT NAME (WWN) NODE NAME RCV BUF CREDIT CLASS

000001 50060B0000014932 50060B0000014933 992 EE 4 3

PRLI REQ: IFN RXD

DONE.

     The following are common HBA vendor codes:

Refer to the open systems host matrix if you need to know whether these HBAs are supported for specific hosts.

00-00-D1 (hex) ADAPTEC INCORPORATED

0000D1 (base 16) ADAPTEC INCORPORATED

00-30-D3 (hex) Agilent Technologies

0030D3 (base 16) Agilent Technologies

00-60-69 (hex) BROCADE COMMUNICATIONS SYSTEMS

006069 (base 16) BROCADE COMMUNICATIONS SYSTEMS

00-02-A5 (hex) Compaq Computer Corporation

0002A5 (base 16) Compaq Computer Corporation

00-60-48 (hex) EMC CORPORATION

006048 (base 16) EMC CORPORATION

00-00-C9 (hex) EMULEX CORPORATION

0000C9 (base 16) EMULEX CORPORATION

00-E0-24 (hex) GADZOOX NETWORKS

00E024 (base 16) GADZOOX NETWORKS


00-60-B0 (hex) HEWLETT-PACKARD CO.

0060B0 (base 16) HEWLETT-PACKARD CO.

00-50-76 (hex) IBM

005076 (base 16) IBM

00-E0-69 (hex) JAYCOR NETWORKS, INC.

00E069 (base 16) JAYCOR NETWORKS, INC.

08-00-88 (hex) MCDATA CORPORATION

080088 (base 16) MCDATA CORPORATION

08-00-0E (hex) NCR CORPORATION

08000E (base 16) NCR CORPORATION

00-E0-8B (hex) QLOGIC CORP.

00E08B (base 16) QLOGIC CORP.

00-00-6B (hex) SILICON GRAPHICS INC./MIPS

00006B (base 16) SILICON GRAPHICS INC./MIPS

00-10-9B (hex) VIXEL CORPORATION

00109B (base 16) VIXEL CORPORATION

 This information will help you to identify the vendor of particularar HBA's WWN.

File System Management

### Steps necessary to slice & create file systems###

Steps:

1. unmount existing file systems

-umount /data2 /data3

2. confirm fdisk partitions via 'format' utility

-format - select disk - select fdisk

3. use partition - modify to create slices on desired drives

DISK1   -slice 0 - /dev/dsk/c0t1d0s0

DISK2   -slice 0 - /dev/dsk/c0t2d0s0

4. Create file system using 'newfs /dev/rdsk/c0t0d0s0'

5. Use 'fsck /dev/rdsk/c0t1d0s0' to verify the consistency of the file system

6. Mount file systems at various mount points

  #mount /dev/dsk/c0t1d0s0 /data2

  #mount /dev/dsk/c0t2d0s0 /data3

7. create entries in Virtual File System Table (/etc/vfstab) file

###How to determine file system associated with device###

1. fstyp /dev/dsk/c0t0d0s0 - returns file system type

2. grep mount point from /etc/vfstab - returns matching line

grep /var /etc/vfstab

3. cat /etc/mnttab - displays currently mounted file system

###Temporary File System (TEMPFS) Implementation###

TempFS provides in-memory (RAM), very fast, storage and boosts application performance

Steps:

1. Determine available memory and the amount you can spare for TEMPFS

   #prtconf 

   #allocate 100MB

2. Execute mount command:

   #mkdir /tempdata

   #chmod 777 /tempdata

   #mount -F tmpfs -osize=100m swap /tempdata

Note: TEMPFS data does NOT persist/survive across reboots

Note: TEMPFS data is lost when the following occurs:

1. TEMPFS mount point is unmounted: i.e. umount /tempdata

2. System reboot

Modify /etc/vfstab to include the TEMPFS mount point for reboots

#swap - /tempdata tmpfs - yes -

###Swap File/Partition Creation###

 #swap -l | -s - to display swap information

#mkfile size location_of_file - to create swap file

  #mkfile 512m /data2/swap2

  #swap -a /data2/swap2 - activates swap file

 ##To remove swap file:

  #swap -d /data2/swap2 - removes swap space from kernel. does NOT remove file

  #rm -rf /data2/swap2

###Swap Partition Creation###

format - select disk - partition - select slice/modify

  #swap -a /dev/dsk/c0t2d0s1

Modify /etc/vfstab