Cannot trunk between DFC3CXL and DFC3C modules

[fcatalao]

Hi,

Wondering if anyone has com across this problem.

We have a 6513 which had 2x 8port (WS-X6708-10GE) 10GB modules one in slot 10 and another in slot 12. Between this two modules we created a 4 port trunk 40GB (2 ports in each module) between the 6513 and a Nexus 7018.

Yesterday we swopped one of the moduless for a 16 port 10GB (WS-X6716-10GE) and cannot trunk between the two cards. Only 2 ports work in either one or the other.

Seems because of the difference between them (DFC3CXL & DFC3C). Taking a look at the logging we noticed something to the fact of incompatability QOS feature between them.

This is what we have installed;

sh module
Mod Ports Card Type                              Model            

--- ----- -------------------------------------- ------------------ -----------
  2   24  CEF720 24 port 1000mb SFP       WS-X6724-SFP     

  7    2   Supervisor Engine 720 (Active)       WS-SUP720-3B      
  9   48  CEF720 48 port 1000mb SFP        WS-X6748-SFP      
10   16  CEF720 16 port 10GE                  WS-X6716-10GE     
11   48  CEF720 48 port 1000mb SFP        WS-X6748-SFP      
12    8  CEF720 8 port 10GE with DFC       WS-X6708-10GE     
13   48  CEF720 48 port 1000mb SFP        WS-X6748-SFP     

Mod  Sub-Module                  Model              Serial       Hw     Status
---- --------------------------- ------------------ ----------- ------- -------
  2  Centralized Forwarding Card     WS-F6700-CFC      

  7  Policy Feature Card 3              WS-F6K-PFC3B      

  7  MSFC3 Daughterboard             WS-SUP720         

  9  Centralized Forwarding Card     WS-F6700-CFC      

10  Distributed Forwarding Card      WS-F6700-DFC3C    

11  Centralized Forwarding Card     WS-F6700-CFC      

12  Distributed Forwarding Card      WS-F6700-DFC3CXL  

13  Centralized Forwarding Card     WS-F6700-CFC     

sh platform hardware pfc mode
PFC operating mode : PFC3B

Thanks

Fernando

[fcatalao]

Never mind I found the solution.

And I meant "Cannot create etherchannel.." not trunk.

[Giuseppe Larosa]

Hello Fernando,

as it may be useful to other people, may you post your solution to this issue?

Is it related to dedicated / oversubscribed mode in WS-6716 linecard?

This can give the whole story to forum readers

Best Regards

Giuseppe

[fcatalao]

LOL.

I apologise. I am waiting to test first. Once our cabling team installs a new fibre to the core I will able to test but I´m pretty sure it has has to do with oversubscripotion mode.

The WS-X6716-10GE module has an ingress queue  1p7q2t (oversubscription mode ) whereas the WS-X6708-10GE has 8q4t.

Hence the reason for getting the following;

%EC-SP-5-CANNOT_BUNDLE2: TenGig10/1 is not compatible with TenGig12/1 and will be suspended (qos-card types of TenGig10/1 do not match TenGig12/1)

.

The solution will be to configure "no mls qos channel-consistency" in port-channel interface.

[nbrucej]

Yes please tell us the solution