Visit Our UNIX and Linux User Community

Full Discussion: AIX MPIO and EMC
Top Forums UNIX for Advanced & Expert Users AIX MPIO and EMC Post 302096623 by kmilberg on Thursday 16th of November 2006 05:52:48 PM
Old 11-16-2006
Just wondering if you have an answer, we have the same issue.
Test Your Knowledge in Computers #239
Difficulty: Easy
In March 1970, the ARPANET reached the East Coast of the United States, when an IMP at the Department of Energy in Washington, DC was connected to the network.
True or False?

10 More Discussions You Might Find Interesting

1. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

2. AIX

AIX 5.3 MPIO vs RDAC on DS4000 range

Hi I would like to ask what the benefits are of changing from RDAC to MPIO when connecting to a DS4000 on AIX 5.3? I have heard that IBM MPIO "might" support more than 1 active path to a LUN when connecting to a DS4800 through more than 1 host connection on the same AIX client. I understand that... (8 Replies)
Discussion started by: kimyo
8 Replies

3. AIX

AIX native MPIO

Hi folks, 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
3 Replies

4. AIX

Need EMC Symmetrix driver for AIX 5.3

Hi all, I hope I'm putting my first post at this site into the right forum. I need help finding the EMC disk driver for AIX version 5.3. I have some new EMC disk presented to a backup server of mine, and right now the EMC hdisks show up looking like this in an lsdev: hdisk495 Available... (2 Replies)
Discussion started by: C.J.Hund
2 Replies

5. AIX

Uninstall native MPIO driver on AIX

Hi, 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
4 Replies

6. 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

7. AIX

AIX Sanboot from EMC Symmetrix with NPIV

Hi All.. On to a new implementation with AIX 7.1 san boot from EMC disks (Using NPIV). Anyone played with this recently? Wondering if we need PowerPath on the AIX clients or has native MPIO matured to replace it. Thoughts? Thanks Mr B (6 Replies)
Discussion started by: balaji_prk
6 Replies

8. AIX

AIX Migration issue with EMC ODM sets

Hi Experts , I want to start migrating our AIX 6.1 to AIX 7.1 . I am planning to use alt_disk_migration . Chris gibson has awesome documentation in the internet. However I am running into an issue with EMC odm filesets . So my current OS is AIX 6.1. and I have this : lslpp -l | grep EMC ... (7 Replies)
Discussion started by: JME2015
7 Replies

9. AIX

AIX help -reconnect EMC lun

we have an old AIX system with important data on an EMC LUN. the AIX server crashed and we had to rebuild it with the old AIX os 5.8. how do we reconnect the EMC LUN without losing the data? (15 Replies)
Discussion started by: jhudson12
15 Replies

10. AIX

issue AIX MPIO path closed

Hello, I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system / > lspv hdisk0 00fa6d1288c820aa rootvg active hdisk1 00fa6d1288c8213c None hdisk2 ... (9 Replies)
Discussion started by: Phat
9 Replies
intrbald(1M)															      intrbald(1M)

intrbald - daemon for balancing interrupts SYNOPSIS
interval | DESCRIPTION
Balancing interrupts is a process which distributes interrupts across the available CPUs in an optimal fashion. This action is performed by (see intctl(1M)). Performing frequent CPU migrations between system partitions may require you to perform periodic balancing of interrupts. This is espe- cially true with systems that use WLM (Workload Manager), iCAP (Instant Capacity), and vPars (Virtual Partitions) products. If the fre- quency of CPU migration is high, then balancing of interrupts should be performed more frequently. The daemon monitors the system for imbalance in interrupt distribution. If an imbalance is detected after the specified interval executes to balance the interrupt distribution. uses the parameters from the configuration file for balancing the interrupts. For more information about the command, see intctl(1M) and the configuration file. The daemon is started from the general purpose sequencer script (see rc(1M)), at run level 2 and is killed at run level 1. By default, the daemon is not enabled. The daemon configuration file must be edited and the parameter set to in order to enable running the daemon. After setting to for the first time, you can start the daemon manually by executing the script Otherwise, the daemon will automatically start the next time the system is restarted. Any actions performed by the daemon are logged in and details of interrupt migrations performed will be logged in the file Options recognizes the following options: Instructs the running daemon to reexamine the configuration file If the parameter has been updated, then the running daemon uses the new value. If the parameter is set to then the running daemon stops executing. The daemon checks if the system requires any balancing of interrupts after interval seconds; the valid range is 5 seconds to seconds (see limits(5)). This value can also be specified persistently in the configuration file by setting the parameter. The default value is 60 seconds. Setting this value too small can cause unnecessary interrupt migrations. Gracefully kills the running daemon. intrbald rc Configuration File is the configuration file. The following parameters can be persistently specified in this configuration file: Specifies if the daemon should be started automatically during the system bootup process by the script. The daemon will only be started automatically if this parameter is set to NOTE: This value is by default. Before using the daemon, needs to be changed to in the file. Then the daemon needs to be started, either manually by running or it will be started automatically at next boot via the script. The daemon checks if the system requires any interrupt balancing after this interval. The interval is specified in seconds; the valid range is 5 seconds to seconds (see lim- its(5)). The default is 60 seconds. Setting this value too small could cause unnecessary interrupt migrations. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. WARNINGS
The command can be executed only by the superuser. This command should be used only by performance analysts for performance tuning pur- poses. If the interrupts are not redistributed properly, a possible decrease in overall system performance can occur. Some processors can become overloaded while other processors will not be optimally utilized. FILES
configuration file. See the section above. script. start symbolic link. kill symbolic link. daemon log file. SEE ALSO
intctl(1M), ioscan(1M), rc(1M), limits(5). intrbald(1M)

Featured Tech Videos

All times are GMT -4. The time now is 09:39 PM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy