Hi Jessie,
You are running RSTP, which sends version 2 BPDUs. If the switch receives on a port version 0 BPDU (i.e. regular STP BPDUs), it will go to an STP compatibility mode and will start sending version 0 BPDUs on this port.
So basically, what you are seeing is that all your neighbors are running STP, except the one connected to Po31 who is running RSTP.
Regards,
Francois

Similar Messages

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

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

Peer-Switch with vPC and non-vPC Vlan Port-Channels

Hi,
in a design guide i have noticed that it is best practice to split vPC and non-vPC vlans on different inter-switch port-channels. Now, if i want to use the Peer-Switch function, but the port-channel interface of the non-vPC-vlan channel moves into blocking state. The option spanning-tree pseudo-information has no influence. Is peer-switch possible in my kind of topology?
Greeting,
Stephan

I believe absolutly possible. specifically coz peer-switch and spt pseudo-info are specific and local to cisco fabric services running as part of vpc technology. Personally me has lab with vpc-domain compounded of 2 N5Ks. They are peer-switches with spt-pseudoinfo and they have MST running on non VPC links independantly from vpc.

Nexus 6004: Question about port-profile type port-channel

I'm setting up a new deployment of Nexus 6004 switches and want to utilize port-profiles as much as possible to simplify management down the road.
All uplinks to other switches, routers and firewalls will be connected using VPC:s. On the port-channels (vpc) the only thing that will change over time is the allowed vlans.
It seems that port-profiles of the type port-channel does not behave in the same way as those with type ethernet, at least not when adding vlans.
If I modify the port-profile using "switchport trunk allowed vlan add XXX" it will delete the previous config and only retain "switchport trunk allowed vlan add XXX", and not merge it with the previous config as is expected.
Question: Is this a bug or is it working as intended?
RH_N6K4_01(config-sync)# switch-profile rh
Switch-Profile started, Profile ID is 1
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan 3
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
assigned interfaces:
===================================
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan add 84
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
assigned interfaces:
Expected behavior here would be "switchport trunk allowed vlan 3,84". This only occurs when using "port-profile type port-channel" not when using "port-profile type ethernet"

<> is template syntax and is generally the type of object a container holds.. So it is defining that the MSGQUEUE type is a deque holding struct_buffer*'s.

Interface port-channel btw N2K and Brocade VDX

Dear all,
I tried to configure a port-channel between a nexus 2K (2FEX) and a brocade VDX (VDX6710).
As you seen below, my configuration :
N2K
Po10
switchport access vlan 200
Eth101/1/6
switchport access vlan 200
channel-group 10 mode active (used LACP)
Eth102/1/6
switchport access vlan 200
channel-group 10 mode active (used LACP)
VDX
interface Port-channel 27
vlag ignore-split
speed 1000
switchport
switchport mode access
switchport access vlan 200
spanning-tree shutdown
no shutdown
interface GigabitEthernet 21/0/31
channel-group 27 mode active type standard
lacp timeout long
no shutdown
interface GigabitEthernet 22/0/31
channel-group 27 mode active type standard
lacp timeout long
no shutdown
Unfortunately, we can't up the link for interfaces and so the port-channel.
We have the next message from the N5K for FEX :
%ETHPORT-5-IF_ADMIN_UP: Interface Ethernet101/1/6 is admin up .
%ETHPORT-5-SPEED: Interface Ethernet101/1/6, operational speed changed to 1 Gbps
%ETHPORT-5-IF_DUPLEX: Interface Ethernet101/1/6, operational duplex mode changed to Full
%ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet101/1/6, operational Receive Flow Control state changed to off
%ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet101/1/6, operational Transmit Flow Control state changed to on
%ETHPORT-5-IF_UP: Interface Ethernet101/1/6 is up in mode access
%ETHPORT-5-IF_DOWN_NONE: Interface Ethernet101/1/6 is down (None)
%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/6 is down (Error disabled. Reason:BPDUGuard)
Any idea about the configuration ?
Thanks for your help.
Matthieu

