ASR 1006 shaping\policing on port-channel interfaces

Hello
I encountered a problem - ASR 1006 ignores shaping\policing configuration on a port-channel interfaces.
If I configure:
policy-map Shaping
class class-default
shape average 100000
interface TenGigabitEthernet0/0/0
no ip address
channel-group 1 mode active
interface Port-channel1.10
encapsulation dot1Q 10
ip address 1.0.0.1 255.255.255.0
service-policy output Shaping
With such configuration shaping doesn't work. But it works on ordinary tenGigabit interfaces...
I've tried several ios xe versions.. no changes
Are there any ristrictions with shaping on Port-channel interfaces?

Hi,
Traditional QoS will not work for etherchannels. Please read to find suitable config for your case.
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_mqc/configuration/xe-3s/qos-mqc-xe-3s-book/qos-eth-int.html#GUID-6137A7B8-B2D1-4024-8AC9-E7EBEDD868C6

Similar Messages

Storm Control on Port-Channel Interfaces (6500 platform)

Hello.
I cannot find it anywhere in the documentation for the Cisco 6500 platform (IOS). The question is this: When calculating the percentage of broadcast passing through a Port-Channel interface, which total bandwidth figure is used by the switch? For example:
a. If we have a bundle of 4 Gig interfaces in a PortChannel with Storm-Control applied, the threshold will be calculated over 4Gb/s or 1Gb/s?
b. If the same PortChannel for some reason loses 2 of the uplinks in the Bundle, will the calculation be made over 4Gb/s, 2Gb/s or 1Gb/s?
Thanks!

Hi Leo,
I can't find any reference to this at the moment, but my thoughts are that it will be based on a single member port of the port-channel.
Remember that a port-channel is logically a single link and so a broadcast is only sent on one of the links of the port-channel and not all of them. The decision as to which link is used will be the same as for any other frame i.e., the broadcast address is used within the hashing calculation to choose the physical port.
If the storm-control values are determined based upon the aggregate bandwidth, and changes as links are added/removed from the agregate, then the suppression threshold values for link carrying the broadcasts is never going to be correct.
Regards

MPLS TE over Port-channel interfaces

I get the following 'warning' when configuring MPLS TE on a port-channel interface. Any comments on what the limitations to using TE on a port-channel interface are?
7606(config)#interface port-channel99
7606(config-if)#mpls traffic-eng tunnels
%Warning: MPLS TE support is limited for port-channel interfaces.
For additional information, please contact the MPLS TE product manager.

Hi,
I configured TE and FRR on Port-Channel also. Router#sho mpls traffic-eng fast-reroute database Headend frr information:
Protected tunnel In-label Out intf/label Tunnel1000 Tun hd Po1:implicit-nul Tunnel1001 Tun hd Po2:implicit-nul LSP midpoint frr information:
LSP identifier In-label Out intf/label Router#show mpls traffic-eng tunnels brief
Signalling Summary:
LSP Tunnels Process: running
Passive LSP Listener: running
RSVP Process: running
Forwarding: enabled
Periodic reoptimization: every 10 Periodic FRR Promotion: every 300 Periodic auto-bw collection: every 300 TUNNEL NAME DESTINATION CISCO ISC-P139 172.16.254.253 - CISCO ISC-P141 172.16.254.252 - CISCO ISC-P145 172.16.254.251 - CISCO ISC-P147 172.16.254.250 - CISCO ISC-B181 172.16.254.253 - CISCO ISC-B182 172.16.254.252 - CISCO ISC-P166 172.16.254.254 Po2 CISCO ISC-B187 172.16.254.252 Po1 CISCO ISC-B188 172.16.254.251 Po2 CISCO ISC-P159 172.16.254.254 Po1 CISCO ISC-B185 172.16.254.250 Po1 CISCO ISC-B186 172.16.254.253 Po2 CISCO ISC-P173 172.16.254.254 Po2 CISCO ISC-P174 172.16.254.253 Po2 CISCO ISC-B189 172.16.254.254 Po1 CISCO ISC-B190 172.16.254.250 Po2 CISCO ISC-P153 172.16.254.252 Po1 CISCO ISC-P155 172.16.254.254 Po1 CISCO ISC-B183 172.16.254.251 Po1 CISCO ISC-B184 172.16.254.254 Po2 Displayed 6 (of 6) heads, 8 (of 8) midpoints, Can you explain more detail about the limited Many thanks I saw some TE Tunnels worked with FRR, some didn't. I enclose here for reference.

