12-28-2011
Hi All..
Once plug out && plug in luns from storage to server connetivity...
10 More Discussions You Might Find Interesting
1. Solaris
Hello...I got a problem here. I have HBAs installed in one of the domains in E20 and I gotta find out the brand and firmware. But when I do a prtconf, I cannot see the HBA. For other servers installed with HBAs, when I do prtconf on them I can see either qlc or em. Can you guys enlighten me how to... (5 Replies)
Discussion started by: xiaochensg
5 Replies
2. Solaris
I have installed a qlogic HBA card in an E450 Solaris 9 with all the SUNW packages and the latest EPROM version. Configuration reboot was done. An orange light flashes to the right of where the card plugs into the fiber cable after booting, and the following error apprears at the start of the boot... (9 Replies)
Discussion started by: floydm
9 Replies
3. UNIX for Advanced & Expert Users
I have a V490 that has couple internal disks attached to the same dual-port HBA card that I'm planning attach to the SAN for additional storage.
Would I sacrifice performance if I use the same HBA?
Is it better to throw in a new HBA instead? (1 Reply)
Discussion started by: kiem
1 Replies
4. UNIX Desktop Questions & Answers
Does Red Hat Fedora support Nvidia card 8800GTX and 260 card?
Does any Linux OS support Nvidia card? (1 Reply)
Discussion started by: sito
1 Replies
5. AIX
Hi All,
SUN emulex HBA card has been installed on P520 box.
When i run the cfgmgr i am getting the following message.
lpar2#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for
device support but are not currently installed.... (0 Replies)
Discussion started by: b_manu78
0 Replies
6. Solaris
Hi All,
I'm actually trying to configure a Qlogic HBA on a solaris9 connecting in a Brocade SAN. I installed Solaris9 and now trying to look at FC devices..
bash-2.05# luxadm -e port
Found path to 0 HBA ports
bash-2.05# luxadm probe
No Network Array enclosures found in /dev/es... (7 Replies)
Discussion started by: ilan
7 Replies
7. Solaris
Hi,
i have a two port hba card in solaris 10 system one of which is disabled. How to enable and configure the other port.
---------- Post updated at 08:17 AM ---------- Previous update was at 03:40 AM ----------
please help :( (7 Replies)
Discussion started by: rishiraaz
7 Replies
8. Solaris
Hello,
I am very new to solaris so please bear with me. I have 2 machines in question. For both I am trying to get the HBA Card Hardware information such as:
HBA Model Name
HBA Firmware version
HBA Port details
HBA Driver details
First machine is a Solaris 10. When I execute fcinfo... (6 Replies)
Discussion started by: flagman5
6 Replies
9. Red Hat
Hi,
How to determine if HBA card in getting faulty from linux host ? any pointers. (2 Replies)
Discussion started by: saurabh84g
2 Replies
10. Solaris
Dear all,
I have a new Oracle Blade X4-2B server, running Solaris 10.
The server comes with a HBA card that will not be used now. It has not fibers connected to it. As a consequence, its leds never stop flashing.
My question is: how to disable this HBA card, without removing it physically... (2 Replies)
Discussion started by: Gus1971
2 Replies
LEARN ABOUT LINUX
picld_plugin_register
picld_plugin_register(3PICLTREE) PICL Plug-In Library Functions picld_plugin_register(3PICLTREE)
NAME
picld_plugin_register - register plug-in with the daemon
SYNOPSIS
cc [ flag... ] file... -lpicltree [ library... ]
#include <picltree.h>
int picld_plugin_register(picld_plugin_reg_t *regp);
DESCRIPTION
The picld_plugin_register() function is the function used by a plug-in module to register itself with the PICL daemon upon initialization.
The plug-in provides its name and the entry points of the initialization and cleanup routines in the regp argument.
typedef struct {
int version; /* PICLD_PLUGIN_VERSION */
int critical; /* is plug-in critical? */
char *name; /* name of the plugin module */
void (*plugin_init)(void); /* init/reinit function */
void (*plugin_fini)(void); /* fini/cleanup function */
} picld_plugin_reg_t;
The plug-in module also specifies whether it is a critical module for the proper system operation. The critical field in the registration
information is set to PICLD_PLUGIN_NON_CRITICAL by plug-in modules that are not critical to system operation, and is set to PICLD_PLUG-
IN_CRITICAL by plug-in modules that are critical to the system operation. An environment control plug-in module is an example for a
PICLD_PLUGIN_CRITICAL type of plug-in module.
The PICL daemon saves the information passed during registration in regp in the order in which the plug-ins registered.
Upon initialization, the PICL daemon invokes the plugin_init() routine of each of the registered plug-in modules in the order in which they
registered. In their plugin_init() routines, the plug-in modules collect the platform configuration data and add it to the PICL tree using
PICLTREE interfaces(3PICLTREE).
On reinitialization, the PICL daemon invokes the plugin_fini() routines of the registered plug-in modules in the reverse order of registra-
tion. Then, the plugin_init() entry points are invoked again in the order in which the plug-ins registered.
RETURN VALUES
Upon successful completion, 0 is returned. On failure, a negative value is returned.
ERRORS
PICL_NOTSUPPORTED Version not supported
PICL_FAILURE General system failure
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
libpicltree(3PICLTREE), attributes(5)
SunOS 5.10 19 Sep 2001 picld_plugin_register(3PICLTREE)