Config port channel across different type of media

Please help with the question if we could config port channel across different media type such as Gigabit and Ethernet 10/100 ports ? thanks in advance.

Hello,
no, that is not possible.
When assigning interfaces to a specific port channel, the interfaces must be all Fast
Ethernet or all Gigabit Ethernet. You cannot mix interface types within a single port
channel.
Check the following link:
Configuring the EtherChannel
http://www.cisco.com/univercd/cc/td/doc/product/l3sw/4840g/ios_12/config/4840ec.pdf
HTH,
GP

Similar Messages

Port channels across slots on a 6500

Hi experts,
we have 2 x 6509-E chassis NOT doing VSS, having a 10g module ( WS-X6708-10GE ) in each chassis. We plan to get another 10g module (same as existing) for each chassis. I was planning to move some ports from the existing module to the new module.
Question - Is a port channel supported across 2 modules on the same switch?
thnx

Hey,
Cross module etherchannel is supported as long as physical characteristics of ports match. Do check the QoS properties as well.
Also check the restrictions section as well:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/channel.html#wp1020420
HTH.
Regards,
RS

About MDS 9222i config port-channel

dear everyone~
in project ,i need config MDS 9222i use 4 FCIP interface connect to 7606S 4 GE port for port-channel feature,but in MDS9222i i use port-channel commad ,cannot run。
how can i config it？
thinks~

Hi Sun,
Ethernet PortChannels are not supported on MSM-18/4 modules and 9222i IPS modules.
You can place the fcip interfaces in a fibre channel port-channel instead.
Regards,
David

How to configure a port channel with VLAN trunking (and make it work..)

We're trying to configure a port channel group with trunked ports to connect a NetApp HA pair. We want to create two data LIFs and connect them to the switch stack. We are trying to create 2 data lifs, one for cifs and one for nfs that are on different vlans.
We want the same ports to be able to allow multiple vlans to communicate. (trunked)
These data lifs should be able to fail over to different nodes in the HA pair and still be able to communicate on the network.
What this means is that we have to connect 4 ports each for each node in the NetApp HA Pair to the switches and create a port channel of some type that allows for trunked vlans. When we configure the ports, the configuration is as follows (below):
We are only able to configure an IP on one of the vlans.
When we configure an IP from another vlan for the data lif, it does not respond to a ping.
Does anyone have any idea what I'm doing wrong on the Cisco switch?
interface GigabitEthernet4/0/12
description Netapp2-e0a
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet4/0/13
description Netapp2-e0c
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet6/0/12
description Netapp2-e0b
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet6/0/13
description Netapp2-e0d
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface Port-channel20
description Netapp2-NFS
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
spanning-tree portfast
spanning-tree bpduguard enable
end

Our problem was fixed by the storage people. They changed the server end to trunk, and the encapsulation / etherchannel.
I like all the suggestions, and they probably helped out with the configuration getting this to work.
Thanks!
interface Port-channel20
description Netapp2-NFS
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
interface GigabitEthernet4/0/12
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet4/0/13
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet6/0/12
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet6/0/13
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active

About n1000v with port channel

there is a n1000v connected to multiple upstream switches in the customer's production environment.
the following is from the Cisco Nexus 1000V Interface Configuration Guide, Release4.2(1)SV2(2.1).
You use vPC-HM mode to create a port channel when the switch is connected to multiple upstream switches
that are not clustered.
my question is,
can I use LACP with multiple upstream switches that are not clustered?
can I use LACP with multiple upstream switches that are stacked?
if I stack multiple upstream switches,does it mean clustered?
thanks.

