Sponsored Content
Full Discussion: AIX: DLPAR VFC - HMC v9
Operating Systems AIX AIX: DLPAR VFC - HMC v9 Post 303030813 by aixkidbee on Saturday 16th of February 2019 10:08:02 AM
Old 02-16-2019
AIX: DLPAR VFC - HMC v9

Hey All,

I have running dual VIOS on a P9 systems, and just created a new LPAR profile. My objective is to create LPAR Client VFC adapters, and then DLPAR VFC Server adapters on the VIOS.


In the HMC v9 Enhanced GUI, I have DLPAR a VFC adapter to both VIOS, however, you can't specify the partner adapter to connect to? Why is that?


Also, when I use command line to DLPAR the VFC adapters using chhwres with the -s option, to specify the partner adapter when adding in the VFC adapters to a VIOS, it says that the VFC adapter with X value already has the X value partner adapter already associated with another adapter.
e.g In the VIOS profile, an existing Server Fibre Channel Adapter has Adapter ID 14 and Partner Adapter ID 11, and I want to DLPAR Server Fibre Channel Adapter Adapter ID 15 and Partner Adapter ID 11 (for another LPAR of course) and it won't allow.


Command:
Code:
chhwres -m xyz123 -r virtualio --rsubtype fc -o a -p VIOS_A  -a  "adapter_type=server,remote_lpar_name=xyz123,remote_slot_num=14" -s 11


Why is this failing? All existing Server Fibre Channel adapters in the VIOS profile all have obviously different Server Adapter IDs but all pointing to the same Partner Adapter IDs to their own LPAR clients.

Last edited by vbe; 02-16-2019 at 11:21 AM..
 

10 More Discussions You Might Find Interesting

1. AIX

AIX HMC LSCOD with space

I am trying to run the lscod command against an HMC that has managed system names with spaces. Tried enclosing the managed system names in quotes; single and double. How do I get the command to run? ssh hmcname lscod -m 'managed system 1' -t cap -r proc -c cuod Thanks, ~Donavon (0 Replies)
Discussion started by: djlerman
0 Replies

2. AIX

AIX and HMC installation issue

I started the AIX install with a fiber channel disk, and let it run: restricted by GSA ADP Schedule Contract with IBM Corp. . . . . . << End of copyright notice for perfagent.tools >>. . . . ... (2 Replies)
Discussion started by: Gideon1a
2 Replies

3. AIX

Virtualizing the Fiber card (VFC) on P595

Hi, We have a P595 machine with a dual port Fiber card per VIOs. We have two VIOs in the box. VIO1: ---> 2 port Fiber Card VIO2: ---> 2 port Fiber Card One port on each fiber card is utilized. Connected to SAN switches. We are getting all disks from SAN both for VIOs and LPARs. Now... (0 Replies)
Discussion started by: aixromeo
0 Replies

4. AIX

AIX HMC - Getting Colon ":" in output

Hi, I am executing below commands on HMC. I see that there is only colon ":" in output. Can someone please help why I am getting ":" in output? Why I am not getting proper output? xxxxx@yyyyhmc1:~> viosvrcmd -m PCC-p590#2-SN024D8F0 -p ppvio1 -c "lsmap -all" :xxxxx@yyyyhmc1:~> viosvrcmd... (0 Replies)
Discussion started by: marya
0 Replies

5. AIX

Upgrade AIX without HMC

Hi all, i would like to know if it's possible upgrade AIX 5.3 to 6.1 on a LPAR without use the HMC. so i would like to know if i must use the console to do it or i can do all from the up&running system on LPAR. Thanks in advance. Mario (4 Replies)
Discussion started by: Zio Bill
4 Replies

6. AIX

HMC - tracking dlpar

I am trying to generate a report to track dlpar operation performed on a MS and was wondering if anyone has done this before. I can get history from HMC using lssvcevents , but this does not give me details as to what quantity was added or removed . Any thoughts ? Thanks (3 Replies)
Discussion started by: mk8570
3 Replies

7. AIX

Install AIX lpar via hmc, can't access cd drive

Hi , I would like to access the cd drive of , i have power series server , and have lpars . I try to install AIX in an lpar via HMC, but it can't access the cd drive. how i can make installtion or make the the cd drive accessible in hmc or in power series server? Thanks in advance (2 Replies)
Discussion started by: prpkrk
2 Replies

8. AIX

Install AIX , do i need hmc console

Hi, For installing aix on power series , do i need to install hmc first? or i can connect hmc after? Rgs, (7 Replies)
Discussion started by: prpkrk
7 Replies

9. AIX

View IP of HMC from AIX

Trying to get the IP address of the HMC connected to some servers running AIX 6 and 7. I thought this would be as easy as running 'lsrsrc IBM.MCP IPAddresses', but when I run that command, the resource is empty. Is there some where else I should be looking, or is there a reason why this resource... (5 Replies)
Discussion started by: acascianelli
5 Replies

