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
CNW(4)							   BSD Kernel Interfaces Manual 						    CNW(4)

NAME
cnw -- Netwave AirSurfer wireless network driver SYNOPSIS
cnw* at pcmcia? function ? DESCRIPTION
The cnw interface provides access to a theoretical 1 Mb/s wireless Ethernet network based on the Netwave AirSurfer Wireless LAN (formerly known as the Xircom Netwave Wireless LAN). Note that the driver does not support newer devices such as the Netwave AirSurfer ``Plus'', or the BayStack 650/660. These devices are sup- ported by the awi(4) driver. Netwave devices are not compatible with IEEE 802.11 wireless networks. Also note that there are Netwave devices with different wireless fre- quency, depending on the radio band plan in each country. The card uses 36K of I/O memory mapped to the card. You may need to increase memory space available to the PCMCIA controller. See pcmcia(4) for details. In use, the cards appear to achieve up to a 420Kb/s transfer rate, though a transfer rate between 250Kb/s and 350Kb/s is typical. The card operates in the 2.4GHz frequency range and is subject to interference from microwaves, IEEE 802.11 wireless network devices, as well as earth. For example, it seems that IEEE 802.11 channel 14 conflicts with Netwave (US frequency). They interfere with each other if they are both operated in the same geographic region, causing weird packet loss. You may be able to avoid the interference with IEEE 802.11 devices, by changing the IEEE 802.11 channel. HARDWARE
Cards supported by the cnw driver include: Xircom CreditCard Netwave NetWave AirSurfer DIAGNOSTICS
cnw0: can't map memory Indicates that the driver was not able to allocate enough PCMCIA bus address space into which to map the device. See pcmcia(4) and increase memory available to the PCMCIA controller. SEE ALSO
arp(4), awi(4), inet(4), intro(4), pcmcia(4), cnwctl(8) BSD
January 5, 1997 BSD