Hi,
See some of the guidelines:
Guidelines and Limitations
Port channeling has the following guidelines and restrictions:
•All ports in the port channel must be in the same Cisco Nexus 1000V module; you cannot configure port channels across Cisco Nexus 1000V modules.
•Port channels can be formed with multiple upstream links only when they satisfy the compatibility requirements and under the following conditions:
–The uplinks from the host are going to the same upstream switch.
–The uplinks from the host going to multiple upstream switches are configured with vPC-HM.
•You can configure multiple port channels on a device.
•After you configure a port channel, the configuration that you apply to the port channel interface affects the port channel member ports. The configuration that you apply to the member ports affects only the member port where you apply the configuration.
•You must remove the port security information from a port before you can add that port to a port channel. Similarly, you cannot apply the port security configuration to a port that is a member of a channel group.
•You can configure ports that belong to a port channel group as PVLAN ports.
•Any configuration changes that you apply to the port channel is applied to every member interface of that port channel.
•Channel member ports cannot be a source or destination SPAN port.
That said LACP should work on switches that are not clustered and meet the conditions above.
A stack is treated as one unit which means that would be like you have just one big chassis.
Stacking does not the same as clustering it works different. so if you stack them that would be a stack not a cluster
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1270746
Hope this helps.

Load-balancing Algorithm for NX-OS Port Channels

Hi, all
I do not understand description of port-channel load-balance ethernet command.
switch(config)# port-channel load-balance ethernet ?
destination-ip         Destination IP address
destination-mac        Destination MAC address
destination-port       Destination TCP/UDP port
source-dest-ip         Source & Destination IP address (includes l2)
source-dest-ip-only    Source & Destination IP addresses only
source-dest-mac        Source & Destination MAC address
source-dest-port       Source & Destination TCP/UDP port (includes l2 and l3)
source-dest-port-only Source & Destination TCP/UDP port only
source-ip              Source IP address
source-mac             Source MAC address
source-port            Source TCP/UDP port
Please tell me what the following descriptions mean.
Source & Destination IP address (includes l2)
Source & Destination TCP/UDP port (includes l2 and l3)
What are the meaning of "includes l2" and "includes l2 and l3" ?
Thank you for your cooperation in advance.

Hi Satoru,
On the Nexus 5000/6000 platforms, all FEXs will inherit the global hashing algorithm from the parent device.
On the Nexus 7000 platform, hashing algorithms can be assigned on a per FEX basis (all load balancing changes must be made from the Admin VDC):
N7K-A(config)# port-channel load-balance src-dst ip-l4port fex 134
Any FEX without a hashing algorithm configured with inherit the global hash. Making changes to the modular/global hash will not alter FEX specific hashing algorithms.
To verify the configuration applied you can use this command:
N5K_A# show port-channel load-balance
On the Nexus 7000, the per FEX algorithm can be checked by appending the ‘fex <#>’ to the end of the command in the Admin VDC or the FEX’s respective VDC:
N7K-A(config)# show port-channel load-balance fex 134
Regards,
Richard

WLC LAG Mode and Port Channel

So I was reading the controller best practices and got this:
When you use LAG, the controller relies on the switch for the load balancing decisions on traffic that come from the network. It expects that traffic that belongs to an AP always enters on the same port. Use only ip-src or ip-src ip-dst load balancing options in the switch EtherChannel configuration. Some switch models might use unsupported load balancing mechanisms by default, so it is important to verify.
This is how to verify the EtherChannel load balancing mechanism:
switch#show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-dst-ip
EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address
This is how to change the switch configuration (IOS):
switch(config)#port-channel load-balance src-dst-ip
Now Cisco switches by default will do src-mac. If I make this change obviously this would be a global change. I don't believe it should cause any performance issues but wanted to get some expert opinions on this. Switches my controller will be connected to will also have two routers connected as well via Port Channel.
I'm trying to understand the reasoning behind this.

I've never seen that command cause any issues in any deployment I've worked on.
HTH,
Steve

Nexus 1000v - port-channel "refresh"

Hi All,
My question is, does anyone have any information on this 1000v command:
Nexus-1000v(config)# port-channel internal device-id table refresh
I am looking for a way for the port-channel interface to be automatically removed from the 1000v once the VEM has been deleted, currently the port-channel interface does not disappear when the VEM has been removed. This seems to be causing problems once the same VEM is re-added later on. Ports are getting sent into quarantine states and ending up in invalid states (eg. NoPortProfile state when there is actually a port-profile attached).
Anyway, if anyone can explain the above command or tell me how to find out more, it would be great, I can't find it documented anywhere and the context-sensitive help in the NXOS is vague at best.