Fexes are really made to connect hosts and not switches . So the ports should not see bpdu's so bpduguard is err-disabling the ports.
Spanning Tree Protocol
HIFs go down with the BPDUGuard errDisable message
HIFs go down accompanied with the message, BPDUGuard errDisable.
Possible Cause
By default, the HIFs are in STP edge mode with the BPDU guard enabled. This means that the HIFs are supposed to be connected to hosts or non-switching devices. If they are connected to a non-host device/switch that is sending BPDUs, the HIFs become error-disabled upon receiving a BPDU.
Solution
Enable the BPDU filter on the HIF and on the peer connecting device. With the filter enabled, the HIFs do not send or receive any BPDUs. Use the following commands to confirm the details of the STP port state for the port:

Configuring 9222i for Port-Channels to 6500

I need to configure an MDS 9222i to do EhterChannel for redundant links to a Cisco 6500. I have tried to configure channel-group on the GE interface and I get an error (see below)
b0maumigrjax(config-if)# channel-group 1
command failed: Member list of different interface types not supported [created]
9222i Config
interface port-channel 1
channel mode active
switchport rate-mode dedicated
interface GigabitEthernet1/1
ip address 1.1.1.10 255.255.255.0
switchport description Core.Link.Connection.22
no shutdown
interface GigabitEthernet1/2
ip address 1.1.1.1.11 255.255.255.0
switchport description Core.Link.Connection.23
no shutdown
6500 Config
Interface Port-Channel 1
sw acc vlan 10
interface GigabitEthernet1/2
channel-group 1 mode active
no shut
interface GigabitEthernet1/1
channel-group 1 mode active
no shut

David,
I tried that as well. I still was not able to get the interface's to come up in sh ether summ on the switch.
fcip profile 1
ip address 10.136.120.10
tcp max-bandwidth-mbps 50 min-available-bandwidth-mbps 20 round-trip-time-ms 5
fcip profile 2
ip address 10.136.120.11
tcp max-bandwidth-mbps 50 min-available-bandwidth-mbps 20 round-trip-time-ms 5
interface fcip1
use-profile 1
peer-info ipaddr 10.136.120.13
channel-group 1 force
no shutdown
interface fcip2
use-profile 2
peer-info ipaddr 10.136.120.14
channel-group 1 force
no shutdown

Port Channel in Nexus

Hi All,
I have a scenario where I have two nexus 5596 as upstream and have vPC in between. downstream is the server hooking to the upstrean both nexus devices.
On Both the Nexus switch the port channel is down and the VPC is also down. The physical interfaces are up and passing traffic to the server.
My understanding is if the server NIC's are teamed, even the switches should also have the portchannle to work properly.
But since portchannel and vpc both are down in both the switches
1. how the switch is passing traffic.
2. I checked the configs for portchannel formation on phy ports which looks good to me still po is down. Why?
3. I understand as port channel is down so vPC is down ( correct me if I am wrong).
I have attached the diagram & below are the logs for ur reference:
The output on Nexus5596 2 device is same as on Nexus5596 1
Nexus5596 1#Sh vpc
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link
vPC domain id                   : 106
Peer status                     : peer adjacency formed ok
vPC keep-alive status           : peer is alive
Configuration consistency status: success
Per-vlan consistency status     : success
Type-2 consistency status       : success
vPC role                        : primary
Number of vPCs configured       : 29
Peer Gateway                    : Disabled
Dual-active excluded VLANs      : -
Graceful Consistency Check      : Enabled
vPC Peer-link status
id   Port   Status Active vlans
1    Po4    up     1-2,713-718,999
vPC status
id     Port        Status Consistency Reason                     Active vlans
9      Po9         up     success     success                    2,713-718
701    Po701       down* success     success                    -
702    Po702       down* success     success                    -
Nexus5596 1# sh port-channel su
Group Port-       Type     Protocol Member Ports
      Channel
