Do not create vlan interface (dladm create-vlan ..).
Delete that interface.
If using VLAN tagging add the virtual switch in this manner :
Then add tagged interface into guest domain :
This way, tagging will be done by hypervisor vnet/vsw, not inside guest domain.
Guest domain will be in VLAN 503 exclusively.
Good practice would be to aggregate all four network ports into one aggr0 then use that for as net-dev.
You will get redundancy in case of failure, as well as combined bandwidth of 4 network ports.
Also, on that aggregated interface specify as many VLAN ids that are used in your environment when creating VSW.
The switch network ports should be configured as trunk.
Hi,
I have a question on web servers and network switches.
Why a network switch should support certificate management, that means generating public and private keys... installing a certificate etcetra.
Regards
Chaitanya. :b: (4 Replies)
I want to know potential problems with the following scenario OR if it is an ok way to have my network setup:
I have 2 WAN connections to the internet. I have each WAN connection plugged into its own router. Router DD-WRT is gateway for servers (192.0.10.50). Router Tomato is gateway for pc's... (1 Reply)
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Solaris for Sparc 11.1 with the latest patches. Created a Guest LDOM with two vnet's net0 and net1, installed a guest whole root, ip exclusive zone that I want to be able to utilize DHCP. I have been able to create the zone but unable to get it to boot because I am unable to assign an anet to it.... (4 Replies)
I have an Oracle VM set up with 1 virtual disk. I am trying to add 2 new disks to it. I was able to successfully add 1 (it appears when I run "format" in the VM) but when I add the second and third disks they do not appear in my VM.
Here are the commands I ran:
ldm add-vdsdev... (3 Replies)
Hi,
Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image.
Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch.
So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Hello Guys,
Can some help me with a configuration from 2x10g cards to 4 Ldoms and a Vlan configuration,
Solaris 11
dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net0 Ethernet up 1000 full ixgbe0
net1 Ethernet ... (2 Replies)
I'm really stuck here. I've created an LDOM on a SPARC T4-1 with Solaris 11.4 to run a copy of Linux for SPARC. I got the Linux ISO installed and Linux itself installed and booted OK. The only thing is is that there's no networking available in the Linux guest.
This question is basically the... (7 Replies)
I have a Sun T4-1 running Solaris 11.4 with a static IP 192.168.0.183. On this machine is a Solaris 10 LDOM with a static IP of 192.168.0.78. The other day I had to stop the LDOM to do a memory reconfigure. When I rebooted it I got an error that the IP 192.168.0.78 was already in use and so... (4 Replies)
Discussion started by: Michele31416
4 Replies
LEARN ABOUT DEBIAN
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