FRR intf/label Status
Tu1004:implicit- ready
Tu1005:implicit- ready
FRR intf/label Status
seconds, next in 8 seconds
seconds, next in 146 seconds
seconds, next in 133 seconds
UP IF DOWN IF STATE/PROT
Po1 up/up
Po2 up/up
Po1 up/up
Po2 up/up
Po2 up/up
Po1 up/up
- up/up
Po2 up/up
Po1 up/up
- up/up
Po2 up/up
Po1 up/up
- up/up
Po1 up/up
- up/up
Po1 up/up
Po2 up/up
- up/up
Po2 up/up
- up/up
6 (of 6) tails
support for TE on Port-channel?

Policy maps on port-channel sub-interfaces

We're trying to implement an enterprise QoS policy and I'm wondering how we can apply our QoS policy maps to several different sub-interfaces on a port-channel. In our case, we have both LAN and WAN connections that connect as VLANs on a switch and terminate as sub-interfaces on a port-channel that combines two Gigabit Ethernet interfaces on our router. The LAN connection will need to have a ingress service-policy to classify traffic as it comes from a customer LAN, and the WAN connections will have to have an egress service-policy to place the traffic classes into LLQ and CBWFQ queues as it leaves the router. Could I put both the ingress and egress service-policies on the physical router interface, or should I put them on the port-channel interface? Or should I apply them to the individual sub-interfaces? For example, I could put the ingress classification service-policy on the LAN sub-interface connection.
Any thoughts or insight would be helpful. Thanks.

I can't put it as input because :
gw-a(config-subif)#service-policy input policy_upload
Traffic Shaping feature not supported in input policy.
Here's a show during a bandwidth test. You can see the offered rate is properly measured and is _way_ above the target shape rate.
gw-a#show policy-map interface Port-channel 1.2
Port-channel1.2
Service-policy output: policy_upload
    Class-map: class-default (match-any)
      624006 packets, 842239036 bytes
      5 minute offered rate 12774000 bps, drop rate 0 bps
      Match: any
      Queueing
      queue limit 64 packets
      (queue depth/total drops/no-buffer drops) 0/0/0
      (pkts output/bytes output) 0/0
      shape (average) cir 100000, bc 400, be 400
      target shape rate 100000

ASR 1001 OTV Port-Channel

I saw in the release notes that 3.10 for the ASR 1001 supports port-channel for the internal otv interface. I upgraded to that release and it lets me use a port-channel interface, but it won't let me use the serivce instance command on the L2 interface. I can add the channel-group command but not any otv commands. Has anyone seen this yet?
Thanks,
Tom

Hi tom,
Not sure if you have resolved this issue, but, I hope you are configuring the port-channel with all the service-instance configurations. If yes, and you are getting into issues, please do post the output of the issue, we can have a look at the same.

Port-Channel binding on vfc interface

Hi there,
I am currently setting up a CNA / Nexus test configuration in a Blade Server chassis.
I am using a Fujitsu CEE switch in the chassis in between CNA and Nexus.
The FJ switch is connected to the Nexus via a port-channel with 8 member ports.
And here comes my problem. I normally bind physical interfaces to my vfcs
When I now try to bind the logical port-channel interface to my vfc it says this is only possible if the channel contains not more than one member port.
If this would work all my CNA WWPNs would be mapped to a single vfc interface.
What now?
I have 18 blades each equipped with one CNA . Means on both of my Nexus fabrics I have to configure 18 vfcs and bind the 36 WWPNs manually to them.
This is really kind of annoying.
Does anybody now if this will be fixed with a future firmware release or if there is any workaround available that makes life easier?
Thanks a lot in advance!