4     Po4(SU)     Eth      LACP      Eth1/27(P)   Eth1/28(P)
9     Po9(SU)     Eth      LACP      Eth1/29(P)   Eth1/30(P)   Eth1/31(P)
                                                    Eth1/32(P)
701   Po701(SD)   Eth      LACP      Eth1/1(I)
702   Po702(SD)   Eth      LACP      Eth1/2(I)
Nexus5596 1#sh run int e1/1
interface Ethernet1/1
description snrkdc1285_1/0
switchport mode trunk
switchport trunk native vlan 713
switchport trunk allowed vlan 713-718
spanning-tree port type edge trunk
no snmp trap link-status
channel-group 701 mode active
Nexus5596 1# sh int e1/1 status
Port          Name               Status    Vlan      Duplex Speed   Type
Eth1/1        snrkdc1285_1/0     connected trunk     full    10G     10Gbase-SR
Thanks,
Sagar

Reza - My bad I mistakenly mentioned e1/10 in diagram but it is e1/1 for po701
Since these are L2 switches SH IP INT BR shows only mgmt Ip
Please find the requested outputs as below.
nexus5596 1#sh run int po701
interface port-channel701
description snrkdc1285
switchport mode trunk
switchport trunk native vlan 713
switchport trunk allowed vlan 713-718
spanning-tree port type edge trunk
speed 10000
no snmp trap link-status
vpc 701
nexus5596 2# sh run int po701
interface port-channel701
description snrkdc1285
switchport mode trunk
switchport trunk native vlan 713
switchport trunk allowed vlan 713-718
spanning-tree port type edge trunk
speed 10000
no snmp trap link-status
vpc 701
nexus5596 1#sh int br
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        713     eth trunk up      none                        10G(D) --
Eth1/2        713     eth trunk up      none                        10G(D) --
Port-channel VLAN    Type Mode   Status Reason                    Speed   Protocol
Interface
Po4          1       eth trunk up      none                       a-10G(D) lacp
Po9          2       eth trunk up      none                       a-10G(D) lacp
Po701        713     eth trunk down    No operational members       10G(D) lacp
Po702        713     eth trunk down    No operational members       10G(D) lacp
nexus5596 2#sh int br
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        713     eth trunk up      none                        10G(D) --
Eth1/2        713     eth trunk up      none                        10G(D) --
Port-channel VLAN    Type Mode   Status Reason                    Speed   Protocol
Interface
Po4          1       eth trunk up      none                       a-10G(D) lacp
Po9          2       eth trunk up      none                       a-10G(D) lacp
Po701        713     eth trunk down    No operational members       10G(D) lacp
Po702        713     eth trunk down    No operational members       10G(D) lacp

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

Disappointed: ASA 8.4 Redundant using Port-channels

So I finally got all our ASAs upgrade to version 8.4 and was all sorts of excited to configure port-channels to our 6500 + SUP7203B switches. I was severally disappointed to discover that I cannot configure two port-channels and have them be members of a redundant interface pair. It would seem like a logical topology.
Port-channel1 = Gig0/0 & Gig0/1
Port-channel2 = Gig0/2 & Gig0/3
Redundant1 = Port-channel1 & Port-channel2
Port-channel1 would connect to the primary 6500
Port-channel2 would connect to the backup 6500
What would it take to make this work? Am I going to have to wait for 8.5? Will we finally get BGP then too? (Had to get that in there)
http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/interface_start.html#wp1329357
EtherChannel Guidelines
•You can configure up to 48 EtherChannels.
•Each channel group can have eight active interfaces. Note that you can assign up to 16 interfaces to a channel group. While only eight interfaces can be active, the remaining interfaces can act as standby links in case of interface failure.
•All interfaces in the channel group must be the same type and speed. The first interface added to the channel group determines the correct type and speed.
•The device to which you connect the ASA 5500 EtherChannel must also support 802.3ad EtherChannels; for example, you can connect to the Catalyst 6500 switch.
•All ASA configuration refers to the logical EtherChannel interface instead of the member physical interfaces.
•You cannot use a redundant interface as part of an EtherChannel, nor can you use an EtherChannel as part of a redundant interface. You cannot use the same physical interfaces in a redundant interface and an EtherChannel interface. You can, however, configure both types on the ASA if they do not use the same physical interfaces.

