Sponsored Content
Operating Systems Solaris How to enable hba port of a two port hba card Post 302498515 by scorpionzoe on Monday 21st of February 2011 03:12:38 PM
Old 02-21-2011
Yes there is a useful command :

# cfgadm -a [to see the appropriate port to enable]
You can use the man to get the help but in all cases if the cards have been disabled you can enable'em:
# cfgadm -c connect name_of_port
# cfgadm -c configure name_of_port
The man pages in the top of the page, they are very useful for thorough details.
 

10 More Discussions You Might Find Interesting

1. Solaris

HBA Card

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

Need HBA card driver

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

3. IP Networking

4GB Dual Port HBA

I have one 4GB, dual port HBA. Is each port rated for 4GB, or is it the whole HBA rated for 4GB? Also, how do I determine which is port0 / port1 with "lscfg -vl fcs0" command. Thanks. (0 Replies)
Discussion started by: jwholey
0 Replies

4. Solaris

Solaris 10. fcinfo hba-port shows adapter not Found

I understand that fcinfo hba-port should show information(WWN, HBA vendor, etc..) but my result show "No adapter found". If I used grep -i 'version' /var/adm/messages* then I see my installed HBA (QLogic FCode at 2.00.09).. I am wondering why and what I had failed to install? Thanks in advance.... (23 Replies)
Discussion started by: Y4Net
23 Replies

5. Solaris

Few things related to HBA port & fcinfo command

Hi Gurus I need to know few things related to HBA port & fcinfo command I have a server where there are 4 HBA ports cards are their. Out of 4 ports 2 are in use & 2 are not in use when I check it physicall. Now I want to know the command through which I can get information about all above... (6 Replies)
Discussion started by: girish.batra
6 Replies

6. Solaris

How to enable Serial port on ILOM, when Network Port is enabled in parallel

Hi Everyone, In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies

7. Solaris

Which FC HBA card support Solaris9

I have JNI FCE-6460-N fc card , it is detected in OK prompt.....I connected Sun StorEDGE A5000 FC storage. in OK prompt, PROBE-SCSI-ALL showing A5000 fc hdds details in ok prompt..... but in OS level.....not showing the hdd, i tried in DEVFSADM command and FORMAT command not showing A5000... (3 Replies)
Discussion started by: anysystem
3 Replies

8. Red Hat

HBA card faulty

Hi, How to determine if HBA card in getting faulty from linux host ? any pointers. (2 Replies)
Discussion started by: saurabh84g
2 Replies

9. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies

10. Solaris

Solaris 10: how to disable an unused HBA card

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
cfgadm_ac(1M)						  System Administration Commands					     cfgadm_ac(1M)

NAME
cfgadm_ac - EXX00 memory system administration SYNOPSIS
/usr/sbin/cfgadm [-c configure] [-f] [-o disable-at-boot | enable-at-boot ] ac#:bank# ... /usr/sbin/cfgadm [-c unconfigure] [-o disable-at-bootp | enable-at-boot ] ac#:bank# ... /usr/sbin/cfgadm [-v] [-o quick | normal | extended, [max_errors=#] ] -t ac#:bank#... /usr/sbin/cfgadm -x relocate-test ac#:bank# ... /usr/sbin/cfgadm [-l] -o disable-at-boot | enable-at-boot ac#:bank# ... DESCRIPTION
The ac hardware specific library /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1 provides the functionality for configuring and unconfiguring memory banks on E6X00, E5X00, E4X00 and E3X00 systems as part of the Dynamic Reconfiguration of CPU/Memory boards using cfgadm_sysctrl(1M). Memory banks appear as attachment points in the device tree. For each CPU/Memory board, two attachment points are published, one for each bank on the board: bank0 and bank1. If the bank is unpopulated, the receptacle state is empty. If the bank is populated, the receptacle state is connected. The receptacle state of a memory bank can never be disconnected. The occupant state of a connected memory bank can be configured or unconfigured. If the occupant state is configured, the memory is in use by Solaris, if unconfigured it is not. OPTIONS
Refer to cfgadm(1M) for complete descriptions of the command options. The following options are supported: -c configure | unconfigure Change the occupant state. The configure argument ensures that the memory is initialized and adds the memory to the Solaris memory pool. The unconfigure argument removes the memory from use by Solaris. When a CPU/Memory board is to be removed from a system, both banks of memory must be unconfigured. cfgadm refuses the configure operation if the memory on the board is marked disabled-at-boot (see info field), unless either the -f (force) option or the enable at boot flag, (-o enable-at-boot), is given. The configure operation takes a short time proportional to the size of memory that must be initialized. cfgadm refuses the unconfigure operation if there is not enough uncommitted memory in the system (VM viability error) or if the bank to be unconfigured has memory that can't be removed (non-relocatable pages error). The presence of non-relocatable pages is indicated by the word permanent in the info listing field. Removing memory from use by Solaris may take a significant time due to factors such as system load and how much paging to secondary storage is required. The unconfigure operation can be cancelled at any time and the memory returned to the fully configured state by interrupting the command invocation with a signal. The unconfigure operation self-cancels if no memory can be removed within a timeout period. The default timeout period of 60 seconds can be changed using the -o timeout=# option, with a value of 0 disabling the timeout. -f Force option. Use this option to override the block on configuring a memory bank marked as disabled at boot in the non-volatile dis- abled-memory-list variable. See Platform Notes:Sun Enterprise 6x00/5x00/4x00/3x00 Systems -l List option. This option is supported as described in cfgadm(1M). The type field is always memory. The info field has the following information for empty banks: slot# empty The slot# indicates the system slot into which the CPU/Memory board is inserted. For example, if this were slot11 the attachment point for use with cfgadm to manipulate the associated board would be sysctrl0:slot11. The info field has the following information for connected banks: slot# sizeMb|sizeGb [(sizeMb|sizeGb used)] base 0x### [interleaved #-way] [disabled at boot] [permanent] The size of the bank is given in Mb or Gb as appropriate. If the memory is less than completely used, the used size is reported. The physical base address is given in hexadecimal. If the memory bank is interleaved with some other bank, the interleave factor is reported. If the memory on the board is disabled at boot using the non-volatile disabled-memory-list variable, this is reported. If the bank has memory that cannot be removed this is reported as permanent. -o disable-at-boot | enable-at-boot These options allow the state of the non-volatile disabled-memory-list variable to be modified. These options can be used in conjunc- tion with the issuing of a -c option or with the explicit or implied listing command, -l, if no command is required. Use of -o enable- at-boot with the configure command to override the block on configuring memory on a board in the disabled memory list. -o extended | normal | quick Use with the -t option to specify test level. The normal test level ensures that each memory cell stores both a 0 and a 1, and checks that all cells are separately addressable. The quick test level only does the 0s and 1s test, and typically misses address line problems. The extended test uses patterns to test for adjacent cell interference problems. The default test level is normal. See -t option. -o max_errors=# Use with the -t option to specify the maximum number of allowed errors. If not specified, a default of 32 is assumed. -o timeout=# Use with the unconfigure command to set the self-cancelling timeout. The default value is 60 and the unit is seconds. A value of 0 means no timeout. -t Test an unconfigured bank of memory. Specify the test level using the -o quick | normal | extended option. cfgadm exits with a 0 (success) if the test was able to run on the memory bank. The result of the test is available in the condition for the attachment point. -v Verbose option. Use this option in combination with the -t option to display detailed progress and results of tests. -x relocate-test For all pages of memory in use on the specified memory bank, a relocation operation as used in the unconfigure command is attempted. The success of this operation does not guarantee that the bank can be unconfigured. Failure indicates that it probably cannot be uncon- figured. This option is for test purposes only. OPERANDS
The following operand is supported: ac#:bank# The attachment points for memory banks are published by instances of the address controller (ac) driver (ac#). One instance of the ac driver is created for each system board, but only those instances associated with CPU/Memory boards publish the two bank attachment points, bank0 and bank1. This form conforms to the logical ap_id specification given in cfgadm(1M). The corresponding physical ap_ids are listed in the FILES section. The ac driver instance numbering has no relation to the slot number for the corresponding board. The full phys- ical attachment point identifier has the slot number incorporated into it as twice the slot number in hexadecimal directly following the fhc@ part. FILES
/devices/fhc@*,f8800000/ac@0,1000000:bank? attachment points /usr/platform/sun4u/lib/cfgadm/cfgadm_ac.so.1 hardware specific library file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm.u | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), cfgadm_sysctrl(1M), config_admin(3CFGADM), attributes(5) Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic Reconfiguration User's Guide Platform Notes:Sun Enterprise 6x00/5x00/4x00/3x00 Systems NOTES
Refer to the Sun Enterprise 6x00, 5x00, 4x00 and 3x00 Systems Dynamic Reconfiguration User's Guide for additional details regarding dynamic reconfiguration of EXX00 system CPU/Memory boards. SunOS 5.10 29 Sep 1999 cfgadm_ac(1M)
All times are GMT -4. The time now is 07:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy