WAAS Port Channel Configuration

In the recent weeks we got some reports that CIFS writing performance to NETAPP OnTap 7.3 filer was degraded for WAAS accelerated connections. NETAPP OnTAP 7.2 and native Microsoft filers were running fine. In our Testlab we could correlate this issue with the port channel setup on our WAAS devices. With round robin (standard setting) the CIFS writing perforamce was poor. By switching the port channel loadbalancing to src-dst-ip-port the performance was excellent.
Is there any known best practices recommendation for port channel configuration on WAAS devices?
Many thanks in advance, Peter.

The best practice depends on your network. Most deployments are fine with the default round robin configuration for port channel on the WAE. But I have encountered some installations where the configuration had to be changed in order to avoid out of order packets causing slow performance (like, if there is a firewall between the WAE and the server).
Sent from Cisco Technical Support iPhone App

Similar Messages

Clearing port channel configurations

In one of my 6509s I've got a lot of old port channel configs listed that I can't remove. How do I remove them short of clearing the config entirely?
Here's an example...
set port channel 3/41-42 64
set port channel 3/43-44 65
set port channel 6/47-48 67
set port channel 3/13-14 68
set port channel 9/5-6 86
set port channel 9/9-11 87
set port channel 2/2 93
set port channel 7/1-4 100
set port channel 7/25-28 106
set port channel 7/37-40 109
set port channel 7/41-44 110
set port channel 7/45-48 111
set port channel 4/5-8 112
set port lacp-channel 5/22,5/45 126
set port channel 6/29-30 127
set port channel 9/13-14 128
set port channel 9/12 129
set port channel 9/15-16 161
set port channel 4/41 537
set port channel 6/31-32 538
set port channel 8/1-4 661
set port channel 9/1-4 665
set port channel 1/1,2/1 719
set port channel 8/11-12 720
set port channel 8/13-16 721
set port channel 8/9-10 722
set port channel 8/7-8 723
set port channel 8/5-6 725
set port channel 4/9-12 726
set port channel 3/5-8 731
set port channel 3/1-4 732
set port channel 4/1-4 733
set port channel 9/7-8 734
set port channel 3/15-16 828
I can't do a "clear port channel" or anything like that.

Hi Friend,
I don't think you can remove this commands from configuration till the time you reuse this ports with etherchannel configuration.
The best idea will be copy the configuration from switch and paste it on a notepad and delete these lines and copy from notepad again and paste it on switch and I think this will take care of your issue.
HTH, if yes please rate the post.
Ankur

ASA5550 port channel configuration ERROR: nameif not allowed on empty etherchannel interface

Hi All,
I am having problem when configure port channel on asa5550
IOS ver asa914-k8.bin also in ver 9.02   and 8.47.
Please let me know how can I solve this problem.
UK-LON-FW(config)# int port-channel 3
UK-LON-FW(config-if)# vlan 245
                       ^
ERROR: % Invalid input detected at '^' marker.
UK-LON-FW(config-if)# nameif secure
ERROR: nameif not allowed on empty etherchannel interface.
UK-LON-FW(config-if)#
here is my interfaces configuration:
interface GigabitEthernet0/0
description fw1:G0/0 to uk-lon-gw1:e1/8 fw2:G0/0 to uk-lon-gw2:e1/9 outside zone
channel-group 1 mode on
no nameif
no security-level
no ip address
interface GigabitEthernet0/1
description fw1:G0/1 to uk-lon-gw2:e1/8 fw2:G0/1 to uk-lon-gw1:e1/9 outside zone
channel-group 1 mode on
no nameif
no security-level
no ip address
interface GigabitEthernet0/2
description fw1:G0/2 to uk-lon-sw1a:1 fw2:G0/2 to uk-lon-sw1a:2 dmz
channel-group 2 mode on
no nameif
no security-level
no ip address
interface GigabitEthernet0/3
description fw1:G0/3 to uk-lon-sw1b: fw2:G0/3 to uk-lon-sw1b:2 dmz
channel-group 2 mode on
no nameif
no security-level
no ip address
interface Management0/0
management-only
nameif management
security-level 0
ip address 10.10.51.18 255.255.254.0
interface GigabitEthernet1/0
description fw1:G1/0 to uk-lon-sw1a:3 fw2:G1/0 to uk-lon-sw1a:4 secure zone
no nameif
no security-level
no ip address
interface GigabitEthernet1/1
description fw1:G1/1 to uk-lon-sw1b:3 fw2:G1/1 to uk-lon-sw1b:4 secure zone
no nameif
no security-level
no ip address
interface GigabitEthernet1/2
description LAN Failover Interface
no nameif
no security-level
no ip address
interface GigabitEthernet1/3
description STATE Failover Interface
no nameif
no security-level
no ip address
interface Port-channel1
description outside zone
no nameif
no security-level
no ip address
interface Port-channel1.5
description outside zone Bundle FW:G0/0-G0/1 connect to GW1:e1/8-GW2:e1/8
vlan 5
nameif outside
security-level 0
ip address 216.239.105.5 255.255.255.128 standby 216.239.105.6
interface Port-channel2
description dmz Bunlde uk-lon-fw:G0/2-3 to sw1a:1-2 sw1b:1-2
no nameif
no security-level
no ip address
interface Port-channel2.105
description dmz
vlan 105
nameif dmz
security-level 50
ip address 216.239.105.193 255.255.255.192 standby 216.239.105.194
interface Port-channel3
description secure zone Bunlde uk-lon-fw:G1/0-1 to sw1a:3-3 sw1b:3-4
no nameif
security-level 100
ip address 10.254.105.1 255.255.255.0 standby 10.254.105.2
UK-LON-FW(config-if)#