Hello Yaplej,
Agree with you but unfortunetly this is not supported yet,
We migh need to wait some time before this desing can be accomplish,
Regards,
If you do not have any other question please mark the question as answered

Dlsw using port channel

I have 2 dlsw router at head quater office, named dlswA and dlswB.
From branches router, dlswA is a primary peer and dlswB is a backup peer.
Both dlswA and B have 2 fast ethernet interfaces.
The current configuration of dlswA and dlswB are 1 port as IP port and other port as sna/bridge port.
With this configuration the problem is when SNA port at dlswA problem, then dlsw circuit will have the problem, because dlsw peer from branches still connected to dlswA.
if I configure 2 fast ethernet port become a port channel. And configure IP and bridge group at port channel interface (IP and SNA at the same interfaces), so when the port channel is down, then branches will connect to dlswB as a backup peer
Are the port channel configuration will solve the problem ? How about the stability of this configuration?

Thank Matthias for your reply.
Both of head end routers are on the same vlan and the host is using same mac address.
As far as i know if from branch have 2 active peer with cost setup, there will loops posibility because both head end routers are using ethernet with same vlan and same host mac address.
I test the port channel within my LAB using netbios, seem works as expected. when single port at port channel down, branch circuit still remain at dlswA router, when all port channel member down, the branch peering move to dlswB.
Here are the config:
hostname dlswA
dlsw local-peer peer-id 192.168.255.1 promiscuous
dlsw bridge-group 1
interface Port-channel10
ip address 192.168.255.1 255.255.255.248
bridge-group 1
interface FastEthernet0/0
no ip address
duplex auto
speed auto
channel-group 10
interface FastEthernet0/1
no ip address
duplex auto
speed auto
channel-group 10
end
hostname dlswB
dlsw local-peer peer-id 192.168.255.10 promiscuous
dlsw bridge-group 1
interface Port-channel11
ip address 192.168.255.10 255.255.255.248
bridge-group 1
interface FastEthernet0/0
no ip address
duplex auto
speed auto
channel-group 11
interface FastEthernet0/1
no ip address
duplex auto
speed auto
channel-group 11
end
Hostname Branch
dlsw local-peer peer-id 172.16.0.1
dlsw remote-peer 0 tcp 192.168.255.1
dlsw remote-peer 0 tcp 192.168.255.10 backup-peer 192.168.255.1 linger 0
dlsw bridge-group 1
interface Loopback0
ip address 172.16.0.1 255.255.255.255
interface FastEthernet0/1
no ip address
duplex auto
speed auto
bridge-group 1
But I'm not sure this scenario will work for sna application like ATM machine, and SNA SAA gateway.
Please kindly advised, Is there any alternatif ?

Nexus 7010 port-channel to ESXi host running on Dell 910 and 810

Was wondering has anyone had any experience with configuring a port-channel going back to ESXi host. My basic config is below. My issue is with what to put in the spanning-tree port type. Do I use normal, edge, network, or edge trunk?? Yes I have read most of the documentation out there but am just a lil confused. I just wanna be right.
Also if anyone has any suggestions for the Vswitch config as well that would be much appreciated.
int PO 201
desc 01_6-1
switchport mode trunk
switchport access vlan 99
switchport trunk native vlan 777
switchport trunk allowed vlan 220,300,310,320-321,350,390-391
switchport trunk allowed vlan add 420,777
spanning-tree port type normal (what should go here)
speed auto
medium p2p
no shutdown
int e8/11
desc 01_6-1
channel-group 201 force
int e10/11
desc 01_6-1
channel-group 201 force
Thanks Guys