Brendan,
I don't have much information on that command, but I do know it wont remove any unused port channels. They have to be manually deleted if they're no longer needed.
The port Channel ID will remain even after a VEM is removed in case the assigned VEM comes back. When a VEM is decommisioned permanently, I'll do a "no vem x" to also remove the Host entry for that VEM from the VSM. This way the module slot # can be re-assigned to the next new VEM inserted. After adding/removing VEMs just do a "show port-channel summary" to see any unused Port Channel IDs, and delete them. It's a quick & painless task.
I would hope this wouldn't be a common issue - how often are you deleting/removing VEMs?
Regards,
Robert

Port channel configuration with VMware

Hi everyone, I have dual 6120 interconnects, each of which have two uplink ports. I also have two Catalyst 4900M switches to uplink to. So I plan to configure both 802.1q and 802.3ad on each of the 6120 uplink pairs. My question relates to the physical cabling, bearing in mind ESX will be running on the blades.
Would you cable both the uplink ports on interconnect 1 to switch 1? Or would you cross-connect them to both switch 1 and switch 2?
As per this article I see ESX does not support splitting a port channel across two switches, but I am unsure how the presence of the 6120s affects this. Can anyone suggest the best way of doing the cabling based on the kit I have? Thanks.
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1001938&sliceId=1&docTypeID=DT_KB_1_1&dialogID=14912551&stateId=1%200%2014916516

Hey Simon, let's address this is two parts because there are two layers: server-bound (ESX-6120) and north-bound (6120-Cat4900).
At the ESX end, use the default srcPort in the vSwitch / port group with both 10GbE uplink ports (vmnic0 and vmnic1) set to active (not active/passive). There are no loops in this configuration. On the VNIC (in UCSM) you select trunk port and allow all the VLANs that your vSwitch port groups needs. If you don't use a VLAN for the Service Console/ESXi Management, then make sure you set Native to the correct VLAN in the VNIC to allow untagged traffic down the right path.
At the 6120 you can't explicitly configure a trunk for border ports, they are already set so and when you add VLANs they are added to every border port trunk configuration. You, of course, need to make sure the Cat4900 ports at the other end of the cable have the same trunkport VLAN configuration.
So in summary - set VLANs in vSwitch port groups, VNIC in UCSM and northbound switch.
Now when it comes to port channels, you can only configure two or more border ports as a port channel if they are cabled to the same Cat4900. If you had Nexus 5k/7k northbound then you could use vPC on them to allow "mesh" cabling (ie. one 6120 connects to both Nexus switches). But as you aren't using Nexus you will end up with a configuration as Jeremy explained:
ESX --> vSwitch0 --> srcPort load balancing --> 2 active uplinks --> many port groups
6120-a --> Cat4900-a
6120-b --> Cat4900-b
However, I would still recommend using a couple of border ports in a port channel on each fabric to each Cat4900 because, if you pull out a cable/lose a port, then when that port is re-enabled the existing live traffic is redistributed whereas without the port channel only new traffic will be spread across both links.
Cheers
Steve
Cisco UCS Team

UCS - san-port-channel over vpc

Hi,
I'm hoping someone can help out with this,
I have a setup with 2 Nexus 5548's connected over a vpc peer link and a keepalive, These two nexus switch's have a standard VPC connection to an upstream 6500. this is working fine,
Then there are multiple native FC connections from the 5548's to 6248's. I know there is the option to configure FC port-channel's on the UCS 2.0 but is it possible to put fc interfaces of the nexus 5548 into a san port-channel across a vpc between the the nexus 5548's.
so for example, can i port-channel the following across a vpc or is a san port-channel restricted to ports on the same nexus switch only.
Fabric A fc1/31 & fc1/32 uplinked to -> NX5K-1 Port fc1/31 & NX5K-2 Port fc1/32 (san port-channel 10 over a VPC)
Fabric B fc1/31 & fc1/32 uplinked to -> NX5K-1 Port fc1/32 & NXFK-2 Port fc1/31 (san port-channel 11 over a VPC)
Thanks,
Ray.

