Sponsored Content
Operating Systems AIX Need Help with SDD / SDDPCM / MPIO Post 302973100 by sh_1580 on Saturday 14th of May 2016 08:30:36 AM
Old 05-14-2016
What is firmware level on Ds4300 ?
Please check compatible OS & multipath with that Firmware on IBM SSIC website.

Sent from my Le X507 using Tapatalk
 

10 More Discussions You Might Find Interesting

1. Solaris

IBM SDD on Sun

I just installed IBMsddsun64_........... on my sun server. I untarred it (tar xvf) & I tried to install the paxkage. When I did pkgadd -d ./IBMsdd..... I get a message Error, no packages were found. Any idea Thanks, (1 Reply)
Discussion started by: Remi
1 Replies

2. UNIX for Advanced & Expert Users

Help with SDD, SAN ESS and AIX 5.3 Host

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

3. Filesystems, Disks and Memory

SDD for SVC on HP-UX and LINUX

Hello Unix Admins: Has any one in this distribution list implemented SVC (SAN Volume Contoller - A solution from IBM) in your environment? If you have, do you have any do's / don'ts? Anything which you like sharing would be really appreciated. For example, my inputs: I tried implementing... (1 Reply)
Discussion started by: kdossjojo
1 Replies

4. AIX

SDD SDDPCM MPIO lspath Jargon

Can anyone recommend me some reading material surrounding how AIX handles LUNs: - with and without MPIO installed - with and without SDD or SDDPCM installed Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed? I guess... (0 Replies)
Discussion started by: apra143
0 Replies

5. Red Hat

IBM SDD driver

I was wondering if there is a way of auto-detecting a new vpath, using IBM's SDD driver, on a Linux platform. ON AIX it is a simple as running cfgmgr. Alan (0 Replies)
Discussion started by: alanp
0 Replies

6. AIX

AIX with SDD to VIOed SDDPCM?

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

7. AIX

AIX SDD

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

8. AIX

Upgrading from native MPIO to SDDPCM AIX 6.1

We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC. Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers. My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies

9. AIX

sddpcm on vio

I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO. On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Discussion started by: mk8570
4 Replies

10. AIX

hdisk status in sdd volume groups

hi all we recently upgraded our san switches. after that, i found i got many hdisks showing in lsdev with status "Defined" and "Available". the number of "Defined" is equal to "Available". the time stamp shows all "Available" disks created at our downtime night. "datapath query device"... (0 Replies)
Discussion started by: rs6000er
0 Replies
fwupgrade(8)						      System Manager's Manual						      fwupgrade(8)

NAME
fwupgrade - Updates the system firmware from a loadable firmware image (*.exe or *.sys) SYNOPSIS
/sbin/fwupgrade [-a] [-e] [-ignore] [-q] [-r] [-s] [-v] [-t CD-ROM_path] [-i path] /sbin/fwupgrade [-v] -f firmware_filename OPTIONS
Forces a firmware update without comparing the current firmware with the source firmware. Updates only if the current firmware is not equivalent to the source firmware. Specifies the path of the (*.exe or *.sys) firmware image. This is only used when you use a firmware image that is not on the distribution CD-ROM. For example, an image obtained from a web site download. You must ensure that the firmware image is the correct one for the target system, and verify that the image has the necessary support. This is indicated by bit1 and bit2 in the Flags column of the smmtable.txt file. Specifies the mount point of the target disk during an installation. This switch is to be used exclusively by the Tru64 UNIX install program. This switch suppresses error messages that are displayed if no firmware files are found on the distribution media, and causes the fwupgrade program to exit successfully. Does not upgrade the firmware, but displays information about the success of the desired operation. This enables you to to query fwupgrade to verify planned actions, such as ensuring whether the firmware really needs to be upgraded, or finding out if the target system supports a soft-reset. Resets the machine by software and reboots after the upgrade. The utility will exit with an error status if the system hardware does not support this feature. Sets silent mode, in which the firmware is upgraded without prompting you. If there is an error, the program also exits silently without prompting you. When this switch is used, you are not prompted for confirmation for the upgrade to proceed. Specifies the path of the mounted Firmware CD. If the -s option is not specified, you will be prompted to enter this path. Sets verbose mode, in which additional information is dis- played. DESCRIPTION
The fwupgrade command provides a means of updating the system firmware when a (*.exe or *.sys) loadable firmware update image is available. A firmware upgrade will shut down the system and require a full hardware reset. If the source firmware image does not support the loadable firmware update functionality, fwupgrade will exit with error status. The system must provide a SAVE_ENV callback that complies with the Alpha SRM. You can tell if the SAVE_ENV callback exists by executing the command: # consvar -a The SAVE_ENV is supported on the target system if the following message is displayed: Console environment variables saved If the SAVE_ENV is not supported on the target system, the following message is displayed: Failed to save environment variables Your programs can either check the return status of consvar -a or the return status of: setsysinfo(SSI_PROM_SAVE_ENV,...). See the setsysinfo(2) reference page for more information. EXIT STATUS
If you confirm that the firmware is to be upgraded, and no errors occur setting up the upgrade process, then fwupgrade will reboot the sys- tem rather than exit. An exception is that there is no reboot performed when the -i option is used. Instead, a status of 0 is returned. If you query whether the process would be successful, or if an upgrade request fails, the exit values are: Success. Firmware is adequate and supported. Failure. Firmware is not supported. Firmware needs to updated (when queried). EXAMPLES
To find out all information about your current firmware, platform, and the source firmware: # /sbin/fwupgrade -v -q Current Firmware: 4.10-0 Platform: 17-2-1091 Unable to open smmtable.txt at '/'. What is the mount point for the firmware CD? /mnt Firmware CD Version: 4.0 Distribution Firmware: 4.10-0 LFU File: /dev/rz2a at alpha1000/as1000_e4_v4_8.exe LFU Support: Y Soft Reset: Y System Firmware does not need to be upgraded To upgrade the firmware: # ./fwupgrade -t /mnt Current Firmware: 4.7-0 Are you sure that you wish to update the system firmware from 4.7-0 to 4.10-0?(yes/no)yes fwupgrade:Rebooting to update the system firmware... Terminated # syncing disks... done rebooting.... (transferring to monitor) FILES
The loadable firmware update images provided by Compaq. Typically, these are distributed on a firmware CD-ROM. If you obtain firmware images from a source other than the firmware CD-ROM (such as a www server) you should verify that they are the correct images for the tar- get system. A file provided with the firmware CD-ROM, used to determine the presence of the firmware CD-ROM and information about source firmware. SEE ALSO
Commands: consvar(8) Functions: setsysinfo(2) fwupgrade(8)
All times are GMT -4. The time now is 05:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy