2960 Stack Port Channel Question

I have a 2960 stack with 2 WS-C2960S-48FPD-L distribution switches running c2960s-universalk9-mz.150-2.SE2.bin.
I then have three stand alone 2960S-48 access switches running the same code.
I will have two ten Gig uplinks in a port-channel back to a 6500. I have this config. however
I would like to have port-channel between each of the distribution switches in the stack and each of the stand alone access switches.
So as an example:
distribution switches: port 1/0/48 and 2/0/48 in port channel 1
access switches: 1/0/51 and 1/0/52 in channel-group 1 active
Am I right in thinking that because these port channels come off of two different switches in a 2960 stack that they need to be LACP and the ports on the access switches need to be in "channel-group X active". And does it need to be in active mode on both sides?
Thank You in advance

Yes, both sides must have identical channel mode.

Similar Messages

Nexus 1000v port-channels questions

Hi,
I’m running vCenter 4.1 and Nexus 1000v and about 30 ESX Hosts.
I’m using one system uplink port profile for all 30 ESX Host; On each of the ESX host I have 2 NICs going to a Catalyst 3750 switch stack (Switch A), and another 2 NICs going to another Catalyst 3750 switch stack (Switch B).
The Nexus is configured with the “sub-group CDP” command on the system uplink port profile like the following:
port-profile type ethernet uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1,800,802,900,988-991,996-997,999
switchport trunk native vlan 500
mtu 1500
channel-group auto mode on sub-group cdp
no shutdown
system vlan 988-989
description System-Uplink
state enabled
And the port channel on the Catalyst 3750 are configured like the following:
interface Port-channel11
description ESX-10(Virtual Machine)
switchport trunk encapsulation dot1q
switchport trunk native vlan 500
switchport trunk allowed vlan 800,802,900,988-991
switchport mode trunk
switchport nonegotiate
spanning-tree portfast trunk
end
interface GigabitEthernet1/0/18
description ESX-10(Virtual Machine)
switchport trunk encapsulation dot1q
switchport trunk native vlan 500
switchport trunk allowed vlan 800,802,900,988-991
switchport mode trunk
switchport nonegotiate
channel-group 11 mode on
spanning-tree portfast trunk
spanning-tree guard root
end
interface GigabitEthernet1/0/1
description ESX-10(Virtual Machine)
switchport trunk encapsulation dot1q
switchport trunk native vlan 500
switchport trunk allowed vlan 800,802,900,988-991
switchport mode trunk
switchport nonegotiate
channel-group 11 mode on
spanning-tree portfast trunk
spanning-tree guard root
end
Now Cisco is telling me that I should be using MAC pinning when doing a trunk to two different stacks , and that each interface on 3750 should not be configured in a port-channel like above, but should be configured as individual trunks.
First question: Is the above statement correct, are my uplinks configured wrong? Should they be configured individually in trunks instead of a port-channel?
Second questions: If I need to add the MAC pinning configuration on my system uplink port-profile can I create a new system uplink port profile with the MAC pinning configuration and then move one ESX host (with no VM on them) one at a time to that new system uplink port profile? This way, I could migrate one ESX host at a time without outages to my VMs. Or is there an easier way to move 30 ESX hosts to a new system uplink profile with the MAC Pinning configuration.
Thanks.

Hello,
From what I understood, you have the following setup:
     - Each ESX host has 4 NICS
     - 2 of them go to a 3750 stack and the other 2 go to a different 3750 stack
     - all 4 vmnics on the ESX host use the same Ethernet port-profile
          - this has 'channel-group auto mode on sub-group cdp'
     - The 2 interfaces on each 3750 stack are in a port-channel (just 'mode on')
If yes, then this sort of a setup is correct. The only problem with this is the dependance on CDP. With CDP loss, the port-channels would go down.
'mac-pinning' is the recommended option for this sort of a setup. You don't have to bundle the interfaces on the 3750 for this and these can be just regular trunk ports. If all your ports are on the same stack, then you can look at LACP. The CDP option would not be supported in the future releases. In fact, it is supposed to be removed from 4.2(1)SV1(2.1) but I still see the command available (ignore 4.2(1)SV1(4) next to it) - I'll follow up on this internally:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_2_1_1/interface/configuration/guide/b_Cisco_Nexus_1000V_Interface_Configuration_Guide_Release_4_2_1_SV_2_1_1_chapter_01.html
For migrating, the best option would be as you suggested. Create a new port-profile with mac-pinning and move one host at a time. You can migrate VMs off the host before you change the port-profile and can remove the upstream port-channel config as well.
Thanks,
Shankar

