Sponsored Content
Operating Systems AIX AIX LPAR FC connection to SAN Post 303031503 by bakunin on Friday 1st of March 2019 11:28:21 AM
Old 03-01-2019
Quote:
Originally Posted by Phat
In the HMC profile, I can see there are 3 physical FC assigned to the server as attached.

I also see 6 FC ports which is equivalent from 3x2=6
Exactly. Look at the "location codes" which i have marked bold:

Code:
[root@zzz] / > lsdev -Cc adapter | grep fcs
fcs0 Available 00-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs1 Available 00-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs2 Available 01-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs3 Available 01-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs4 Available 05-00 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)
fcs5 Available 05-01 8Gb PCI Express Dual Port FC Adapter (df1000f114108a03)

fcs0 and fcs1 are port 0 and 1 from the same adapter, etc. for the others. In the HMC display you posted you see the "real" (physical) location codes where the adapters are located in the system. I.e. one adapter is located in the CEC with serial number 9K83854 in slot P1-C5.

Quote:
Originally Posted by Phat
Can we say the "physical" FC adapter here are actually the real physical FC adapter from Power Machine which are assigned to the lpar not via VIOS (with virtual FC adapter) ?
Yes, absolutely. The reason for the VIOS is this: you have some "anonymous" resources like memory and CPUs which you can easily transfer between LPARs. You cannot do this with adapters, obviously, because they are connected to something and they are configured on the "outside" too. Neither you can do that with disks because they contain data which makes them the opposite of "anonymous". Therefore there is the VIOS, which takes all the physical ressources, creates virtual constructs representing these and then gives these constructs to the LPAR. This way you can move an LPAR from on managed system to the other because VIOSes ahve special means to transfer the physical layer between one another and for the LPAR the virtual construct it uses never changes - just the way it is representing some physical ressource.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

p6 570 network for AIX LPAR

know how to do it. (3 Replies)
Discussion started by: rainbow_bean
3 Replies

2. AIX

VIO SAN STORAGE LPAR ( Dynamically increasing size )

Hi, Is there a way to dynamically increase the size of virtual disk on the LPAR. The virtual disk is coming from my VIO Server. From my SAN I have allocated a disk to VIO Server and from VIO Server to my LPAR....If I increase the space of the logical SAN DISK (DS 4700 using IBM TotalStorage... (0 Replies)
Discussion started by: filosophizer
0 Replies

3. AIX

How to Find if AIX machine is LPar or not

Hi, I want to know if there is any command which will tell me if an AIX machine is a LPar or not. I am using "lparstat -i" but it does not work on all AIX machines. Is there any generic command by whose output I will come to know if it is an LPar or not? Please help. Thanks, Vineet (3 Replies)
Discussion started by: vineetd
3 Replies

4. AIX

p595 LPAR no longer sees SAN boot disk

Hello, we have a wierd and urgent problem, with a few of our p595 LPARs running AIX 5.3. The LPARs ran AIX 5.3 TL 7 and booted off EMC SAN disks, using EMC Powerpath. Every boot we run "pprootdev on" and "pprootdev fix". We can issue "bosboot -a" and we can reboot the machines. Now, on two... (2 Replies)
Discussion started by: rwesterik
2 Replies

5. Solaris

SAN connection - configuring fibre attached hard drive

Hi All, I recently got a connection to the SAN through a fibre channel on my solaris box: #luxadm -e port /devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:devctl CONNECTED #ls -l /dev/cfg lrwxrwxrwx 1 root root 48 Feb 23 12:31 c4 -> ../../devices/pci@1d,700000/SUNW,qlc@1/fp@0,0:fc I then... (2 Replies)
Discussion started by: dede
2 Replies

6. AIX

AIX admin - lpar question

Hi Guru, my question is that can I create LPAR in AIX 5.3, 6.0, 6.1 by using smit lpar, rather than using HMC or AIX Commands? Thank you very much. Mir Alihttp://xwww.unix.com/images/icons/icon5.gif (3 Replies)
Discussion started by: Tahniet
3 Replies

7. AIX

How to check the LPAR in a AIX box ?

I have login into a server, and when i launch this command uname -L. I can see there is a LPAR. But is there anymore commands i can use to get more information on the LPAR ? like it is VIO ? wat the IP address ? etc, etc. please help. Thank you. (7 Replies)
Discussion started by: wingcross
7 Replies

8. AIX

AIX 5.2.0 on own hardware -> i550 LPAR

We are running into a problem that we thought had solved but no go... We have multiple machine types but 1 AIX and 2 i550 (AS/400) with 4 lpar each. Existing AIX is an old (2004 vintage) machine with 5.2 on it for historical use only. Existing Power6 i550 running code that will used... (6 Replies)
Discussion started by: jackb_guppy
6 Replies

9. AIX

Will it affect my AIX LPAR security, when i set up email alerts on AIX server.

Hello, I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior. for example 1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert. 2) disk usage alerts 3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies

10. UNIX for Beginners Questions & Answers

AIX - SAN Mount and Unmount on LPAR

We have 2 LPAR. LPAR #1 have a Application, Database Server process (ctree Server) and SAN+Physical Table. LPAR#2 has only Application. Both Application process are connected to Database via C-tree Server Process (Running on LPAR #1.. We want to keep one Active C-tree Server and one Backup... (1 Reply)
Discussion started by: gabhanes
1 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 07:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy