03-05-2020
Thanks for the suggestion.
I am expecting this setup, as the whole picture. Hope it makes sense.
One single interface (be it aggr or ipmp) with one IP will be presented to OVM (OV Manager) as host, as an IP with multiple VLAN tagged. After finishing the repository and other post-work, I should be create VM.
For example, I can get a request "create a Solaris-10 VM with 2 interfaces, one VLAN#2170 and one VLAN#2161". This interface will be visible on OVM Manager as bond0.
We have more than 20 VLANs, so don't want to configure 20 IPs for each VLAN. Ideally, all those VLANs should be tagged on this single interface. Any suggestion, how can I achieve it?
Please ask, if I am not able to explain it well.
9 More Discussions You Might Find Interesting
1. Solaris
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (2 Replies)
Discussion started by: hcclnoodles
2 Replies
2. UNIX for Advanced & Expert Users
Hi there
I have a requirement to provide failover to our customer boxes in case of interface / switch failure, I have been looking at Solaris Link Aggregation with LACP and I wanted to ask a question
Ive seen multiple websites that say the following
Does this also mean that if the... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
3. AIX
Hi,
I need to setup a hacmp cluster (my first one, we usually use VCS on AIX), but I require more network bandwith than a normal gigabit etherchannel setup can provide, so I am thinking about using linkaggregation - 2 active adapters to one switch and a single backup adapter to another switch... (4 Replies)
Discussion started by: zxmaus
4 Replies
4. Solaris
Me again :)
I'm trying to find a page describing the L2, L3 und L4 modes of dladm.
It's nice to read "hashed by ip header", but how should I use that?
On the file-server it's ok to have the six interfaces serving six clients each on it's own. But an rsync connection via switch between two... (8 Replies)
Discussion started by: PatrickBaer
8 Replies
5. IP Networking
Hello,
I've been using mode 4 with four slaves, however looking at ifconfig showed that the traffic was not balanced correctly between the interfaces, the outgoing traffic has been alot higher on the last slave.
Example:
eth0 RX 123.2 GiB TX 22.5 GiB
eth1 RX 84.8 GiB TX 8.3 GiB
eth2... (3 Replies)
Discussion started by: TehOne
3 Replies
6. Solaris
Hi All, I am trying to aggregate the NIC's,(igb2 and igb3) (igb0 is used by the physical system and igb1 is used by primary-vsw0) to create the domains on that for faster data transfer, I followed the process for creating the aggregation, dladm create-aggr -d igb2 -d igb3 1
after creating the... (2 Replies)
Discussion started by: buildscm
2 Replies
7. Solaris
I have setup link aggregation with 3 interfaces on my solaris 10 system.
All looks good but my problem is that the traffic is only going out bge0 and not the other 2 links.
bash-4.3# dladm show-aggr -s
key:33 ipackets rbytes opackets obytes %ipkts %opkts
... (3 Replies)
Discussion started by: primeaup
3 Replies
8. IP Networking
Hi
ihave three link of internet and iwant to put one linux front of a firewall that this three linux speard firewall such az load balance and fialover but dont close any port and protocol and only firewall have been internet what way can i use for it ?
are there any script and services do that... (0 Replies)
Discussion started by: mnnn
0 Replies
9. Solaris
Hi,
This is Solaris-10 x86 platform.
I am not able to ping gateway associated with aggr50001. I am not getting idea, where could be issue. Please advise.
# netstat -nr
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
--------------------... (10 Replies)
Discussion started by: solaris_1977
10 Replies
LEARN ABOUT FREEBSD
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 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