01-23-2008
the answer ....
ensure your system is at the correct OS level
determine mpio or datapath devices
SAN configuration and hardware to be determined.
install drivers
shut down the box
install the card
cable up
turn server on
configure san
run cfgmgr
in a nutshell .....
unless someone else has any other tips ....
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 OSF1
cfgmgr_set_status
cfgmgr_set_status(9r) cfgmgr_set_status(9r)
NAME
cfgmgr_set_status - General: Reports failure to the cfgmgr framework
SYNOPSIS
int cfgmgr_set_status(
char *driver_name );
ARGUMENTS
Specifies the name of the device driver for which you want to report an associated failure. This name is a string that matches the string
you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the driver name
(followed by a colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product
installation.
DESCRIPTION
The cfgmgr_set_status routine reports to the cfgmgr framework that a failure has occurred during static configuration. If the specified
device driver is in the static configuration state, it does not know that the configuration operation is complete until all register call-
back requests (routines) have successfully completed. Therefore, a device driver calls cfgmgr_set_status to report a possible failure dur-
ing static configuration to the cfgmgr framework.
Specifically, cfgmgr_set_status performs the following failure operations: Adjusts the state of the specified device driver Unconfigures
the specified device driver from the cfgmgr framework
The cfgmgr_set_status routine calls the device driver's configure routine at its CFG_OP_UNCONFIGURE entry point as part of these failure
operations. The code associated with the CFG_OP_UNCONFIGURE entry point is responsible for determining how to deallocate any allocated
resources during these failure operations.
The cfgmgr_set_status routine does not notify the operator of a configuration failure. Part of the code associated with the CFG_OP_UNCON-
FIGURE entry point could include an error logging operation to record the fact that a failure has occurred. The reason for doing this is
that the cfgmgr framework's task is to accomplish the unconfigure operation of a statically configured device driver.
You call the cfgmgr_set_status routine in the device driver's callback routine when the static configuration operation fails. You register
a callback routine by calling the register_callback routine.
RETURN VALUES
Upon successful completion, cfgmgr_set_status returns the value ESUCCESS. This success value indicates that cfgmgr_set_status adjusted the
state of the device driver and caused the cfgmgr framework to unconfigure the driver. Otherwise, cfgmgr_set_status returns one of the fol-
lowing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified
in the driver_name argument does not exist. In this case, cfgmgr_set_status cannot adjust the state and unconfigure the device driver. The
device driver that you specified in the driver_name argument was not statically configured. The device driver that you specified in the
driver_name argument is not in the static configuration state.
EXAMPLES
See Writing Device Drivers: Tutorial for a code example of the cfgmgr_set_status interface.
SEE ALSO
Routines: cfgmgr_get_state(9r), register_callback(9r)
cfgmgr_set_status(9r)