Hi Marvin,
Thank you for your answer. I did everything but it did not work. Turn out it is a bug ver 8.45 will let you created the sub logical interface but actually it did not work right. Verson 9.x doesn't let you create more than 2 port channel (limitation of ASA5550 hardware).
https://tools.cisco.com/bugsearch/bug/CSCtq62715/?reffering_site=dumpcr
Also, you can see the 8.4 release notes were you can see that it is not supported:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/release/notes/asarn84.html#pgfId-522232
Interface Features
EtherChannel support (ASA 5510 and higher)
You can configure up to 48 802.3ad EtherChannels of eight active interfaces each.
Note 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.
We introduced the following commands: channel-group , lacp port-priority , interface port-channel , lacp max-bundle , port-channel min-bundle , port-channel load-balance , lacp system-priority , clear lacp counters , show lacp , show port-channel .

Catalyst 3750G and WLC 440x - Port Channel - Configuration - Best Pactice

What is the best practice to use when configuring port channel between Catalystr 3750G switch stack and WLC 4402 / 4404 Wireless Lan Controllers:
a) Negotiate to LACP
b) Negotiate to PAgP
or
c) Hard-code to Port Channel without any negotiation.
Any pointers to any useful links - much appreciated and configuration example as well.

Answer is 'C'... channel-mode on
Configuring Neighbor Devices to Support LAG
The controller's neighbor devices must also be properly configured to support LAG.
â¢Each neighbor port to which the controller is connected should be configured as follows:
interface GigabitEthernet
switchport
channel-group mode on
no shutdown
â¢The port channel on the neighbor switch should be configured as follows:
interface port-channel
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan
switchport trunk allowed vlan
switchport mode trunk
no shutdown
Here is a link that explains it. Hope this answers your question:
http://www.cisco.com/en/US/docs/wireless/controller/4.2/configuration/guide/c42mint.html#wp1116136
Here is a Best Practice doc:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080810880.shtml

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

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

SG300 Port-Channel Configuration

