Solaris tip of the week: Link Aggregation and Logical Interfaces


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Solaris tip of the week: Link Aggregation and Logical Interfaces
# 1  
Old 09-25-2008
Solaris tip of the week: Link Aggregation and Logical Interfaces

This tip describes two options for configuring network interfaces: 1) Link aggregation (IEEE 802.3ad), which uses Ethernet network cables/ports in parallel to increase the link speed above the limit of any single cable or port and increases redundancy for higher availability, and 2) Logical interfaces, which enable you to assign multiple IP addresses to a single physical interface and share the bandwidth of a single interface across multiple IP addresses.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

Solaris link aggregation not working as expected

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

2. Solaris

Link aggregation and status of network interfaces in “ipadm” command

I am again rephrasing the issue that we are facing: We are creating link aggregations with two interfaces named net0 & net5: # dladm create-aggr -m dlmp -l net0 -l net5 -l net2 aggr1 Setting prob targets for aggr1: # dladm set-linkprop -p probe-ip=+ aggr1 Setting failure detection... (3 Replies)
Discussion started by: amitanshu.verma
3 Replies

3. Solaris

Link aggregation issues Solaris 10

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)
Discussion started by: primeaup
3 Replies
Login or Register to Ask a Question
afe(7D) 							      Devices								   afe(7D)

NAME
afe - ADMtek Fast Ethernet device driver SYNOPSIS
/dev/afe DESCRIPTION
The afe driver is a multi-threaded, loadable, clonable, GLD-based STREAMS driver supporting the Data Link Provider Interface dlpi(7P) on ADMtek (now Infineon) Centaur and Comet Fast Ethernet controllers. APPLICATION PROGRAMMING INTERFACE
The afe driver can be used as either a "style 1" or a "style 2" Data Link Service Provider. Physical points of attachment (PPAs) are inter- preted as the instance number of the afe controller as assigned by the Solaris operating environment. The relevant fields returned as part of a DL_INFO_ACK response are: o Maximum SDU is 1500. o Minimum SDU is 0. o The dlsap address length is 8. o MAC type is DL_ETHER. o SAP length is -2. The 6-byte physical address is followed immediately by a 2-byte SAP. o Service mode is DL_CLDLS. o Broadcast address is the 6-byte Ethernet broadcast address (ff:ff:ff:ff:ff:ff). If the SAP provided is zero, then IEEE 802.3 mode is assumed and outbound frames will have the frame payload length written into the type field. Likewise, inbound frames with a SAP between zero and 1500 are interpreted as IEEE 802.3 frames and delivered to any streams that are bound to SAP zero (the 802.3 SAP). PROPERTIES
The following properties may be configured using either ndd(1M) or the afe.conf configuration file as described by driver.conf(4): adv_autoneg_cap Enables (default) or disables IEEE 802.3u auto-negotiation of link speed and duplex settings. If enabled, the device negotiates among the supported (and configured, see below) link options with the link partner. If disabled, at least one of the link options below must be specified. The driver selects the first enabled link option according to the IEEE 802.3u specified preferences. adv_100T4_cap Enables the 100 BaseT4 link option. (Note that most hardware does not support this unusual link style. Also, this uses two pairs of wires for data, rather than one.) adv_100fdx_cap Enables the 100 Base TX full-duplex link option. (This is generally the fastest mode if both link partners support it. Most modern equipment supports this mode.) adv_100hdx_cap Enables the 100 Base TX half-duplex link option. (Typically used when the link partner is a 100 Mbps hub.) adv_10fdx_cap Enables the 10 Base-T full-duplex link option. (This less-frequently used mode is typically used when the link partner is a 10 Mbps switch.) adv_10hdx_cap Enables the 10 Base-T half-duplex link option. (This is the fall-back when no other option is available. It is typically used when the link partner is a 10 Mbps hub or is an older network card.) ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SPARC, x86 | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ FILES
/dev/afe Special character device. /kernel/drv/afe 32-bit driver binary (x86). /kernel/drv/amd64/afe 64-bit driver binary (x86). /kernel/drv/sparcv9/afe 64-bit driver binary (SPARC). /kernel/drv/afe.conf Configuration file. SEE ALSO
ndd(1M), driver.conf(4), attributes(5), streamio(7I), dlpi(7P) IEEE 802.3 -- Institute of Electrical and Electronics Engineers, 2002 SunOS 5.11 1 Apr 2007 afe(7D)