My company has an old system P4 with the following config
Code:
# prtconf | more
System Model: IBM,7029-6C3
Processor Type: PowerPC_POWER4
Number Of Processors: 2
Processor Clock Speed: 1200 MHz
CPU Type: 64-bit
Kernel Type: 32-bit
LPAR Info: 1 NULL
Memory Size: 16384 MB
Good Memory Size: 16384 MB
Firmware Version: IBM,RG040325_d75e04_s
Console Login: enable
Auto Restart: true
Full Core: false
# lsdev -Cc adapter
fcs0 Available 1H-08 FC Adapter
fcs1 Available 1n-08 FC Adapter
lscfg -vl fcs0
fcs0 U0.1-P1-I5/Q1 FC Adapter
Part Number.................00P4295
EC Level....................A
Serial Number...............1D4230CADC
Manufacturer................001D
Feature Code/Marketing ID...5704
FRU Number.................. 00P4297
Device Specific.(ZM)........3
Network Address.............10000000C93E6B3E
ROS Level and ID............02E01871
Device Specific.(Z0)........2003806D
Device Specific.(Z1)........00000000
Device Specific.(Z2)........00000000
Device Specific.(Z3)........03000909
Device Specific.(Z4)........FF601231
Device Specific.(Z5)........02E01871
Device Specific.(Z6)........06631871
Device Specific.(Z7)........07631871
Device Specific.(Z8)........20000000C93E6B3E
Device Specific.(Z9)........HS1.81X1
Device Specific.(ZA)........H1D1.81X1
Device Specific.(ZB)........H2D1.81X1
Device Specific.(YL)........U0.1-P1-I5/Q1
# oslevel -r
5200-05
which AIX 5.2 ML 05
# lsdev -Cc disk
hdisk0 Available 1S-08-00-5,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 1n-08-02 1722-600 (600) Disk Array Device
hdisk3 Available 1H-08-02 1722-600 (600) Disk Array Device
hdisk4 Available 1n-08-02 1722-600 (600) Disk Array Device
hdisk5 Available 1H-08-02 1722-600 (600) Disk Array Device
hdisk6 Available 1n-08-02 1722-600 (600) Disk Array Device
lspath -H
status name parent
Enabled hdisk0 scsi0
Enabled hdisk1 scsi0
lslpp -l | grep mpio
devices.common.IBM.mpio.rte
lslpp -lc | grep mpio
/usr/lib/objrepos:devices.common.IBM.mpio.rte:5.2.0.50::COMMITTED:F:MPIO Disk Path Control Module:
manage_disk_drivers -l
ksh: manage_disk_drivers: not found.
///not found due to old version 5.2
mpio_get_config -Av
ksh: mpio_get_config: not found.
///not found due to old version 5.2
SAN STORAGE DS4300
PROFILE FOR STORAGE SUBSYSTEM: (8/23/13 10:43:42 PM)
SUMMARY------------------------------
Number of controllers: 2
Number of arrays: 4
Total number of logical drives (includes an access logical drive): 6 of 1024 used
Number of standard logical drives: 5
Number of access logical drives: 1
Number of drives: 14
Supported drive types: Fibre (14)
Total hot spare drives: 4
Standby: 4
In use: 0
Access logical drive: LUN 31 (see Mappings section for details)
Default host type: AIX (Host type index 6)
Current configuration
Firmware version: 06.12.16.00
NVSRAM version: N1722F600R912V05
Pending configuration
Staged firmware download supported?: Yes
Firmware version: None
NVSRAM version: None
Transferred on: None
But this one doesn't have any issues, Controller A is connected to Port 0 of Fiber Card 1 and Controller B is connected to Port 1 of Fiber Card 2 but there is a switch in between them and there is zoning.
I will zone the switch as IBMTECH suggested and try and post the details...
If anyone know how to solve this issue, please post.
thanks
Hi All,
I have mirrored SAN volume on my B80 rootvg. Can I just remove the mirror and "Remove a P V from a V G" and it will be a diskless AIX?
Is that going to boot on SAN rootvg volume?
Thanks in advance,
itik (3 Replies)
Hello everyone
I got several aix boxes with aix 5.3
I got a ibm san ds4500
My question is
How can I do a match between my disks on aix and the san?
I try to do a match with the LUN but for example. In my san I got several 1 LUN and on one of my aix box I got this
If I type lscfg... (4 Replies)
We are considering a DR strategy of booting AIX 5.3 and 5.3 logical partitions from EMC Symmetrix SAN disks, so that we can replicate via SRDF to a recovery site. Has anyone tried configuring AIX 5.x systems to boot from SAN disk? If so, can you provide any information on the pros and cons of... (6 Replies)
hi all,
have a solaris 9 OS and a SAN disk which used to work fine is not getting picked up by my machine. can anyone point out things to check in order to troubleshoot this ??
thanks in advance. (3 Replies)
Scenario:
I've got 2 M5000's connected to a 9985 SAN storage array. I have configured the SAN disks with stmsboot, format and newfs. I can access the same SAN space from both systems. I have created files from both systems on the SAN space.
Question:
Why can't I see the file created... (3 Replies)
Hi all,
My main function is as a DBA. Another person manages the server and the SAN.
I just want to know if I should be worried about high disk I/O or is it irrelevant as the I/O "load balancing" will be "taken care" of by the SAN?
For example, I have hdisk1-5 and I can see that there are... (2 Replies)
Hi,
I have a production solaris 10 SPARC system (portal). Yesterday legato/Networker gave an I/O Error on one of the files on its SAN mounted disk.
I went to that particular file on the system, did an ls and it showed the file. However, ls -l did not work and it said IO error.
... (6 Replies)
Hello All,
Our servers having emc clarion for the data disks. Is that possible to see those san disks raid level from AIX ?
Am having AIX 6.1 and EMC clarion 5.5.
Regards,
Gowtham.G (3 Replies)
Hi guys, :)
I'm a studient in IT field (AIX)
I'm trying to map a LUN from a SAN (DS3400) to an AIX server (5300-04-00)
I know there is no MPIO on this version of AIX, and i see double my LUN from the SAN
root@localhost # lscfg | grep hdisk
+ hdisk7 ... (13 Replies)
I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
LEARN ABOUT OPENSOLARIS
devinfo
devinfo(1M) System Administration Commands devinfo(1M)NAME
devinfo - print device specific information
SYNOPSIS
/usr/sbin/devinfo -i device
/usr/sbin/devinfo -p device
DESCRIPTION
The devinfo command is used to print device specific information about disk devices on standard out. The command can only be used by the
superuser.
OPTIONS -i Prints the following device information:
o Device name
o Software version (not supported and prints as 0)
o Drive id number (not supported and prints as 0)
o Device blocks per cylinder
o Device bytes per block
o Number of device partitions with a block size greater than zero
-p Prints the following device partition information:
o Device name
o Device major and minor numbers (in hexadecimal)
o Partition start block
o Number of blocks allocated to the partition
o Partition flag
o Partition tag
This command is used by various other commands to obtain device specific information for the making of file systems and determining parti-
tion information. If the device cannot be opened, an error message is reported.
OPERANDS
device Device name.
EXIT STATUS
0 Successful operation.
2 Operation failed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO prtvtoc(1M), attributes(5)SunOS 5.11 8 May 1997 devinfo(1M)