We have an SG300 52P and a SG300 28P that we need to LAG/Trunk together, but have had a hell of a time doing it. Both switches are updated to 1.3.0.62. The 52 port switch is configured in layer 3, the 28 port switch in layer 2. All connectivity that is directly connected to the 52 port works as intended, but no traffic on the 28 port over the port channel to VLANs outside the native VLAN are working. Strangely too, it is possible to ping the 28 port from a serial connection on the 52 port on the native vlan address, but cannot access the management interface over ethernet. The last 4 ports of each switch are part of the port channel.
Here are the two configurations:
52 Port:
vlan database
vlan 2,4,6,8,10,100
ip dhcp relay address 10.0.4.10
ip dhcp relay address 10.0.4.14
ip dhcp relay enable
ip name-server 10.0.4.10 10.0.4.14
hostname CORE-SW1
ip ssh server
ip ssh pubkey-auth
snmp-server server
snmp-server community public ro 10.0.4.5 view Default
interface vlan 1
Name ReserverdDefault
ip address 192.168.0.1 255.255.255.0
no ip address dhcp
interface vlan 2
ip address 10.0.2.1 255.255.255.0
ip dhcp relay enable
interface vlan 4
ip address 10.0.4.1 255.255.255.0
ip dhcp relay enable
interface vlan 6
ip address 10.0.6.1 255.255.255.0
ip dhcp relay enable
interface vlan 8
ip address 10.0.8.1 255.255.255.0
ip dhcp relay enable
interface vlan 10
ip address 10.0.10.1 255.255.255.0
ip dhcp relay enable
interface vlan 100
name Network
ip address 10.0.0.1 255.255.255.0
ip dhcp relay enable
interface gigabitethernet1
switchport mode access
switchport access vlan 100
interface gigabitethernet2
switchport mode access
switchport access vlan 100
(all ports between are configured like ports 1 & 2)
interface gigabitethernet49
channel-group 1 mode on
interface gigabitethernet50
channel-group 1 mode on
interface gigabitethernet51
channel-group 1 mode on
interface gigabitethernet52
channel-group 1 mode on
interface Port-channel1
description CORELINK
speed 1000
no negotiation
switchport trunk allowed vlan add 2,4,6,8,10
switchport trunk native vlan 100
ip default-gateway 10.0.0.254
28 Port:
vlan database
vlan 2,4,6,8,10,100
ip dhcp relay address 10.0.4.10
ip dhcp relay address 10.0.4.14
ip dhcp relay enable
ip name-server 10.0.4.10 10.0.4.14
hostname ACC-SW1
ip ssh server
ip ssh pubkey-auth
snmp-server server
snmp-server community public ro 10.0.4.5 view Default
interface vlan 1
Name ReserverdDefault
no ip address dhcp
interface vlan 2
ip dhcp relay enable
interface vlan 4
ip dhcp relay enable
interface vlan 6
ip dhcp relay enable
interface vlan 8
ip dhcp relay enable
interface vlan 10
ip dhcp relay enable
interface vlan 100
name Network
ip address 10.0.0.2 255.255.255.0
ip dhcp relay enable
interface gigabitethernet1
switchport mode access
switchport access vlan 100
interface gigabitethernet2
switchport mode access
switchport access vlan 100
(all ports between are configured like ports 1 & 2)
interface gigabitethernet25
channel-group 1 mode on
interface gigabitethernet26
channel-group 1 mode on
interface gigabitethernet27
channel-group 1 mode on
interface gigabitethernet28
channel-group 1 mode on
interface Port-channel1
description CORELINK
speed 1000
no negotiation
switchport trunk allowed vlan add 2,4,6,8,10
switchport trunk native vlan 100
Thank you in advance for any assistance that you can provide, I have been tearing my hair out on this
-Drew

The LAG is back up and working on native VLAN 100, but I am still not able to pass other vlan traffic from the L2 to L3 switch. The switch also took out my switchport trunk native vlan 100 configs on both switches when they were connected. After I manually put the configuration back the switches were able to communicate. Here is the current port channel and LAG configurations:
52:
interface gigabitethernet51
description "LAG 3"
channel-group 1 mode on
no macro auto smartport
interface gigabitethernet52
description "LAG 4"
channel-group 1 mode on
no macro auto smartport
interface Port-channel1
negotiation 1000f
description CORELINK
spanning-tree link-type point-to-point
switchport trunk allowed vlan add 2,4,10,14
switchport trunk native vlan 100
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
28:
interface gigabitethernet27
description "LAG 3"
channel-group 1 mode on
interface gigabitethernet28
description "LAG 4"
channel-group 1 mode on
interface Port-channel1
negotiation 1000f
description CORELINK
spanning-tree link-type point-to-point
switchport trunk allowed vlan add 2,4,10,14
switchport trunk native vlan 100
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch
When I try to ping 10.0.4.1 from the 28 port, here is the output:
Pinging 10.0.4.1 with 18 bytes of data:
PING: net-unreachable
PING: net-unreachable
PING: net-unreachable
PING: net-unreachable
----10.0.4.1 PING Statistics----
4 packets transmitted, 0 packets received, 100% packet loss
Thank you again for any assistance you can provide.
-Drew

Configuring port-channel on N7K

Hi there,
I am trying to build a port-channel from N7K-01 to N7K-02 using a breakout cables (40G interface from N7K-01 to 4x10G interfaces on N7K-02). it didn't work
is this require a special configuration??? because I have done port-channel configuration between two 40G interfaces and it works.
appreciate your valuable support if possible to share the needed configuration to accomplish this.
thanks,
regards,
Haitham.

Hi,
when I do it directly between cisco ASR9k, the 10g interfaces are up with lights but 40G side is red not up.
between cisco N7Ks, no lights from both sides. between N7Ks cable is going to patch-panel and then to other nexus.
thanks,

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

Possible to use inline mode with Port Channel

Hi,
Just wondering if anyone has used inline mode with Port Channel configuration placing WAE device between router and switch. Any tips or gotcahs to be concerned about. We currently have inline mode running at this location but site would want redudancy built in through port channel.
kind regards,
Nigel

Hi Nigel,
This is not supported :
Taken from here :
http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/waas/v531/command/reference/cmdr/glob_cfg.html#wp1532575
Best regards
Finn Poulsen

6248 connected to 3750 yet ports not configured as trunkport