10. AIX

IBM VIOS AIX HMC Error

hello P6 was managed by HMC, tried to install on it VIOS 2.2.6 and got this error message Hosting requires a hosting partition -- boot not permitted vios-4 - imgbb.com then after creating an lpar in HMC got this message B2001230 vios-3 - imgbb.com anyone know how to solve this... (3 Replies)
Discussion started by: filosophizer
3 Replies
EM(4)							   BSD Kernel Interfaces Manual 						     EM(4)

NAME
em -- Intel(R) PRO/1000 Gigabit Ethernet adapter driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device em Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_em_load="YES" DESCRIPTION
The em driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 81572, 82573, and 82574 Ethernet controller chips. The driver supports Transmit/Receive checksum off- load and Jumbo Frames on all but 82542-based adapters. Furthermore it supports TCP segmentation offload (TSO) on all adapters but those based on the 82543, 82544 and 82547 controller chips. The identification LEDs of the adapters supported by the em driver can be controlled via the led(4) API for localization purposes. For further hardware information, see the README included with the driver. For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter. All hardware require- ments listed apply to use with FreeBSD. Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. This driver version supports VLANs. The em driver supports the following media types: autoselect Enables auto-negotiation for speed and duplex. 10baseT/UTP Sets 10Mbps operation. Use the mediaopt option to select full-duplex mode. 100baseTX Sets 100Mbps operation. Use the mediaopt option to select full-duplex mode. 1000baseSX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. 1000baseTX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. The em driver supports the following media options: full-duplex Forces full-duplex operation half-duplex Forces half-duplex operation. Only use mediaopt to set the driver to full-duplex. If mediaopt is not specified, the driver defaults to half-duplex. For more information on configuring this device, see ifconfig(8). HARDWARE
The em driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips: o Intel PRO/1000 CT Network Connection (82547) o Intel PRO/1000 F Server Adapter (82543) o Intel PRO/1000 Gigabit Server Adapter (82542) o Intel PRO/1000 GT Desktop Adapter (82541PI) o Intel PRO/1000 MF Dual Port Server Adapter (82546) o Intel PRO/1000 MF Server Adapter (82545) o Intel PRO/1000 MF Server Adapter (LX) (82545) o Intel PRO/1000 MT Desktop Adapter (82540) o Intel PRO/1000 MT Desktop Adapter (82541) o Intel PRO/1000 MT Dual Port Server Adapter (82546) o Intel PRO/1000 MT Quad Port Server Adapter (82546EB) o Intel PRO/1000 MT Server Adapter (82545) o Intel PRO/1000 PF Dual Port Server Adapter (82571) o Intel PRO/1000 PF Quad Port Server Adapter (82571) o Intel PRO/1000 PF Server Adapter (82572) o Intel PRO/1000 PT Desktop Adapter (82572) o Intel PRO/1000 PT Dual Port Server Adapter (82571) o Intel PRO/1000 PT Quad Port Server Adapter (82571) o Intel PRO/1000 PT Server Adapter (82572) o Intel PRO/1000 T Desktop Adapter (82544) o Intel PRO/1000 T Server Adapter (82543) o Intel PRO/1000 XF Server Adapter (82544) o Intel PRO/1000 XT Server Adapter (82544) LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.em.rxd Number of receive descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.txd Number of transmit descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.rx_int_delay This value delays the generation of receive interrupts in units of 1.024 microseconds. The default value is 0, since adapters may hang with this feature being enabled. hw.em.rx_abs_int_delay If hw.em.rx_int_delay is non-zero, this tunable limits the maximum delay in which a receive interrupt is generated. hw.em.tx_int_delay This value delays the generation of transmit interrupts in units of 1.024 microseconds. The default value is 64. hw.em.tx_abs_int_delay If hw.em.tx_int_delay is non-zero, this tunable limits the maximum delay in which a transmit interrupt is generated. DIAGNOSTICS
em%d: Unable to allocate bus resource: memory A fatal initialization error has occurred. em%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred. em%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection (cable). SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com. If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to <freebsdnic@mailbox.intel.com>. FILES
/dev/led/em* identification LED device nodes EXAMPLES
Make the identification LED of em0 blink: echo f2 > /dev/led/em0 Turn the identification LED of em0 off again: echo 0 > /dev/led/em0 SEE ALSO
altq(4), arp(4), igb(4), led(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8) HISTORY
The em device driver first appeared in FreeBSD 4.4. AUTHORS
The em driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>. BUGS
Hardware-assisted VLAN processing is disabled by default. You can enable it on an em interface using ifconfig(8). BSD
May 14, 2010 BSD
All times are GMT -4. The time now is 10:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy