My product have around 10-15 programs/services running in the sun box, which together completes a task, sequentially. Several instances of the each program/service are running in the unix box, to manage the load and for risk-management reasons. As of now, we dont follow a strict strategy in... (2 Replies)
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)
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)
Hi. I am IT manager/developer for a small organization. I have been doing as-needed linux server administration for several years and am by no means an expert. I've built several of my own servers, and our org is currently using hosting services for our servers and I am relatively happy.
We... (3 Replies)
On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem.
The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like
5.3 TL3 = IBM.MPIO 5.3.0.30
5.3... (0 Replies)
Dear Solaris Experts,
We are upgrading from sun4u to T4 systems and one proposal is to use LDOMs and also zones within LDOMs.
Someone advised using only zones and not LDOMs because the new machines have fewer chips and if a chip or a core fails then it doesn't impact the zones, but impacts... (3 Replies)
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Hello,
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
6 Replies
LEARN ABOUT NETBSD
cz
CZ(4) BSD Kernel Interfaces Manual CZ(4)NAME
cz -- Cyclades-Z series multi-port serial adapter device driver
SYNOPSIS
cz* at pci? dev ? function ?
DESCRIPTION
The cz device driver supports the Cyclades-Z series of multi-port serial adapters. The Cyclades-Z is an intelligent serial controller com-
prising:
o PLX9060ES PCI bus interface
o Xilinx XC5204 FPGA
o IDT R3052 MIPS CPU
The MIPS CPU runs firmware provided by the device driver. Communication with the MIPS is performed by modifying data structures located in
board local RAM or host RAM.
The Cyclades-Z comes in three basic flavors:
o Cyclades-8Zo rev. 1 -- This is an older 8-port board with no FPGA. The serial ports are provided by an octopus cable.
o Cyclades-8Zo rev. 2 -- This is the newer 8-port board. The serial ports are provided by an octopus cable.
o Cyclades-Ze -- This is the expandable version of the Cyclades-Z. It uses an HD-50 SCSI cable to connect the board to a 1U rack
mountable serial expansion box. Each box has 16 RJ45 serial ports, and up to 4 boxes may be chained together, for a total of 64
ports. Boxes 3 and 4 require their own external power supply, otherwise the firmware will refuse to start (as it cannot communi-
cate with the UARTs in those boxes).
The Cyclades-Z has several features to improve performance under high serial I/O load:
o The board may operate in interrupt-driven mode or polled mode to reduce interrupt load.
o Each channel has a large input and output buffer.
o Each channel may be programmed to generate an interrupt based on reception of a specific character, e.g. a PPP End-Of-Frame charac-
ter.
o The MIPS CPU on the board performs all flow-control handling.
FILES
/dev/ttyCZnnnn -- dial-in (normal) TTY device
/dev/dtyCZnnnn -- dial-out TTY device
SEE ALSO pci(4), termios(4), tty(4)HISTORY
The cz driver first appeared in NetBSD 1.5.
AUTHORS
The cz driver was written by Jason R. Thorpe <thorpej@zembu.com> and
Bill Studenmund <wrstuden@zembu.com> of Zembu Labs, Inc.
BUGS
The cz driver does not currently implement communication via host RAM. While this may improve performance by reducing the number of PCI mem-
ory space read/write cycles, it is not straightforward to implement with the current bus_dma(9) API.
Interrupt mode has not been tested.
There is no support for reading or writing the EEPROM connected to the PLX PCI bus controller.
BSD May 17, 2000 BSD