Sponsored Content
Operating Systems Solaris Link Aggregation without LACP Post 302918717 by hicksd8 on Thursday 25th of September 2014 07:08:54 AM
Old 09-25-2014
Yes, you should be able to configure aggregation without LACP (if your switch doesn't support it).

However, the Solaris network configuration is completely different between Solaris 10 and Solaris 11 so what have you got there?
 

10 More Discussions You Might Find Interesting

1. Solaris

Link Aggregation

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)
Discussion started by: hcclnoodles
2 Replies

2. UNIX for Advanced & Expert Users

Link Aggregation and LACP

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)
Discussion started by: hcclnoodles
1 Replies

3. IP Networking

bonding lacp and link aggregation

Hello, I am trying to get clarity on a few things and am looking for some info. In every article I have read about link aggregation and lacp, it can be used combine physical links to create 1 logical link for increased bandwidth. But what it doesn't say is if this is limited by source/dst. ... (1 Reply)
Discussion started by: jaredo
1 Replies

4. IP Networking

LACP aggregation on separates switches

Hello, I'm working on LACP architecture. I would like to know if it's possible to aggregate two links on two separate switches. Here an example I want : Aggregation of link1 and link2 to obtain a logical 2 gbit/s link. Also have redundancy, if one of them is down, the traffic goes through the... (1 Reply)
Discussion started by: jbemonet
1 Replies

5. AIX

Link aggregation with hacmp ?

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)
Discussion started by: zxmaus
4 Replies

6. HP-UX

Link Aggregation HPUX

Hi, Hoping someone can offer some advice on something i have not dealt with before. We have a server that seems to have some very strange configuration done on it. It has 2 physical NIC's and rather than both be aggregated into LAN900 we have 1 in LAN900 and 1 in LAN901? (See Below)... (2 Replies)
Discussion started by: Andyp2704
2 Replies

7. Solaris

Link aggregation

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)
Discussion started by: PatrickBaer
8 Replies

8. HP-UX

Break Link Aggregation in HP UX.

Hi, I want to Break the Link Aggregation. My aggregation are lan0+lan1 = lan900. Now I want to break this and put the IP in lan0. But i have cluster environment and this is the main database server. So It need to change in cluster script. But I dont know where I have to change it. Please... (1 Reply)
Discussion started by: mkiron
1 Replies

9. IP Networking

Link Aggregation

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)
Discussion started by: mnnn
0 Replies

10. Solaris

How can I test link aggregation?

Hi, I have Solaris-10 server and link aggregation is configured on this in below way # dladm show-aggr key: 1 (0x0001) policy: L4 address: 3c:d9:2b:ee:a8:a (auto) device address speed duplex link state bnx1 3c:d9:2b:ee:a8:a... (8 Replies)
Discussion started by: solaris_1977
8 Replies
Intro(9S)						    Data Structures for Drivers 						 Intro(9S)

NAME
Intro, intro - introduction to kernel data structures and properties DESCRIPTION
Section 9P describes kernel properties used by device drivers. Section 9S describes the data structures used by drivers to share informa- tion between the driver and the kernel. See Intro(9E) for an overview of device driver interfaces. In Section 9S, reference pages contain the following headings: o NAME summarizes the purpose of the structure or property. o SYNOPSIS lists the include file that defines the structure or property. o INTERFACE LEVEL describes any architecture dependencies. o DESCRIPTION provides general information about the structure or property. o STRUCTURE MEMBERS lists all accessible structure members (for Section 9S). o SEE ALSO gives sources for further information. Of the preceding headings, Section 9P reference pages contain the NAME, DESCRIPTION, and SEE ALSO fields. Every driver MUST include <sys/ddi.h> and <sys/sunddi.h>, in that order, and as final entries. The following table summarizes the STREAMS structures described in Section 9S. +-----------------------------+-----------------------------+ | Structure | Type | +-----------------------------+-----------------------------+ |copyreq |DDI/DKI | +-----------------------------+-----------------------------+ |copyresp |DDI/DKI | +-----------------------------+-----------------------------+ |datab |DDI/DKI | +-----------------------------+-----------------------------+ |fmodsw |Solaris DDI | +-----------------------------+-----------------------------+ |free_rtn |DDI/DKI | +-----------------------------+-----------------------------+ |iocblk |DDI/DKI | +-----------------------------+-----------------------------+ |linkblk |DDI/DKI | +-----------------------------+-----------------------------+ |module_info |DDI/DKI | +-----------------------------+-----------------------------+ |msgb |DDI/DKI | +-----------------------------+-----------------------------+ |qband |DDI/DKI | +-----------------------------+-----------------------------+ |qinit |DDI/DKI | +-----------------------------+-----------------------------+ |queclass |Solaris DDI | +-----------------------------+-----------------------------+ |queue |DDI/DKI | +-----------------------------+-----------------------------+ |streamtab |DDI/DKI | +-----------------------------+-----------------------------+ |stroptions |DDI/DKI | +-----------------------------+-----------------------------+ The following table summarizes structures that are not specific to STREAMS I/O. +-----------------------------+-----------------------------+ | Structure | Type | +-----------------------------+-----------------------------+ |aio_req |Solaris DDI | +-----------------------------+-----------------------------+ |buf |DDI/DKI | +-----------------------------+-----------------------------+ |cb_ops |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_device_acc_attr |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dma_attr |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dma_cookie |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dma_lim_sparc |Solaris SPARC DDI | +-----------------------------+-----------------------------+ |ddi_dma_lim_x86 |Solaris x86 DDI | +-----------------------------+-----------------------------+ |ddi_dma_req |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_dmae_req |Solaris x86 DDI | +-----------------------------+-----------------------------+ |ddi_idevice_cookie |Solaris DDI | +-----------------------------+-----------------------------+ |ddi_mapdev_ctl |Solaris DDI | +-----------------------------+-----------------------------+ |devmap_callback_ctl |Solaris DDI | +-----------------------------+-----------------------------+ |dev_ops |Solaris DDI | +-----------------------------+-----------------------------+ |iovec |DDI/DKI | +-----------------------------+-----------------------------+ |kstat |Solaris DDI | +-----------------------------+-----------------------------+ |kstat_intr |Solaris DDI | +-----------------------------+-----------------------------+ |kstat_io |Solaris DDI | +-----------------------------+-----------------------------+ |kstat_named |Solaris DDI | +-----------------------------+-----------------------------+ |map |DDI/DKI | +-----------------------------+-----------------------------+ |modldrv |Solaris DDI | +-----------------------------+-----------------------------+ |modlinkage |Solaris DDI | +-----------------------------+-----------------------------+ |modlstrmod |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_address |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_arq_status |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_device |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_extended_sense |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_hba_tran |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_inquiry |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_pkt |Solaris DDI | +-----------------------------+-----------------------------+ |scsi_status |Solaris DDI | +-----------------------------+-----------------------------+ |uio |DDI/DKI | +-----------------------------+-----------------------------+ SEE ALSO
Intro(9E) NOTES
Do not declare arrays of structures as the size of the structures can change between releases. Rely only on the structure members listed in this chapter and not on unlisted members or the position of a member in a structure. SunOS 5.11 15 May 2001 Intro(9S)
All times are GMT -4. The time now is 04:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy