I have some unclear about how VIOS uses its resources.
Assume that VIOS lpar has only 1 physical FC, and we use that to connect to the Lun. Then we install VIOS for the lpar on that Lun.
So my question is, afterward, we can still use that physical FC for the virtual FC we create later?
This can be same mechanism with virtual ethernet?
I have 1 physical ethernet assigned to vios, and configure IP on that, everything is fine until I tried to map another virtual ethernet to it and got the issue below:
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 2
Adapter ent0 has an interface configured over it, or it belongs to another SEA, VLAN or EtherChannel
Command did not complete.
All of these mean that we have to use another physical device (FC, ethernet) for virtual devices??
On the VIOS, don't allocate an IP address to the adapter
configure the SEA, then create virtual adapter on the vios and add the IP to the virtual adapter.
For the fibre, are you saying you are booting the VIOS from SAN? No internal disks on the frame that you could use instead?
How many client VMs are you going to serve with the VIOS - will you have another VIOS on the same frame for redundancy ?
Then, on AIX lpar (vio client) create new virtual ethernet. Then use smitty tcpip to configure the IP.
I can end up pinging the aix lpar
Regarding your question, this frame is no longer used in prod, so I took it as my test machine with few lpar and 1 VIOS only.
I have internal disks(SAS). But I wonder, if I have only 1 physical FC connected with LUN, Could I reuse it also for another virtual FCs to connect to other Lun? or I need another physical FC to do that?
you can connect your fibre adapter to as many VMs as you want - you just need to configure the amount of virtuals you will probably need in the profile of the vios and then you just map
