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
vde_l3
VDE_L3(1) General Commands Manual VDE_L3(1)NAME
vde_l3 - Virtual Distributed Ethernet 'Layer 3' Switch.
SYNOPSIS
vde_l3 -v vde_plug:ipaddress/netmask [-v...] [-r target_network/netmask:gateway] [-G default_gw] [-M mgmt_socket]
DESCRIPTION
A vde_l3 connects to one or more vde_switches, performing ip forwarding among its virtual interfaces. A new interface is created at startup
for each -v option given at command line. Static routes to target networks can be defined using the -r option.
vde_l3 -v /var/run/s1.ctl:192.168.0.1/24
connects to the vde sock at /var/run/s1.ctl with its virtual interface ve0, having the address 192.168.0.1 and netmask 255.255.255.0.
vde_l3
-v /var/run/s1.ctl:192.168.0.1/24
-v /var/run/s2.ctl:10.0.0.254/255.255.0.0
connects to the two vde socks, with its virtual interfaces ve0 and ve1, having addressess 192.168.1.0 and 10.0.0.254 respectively. Hosts in
each network can specify the vde_l3 as their gateway to reach the other one.
OPTIONS -v vde_plug:ipaddress/netmask
Creates a virtual network interfaces on the vde_l3 box, with address ipaddress and netmask netmask. Please note that the netmask can
be specified either in the 'classic' A.B.C.D mode, or just by giving the number of leading bits (f.e., /17 for 255.255.128.0). One
can define as many interfaces as she wants.
-r target_network/netmask:gateway
Specify a static route through gateway to reach hosts in target_network with netmask netmask. One can define as many routes as she
wants.
-G default_gw
Specify a default gateway, to be used whenever no static route is defined for a target host.
-M mgmt_socket
the unix socket where the parameters (interfaces addresses, routes, etc.) can be checked and changed runtime. unixterm(1) can be
used as a remote terminal for wirefilter.
NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik"
i.e. the German "Association for Electrical, Electronic & Information Technologies").
SEE ALSO vde_switch(1), vdeq(1), unixterm(1), vde_cryptcab(1), wirefilter(1).
AUTHORS
VDE_L3 is a tool by Daniele Lacamera <root@danielinux.net>
VDE is a project by Renzo Davoli <renzo@cs.unibo.it>
Virtual Distributed Ethernet May 7, 2007 VDE_L3(1)