This is not possible. Vpc is layer 2 only ethernet port channel. San port channel cannot be built accross vpc
Sent from Cisco Technical Support iPhone App

Do I configure spanning-tree port type ed trunk on LACP port-channels

Hello,
Can't seem to see a clear answer and wondering if something could offer some advice please?
We are using LACP aggregation across all our 10 gig attached servers and also trunking them. We're running a VPC pair of 5596 Nexus.
For a standard trunk port I always add the spanning-tree port type edge trunk to the interface config.
However I think I should be adding this to the overiding port-channel config. At present a colleague has configured the VPC below omitting the spanning-tree port type config.
interface port-channel100
description a-server
switchport mode trunk
switchport trunk allowed vlan 100
vpc 100
The port member configs are these which do contain the spanning tree port type:
interface Ethernet1/1
description a-server(1)
switchport mode trunk
switchport trunk allowed vlan 100
spanning-tree port type edge trunk
channel-group 100 mode active
I always try to keep the overiding port channel config the same as its members and obviously for most config, you can't have disparate configs anyway.
However for the spanning tree config the NexOS allows you to have the members with spanning tree port types and not have to reflect that in the port-channel.
However I have this issue with STP:
Switch1# show spanning-tree interface po100
Vlan Role Sts Cost Prio.Nbr Type
VLAN0100 Desg BKN*200 128.4996 (vPC) Network P2p *BA_Inc
Is this due to the inconsistency with my port channel to member configs?
Any advice would be gratefully accepted.
Thanks!

Hi Paul, there are some parameters you can define on individual ports and there are some of them that will be inherited from the port-channel configuration no matter what has been configured under the infidividual ports. Spanning-tree configuration is one of the inherited ones. As soon as the port joins into a port-channel, it will start to use spanning-tree settings under the port-channel. When it leaves the channel, then it can continue to use the individual configuration.
There is a nice summary here under NX-OS Interface Conf Guide > Port-Channel Conf:
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/interfaces/configuration/guide/if_portchannel.html#wp1798338
Evren

Which is better Different Distribution channel or different sales order typ

Hi
My requirement can be met with three config options. Kindly go through these options and suggest which one is best and why
1. Keeping one distribution channel and different sales order types.
2. Configuring different distribution channel but single sales order type.
3. Configuring different distribution channel and different sales order types.
Kindly suggest
Regards
Gaurav Jain

Hi there,
Without telling what the requirement is how can we suggest you something?
All the below options are possible in SD. Depends on the scenario to choose which is the best 1.
Regards,
Sivanand

About virtual channel in different device and/or different type channel

Hi all,
I am looking for a way to write to several analog channels at the same time. In my code, I didnt' pay much attention to that, I just have them placed in the the same frame in the flat sequence such that they might be started to write simultaneously. However, sometimes they might not working perfectly. I am reading something on DAQmx and I found that there is something call virtual channel so I have put more than 1 channel into a unit (called virtual cahnnel), so I can write something to it at the same time. Here are my question
1) what's the different between virtual channel and channel group? If I write a array of 3 elements to a channel group (consists of dev1/ao1, dev1/ao2 and dev1/ao5), am I writing to channel group or virtual channel?
2) can I bind different channels from different devices to form a virtual channel, e.g. dev0/ao0 dev1/ao0 dev2/ao0?
3) can I bind different type of channel to form a virtual channel, e.g. dev0/ao0, dev0/port0/line0?
4) last question is about synchronization on writing to a virtual channel (or channel group?) Last say I have a pulse train each pulse is separated in time by 1.2ms and total time is 122.4ms. The pulse train will be sent to dev0/ao3, and at 12ms after start send very first pulse of the train, I need to write two analog signal to dev1/ao1 and dev1/ao5. In my current code, create a flat sequence, start the task for sending the train in the first frame, put delay in second frame and delay for 12ms, write dev1/ao1 and dev1/ao5 in the third frame. For some times, this gives me acceptable timing but not always. I wonder how does it help to use virtual channel?
In the similar situtation, what about if instead of writing to two analog channel, I write to one analog channel and one digital channel?
Thanks.

