Login or Register to Ask a Question and Join Our Community


Solaris

Solaris link aggregation not working as expected

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Solaris link aggregation not working as expected
# 1  
Old 01-04-2019
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.
Code:
# netstat -nr

Routing Table: IPv4
  Destination           Gateway           Flags  Ref     Use     Interface
-------------------- -------------------- ----- ----- ---------- ---------
default              172.31.xx.xx          UG        1         12 aggr62001
default              172.31.xx.xy         UG        1         14 aggr64001
default              172.31.xx.yy          UG        1       6182 aggr50001
default              172.31.yy.yy        UG        1         12 aggr66001
default              172.31.yy.yx          UG        1          5 aggr81001
default              172.31.yx.yx         UG        1         24 aggr60001
--
--
--
--
--
# dladm show-link
bnx0            type: non-vlan  mtu: 1500       device: bnx0
bnx1            type: non-vlan  mtu: 1500       device: bnx1
bnx2            type: non-vlan  mtu: 1500       device: bnx2
bnx3            type: non-vlan  mtu: 1500       device: bnx3
igb0            type: non-vlan  mtu: 1500       device: igb0
igb1            type: non-vlan  mtu: 1500       device: igb1
igb2            type: non-vlan  mtu: 1500       device: igb2
igb3            type: non-vlan  mtu: 1500       device: igb3
aggr1           type: non-vlan  mtu: 1500       aggregation: key 1
aggr2           type: non-vlan  mtu: 1500       aggregation: key 2
aggr150002      type: vlan 150  mtu: 1500       aggregation: key 2
aggr50001       type: vlan 50   mtu: 1500       aggregation: key 1
aggr55001       type: vlan 55   mtu: 1500       aggregation: key 1
aggr60001       type: vlan 60   mtu: 1500       aggregation: key 1
aggr62001       type: vlan 62   mtu: 1500       aggregation: key 1
aggr64001       type: vlan 64   mtu: 1500       aggregation: key 1
aggr66001       type: vlan 66   mtu: 1500       aggregation: key 1
aggr81001       type: vlan 81   mtu: 1500       aggregation: key 1
# 
# dladm show-aggr
key: 1 (0x0001) policy: L4      address: 3c:d9:2b:f9:20:5e (auto)
           device       address                 speed           duplex  link    state
           bnx1         3c:d9:2b:f9:20:5e         1000  Mbps    full    up      attached
           igb2         f4:ce:46:a7:df:ba         0     Mbps    half    down    standby
key: 2 (0x0002) policy: L4      address: 3c:d9:2b:f9:20:5c (auto)
           device       address                 speed           duplex  link    state
           bnx0         3c:d9:2b:f9:20:5c         1000  Mbps    full    up      attached
           igb3         f4:ce:46:a7:df:bb         1000  Mbps    full    up      attached
#
# dladm show-dev
bnx0            link: up        speed: 1000  Mbps       duplex: full
bnx1            link: up        speed: 1000  Mbps       duplex: full
bnx2            link: unknown   speed: 0     Mbps       duplex: unknown
bnx3            link: unknown   speed: 0     Mbps       duplex: unknown
igb0            link: unknown   speed: 0     Mbps       duplex: half
igb1            link: unknown   speed: 0     Mbps       duplex: half
igb2            link: down      speed: 0     Mbps       duplex: half
igb3            link: up        speed: 1000  Mbps       duplex: full
#

HERE IS SETUP OF WORKING SERVER -->
# dladm show-aggr
key: 1 (0x0001) policy: L4      address: 3c:d9:2b:f9:20:12 (auto)
           device       address                 speed           duplex  link    state
           bnx1         3c:d9:2b:f9:20:12         1000  Mbps    full    up      attached
           igb2         f4:ce:46:a7:e6:26         1000  Mbps    full    up      attached
key: 2 (0x0002) policy: L4      address: 3c:d9:2b:f9:20:10 (auto)
           device       address                 speed           duplex  link    state
           bnx0         3c:d9:2b:f9:20:10         1000  Mbps    full    up      attached
           igb3         f4:ce:46:a7:e6:27         1000  Mbps    full    up      attached
# dladm show-dev
bnx0            link: up        speed: 1000  Mbps       duplex: full
bnx1            link: up        speed: 1000  Mbps       duplex: full
bnx2            link: unknown   speed: 0     Mbps       duplex: unknown
bnx3            link: unknown   speed: 0     Mbps       duplex: unknown
igb0            link: unknown   speed: 0     Mbps       duplex: half
igb1            link: unknown   speed: 0     Mbps       duplex: half
igb2            link: up        speed: 1000  Mbps       duplex: full
igb3            link: up        speed: 1000  Mbps       duplex: full
#

Probably I would like to make igb2 as full duplex, but there is no igb2 interface in ifconfig. All i can see are aggr interfaces. How will I see underlying interface of igb2 ?
Thanks
# 2  
Old 01-05-2019
Try to access the interface with ndd.
First list the supported values.
Code:
ndd /dev/igb0 \?

Or
Code:
ndd /dev/igb \?

