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)
I have some linux machines that I am trying to increase the throughput to on a single connection. They connect to a switch with two 1GbE lines and the switch does not have Link Aggregation support for these machines. I have tried bonding with balance-rr, balance-alb, but the machines can only... (4 Replies)
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)
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)
Hi,
I'm not from the Solaris world and some of these things are new to me. Can someone tell me if it is possible to configure link aggregation without using LACP?
I am told etherchannel was setup without LACP. (3 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,
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
LEARN ABOUT HPUX
lanscan
lanscan(1M)lanscan(1M)NAME
lanscan - display LAN device configuration and status
SYNOPSIS
Remarks
The and commands are deprecated. See for more information.
DESCRIPTION
displays the following information about each LAN device that has software support on the system:
o Hardware Path.
o Active Station Address (also known as Physical Address).
o Card Instance Number
o Hardware State.
o Network Interface "NamePPA". The Network Interface "Name" and the "PPA" (Physical Point of Attachment) number are concatenated
together. A single hardware device may have multiple "NamePPA" identifiers, which indicates multiple encapsulation methods may
be supported on the device. For Ethernet/IEEE 802.3 links, the "Name" is used to designate Ethernet encapsulation, and for IEEE
802.3 encapsulation. For other links (FDDI, Token Ring), only the encapsulation designation is used.
o Network Management ID.
o MAC Type.
o HP DLPI Supported. Indicates whether or not the lan device driver will work with HP's Common Data Link Provider Interface.
o DLPI Major Number.
o Extended Station Address for those interfaces which require more than 48 bits. This is displayed only when the option is
selected.
o Encapsulation Methods that the Network Interface supports. This is displayed only when the option is selected.
Options
recognizes the following command-line options:
Display station addresses only. No headings.
Display interface names only. No headings.
Display information about PPAs that are acquired by APA.
No headings.
Display MAC types only. No headings.
Display Network Managements IDs only. No headings.
Display PPA numbers only. No headings.
Same as except link aggregate PPA's will be followed by a list of LAN interface PPA's that are configured in the corresponding link
aggregate. No headings.
Verbose output. Two lines per interface. Includes displaying of extended
station address and supported encapsulation methods.
WARNINGS
does not display information about LAN devices that do not have software support such as LAN interface cards that fail to bind properly at
boot-up time.
Obsolescence
The and commands are deprecated. These commands will be removed in a future HP-UX release. HP recommends the use of replacement command
nwmgr(1M) to perform all network interface-related tasks.
AUTHOR
was developed by HP.
SEE ALSO ifconfig(1M), ioscan(1M), nwmgr(1M), lanadmin(1M), linkloop(1M), lan(7).
TO BE OBSOLETED lanscan(1M)