04-19-2007
thanks for the info.
i am considering calling IBM on this. While it is only a test box and the data isnt that important its the other data on the SAN that im worried about.
As for SDD yes it was upgraded -
it was still on devices.sdd.43.rte so i had to upgrade to devices.sdd.53.rte which puts it on version 1.6.2.0.
This is the problems im getting though - when i run the command you suggested - datapath query ver - it comes up again with device file not found.
As for the LUN ID's ,take a look at the data i posted - unless im mistaken the same LUN id's are still present ( these are the numbers after the vpathxx (dev) part arent they? ). Same LUN id's just in a slightly different order. So i was happy with that.
I'm starting to wonder that even though i have followed the IBM instructions that there is a conflict between the newer version of all the software i.e.
SDD
Host Attachment script
devices.fcp.disk.ibm2105.rte
devices.scsi.disk.ibm2105.rte
and something else on my server - also i cannot seem to find the FC adapters that i have on the IBM website
lscfg -vl fcs0 produces
fcs0 P1-I1/Q1 FC Adapter
Part Number.................00P2995
EC Level....................A
Serial Number...............1D2360CD0C
Manufacturer................001D
Feature Code/Marketing ID...2765
FRU Number.................. 00P2996
Network Address.............10000000C92EC946
ROS Level and ID............02C03891
Device Specific.(Z0)........2002606D
Device Specific.(Z1)........00000000
Device Specific.(Z2)........00000000
Device Specific.(Z3)........02000909
Device Specific.(Z4)........FF401050
Device Specific.(Z5)........02C03891
Device Specific.(Z6)........06433891
Device Specific.(Z7)........07433891
Device Specific.(Z8)........20000000C92EC946
Device Specific.(Z9)........CS3.82A1
Device Specific.(ZA)........C1D3.82A1
Device Specific.(ZB)........C2D3.82A1
Device Specific.(YL)........P1-I1/Q1
But the feature code is unfound in IBM ?? wierd
Anyone ever had problems like this before - i am seriously considering reverting to the older versions of the software if possible
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
There is a TSM server in which iam getting this error
Unable to read or write logical volume manager
record. PV may be permanently corrupted. Run diagnostics
how do i run the diagnostics??
any suggestions will really help.
Thanks!
karthik (1 Reply)
Discussion started by: karthikosu
1 Replies
2. UNIX for Advanced & Expert Users
Hi
We are running AIX5.3 on pseries 570. We have IBM ESS SAN stroage attached. We need to kick off flashcopy backups on the SAN. I have installed the CLI software but am missing a fileset. ibm2105esscli.rte or ibm2105cli.rte
This fileset contains the commands that can be issued from AIX to... (1 Reply)
Discussion started by: terrym
1 Replies
3. UNIX for Advanced & Expert Users
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (1 Reply)
Discussion started by: djdavies
1 Replies
4. AIX
Hi,
I have a strange problem. we're trying to connect an IBM pseries, to a Brocade switch, for SAN acess, using a badged emulex card, (IBM FC6239) WE can configure the device to see the fabric. The only problem we have is that the Brocade sees the HBA as storage, and not as a HBA.
We've zoned... (1 Reply)
Discussion started by: praxis22
1 Replies
5. AIX
Sorry for my english.
We have a IBM BLADES JS21. AIX 5.3 update to 6.
Our JS21 has 2 FC (fcs0 and fcs1).
We have one DS4072, one Disk system with 2 controllers and 2 FC by controllers.
This means, all AIX FC see all Disk systems controllers by 2 FC switchs. (one fc two roads)
FC AIX... (4 Replies)
Discussion started by: fjgonzalez
4 Replies
6. Shell Programming and Scripting
Hi,
when i am trying to FTP one file (test.txt) from Unix server to my local machine then i am getting the following error, as shown below
ftp> binary
200 Type set to I.
ftp> put C:\FTP\test.txt
C:FTPtest.txt: No such file or directory
ftp>
The red color text is the error.
Can... (3 Replies)
Discussion started by: sunitachoudhury
3 Replies
7. AIX
Hi folks.
We want to move a "physical" AIX box to a VIOed LPAR. The physical box is running SDD with disks from a DS8300. I want to be able to reattach those LUNs from the DS8300 to my VIO server which is running SDDPCM and then assigned them back to my AIX LPAR. Any thoughts about this?
I... (1 Reply)
Discussion started by: Stephan
1 Replies
8. AIX
I have sdd driver installed correctly but
when I run the command:
datapath query adapter
No device file found
what does it mean.. it is not using vpath or whats wrong? (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies
9. AIX
Hi
What are the steps to be followed when upgrading MQ version from 6 to 7 in aix server?
cbsdbprd01 # oslevel -s
5300-10-01-0921
cbsdbprd01 # lslpp -l | grep -i mq
mqm.base.runtime 6.0.2.1 COMMITTED WebSphere MQ Runtime for
mqm.base.samples 6.0.2.1 ... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
10. UNIX for Beginners Questions & Answers
What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL. (2 Replies)
Discussion started by: wibhore
2 Replies
LEARN ABOUT CENTOS
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.10 8 May 1997 devinfo(1M)