Actually the default should be autonegotiation, also on the other side (LAN switch).
# 3  
Old 01-05-2019
/dev/igb2 as well as /dev/igb0, both shows all below supported values and I tried changing from half duplex to full duplex, but igb2 still shows down and standby.
Code:
# ndd /dev/igb2 \?
?                             (read only)
mtu                           (read and write)
min_allowed_mtu               (read only)
max_allowed_mtu               (read only)
adv_autoneg_cap               (read and write)
adv_1000fdx_cap               (read and write)
adv_1000hdx_cap               (read only)
adv_100fdx_cap                (read and write)
adv_100hdx_cap                (read and write)
adv_10fdx_cap                 (read and write)
adv_10hdx_cap                 (read and write)
adv_100T4_cap                 (read only)
link_status                   (read only)
link_speed                    (read only)
link_duplex                   (read only)
autoneg_cap                   (read only)
pause_cap                     (read only)
asym_pause_cap                (read only)
1000fdx_cap                   (read only)
1000hdx_cap                   (read only)
100fdx_cap                    (read only)
100hdx_cap                    (read only)
10fdx_cap                     (read only)
10hdx_cap                     (read only)
lp_autoneg_cap                (read only)
lp_pause_cap                  (read only)
lp_asym_pause_cap             (read only)
lp_1000hdx_cap                (read only)
lp_1000fdx_cap                (read only)
lp_100fdx_cap                 (read only)
lp_100hdx_cap                 (read only)
lp_10fdx_cap                  (read only)
lp_10hdx_cap                  (read only)
link_autoneg                  (read only)
tx_copy_thresh                (read and write)
tx_recycle_thresh             (read and write)
tx_overload_thresh            (read and write)
tx_resched_thresh             (read and write)
rx_copy_thresh                (read and write)
rx_limit_per_intr             (read and write)
intr_throttling               (read and write)
adv_pause_cap                 (read only)
adv_asym_pause_cap            (read only)
# ndd -set /dev/igb2 adv_100hdx_cap 0
# ndd -set /dev/igb2 adv_100fdx_cap 1
# dladm show-aggr
key: 1 (0x0001) policy: L4      address: 3c:d9:2b:f9:20:5e (auto)
           device       address                 speed           duplex  link    state
           bnx1         3c:d9:2b:f9:20:5e         1000  Mbps    full    up      attached
           igb2         f4:ce:46:a7:df:ba         0     Mbps    half    down    standby
key: 2 (0x0002) policy: L4      address: 3c:d9:2b:f9:20:5c (auto)
           device       address                 speed           duplex  link    state
           bnx0         3c:d9:2b:f9:20:5c         1000  Mbps    full    up      attached
           igb3         f4:ce:46:a7:df:bb         1000  Mbps    full    up      attached
#

There are multiple gateways on this server. Concerned gateway is not pingable and that is going via aggr50001
Code:
# traceroute 172.31.12.1
traceroute: Warning: Multiple interfaces found; using 172.31.12.20 @ aggr50001
traceroute to 172.31.12.1 (172.31.12.1), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  *

Last edited by solaris_1977; 01-05-2019 at 05:22 AM..
# 4  
Old 01-05-2019
adv_100fdx_cap?
I think you want adv_1000fdx_cap
Also ensure that adv_autoneg_cap is set.
This User Gave Thanks to MadeInGermany For This Post:
jim mcnamara
# 5  
Old 01-05-2019
Sorry, my mistake
I have set that now, but no luck
Code:
# ndd -get /dev/igb2 adv_autoneg_cap
1
# ndd -get /dev/igb2  adv_1000fdx_cap
1
# ndd -get /dev/igb2 adv_100fdx_cap
0
# dladm show-aggr
key: 1 (0x0001) policy: L4      address: 3c:d9:2b:f9:20:5e (auto)
           device       address                 speed           duplex  link    state
           bnx1         3c:d9:2b:f9:20:5e         1000  Mbps    full    up      attached
           igb2         f4:ce:46:a7:df:ba         0     Mbps    half    down    standby
key: 2 (0x0002) policy: L4      address: 3c:d9:2b:f9:20:5c (auto)
           device       address                 speed           duplex  link    state
           bnx0         3c:d9:2b:f9:20:5c         1000  Mbps    full    up      attached
           igb3         f4:ce:46:a7:df:bb         1000  Mbps    full    up      attached
#

# 6  
Old 01-07-2019
For a test, set adv_autoneg_cap is set to 0.
If only adv_1000fdx_cap is enabled then it will be enforced.
If the enforcement works, install a patch for the igb driver (reboot to activate), then enable adv_autoneg_cap again.
If not, then something is wrong with the LAN switch (or the cable).
# 7  
Old 01-07-2019
I just checked with Network team and they confirmed that link is fine on switch side, but Link aggregation (LACP) is showing down.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. 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

2. 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

3. Solaris

Link Aggregation without LACP

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)
Discussion started by: techy1
3 Replies

4. 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

5. Solaris

solaris link aggregation problem , once i reboot it is not showing, not able to ping the default gat

Hi All, I am trying to aggregate the NIC's,(igb2 and igb3) (igb0 is used by the physical system and igb1 is used by primary-vsw0) to create the domains on that for faster data transfer, I followed the process for creating the aggregation, dladm create-aggr -d igb2 -d igb3 1 after creating the... (2 Replies)
Discussion started by: buildscm
2 Replies

6. 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

7. 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

8. 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

9. 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
Login or Register to Ask a Question