Port-channel question on 9148

hey I have a question about port-channel.
we have a port-channel 10 which contains 4 interfaces as below.
my question is how the port-channel associated with the servers? I mean the output "sh flogi database" as below........
do we need to add port-channel as a zone member ? I think the answer is no since I don;t see the port-channel as a zone member....
=================================================================
tormds01# sh interface port-channel 10
port-channel 10 is up
    Hardware is Fibre Channel
    Port WWN is 24:0a:54:7f:ee:a0:d5:48
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is F
    Port vsan is 510
    Speed is 32 Gbps
    5 minutes input rate 124316072 bits/sec, 15539509 bytes/sec, 9919 frames/sec
    5 minutes output rate 2205921104 bits/sec, 275740138 bytes/sec, 141424 frames/sec
      43540499847 frames input, 70772376296224 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      237450525827 frames output, 442040501099476 bytes
        0 discards, 0 errors
      0 input OLS, 0 LRR, 0 NOS, 0 loop inits
      0 output OLS, 0 LRR, 0 NOS, 0 loop inits
    Member[1] : fc1/1
    Member[2] : fc1/5
    Member[3] : fc1/9
    Member[4] : fc1/13
    Interface last changed at Tue Apr 8 22:16:49 2014
tormds01# sh flogi database
INTERFACE        VSAN    FCID           PORT NAME               NODE NAME
fc1/3            510   0x860000 50:06:01:64:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spa0]
fc1/7            510   0x860100 50:06:01:6c:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spb0]
fc1/11           510   0x860200 50:06:01:60:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spa2]
fc1/15           510   0x860300 50:06:01:68:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spb2]
port-channel 10 510   0x860400 24:0a:54:7f:ee:92:3e:80 21:fe:54:7f:ee:92:3e:81
port-channel 10 510   0x860401 20:01:04:25:b5:3a:00:8f 20:01:00:25:b5:30:00:8f
                           [mcvhes0101hba0]
port-channel 10 510   0x860402 20:01:04:25:b5:3a:00:9f 20:01:00:25:b5:30:00:9f
                           [mcvhes0102hba0]
port-channel 10 510   0x860404 20:01:04:25:b5:3a:00:6f 20:01:00:25:b5:30:00:6f
                           [mcvhes0103hba0]
port-channel 10 510   0x860408 20:01:04:25:b5:3a:00:7f 20:01:00:25:b5:30:00:7f
                           [mcvhes0104hba0]
port-channel 10 510   0x86040f 20:01:04:25:b5:3a:00:4f 20:01:00:25:b5:30:00:4f
                           [mcvhes0105hba0]
port-channel 10 510   0x860410 20:01:04:25:b5:3a:00:5f 20:01:00:25:b5:30:00:5f
                           [mcvhes0106hba0]
port-channel 10 510   0x860417 20:01:04:25:b5:3a:00:2f 20:01:00:25:b5:30:00:2f
                           [mcvhes0107hba0]
port-channel 10 510   0x860418 20:01:04:25:b5:3a:00:0f 20:01:00:25:b5:30:00:0f
                           [mcvhes0109hba0]
port-channel 10 510   0x86041b 20:01:04:25:b5:3a:00:bf 20:01:00:25:b5:30:01:bf
                           [mcvhes0110hba0]
port-channel 10 510   0x86041d 20:01:04:25:b5:3a:00:1f 20:01:00:25:b5:30:00:1f
                           [mcvhes0111hba0]
port-channel 10 510   0x86041e 20:01:04:25:b5:3a:00:3f 20:01:00:25:b5:30:00:3f
                           [mcvhes0108hba0]
port-channel 10 510   0x86041f 20:01:04:25:b5:3a:00:ff 20:01:00:25:b5:30:01:ff
                           [mcvhes0112hba0]
port-channel 10 510   0x860423 20:01:04:25:b5:3a:00:df 20:01:00:25:b5:30:01:df
                           [mcvhes0113hba0]
port-channel 10 510   0x860425 20:01:04:25:b5:3a:00:ef 20:01:00:25:b5:30:01:ef
                           [mcvhes0114hba0]
port-channel 10 510   0x860426 20:01:04:25:b5:3a:00:cf 20:01:00:25:b5:30:01:cf
                           [mcvhes0115hba0]
port-channel 10 510   0x860427 20:01:04:25:b5:3a:00:8e 20:01:00:25:b5:30:01:8f
                           [MCDBWS0200hba0]
port-channel 10 510   0x860429 20:01:04:25:b5:3a:00:9e 20:01:00:25:b5:30:01:9f
                           [MCDBWS0201hba0]
port-channel 10 510   0x86042a 20:01:04:25:b5:3a:00:7e 20:01:00:25:b5:30:01:7f
                           [mcvhes0118hba0]
port-channel 10 510   0x86042b 20:01:04:25:b5:3a:00:af 20:01:00:25:b5:30:01:af
                           [mcvhes0116hba0]
port-channel 10 510   0x86042c 20:01:04:25:b5:3a:00:6e 20:01:00:25:b5:30:01:6f
                           [mcvhes0117hba0]
port-channel 10 510   0x86042d 20:01:04:25:b5:3a:00:4e 20:01:00:25:b5:30:01:4f
                           [mcvhes0119hba0]
port-channel 10 510   0x86042e 20:01:04:25:b5:3a:00:5e 20:01:00:25:b5:30:01:5f
                           [mcvhes0120hba0]
port-channel 10 510   0x860431 20:01:04:25:b5:3a:00:2e 20:01:00:25:b5:30:01:2f
                           [awotorprodsql01hba0]
port-channel 10 510   0x860432 20:01:04:25:b5:3a:00:3e 20:01:00:25:b5:30:01:3f
                           [awotorprodsql02hba0]
port-channel 10 510   0x860435 20:01:04:25:b5:3a:00:fe 20:01:00:25:b5:30:00:ef
                           [dbcactv01n3hba0]
port-channel 10 510   0x860436 20:01:04:25:b5:3a:00:de 20:01:00:25:b5:30:00:bf
                           [dbcactv01n4hba0]
port-channel 10 510   0x860439 20:01:04:25:b5:3a:00:ce 20:01:00:25:b5:30:00:8e
                           [mcvhes0123hba0]
port-channel 10 510   0x86043a 20:01:04:25:b5:3a:00:be 20:01:00:25:b5:30:00:af
                           [mcvhes0122hba0]
port-channel 10 510   0x86043c 20:01:04:25:b5:3a:00:ae 20:01:00:25:b5:30:00:9e
                           [mcvhes0124hba0]
port-channel 10 510   0x860443 20:01:04:25:b5:3a:00:8d 20:01:00:25:b5:30:00:6e
                           [mcvhes0125hba0]
port-channel 10 510   0x860445 20:01:04:25:b5:3a:00:ee 20:01:00:25:b5:30:00:cf
                           [mcvhes0121hba0]
port-channel 10 510   0x860446 20:01:04:25:b5:3a:00:9d 20:01:00:25:b5:30:00:7e
                           [mcvhes0126hba0]
port-channel 10 510   0x860447 20:01:04:25:b5:3a:00:6d 20:01:00:25:b5:30:00:4e
                           [mcvhes0127hba0]
port-channel 10 510   0x860449 20:01:04:25:b5:3a:00:7d 20:01:00:25:b5:30:00:5e
                           [mcvhes0128hba0]

I think what you do is F-Port trunking channeling !
port-channel as a zone member ? I assume you will do pwwn based zoning; in which case the answer is NO !

Port-Channel Question

I need help on a cisco config and was wondering if anyone could help me. I currently have 4 Cisco 3750 which are stacked in our server room and now I have 4 more Cisco 3750 which are stacked also in a wiring closet. I just up-linked both 3750 stacks using 4 Fiber SFP SX modules. I wanted to config a port-channel on each stack however after 5 minutes or so the switch disables the port-channel interface as a config error on the port channel.
This is my current config
interface Port-channel1
description "Uplink to 3750 Stack 2"
switchport trunk encapsulation dot1q
switchport trunk native vlan 7
switchport mode trunk
interface GigabitEthernet1/0/25
switchport trunk encapsulation dot1q
switchport trunk native vlan 7
switchport mode trunk
channel-group 1 mode on
**Update** Just as FYI we have a VoIP network in which I'm trying to do is load balance/agrigate the network traffic a cross each switch in the stack (Cross Stack EtherChannel).
Thanks for the help.

