Port-channel L2 problem with Fabric Interconnect and Nexus 7010

berwin_kan · ‎01-25-2011

Hi,

i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.

but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.

I was trying :

1. I using non dedicated port in Nexus 7010.

- rate-mode share

- channel-group 1 mode active

- switchport mode trunk

when i using this option, the port-channel in Nexus 7010 was suspended

2. I using non dedicated port in Nexus 7010

- rate-mode share

- channel group 1 mode on

- switchport mode trunk

when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.

3. I using dedicated port in Nexus 7010

- rate-mode share

- channel group 1 mode active

- switchport mode trunk

when i using this option, the port-channel in Nexus 7010 was suspended

4. I using dedicated port in Nexus 7010

- rate-mode dedicated

- channel group 1 mode active

- switchport mode trunk

when i using this option, the port-channel in Nexus 7010 was came up and running well.

but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.

is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.

i attach the topology of N7K with Fabric interconnect.

regards,

Berwin H

Manish Tandon · ‎01-26-2011

Berwin

For uplinks the port-channel mode is always active.

It is the only mode allowed i.e it is not configurable.

Thanks

--Manish

berwin_kan · ‎01-26-2011

Hi manish thanks for your respon,

do you have any idea if i want use port-channel and rate-mode share in nexus 7010?

i use N7K-M132XP-12 module in nexus 7010.

still hoping to use rate-mode share and bundle into port-channel for the connection to Fabric Interconnect..

regards,

Berwin H

Manish Tandon · ‎01-26-2011

Berwin

I will have to try the lacp with the shared mode on the 7000.

I do not have a 7000 on my setup so not sure yet if the shared mode is doing something different.

Did you try running debugs on the 7000 to see where lacp errors out?

It should be channel mode active on both sides. Active/passive technically should form a port channel too.

Thanks

--Manish

Manish Tandon · ‎01-27-2011

Berwin

It seems to work when we tried it in the lab.

See attached for the relevant show commands.

Thanks

--Manish

berwin_kan · ‎01-27-2011

Hi Manish,

Thanks for your support,

i will try this again for the third chance..

since our datacenter already production i will try in saturday night this week, and i will documentation and reporting to this thread.

Thanks a lot!

Berwin H.

berwin_kan · ‎02-01-2011

Hi Manish,

I attach what i have done last week. u can see the details in document.

the conclusion is: I still cannot configure port-channel with Non Dedicated port using rate-mode share.

i see something that confusing me,

when i enable rate-mode share in Interface E1/1-2 which is a dedicated port, i still see the rate-mode dedicated command in interface member port-group (Interface E1/3,1/4,1/5,1/6,1/7,1/8). so i try to remove the command using no rate-mode dedicated/rate-mode share but it cannot removed.

i think this command that makes the port-channel in non dedicated port cannot bundled.

is it a bug ?

Thanks.

Berwin H

berwin_kan · ‎02-20-2011

Hi Manish,

the issue was solved, i was fix it last week.

the solution is:

i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2) so i allocate the interface on all module N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.

i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.

So here the result of my port-channel :

SVRN7KFARM-HO-01# show port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
--------------------------------------------------------------------------------
Group Port-       Type     Protocol Member Ports
      Channel
--------------------------------------------------------------------------------
1     Po1(SU)     Eth      LACP      Eth1/1(P)    Eth1/2(P)    Eth1/3(P)
                                     Eth1/4(P)    Eth1/25(P)
2     Po2(SU)     Eth      LACP      Eth1/9(P)    Eth1/10(P)   Eth1/11(P)
                                     Eth1/12(P)   Eth1/26(P)
3     Po3(SU)     Eth      LACP      Eth1/17(P)   Eth1/18(P)
4     Po4(SU)     Eth      NONE      Eth10/32(P) Eth10/34(P) Eth10/35(P)
                                     Eth10/36(P)

Thanks.

Berwin H

Manish Tandon · ‎02-21-2011

Berwin

Sorry for the delay in response ..

I checked with a few 7k folks and what the steps you did should have have changed the behavior.

What moving the interfaces to a vdc does is that it reporgrammes them. So if it was in some weird state, it starts clean when moved back.

So maybe your system was in such a state (very hard to tell without debugging etc done in such state).

As an exmaple, CSCtl59485 is related to the F1 LC being misprogrammed and the workaround is listed as move them from the vdc and put them back.

Thanks

--Manish