I've been given an IP address to assign to an ldom that is in a different subnet than the host, and I am looking for assistance in getting it online. I believe I need "VLAN tagging" as found in this link, but I do not understand all of the terminology.
My host machine is on subnet 10.25.112.x, and I have ldoms on the same subnet that are online and working properly. My new ldom has an IP address on the subnet 10.26.63.x.
host LDOM same subnet LDOM different subnet
I don't fully understand the example they give in this link. In my situation is the 112 subnet the untagged VLAN?
Hope someone can help here.....
I'm looking for some websites with info on VAX/VMS. I've tried google, yahoo and other search engines, but to no avail.
Am I looking in the correct place?? :confused: (5 Replies)
Hi
I'm using a Linux machine (CENTOS 5) to ftp a file from a VMS Alpha box (i hardly know anything about these machines). All seems to be working upto the point where it states the transfer has started but it just hangs...
ftp> get SPOOL.28
local: SPOOL.28 remote: SPOOL.28
200 Port 228.87... (2 Replies)
Hi All,
I'm trying to configure a vlan interface, to do this I'm using the following command "vconfig add eth0 20". I have my interface up and running, but when I test it using "ping -I eth0.20 192.168.1.1" and in other console use "tcpdump -i eth0.20" I can not see any tagged frame.
... (0 Replies)
I have 1 AIX server, 4 dual ported fiber attached ethernet cards and 4 VLANS coming in. Is it possible to present those 8 ports as 1 IP address using etherchannel? Thanks. (5 Replies)
All
I am a VMS guy just learning UNIX.
My first task is to SFTP files from VMS to UNIX in BATCHMODE without having to enter a password. Note that using SFTP interactively works just fine.
I have followed some specific instructions provided by a vendor with no success. I have also read... (0 Replies)
Hi Gurus,
Can anyone explain me what is a Vlan and a Native vlan. How to check the native Vlan on my server having a solaris10 OS.
Thanks in advance.:) (2 Replies)
Hello,
I am looking into HP-UX 11.31 VMs and I had a few questions.
We own two systems with 11.31 installed on them:
HP 9000 rp3440 (RISC)
- 2gb memory
- 2 processors
HP Integrity rx2660 (Itanium)
- 8gb memory
- 4 processors
Looking at the memory requirements in the Integrity VM... (4 Replies)
Hey everyone. I work in a data center, and I'm working on getting my CCNA. Now when I read articles on the idea of VLAN's it makes sense. Especially if you have multiple switches daisy chained in multiple locations. My two main questions though are that most of these examples use PC's as examples... (2 Replies)
In a "typical" data centre environment (telco, financial services etc), would a Linux OS typically have one IP address connected to one VLAN or would it have many IPs and/or VLANs. I say "Linux OS" as I'm referring to an instance of the OS not necessarily a Host or server. Think Linux OS = VM in a... (9 Replies)
Discussion started by: PCB
9 Replies
LEARN ABOUT DEBIAN
if_vlan
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 lines 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.
Initially vlan assumes the same minimum length for tagged and untagged frames. This mode is selected by the sysctl(8) variable
net.link.vlan.soft_pad set to 0 (default). However, there are network devices that fail to adjust frame length, should it fall 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 stays 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.
By now, the list of physical interfaces able of full VLAN processing in the hardware is limited to the following devices: ae(4), age(4),
alc(4), ale(4), bce(4), bge(4), cxgb(4), em(4), ixgb(4), jme(4), msk(4), nge(4), re(4), sge(4), stge(4), ti(4), txp(4), and vge(4).
The rest of the Ethernet interfaces can run VLANs using software emulation in the vlan driver. However, some of them 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.
The following interfaces support long frames for vlan natively: bfe(4), cas(4), dc(4), fwe(4), fxp(4), gem(4), hme(4), le(4), nfe(4), nve(4),
rl(4), sf(4), sis(4), sk(4), ste(4), tl(4), tx(4), vr(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 of theirs. 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 April 14, 2010 BSD