News update:
The HMC version 7.7.7.0 SP1 having the feature to install the VIOS in the GUI
The HMC version 7.7.7.0 SP1 having the feature to install the VIOS in the GUI
Thursday, May 30, 2013
Friday, February 10, 2012
Unix star group
The further discussion & document will be shared in the google group please join the group
Monday, February 6, 2012
Power 7 features
Power 7 Features
MaxCore:-
1. We can select to run POWER7 in TurboCore(TM) mode to optimize for database or other transaction-oriented workloads and utilize up to 4 cores per chip with twice the cache per core and a faster speed - This saves clients on software costs for those applications that are licensed per core. If the client has workloads is more simultaneous tasks will being all run in parallel, then POWER7 can be run in MaxCore mode providing up to 8 cores and up to 32 threads per socket or chip - each capable of handling a task in parallel with the others.
Intelligent Threads:-
2. Like the two processor modes, POWER7 also features Intelligent Threads that can vary based on the workload demand. The system will either automatically select or the system administrator can manually select whether a workload benefits from dedicating as much capability as possible to a single thread of work, or if the workload benefits more from having capability spread across 2 or 4 threads of work. With more threads, POWER7 can deliver more total capacity as more tasks are accomplished in parallel. With fewer threads, those workloads that need very fast individual tasks, we can get the performance they need for maximum benefit.
Intelligent Cache:-
3. Many workloads benefit from having access to a large amount of very fast memory directly on the processor. This type of memory is known as "cache" and helps the processor cores execute tasks faster when the next piece of information required is close at hand. POWER7 processors have Intelligent Cache with the ability to maximize cache access for the processor cores running tasks that most need it. Each of the up to 8 cores on a POWER7 processor has a very fast level of cache dedicated to each processor core. There is also a larger pool of cache shared among all cores on the chip. If a task running on any specific core doesn't need all of it's portion of the larger pool of cache, other cores can utilize it as access will be intelligently assigned to where it is most needed.
Intelligent Energy:-
4. Finally, POWER7 includes Intelligent Energy features that help to dynamically optimize energy usage and performance so that the best possible balance is maintained. Intelligent Energy features like EnergyScale work with IBM Systems Director Active Energy Manager to dynamically optimize processor speed based on thermal conditions and system utilization. If the system's environment is favorable, the system can speed up processor cores to a frequency up to 10% higher than the normal rated speed to better handle demanding workloads. When utilization is lighter, or if environmental conditions are less favorable, the system can slow processor cores by as much as 50% to save energy. Users can select whether Intelligent Energy Optimization favors maximizing performance or energy savings based on their needs.
AME:-
5. For workloads that require large amounts of memory, or in virtualized environments where more memory is very beneficial, clients can utilize POWER7's Active Memory Expansionto make the physical memory on the system appear to the application as if it were up to twice as large as it actually is. For systems that have their full complement of memory or of memory components, Active Memory Expansion can provide additional memory capability to applications transparently. Active Memory Expansion is a unique POWER7 capability that clients can leverage to take maximum advantage of their memory resources.
Note: About the AME there will be more defecnitions
Active system optimizer:-
6. With AIX 7 TL1 expect to see a new feature called active system optimizer, which is designed to autonomically improve workload performance (AIX 7 on POWER7 only). A new network option you can set is called tcp_fastlo, which enables TCP fast loopback.This reduces TCP/IP overhead and lowers CPU utilization if two TCP endpoints are on the same frame (e.g., communication between two processes in the same LPAR).
Gen2 PCIe:-
7. PCIe Gen2 provides for more I/O ports available per adapter. You'll now see dual port 10G Ethernet cards and 4-port 8G fibre adapters. You'll be able to push SAS data out at 6G per second vs. the current generation's 3G per second. The new 5913 Large Cache SAS adapter has 1.8 GB cache and can drive up to 72 HDD or 26 SSD, or you can mix and match the drive types with this adapter. A huge improvement with this card is that it no longer has batteries, so you won't have to worry about replacing them. If it losespower the card will use a capacitor and write to flash memory
Wednesday, January 11, 2012
SSP on VIO
Shared storage pool
----------------------------
Advantage:-
* simply the aggregation of larg number of disk accress multiple VIO server
* Improve the utilization of the available storage
* using the thin-provisioned, even after mapped a size of logical unit to the client, it will use only when the disk is start filling
Disadvantage:-
* client partition which used this SSP is not supports the live partition mobility
* The number of max client partition per VIOS in the cluster is 20
* The number of max physical volume in SSP is 128
* The number of maximum logical unit in the cluster is 200
* This will support only IP version 4
* minum LUN that mapped to the SSP should be 20GB
* Fiber channel over etnernet (FCoE) adapter not supported
* It will not support non-MIO, SDD, powerpath, legacy HDLM & so on)
* The client server in cluster will not support AMS & suspend/Resume
* The server does not supports SEA interrupt mode
* The logical volume that mapped to the client can't exceed 1TB
Important point:-
* At the time of creating the cluster, only single node per cluster & one single SP per clsuter supported
* The mapping will be the logical usit resides behind the SSP
* Clsuter ip address must be the first entry on /etc/hosts
* changing the hostname is not supported after the VIO is added as the part of clsuter
* Repository disk & SSP should have the redundany at the storage level
* At the time of writing, physical disk in SSP can't be replaced or removed
* only VIOS will be the part of this clsuter
* This clsuter using CAA( clsuter Aware AIX) & RSCT technology, So a network connection is must in between the nodes.
* "poold" daemon handle group services & "vio_daemon" is responsilbe for montior the clsuter & SSP health
prerequest:-
* Power6 & above
* Powervm standar or enterprise edition
* VIO 2.2.0.11 Fix pack 24 sp 1 or later
* Atleast 4GB memory
* client partition should be 5.3 or later
* The physcial drive in SSP should have the default PCM, SDDPCM, Powerpath PCM , HDLM PCM & so on)
* At the time of writing, the SSP supports a sinlge node in the cluster & it will work only when 'poold' & 'vio_daemon' is running
* Each VIOS in cluster requires at least one PV for CAA
Cheers,
GuruRam
Thursday, November 10, 2011
New P7 changed
Last week IBM announced some changes to AIX and the POWER7 lineup. Although the entry servers will still be known as the 710, 720, 730 and 740 and the enterprise servers will still be called the 770 and 780, they will all have new model and machine type numbers. This is intended to help customers differentiate the new servers from the old, though it's important to understand that these machines are not POWER7+.General availability is set for Oct. 21.Here are the new numbers:
Model Machine Type
710 8231-E1C
720 8202-E4C
730 8231-E2C
740 8205-E6C
770 9117-MMC
780 9179-MHC
All of the POWER7-enhanced systems end with the letter C, while of course the current models end in B, so it's easy to determine which system type you have.Another change made in the interest of clarity is that the 710 and 730 no longer share the same machine type and model. Also note that the 740 is no longer available as a tower -- it's exclusively rack-mounted
now.
Enhanced I/O Capabilities and Higher Memory Densities
The biggest changes in the hardware revolve around the enhanced I/O capabilities and the increased memory densities across the servers. The servers all benefit from PCIe Gen2, which, according to the announcement details that I saw, provides "twice the I/O bandwidth which will enable higher performance, greater efficiencies and more flexibility." if you're not driving your Gen1 PCIe adapters to the point where they become your bottleneck, simply switching to Gen2 won't magically give you better performance. However, you will get better utilization of the hardware going forward with Gen2.
PCIe Gen2 provides for more I/O ports available per adapter. You'll now see dual port 10G Ethernet cards and 4-port 8G fibre adapters. You'll be able to push SAS data out at 6G per second vs. the current generation's 3G per second. The new 5913 Large Cache SAS adapter has 1.8 GB cache and can drive up to 72 HDD or 26 SSD, or you can mix and match the drive types with this adapter. A huge improvement with this card is that it no longer has batteries, so you won't have to worry about replacing them. If it losespower the card will use a capacitor and write to flash memory. Note that this available from Oct. 31.
Gen2 allows you to more fully virtualize your systems by pushing more I/O with fewer adapters. With the new Gen2 adapters, you'll benefit whether it's fibre, SAS, networking or infiniband. Moving forward, we can stop thinking about PCI-X and concentrate solely on PCIe.
These new systems have more PCIe I/O slots in the CEC, with greater functionality per slot. The familiar IVE/HEA adapter is replaced with a standard 2-port 1 GB Ethernet card (on the entry systems) and an integrated multifunction card (on the enterprise machines). The latter consists of a 4-port card with two 10GB Ethernet ports and two 1 GB Ethernet ports, plus USB ports and a serial port.
There were four card slots in the entry level CEC; now the entry systems have five slots that can be populated, while the enterprise machines have six slots per CEC. Considering the optional half height cards that can be added to the 720 and 740, you can have up to 10 total cards by counting the standard Ethernet card that comes with the system (though you can't use another card in place of the Ethernet card in that slot).
This announcement also includes new DIMM sizes: 64 GB in the enterprise server space and 16 GB in the entry systems. This allows the new "C" models to have greater maximum memory: 128 GB on the 710, 256 GB on the 720 and 730, and 512 GB on the 740. The new 770 and 780 models can have up to 4 TB of memory in the 4 node system, 1 TB per CEC.
If you need even more cores, a 96-core large capacity 780 server is available. Imagine pairing up 96 cores and 4 TB of memory on your 780. In addition, a clock speed tweak brings the 770 to 3.3 and 3.7 GHz, depending on whether you chose six or eight core per socket. The 780 can max out at 3.92 GHz.
PowerVM and AIX Updates
A few changes are coming with PowerVM and AIX. Active memory mirroring is a feature where the hypervisor has two copies running at the same time, with both copies being updated simultaneously. In the (rare) event of a hypervisor memory failure on the primary copy, the second copy will be invoked with notification sent to IBM. This capability was previously available on the 795, but now with the new machines it comes standard on the 780 and as an option on the 770.
With AIX 7 TL1 expect to see a new feature called active system optimizer, which is designed to autonomically improve workload performance (AIX 7 on POWER7 only). A new network option you can set is called tcp_fastlo, which enables TCP fast loopback. This reduces TCP/IP overhead and lowers CPU utilization if two TCP endpoints are on the same frame (e.g., communication between two processes in the same LPAR).
Another new capability is active memory deduplication. It's available on the new machines running the new firmware, and is used in conjunction with active memory sharing. Active memory deduplication allows systems containing duplicate memory pages to remove those duplicates while fitting similar workloads within any physical memory constraints.
In addition, AIX features JFS2 filesystem enhancements that allow admins to tune performance by altering filesystem caching. This can be accomplished without having to unmount filesystems. Compared to earlier AIX releases, there's a 50 percent reduction in JFS2 memory usage for metadata.
Other software enhancements include:
A new logical volume manager option to retry failed I/O operations indefinitely. This capability can aid in recovery from transient failure of SANs, for instance. AIX 5.3 WPARs, which follow on the current AIX 5.2 WPAR offering. This allows you to run 5.3 workloads inside of AIX 7 into the future (i.e., even after IBM eventually ends its support of AIX 5.3). AIX 5.3 TL12 SP4 is required to make use of the 5.3 WPARs.
The new C models, supports AIX and VIOS
AIX 5.3 TL12 SP5
AIX 6.1 TL5 SP7
AIX 6.1 TL6 SP6
AIX 7.1 TL0 SP4
AIX 7.1 TL1
VIOS 2.2.1
PowerVM offers its own improvements. Live partition mobility operations can potentially run at twice the previous speed while performing up to eight LPM operations at once. Network balancing allows for load balancing across backup and primary shared Ethernet adapters. Shared storage pools are also enhanced. These PowerVM capabilities are available on the new VIO server. I'll definitely write much more on this soon.
There are also updates to PowerHA SystemMirror, including an SAP LiveCache Hot Standby solution, and PowerHA Federated Security, which provides for centralized administration via System Director, along with additional supported storage options to use with HA (including XIV, the V7000, the SVC and DS8800 and options from EMC, Hitachi and HP).
IBM planned in Feature: unattended installation (no-touch VIOS installation), GUI-based VIOS installs, VIOS setup and validation tools, and the capability to manage VIO servers as a pair rather than individually.
Cheers,
Guru
Last week IBM announced some changes to AIX and the POWER7 lineup. Although the entry servers will still be known as the 710, 720, 730 and 740 and the enterprise servers will still be called the 770 and 780, they will all have new model and machine type numbers. This is intended to help customers differentiate the new servers from the old, though it's important to understand that these machines are not POWER7+.General availability is set for Oct. 21.Here are the new numbers:
Model Machine Type
710 8231-E1C
720 8202-E4C
730 8231-E2C
740 8205-E6C
770 9117-MMC
780 9179-MHC
All of the POWER7-enhanced systems end with the letter C, while of course the current models end in B, so it's easy to determine which system type you have.Another change made in the interest of clarity is that the 710 and 730 no longer share the same machine type and model. Also note that the 740 is no longer available as a tower -- it's exclusively rack-mounted
now.
Enhanced I/O Capabilities and Higher Memory Densities
The biggest changes in the hardware revolve around the enhanced I/O capabilities and the increased memory densities across the servers. The servers all benefit from PCIe Gen2, which, according to the announcement details that I saw, provides "twice the I/O bandwidth which will enable higher performance, greater efficiencies and more flexibility." if you're not driving your Gen1 PCIe adapters to the point where they become your bottleneck, simply switching to Gen2 won't magically give you better performance. However, you will get better utilization of the hardware going forward with Gen2.
PCIe Gen2 provides for more I/O ports available per adapter. You'll now see dual port 10G Ethernet cards and 4-port 8G fibre adapters. You'll be able to push SAS data out at 6G per second vs. the current generation's 3G per second. The new 5913 Large Cache SAS adapter has 1.8 GB cache and can drive up to 72 HDD or 26 SSD, or you can mix and match the drive types with this adapter. A huge improvement with this card is that it no longer has batteries, so you won't have to worry about replacing them. If it losespower the card will use a capacitor and write to flash memory. Note that this available from Oct. 31.
Gen2 allows you to more fully virtualize your systems by pushing more I/O with fewer adapters. With the new Gen2 adapters, you'll benefit whether it's fibre, SAS, networking or infiniband. Moving forward, we can stop thinking about PCI-X and concentrate solely on PCIe.
These new systems have more PCIe I/O slots in the CEC, with greater functionality per slot. The familiar IVE/HEA adapter is replaced with a standard 2-port 1 GB Ethernet card (on the entry systems) and an integrated multifunction card (on the enterprise machines). The latter consists of a 4-port card with two 10GB Ethernet ports and two 1 GB Ethernet ports, plus USB ports and a serial port.
There were four card slots in the entry level CEC; now the entry systems have five slots that can be populated, while the enterprise machines have six slots per CEC. Considering the optional half height cards that can be added to the 720 and 740, you can have up to 10 total cards by counting the standard Ethernet card that comes with the system (though you can't use another card in place of the Ethernet card in that slot).
This announcement also includes new DIMM sizes: 64 GB in the enterprise server space and 16 GB in the entry systems. This allows the new "C" models to have greater maximum memory: 128 GB on the 710, 256 GB on the 720 and 730, and 512 GB on the 740. The new 770 and 780 models can have up to 4 TB of memory in the 4 node system, 1 TB per CEC.
If you need even more cores, a 96-core large capacity 780 server is available. Imagine pairing up 96 cores and 4 TB of memory on your 780. In addition, a clock speed tweak brings the 770 to 3.3 and 3.7 GHz, depending on whether you chose six or eight core per socket. The 780 can max out at 3.92 GHz.
PowerVM and AIX Updates
A few changes are coming with PowerVM and AIX. Active memory mirroring is a feature where the hypervisor has two copies running at the same time, with both copies being updated simultaneously. In the (rare) event of a hypervisor memory failure on the primary copy, the second copy will be invoked with notification sent to IBM. This capability was previously available on the 795, but now with the new machines it comes standard on the 780 and as an option on the 770.
With AIX 7 TL1 expect to see a new feature called active system optimizer, which is designed to autonomically improve workload performance (AIX 7 on POWER7 only). A new network option you can set is called tcp_fastlo, which enables TCP fast loopback. This reduces TCP/IP overhead and lowers CPU utilization if two TCP endpoints are on the same frame (e.g., communication between two processes in the same LPAR).
Another new capability is active memory deduplication. It's available on the new machines running the new firmware, and is used in conjunction with active memory sharing. Active memory deduplication allows systems containing duplicate memory pages to remove those duplicates while fitting similar workloads within any physical memory constraints.
In addition, AIX features JFS2 filesystem enhancements that allow admins to tune performance by altering filesystem caching. This can be accomplished without having to unmount filesystems. Compared to earlier AIX releases, there's a 50 percent reduction in JFS2 memory usage for metadata.
Other software enhancements include:
A new logical volume manager option to retry failed I/O operations indefinitely. This capability can aid in recovery from transient failure of SANs, for instance. AIX 5.3 WPARs, which follow on the current AIX 5.2 WPAR offering. This allows you to run 5.3 workloads inside of AIX 7 into the future (i.e., even after IBM eventually ends its support of AIX 5.3). AIX 5.3 TL12 SP4 is required to make use of the 5.3 WPARs.
The new C models, supports AIX and VIOS
AIX 5.3 TL12 SP5
AIX 6.1 TL5 SP7
AIX 6.1 TL6 SP6
AIX 7.1 TL0 SP4
AIX 7.1 TL1
VIOS 2.2.1
PowerVM offers its own improvements. Live partition mobility operations can potentially run at twice the previous speed while performing up to eight LPM operations at once. Network balancing allows for load balancing across backup and primary shared Ethernet adapters. Shared storage pools are also enhanced. These PowerVM capabilities are available on the new VIO server. I'll definitely write much more on this soon.
There are also updates to PowerHA SystemMirror, including an SAP LiveCache Hot Standby solution, and PowerHA Federated Security, which provides for centralized administration via System Director, along with additional supported storage options to use with HA (including XIV, the V7000, the SVC and DS8800 and options from EMC, Hitachi and HP).
IBM planned in Feature: unattended installation (no-touch VIOS installation), GUI-based VIOS installs, VIOS setup and validation tools, and the capability to manage VIO servers as a pair rather than individually.
Cheers,
Guru
Wednesday, February 23, 2011
IVM & HMC difference
With IVM, dual VIO server configuration is not possible
- system power-on must be done by physically pushing the system power-on
button or remotely accessing ASMI
- Multiple systems can be managed via one HMC interface, but IVM can mange
only one system
- In Power5 some Power6 systems, you cannot assign physical adapters to
partitions by IVM
- Only one virtual SCSI adapter is supported for IVM-managed LPARs
- Multiple Shared Processor Pools are not supported on IVM-managed POWER6
systems
regards,
Guru
- system power-on must be done by physically pushing the system power-on
button or remotely accessing ASMI
- Multiple systems can be managed via one HMC interface, but IVM can mange
only one system
- In Power5 some Power6 systems, you cannot assign physical adapters to
partitions by IVM
- Only one virtual SCSI adapter is supported for IVM-managed LPARs
- Multiple Shared Processor Pools are not supported on IVM-managed POWER6
systems
regards,
Guru
Tuesday, February 22, 2011
unable to find the boot device
While creating the bosboot or while listing the boot list we will get an error as "unable to find the boot device" or there will be no output while giving the command "bootinfo -b".
This is due to bugs on the OS(5.3 TL7 or 6.1 TL3/5 SP3) , please proceed the below steps.
Verify the /dev/ipldevice & /dev/ipl_blv
Verify the df -g (check for hd5)
use the command "ipl_varyon -i" command to verify the boot disk info
" You can able to see the rootvg's hdisk status as 'YES' "
if the ipldevice or ipl_blv is not there create the link as shown below
Link the rootvg's hdisk to ipldevice " ln /dev/rdsik# /dev/ipldevice"
Link the hd5 to ipl_blv "ln /dev/hd5 /dev/ipl_blv"
Now if everything looks good reboot the LPAR. It will resolve the issue
Note:-
Before doing any installation (TL upgrade, patching or OS migration) reboot the machine to be in the safer side.
Regards,
Guru
This is due to bugs on the OS(5.3 TL7 or 6.1 TL3/5 SP3) , please proceed the below steps.
Verify the /dev/ipldevice & /dev/ipl_blv
Verify the df -g (check for hd5)
use the command "ipl_varyon -i" command to verify the boot disk info
" You can able to see the rootvg's hdisk status as 'YES' "
if the ipldevice or ipl_blv is not there create the link as shown below
Link the rootvg's hdisk to ipldevice " ln /dev/rdsik# /dev/ipldevice"
Link the hd5 to ipl_blv "ln /dev/hd5 /dev/ipl_blv"
Now if everything looks good reboot the LPAR. It will resolve the issue
Note:-
Before doing any installation (TL upgrade, patching or OS migration) reboot the machine to be in the safer side.
Regards,
Guru
Thursday, May 28, 2009
HACMP IP concepts
HACMP
Boot ip address:
The Ip which we are assigning to the physical adapter, using smitty tcpip, this boot ip will work while system is booting & until the HACMP service is starting, this boot ip address will there in the entire physical adapter which is included in the HACMP network.
Note: By default there is no route for this IP address, the route ip will only available for Service, persistent & management ip address.
Persistent ip address:
The Persistent ip address is only for the administrator access, this will never come under any official document which we declared to the client, this is also one of the virtual ip, even if all the ips goes down also this will work, all the admin work should happen through this IP only.
It’s regardless whether the HACMP service is running or not, this is one of the routed ip address, where you can access at any time. This ip will be in primary network card.
Note: One persistent ip is allowed for one network, for example a node connected to 2 networks defined in HACMP, that node can be identified by two persistent ip labels (addresses).
This persistent ip we will declare this while configuring the HACMP we will mention, as soon as the Nodes synched it start working, even the HACMP service stopped also. If the primary cards failed the persistent ip will automatically switched to the secondary interface, if the server is breakdown or rebooted that time only the this ip will go down.
Concept of the Persistent ip:
For IPAT via ip replacement:
The persistent ip must be in the different subnet to the standby interface, but it can be in same subnet as the primary interface & service ip.
For IPAT via ip alias:
The persistent ip must be different from both the boot ip subnet.
Service Ip:
The Service ip is the ip used by the client to access the application, this service ip is monitoring by the HACMP service because it’s the part of the RG.
Two Types of Service IP:
Shared service ip:
This service ip can be configured on multiple nodes and it’s the part of RG that can be active on one node at a time.
Node-bound service ip:
This service ip can configure on one node only (not shared on multiple node), this type of ip concept is usable in concurrent RG.
Note: This service ip’s will work when the HACMP service is coming up.
We have 4 types service ip distribution:
Anti-Collocation:
This is the normal configuration, the Service ip will distribute to all boot ip interface in the same HACMP network.
Collocation:
HACMP will allocate all service ip on the same boot ip interface.
Collocation with persistent label:
HACMP will allocate all the service ip on boot ip interface that is hosting the persistent IP label, this will be useful for the VPN user & firewall setup where only one interface is granted for external communication.
Anti-Collocation with persistent label:
HACMP will distribute all the service ip label to all the boot ip interface in the same HACMP network, this is not hosting the persistent ip label, if there is shortage of interface then the service ip will share the adapter with the persistence alias ip label.
Wednesday, May 6, 2009
TSM Server-Side Daily Administrator Checklist
1. List TSM license compliance.
audit lic
select compliance from licenses
2. Query server processes and pending requests to determine if any jobs are waiting on operator action.
q pr
q req
q se
3. Query all disk storage pools to determine if the migration process has completed.
select stgpool_name, pct_utilized from stgpools where devclass='DISK'
4. List all drives that are OFFLINE.
select drive_name from drives where not online='YES'
5. List all paths that are OFFLINE.
select source_name, source_type, destination_name, destination_type from paths where not online='YES'
6. List all locked nodes.
select node_name from nodes where not locked='NO'
7. List all non-writeable tape and disk volumes.
q v acc=unavail
q v acc=reado
q v acc=destroyed
select volume_name, read_errors, write_errors from volumes where (read_errors>0 or write_errors>0)
select volume_name from volumes where devclass_name='DISK' and not status='ONLINE'
8. Verify that the library has sufficient scratch volumes.
select library_name,status,count(*) as "VOLUMES" from libvolumes group by library_name,status
9. Verify that the database extension and reduction values are non-zero and that the Cache Hit Ration is above 99%.
q db f=d
10. Verify that the recovery log extension and reduction values are non-zero and that the Wait Percentage is zero.
q log f=d
11. Verify that database and recovery log volumes are online and synchronized.
q dbv f=d
q logv f=d
12. Inspect TSM database fragmentation level.
select cast((100 - (cast(max_reduction_mb as float) * 256 ) / (cast(usable_pages as float) - cast(used_pages as float) ) * 100) as decimal(4,2)) as PERCENT_FRAG from db
13. Verify that the scheduled database backups completed successfully.
select date (date_time) as date, time(date_time) as time, volume_name, type from volhistory where type in ('BACKUPFULL', 'BACKUPINCR', 'DBSNAPSHOT', 'DBDUMP')
14. Verify that all CLIENT schedules for the last day succeeded.
q ev * * begind=-1 endd=today begint=00:00:00 endt=00:00:00
To restrict the listing to only those nodes with non-completed status:
q ev * * begind=-1 endd=today begint=00:00:00 endt=00:00:00 ex=y
15. Verify that all ADMINISTRATIVE schedules for the last day succeeded.
q ev * t=a begind=-1 endd=today begint=00:00:00 endt=00:00:00
To restrict the listing to only those nodes with non-completed status:
q ev * t=a begind=-1 endd=today begint=00:00:00 endt=00:00:00 ex=y
16. Check the activity log for error messages.
q actl search=AN?????E begind=-1 begint=00:00 endd=today endt=00:00
17. List nodes that are not associated with a backup schedule.
select node_name from nodes where node_name not in (select node_name from associations)
18. Cross match the TSM node name with the host name or computer name.
select node_name, tcp_address, tcp_name from nodes
19. List PRIMARY POOL volumes that have been checked out of the library.
select volume_name, stgpool_name from volumes where stgpool_name in (select stgpool_name from stgpools where devclass<>'DISK' and pooltype='PRIMARY') and volume_name not in (select volume_name from libvolumes)
20. Checkout all D/R Media for offsite storage.
move drm * wherest=mo tost=va rem=b
21. Verify that all D/R volumes have been checked out.
select volume_name from libvolumes where volume_name in (select volume_name from volumes where stgpool_name in (select stgpool_name from stgpools where devclass<>'DISK' and pooltype='COPY'))
22. Verify that all TSM database backup volumes have been checked out.
select volume_name from libvolumes where last_use='DbBackup'
23. Identify previous offsite volumes that can be recycled to scratch status and checkin the same.
q drm wherest=vaultr
move drm * wherest=vaultr tost=onsite
checki libvcheckl=b stat=scr search=b wait=0
24. Generate a list of unlocked TSM administrator accounts with full system privileges.
select admin_name from admins where not system_priv='No' and not locked='No'
25. List TSM Nodes and Client (BA/TDP) versions by platform.
select platform_name as OS, client_os_level as OS_VER, node_name as Node, cast(cast(client_version as char(2)) '.' cast(client_release as char(2)) '.' cast(client_level as char(2)) '.' cast(client_sublevel as char(2)) as char(15)) as "TSM Client" from nodes order by platform_name, "TSM Client", Node
26. Data backed up in the last 24 hours:
select entity, date(start_time) as DATE, time(start_time) as START_TIME, time(end_time) as END_TIME, substr(char(end_time-start_time),3,8) as DURATION, cast((bytes/1024/1024/1024) as decimal(18,2)) as GB_BACKED_UP, successful from summary where cast((current_timestamp-start_time) hours as decimal)<24>=current_timestamp-24 hours and activity='BACKUP' group by entity
29. Size and duration of archive operations for each node in the last 24 hours:
select entity as "Node Name ", cast(sum(bytes/1024/1024) as decimal(10,3)) as "Total MB", substr(cast(min(start_time) as char(26)),1,19) as "Date/Time ", cast(substr(cast(max(end_time)-min(start_time) as char(20)),3,8) as char(8)) as "Length " from summary where start_time>=current_timestamp-24 hours and activity='ARCHIVE' group by entity
30. Compare PRIMARY and COPY pool occupancy totals.
select sum(num_files) as num_of_files,sum(physical_mb) as Physical_mb,sum(logical_mb) as logical_mb from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='PRIMARY')
select sum(num_files) as num_of_files,sum(physical_mb) as Physical_mb,sum(logical_mb) as logical_mb from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='COPY')
regards,
GuruRam
audit lic
select compliance from licenses
2. Query server processes and pending requests to determine if any jobs are waiting on operator action.
q pr
q req
q se
3. Query all disk storage pools to determine if the migration process has completed.
select stgpool_name, pct_utilized from stgpools where devclass='DISK'
4. List all drives that are OFFLINE.
select drive_name from drives where not online='YES'
5. List all paths that are OFFLINE.
select source_name, source_type, destination_name, destination_type from paths where not online='YES'
6. List all locked nodes.
select node_name from nodes where not locked='NO'
7. List all non-writeable tape and disk volumes.
q v acc=unavail
q v acc=reado
q v acc=destroyed
select volume_name, read_errors, write_errors from volumes where (read_errors>0 or write_errors>0)
select volume_name from volumes where devclass_name='DISK' and not status='ONLINE'
8. Verify that the library has sufficient scratch volumes.
select library_name,status,count(*) as "VOLUMES" from libvolumes group by library_name,status
9. Verify that the database extension and reduction values are non-zero and that the Cache Hit Ration is above 99%.
q db f=d
10. Verify that the recovery log extension and reduction values are non-zero and that the Wait Percentage is zero.
q log f=d
11. Verify that database and recovery log volumes are online and synchronized.
q dbv f=d
q logv f=d
12. Inspect TSM database fragmentation level.
select cast((100 - (cast(max_reduction_mb as float) * 256 ) / (cast(usable_pages as float) - cast(used_pages as float) ) * 100) as decimal(4,2)) as PERCENT_FRAG from db
13. Verify that the scheduled database backups completed successfully.
select date (date_time) as date, time(date_time) as time, volume_name, type from volhistory where type in ('BACKUPFULL', 'BACKUPINCR', 'DBSNAPSHOT', 'DBDUMP')
14. Verify that all CLIENT schedules for the last day succeeded.
q ev * * begind=-1 endd=today begint=00:00:00 endt=00:00:00
To restrict the listing to only those nodes with non-completed status:
q ev * * begind=-1 endd=today begint=00:00:00 endt=00:00:00 ex=y
15. Verify that all ADMINISTRATIVE schedules for the last day succeeded.
q ev * t=a begind=-1 endd=today begint=00:00:00 endt=00:00:00
To restrict the listing to only those nodes with non-completed status:
q ev * t=a begind=-1 endd=today begint=00:00:00 endt=00:00:00 ex=y
16. Check the activity log for error messages.
q actl search=AN?????E begind=-1 begint=00:00 endd=today endt=00:00
17. List nodes that are not associated with a backup schedule.
select node_name from nodes where node_name not in (select node_name from associations)
18. Cross match the TSM node name with the host name or computer name.
select node_name, tcp_address, tcp_name from nodes
19. List PRIMARY POOL volumes that have been checked out of the library.
select volume_name, stgpool_name from volumes where stgpool_name in (select stgpool_name from stgpools where devclass<>'DISK' and pooltype='PRIMARY') and volume_name not in (select volume_name from libvolumes)
20. Checkout all D/R Media for offsite storage.
move drm * wherest=mo tost=va rem=b
21. Verify that all D/R volumes have been checked out.
select volume_name from libvolumes where volume_name in (select volume_name from volumes where stgpool_name in (select stgpool_name from stgpools where devclass<>'DISK' and pooltype='COPY'))
22. Verify that all TSM database backup volumes have been checked out.
select volume_name from libvolumes where last_use='DbBackup'
23. Identify previous offsite volumes that can be recycled to scratch status and checkin the same.
q drm wherest=vaultr
move drm * wherest=vaultr tost=onsite
checki libv
24. Generate a list of unlocked TSM administrator accounts with full system privileges.
select admin_name from admins where not system_priv='No' and not locked='No'
25. List TSM Nodes and Client (BA/TDP) versions by platform.
select platform_name as OS, client_os_level as OS_VER, node_name as Node, cast(cast(client_version as char(2)) '.' cast(client_release as char(2)) '.' cast(client_level as char(2)) '.' cast(client_sublevel as char(2)) as char(15)) as "TSM Client" from nodes order by platform_name, "TSM Client", Node
26. Data backed up in the last 24 hours:
select entity, date(start_time) as DATE, time(start_time) as START_TIME, time(end_time) as END_TIME, substr(char(end_time-start_time),3,8) as DURATION, cast((bytes/1024/1024/1024) as decimal(18,2)) as GB_BACKED_UP, successful from summary where cast((current_timestamp-start_time) hours as decimal)<24>=current_timestamp-24 hours and activity='BACKUP' group by entity
29. Size and duration of archive operations for each node in the last 24 hours:
select entity as "Node Name ", cast(sum(bytes/1024/1024) as decimal(10,3)) as "Total MB", substr(cast(min(start_time) as char(26)),1,19) as "Date/Time ", cast(substr(cast(max(end_time)-min(start_time) as char(20)),3,8) as char(8)) as "Length " from summary where start_time>=current_timestamp-24 hours and activity='ARCHIVE' group by entity
30. Compare PRIMARY and COPY pool occupancy totals.
select sum(num_files) as num_of_files,sum(physical_mb) as Physical_mb,sum(logical_mb) as logical_mb from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='PRIMARY')
select sum(num_files) as num_of_files,sum(physical_mb) as Physical_mb,sum(logical_mb) as logical_mb from occupancy where stgpool_name in (select stgpool_name from stgpools where pooltype='COPY')
regards,
GuruRam
Monday, May 4, 2009
When do AIX kenel processes start
ஹாய்,
"ps -fk" lists that there are many kernel processes with PPID=0. I have read in documents that init process is started to handle rc.boot at boot time. So, when do kernel processes start, and why they have PPID=0? Furthermore, "swapper" process has both PID=PPID=0. Is it realy the parent of init and others who have PPID=0?
Process 0 is the parent of Init.
The very first kernel process/thread is a pure Kernel-Land process and
has PID 0.
Then Process 0 becomes the "swapper".
Process 0 launch the init process (PID 1), which is responsible for
User-Land processes.
That'why Init is the (grand) father of all user-land processes.
There are some other pure kernel-land process that are launched by the
PID 0 process, hence they have PPID 0 (e.g. kproc).
regards,
Guru Ram
"ps -fk" lists that there are many kernel processes with PPID=0. I have read in documents that init process is started to handle rc.boot at boot time. So, when do kernel processes start, and why they have PPID=0? Furthermore, "swapper" process has both PID=PPID=0. Is it realy the parent of init and others who have PPID=0?
Process 0 is the parent of Init.
The very first kernel process/thread is a pure Kernel-Land process and
has PID 0.
Then Process 0 becomes the "swapper".
Process 0 launch the init process (PID 1), which is responsible for
User-Land processes.
That'why Init is the (grand) father of all user-land processes.
There are some other pure kernel-land process that are launched by the
PID 0 process, hence they have PPID 0 (e.g. kproc).
regards,
Guru Ram
Sunday, January 4, 2009
HACMP snapshot backup
Hi dudes,
Lets see about the HACMP snapshot backup,the below mentioned snaphots taken from one node of HACMP, take the backup from one node is enough, it will take the entire backup,
Hope this will help you peoples.
regards,
Guru.
"Moving out from the team is also the team work"
Thursday, December 25, 2008
TSM client side access
Hi dudes,
There is something crazy about this TSM in all our mind, after looking on to this, its much easier like linux. I hope that the below mentioned messages will give you some dare to speak about TSM in the conference,
Basic Info on TSM Client
Some Terms:
Node Name: Name assigned to TSM client while registering in TSM server
Backup: It’s a backup, which can have 2 or more versions in TSM Server
1. Active version of backup which is the latest backup
2. Inactive version of backup which is older than the latest backup
Archive: It’s a backup, which can have any no. of versions depends upon the expiry date defined in the management class(no. of days of archive stored in tsm server)
You can open a TSM client software using
1. dsm – GUI based tool
2. dsmc – Text based tool
Lets get into some basic commands:
To View the session information like the server name, node name (client) etc…
$ dsmc query session
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 0.12
Client date/time: 11/24/0801:15:11
(c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved.
Node Name: DDADB350
Session established with server TSM_SERVER: AIX-RS/6000
Server Version 5, Release 2, Level 3.0
Data compression forced on by the server
Server date/time: 11/24/0801:15:12 Last access: 11/24/0800:54:26
TSM Server Connection Information
Server Name.............: TSM_SERVER
Server Type.............: AIX-RS/6000
Server Version..........: Ver. 5, Rel. 2, Lev. 3.0
Last Access Date........: 11/24/0800:54:26
Delete Backup Files.....: "Yes"
Delete Archive Files....: "Yes"
Node Name...............: DDADB350
User Name...............: root
This shows that
client name is CLIENT
TSM server name is TSM_SERVER.
TSM Server version is 5.2
TSM Client version is 5.3
How to take a backup:
To take selective files:
$ dsmc selective /usr/* -subdir=yes
To take incremental:
$ dsmc incremental /usr/* -subdir=yes
How to archive:
$ dsmc archive /usr/* -archmc=arch0365 –subdir=yes
Here archmc is the term for management class and arch0365 is a customized management class, which will keep the data in tape for 365 days. We can create customized MC in TSM Server.
How to check the active backup:
$ dsmc query backup /usr/* -subdir=yes
How to check the inactive backup:
$ dsmc query backup /usr/* -inactive –subdir=yes
How to check for archived data:
$ dsmc query archive /usr/* -subdir=yes
This will list the files archived, which can be on different dates:
You can use from date option to get a list of archive from that particular date:
$ dsmc query archive /usr/* -fromdate=11/02/06 –subdir=yes
How to check the latest backup date and time:
$ dsmc query filespace
here fs means the file space. File space is the space kept in TSM server for each file system. This command will list the backup information with last backup date.
$ root dsmc query filespace
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 0.12
Client date/time: 11/24/0801:25:50
(c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved.
Node Name: DDADB350
Session established with server TSM_SERVER: AIX-RS/6000
Server Version 5, Release 2, Level 3.0
Data compression forced on by the server
Server date/time: 11/24/0801:25:50 Last access: 11/24/0801:15:12
TSM Scrollable Window - Query Filespace
# Last Incr Date Type File Space Name
---------------------------------------------------------------------------------------------------------------------
1. | 02/10/06 22:01:45 JFS /
2. | 02/10/06 22:04:46 JFS2 /db2/RVI/db2dump
3. | 11/24/0800:54:17 JFS2 /db2/RVI/dbs
4. | 02/10/06 22:04:46 JFS2 /db2/RVI/sapdata
5. | 02/10/06 22:04:46 JFS2 /db2/RVI/sapdatat
6. | 02/10/06 22:04:47 JFS2 /db2/db2as
7. | 02/10/06 22:04:54 JFS2 /db2/db2rvi
8. | 02/10/06 22:04:07 JFS /home
9. | 00/00/00 00:00:00 API:archive /mksysb_apitsm
10. | 02/10/06 22:04:18 JFS /opt
11. | 02/10/06 22:05:19 JFS2 /opt/TWS
12. | 11/24/0800:54:10 JFS2 /sapmnt/RVI
13. | 11/24/0800:54:25 JFS2 /sapwork/RVI
14. | 00/00/00 00:00:00 JFS /snap
15. | 02/10/06 22:03:41 JFS /usr
16. | 02/10/06 22:04:27 JFS /usr/local
17. | 02/10/06 22:04:36 JFS /usr/local/Tivoli/lcf/ddadb350
18. | 11/24/0800:54:14 JFS2 /usr/sap/RVI
19. | 02/10/06 22:04:01 JFS /var
20. | 02/10/06 22:04:41 JFS /var/local
0---------10--------20--------30--------40--------50--------60--------70--------80--------90--------100-------110----
=Up=Down =Right =Left
There is something crazy about this TSM in all our mind, after looking on to this, its much easier like linux. I hope that the below mentioned messages will give you some dare to speak about TSM in the conference,
Basic Info on TSM Client
Some Terms:
Node Name: Name assigned to TSM client while registering in TSM server
Backup: It’s a backup, which can have 2 or more versions in TSM Server
1. Active version of backup which is the latest backup
2. Inactive version of backup which is older than the latest backup
Archive: It’s a backup, which can have any no. of versions depends upon the expiry date defined in the management class(no. of days of archive stored in tsm server)
You can open a TSM client software using
1. dsm – GUI based tool
2. dsmc – Text based tool
Lets get into some basic commands:
To View the session information like the server name, node name (client) etc…
$ dsmc query session
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 0.12
Client date/time: 11/24/0801:15:11
(c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved.
Node Name: DDADB350
Session established with server TSM_SERVER: AIX-RS/6000
Server Version 5, Release 2, Level 3.0
Data compression forced on by the server
Server date/time: 11/24/0801:15:12 Last access: 11/24/0800:54:26
TSM Server Connection Information
Server Name.............: TSM_SERVER
Server Type.............: AIX-RS/6000
Server Version..........: Ver. 5, Rel. 2, Lev. 3.0
Last Access Date........: 11/24/0800:54:26
Delete Backup Files.....: "Yes"
Delete Archive Files....: "Yes"
Node Name...............: DDADB350
User Name...............: root
This shows that
client name is CLIENT
TSM server name is TSM_SERVER.
TSM Server version is 5.2
TSM Client version is 5.3
How to take a backup:
To take selective files:
$ dsmc selective /usr/* -subdir=yes
To take incremental:
$ dsmc incremental /usr/* -subdir=yes
How to archive:
$ dsmc archive /usr/* -archmc=arch0365 –subdir=yes
Here archmc is the term for management class and arch0365 is a customized management class, which will keep the data in tape for 365 days. We can create customized MC in TSM Server.
How to check the active backup:
$ dsmc query backup /usr/* -subdir=yes
How to check the inactive backup:
$ dsmc query backup /usr/* -inactive –subdir=yes
How to check for archived data:
$ dsmc query archive /usr/* -subdir=yes
This will list the files archived, which can be on different dates:
You can use from date option to get a list of archive from that particular date:
$ dsmc query archive /usr/* -fromdate=11/02/06 –subdir=yes
How to check the latest backup date and time:
$ dsmc query filespace
here fs means the file space. File space is the space kept in TSM server for each file system. This command will list the backup information with last backup date.
$ root dsmc query filespace
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 3, Level 0.12
Client date/time: 11/24/0801:25:50
(c) Copyright by IBM Corporation and other(s) 1990, 2005. All Rights Reserved.
Node Name: DDADB350
Session established with server TSM_SERVER: AIX-RS/6000
Server Version 5, Release 2, Level 3.0
Data compression forced on by the server
Server date/time: 11/24/0801:25:50 Last access: 11/24/0801:15:12
TSM Scrollable Window - Query Filespace
# Last Incr Date Type File Space Name
---------------------------------------------------------------------------------------------------------------------
1. | 02/10/06 22:01:45 JFS /
2. | 02/10/06 22:04:46 JFS2 /db2/RVI/db2dump
3. | 11/24/0800:54:17 JFS2 /db2/RVI/dbs
4. | 02/10/06 22:04:46 JFS2 /db2/RVI/sapdata
5. | 02/10/06 22:04:46 JFS2 /db2/RVI/sapdatat
6. | 02/10/06 22:04:47 JFS2 /db2/db2as
7. | 02/10/06 22:04:54 JFS2 /db2/db2rvi
8. | 02/10/06 22:04:07 JFS /home
9. | 00/00/00 00:00:00 API:archive /mksysb_apitsm
10. | 02/10/06 22:04:18 JFS /opt
11. | 02/10/06 22:05:19 JFS2 /opt/TWS
12. | 11/24/0800:54:10 JFS2 /sapmnt/RVI
13. | 11/24/0800:54:25 JFS2 /sapwork/RVI
14. | 00/00/00 00:00:00 JFS /snap
15. | 02/10/06 22:03:41 JFS /usr
16. | 02/10/06 22:04:27 JFS /usr/local
17. | 02/10/06 22:04:36 JFS /usr/local/Tivoli/lcf/ddadb350
18. | 11/24/0800:54:14 JFS2 /usr/sap/RVI
19. | 02/10/06 22:04:01 JFS /var
20. | 02/10/06 22:04:41 JFS /var/local
0---------10--------20--------30--------40--------50--------60--------70--------80--------90--------100-------110----
=Up
=Quit
query filespace> Q
How to restore active backup:
$ dsmc restore /usr/* -subdir=yes
You have to use “subdir” option to restore subdirectories.
How to restore inactive backups:
$ dsmc restore /usr/* - inactive –subdir=yes
How to restore archive:
$ dsmc retrieve /usr/* -subdir=yes
You can retrieve a archive from a particular date using “fromdate” option.
$ dsmc retrieve /usr/* -fromdate=11/02/06 –subdir=yes
To get the scheduled backup information on a client:
$ dsmc
tsm> q schedule
Schedule Name: AIX_05_client_04
Description: Incr backups
Schedule Style: Classic
Action: Incremental
Options:
Objects:
Priority: 5
Next Execution: 20 Hours and 27 Minutes
Duration: 1 Hour
Period: 1 Day
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expire: Never
Schedule Name: AIX_05_MKSYSB_19
Description: Monthly System Backup
Schedule Style: Classic
Action: Command
Options:
Objects: /usr/local/bin/mksysb_apitsm
Priority: 5
Next Execution: 190 Hours and 27 Minutes
Duration: 1 Hour
Period: 1 Month
Day of Week: Any
Month:
Day of Month:
Week of Month:
Expire: Never
Here we have 2 schedules for this client.
For help:
$ dsmc
Ø help
To search the IBM Tivoli Storage Manager technical support Web site to find
technical solutions and answers to frequently asked questions, refer to
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html.
The following help topics are available.
Enter the number of the desired help topic or 'q' to quit,
'd' to scroll down, 'u' to scroll up.
0 - Summary of Changes for TSM Version 5.3
1 - Using Commands
2 - Select from the commands listed below:
3 - ARCHIVE
4 - BACKUP GROUP
5 - BACKUP IMAGE
6 - BACKUP NAS
7 - BACKUP WAS
8 - CANCEL PROCESS
9 - CANCEL RESTORE
10 - DELETE ACCESS
11 - DELETE ARCHIVE
12 - DELETE BACKUP
13 - DELETE FILESPACE
14 - DELETE GROUP
15 - EXPIRE
16 - HELP
17 - INCREMENTAL
18 - LOOP
19 - MACRO
20 - MONITOR PROCESS
21 - PREVIEW
22 - QUERY ACCESS
23 - QUERY ARCHIVE
24 - QUERY BACKUP
25 - QUERY BACKUPSET
26 - QUERY FILESPACE
27 - QUERY GROUP
28 - QUERY IMAGE
29 - QUERY INCLEXCL
30 - QUERY MGMTCLASS
31 - QUERY NODE
32 - QUERY OPTIONS
33 - QUERY RESTORE
You can get the syntax of any command here.
will be continue.............
warm regards,
Guru
**********************
*Experiance the name, *
*men given to thier mistake *
Wednesday, December 24, 2008
Adding the printer quue
Hi,
The procedure to add the network printer queue is not a difficult task at any time, in AIX too.
Example: Printer IP (192.168.1.2)
Put the entry in your AIX server host file
vi /etc/hots
192.168.1.2 tallyprinter
Smitty printer --> print spooling --> Add a print queue -->remote--> Local filtering before sending to print server--> others(select if printer is not listed)-->generic printer -->
ASCII (lp001)
hostname of remote server (tallyprinter)
name of the queue on the remote server (lp001)
press Enter...............
now the network printer is added with the name "lp001"
you can check the printer with the command
"lp -dlp001 /etc/host"
regards,
Guru
The procedure to add the network printer queue is not a difficult task at any time, in AIX too.
Example: Printer IP (192.168.1.2)
Put the entry in your AIX server host file
vi /etc/hots
192.168.1.2 tallyprinter
Smitty printer --> print spooling --> Add a print queue -->remote--> Local filtering before sending to print server--> others(select if printer is not listed)-->generic printer -->
ASCII (lp001)
hostname of remote server (tallyprinter)
name of the queue on the remote server (lp001)
press Enter...............
now the network printer is added with the name "lp001"
you can check the printer with the command
"lp -dlp001 /etc/host"
regards,
Guru
Friday, November 7, 2008
UNIX performance monitoring
The nmon is the IBM recommended tool to monitor the server performance (linux,AIX)
Download nmon clickhere
Setup procedure:-
This is the tool u can insert in the linux or aix machine by creating one directory, run the below mentioned command in that particular directory wr u placed the nmon file.
this is the EXcel file, before open this file disable the macros in the microsoft Excel security settings, and open the nmon anlyzer file click on the button available over there it will ask for the nmon file, choose the location of the file wr u have in ur desktop, this tool will generate the GUI based report.
this report have almost all nformation of your system including LPAR, CPU,MEMORY,NETWORK,HDD usage, SAN............... etc.,
You can use this at the peak time to check the performance of the servers like DB2, SQL, Websphere, HTTP servers.
regards,
Guru
Download nmon clickhere
Setup procedure:-
This is the tool u can insert in the linux or aix machine by creating one directory, run the below mentioned command in that particular directory wr u placed the nmon file.
./nmonIt will generate one file in the hostname, export that file to your desktop machine using FTP or Winscp, the file will be in the .nmon extention, now u download the nmon analyzer clickhere-fT -s 30 -c 120
this is the EXcel file, before open this file disable the macros in the microsoft Excel security settings, and open the nmon anlyzer file click on the button available over there it will ask for the nmon file, choose the location of the file wr u have in ur desktop, this tool will generate the GUI based report.
this report have almost all nformation of your system including LPAR, CPU,MEMORY,NETWORK,HDD usage, SAN............... etc.,
You can use this at the peak time to check the performance of the servers like DB2, SQL, Websphere, HTTP servers.
regards,
Guru
Thursday, September 25, 2008
The HACMP
HACMP is the aplication developed by IBM for the AIX, but after the version 5.4 the HACMP is designed to work with linux also.
This developed on the basis of HA clustering, By default the application will choose the default location /opt/...., but the HACMP will choose /usr/es/sbin/cluster
./clstat is the command to view the cluster state, it will show you the cluster name & the resource group information.
http://rakeshs.com/viewtopic.php?f=5&t=5
regards,
Guru
This developed on the basis of HA clustering, By default the application will choose the default location /opt/...., but the HACMP will choose /usr/es/sbin/cluster
./clstat is the command to view the cluster state, it will show you the cluster name & the resource group information.
http://rakeshs.com/viewtopic.php?f=5&t=5
regards,
Guru
Tuesday, September 16, 2008
Killing an unwanted user by giving "w" commands
KILL A USER, IN THE UNIX SENSE
To kill all the processes associated with a particular user
simply:
# kill -9 `ps -aefgrep jondoe awk '{ print $2 }'`
To kill all the processes associated with a particular user
simply:
# kill -9 `ps -aefgrep jondoe awk '{ print $2 }'`
Thursday, September 11, 2008
Vi Cheat Sheet
Click here for the Advanced VI Cheatsheet
Modes
| Vi has two modes insertion mode and command mode. The editor begins in command mode, where the cursor movement and text deletion and pasting occur. Insertion mode begins upon entering an insertion or change command. [ESC] returns the editor to command mode (where you can quit, for example by typing :q!). Most commands execute as soon as you type them except for "colon" commands which execute when you press the ruturn key. |
Quitting
| :x | Exit, saving changes |
| :q | Exit as long as there have been no changes |
| ZZ | Exit and save changes if any have been made |
| :q! | Exit and ignore any changes |
Inserting Text
| i | Insert before cursor |
| I | Insert before line |
| a | Append after cursor |
| A | Append after line |
| o | Open a new line after current line |
| O | Open a new line before current line |
| r | Replace one character |
| R | Replace many characters |
Motion
| h | Move left |
| j | Move down |
| k | Move up |
| l | Move right |
| w | Move to next word |
| W | Move to next blank delimited word |
| b | Move to the beginning of the word |
| B | Move to the beginning of blank delimted word |
| e | Move to the end of the word |
| E | Move to the end of Blank delimited word |
| ( | Move a sentance back |
| ) | Move a sentance forward |
| { | Move a paragraph back |
| } | Move a paragraph forward |
| 0 | Move to the begining of the line |
| $ | Move to the end of the line |
| 1G | Move to the first line of the file |
| G | Move to the last line of the file |
| nG | Move to nth line of the file |
| :n | Move to nth line of the file |
| fc | Move forward to c |
| Fc | Move back to c |
| H | Move to top of screen |
| M | Move to middle of screen |
| L | Move to botton of screen |
| % | Move to associated ( ), { }, [ ] |
Deleting Text
| Almost all deletion commands are performed by typing d followed by a motion. For example, dw deletes a word. A few other deletes are: |
| x | Delete character to the right of cursor |
| X | Delete character to the left of cursor |
| D | Delete to the end of the line |
| dd | Delete current line |
| :d | Delete current line |
Yanking Text
| Like deletion, almost all yank commands are performed by typing y followed by a motion. For example, y$ yanks to the end of the line. Two other yank commands are: |
| yy | Yank the current line |
| :y | Yank the current line |
Changing text
| The change command is a deletion command that leaves the editor in insert mode. It is performed by typing c followed by a motion. For wxample cw changes a word. A few other change commands are: |
| C | Change to the end of the line |
| cc | Change the whole line |
Putting text
| p | Put after the position or after the line |
| P | Put before the poition or before the line |
Buffers
| Named buffers may be specified before any deletion, change, yank or put command. The general prefix has the form "c where c is any lowercase character. for example, "adw deletes a word into buffer a. It may thereafter be put back into text with an appropriate "ap. |
Markers
| Named markers may be set on any line in a file. Any lower case letter may be a marker name. Markers may also be used as limits for ranges. |
| mc | Set marker c on this line |
| `c | Go to beginning of marker c line. |
| 'c | Go to first non-blank character of marker c line. |
Search for strings
| /string | Search forward for string |
| ?string | Search back for string |
| n | Search for next instance of string |
| N | Search for previous instance of string |
Replace
| The search and replace function is accomplished with the :s command. It is commonly used in combination with ranges or the :g command (below). |
| :s/pattern/string/flags | Replace pattern with string according to flags. |
| g | Flag - Replace all occurences of pattern |
| c | Flag - Confirm replaces. |
| & | Repeat last :s command |
Regular Expressions
| . (dot) | Any single character except newline |
| * | zero or more occurances of any character |
| [...] | Any single character specified in the set |
| [^...] | Any single character not specified in the set |
| ^ | Anchor - beginning of the line |
| $ | Anchor - end of line |
| \< | Anchor - begining of word |
| \> | Anchor - end of word |
| \(...\) | Grouping - usually used to group conditions |
| \n | Contents of nth grouping |
| [A-Z] | The SET from Capital A to Capital Z |
| [a-z] | The SET from lowercase a to lowercase z |
| [0-9] | The SET from 0 to 9 (All numerals) |
| [./=+] | The SET containing . (dot), / (slash), =, and + |
| [-A-F] | The SET from Capital A to Capital F and the dash (dashes must be specified first) |
| [0-9 A-Z] | The SET containing all capital letters and digits and a space |
| [A-Z][a-zA-Z] | In the first position, the SET from Capital A to Capital Z In the second character position, the SET containing all letters |
| /Hello/ | Matches if the line contains the value Hello |
| /^TEST$/ | Matches if the line contains TEST by itself |
| /^[a-zA-Z]/ | Matches if the line starts with any letter |
| /^[a-z].*/ | Matches if the first character of the line is a-z and there is at least one more of any character following it |
| /2134$/ | Matches if line ends with 2134 |
| /\(21|35\)/ | Matches is the line contains 21 or 35 Note the use of ( ) with the pipe symbol to specify the 'or' condition |
| /[0-9]*/ | Matches if there are zero or more numbers in the line |
| /^[^#]/ | Matches if the first character is not a # in the line |
| Notes: 1. Regular expressions are case sensitive 2. Regular expressions are to be used where pattern is specified | |
Counts
| Nearly every command may be preceded by a number that specifies how many times it is to be performed. For example, 5dw will delete 5 words and 3fe will move the cursor forward to the 3rd occurence of the letter e. Even insertions may be repeated conveniently with thismethod, say to insert the same line 100 times. |
Ranges
| Ranges may precede most "colon" commands and cause them to be executed on a line or lines. For example :3,7d would delete lines 3-7. Ranges are commonly combined with the :s command to perform a replacement on several lines, as with :.,$s/pattern/string/g to make a replacement from the current line to the end of the file. |
| :n,m | Range - Lines n-m |
| :. | Range - Current line |
| :$ | Range - Last line |
| :'c | Range - Marker c |
| :% | Range - All lines in file |
| :g/pattern/ | Range - All lines that contain pattern |
Files
| :w file | Write to file |
| :r file | Read file in after line |
| :n | Go to next file |
| :p | Go to previos file |
| :e file | Edit file |
| !!program | Replace line with output from program |
Other
| ~ | Toggle upp and lower case |
| J | Join lines |
| . | Repeat last text-changing command |
| u | Undo last change |
| U | Undo all changes to line |
Subscribe to:
Posts (Atom)
