You do not define IP address of tagged VLAN on aggr0.
In your case you should :
Delete the address
Define the above address on VLAN interface vlan2170
Try pinging the gateway then.
Only native VLAN (untagged) will work on aggr0, while others such as 2170 will work on vlan2170 interface.
Those vlanNUM interfaces are the ones you configure IP address on for tagged VLAN(s) you created with dladm create-vlan ... over aggr0
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 SUSE
ifcfg-vlan
IFCFG-VLAN(5) Network configuration IFCFG-VLAN(5)NAME
ifcfg-vlan - virtual LAN interface configuration
SYNOPSIS
/etc/sysconfig/network/ifcfg-vlan*
Virtual LANs (802.1q)
To setup a vlan interface you need a configuration file that contains at least the mandatory
ETHERDEVICE
variable with the real interface used for the virtual LAN.
Further, it may contain the optional
VLAN_ID
variable that specifies the VLAN ID.
By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID.
Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either:
ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42)
or
ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42)
The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042).
Also in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config,
the interface name have any name (e.g. ifcfg-foobar).
Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and that they violate the
name scheme.
The real interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file
YaST will consider this interface as unused, if will not follow hotplug events and you're unable to apply any settings, e.g. ETH-
TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'.
The rest of the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for
details.
EXAMPLES
Sets up vlan3 vlan interface on top of eth0:
ifcfg-vlan3
STARTMODE='auto'
ETHERDEVICE='eth0'
IPADDR='192.168.3.27/24'
Sets up eth0.3 vlan interface on top of eth0:
ifcfg-eth0.3
STARTMODE='auto'
ETHERDEVICE='eth0'
IPADDR='192.168.3.27/24'
Sets up lan1 vlan interface with ID 42 on top of eth0:
ifcfg-lan1
STARTMODE='auto'
ETHERDEVICE='eth0'
VLAN_ID='42'
IPADDR='192.168.3.27/24'
BUGS
Please report bugs at <http://www.suse.de/feedback>
AUTHOR
Christian Zoz <zoz@suse.de>
Michal Svec <msvec@suse.cz>
Bjoern Jacke
Mads Martin Joergensen <mmj@suse.de>
Michal Ludvig <mludvig@suse.cz>
Marius Tomaschewski <mt@suse.de>
SEE ALSO routes(5), ifcfg(5), ifup(8).
sysconfig August 2004 IFCFG-VLAN(5)