11-01-2008
I got this SDD related info on my AIX box
lslpp -l | grep -i sdd
devices.sdd.52.rte 1.6.0.2 APPLIED IBM Subsystem Device Driver
devices.sdd.52.rte 1.6.0.2 APPLIED IBM Subsystem Device Driver
Shockneck..
"Basic SDD commands are hd2vp (to create vpath devices from hdisks) vp2hd (to remove the vpath device) and dpovgfix (if the vpath configuration got messed up). "
I am unable to find these commands in my box... any comments on this
I got the following info from one of my colleague's
AIX 4.3 to 5.2 ...the san disk naming convension is vpath.....later version ie 5.3......it will show as hdisk
Is that the case
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone have an idea what this means? hdisk10 is part of vg1. (vg1 has 11 hdisks)
I get this msg every morning @ 5:04 CST
This is the orignal message:
A PROBLEM WAS DETECTED ON Fri Aug 17 03:02:09 PDT 2001 801014
The Service Request Number(s)/Probable Cause or... (2 Replies)
Discussion started by: Optimus_P
2 Replies
2. AIX
Is there a simply way for me to map a vpath to an hdisk on AIX 5.2? (5 Replies)
Discussion started by: 2dumb
5 Replies
3. AIX
Hi,
in an environment with svc's and ds8xxx wat disk algorithm should be used and what is the difference here:
I can set the algorithm to Load_balance and to Round_robin (see output below).
some info:
hdisk3 ******** MPIO FC 2145
devices.sddpcm.53.rte 2.2.0.0 COMMITTED ... (1 Reply)
Discussion started by: raba
1 Replies
4. AIX
May I know how can I add a new SSA pdisk into array and become usable hdisk? I have inserted a 36GB SSA disk into enclosure and done the "cfgmgr" and I can see it already been regconized as pdisk47.
I would like to make it a system disk in order for me to add to my volume group. Please let me... (3 Replies)
Discussion started by: kwliew999
3 Replies
5. AIX
How do you create a dummy hdisk with AIX 6.1? In previous versions, I've used this and works, but now I get this error.
hostname:/:# mkdev -l hdisk57 -c disk -t osdisk -s scsi -p fscsi0 -w 0,10 -d
Method error (/etc/methods/define):
0514-022 The specified connection is not valid.
Any... (2 Replies)
Discussion started by: kah00na
2 Replies
6. AIX
Hi all,
I'm getting some errors on AIX regarding Flashcopy and volume group hard disks.
The script that activates flashcopy showed this errors:
Recreating Flashcopy for lun01_A1
Performing syntax check...
Syntax check complete.
Executing script...
Script execution complete.
SMcli... (1 Reply)
Discussion started by: enux
1 Replies
7. AIX
I know the lv name (i.e. dprod_0000017).
#lslv dprod_0000017
LOGICAL VOLUME: dprod_0000017 VOLUME GROUP: prod01vg
LV IDENTIFIER: 00cb337d00004c0000000111d8566a5a.69 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: ... (2 Replies)
Discussion started by: Daniel Gate
2 Replies
8. AIX
Hi. I found an issue with my appvg present in my server.my server is a single node and not part of hacmp.
pmut3# lspv
hdisk0 00c5c9cf92ebb96a rootvg active
hdisk1 00c5c9cfcf30eee9 appvg
hdisk2 00c5c9cfcf30ef98 ... (5 Replies)
Discussion started by: newtoaixos
5 Replies
9. Shell Programming and Scripting
Hi,
Planning to implement script to fetch whether the hdisks are in proper sequence. Need output for incorrect sequence
Correct
#lspv
hdisk0
hdisk1
hdisk2
::::::::::::
hdisk5
Incorrect sequence
#lspv
hdisk0
hdisk6
hdisk7
hdisk10
Any idea pls share (2 Replies)
Discussion started by: ksgnathan
2 Replies
10. AIX
Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies
socal(7D) Devices socal(7D)
NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver
SYNOPSIS
socal@sbus-slot,0
DESCRIPTION
The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface
can connect to a Fibre Channel Arbitrated Loop (FC-AL).
The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL.
FILES
/kernel/drv/socal ELF Kernel Module
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO
sbus(4), sf(7D), ssd(7D)
Writing Device Drivers
ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH)
ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL)
Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA)
DIAGNOSTICS
The messages described below may appear on system console in addition to being logged.
On the console, these messages are preceded by:
socal%d: port %a
where %d is the instance number of the socal controller and %a is the port on the host adapter.
Fibre Channel Loop is ONLINE
The Fibre Channel loop is now online.
Fibre Channel Loop is OFFLINE
The Fibre Channel loop is now offline.
attach failed: device in slave-only slot.
Move soc+ card to another slot.
attach failed: bad soft state.
Driver did not attach, devices will be inaccessible.
attach failed: unable to alloc xport struct.
Driver did not attach, devices will be inaccessible.
attach failed: unable to map eeprom
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map XRAM
Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to map registers
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access status register
Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to install interrupt handler
Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to access host adapter XRAM
Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: unable to write host adapter XRAM
Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
attach failed: read/write mismatch in XRAM
Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible.
SunOS 5.10 9 May 1997 socal(7D)