You will need to bind the MAC address of the servers to vFC since you cannot bind the same physical interface to multiple vFCs. I am not aware of any alternate upcoming solutions for this. I have seen many many customers do this with Nexus 4000's in IBM bladecenters which houses the servers.

ASA 5585 port-channels

I want to create a port-channel with 2 10Gbs interfaces on 2 ASA 5585 firewalls, and set them up in a failover pair.
In order to do this, do I simply put two 10Gbs interfaces into a channel and then configure the IP addressing and failover address on the logical port-channel interface? (aka interface po1).
Any limitations with this?

Yes, that is exactly what you do..
Create portchannel on switch and ASA
Trunk the vlan on switch side
Create logical interfaces on ASA

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 ?

Sg300-28 port-channel options

i have an sg300-28 running the latest firmware, and would like some insight on port-channel options. below are the port configs i have for a LAG to my router. i am currently using 802.3ad with LACP. my router is a linux machine pulling duty as a basic (no dynamic routing) router, firewall and internet gateway. the bonding options on the routers side explained at
http://docs.fedoraproject.org/en-US/Fedora/16/html/System_Administrators_Guide/sec-Using_Channel_Bonding.html. the mode is 4 or 802.3ad and the xmit_hash_policy is 2 or layer2+3. i also have 2 servers setup in a similar fashion with 2 interfaces in a LAG.
when i run a bandwidth test, iperf, between the two servers, i only get 900+ mbps which indicates that the GB ports are running fine. this also indicates to me that the traffic is not being "striped" across the port-channeled interfaces, thereby giving me the aggregated bandwidth of all interfaces in the LAG. i have found no options to use the balance-xor mode to create port-channels, which as i understand it, would aggregate the total bandwidth of all interfaces in the LAG. is the sg300 capable of creating a LAG that will combine the throughput of all the members of the LAG? for example, create a 2 GB pipe when 2 interfaces are port-channeled? is the balance-xor mode what would do this (regardless of the sg300's ability to do this)
interface gigabitethernet25
description "Port Channel to Router"
channel-group 1 mode auto
lldp notifications enable
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
lldp management-address automatic
interface gigabitethernet26
description "Port Channel to Router"
channel-group 1 mode auto
lldp notifications enable
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
lldp management-address automatic
interface gigabitethernet27
description "Port Channel to Router"
channel-group 1 mode auto
lldp notifications enable
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
lldp management-address automatic
interface gigabitethernet28
description "Port Channel to Router"
channel-group 1 mode auto
lldp notifications enable
lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
lldp management-address automatic
interface Port-channel1
description "Port Channel to Router"
switchport mode general
switchport general allowed vlan add 2-3,25,37,50,52,253-255 tagged
switchport general pvid 255

Hi Brendan,
You said "i only get 900+ mbps which indicates that the GB ports are running fine. this also indicates to me that the traffic is not being "striped" across the port-channeled interfaces, thereby giving me the aggregated bandwidth of all interfaces in the LAG. i have found no options to use the balance-xor mode to create port-channels, which as i understand it, would aggregate the total bandwidth of all interfaces in the LAG."
As the Admin guide says on page 130, http://www.cisco.com/en/US/docs/switches/lan/csbms/sf30x_sg30x/administration_guide/78-19308-01.pdf
Load Balancing
Traffic forwarded to a LAG is load-balanced across the active member ports, thus achieving an effective bandwidth close to the aggregate bandwidth of all the active member ports of the LAG.
Traffic load balancing over the active member ports of a LAG is managed by a hash-based distribution function that distributes Unicast and Multicast traffic based on Layer 2 or Layer 3 packet header information.
The switch supports two modes of load balancing:
By MAC Addresses—Based on the destination and source MAC addresses of all packets.
By IP and MAC Addresses—Based on the destination and source IP addresses for IP packets, and destination and source MAC addresses for
non-IP packets.
   So, an IP host running running IPERF maybe checking unicast throughput between the two IP hosts. There will be a Source and Desination IP address in that test. The switch will direct the traffic over one of the LAG port members . It wont Round robin the unicast traffic over multiple LAG ports, if the Source and Desination IP address of the traffic is the same. .
If the PC running IPerf, had another concurrent IPerf session to another or different IP host, the hash algorithm on the switch may direct that stream , maybe, over a different physical LAG interface.
So your comment about achieving 900+mbps sounds normal   Yes LAG spreads the load, the benefit comes when lots of hosts on both sides of the switches.
You hay find with just two hosts on either side of a LAG, that the switch may run the traffic between two hosts over just one member of the LAG group.
regards Dave

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

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.

Nexus 1000v - port-channel "refresh"

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

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

6880X VSS Port-Channel

Hi
I was trying to configure two 6800x switches as a VSS pair, Ive done this on 4500x switches before and worked a treat. when setting up a L2 port-channel, for some reason it puts the ports into routed mode and does not allow me to build a L2 port-channel.
So I add the following config for the port-channel
Interface port-channel 10
Description VSL_Link
switchport
switch virtual link 2
no shut
Interface range Tengig 1/1 – 1/2
Description VSL_Link
switchport mode trunk
channel-group 10 mode on
Now as soon as I type the channel-group 10 mode on, it gives an error
"Command rejected (Port-channel10): Either port is L2 and port-channel is L3, or vice-versa"
I managed to create a L2 port-channel on a 4500x, will the 6800x only allow me to create a l3 port channel.

Hi
I tried this config on the 4500x and it worked, now I have also added the switchport mode trunk command to both the port-channel and interface and still getting the same error.
When I do sh int status, the ports are showing as routed
I cleared the config and first set both interface as trunks, then when I do the channel-group 10 mode on command, it accepts the command an automatically creates the port-channel, but the interfaces show as routed.
This is my first time using a 6880x, when i logged into it, the default hostname is set to Router. I was expecting it to be named Switch, not that the hostname affects the config but makes me wonder, is the config different for the 6880x as opposed to other L3 switches

7200/7301 MTU issue on Port-Channel

Hi guys,
I have an issue with MTU on port-channel :
When I create a port-channel interface, I can set MTU to 1530 max
When I configure an interface in this port-channel, I can set port-channel MTU to 9216 max.
But when I reload, "mtu 9216" command is rejected and port-channel MTU is set to 1500 :
mtu 9216
^
% Invalid input detected at '^' marker.
%Interface MTU set to channel-group MTU 1500.
IOS version is 12.4(25g)
Thank you so much.

Hi guys,
I have an issue with MTU on port-channel :
When I create a port-channel interface, I can set MTU to 1530 max
When I configure an interface in this port-channel, I can set port-channel MTU to 9216 max.
But when I reload, "mtu 9216" command is rejected and port-channel MTU is set to 1500 :
mtu 9216
^
% Invalid input detected at '^' marker.
%Interface MTU set to channel-group MTU 1500.
IOS version is 12.4(25g)
Thank you so much.

MDS configuration for port channel

I've tried to set up the new FC port channel upload to a pair of MDS 9124s, but as I don't know enough about the MDS side I can't get the link to come up. Are there any references available anywhere that tell you blow by blow exactly how to configure the MDS side of the port channel? Or perhaps a sample working config?
Thanks

Simon,
A few items:
1) You are on 1.4.1i Balboa code
2) FI's are in FC switch mode as MDS 9124's don't support F-port channel (NPV/NPIV)
3) It's a lot easier the first time if you have matched speed sfp+ all around. Although, with the correct configs, unmatched speeds can be made to work.
If the FIs are in switch mode and your MDS is running a minimum 3.3 here are some configs that may help:
MDS side interfaces 4/11 and 4/12 are plugged into the UCS fc ports. First setup and ensure ISLs are working properly between UCS and MDS, then configure the port-channels
interface fc4/11
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
interface fc4/12
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
The UCS GUI Equipment -> Fabric Interconnects -> FI-A -> Set FC Switching Mode. This will cause both FI's to reboot into FC switch mode. This is VERY DISRUPTIVE, both FI's will reboot.
On the UCS CLI you should see this on the UCS fc ports connected to the MDS
cae-sj-ca3-A(nxos)# show running-config interface fc 2/1-2
!Command: show running-config interface fc2/1-2
!Time: Wed Oct 20 16:49:39 2010
version 4.2(1)N1(1.4)
interface fc2/1
switchport mode E
no shutdown
interface fc2/2
switchport mode E
no shutdown
Until you have VSAN trunks enabled, make sure the ports on the UCS and MDS are in the same VSAN. VSAN 1 for example.
Once you have working ISLs, then proceed to turn them into port-channels and enable VSAN trunking. Start with the MDS
Create a channel group, it should look like this
cae-sj-9506-1# show run interface port-channel 3
!Command: show running-config interface port-channel 3
!Time: Wed Oct 20 17:06:01 2010
version 5.0(1a)
interface port-channel 3
channel mode active
switchport mode E
switchport rate-mode dedicated
switchport trunk mode auto <-- VSAN trunking
Enable VSAN trunking on the MDS ISL interfaces, it'll look like this:
cae-sj-9506-1# show run interface fc 4/11-12
!Command: show running-config interface fc4/11-12
!Time: Wed Oct 20 17:07:05 2010
version 5.0(1a)
interface fc4/11
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
interface fc4/12
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
Add the channel group information to the MDS ISL interfaces:
Enter configuration commands, one per line. End with CNTL/Z.
cae-sj-9506-1(config)# interface fc 4/11-12
cae-sj-9506-1(config-if)# channel-group 3 force
fc4/11 fc4/12 added to port-channel 3 and disabled
please do the same operation on the switch at the other end of the port-channel,
then do "no shutdown" at both ends to bring it up
cae-sj-9506-1(config-if)# show run interface fc 4/11-12
!Command: show running-config interface fc4/11-12
!Time: Wed Oct 20 17:07:39 2010
version 5.0(1a)
interface fc4/11
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
channel-group 3 force
no shutdown
interface fc4/12
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
channel-group 3 force
no shutdown
Create the SAN port channel on the UCS side
SAN -> SAN Cloud -> Fabric A -> FC Port Channels -> Create Port Channel
After you create the SAN port channel in UCS, make sure and enable it. I also bounce the MDS port channel at this point.
If all is correct, in a few agonizing minutes, the port-channel will be formed and passing data.
cae-sj-ca3-A(nxos)# show interface san-port-channel 1
san-port-channel 1 is trunking
    Hardware is Fibre Channel
    Port WWN is 24:01:00:0d:ec:d3:5d:c0
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1
    Speed is 8 Gbps
    Trunk vsans (admin allowed and active) (1,10,26,50,66,100-101,103,123,222,24
0)
    Trunk vsans (up)                       (1,10,50,100,103)
    Trunk vsans (isolated)                 (26,66,101,123,222,240)
    Trunk vsans (initializing)             ()
    5 minute input rate 2312 bits/sec, 289 bytes/sec, 2 frames/sec
    5 minute output rate 1440 bits/sec, 180 bytes/sec, 2 frames/sec
      2669 frames input, 194760 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      2677 frames output, 158316 bytes
        0 discards, 0 errors
    0 input OLS, 1 LRR, 0 NOS, 0 loop inits
Again, make sure you have the ISLs up an running first before configuring the port-channels. It makes troubleshooting much easier.
Let me know if you need any help.

ASR 1006 shaping\policing on port-channel interfaces

Similar Messages

Maybe you are looking for