ifconfig for both machines is exactly the same other than of course the ip change. Here is one of the two
I guess my first question is when is an interface of type VLAN created for a LPAR; 'ent1' in my case? Since en1 and ent1 is missing on the new lpar I'm just trying to figure out what it means and when it gets created.
Just to be clear both LPARs have same virtual adapter configurations and hence I was expecting the same number of interfaces being visible in lsdev output.
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)
Hello all,
I want to add a new virtual interface on HP-UX B.11.11 U 9000/800 box.
I know that ifconfig can be used to add the Virtual interface.
BUt i do not know the exact syntax. it some times gives plumb error if i try to add
# ifconfig vif0 10.1.10.1 up
plumb error: No such file... (3 Replies)
Hello all,
I have configured a virtual interface using ifconfig on HP UX 11.11.
When i try to do traceroute with -i option i get * * * from traceroute.
i use $traceroute -i lan0:1 my-gateway
traceroute to my-gateway (15.70.180.1), 30 hops max, 40 byte packets
1 * * *
2 * * *
30 * *... (2 Replies)
How would i create virtual interface in linux to configure more than one IP address for a physical interface?
any help wll be appreciated.
https://www.unix.com/images/misc/progress.gif (1 Reply)
I just wondering if there are ways to open multiple virtual terminal to a single LPAR.
After I have use putty to login to the VIOS. I will use mkvt -id <LPAR id> to open console but if my friend want to open 2 second one, it will say, VT already connected.
IS there a way to work this around ? ... (1 Reply)
Hello, hopefully someone can help me out with this, I have created a virtual Ethernet adapter on the VIO but would like to add it to my new LPAR.
On my VIO only my disk is mapped.
$ lsmap -all
SVSA Physloc Client Partition ID
--------------- --------------------------------------------... (5 Replies)
Hi,
When i'am taking nmon report I am missing the LPAR tab that shows CPU and Shared CPU utilization.
My OS version is 6100-06-05-1115
Topas_nmon
Kindly suggest and help me to sort out this issue. (3 Replies)
Hello,
VIOS 2.2.1.4 using IVM.
I'm trying to extend a virtual disk assigned to a running lpar so that I can expand the lpar's datavg and grow some filesystems for the user.
Storage admin expanded the lun and new size was reflected in VIO right away. I then needed the storage pool to... (2 Replies)
Hello,
Is there a way to run
xclock
or
startx
on LPAR, since LPAR doesn't have any console or it is connected to HMC
usually the way is to export the display to some PC which has Xmanager running on it, but in my case, I want to run xmanager on the AIX Lpar and run on it the... (2 Replies)
Discussion started by: filosophizer
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)