IT Products Knowledge Share

LUN Migration on Sun Solaris 10 with Sun Cluster 3.3 -Replacing a Quorum device as well.

2014-02-19T11:07:00.002-08:00

/dev/did/dsk/d9s2 is a quorum device and also db runs on it. It needs to be replaced with the New LUN.
The new lun has to be added to both the nodes and we need to ensure the same.

1. Check the old lun on the system.
echo |format ; powermt display dev=all; zpool status GRID

2.Check the new lun and label it.
devfsadm -Cv ; echo |format

We can run the below commands to both the nodes.
cldevice populate - update the global device namespace.
cldevice list -v - Verify that a device ID (DID) has been assigned to the disk drive.

3. Check the status of the pool
zpool status GRID

4. Attach the new lun
zpool attach -f GRID <device> <new-device>
#zpool attach -f GRID /dev/did/dsk/d9s2 <new-device> (New Device will be a DID device)

5. Detach the old lun after the mirroing gets completed. (Important -Ensure that it has completed )
zpool detach GRID /dev/did/dsk/d9s2 (OLD LUN)

6. Add a Quorum device.
scsetup , Answer the questions... then verify the quorum device by running cluster status (We should have the new device in place as a quorum disk)

VERY Important: After ensuring that the Quorum disk is in place in cluster status output.
# luxadm remove_device -F /dev/rdsk/cNtXdYsZ
# devfsadm -C
# cldevice clear

Test the Failover by running.
clrg switch -n Nodename RG

Sun Cluster 3.3 Commands

2014-01-27T18:10:00.002-08:00

ome Sun Cluster 3.3 commands

1. Cluster

The command to use is cluster

# cluster status: the status of the cluster nodes.
# cluster show: Displays the cluster parameters.
# cluster shutdown: shuts down the cluster.
# cluster list: list of cluster nodes configured

2. Management of a resource group

The command to use is CLRG

# CLRG list: list of resource groups.
# CLRG list RG: RG group list.
# CLRG status: the status of resource groups.
# CLRG status RG: RG group status.
# CLRG remaster +: reinstate the resources groups to their preferred nodes.
# CLRG switch-n NODE RG: RG group moves to the node NODE.
# CLRG evacuate-n NODE RG: Move all resources NODE node to the other node.
# CLRG offline RG: stop all resources in the group.
# CLRG online RG: starts all resources in the group.
# RG CLRG restart: restarts all the resources of the group.
# CLRG manage RG: Password group under the control of the cluster.
# CLRG unmanage RG: pass the group beyond the control of the cluster.
# CLRG show RG-v: displays the properties of RG Group.

3. Resource Management

The command to use is clrs

# clrs list: list all resources.
# clrs list: list all the resources of the group RG.
# clrs status: the status of all resources.
# RS clrs status: the status of the RS resources.
# clrs RG-g status: the status of all resources group RG.
# clrs disable RS: RS resource stops.
# clrs enable RS: RS resource starts.
# clrs monitor RS: starts monitoring the resource RS.
# clrs unmonitor RS: stop monitoring the resource RS.
# clrs clear-f STOP_FAILED RS: removes the flag STOP_FAILED RS resource.
# clrs show-v RS: displays the properties of the resource RS.
# clrs set-p property = value RS: Changes the value of the property by value proprité

To add a value to a property already defined, it is possible to use + = instead of =

4. Management Logical Hosts

The command to use is clrslh

# clrslh list: list all logical hosts.
# clrslh status: the status of all logical hosts.
# clrslh disable LH: LH stop resource.
# clrslh enable LH: LH starts resources.
# clrslh monitor LH: LH starts monitoring.
# clrslh unmonitor LH: LH stops monitoring.
# LH clrslh clear: removes the error flag of LH.
# clrslh show LH: displays the properties of LH

Solaris 11- Configuring Nsswitch.conf

2013-12-12T15:06:00.002-08:00

##Configuring nsswitch.conf

The next step is to configure the svc:/system/name-service/switch service .

solaris:~$ svccfg -s name-service/switch

svc:/system/name-service/switch> setprop config/default = files

svc:/system/name-service/switch> setprop config/host = "files dns"

svc:/system/name-service/switch> setprop config/ipnode = astring: "files dns"

svc:/system/name-service/switch> exit

solaris:~$ svcadm refresh name-service/switch

solaris:~$ svcadm restart name-service/switch

Now examine the /etc/nsswitch.conf to confirm it worked:

Solaris 11- Configuring DNS Client on the server?

2013-12-12T15:05:00.003-08:00

Now use the svccfg to modify the svc:/network/dns/client service:

solaris:~$ svccfg -s dns/client

svc:/network/dns/client> listprop config

config application

config/value_authorization astring solaris.smf.value.name-service.dns.client

config/nameserver net_address 10.0.0.1

Modify the config/nameserver property and list the results:

svc:/network/dns/client> setprop config/nameserver = (192.168.1.1 4.2.2.2 8.8.8.8)

svc:/network/dns/client> listprop config

config application

config/value_authorization astring solaris.smf.value.name-service.dns.client

config/nameserver net_address 192.168.1.1 4.2.2.2 8.8.8.8

Add the config/search and config/domain properties and list the results:

svc:/network/dns/client> setprop config/search = xyz.com

svc:/network/dns/client> setprop config/domain = xyz.com

svc:/network/dns/client> listprop config

config application

config/value_authorization astring solaris.smf.value.name-service.dns.client

config/nameserver net_address 192.168.1.1 4.2.2.2 8.8.8.8

config/search astring xyz.com

config/domain astring xyz.com

svc:/network/dns/client> exit

Finally refresh and restart the dns/client service:

solaris:~$ svcadm refresh dns/client

solaris:~$ svcadm restart dns/client

Solaris 11 - How to change the hostname of the server?

2013-12-12T15:04:00.001-08:00

1 - To check the current environment properties:

root@solaris:~# svccfg -s system/identity:node listprop config

config application

config/enable_mapping boolean true

config/nodename astring solaris

config/loopback astring solaris

2 - Set the new hostname

root@solaris:~# svccfg -s system/identity:node setprop config/nodename="my-host-name"

root@solaris:~# svccfg -s system/identity:node setprop config/loopback="my-host-name"

3- Refresh the properties:

root@solaris:~# svccfg -s system/identity:node refresh

4 - Restart the service:

root@solaris:~# svcadm restart system/identity:node

5 - verify that the changes took place:

root@solaris:~# svccfg -s system/identity:node listprop config

config application

config/enable_mapping boolean true

config/nodename astring my-host-name

config/loopback astring my-host-name

root@solaris:~# hostname

my-host-name

Oracle Solaris 11 Auditing

2013-11-12T02:27:00.000-08:00

Important files to know: /etc/security/audit_class and /etc/security/audit_event

Important Commands to know: auditconfig , auditrecord

Location for Auditing Logs : /var/audit/

auditconfig -getflags

auditconfig -getnaflags (Get non-attributable flag)

auditconfig -getplugin (To determine which plugins are active)

auditconfig -lspolicy ( List of policies)

auditconfig -getpolicy

auditconfig -setpolicy -cnt (Removing the cnt policy)

auditrecord -c lo (To determine the type of records included under the lo class. Option -c is for selecting the class as mentioned in audit_class)

Configuring Solaris Zones in VCS Clusters

2013-11-08T16:41:00.000-08:00

I have been thinking from quite a while for providing the High Availability to Non-Global zones Vertias Clusters.

Lets see , how we can configure the same.

In Vertias Cluster, Assuming that the non global zone will be on a shared storage and we are configuring a failover or a parallel Service Group.

Configure a parallel service group with required storage resources (DiskGroup,Volume, Mount, etc.) to mount the zone root on the nodes. Set the required dependency between storage resources (DiskGroup->Volume->Mount).
sysA# hagrp -add zone_grp
sysA# hagrp -modify zone_grp Parallel 1 (This step is not included while configuring failover)
sysA# hagrp -modify zone_grp SystemList sysA 0 sysB 1
sysA# hares -add zone_dg DiskGroup zone_grp
sysA# hares -add zone_vol Volume zone_grp
sysA# hares -add zone_mnt Mount zone_grp
sysA# hares -link zone_mnt zone_vol
sysA# hares -link zone_vol zone_dg

Bring the service group online on all the nodes. This command mounts the zone root on all the nodes.
sysA# hagrp -online zone_grp -any (Parallel)
sysA# hagrp -online zone_grp -sysA (Failover)

Boot the local zone on all the nodes outside VCS.
sysA# zoneadm -z local-zone1 boot
sysB# zoneadm -z local-zone2 boot

Run the hazonesetup utility with correct arguments on all the nodes successively.(Parallel)
sysA# hazonesetup -g zone_grp -r zone_res -z local-zone1 -p password -a -l -s sysA,sysB
sysB# hazonesetup -g zone_grp -r zone_res -z local-zone2 -p password -a -l -s sysA,sysB

Run the hazonesetup utility with correct arguments on all the nodes successively.(Failover)
sysA# hazonesetup -g zone_grp -r zone_res -z local-zone1 -p password -a -s sysA,sysB
sysB# hazonesetup -g zone_grp -r zone_res -z local-zone2 -p password -a -s sysA,sysB

Set the proper dependency between the Zone resource and other storage
resources. The Zone resource should depend on storage resource
(Mount->Zone).
sysA# hares -link zone_res zone_mnt

How-to for simple SysAdmin tasks which gets performed differently on Solaris 11

2013-11-08T02:35:00.000-08:00

The previous behavior of modifying a configuration file to configure naming services no longer works.

How a system will get information on hosts, users?
On Solaris 10 - Update /etc/nsswitch.conf

On Solaris 11
#svccfg -s svc:/system/name-service/switch:default

How a system will be able to resolve the hostname resolution with DNS?
On Solaris 10 - Update /etc/resolv.conf

On Solaris 11
# svccg
svc:> select /network/dns/client
svc:/network/dns/client> setprop config/options = "ndots:2,retrans:3,retry:1"
svc:/network/dns/client> listprop config/options
config/options astring ndots:2,retrans:3,retry:1
# svcadm refresh dns/client

How to change the hostname of the system?
On Solaris 10- Update /etc/nodename

On Solaris 11
# svccfg -s svc:/system/identity:node setprop config/nodename = astring: nodename
# svcadm refresh svc:/system/identity:node

# svcadm restart svc:/system/identity:node

How to change or configure Locale and the timezone?

Solaris 11 -changing locale
# svccfg -s svc:/system/environment:init setprop environment/LANG = astring: fr_FR.UTF-8# svcadm refresh svc:/system/environment

Solaris 11- For changing Timezone
# svccfg -s timezone:default setprop timezone/localtime= astring: US/Mountain

# svcadm refresh timezone:default

How to set default route on Solaris 10 vs 11?
On Solaris 10,
You need to update /etc/defaultrouter

Oracle Solaris 11, you can persistently set the default route for a system,
route -p add default ip-address

Few Important Solaris 11 process

2013-11-08T00:49:00.000-08:00

The below are the few important processes which does not require any administration but important to know.

`fsflush`	System daemon that flushes pages to disk
`init`	Initial system process that starts and restarts other processes and SMF components
`intrd`	System process that monitors and balances system load due to interrupts
`kmem_task`	System process that monitors memory cache sizes
`pageout`	System process that controls memory paging to disk
`sched`	System process that is responsible for OS scheduling and process swapping
`vm_tasks`	System process with one thread per processor that balances and distributes virtual memory related workloads across CPUs for better performance.
`zpool-pool-name`	System process for each ZFS storage pool containing the I/O taskq threads for the associated pool

Understanding the Boot Process of Solaris 11 -First Cloud Ready OS

2013-11-04T20:02:00.000-08:00

##Boot Process on Sparc Platforms.##

The boot process can be divided in 4 parts in Sparc Platforms. However the last three steps are common on the SPARC and x86 hardwares.

1. OpenBoot PROM phase
-The OpenBoot Program starts looking for a filesystem reader, it reads the partition map on the boot disk, called a VTOC , at sector 0 . The utility will find and load a file reader from sectors 0-15 , an area called the boot block.
-Now it can find and read the boot archive , a collection of configuration files and driver code that prepares the system to load and execute the kernel program.

Imp1 : We can override the values that are passed as defaults to the kernel by running " boot -a "
Imp2: We can also change the running state or the logging level of Solaris 11 system using "boot -m "

boot -m milestone=<milestone> ( none | all | single-user |multi-user|multi-user-server ] -For setting run state.
boot -m [quiet|verbose|debug] --For Logging

##Boot Process on x86 Platforms.##
In x86 boot process the BIOS call the Master Boot Record (MBR) , 512-byte construct that includes support for a partition table and bootstrap code. The MBR provides support for multibooting, a practice of putting multiple operating systems on a single disk.

The x86 counterpart to the OBP boot utility is the GRUB(Grand Unified Boot Loader)

2. Booter phase
At this point the boot archive file gets read. it comes in a sequence before a file system is available, which is why system needs a special file reader, identified by bootfs variable , to begin with.

Imp: There are three important variables which are being passed.
-bootfs - Locates the file system reader. (variable value eg: rpool/ROOT/solaris)
-kernel -This variable locates the kernel program (variable value eg: /platform/i86pc/kernel/amd64/unix
-module - This variable locates the boot archive file (variable value eg: /platform/i86pc/amd64/boot_archive )

3. Ramdisk phase
The Ramdisk component is a file in ISO format that is mounted and used as a stand-alone, read-only filesystem. It contains drivers and configuration files which setup the earliest stanges of initalizing the kernel program.

Imp: Boot archive is the ramdisk image.

4. Kernel phase
Once those drivers supports the root file system and can attach it to the root device specified in system setup. The kernel then extracts the remaining primary modules from the boot archive, initializes itself, mounts the real root file system, then discards the boot archive. Once initialized, the kernel program can call other programs that build the system to a user-accessible state.

In details:
Once the kernel is loaded, it starts the UNIX system, mounts the necessary file systems from vfstab and runs /usr/sbin/init to bring the system to the “initdefault” state specified in /etc/inittab.

When the system is booted, init is invoked and the following occurs. First, it reads the properties for the svc:/system/environment:init service. Among these properties are values for locale-related environments, such as LANG or LC_CTYPE. init then looks in /etc/inittab for the initdefault entry

Inittab Important Entires
ap::sysinit:/usr/sbin/autopush -f /etc/iu.ap
smf::sysinit:/lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/console

p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/msglog 2<>/dev/msglog

Lets understand each of the top two important entries.
ONE ap::sysinit:/usr/sbin/autopush -f /etc/iu.ap
The autopush command configures the list of modules to be automatically pushed onto the stream when a device is opened. It can also be used to remove a previous setting or get information on a setting.

cat iu.ap -This file contains
# major minor lastminor modules
wc -1 0 ldterm ttcompat

qcn 0 255 ldterm ttcompat

The mentioned modules in the file are present in /kernel/drv directory. For example wc.conf is mentioned in the /kernel/drv and the modules will be loaded accordingly.

SECOND

smf::sysinit:/lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/console

svc.startd is the master restarter daemon for Service Management Facility (SMF) and the default restarter for all services. svc.startd starts, stops, and restarts services based on administrative requests, system failures, or application failures

So, Now lets understand what is boot-archive.
When we install Solaris 11, the system creates the archive by copying key files from the root filesystem . And when ever we make any configuration change which might affect one of these files, so it's important to keep boot archive in sync with the root filesystem copy before shutting down.(sync using update-archive command )

Imp: In solaris 11 the bootadm utility is used to perform the below task.
SPARC: bootadm list-archive and update-archive
x86 : bootadm list-archive | update-archive | list-menu |set-menu

Imp:

How to failover a VCS Service Group ?

2013-09-18T11:19:00.001-07:00

For Example: You have a service group(sg1) currently running on nodeA and you want to fail it over to node B. Then you need to run the below command to perform the failover.

hagrp -switch sg1 to nodeB

VCS- Implementing Veritas Cluster File System (CFS)

2013-09-18T11:15:00.000-07:00

Veritas Cluster File System (CFS)

CFS allows the same file system to be simultaneously mounted on multiple nodes in the cluster.

The CFS is designed with master/slave architecture. Though any node can initiate an operation to create, delete, or resize data, the master node carries out the actual operation. CFS caches the metadata in memory, typically in the memory buffer cache or the vnode cache. A distributed locking mechanism, called GLM, is used for metadata and cache coherency among the multiple nodes.

The examples here are :

1. Based on VCS 5.x but should also work on 4.x
2. A new 4 node cluster with no resources defined.
3. Diskgroups and volumes will be created and shared across all nodes.

Before you configure CFS

1. Make sure you have an established Cluster and running properly.
2. Make sure these packages are installed on all nodes:

VRTScavf Veritas cfs and cvm agents by Symantec
VRTSglm Veritas LOCK MGR by Symantec

3. Make sure you have a license installed for Veritas CFS on all nodes.
4. Make sure vxfencing driver is active on all nodes (even if it is in disabled mode).

Check the status of the cluster

Here are some ways to check the status of your cluster. On these examples, CVM/CFS are not configured yet.

# cfscluster status
 NODE         CLUSTER MANAGER STATE            CVM STATE
serverA        running                        not-running                   
serverB        running                        not-running                   
serverC        running                        not-running                   
serverD        running                        not-running                   

 Error: V-35-41: Cluster not configured for data sharing application

# vxdctl -c mode
mode: enabled: cluster inactive

# /etc/vx/bin/vxclustadm nidmap
Out of cluster: No mapping information available

# /etc/vx/bin/vxclustadm -v nodestate
state: out of cluster

# hastatus -sum

-- SYSTEM STATE
-- System               State                Frozen             

A  serverA             RUNNING              0                   
A  serverB             RUNNING              0                   
A  serverC             RUNNING              0                   
A  serverD             RUNNING              0

Configure the cluster for CFS

During
configuration, veritas will pick up all information that is set on your
cluster configuration. And will activate CVM on all the nodes.

# cfscluster config

       The cluster configuration information as read from cluster
       configuration file is as follows.
               Cluster : MyCluster
               Nodes   : serverA serverB serverC serverD


       You will now be prompted to enter the information pertaining
       to the cluster and the individual nodes.

       Specify whether you would like to use GAB messaging or TCP/UDP
       messaging. If you choose gab messaging then you will not have
       to configure IP addresses. Otherwise you will have to provide
       IP addresses for all the nodes in the cluster.
 
       ------- Following is the summary of the information: ------
               Cluster         : MyCluster
               Nodes           : serverA serverB serverC serverD
               Transport       : gab
       -----------------------------------------------------------


       Waiting for the new configuration to be added.

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

       Cluster File System Configuration is in progress...
       cfscluster: CFS Cluster Configured Successfully

Check the status of the cluster

Now let's check the status of the cluster. And notice that there is now a new service group cvm. CVM is required to be online before we can bring up any clustered filesystem on the nodes.

# cfscluster status

 Node             :  serverA
 Cluster Manager  :  running
 CVM state        :  running
 No mount point registered with cluster configuration


 Node             :  serverB
 Cluster Manager  :  running
 CVM state        :  running
 No mount point registered with cluster configuration


 Node             :  serverC
 Cluster Manager  :  running
 CVM state        :  running
 No mount point registered with cluster configuration


 Node             :  serverD
 Cluster Manager  :  running
 CVM state        :  running
 No mount point registered with cluster configuration

# vxdctl -c mode
mode: enabled: cluster active - MASTER
master: serverA

# /etc/vx/bin/vxclustadm nidmap
Name                             CVM Nid    CM Nid     State
serverA                         0          0          Joined: Master
serverB                         1          1          Joined: Slave
serverC                         2          2          Joined: Slave
serverD                         3          3          Joined: Slave

# /etc/vx/bin/vxclustadm -v nodestate
state: cluster member
       nodeId=0
       masterId=1
       neighborId=1
       members=0xf
       joiners=0x0
       leavers=0x0
       reconfig_seqnum=0xf0a810
       vxfen=off

# hastatus -sum

-- SYSTEM STATE
-- System               State                Frozen             

A  serverA             RUNNING              0                   
A  serverB             RUNNING              0                   
A  serverC             RUNNING              0                   
A  serverD             RUNNING              0                   

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State         

B  cvm             serverA             Y          N               ONLINE        
B  cvm             serverB             Y          N               ONLINE        
B  cvm             serverC             Y          N               ONLINE        
B  cvm             serverD             Y          N               ONLINE

How to find a file or files using maximum space on Unix Systems like Solaris , Linux, HP-UX or AIX?

2013-09-18T11:12:00.000-07:00

Example For Finding out the file bigger than 100MB

find /var -xdev -size +100000000c -exec ls -lh {} \;

-xdev is being used so that you can find out the file in the filesystem where /var is located. Many times we have other filesystems as well part of /var like /var/crash(which is mounted from a another Filesystem) .

So, my advice is to always xdev to ensure that you are searching in the right directory.

HP Service Guard Basic Commands and Important Files

2013-09-17T15:20:00.000-07:00

1. How to check the Service Guard Cluster Version?
root@nodeA:/# cmversion
A.11.17.00

2. How to search for the existing SG clusters in the network?
cmquerycl to search existing Serviceguard clusters in the Network.

root@nodeA:/# cmquerycl -v
Looking for Serviceguard nodes ... Done
Cluster Name Node Name Version Status
Swrecovery
nodeA up to date
nodeB up to date

3. How to check the status of the cluster?

root@nodeA:/etc/cmcluster/sw# cmviewcl -v

CLUSTER STATUS

swrecovery up

NODE STATUS STATE

nodeA up running

nodeB up running

4. How to ensure that the Cluster will start at boot time?

Update: /etc/rc.config.d/cmcluster

AUTOSTART_CMCLD =1

5. How to stop the cluster on both nodes?

#cmhaltcl -v

6. How to start the node in the cluster?

cmrunnode nodeB

7. How to halt a node in the cluster?

cmhaltnode -v nodeB

8. How to start and halt a package?

cmrunpkg -v sw-pkg

cmhaltpkg -v sw-pkg

Few more details.

# cmmodpkg –e pkg1 Globally enable switching for a package.

# cmmodpkg –d pkg1 Globally disable switching for a package.

# cmmodpkg –n nodeA –e pkg1 Enable a node to run a package.

# cmmodpkg –n nodeA –d pkg1 Disable a node to run a package

Setting no expiry of the accounts on solaris

2013-06-12T10:47:00.003-07:00

To turn off password aging and setting the user account to non-expiry

passwd -x -1 username

HP-UX - Find out the serial number of the server

2013-05-28T10:22:00.002-07:00

Itanium
#machinfo

PA-RISC
#getconf MACHINE_SERIAL

HP-UX - How to check the kernel parameter utilization?

2013-05-28T09:29:00.000-07:00

Lets assume we are checking the utilization of shmmax

#kcusage

Tunable Usage / Setting
=============================================
dbc_max_pct 5 / 50
maxdsiz 37666816 / 1073741824
maxdsiz_64bit 7258112 / 4294967296
maxfiles_lim 56 / 8192
maxssiz 1179648 / 8388608
maxssiz_64bit 20480 / 268435456
maxtsiz 421888 / 100663296
maxtsiz_64bit 237568 / 1073741824
maxuprc 0 / 256
max_thread_proc 57 / 256
msgmni 2 / 512
msgseg 0 / 8192
msgtql 0 / 1024
nfile 586 / 65536
nflocks 20 / 4096
ninode 653 / 4880
nkthread 484 / 8416
nproc 150 / 4200
npty 0 / 60
nstrpty 0 / 60
nstrtel 0 / 60
semmni 23 / 2048
semmns 25 / 8192
shmmax 17906400 / 68719476736 --- Utilization is 17906400 of 68719476736
shmmni 7 / 400

HP-UX - How to set the kernel parameter?

2013-05-28T09:23:00.000-07:00

Lets assume that we need to change the kernel parameter shmmax.

Kctune is used to change the kernel parameter.
kctune shmmax=4398046511104

Solaris - Find out the serial number of the server?

2013-05-21T09:51:00.000-07:00

How to find out the serial number of the server by running prtdiag command?
root@Server1:~ # prtdiag -v > /var/tmp/prtdiag.out; sed -n '/^Ch/{p;n;n;p;}' /var/tmp/prtdiag.out; rm /var/tmp/prtdiag.out
Chassis Serial Number
0000XXX000

Redhat- How to find the Hardware Model on linux ?

2013-05-20T19:14:00.003-07:00

Dmidecode reports information about your system's hardware as described in your system BIOS according to the SMBIOS/DMI standard

#dmidecode

This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).

Aix -How to find RAM on the server?

2013-05-20T19:09:00.000-07:00

The bootinfo command uses the device configuration databases in information searches.

Just type the following command as the root user:

#bootinfo -r

It will displays amount of real memory in kilobytes. bootinfo command may not be available in latest AIX UNIX version, try following command:

#lsattr -El sys0 | grep realmem

Aix- How to check if kernel is 32bit or 64 bit?

2013-05-20T14:59:00.001-07:00

KERNEL_BITMODE

# getconf KERNEL_BITMODE
64

HARDWARE_BITMODE

# getconf HARDWARE_BITMODE
64

Redhat Linux - How to for GFS Filesystems

2013-05-20T12:57:00.000-07:00

How-to for GFS Filesystems

You can use either of the following formats to create a clustered GFS file system:
#gfs_mkfs -p lock_dlm -t ClusterName:FSName -j Number BlockDevice
#mkfs -t gfs -p lock_dlm -t LockTableName -j NumberJournals BlockDevice

You can use either of the following formats to create a local GFS file system:
#gfs_mkfs -p lock_nolock -j NumberJournals BlockDevice
#mkfs -t gfs -p lock_nolock -j NumberJournals BlockDevice

At each node, mount the GFS file systems. For more information about mounting a GFS file
Command usage:
mount BlockDevice MountPoint
mount -o acl BlockDevice MountPoint
The -o aclmount option allows manipulating file ACLs. If a file system is mounted without the -o acl mount option, users are allowed to view ACLs (with getfacl), but are not allowed to set them (with setfacl).

