Sponsored Content
Operating Systems AIX AIX - FC Switch migration, SAN Migration question! Post 302952703 by -=XrAy=- on Friday 21st of August 2015 04:48:48 AM
Old 08-21-2015
Hi,

you could try to make that device available with cfgmgr -l dac0.
If this not help you should validate the state of the parent devcie with lsparent -Cl dac0.

Regards
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

AIX Migration

Hi , Migrating AIX 4.3.3 ML10 to 5.3 ML1 (retaining 32 bit) after successfully going through 5 of the 5.3 Install CD's. After "All fileset's processed successfully " message I was told that system would reboot and then I would get prompted for setting TERm type ( i have an ascii ibm3151) and... (1 Reply)
Discussion started by: Student37
1 Replies

2. HP-UX

SAN migration

Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch. Any... (0 Replies)
Discussion started by: Hils
0 Replies

3. AIX

AIX 5.2 to 5.3 migration

Hello All, We want to upgrade our 44p Model 270 from AIX 5.2 to 5.3. This is a standalone devlopment server but downtime is something we don't want because we have a short development deadline looming. I have no tape drive to make backups to. I myself am a developer and don't have any... (4 Replies)
Discussion started by: Fred Vogel
4 Replies

4. AIX

IY17981 fix required for aix 4.3.3 to aix 5L migration but not found

Hi, redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages. - My system is ML11 : oslevel –r 4330-11 - But xlC.rte is on wrong version : lslpp -L xlC.rte xlC.rte ... (3 Replies)
Discussion started by: astjen
3 Replies

5. HP-UX

SAN Migration of HP-UX hosts

Hello gurus, I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place. Environment: Migrating from CX4 to VMAX - using OR/Hot Pull. Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies

6. Solaris

Need Help On Solaris Cluster Steps For San Migration

I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns. Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong) 1.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies

7. AIX

SAN Migration

Hi all, We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP. Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies

8. HP-UX

SAN Migration question

Hi, I am very new to HP-UX, and we're going to be doing a SAN migration. We're going to take down the machine, and zone it to the new SAN. My question is, will the device names change and will that interfere with the LVM? If the new disks come in with different device names, how would I... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

9. Red Hat

Volume group not activated at boot after SAN migration

I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies

10. Solaris

How to identify if disk is attached to SAN and assist in migration.?

I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX. it has one ldom created on it luxadm probe output --- No Network Array enclosures found in /dev/es Found Fibre Channel device(s): Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
sata(7D)							      Devices								  sata(7D)

NAME
sata - Solaris SATA framework DESCRIPTION
Serial ATA is an interconnect technology designed to replace parallel ATA technology. It is used to connect hard drives, optical drives, removable magnetic media devices and other peripherals to the host system. For complete information on Serial ATA technology, visit the Serial ATA web site at http://www.serialata.org. Up to 32 SATA devices may be plugged directly to each SATA HBA supported by the Solaris SATA framework. The actual number of pluggable devices my be lower, and is limited by a number of device ports on the SATA HBA. The maximum data rate is either 1.5Gb/sec. or 3.0Gb/sec., depending on the capability of a SATA device and SATA HBA controller. The Solaris SATA framework adheres to the Serial ATA 1.0a specification and supports SATA-2 signaling speed 3.0Gb/sec. SATA devices that are connected to SATA HBAs controlled by a SATA framework-compliant HBA driver are treated by the system as SCSI devices. The Solaris SCSI disk driver (sd(7D)) is attached as a target driver for each device node created by the SATA framework. You can use the cfgadm(1M) utility to manage hot plugged and unplugged SATA devices. FILES
/kernel/misc/sata 32-bit ELF kernel module (x86). /kernel/misc/amd64/sata 64-bit ELF kernel module (x86). ATTRIBUTES
See attributes(5) for descriptions of the following attribute: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWckr | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), prtconf(1M), cfgadm_sata(1M), attributes(5), ahci(7D), marvell88sx(7D), nv_sata(7D), sd(7D), si3124(7D) Serial ATA 1.0a Specification -- Serial ATA International Organization. Serial ATA II (Extension to Serial ATA 1.0.a.) -- Serial ATA International Organization. http://www.sun.com/io DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are presented in one of the following formats and are followed by the diagnostic message: sata: WARNING: <controller/devices/.. path>: or: sata: NOTICE: <controller/devices/.. path>: ...where <controller/devices/.. path> identifies a specific SATA HBA issuing a diagnostic message shown below. SATA port X: link lost. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost. SATA port X: link established. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been established. SATA port X: device reset. The device plugged to the specified SATA device port has been reset. The reset may be due to a communication or command error, command timeout, or an explicit request from the host. SATA port X failed. The specified SATA device port failed and is in an unusable state. You can change the port state by deactivating the port and activat- ing it again using cfgadm SATA hardware-specific commands (see cfgadm_sata(1M)). SATA port X error. An error was detected in specified SATA device port operations. SATA device detached at port X. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost and could not be re-established. The SATA framework assumes that the device is unplugged from the specified SATA device port. SATA device detected at port X. Communication( via serial link) between the HBA and the device plugged to the specified empty SATA device port has been established. The SATA framework assumes that the new device is plugged to the specified SATA device port. SATA disk device at port X. This message is followed by a disk description specifying the disk vendor, serial number, firmware revision number and the disk capa- bilities. SATA CD/DVD (ATAPI) device at port X. This message is followed by a SATA CD/DVD description specifying the DVD vendor, serial number, firmware revision number and the DVD capabilities. SATA device at port X cannot be configured. Application(s) accessing previously attached device have to release it before newly inserted device can be made accessible. The port cannot be configured because there is application using the previous attached device, so the application must release it, then the newly inserted device can be configured. Application(s) accessing previously attached SATA device have to release it before newly inserted device can be made accessible. The target node remained and it belongs to a previously attached device. This happens when the file was open or the node was waiting for resources at the time the associated device was removed. Instruct event daemon to retry the cleanup later. sata: error recovery request for non-attached device at cport X. When error recovery is requested, the device is not yet attached. SATA device at port X will not be power-managed. When property "pm-capable" on the target device node setting fails, the SATA device won't be power-managed. SATA disk device at port X does not support LBA. The disk device plugged into specified SATA device port does not support LBA addressing and cannot be used. Cannot identify SATA device at port X - device will not be attached. IDENTIFY (PACKET) DEVICE data cannot be retrieved successfully after the device is attached to the SATA port. sata: <HBA driver name><instance number>:hba attached failed. The SATA HBA instance attach operation failed. This HBA instance cannot be configured and is not available. sata: invalid ATAPI cdb length<command cdb length>. The length of the command cdb is greater than that the device can support. sata: invalid sata_hba_tran version X for driver <HBA driver name>. The specified SATA HBA driver and the SATA framework are incompatible. The driver cannot attach and SATA HBAs controlled by this driver (and devices plugged to this SATA HBA ports) are not available. sata_hba_attach: cannot create SATA attachment point for port X. The specified SATA device port cannot be configured in the system and a device plugged to this port could not be not be configured and used. sata_create_target_node: cannot create target node for device at port X. The device target node for the device plugged to the specified SATA device port could not be created. As a result, the device cannot be configured and used. SunOS 5.11 5 Sep 2007 sata(7D)
All times are GMT -4. The time now is 01:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy