01-14-2008
Fibre Cards
What kind of systems are you putting these cards in? What type of storage device are you using? There may be some specific software necessary for your disks.
Normally there is no issue with the install. Where things can get exciting is in the zoning and allocation of resources on the SAN device.
Good luck.
Shawn
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi there, I'm a newbie so please be patient. I wanted to know if it was possible to run X server on a box w/o a video card. The reason I want to do this is I'd like to have a CDE session from sun workstation into the AIX box. Please let me know if this is feasible. Thanks for your time. (5 Replies)
Discussion started by: blah00000
5 Replies
2. Solaris
Hi,
After I installed Solaris 10 in the Intel platform (chipset 865*) network card was not detected, were shall I get this driver? iam new to Solaris. (2 Replies)
Discussion started by: pravin_2929
2 Replies
3. Debian
I've had no luck with help on linuxquestions so I figured I'd try here. I'm using debian etch.
The problem is that I can not install my network card because it says:
Makefile:62: *** Linux kernel source not found. Stop.
I have the kernel-headers installed.
I've looked all over the... (9 Replies)
Discussion started by: Virtuality
9 Replies
4. AIX
Want to configure IBM raid strorage but the aix 5L cds do not have the drivers for the fibre channels. The machine is RS/6000. I have gone to IBM downlaodable sites but i can't find the drivers? help pliz:mad: (4 Replies)
Discussion started by: Zim-Aix-Guru
4 Replies
5. Solaris
Hi all
i would like to ask some suggests about my next job!
I have to install a new Sun Netra T5220, with an additional internal StorageTek SAS HBA Raid.
The problem come in if every disk is now controlled by the HBA, how can I install the OS?
No disk is being detected by the OS.
SAS card... (2 Replies)
Discussion started by: kakabobo
2 Replies
6. UNIX for Dummies Questions & Answers
Hey guys,
Sorry, this question might look stupid but I have no idea how to install a network card.
My server is a Dell PowerEdge T105 with Debian 5.0 Lenny.
My network card is a Broadcom NetXtreme BCM5722 Gigabit Ethernet PCI Express.
I've plugged the card innside my server and I can see... (2 Replies)
Discussion started by: chebarbudo
2 Replies
7. War Stories
Hi Folks,
A couple of years ago we had to replace the core switches between two of our data centres, a simple task for the most part - these new switches would be state of the art Cisco Catalyst units.
The link between the two sites was a dark fibre, with 8Gb bandwidth running full duplex... (9 Replies)
Discussion started by: gull04
9 Replies
8. AIX
Hello,
Just a quick question
Usually from a PSERIES if you want to connect to IBM SAN Storage
you connect the IBM SAN Storage through a SAN Switch
something like this
---
however my question
Can you connect
from Pseries directly to San Storage without SAN Switch
what would be... (8 Replies)
Discussion started by: filosophizer
8 Replies
9. AIX
Hello all,
Let me introduce about the context and my environment.
We have an AIX 6.1 system, it has 4 FC channels
/ > lsdev -Cc adapter | grep fcs
fcs0 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs1 Available 23-T1 Virtual Fibre Channel Client Adapter
fcs2 Available 23-T1... (14 Replies)
Discussion started by: Phat
14 Replies
LEARN ABOUT OPENSOLARIS
did
did(7) Sun Cluster Device and Network Interfaces did(7)
NAME
did - user configurable disk id driver
DESCRIPTION
Note -
Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software
still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor-
mation about the object-oriented command set, see the Intro(1CL) man page.
Disk ID (DID) is a user configurable pseudo device driver that provides access to underlying disk, tape, and CDROM devices. When the
device supports unique device ids, multiple paths to a device are determined according to the device id of the device. Even if multiple
paths are available with the same device id, only one DID name is given to the actual device.
In a clustered environment, a particular physical device will have the same DID name regardless of its connectivity to more than one host
or controller. This, however, is only true of devices that support a global unique device identifier such as physical disks.
DID maintains parallel directories for each type of device that it manages under /dev/did. The devices in these directories behave the same
as their non-DID counterparts. This includes maintaining slices for disk and CDROM devices as well as names for different tape device
behaviors. Both raw and block device access is also supported for disks by means of /dev/did/rdsk and /dev/did/rdsk.
At any point in time, I/O is only supported down one path to the device. No multipathing support is currently available through DID.
Before a DID device can be used, it must first be initialized by means of the scdidadm(1M) command.
IOCTLS
The DID driver maintains an admin node as well as nodes for each DID device minor.
No user ioctls are supported by the admin node.
The DKIOCINFO ioctl is supported when called against the DID device nodes such as /dev/did/rdsk/d0s2.
All other ioctls are passed directly to the driver below.
FILES
/dev/did/dsk/dnsm block disk or CDROM device, where n is the device number and m is the slice number
/dev/did/rdsk/dnsm raw disk or CDROM device, where n is the device number and m is the slice number
/dev/did/rmt/n tape device , where n is the device number
/dev/did/admin administrative device
/kernel/drv/did driver module
/kernel/drv/did.conf driver configuration file
/etc/did.conf scdidadm configuration file for non-clustered systems
Cluster Configuration Repository (CCscdidadm(1M) maintains configuration in the CCR for clustered systems
SEE ALSO
devfsadm(1M), Intro(1CL), cldevice(1CL), scdidadm(1M)
NOTES
DID creates names for devices in groups, in order to decrease the overhead during device hot-plug. For disks, device names are created in
/dev/did/dsk and /dev/did/rdsk in groups of 100 disks at a time. For tapes, device names are created in /dev/did/rmt in groups of 10
tapes at a time. If more devices are added to the cluster than are handled by the current names, another group will be created.
Sun Cluster 3.2 24 April 2001 did(7)