06-13-2009
Quick Questions:
1) I have two virtual ethernet adapters on my VIO_Server.. Can I create more than one SEA for One Physical Ethernet Adapter
for ENT0
mkvdev -sea ent0 -vadapter ent2 -default ent2 -defaultid 1
en4
then again with a different VLAN ID
mkvdev -sea ent0 -vadapter ent3 -default ent3 -defaultid 2
en5
2) Can I create etherchannel for my physical ports on VIO Server
ENT0 + ENT1 = ENT2
and create SEA for this ENT2 ?
thanks
9 More Discussions You Might Find Interesting
1. AIX
Hi,
I define 2 new LV on the vio server and run a cfgmgr on the partition and see my 2 new hdisk (hdisk6 and hdisk7).
I extend my vg vg000 (on the partition) and add the 2 hdisks.
I had a filesystem on the vg000 and when I added the disk I would like to increase the filesystem. But I cannot do a... (0 Replies)
Discussion started by: touny
0 Replies
2. UNIX for Advanced & Expert Users
I understand that one should setup virtual ethernet adapters in the lpars which is the best way for various lpars to communicate with each other - Does anyone have info on this or can point me to a doc that explains how to set this up? (1 Reply)
Discussion started by: capeme
1 Replies
3. AIX
We're using VIO (not an HMC) to manage our LPAR's We have 3 physical adapters and 4 LPARs. Through the VIO interface we assigned 2 virtual interfaces but require a 3rd interface assigned to these LPARs. I am experiencing issues understanding exactly how to create another virtual adapter, either... (1 Reply)
Discussion started by: scottsl
1 Replies
4. AIX
Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR.
How can I do it without rebooting the LPARS.
POWER6 with HMC
LPARS = AIX 6.1
Any info
developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ...
But... (5 Replies)
Discussion started by: filosophizer
5 Replies
5. AIX
Lucky me, someone has installed a server and got it running with the best intentions, but leaving me a headache. :wall:
We have a simple p520 with 4 disks. 2x145Gb & 2x300Gb. The smaller disk pair have been built into a VIO mirrored rootvg, and quite right too.
The other two disks form a... (3 Replies)
Discussion started by: rbatte1
3 Replies
6. AIX
All
I am trying allocate an IVE to an LPAR (not a VIO) running AIX 7.1. I am getting the error:
HSCL068A
Explanation
Logical port can not be assigned to Logical Partition because this Logical Partition is not the promiscuous LPAR for the physical port.
Has anyone encountered this... (1 Reply)
Discussion started by: johnf
1 Replies
7. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
8. AIX
Hi,
I just successfully build a Virtual Machine in virtual box with Perfectly running HMC v7. I have a IBM eServer pSeries Model 630 Model 6C4 (Power 4) i.e. 7024-6C4. I am not able to have it connect to the HMC console on the Virtual Box.
Can anyone help me on how to connect it to the... (8 Replies)
Discussion started by: uzair_rock
8 Replies
9. AIX
I have a broken PV in a VIO VG that's used to support client LPARs using LVs. On the client LPAR, I reduced all PVs from the relevant client VG and thus deleted it. I.e. there is no client LPAR using the VIO VG. Yet when I try to reducevg the VIO VG, it complains that the LV hosted on the PV is... (2 Replies)
Discussion started by: maraixadm
2 Replies
LEARN ABOUT DEBIAN
fipvlan
FIPVLAN(8) Open-FCoE Tools FIPVLAN(8)
NAME
fipvlan - Fibre Channel over Ethernet VLAN Discovery
SYNOPSIS
fipvlan [-c|--create] [-s|--start] interfaces
fipvlan -a|--auto [-c|--create] [-d|--debug] [-s|--start] [-l|--link-retry <num>]
fipvlan -h|--help
fipvlan -v|--version
DESCRIPTION
The fipvlan command performs Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) VLAN Discovery over Ethernet interfaces.
fipvlan can be used as a diagnostic tool to determine which VLANs have FCoE services available on a network, prior to configuring VLAN
interfaces and the Open-FCoE initiator. fipvlan can also be used to create VLAN interfaces as they are discovered, and to start the
Open-FCoE initiator. The --create and --start options are primarily intended to be used as part of an Open-FCoE boot solution. FCoE
instances started in this way cannot be destroyed or reset by fcoeadm.
fipvlan takes a list of network interface names to run the VLAN discovery protocol over, or the --auto option to use all available Ethernet
interfaces.
fipvlan will enable any interface which is found to be not enabled by the time the program runs. If no response is received on that
interface it will be shutdown again when fipvlan terminates.
OPTIONS
-a, --auto
Use all Ethernet interfaces currently available
-c, --create
Create network interfaces for discovered FCoE VLANs. If a VLAN device already exists for a discovered VLAN, a new VLAN device will not
be created.
-d, --debug
Enable debugging output
-s, --start
Start the Open-FCoE initiator on discovered FCoE VLANs
-f, --suffix <suffix string>
Append the specified string <suffix string> to VLAN interface names.
-l, --link-retry <number of retries>
Retry check for link up up to <number of retries> times. The link state is retried every 500 ms. The default is 20.
-h, --help
Display a help message with basic usage instructions
-v, --version
Display the fipvlan version string
VLAN NAMING CONVENTIONS
The default VLAN device name is dev.vlan; where dev is the name of the Ethernet parent device and vlan is the discovered VLAN ID number. An
optional suffix can be appended to this with -f commandline option.
EXAMPLES
Display all discoverable VLANs with FCoE services
fipvlan --auto
Discover FCoE VLANs on interface eth2, create VLAN devices and start the Open-FCoE initiator
fipvlan --create --start eth2
In this example if FCoE services were available on VLAN 101 of network interface eth2, then a VLAN interface eth2.101-fcoe would be created
and used as the parent device for the initiator.
SEE ALSO
fcoeadm(8) fcoemon(8)
SUPPORT
fipvlan is part of the fcoe-utils package, maintained through the Open-FCoE project. Resources for both developers and users can be found
at the Open-FCoE website http://open-fcoe.org/
Open-FCoE 10/06/2011 FIPVLAN(8)