Hello Oscar,
sorry for the delay.
But presidio's post gives you the answer.
You can check this configuration on the following link:
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_guide_chapter09186a00801cdea1.html#1033981
Switch# configure terminal
Switch(config)# interface range gigabitethernet1/0/25 - 26
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 7
Switch(config-if-range)# channel-group 1 mode on
Switch(config-if-range)# end
do the same for all physical interfaces configured in the channel-group
Lets us know if it helped.
Vlad

5760 WLC cross-satck port-channels?

Hi would anyone know if cross-stack port-channels can be configured on a stack of 5760 WLC's?
I need to aggregate x4 20Gb port-channels comprised of x8 10Gb 10G-LR SFP's
Thanks

Please check the below link
http://www.cisco.com/c/en/us/td/docs/wireless/controller/5700/software/release/3se/layer2/command_reference/b_lay2_3se_5700_cr/b_lay2_32se_5700_cr_chapter_010.html

Stacking 3750s and Port Channel

We're replacing legacy switches with 3750s in the coming months, and I have a question about stacking and port channel.
The 3750s will be Layer 2 switches, and each will be uplinked via Gigabit fiber to a pair of 6500s acting as Layer 3 distribution switches.
One thing I'm not sure about is if it will be possible to built Port Channel links for 2, 3, or 4 GB across different switches, or if I can only put Port Channels on the same switch. My understanding is with stacking it appears as one big switch and I can built Port Channels however I want, but am not 100% if this design will work.

You can certainly configure EtherChannels across different 3750s in the same stack, thus avoiding your single point of failure by having the aggregate ports all in one switch.
However in the scenario the port channel has to be configured explicitly to ON, PaGP is not supported across stack members.
3750 stack switches appear as a single logical switch with a single management address. From which you can configure all physical ports. It is important to remember that you configure your switch priorities accordingly in order to govern which switch is your master, and also set a secondary.
Regards
Allan.
Please kindly rate this post if you find this information helpful.

Port Channel Issue on Cisco 2960s-24ts

Hi All
Last week at a customer site we installed a 2nd 2960s 24 port switch to form a stack using flexstack cables, and the switch stack is working as expected as I can see a master switch and 2nd switch as a member.
For redundancy / resilience we decided to use port 24 on each switch over copper for trunk uplinks to our core switch. The issue that we're having is I can't ping the switch management address. I can however see the address in the arp table and the edge switch is visible when I run show cdp nei. As a work around I've shutdown one of the ports to the downlink from core to edge in order to ping the management address of the switch which is in vlan 1. I'd like to get the port-channel working on both sides for resilience.
ANY HELP IS APPRECIATED...
Core switch is a WS-C3750G-24TS-1U running software version C3750 Boot Loader (C3750-HBOOT-M) Version 12.2(25r)SEE4, C3750 Software (C3750-IPBASE-M)
Edge switch is a WS-C2960S-24TS-L running software version C2960S Boot Loader (C2960S-HBOOT-M) Version 12.2(53r)SE,C2960S Software (C2960S-UNIVERSALK9-M)
The config on the edge switch which goes to the core is :
interface GigabitEthernet1/0/24
description *****
switchport mode trunk
channel-group 6 mode on
end
interface GigabitEthernet2/0/24
description *****
switchport mode trunk
channel-group 6 mode on
end
interface Port-channel6
description ******
switchport mode trunk
end
The config on the downlink ports from the core to the edge:
interface GigabitEthernet1/0/20
description Edge
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 20 mode on
end
interface GigabitEthernet2/0/20
description Edge
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
channel-group 20 mode on
end
interface Port-channel20
description Edge
switchport trunk encapsulation dot1q
switchport mode trunk
end

when using channel-group # on mode you must make sure the ports are on same duplex and speed setting
what happens when you use active mode?

3750-2960 Vlans Issue via Port Channel

Im trying to get all my vlans to pass thru to my 2960 user level switches, from my 3750 stack.
Each one of my 2960 stack is connected to my 3750 via port channel. Here is my port setup.
I have Vlans 1,210,214,216,220,306,406 on my 3750 stack. I cannot see those vlans on my 2960 stack. Why is that? What am I missing from the config?
Thanks...
3750 ports:
interface GigabitEthernet1/0/41
description Uplink to ETHSW03
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,210,214,216,220,306,406
switchport mode trunk
snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree guard loop
channel-protocol lacp
channel-group 7 mode active
interface GigabitEthernet1/0/42
description Uplink to ETHSW03
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,210,214,216,220,306,406
switchport mode trunk
snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree guard loop
channel-protocol lacp
channel-group 7 mode active
interface Port-channel7
description Uplink to ETHSW03
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,210,214,216,220,306,406
switchport mode trunk
snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree guard loop
Here are my 2960 ports setup:
interface GigabitEthernet1/0/47
description Uplink to CORE01
switchport trunk allowed vlan 1,210,214,216,220,306,406
switchport mode trunk
snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree guard loop
channel-protocol lacp
channel-group 1 mode active
interface GigabitEthernet1/0/48
description Uplink to CORE01
switchport trunk allowed vlan 1,210,214,216,220,306,406
switchport mode trunk
snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree guard loop
channel-protocol lacp
channel-group 1 mode active
interface Port-channel1
description Uplink to CORE01
switchport trunk allowed vlan 1,210,214,216,220,306,406
switchport mode trunk
snmp trap mac-notification change added
snmp trap mac-notification change removed
spanning-tree guard loop

I have 1 stack of 3750, connected with flex technology.
I have 3 stacks of 4-2960s, connected with flex technology.
Then, each 2960 stack is connected to my 3750 stack via port channels (gig ports x2).
Now, this is a second office site. We are connected to our datacenter via private ethernet line, and thats where most of our vlans and servers reside.
Output from 3750
P-DB-CORE01#sh vtp status
VTP Version capable             : 1 to 3
VTP version running             : 1
VTP Domain Name                 : NULL
VTP Pruning Mode                : Disabled
VTP Traps Generation            : Disabled
Device ID                       : 6c41.6a9c.a280
Configuration last modified by 10.2.20.1 at 3-3-93 23:43:55
Feature VLAN:
VTP Operating Mode                : Transparent
Maximum VLANs supported locally   : 1005
Number of existing VLANs          : 19
Configuration Revision            : 0
MD5 digest                        : 0x3D 0x05 0x4D 0x8C 0x31 0x07 0x34 0xDA
                                    0x2F 0x60 0xE8 0x24 0xA6 0x27 0x59 0x24
Output from 2960
P-ETHSW03-20.4#sh vtp status
VTP Version capable             : 1 to 3
VTP version running             : 1
VTP Domain Name                 : NULL
VTP Pruning Mode                : Disabled
VTP Traps Generation            : Disabled
Device ID                       : c07b.bcb2.9a80
Configuration last modified by 10.2.20.2 at 1-3-14 13:02:15
Local updater ID is 10.2.20.4 on interface Vl1 (lowest numbered VLAN interface found)
Feature VLAN:
VTP Operating Mode                : Server
Maximum VLANs supported locally   : 255
Number of existing VLANs          : 7
Configuration Revision            : 5
MD5 digest                        : 0x89 0x91 0xBA 0xE3 0x12 0x1B 0xDB 0x1D
                                    0x75 0x43 0x7F 0x8D 0x62 0x5A 0x09 0x70

Port channel from 2960 to Cisco Core 6513

I have a Cisco 6513 Core Switch, which is in a vtp domain and the core is the Server. There are a number of other port channels going from the 6513 to other 2960 switch stacks. The other switch stacks are in vtp client mode and are getting all vlans form the Server 6513 within this vtp domain.
I am trying to connect 2 - 2960S FPD L switches, which are connected together via flex module/flex cable. I have 2 sfp's in the sfp ports on one of these switches and am creating one port channel of 20G(2 10G ports Te1/0/1 and Te1/0/2) going to two 10Gig ports on the Cisco 6513(Te9/7 and Te9/8) as a port channel created on the 6513 end.
I want to know first of all if it is possible to keep the 2960's in transparent mode and only allow 2 vlans to go to these 2 2960's. I don't need all vlans on these switches, and the other 2960 stacks going to the 6513 do have all vlans and are in the vtp domain. This one would only all vlans 4, and 20.
Can someone give me an example of the setup on each end to make this work? I have tried and get a subnet mask error, so I must be going something wrong. The vlans: vlan 4: 10.35.3.0/22 and vlan 20 : 10.35.20.0/24 would be the only ones I would want to tag ports for on these 2 2960 switches in transparent mode.
Wanted to also setup a management interface for vlan 20 so I can remotely connect to 2960 stack. It would be 10.35.20.30 for the int management IP.
Thanks in advance
Dave

Many Cisco switches support two methods of trunking - dot1q and ISL. ISL is a Cisco-proprietary method of trunking. The 2960's do not support ISL, so dot1q is on by default. There's no need for the trunk encapsulation command.
When a frame is transferred over a trunk, dot1q trunking adds a tag to the frame so that the receiving switch knows which vlan the frame belongs to. Your native vlan is a special vlan which does not have a tag applied. Among other things, it's used for administrative traffic between the switches such as the messages the switches exchange to negotiate a port channel. You can use one of your two vlans - vlan 4 or 20 - as your native vlan but it's recommended that you use a different vlan to segregate the traffic. If you do not specify a native vlan, the switch will use vlan 1 as the native. It's considered more secure to not use vlan 1 on your network, so it's recommend to have a different vlan explicitly configured as native. If you're using vlan 1 as native through the rest of the network - if none of your other trunks have a native vlan explicitly configured - it doesn't do much good to change it on this one trunk. You do not have to explicitly allow the native vlan on the trunk. If you leave your native vlan as 1 and allow vlans 4 and 20 it will work fine. You might want to do some research on the security implications and consider changing it through the whole network but that's a separate issue from getting this to work.
Port channel numbers are locally significant. They don't have to match on opposite ends of the channel, they just have to be the same on each interface of a particular switch. You can use either mode desirable or mode on. It changes the way the switches set up the port channel a little bit but it doesn't change the way the channel operates.

Configuring Port Channel on Cisco 2960S-48LPS-L

When I try to move port channel connections to two of the SFP ports on our Cisco 2960S switch, one of the connections fail.
I am using two GBics, both are the same, GLC-T-A 1000Base-T.
The port channel work fine when I use g1/0/47 and 48.
The port channel work fine when using g1/0/48 and SFP 1/0/49
Port channel does not work when using SFP 1/0/49 and SFP 1/0/50.