Formatting the logical Volume
#gfs_mkfs -p lock_dlm -t alpha:mydata1 -j 8 /dev/vg01/lvol0

The gfs_jadd command must be run on mounted file system, but it only needs to be run on one node in the cluster. All the other nodes sense that the expansion has occurred.

#lvextend -L +80G /dev/vgcl_gfs_san_eos/vol01_lv
#gfs_grow -v /dev/vgcl_gfs_san_eos/vol01_lv /db/eospr1/vol01

Aix -How to find processor Type on IBM Power Systems

2013-05-20T12:52:00.001-07:00

Find the type of processor on AIX

Method 1-Using lsattr

#lsattr -El proc0|grep type
type PowerPC_POWER6 Processor type False

# lsattr -El proc0|grep type
type PowerPC_POWER7 Processor type False

Method 2- Using lscfg

# lscfg -vpl proc0 |grep Name Name: PowerPC,POWER5

HP-UX 11.23 mount: cdfs : Invalid argument" Error While Mounting a CD-ROM

2013-05-19T20:35:00.001-07:00

While trying to mount the DVD on HP-UX 11.23 , we got the below error.

#mount /dev/dsk/c0t0d0 /cdrom
mount: cannot access -specific mount command

#mount -F cdfs -o cdcase /dev/dsk/c0t0d0 /cdrom
mount: cdfs : Invalid argument

The DVD drive is claimed and online in the ioscan output.Other DVDs have been tried as well, but with the same results.

To resolve the issue, the cdfs kernel module was checked and found that the module was not loaded.

#kcmodule -B cdfs=loaded

After loading the cdfs kernel module .The DVD was successfully mounted.