I've setup a 2 5108's with 6248 Fabrics and my ethernet uplinks are going to a 3750x. I'm not proficient with all that comes with switching but I manage to get my systems up and running effectively. After installing my esxi's on the systems I noticed that all of them were getting DHCP addressed from my network yet although I enabled my uplinks and configured them as 1gb I hadn't move the patch cables to the uplink ports on the 3750 configured as Trunk ports. Now in the past this was a show stopper. Am I missing something here. And lastly, I intend to aggregate some links with Port Channeling which is easy enough on the UCS but a note states the upstream switch needs to be configured as LACP.
In short:
1.) Do i need to configure my ports on the 3750 as Trunk dot1q or has something changed and it's auto-sensing
2.) To do the Port Channel does it require Trunk or Switch and is it absolute that I configure LACP on the upstream 3750.
Thanks

I understand Trunking, a little however, when it comes to the UCS fabrics I have never been able to configure the upstream switch with anything other than Trunk Mode where I connect my ethenet uplink ports. Yet using a newer 3750x it is running without trunkports where my uplinks are connected. This is not normal. My test....I moved the patch cables to the configured Trunk Ports on the upstream 3750 and it stopped working, moved them back to the switchports and it started working. Next to this system is another with an earlier model 3750, (sorry I'm missing the specifics) and this will not work with the switctport mode, yet when plugged into the trunk ports of the upstream 3750 it works fine. As for Vlan's I have one other than Vlan 1 which is always the way I've configured these. I've configured about 15 sets of fabrics and only this one is acting this way.
As for the Port Channel configuration thanks. I'm assuming that even in trunk mode I can set LACP.

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 ?

Interface Port Channel

My port channel is not coming up can you review my port channel configuration.
SWITCH#
interface Port-channel12
switchport access vlan 513
switchport mode access
end

Hello,
how are your participating interfaces configured ? They should look like this (assuming you use interfaces FastEthernet0/1 and FastEthernet0/2 for your channel on both devices):
3550-1#
interface FastEthernet0/1
switchport access vlan 513
switchport mode access
channel-group 12 mode on
interface FastEthernet0/2
switchport access vlan 513
switchport mode access
channel-group 12 mode on
interface Port-channel12
switchport access vlan 513
switchport mode access
3550-2#
interface FastEthernet0/1
switchport access vlan 513
switchport mode access
channel-group 12 mode on
interface FastEthernet0/2
switchport access vlan 513
switchport mode access
channel-group 12 mode on
interface Port-channel12
switchport access vlan 513
switchport mode access
Do you have physical connectivity at all ?
Regards,
GP

Port Channel

Hi all,
Got a query
I have got following command configured under two interfaces connected to WLC distribution ports
gi1/2
qos vlan-based
gi1/3
qos vlan-based
I have a port-channel configured for both gi1/2 and gi1/3
Do I need to configure qos vlan-based under port-channel as well?

Typically you just need to define QoS on the physical port and not the port channel.
Thanks,
Scott
*****Help out other by using the rating system and marking answered questions as "Answered"*****

Fabric Interconnect Uplink port channeling...

Hi,
We setup port channel of two 10G uplink interfaces on each Fabric Interconnect. Everything is running as expected.
However we noticed that under 'Port-Channel # (Fabric #)' setting on LAN tap, 'Admin Speed' was set to '10Gbps'.
Should we leave this configuration as is or match to the maximum bandwidth of port Channel we set up (20Gbps)?
I only see four options on each port channel configuration, 1 Gbps, 10Gbps, 20Gbps and 40Gbps so I'm not sure if we should change this setting.
Thank you

Hello,
You do not need to change the speed ( admin ). 20 Gbps configuration is applicable for certain server models.
-------- NXOS output -----------------
FI-A(nxos)# sh run int port-channel 1
interface port-channel1
description U: Uplink
switchport mode trunk
speed 10000
FI-A(nxos)# show int port-channel 1
port-channel1 is up
Hardware: Port-Channel, address: 547f.ee67.e0fb (bia 547f.ee67.e0fb)
Description: U: Uplink
MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
full-duplex, 10 Gb/s
FI-A(nxos)# sh int bri
Port-channel VLAN Type Mode   Status Reason                    Speed Protocol
Interface
Po1          1     eth trunk up      none                       a-10G(D) lacp
There is cosmetic defect where we list the operational speed as 10 Gbps instead of 20Gbps
FI-A /eth-uplink/fabric # show port-channel detail
Port Channel:
    Port Channel Id: 1
    Name: FIA
    Admin State: Enabled
    Oper State: Up
   Speed: 10 Gbps
    Oper Speed: 10 Gbps
    State Reason:
    flow control policy: default
HTH
Padma

WAAS Port Channel Configuration

Similar Messages

Maybe you are looking for