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 CENTOS
ipsec_tncfg
IPSEC_TNCFG(5) [FIXME: manual] IPSEC_TNCFG(5)NAME
ipsec_tncfg - lists IPSEC virtual interfaces attached to real interfaces
SYNOPSIS
ipsec tncfg
cat/proc/net/ipsec_tncfg
OBSOLETE
Note that tncfg is only supported on the classic KLIPS stack. It is not supported on any other stack and will be completely removed in
future versions. A replacement command still needs to be designed
DESCRIPTION
/proc/net/ipsec_tncfg is a read-only file which lists which IPSEC virtual interfaces are attached to which real interfaces, through which
packets will be forwarded once processed by IPSEC.
Each line lists one ipsec I/F. A table entry consists of:
+
an ipsec virtual I/F name
+
a visual and machine parsable separator '->', separating the virtual I/F and the physical I/F,
+
a physical I/F name, to which the ipsec virtual I/F is attached or NULL if it is not attached,
+
the keyword mtu=,
+
the MTU of the ipsec virtual I/F,
+
the automatically adjusted effective MTU for PMTU discovery, in brackets,
+
a visual and machine parsable separator '->', separating the virtual I/F MTU and the physical I/F MTU,
+
the MTU of the attached physical I/F.
EXAMPLES
ipsec2 -> eth3 mtu=16260(1443) -> 1500
shows that virtual device ipsec2 with an MTU of 16260 is connected to physical device eth3 with an MTU of 1500 and that the effective MTU
as a result of PMTU discovery has been automatically set to 1443.
ipsec0 -> wvlan0 mtu=1400(16260) -> 1500
shows that virtual device ipsec0 with an MTU of 1400 is connected to physical device wvlan0 with an MTU of 1500 and no PMTU packets have
gotten far enough to bump down the effective MTU from its default of 16260.
ipsec3 -> NULL mtu=0(0) -> 0
shows that virtual device ipsec3 is not connected to any physical device.
FILES
/proc/net/ipsec_tncfg, /usr/local/bin/ipsec
SEE ALSO ipsec(8), ipsec_manual(8), ipsec_eroute(5), ipsec_spi(5), ipsec_spigrp(5), ipsec_klipsdebug(5), ipsec_tncfg(8), ipsec_version(5),
ipsec_pf_key(5)HISTORY
Written for the Linux FreeS/WAN project <http://www.freeswan.org/> by Richard Guy Briggs.
[FIXME: source] 10/06/2010 IPSEC_TNCFG(5)