1) virtual channel is created per task and contains a collection of settings such as a name, a physical channel, input terminal connections, the type of measurement or generation, and can include scaling information.. A virtual group is specific to digital IO and has to deal with the way you read/write data off/to the port
2) yes you can create a task with physical channels from multiple devices assuming they are comparable writes (ie all analog or all analog read, or all digital) but they will have the same channel characteristics (see answer above)
3) no you cannot create a task that handle an AO and a DO from with in the same task
4) if you created a task you are using a virtual channel. The only way to ensure timing is to use hardware timing (ie onboard sample clock of you DAQ card) otherwise the reads/writes are basically interrupts and you are at the mercy of the OS to service the interrupt request
if you need more information please repost with more questions, include your DAQ hardware, and any code pictures to give us a better idea of what you are trying to accomplish and how you are going about it
Applications/Systems/Test
National Instruments | AWR Group

OSPF load balancing across multiple port channels

I have googled/searched for this everywhere but haven't been able to find a solution. Forgive me if I leave something out but I will try to convey all relevant information. Hopefully someone can provide some insight and many thanks in advance.
I have three switches (A, B, and C) that are all running OSPF and LACP port channelling among themselves on a production network. Each port channel interface contains two physical interfaces and trunks a single vlan (so a vlan connecting each switch over a port channel). OSPF is running on each vlan interface.
Switch A - ME3600
Switch B - 3550
Switch C - 3560G
This is just a small part of a much larger topology. This part forms a triangle, if you will, where A is the source and C is the destination. A and C connect directly via a port channel and are OSPF neighbors. A and B connect directly via a port channel and are OSPF neighbors. B and C connect directly via a port channel and are OSPF neighbors. Currently, all traffic from A to C traverses B. I would like to load balance traffic sourced from A with a destination of C on the direct link and on the links through B. If all traffic is passed through B, traffic is evenly split on the two interfaces on the port channel. If all traffic is pushed onto the direct A-C link, traffic is evenly balanced on the two interfaces on that port channel. If OSPF load balancing is configured on the two vlans from A (so A-C and A-B), the traffic is divided to each port channel but only one port on each port channel is utilized while the other one passes nothing. So half of each port channel remains unused. The port channel on B-C continues to load balance, evenly splitting the traffic received from half of the port channel from A.
A and C port channel load balancing is configured for src-dst-ip. B is a 3550 and does not have this option, so it is set to src-mac.
Relevant configuration:
Switch A:
interface Port-channel1
description Link to B
port-type nni
switchport trunk allowed vlan 11
switchport mode trunk
interface Vlan11
ip address x.x.x.134 255.255.255.254
interface Port-channel3
description Link to C
port-type nni
switchport trunk allowed vlan 10
switchport mode trunk
interface Vlan10
ip address x.x.x.152 255.255.255.254
Switch B:
interface Port-channel1
description Link to A
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 11
switchport mode trunk
interface Vlan11
ip address x.x.x.135 255.255.255.254
interface Port-channel2
description Link to C
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 12
switchport mode trunk
interface Vlan12
ip address x.x.x.186 255.255.255.254
Switch C:
interface Port-channel1
description Link to B
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 12
switchport mode trunk
interface Vlan12
ip address x.x.x.187 255.255.255.254
interface Port-channel3
description Link to A
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10
switchport mode trunk
interface Vlan10
ip address x.x.x.153 255.255.255.254

