10 More Discussions You Might Find Interesting
1. AIX
Hello,
In my environment, I have 2 VIOS. There is 1 lpar uses the first VIOS. Now we would like to move it to second VIOS.
My question is, can we migrate the virtual FC on the lpar to second VIOS?
If not, we have to create new virtual FC on second VIOS and map it to the lpar. This also... (3 Replies)
Discussion started by: Phat
3 Replies
2. AIX
Hi,
$ ioslevel
2.2.4.10
I always get these errors when I perform any action using the web interface of IVM / VIOS
Shutdown Partitions Help
You have chosen to shutdown the following partitions. The recommended shutdown method is to use the client operating systems shutdown... (1 Reply)
Discussion started by: filosophizer
1 Replies
3. AIX
I have 4 VIO server. I have to take backup of VIOS. I got the command "backupios" for taking the backup.
My question is if i am taking "backupios -tape /dev/rmt0 " whether it will take rootvg and all the user defined VG / File system which are using for virtual disk for client lpar.
I... (4 Replies)
Discussion started by: sunnybee
4 Replies
4. AIX
Few questions regarding Power HA ( previously known as HACMP) and VIOS POWERVM IVM ( IBM Virtualization I/O Server )
Is it possible to create HACMP cluster between two VIOS servers
Physical Machine_1
VIOS_SERVER_1
LPAR_1
SHARED_DISK_XX
VIOS_SERVER_2
Physical Machine_2
LPAR_2... (6 Replies)
Discussion started by: filosophizer
6 Replies
5. AIX
Hi, I would like to ask you if you could help me to answer these questions. Please.
How to check in vios, size all pv's and to what they are mapped to?
How to chech on vios/hmc which PowerVM edition is used?
Thank you. (7 Replies)
Discussion started by: phobus
7 Replies
6. AIX
Dear friends.. Will it be OK if I backup VIO Server Using smit mksysb?? will it save all virtual host mapings etc...??? thanks in advance (3 Replies)
Discussion started by: Vit0_Corleone
3 Replies
7. AIX
Can anybody provide me with usefull links to get knowledge how VIOS works and how to configure Lpars on it? I am tired and feel lazy to search through IBM redbooks :-) .. so pls help me :p (3 Replies)
Discussion started by: wwwzviadi
3 Replies
8. AIX
I would like to hear your opinions, comments, pros and cons about the IVE (Integrated virtual ethernet) and VIOS (virtual i/o server)
With the VIOS can create virtual ethernet and virtual disk
With the IVE I dont need to create the vios and I can have virtual ethernet (physical and logical... (3 Replies)
Discussion started by: lo-lp-kl
3 Replies
9. AIX
Hello, I'm having troubles running scripts on the VIOS. I want to run a simple script like:
lsmap -all | grep vhost
I've created the file with just like this:
$ cat script1.sh
lsmap -all | grep vhost
When I run the script, it returns the following error message:
script1.sh:... (5 Replies)
Discussion started by: enzote
5 Replies
10. AIX
hi,
i tried to mount using
$ mount nimsrv01:/export/mksysb_dev/VDEVVIO1 /mksysb
in vios mode.
i got following error..
</code>
Some error messages may contain invalid information
for the Virtual I/O Server environment.
mount: 1831-008 giving up on:... (1 Reply)
Discussion started by: honeym210
1 Replies
VLAN(4) BSD Kernel Interfaces Manual VLAN(4)
NAME
vlan -- IEEE 802.1Q VLAN network interface
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device vlan
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_vlan_load="YES"
DESCRIPTION
The vlan driver demultiplexes frames tagged according to the IEEE 802.1Q standard into logical vlan network interfaces, which allows rout-
ing/bridging between multiple VLANs through a single switch trunk port.
Each vlan interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using the
cloned_interfaces variable in rc.conf(5).
To function, a vlan interface must be assigned a parent interface and numeric VLAN tag using ifconfig(8). A single parent can be assigned to
multiple vlan interfaces provided they have different tags. The parent interface is likely to be an Ethernet card connected to a properly
configured switch port. The VLAN tag should match one of those set up in the switched network.
vlan initially assumes the same minimum length for tagged and untagged frames. This mode is selected by setting the sysctl(8) variable
net.link.vlan.soft_pad to 0 (default). However, there are network devices that fail to adjust frame length when it falls below the allowed
minimum due to untagging. Such devices should be able to interoperate with vlan after changing the value of net.link.vlan.soft_pad to 1. In
the latter mode, vlan will pad short frames before tagging them so that their length is not less than the minimum value after untagging by
the non-compliant devices.
HARDWARE
The vlan driver supports efficient operation over parent interfaces that can provide help in processing VLANs. Such interfaces are automati-
cally recognized by their capabilities. Depending on the level of sophistication found in a physical interface, it may do full VLAN process-
ing or just be able to receive and transmit long frames (up to 1522 bytes including an Ethernet header and FCS). The capabilities may be
user-controlled by the respective parameters to ifconfig(8), vlanhwtag, and vlanmtu. However, a physical interface is not obliged to react
to them: It may have either capability enabled permanently without a way to turn it off. The whole issue is very specific to a particular
device and its driver.
At present, these devices are capable of full VLAN processing in hardware: ae(4), age(4), alc(4), ale(4), bce(4), bge(4), bxe(4), cxgb(4),
cxgbe(4), em(4), igb(4), ixgb(4), ixgbe(4), jme(4), msk(4), mxge(4), nxge(4), nge(4), re(4), sge(4), stge(4), ti(4), txp(4), and vge(4).
Other Ethernet interfaces can run VLANs using software emulation in the vlan driver. However, some lack the capability of transmitting and
receiving long frames. Assigning such an interface as the parent to vlan will result in a reduced MTU on the corresponding vlan interfaces.
In the modern Internet, this is likely to cause tcp(4) connectivity problems due to massive, inadequate icmp(4) filtering that breaks the
Path MTU Discovery mechanism.
These interfaces natively support long frames for vlan: axe(4), bfe(4), cas(4), dc(4), et(4), fwe(4), fxp(4), gem(4), hme(4), le(4), nfe(4),
rl(4), sf(4), sis(4), sk(4), ste(4), tl(4), tx(4), vr(4), vte(4), and xl(4).
The vlan driver automatically recognizes devices that natively support long frames for vlan use and calculates the appropriate frame MTU
based on the capabilities of the parent interface. Some other interfaces not listed above may handle long frames, but they do not advertise
this ability. The MTU setting on vlan can be corrected manually if used in conjunction with such a parent interface.
SEE ALSO
ifconfig(8), sysctl(8)
BUGS
No 802.1Q features except VLAN tagging are implemented.
BSD
June 4, 2012 BSD