Thanks.
I was able to find a server, on which I can do "pull the cable test".
From below output, it shows that bnx1 cable was pulled out. since aggr is configured igb2 took the traffic and all link sustained. But first line shows "address: 3c:d9:2b:f9:20:5e (auto)" and this MAC address is for bnx1.
Since igb2 took all the traffic now and its mac is f4:ce:46:a7:df:ba , should it not show in auto ? Sorry, I am confused in understanding this.
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)
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)
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)
Discussion started by: mnnn
0 Replies
LEARN ABOUT OPENSOLARIS
rge
rge(7D) Devices rge(7D)NAME
rge - Realtek Gigabit/Fast Ethernet Network Adapter driver
SYNOPSIS
/dev/rge
DESCRIPTION
The rge Gigabit/Fast Ethernet driver is a multi-threaded, loadable, clonable, GLD-based STREAMS driver supporting the Data Link
Provider Interface, dlpi(7P), on the Realtek Gigabit/Fast Ethernet Network Adapter.
The rge driver functions includes controller initialization, frame transmit and receive, promiscuous and multicast support, and error
recovery and reporting.
APPLICATION PROGRAMMING INTERFACE
The cloning, character-special device /dev/rge is used to access all Realtek Gigabit/Fast Ethernet devices installed within the system.
The rge driver is managed by the dladm(1M) command line utility, which allows VLANs to be defined on top of rge instances and for rge
instances to be aggregated. See dladm(1M) for more details.
The values returned by the driver in the DL_INFO_ACK primitive in response to the DL_INFO_REQ are as follows:
o Maximum SDU (with jumbo frame) is 7000.
o Minimum SDU is 0.
o DSLAP address length is 8 bytes.
o MAC type is DL_ETHER.
o SAP length value is -2, meaning the physical address component is followed immediately by a 2-byte sap component within the
DLSAP address.
o Broadcast address value is Ethernet/IEEE broadcast address (FF:FF:FF:FF:FF:FF).
Once in the DL_ATTACHED state, you must send a DL_BIND_REQ to associate a particular Service Access Point (SAP) with the stream.
CONFIGURATION
By default, the rge driver performs auto-negotiation to select the link speed and mode. Link speed and mode can be any one of the follow-
ing:
o 1000 Mbps, full-duplex
o 100 Mbps, full-duplex
o 100 Mbps, half-duplex
o 10 Mbps, full-duplex
o 10 Mbps, half-duplex
Alternatively, you can set the capabilities advertised by the rge device using ndd(1M). The driver supports a number of parameters whose
names begin with adv_. Each of these parameters contains a boolean value that determines if the device advertises that mode of operation.
The adv_pause_cap indicates if half/full duplex pause is advertised to link partner. You can set adv_asym_pause_cap to advertise to the
link partner that asymmetric pause is desired.
For example, to prevent the device 'rge2' from advertising gigabit capabilities, enter (as super-user):
# ndd -set /dev/rge2 adv_1000fdx_cap 0
All capabilities default to enabled. Note that changing any capability parameter causes the link to go down while the link partners renego-
tiate the link speed/duplex using the newly changed capabilities.
You can find the current parameter settings by using ndd -get. In addition, the driver exports the current state, speed, duplex setting,
and working mode of the link via ndd parameters (these are read only and may not be changed). For example, to check link state of device
rge0:
# ndd -get /dev/rge0 link_status
1
# ndd -get /dev/rge0 link_speed
100
# ndd -get /dev/rge0 link_duplex
2
The output above indicates that the link is up and running at 100Mbps full-duplex. In addition, the driver exports its working mode by
loop_mode. If it is set to 0, the loopback mode is disabled.
FILES
/dev/rge* Character special device.
/kernel/drv/rge 32-bit x86 rge driver binary.
/kernel/drv/amd64/rge 64-bit x86 rge driver binary.
/kernel/drv/sparcv9/rge SPARC rge driver binary.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC, x86 |
+-----------------------------+-----------------------------+
SEE ALSO dladm(1M), attributes(5), streamio(7I), dlpi(7P)
Writing Device Drivers
STREAMS Programming Guide
Network Interfaces Programmer's Guide
SunOS 5.11 21 Dec 2007 rge(7D)