10 More Discussions You Might Find Interesting
I have some concerns over the disk management of my AIX system.
For example server1
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c vg_2 active
hdisk2 00c1cc14d6de272b ... (6 Replies)
Discussion started by: Phat
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
# oslevel -s
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
In general terms what are the differences platform driver,codec driver and Machine driver? (1 Reply)
Discussion started by: rupeshkp728
we are planning to deploy some of our databases on AIX/LPAR based servers (we didn't bought it yet ...). IBM's engineers says that if we want to boot them from SAN the hardware array has to be compatible with MPIO but they don't want to deliver any document with list of arrays supported... (5 Replies)
Discussion started by: andy55
5. UNIX for Dummies Questions & Answers
Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes.
Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
I was trying to uninstall the native MPIO driver on the AIX 6.1 machine we have in our lab and ran into a whole bunch dependent filesets initially. I deleted the disks, fcsX, fscsiX, fcnetX and tried again, but ran into the same error.
Subsequently, I figured out that the OS disks in... (4 Replies)
Discussion started by: ronykris
does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr
is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
10. UNIX for Advanced & Expert Users
We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
MFI(4) BSD Kernel Interfaces Manual MFI(4)
mfi -- LSI MegaRAID SAS driver
To compile this driver into the kernel, place the following lines in your kernel configuration file:
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
This driver is for LSI's next generation PCI Express SAS RAID controllers. Access to RAID arrays (logical disks) from this driver is pro-
vided via /dev/mfid? device nodes. A simple management interface is also provided on a per-controller basis via the /dev/mfi? device node.
The mfi name is derived from the phrase "MegaRAID Firmware Interface", which is substantially different than the old "MegaRAID" interface and
thus requires a new driver. Older SCSI and SATA MegaRAID cards are supported by amr(4) and will not work with this driver.
Two sysctls are provided to tune the mfi driver's behavior when a request is made to remove a mounted volume. By default the driver will
disallow any requests to remove a mounted volume. If the sysctl dev.mfi.%d.delete_busy_volumes is set to 1, then the driver will allow
mounted volumes to be removed.
A tunable is provided to adjust the mfi driver's behaviour when attaching to a card. By default the driver will attach to all known cards
with high probe priority. If the tunable hw.mfi.mrsas_enable is set to 1, then the driver will reduce its probe priority to allow mrsas to
attach to the card instead of mfi.
The mfi driver supports the following hardware:
o LSI MegaRAID SAS 1078
o LSI MegaRAID SAS 8408E
o LSI MegaRAID SAS 8480E
o LSI MegaRAID SAS 9240
o LSI MegaRAID SAS 9260
o Dell PERC5
o Dell PERC6
o IBM ServeRAID M1015 SAS/SATA
o IBM ServeRAID M1115 SAS/SATA
o IBM ServeRAID M5015 SAS/SATA
o IBM ServeRAID M5110 SAS/SATA
o IBM ServeRAID-MR10i
o Intel RAID Controller SRCSAS18E
o Intel RAID Controller SROMBSAS18E
/dev/mfid? array/logical disk interface
/dev/mfi? management interface
mfid%d: Unable to delete busy device An attempt was made to remove a mounted volume.
amr(4), pci(4), mfiutil(8)
The mfi driver first appeared in FreeBSD 6.1.
The mfi driver and this manual page were written by Scott Long <scottl@FreeBSD.org>.
The driver does not support big-endian architectures at this time.
July 15, 2013 BSD