Posted by: ibmadmin | April 12, 2011

SSH Login Without Password

SSH Login Without Password


In day today middleware administration, we may need to run many automated scripts from one UNIX servers to another UNIX servers. In this case, we need to SSH to another server without password to run the scripts. You can following the below steps to configure the SSH from server ONE (user1) to server TWO(user2).

We need to have access to server ONE and  server TWO to generate the SSH key and move the SSH public key to the server TWO.
Read More…

Posted by: ibmadmin | April 12, 2011

IBM MQ – Queue clear

The messages in the queues can be cleared using the following MQSC command.

CLEAR QLOCAL(TEST_Q)
Read More…

Posted by: ibmadmin | February 24, 2011

How Google Indexing Works – SEO

How Google Indexing Works – SEO

Many of us surprise how google indexing works to rank a website. Google has explained about their ranking of a new websites and how we can request google to crawling a new website. The details are well explained in google site and the following link clearly explain about the google crawling.

http://services.google.com/breeze/webmasters/googleforwebmasters/

Google Definition for indexing the websites:

Googlebot is Google’s web crawling robot, which finds and retrieves pages on the web and hands them off to the Google indexer. It’s easy to imagine Googlebot as a little spider scurrying across the strands of cyberspace, but in reality Googlebot doesn’t traverse the web at all. It functions much like your web browser, by sending a request to a web server for a web page, downloading the entire page, then handing it off to Google’s indexer.

If you have developed a new web site and you like to index the new website in google then go to the following link and add your website link in that. That will suggest google to crawling your new site. You can give your site URL in well known site from where google can pick your link and it will index your new site.

http://www.google.com/addurl.html

To know more about google crawling, use the following link..

http://www.googleguide.com/google_works.html

You can post the sitemap.xml in google site to explain about your site links to google. In the same way you can hide your website’s pages by entering the unwanted pages’ url in Robots.txt or in “no index meta tags” in your web pages. To know more about sitemap.xml details visit the following link.

http://www.google.com/support/webmasters/bin/topic.py?topic=8476

And here how the sitemap.xml file for google site.

http://www.google.com/sitemap.xml

Google search can be fine tuned by adding more parameters to your search criteria. Here is the google guideline for the effective search.

http://www.googleguide.com/sharpening_queries.html

Friends please post your view/comments how yahoo and bing search engines works.

Have a safe googling!!!!!!!!!

Read More…

Posted by: ibmadmin | February 22, 2011

SSL at a glance

The following presentation gives us the details explanation about the PKI technology.

Posted by: ibmadmin | February 22, 2011

IBM Websphere Application Server Security

The following presentation help us to understand the IBM Websphere Application Server6.1 security model.

Posted by: ibmadmin | February 22, 2011

JEE 6 at a glance

The new features of JEE 6 is explained in the following slide show.

The details about coding examples are explained in the following slide show.

Posted by: ibmadmin | February 22, 2011

SOA at a glance

The following presentation will give you the overview of the SOA process.

The IBM Websphere Datapower device help us to achieve the SOA road map. The below presentation help us to understand the IBM Websphere Datapower device details.

Posted by: ibmadmin | February 21, 2011

Sticky Bit in UNIX world

Sticky Bit

The sticky bit on a directory is a permission bit that protects files within that directory. If the directory has the sticky bit set, only the owner of the file, the owner of the directory, or root can delete the file. The sticky bit prevents a user from deleting other users’ files from public directories, such as uucppublic:

castle% ls -l /var/spool/uucppublic
drwxrwxrwt 2 uucp uucp 512 Sep 10 18:06 uucppublic
castle%
When you set up a public directory on a TMPFS temporary file system, make sure that you set the sticky bit manually.

You can set sticky bit permissions by using the chmod command to assign the octal value 1 as the first number in a series of four octal values. Use the following steps to set the sticky bit on a directory:

1. If you are not the owner of the file or directory, become superuser.
2. Type chmod and press Return.
3. Type ls -l and press Return to verify that the permissions of the file have changed.
The following example sets the sticky bit permission on the pubdir directory:

castle% chmod 1777 pubdir
castle% ls -l pubdir
drwxrwxrwt 2 winsor staff 512 Jul 15 21:23 pubdir
castle%

Ref: http://snap.nlc.dcccd.edu/reference/sysadmin/julian/ch18/402-404.html#Heading32

Posted by: ibmadmin | February 21, 2011

Getting System Details in Various OS

In middleware environment, getting the hardware configuration is one of the challenging task to calculate the software licenses . In this discussion, I will give some useful commands to get the system information in following OS.

1. Windows 2003 Server
2. Solaris 9/10
3. HP UX

Windows 2003 Server

We can use the ‘msinfo32’ command from the ‘run’ option to list out all the software configuration information for the Windows 2003 Server. This command will gives the system model, number of CUP and total physical and virtual memory on the server.

Sample Output from the msinfo32 command:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
Activation Status
System Name Your System Name
System Manufacturer Dell Inc.
System Model OptiPlex 755
System Type X86-based PC
Processor x86 Family 6 Model 15 Stepping 13 GenuineIntel ~2392 Mhz
BIOS Version/Date Dell Inc. A10, 4/30/2008
SMBIOS Version 2.5
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name Your user id
Time Zone Eastern Standard Time
Total Physical Memory 4,096.00 MB
Available Physical Memory 2.10 GB
Total Virtual Memory 2.00 GB

Available Virtual Memory 1.96 GB
Page File Space 4.45 GB
Page File C:\pagefile.sys

There is an another command which will list out all system configuration details. The command is dxdiag which can be executed from the ‘run’ option.

Here is the same output from the dxdiag command. The same type of command is available in Solaris 9 and Solaris 10 OS that will help us to determine about the complete system configuration and system status.

System Information
------------------
Time of this report: 2/21/2011, 11:28:10
Machine name: Your System Name
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.100427-1636)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: OptiPlex 755
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A10
Processor: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz (2 CPUs)
Memory: 3316MB RAM
Page File: 1159MB used, 3395MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode

The good point about dxdiag command is, we can save the output of the above parameters into a text file. That will gives the flexibility to analyze or share the dxdiag output to any one.

Solaris

We have very interesting commands in Solaris (i.e. Solaris 9 and Solaris 10) to find out the hardware configurations.

The /usr/sbin/prtconf command prints the hardware configuration of the server. It give us the information about the server memory and the server model and other system information. The sample output from the prtconf command is given below.

$ /usr/sbin/prtconf
System Configuration: Sun Microsystems sun4v
Memory size: 32640 Megabytes
System Peripherals (Software Nodes):

SUNW,SPARC-Enterprise-T5120
scsi_vhci, instance #0
packages (driver not attached)

The most useful command in Solaris to identify the complete system configuration details and the diagnose report is /usr/sbin/prtdiag command. The output of the prtdiag command give the complete picture about the physical server configuration details.

The Following output give the details information about the prtdiag command output. We can easily get the number of virtual CPU and the total memory (RAM) size and the memory slot information about the Solaris servers.

$ /usr/sbin/prtdiag
System Configuration: Sun Microsystems sun4v SPARC Enterprise T5120
Memory size: 32640 Megabytes

================================ Virtual CPUs ================================
CPU ID Frequency Implementation Status
------ --------- ---------------------- -------
0 1415 MHz SUNW,UltraSPARC-T2 on-line
1 1415 MHz SUNW,UltraSPARC-T2 on-line
2 1415 MHz SUNW,UltraSPARC-T2 on-line
......
......
62 1415 MHz SUNW,UltraSPARC-T2 on-line
63 1415 MHz SUNW,UltraSPARC-T2 on-line

======================= Physical Memory Configuration ========================
Segment Table:
--------------------------------------------------------------
Base Segment Interleave Bank Contains
Address Size Factor Size Modules
--------------------------------------------------------------
0x0 32 GB 8 4 GB MB/CMP0/BR0/CH0/D0
MB/CMP0/BR0/CH1/D0
4 GB MB/CMP0/BR0/CH0/D1
MB/CMP0/BR0/CH1/D1
4 GB MB/CMP0/BR1/CH0/D0
MB/CMP0/BR1/CH1/D0
4 GB MB/CMP0/BR1/CH0/D1
MB/CMP0/BR1/CH1/D1
4 GB MB/CMP0/BR2/CH0/D0
MB/CMP0/BR2/CH1/D0
4 GB MB/CMP0/BR2/CH0/D1
MB/CMP0/BR2/CH1/D1
4 GB MB/CMP0/BR3/CH0/D0
MB/CMP0/BR3/CH1/D0
4 GB MB/CMP0/BR3/CH0/D1
MB/CMP0/BR3/CH1/D1

================================ IO Devices ================================
Slot + Bus Name + Model
Status Type Path
----------------------------------------------------------------------------
MB/NET0 PCIE network-pciex8086,105e
/pci@0/pci@0/pci@1/pci@0/pci@2/network@0
MB/NET1 PCIE network-pciex8086,105e
/pci@0/pci@0/pci@1/pci@0/pci@2/network@0,1
MB/NET2 PCIE network-pciex8086,105e
/pci@0/pci@0/pci@1/pci@0/pci@3/network@0
MB/NET3 PCIE network-pciex8086,105e
/pci@0/pci@0/pci@1/pci@0/pci@3/network@0,1
MB/SASHBA PCIE scsi-pciex1000,58 LSI,1068E
/pci@0/pci@0/pci@2/scsi@0
MB PCIX usb-pciclass,0c0310
/pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0
MB PCIX usb-pciclass,0c0310
/pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,1
MB PCIX usb-pciclass,0c0320
/pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2

============================ Environmental Status ============================
Fan sensors:
All fan sensors are OK.

Fan indicators:
All fan indicators are OK.

Temperature sensors:
All temperature sensors are OK.

Temperature indicators:
All temperature indicators are OK.

Current sensors:
All current sensors are OK.

Current indicators:
All current indicators are OK.

Voltage sensors:
All voltage sensors are OK.

Voltage indicators:
All voltage indicators are OK.

============================ FRU Status ============================
All FRUs are enabled.
$

In HP UX, we have two type of environment. The HP UX PA-RISC environment uses 32 bit architecture and the 64bit architecture for HP UNIX environment is Itanium is also called as IA64 bit processer.

We can use the /usr/contrib/bin/machinfo command to get the complete details about the IA64 bit harware details.

Here is the sample output from the IA64 bit environment for /usr/contrib/bin/machinfo command.

$/usr/contrib/bin/machinfo
CPU info:
2 Intel(R) Itanium(R) Processor 9310s (1.6 GHz, 5 MB)
2.39 GT/s QPI, CPU version E0

Memory: 10234 MB (9.99 GB)

Firmware info:
Firmware revision: 04.20.05
FP SWA driver revision: 1.18
IPMI is supported on this system.
BMC firmware revision: 4.14

Platform info:
Model: "ia64 hp server Integrity Virtual Machine"
Machine ID number: XXXXXXXXXXXXX-XXX-XXX-XXXX-XXXXXXXXXXXXX
Machine serial number: XXXXXXXX

OS info:
Nodename: Your System Name - Host Name
Release: HP-UX B.11.31
Version: U (unlimited-user license)
Machine: ia64
ID Number: XXXXXXXXXXXX
vmunix adb: error: /stand/current/vmunix: Permission denied.
$

Use the following commands to get the CPU and memory (RAM) configuration details in HP UNIX PA RISC servers.


$ /usr/sbin/ioscan -kf|grep -i processor
processor 0 33 processor CLAIMED PROCESSOR Processor
processor 1 97 processor CLAIMED PROCESSOR Processor
$
$ /usr/sbin/ioscan -kf
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (803)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 0 0/0/0/0 btlan CLAIMED INTERFACE HP PCI 10/100Base-TX Core
ext_bus 0 0/0/1/0 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide LVD
target 0 0/0/1/0.1 tgt CLAIMED DEVICE
tape 0 0/0/1/0.1.0 stape CLAIMED DEVICE HP C5683A
target 1 0/0/1/0.7 tgt CLAIMED DEVICE
ctl 0 0/0/1/0.7.0 sctl CLAIMED DEVICE Initiator
ext_bus 1 0/0/1/1 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Ended
target 2 0/0/1/1.0 tgt CLAIMED DEVICE
disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
target 3 0/0/1/1.2 tgt CLAIMED DEVICE
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
target 4 0/0/1/1.7 tgt CLAIMED DEVICE
ctl 1 0/0/1/1.7.0 sctl CLAIMED DEVICE Initiator
ext_bus 2 0/0/2/0 c720 CLAIMED INTERFACE SCSI C87x Ultra Wide Single-Ended
target 5 0/0/2/0.0 tgt CLAIMED DEVICE
disk 2 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
target 6 0/0/2/0.2 tgt CLAIMED DEVICE
disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
target 7 0/0/2/0.7 tgt CLAIMED DEVICE
ctl 2 0/0/2/0.7.0 sctl CLAIMED DEVICE Initiator
ext_bus 3 0/0/2/1 c720 CLAIMED INTERFACE SCSI C87x Fast Wide Single-Ended
target 8 0/0/2/1.2 tgt CLAIMED DEVICE
disk 4 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
target 9 0/0/2/1.7 tgt CLAIMED DEVICE
ctl 3 0/0/2/1.7.0 sctl CLAIMED DEVICE Initiator
tty 1 0/0/4/0 func0 CLAIMED INTERFACE PCI BaseSystem (103c128d)
tty 0 0/0/4/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 0/2/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
fcp 2 0/2/0/0.10 fcp NO_HW INTERFACE FCP Domain
ext_bus 5 0/2/0/0.10.42.0.0 fcparray NO_HW INTERFACE FCP Array Interface
target 10 0/2/0/0.10.42.0.0.0 tgt NO_HW DEVICE
disk 5 0/2/0/0.10.42.0.0.0.0 sdisk NO_HW DEVICE EMC SYMMETRIX
target 11 0/2/0/0.10.42.0.0.8 tgt NO_HW DEVICE
disk 9 0/2/0/0.10.42.0.0.8.2 sdisk NO_HW DEVICE EMC SYMMETRIX
disk 11 0/2/0/0.10.42.0.0.8.3 sdisk NO_HW DEVICE EMC SYMMETRIX
target 12 0/2/0/0.10.42.0.0.14 tgt NO_HW DEVICE
disk 17 0/2/0/0.10.42.0.0.14.6 sdisk NO_HW DEVICE EMC SYMMETRIX
disk 18 0/2/0/0.10.42.0.0.14.7 sdisk NO_HW DEVICE EMC SYMMETRIX
target 13 0/2/0/0.10.42.0.0.15 tgt NO_HW DEVICE
disk 20 0/2/0/0.10.42.0.0.15.6 sdisk NO_HW DEVICE EMC SYMMETRIX
ext_bus 6 0/2/0/0.10.42.255.0 fcpdev NO_HW INTERFACE FCP Device Interface
target 14 0/2/0/0.10.42.255.0.0 tgt NO_HW DEVICE
ctl 5 0/2/0/0.10.42.255.0.0.0 sctl NO_HW DEVICE EMC SYMMETRIX
fcp 0 0/2/0/0.14 fcp CLAIMED INTERFACE FCP Domain
fcp 5 0/2/0/0.100 fcp CLAIMED INTERFACE FCP Domain
ext_bus 15 0/2/0/0.100.23.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 28 0/2/0/0.100.23.0.0.0 tgt CLAIMED DEVICE
disk 23 0/2/0/0.100.23.0.0.0.0 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 33 0/2/0/0.100.23.0.0.0.1 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 36 0/2/0/0.100.23.0.0.0.2 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 38 0/2/0/0.100.23.0.0.0.3 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 40 0/2/0/0.100.23.0.0.0.4 sdisk CLAIMED DEVICE DGC CX4-960WDR5
ext_bus 11 0/2/0/0.100.23.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 23 0/2/0/0.100.23.255.0.0 tgt CLAIMED DEVICE
ctl 10 0/2/0/0.100.23.255.0.0.0 sctl CLAIMED DEVICE DGC CX4-960
ext_bus 16 0/2/0/0.100.215.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 27 0/2/0/0.100.215.0.0.0 tgt CLAIMED DEVICE
disk 22 0/2/0/0.100.215.0.0.0.0 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 26 0/2/0/0.100.215.0.0.0.1 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 28 0/2/0/0.100.215.0.0.0.2 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 30 0/2/0/0.100.215.0.0.0.3 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 34 0/2/0/0.100.215.0.0.0.4 sdisk CLAIMED DEVICE DGC CX4-960WDR5
ext_bus 12 0/2/0/0.100.215.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 24 0/2/0/0.100.215.255.0.0 tgt CLAIMED DEVICE
ctl 9 0/2/0/0.100.215.255.0.0.0 sctl CLAIMED DEVICE DGC CX4-960
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 1 0/5/0/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
fcp 3 0/5/0/0.20 fcp NO_HW INTERFACE FCP Domain
ext_bus 7 0/5/0/0.20.42.0.0 fcparray NO_HW INTERFACE FCP Array Interface
target 15 0/5/0/0.20.42.0.0.0 tgt NO_HW DEVICE
disk 6 0/5/0/0.20.42.0.0.0.0 sdisk NO_HW DEVICE EMC SYMMETRIX
target 16 0/5/0/0.20.42.0.0.8 tgt NO_HW DEVICE
disk 7 0/5/0/0.20.42.0.0.8.2 sdisk NO_HW DEVICE EMC SYMMETRIX
disk 8 0/5/0/0.20.42.0.0.8.3 sdisk NO_HW DEVICE EMC SYMMETRIX
target 17 0/5/0/0.20.42.0.0.14 tgt NO_HW DEVICE
disk 15 0/5/0/0.20.42.0.0.14.6 sdisk NO_HW DEVICE EMC SYMMETRIX
disk 16 0/5/0/0.20.42.0.0.14.7 sdisk NO_HW DEVICE EMC SYMMETRIX
target 18 0/5/0/0.20.42.0.0.15 tgt NO_HW DEVICE
disk 19 0/5/0/0.20.42.0.0.15.6 sdisk NO_HW DEVICE EMC SYMMETRIX
ext_bus 8 0/5/0/0.20.42.255.0 fcpdev NO_HW INTERFACE FCP Device Interface
target 19 0/5/0/0.20.42.255.0.0 tgt NO_HW DEVICE
ctl 6 0/5/0/0.20.42.255.0.0.0 sctl NO_HW DEVICE EMC SYMMETRIX
fcp 1 0/5/0/0.24 fcp CLAIMED INTERFACE FCP Domain
fcp 4 0/5/0/0.200 fcp CLAIMED INTERFACE FCP Domain
ext_bus 13 0/5/0/0.200.23.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 25 0/5/0/0.200.23.0.0.0 tgt CLAIMED DEVICE
disk 21 0/5/0/0.200.23.0.0.0.0 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 25 0/5/0/0.200.23.0.0.0.1 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 27 0/5/0/0.200.23.0.0.0.2 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 29 0/5/0/0.200.23.0.0.0.3 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 31 0/5/0/0.200.23.0.0.0.4 sdisk CLAIMED DEVICE DGC CX4-960WDR5
ext_bus 9 0/5/0/0.200.23.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 21 0/5/0/0.200.23.255.0.0 tgt CLAIMED DEVICE
ctl 7 0/5/0/0.200.23.255.0.0.0 sctl CLAIMED DEVICE DGC CX4-960
ext_bus 14 0/5/0/0.200.215.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 26 0/5/0/0.200.215.0.0.0 tgt CLAIMED DEVICE
disk 24 0/5/0/0.200.215.0.0.0.0 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 32 0/5/0/0.200.215.0.0.0.1 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 35 0/5/0/0.200.215.0.0.0.2 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 37 0/5/0/0.200.215.0.0.0.3 sdisk CLAIMED DEVICE DGC CX4-960WDR5
disk 39 0/5/0/0.200.215.0.0.0.4 sdisk CLAIMED DEVICE DGC CX4-960WDR5
ext_bus 10 0/5/0/0.200.215.255.0 fcpdev CLAIMED INTERFACE FCP Device Interface
target 22 0/5/0/0.200.215.255.0.0 tgt CLAIMED DEVICE
ctl 8 0/5/0/0.200.215.255.0.0.0 sctl CLAIMED DEVICE DGC CX4-960
ba 6 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ext_bus 4 0/8/0/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
target 20 0/8/0/0.7 tgt CLAIMED DEVICE
ctl 4 0/8/0/0.7.0 sctl CLAIMED DEVICE Initiator
ba 7 0/9 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 8 0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 1 0/10/0/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Base-T Adapter
ba 9 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
lan 2 0/12/0/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Base-T Adapter
pbc 0 32 pbc CLAIMED BUS_NEXUS Bus Converter
processor 0 33 processor CLAIMED PROCESSOR Processor
pbc 1 96 pbc CLAIMED BUS_NEXUS Bus Converter
processor 1 97 processor CLAIMED PROCESSOR Processor
memory 0 192 memory CLAIMED MEMORY Memory
$

Posted by: ibmadmin | February 21, 2011

Welcome To Middleware Administrator World

Friends,

I try to collect some useful information in the middleware administration world and put it here. Please share your views and thought on this.

« Newer Posts

Categories