This is more FYI. 10.82.4.0/24 is a subnet on switch C. The path to it is split across vlans 10 and 11 but once it hits the port channel interfaces only one side of each is chosen. I'd like to avoid creating more vlan interfaces but right now that appears to be the only way to load balance equally across the four interfaces out of switch A.
ME3600#sh ip route 10.82.4.0
Routing entry for 10.82.4.0/24
Known via "ospf 1", distance 110, metric 154, type extern 1
Last update from x.x.x.153 on Vlan10, 01:20:46 ago
Routing Descriptor Blocks:
x.x.x.153, from 10.82.15.1, 01:20:46 ago, via Vlan10
Route metric is 154, traffic share count is 1
* x.x.x.135, from 10.82.15.1, 01:20:46 ago, via Vlan11
Route metric is 154, traffic share count is 1
ME3600#sh ip cef 10.82.4.0
10.82.4.0/24
nexthop x.x.x.135 Vlan11
nexthop x.x.x.153 Vlan10
ME3600#sh ip cef 10.82.4.0 internal
10.82.4.0/24, epoch 0, RIB[I], refcount 5, per-destination sharing
sources: RIB
ifnums:
Vlan10(1157): x.x.x.153
Vlan11(1192): x.x.x.135
path 093DBC20, path list 0937412C, share 1/1, type attached nexthop, for IPv4
nexthop x.x.x.135 Vlan11, adjacency IP adj out of Vlan11, addr x.x.x.135 08EE7560
path 093DC204, path list 0937412C, share 1/1, type attached nexthop, for IPv4
nexthop x.x.x.153 Vlan10, adjacency IP adj out of Vlan10, addr x.x.x.153 093A4E60
output chain:
loadinfo 088225C0, per-session, 2 choices, flags 0003, 88 locks
flags: Per-session, for-rx-IPv4
16 hash buckets
< 0 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
< 1 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
< 2 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
< 3 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
< 4 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
< 5 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
< 6 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
< 7 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
< 8 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
< 9 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
<10 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
<11 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
<12 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
<13 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
<14 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
<15 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
Subblocks:
None

LACP port-channel configs

Hi,
I currently have Nexus 1000v and vSphere 5.1 and want to convert my port-channel uplink port (ESX to Catalyst 3750 stack) from static to LACP; The configs below are what I have now, and I added in BOLD what I think I need to change on both my VSM and Catalyst 3750 stack to make LACP work. Can someone confirm if the configs below are right?
Thanks you for your Help!
conf t
feature lacp
port-profile type ethernet uplink
vmware port-group
feature lacp
mtu 1500
switchport mode trunk
switchport trunk allowed vlan 10,988-989
switchport trunk native vlan 900
channel-group auto mode on
no shutdown
system vlan 10,988-989
description uplink
state enabled
And here is what I have configured on my Cisco 3750 at the other end;
interface Port-channel8
description Etherchannel connection to ESX
switchport trunk encapsulation dot1q
switchport trunk native vlan 900
switchport trunk allowed vlan 10,988,989
switchport mode trunk
switchport nonegotiate
spanning-tree portfast trunk
interface GigabitEthernet3/0/24
description 22 - nic2
switchport trunk encapsulation dot1q
switchport trunk native vlan 900
switchport trunk allowed vlan 10,988,989
switchport mode trunk
switchport nonegotiate
channel-group 8 mode on (need to change to active)
spanning-tree portfast trunk
end
interface GigabitEthernet2/0/24
description 22 - nic3
switchport trunk encapsulation dot1q
switchport trunk native vlan 900
switchport trunk allowed vlan 10,988,989
switchport mode trunk
switchport nonegotiate
channel-group 8 mode on (need to change to active)
spanning-tree portfast trunk
end

I would like to use LACP port channel instead of a static port channel, because LACP will shut down a link in case of a faulty nic (dead, driver issue, etc), instead of trying to send traffic through that link. With static port channel, one side goes down (ESX NIC) the other side (3750) does not see the link go down and still tries to send traffic, instead of hashing the address to another link.

Config port channel across different type of media

Similar Messages

Maybe you are looking for