Solaris 11 link aggregation - not working - can't ping gateway
This link was helpful and I got the idea that vlanNUM would be created on OVM/hypervisor level.
I deleted VLAN interfaces, recreated aggr0 with net0 and net7. But I can't ping its gateway. I can see packets incoming from two VLANs, if I snoop on net0, net7 and aggr0.
Per network guys, their side configurations are okay, but I will check again if my configurations are looking okay.
Am I missing something in this config ?
Last edited by solaris_1977; 03-05-2020 at 02:03 AM..
Reason: Corrected title
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)
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)
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)
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)
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)
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)
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)
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)
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 DEBIAN
lagg
LAGG(4) BSD Kernel Interfaces Manual LAGG(4)NAME
lagg -- link aggregation and link failover interface
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device lagg
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_lagg_load="YES"
DESCRIPTION
The lagg interface allows aggregation of multiple network interfaces as one virtual lagg interface for the purpose of providing fault-toler-
ance and high-speed links.
A lagg interface can be created using the ifconfig laggN create command. It can use different link aggregation protocols specified using the
laggproto proto option. Child interfaces can be added using the laggport child-iface option and removed using the -laggport child-iface
option.
The driver currently supports the aggregation protocols failover (the default), fec, lacp, loadbalance, roundrobin, and none. The protocols
determine which ports are used for outgoing traffic and whether a specific port accepts incoming traffic. The interface link state is used
to validate if the port is active or not.
failover Sends traffic only through the active port. If the master port becomes unavailable, the next active port is used. The first
interface added is the master port; any interfaces added after that are used as failover devices.
By default, received traffic is only accepted when they are received through the active port. This constraint can be relaxed by
setting the net.link.lagg.failover_rx_all sysctl(8) variable to a nonzero value, which is useful for certain bridged network
setups.
fec Supports Cisco EtherChannel. This is a static setup and does not negotiate aggregation with the peer or exchange frames to mon-
itor the link.
lacp Supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol. LACP will negotiate a set of aggre-
gable links with the peer in to one or more Link Aggregated Groups. Each LAG is composed of ports of the same speed, set to
full-duplex operation. The traffic will be balanced across the ports in the LAG with the greatest total speed, in most cases
there will only be one LAG which contains all ports. In the event of changes in physical connectivity, Link Aggregation will
quickly converge to a new configuration.
loadbalance Balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from
any active port. This is a static setup and does not negotiate aggregation with the peer or exchange frames to monitor the
link. The hash includes the Ethernet source and destination address, and, if available, the VLAN tag, and the IP source and
destination address.
roundrobin Distributes outgoing traffic using a round-robin scheduler through all active ports and accepts incoming traffic from any active
port.
none This protocol is intended to do nothing: it disables any traffic without disabling the lagg interface itself.
Each lagg 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).
The MTU of the first interface to be added is used as the lagg MTU. All additional interfaces are required to have exactly the same value.
EXAMPLES
Create a 802.3ad link aggregation using LACP with two bge(4) Gigabit Ethernet interfaces:
# ifconfig bge0 up
# ifconfig bge1 up
# ifconfig lagg0 laggproto lacp laggport bge0 laggport bge1
192.168.1.1 netmask 255.255.255.0
The following example uses an active failover interface to set up roaming between wired and wireless networks using two network devices.
Whenever the wired master interface is unplugged, the wireless failover device will be used:
# ifconfig em0 up
# ifconfig ath0 ether 00:11:22:33:44:55
# ifconfig create wlan0 wlandev ath0 ssid my_net up
# ifconfig lagg0 laggproto failover laggport em0 laggport wlan0
192.168.1.1 netmask 255.255.255.0
(Note the mac address of the wireless device is forced to match the wired device as a workaround.)
SEE ALSO ng_fec(4), ng_one2many(4), sysctl(8), ifconfig(8)HISTORY
The lagg device first appeared in FreeBSD 6.3.
AUTHORS
The lagg driver was written under the name trunk by Reyk Floeter <reyk@openbsd.org>. The LACP implementation was written by YAMAMOTO Takashi
for NetBSD.
BUGS
There is no way to configure LACP administrative variables, including system and port priorities. The current implementation always performs
active-mode LACP and uses 0x8000 as system and port priorities.
BSD October 18, 2010 BSD