Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: AIX LPAR FC connection to SAN
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

LEARN ABOUT SUSE

tgt-admin

TGT-ADMIN(8)						      TGT Configuration Tool						      TGT-ADMIN(8)

NAME

       tgt-admin - Linux SCSI Target Configuration Tool.

SYNOPSIS

       tgt-admin -[OPTION]...

DESCRIPTION

       tgt-admin is a utility which allows a persistent configuration of targets and luns.
       It uses tgtadm commands to create, delete and show targets.

OPTIONS

       -e, --execute

       read /etc/tgt/targets.conf and execute tgtadm commands.
       if target already exists it will be deleted and a new instance will be created with the new parameters instead.

       -d, --delete

       delete all the targets

       -s, --show

       show all the targets

       -f, --force

       don't exit on tgtadm errors

       -p, --pretend

       only print tgtadm options

       -v, --verbose

       increase verbosity (no effect in "pretend" mode)

       -c, --conf <conf_file>

       specify an alternative configuration file instead of /etc/tgt/target.conf, which is the default.

       -h, --help

       display a list of available options and exits

CONFIGURATION FILE SYNTAX

       The defualt configuration file is: /etc/tgt/target.conf. It defines all the targets and their properties.
       The  configuration  file is in XML format and uses tags.  Configuration file contains several target blocks, where each block contains tar-
       get's proerties such as storage devices, initator ACL and authorization information. You can include other config files using:
       include /etc/tgt/xen/*.conf.

       There are 2 types of storage devices:

       backing-store - defines a virtual device on the target.

       direct-store  - defines a direct mapped device with the same properties as the physical device (such as VENDOR_ID , SERIAL_NUM, etc.)

       initiator-address - allows connections only from the specify IP address. defaults to ALL if no "initiator-address" is specified

       incominguser - define iscsi incoming authentication setting. if no "incominguser" is specified, it is not used.

       outgoinguser - define iscsi outgoing authentication setting. if no "outgoinguser" is specified, it is not used.

       example for a configuration file:
       <target iqn.2007-04.com.example:san.monitoring>
	  backing-store /dev/san/monitoring

	  # if no "incominguser" is specified, it is not used
	  incominguser backup secretpass12

	  # defaults to ALL if no "initiator-address" is specified
	  initiator-address 192.168.1.2 </target>

       <target iqn.2007-02.com.example:san.xen1>
	  backing-store /dev/san/xen1-disk1 # LUN1
	  direct-store /dev/san/xen1-disk2 # LUN2

	  initiator-address 192.168.1.2     # Allowed IP
	  initiator-address 192.168.5.6     # Allowed IP

	  incominguser user1 secretpass12
	  incominguser user2 secretpass23

	  outgoinguser userA secretpassA </target>

       <target iqn.2007-02.com.example:san.xen2>
	  backing-store /dev/san/xen2 </target>

       <target iqn.2007-06.com.example:san.vmware1>
	  backing-store /dev/san/vmware1 </target>

FILES

       /etc/tgt/target.conf
	      Configuration file for tgt-admin.

SEE ALSO

       tgtadm(8)

REPORTING BUGS

       Report bugs to <stgt-devel@lists.berlios.de>

TGT Configuration Tool						    2008-07-21							      TGT-ADMIN(8)
All times are GMT -4. The time now is 06:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy