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 HPUX
apa
apa(7) Miscellaneous Information Manual apa(7)NAME
apa - HP Auto Port Aggregation (APA) to create link aggregates (often called trunks) and failover groups of network links
DESCRIPTION
HP APA, the HP link aggregate or trunking product, provides the ability to logically group two or more physical network ports into a single
Fat Pipe, often called a Network traffic is load balanced across all of the links in the aggregation, which allows you to build large band-
width logical links into the server that are highly available and completely transparent to the client and server applications. HP APA is
available for HP-UX 11i V1, V2 and V3.
In addition to increased performance, enterprise users require protection against business interruptions and loss of productivity. HP APA
features automatic link failure detection and the ability to transfer traffic to one of the redundant links in a specified failover group.
This is done transparently to the applications to ensure a highly available environment.
Like any other LAN interface, configure IP addresses on these APA lan interfaces using the command. See ifconfig(1M)) for more informa-
tion.
FEATURES AND BENEFITS
HP APA provides the following key benefits:
o Bandwidth scalability: Allows scaling of networks to improve aggregate throughput.
o High availability: Provides redundancy or link aggregate of network ports.
o Load balancing: Supports load balancing and failure recovery capabilities and distributes traffic across the aggregated links,
based on IP addresses, TCP/UDP Port numbers, or MAC addresses.
o Single MAC address: Assigns one single logical MAC address to an aggregate and all its ports.
o Flexibility: Allows addition and deletion of ports in an aggregate to achieve desired performance whenever needed.
o Investment protection: Utilizes Ethernet technology, which provides a natural upgrade path for current Ethernet installations,
leveraging existing end-stations, management tools and training.
o Lower IT costs: Provides automated configuration and management tools using the IEEE 802.3ad standard or FEC protocol.
CONFIGURATION MODES
HP APA allows the following configuration modes:
o Used for link aggregates on HP servers that are connected to a switch that has manual aggregation (trunk) configured.
o Used for link aggregates on HP servers that are connected to a switch that has aggregation (trunk) configured with Cisco's Fast
EtherChannel (FEC) protocol, also known as PAgP.
o Used for link aggregates on HP servers that are connected to a switch that has aggregation (trunk) configured with IEEE 802.3ad
(LACP) protocol.
o Used for failover group configuration on HP servers. There is no special feature required on switch connected to the links.
MANAGING APA CONFIGURATION
APA interfaces can be configured and managed by using the (SMH):
o On the SMH page, click the tab, then click in the section.
o Use the text based interactive tool:
See smh(1M) for more information.
APA interfaces can also be configured and managed by using the command line interface. See nwmgr(1M) and nwmgr_apa(1M) manpages or run:
for information on how to use the command for configuring APA interfaces.
APA interfaces can also be configured and managed by using the legacy command for link aggregates and by using the command for failover
group. These commands are available since initial release of the product. However, starting with the HP-UX 11i V3 APA product, HP recom-
mends using the command instead of using and commands.
See the documents listed in the for details on how to use these commands.
PRODUCT DOCUMENTATION
For detailed information, including installation, configuration, and troubleshooting, please see the following documents at in the I/O
Cards and Networking Software collection:
o
o
WARNINGS
The and commands are deprecated. These commands will be removed in a future HP-UX release. HP recommends the use of replacement command to
perform all network interface-related tasks.
FILES
Link Aggregate configuration file
Port configuration file
Failover group configuration file
AUTHORS
The Auto Port Aggregation (APA) product is developed by HP.
SEE ALSO netstat(1), ifconfig(1M), lanadmin(1M), lanscan(1M), linkloop(1M), nwmgr(1M), nwmgr_apa(1M), smh(1M), lan(7).
apa(7)