Short answer: You could use spanning tree port type edge (trunk; if it's going to be a trunk). The vswitch isn't really a switch, it doesn't participate in spanning tree, so it's fine to make it an edge port.
In my experience, many VMware guys don't like port channels as much as the other more host-centric NIC teaming methods. I think this has to do with ESX having a less than stellar implementation of etherchannel/LACP early on.

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

Port Channels - WLC 5508 and 4510

LACP and PAgP are not supported on the controller and it appears that the 4500 series will not use LAG.
interface Port-channel10
description WLC Port-Channel
switchport
switchport mode trunk
service-policy input AutoQos-4.0-Input-Policy
service-policy output OUTPUT-PRIORITY-POLICING-ETHERCHANNEL
interface GigabitEthernet3/1
description Cisco 5508 Wireless Controller
switchport mode trunk
channel-group 10 mode active
spanning-tree link-type point-to-point
interface GigabitEthernet3/2
description Cisco 5508 Wireless Controller
switchport mode trunk
channel-group 10 mode active
spanning-tree link-type point-to-point
I am getting the error, "lacp not enabled on remote port..". I removed the 2nd fiber cable and removed the channel-group so I could get the WLC back online. Any help would be greatly appreciated.

In order to get the ether channel to work with the WLC you need to change your configuration from:
interface GigabitEthernet3/1
channel-group 10 mode active
interface GigabitEthernet3/2
channel-group 10 mode active
To mode ON
interface GigabitEthernet3/1
channel-group 10 mode on
interface GigabitEthernet3/2
channel-group 10 mode on
Mode ON tells the switch to do Link Aggregation Protocol and does try and negotiate using one of the two control protocols LACP or PAgP.
using mode ON is part of the configuration guide when enabling Cisco WLC LAG option.

ASA port-channel command on IOS v. 9.0(4)

I have configured 2 of ASA 5550 on a port channel as follows:
=======================================
router# show version
Cisco Adaptive Security Appliance Software Version 8.4(2)
router# show module
0 ASA 5550 Adaptive Security Appliance         ASA5550            JMX1226L1S9
1 SSM-4GE Included with ASA 5550 System        SSM-4GE-INC        JAF1224ATNS
router# show interface Port-channel48
Interface Port-channel48 "", is up, line protocol is up
Hardware is EtherChannel/ON, BW 2000 Mbps, DLY 10 usec
    Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
    Input flow control is unsupported, output flow control is off
    Media-type configured as RJ45 connector
    Available but not configured via nameif
    MAC address 001f.ca97.44e2, MTU not set
    IP address unassigned
Members in this channel:
      Active:   Gi1/2 Gi1/3
router# show startup-config
interface GigabitEthernet1/2
channel-group 48 mode on
no nameif
no security-level
no ip address
interface GigabitEthernet1/3
channel-group 48 mode on
no nameif
no security-level
no ip address
interface Port-channel48
no nameif
no security-level
no ip address
interface Port-channel48.4
vlan 4
interface Port-channel48.5
vlan 5
After migrating to version 9.0(4) I could not configure channel group on int g 1/2.
=======================================
router# show version
Cisco Adaptive Security Appliance Software Version 9.0(4)
router# show module
0 ASA 5550 Adaptive Security Appliance         ASA5550            JMX1421L333
1 SSM-4GE Included with ASA 5550 System        SSM-4GE-INC        JAF1419ALAK
router# configure terminal
router(config)# interface GigabitEthernet1/2
router(config-if)# channel-group 48 mode on
                      ^
ERROR: % Invalid input detected at '^' marker.
router(config-if)# ?
So I have the following questions about verion 9:
1. Can I still use port-channels on a sigle ASA?
2. Should I replace port-channel by lacp command on a sigle ASA?
3. Does lacp command can be used only on clusters ?
Att.,
Rosa

The following is documented in the config guide for both 8.4 and 9.0:
•You cannot use interfaces on the 4GE SSM, including the integrated 4GE SSM in slot 1 on the ASA 5550, as part of an EtherChannel.
So, even with 8.4 it was probably never meant to work.

Port-channel - type Peer STP

Similar Messages

Maybe you are looking for