04-18-2007
I highly recommend you get a SAN Engineer that knows what they are doing. I f you have SAN support with IBM *CALL THEM*. they are smart enough not to take you beyond what they are capable.
I believe they let you have one support call at purchase that they will let you keep open for 30 days.
If don't have support pay the T&M to IBM. Even if it costs a couple thousand it may be worth it.
This is not much, but a SAN Engineer upgraded our ESS sdd and host attachment scripts over a year ago. The pool of disks were at that time viewable by all of 4 AIX systems, but the disks weren't carved on all 4 systems. At any rate, the vpath #s did change after our upgrade. From what I understood they where expected to change. The LUN IDs are what is important. Be careful.
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 REDHAT
kbdrate
KBDRATE(8) Linux Programmer's Manual KBDRATE(8)
NAME
kbdrate - reset the keyboard repeat rate and delay time
SYNOPSIS
kbdrate [ -s ] [ -r rate ] [ -d delay ]
DESCRIPTION
kbdrate is used to change the keyboard repeat rate and delay time. The delay is the amount of time that a key must be depressed before it
will start to repeat.
Using kbdrate without any options will reset the repeat rate to 10.9 characters per second (cps) and the delay to 250 milliseconds (ms) for
Intel- and M68K-based systems. These are the IBM defaults. On SPARC-based systems it will reset the repeat rate to 20 cps and the delay to
200 ms.
OPTIONS
-s Silent. No messages are printed.
-r rate
Change the keyboard repeat rate to rate cps. For Intel-based systems, the allowable range is from 2.0 to 30.0 cps. Only certain,
specific values are possible, and the program will select the nearest possible value to the one specified. The possible values are
given, in characters per second, as follows: 2.0, 2.1, 2.3, 2.5, 2.7, 3.0, 3.3, 3.7, 4.0, 4.3, 4.6, 5.0, 5.5, 6.0, 6.7, 7.5, 8.0,
8.6, 9.2, 10.0, 10.9, 12.0, 13.3, 15.0, 16.0, 17.1, 18.5, 20.0, 21.8, 24.0, 26.7, 30.0. For SPARC-based systems, the allowable
range is from 0 (no repeat) to 50 cps.
-d delay
Change the delay to delay milliseconds. For Intel-based systems, the allowable range is from 250 to 1000 ms, in 250 ms steps. For
SPARC systems, possible values are between 10 ms and 1440 ms, in 10 ms steps.
-V Display a version number and exit.
BUGS
Not all keyboards support all rates.
Not all keyboards have the rates mapped in the same way.
Setting the repeat rate on the Gateway AnyKey keyboard does not work. If someone with a Gateway figures out how to program the keyboard,
please send mail to util-linux@math.uio.no.
All this is very architecture dependent. Nowadays kbdrate first tries the KDKBDREP and KIOCSRATE ioctls. (The former usually works on an
m68k machine, the latter for SPARC.) When these ioctls fail an ioport interface as on i386 is assumed.
FILES
/etc/rc.local
/dev/port
/dev/kbd
Linux 1.1.19 22 June 1994 KBDRATE(8)