Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

3Com 4800G and 4200G - problem in link aggregation

AlexeyKuznetsov
Occasional Visitor

3Com 4800G and 4200G - problem in link aggregation

Hi

We have 4800G-24 and 4200G-12 switches. 4800 is core switch and 4200G is server farm switch. We wont create aggregated link between switches. I use command line and documentation :). I create manual agg/ link. Ports on both switches have the same settings (speed duplex mdi..I set manually).

All works fine (AL created sucessfull, ports are selected on both switches) only when ports on 4800 are in access mode and on 4200G in trunk mode.

But we use VLANS...

When i add VLANS (tagget) to AL link on 4200G - all works.

When i add VLANS (tagget) to AL link on 4800G - no. Ports on 4800G change mode to trunk and go into unselected state in AL. As a result AL stops working.
Where error?

Can 4800G create AL from trunk ports?
I must use static aggregation link?
Errors in switches config?

4 REPLIES
snoms
Occasional Advisor

Re: 3Com 4800G and 4200G - problem in link aggregation

Well, I have never had problems with link aggregation on 4800Gs. Have you tried LACP, yet?

Shirin
Frequent Advisor

Re: 3Com 4800G and 4200G - problem in link aggregation

Considering that VLANs in this example exist/have been created;


Manual LA - 4200G side:
system-view
link-aggregation group 1 mode manual
interface GigabitEthernet 1/0/1
port link-aggregation group 1
interface GigabitEthernet 1/0/2
port link-aggregation group 1
interface GigabitEthernet 1/0/1
port link-type trunk
port trunk permit vlan 10 20 30 40 50

 

Manual LA - 4800G side:
system-view
interface bridge-aggregation 1
interface gigabitethernet 1/0/1
port link-aggregation group 1
interface gigabitethernet 1/0/2
port link-aggregation group 1
interface bridge-aggregation 1
port link-type trunk
port trunk permit vlan 10 20 30 40 50

peter_andries
Occasional Visitor

Re: 3Com 4800G and 4200G - problem in link aggregation

First things first make sure your vlans are created.

 

Create a bridge aggregation group

NOTE! It is in static mode by default 

[Sw-A]interface bridge-aggregation 1

[Sw-A-Bridge-Aggregation1]description Connection-to-Distribution-1

[Sw-A-Bridge-Aggregation1]quit

 

Assign interfaces to bridge aggregation

[Sw-A]interface GigabitEthernet 1/0/1

[SW-A-GigabitEthernet1/0/1]port link-aggregation group 1

[SW-A-GigabitEthernet1/0/1]interface GigabitEtherne1/0/2

[SW-A-GigabitEthernet1/0/2]port link-aggregation group 1

[SW-A-GigabitEthernet1/0/2]quit

Parameters on a bridge aggregation interface are set the same as on a physical interface

[Sw-A]interface bridge-aggregation 1

[Sw-A-Bridge-Aggregation1]port link-type trunk

[Sw-A-Bridge-Aggregation1]port trunk permit vlan 100 200


Check your link aggregation

 

[4800G] display link-aggregation summary
[4800G] display link-aggregation verbose Bridge-Aggregation 1

 

NOTE: If VLAN 100 or 200 does not exist, the system will not give you an error message nor it will create the vlan, so make sure you only use existing vlans. (refereing to port trunk permit vlan 100 200)

egodkin
Occasional Advisor

Re: 3Com 4800G and 4200G - problem in link aggregation

Must I create a separate bridge aggregation for each distribution?  I currently have one bridge-agg that permits all vlans could I not assign that to each port going to the edge?  And then separate vlans on the edge switch?  Or would the unnecessary push of vlans take down the edge?