Cisco C2960S software version: 12.2(55)SE7. Using C2960S-UNIVERSALK9-M.
Port configurations for g1/0/48 - 51:
interface GigabitEthernet1/0/49
description Trunk to Cisco Core
switchport mode trunk
srr-queue bandwidth share 1 30 35 5
priority-queue out
mls qos trust cos
macro description cisco-switch
auto qos trust
spanning-tree link-type point-to-point
channel-group 2 mode on
When working, both ports show green status lights.
ort      Name               Status       Vlan       Duplex Speed Type
Po2       Trunk to Core      connected    trunk      a-full a-1000
*: interface is up
IHQ: pkts in input hold queue     IQD: pkts dropped from input queue
OHQ: pkts in output hold queue    OQD: pkts dropped from output queue
RXBS: rx rate (bits/sec)          RXPS: rx rate (pkts/sec)
TXBS: tx rate (bits/sec)          TXPS: tx rate (pkts/sec)
TRTL: throttle count
Interface               IHQ   IQD OHQ   OQD RXBS RXPS TXBS TXPS TRTL
* Port-channel2            0     0    0     0 8390000 909 970000 551    0
Age of the Port-channel   = 0d:10h:57m:35s
Logical slot/port   = 5/2          Number of ports = 2
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =    -
Port security       = Disabled
Ports in the Port-channel:
Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
0     00     Gi1/0/47 On                 0
0     00     Gi1/0/49 On                 0
When not working, one port shows green, then other port status light is off.
GigabitEthernet1/0/49 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 3c0e.233f.a531 (bia 3c0e.233f.a531)
Description: Trunk to Cisco Core
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 1000Mb/s, link type is auto, media type is 10/100/1000BaseTX SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:09, output 00:00:19, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1954000 bits/sec, 213 packets/sec
5 minute output rate 38000 bits/sec, 16 packets/sec
     2935639 packets input, 880524431 bytes, 0 no buffer
     Received 2211794 broadcasts (310067 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 310067 multicast, 0 pause input
     0 input packets with dribble condition detected
             370489 packets output, 66729219 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out
GigabitEthernet1/0/50 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is 3c0e.233f.a532 (bia 3c0e.233f.a532)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Auto-duplex, Auto-speed, link type is auto, media type is Not Present
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     0 packets output, 0 bytes, 0 underruns
--More--              0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out
Let me know if you need more info.

Port-channel configuration 3560X and 2960S

Hello,
I am trying to connect a 2960 swith to 3560X using port channel. I have configred the switches with the following configratuion and connected them with straight ethernet cable, the link came up and then it went int err-disable state. I re-enabled the links and connected them using one cross over cable it connected and remained connected for a whole day in my lab. When I shut down both switches and took them the server room and connected both ports using cross over cable it came up and then went into err-disable state. Bellow is my configuration, can you please point out to me what I am missing: (no VTP domain configured on any of the switches)
------------------2960 configuration----------------------
interface Port-channel1
switchport trunk native vlan 999
switchport mode trunk
interface GigabitEthernet1/0/51
switchport trunk native vlan 999
switchport mode trunk
channel-group 1 mode on
interface GigabitEthernet1/0/52
switchport trunk native vlan 999
switchport mode trunk
channel-group 1 mode on
------------------3560X configuration-------------------------------
interface Port-channel1
switchport trunk encapsulation dot1q
switchport trunk native vlan 999
switchport mode trunk
interface GigabitEthernet0/23
switchport trunk encapsulation dot1q
switchport trunk native vlan 999
switchport mode trunk
channel-group 1 mode
interface GigabitEthernet0/24
switchport trunk encapsulation dot1q
switchport trunk native vlan 999
switchport mode trunk
channel-group 1 mode on
Thank you.

Hi,
Your condig looks good and straightthrough cable should work just fine. Can you do the following:
take the interfaces out of the portchannel
shut the portchannel
shut the interfaces
add the interfaces to the portchannel
"no sh" the PO and test again?
This should bring up the interface and the portchannel
HTH

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.

N7K Port Channel Layer 3 VLAN Question

I have 2 N7K switches and would like to connect them via port channel and put the channel in VLAN 101. I have the following config, does it make sense? Thanks in advance!
interface eth 3/1
switchport
channel-group 101 mode active
interface eth 3/2
switchport
channel-group 101 mode active
interface port-channel 101
switchport
switchport mode access
switchport access vlan 10
spanning-tree network type edge
interface vlan 10
ip address 10.1.1.1/24

Could be something like this in the both sides (if the port numbers match):
conf t
feature lacp
feature interface-vlan
interface eth 3/1
switchport
channel-group 101 mode active
interface eth 3/2
switchport
channel-group 101 mode active
interface port-channel 101
switchport
switchport mode access
switchport access vlan 101
spanning-tree port type network
interface vlan 101
ip address 10.1.1.1/24
no shut
end
vlan 101
end
*(This ip address will be available in only one box, you can use a FHRP as well, to increase the level of reachability)

SGE2010 port-channel and trunking config question

I have port-channels configured and working for the native VLAN on multiple SGE2010s. I now want to add multiple VLANs and enable trunking for the port-channel. I am not clear on the appropriate way to enable trunking as it can be enabled on the port and on the port-channel. The ports and port-channel are currently in access mode. If anyone can provide the correct configuration, I would appreciate the guidance. I also need to get the port-channels and trunking working with 3Com 4500 & 4200s. If you know of any configuration issues, again any guidance would be appreciated

Hi Jacqueline,
Sorry Juans answer needs some correction, but I am grateful for Juans participation.
The SGE2010 does not support a CLI.
There is a unsupported CLI, that someone plastered somehwere on this community, but i must admit i still like to use the GUI.
The software on the SGE2XXX was recently updated so you can find that on the cisco.com website.
I have created a link below to a recording i just made, regarding Link aggregation on the SGE2XXXX, i thnk if you see the 11 minute recording a couple of times, maybe pause it, play with your switch, it will start to make sense.
you can't breat the switch by configuring it
click here to see a recording of me creating a Link aggregation between two switches
regards Dave

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.

2960 Stack Port Channel Question

Similar Messages

Maybe you are looking for