Port channels across slots on a 6500

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

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

Similar Messages

Config port channel across different type of media

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

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

UCS - san-port-channel over vpc

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

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

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.

Xconnect 20Gb Port-channel over MPLS Possible?

Can anybody confirm if you can establish an Xconnect between two 20Gb port-channels (2x 10Gig bundle). The core is 40Gig and running MPLS. We have many gigabit pseudowires running over it already.
Our intention is to terminate 10Gig server traffic on 4900M's and then have a 20Gb Port channel trunk link into a 6500 (which is part of the MPLS cloud). We would then issue the xconnect directly on the 20Gig port channel in order to traverse the MPLS Core.
Has anyone configured this before? Are there any caveats to watch out for? What sort of performance hit (if any does) xconnect functionality have on 10Gig Traffic.

Hi,
Yes it's supported but test it first (as always ;-) )
HTH
Laurent.

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

ACE port-channel number in 6500 chassis

Hello
Does anybody know how 6500 assigns the port-channel number for ACE ?
Thanks in advance
Regards
Lukas

There is no portchannel for the ace module.
This is a tengig interface.
For example, with an ACE in slot 2.
gdufour-cat6k-2#show mod 2
Mod Ports Card Type                              Model              Serial No.
2    1 Application Control Engine Module      ACE10-6500-K9      SAD1020084Z
Mod MAC addresses                       Hw    Fw           Sw           Status
2 0030.f275.b4ec to 0030.f275.b4f3   1.1   8.7(0.22)ACE A2(1.6a)     Ok
Mod Online Diag Status
2 Pass
gdufour-cat6k-2#show int tenGigabitEthernet 2/1 switchport
Name: Te2/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: 7,10,20,30,31,40,60,70,77,100,200,203,330,1100
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled

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

Configuring 9222i for Port-Channels to 6500

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

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

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

FWSM Default port channel?

I'm doing some L2 cleanups across mutliple 6509E environments and I've found something consistent that I can't find in documentation.
On all my pairs of 6509s where I have FWSMs bundled (6509-A has FWSM-1 is Slot 1 and 6509-B has FWSM-2 in Slot 1) I also have a port channel 305. Obviously when I do a "show run" or "show int desc" I don't see anything in slot one. It's a service module. But the port channel is referencing ports 1/1-6. And it's all in service/up. I was about to delete this as I thought it was some leftover config (TEST 6509s) until I went and saw the same things on our PROD 6509s. Can anyone explain this or provide some documentation on it? Is it cosmetic? Necessary? Can I delete it as part of my audit cleanup? Don't want to mess with it even in TEST without some information. Nothing on google that's clear and I can't find anything on CCO.
6509-1#sho etherch 305 summ
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator
        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port
        w - waiting to be aggregated
Number of channel-groups in use: 11
Number of aggregators:           11
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
305    Po305(SU)        -        Gi1/1(P)       Gi1/2(P)       Gi1/3(P)
                                 Gi1/4(P)       Gi1/5(P)       Gi1/6(P)
Last applied Hash Distribution Algorithm:   -
6509-1#sho etherch 305 det
Group state = L2
Ports: 6   Maxports = 8
Port-channels: 1 Max Port-channels = 1
Protocol:    -
Minimum Links: 0
                Ports in the group:
Port: Gi1/1
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 0           Load = 0x41        Protocol =    -
Age of the port in the current state: 46d:06h:53m:39s
Port: Gi1/2
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 1           Load = 0x02        Protocol =    -
Age of the port in the current state: 46d:06h:53m:39s
Port: Gi1/3
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 2           Load = 0x04        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
Port: Gi1/4
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 3           Load = 0x88        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
Port: Gi1/5
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 4           Load = 0x10        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
Port: Gi1/6
Port state    = Up Mstr In-Bndl
Channel group = 305         Mode = On      Gcchange = -
Port-channel = Po305       GC   =   -         Pseudo port-channel = Po305
Port index    = 5           Load = 0x20        Protocol =    -
Age of the port in the current state: 46d:06h:53m:41s
                Port-channels in the group:
Port-channel: Po305
Age of the Port-channel   = 46d:06h:55m:56s
Logical slot/port   = 14/11          Number of ports = 6
GC                  = 0x00000000      HotStandBy port = null
Port state          = Port-channel Ag-Inuse
Protocol            =    -
Fast-switchover     = disabled
Load share deferral = disabled
Ports in the Port-channel:
Index   Load   Port     EC state        No of bits
------+------+------+------------------+-----------
0     41     Gi1/1    On    2
1     02     Gi1/2    On    1
2     04     Gi1/3    On    1
3     88     Gi1/4    On    2
4     10     Gi1/5    On    1
5     20     Gi1/6    On    1
Time since last port bundled:    46d:06h:53m:41s    Gi1/6
Last applied Hash Distribution Algorithm:   -
NOC-SW-ITEST-AGG1#

The connection between the FWSM and the switch is a 6-GB 802.1Q trunking EtherChannel. This EtherChannel is automatically created when you install the FWSM.
http://cisconetwork.org.ua/1587051893/ch04lev1sec1.html
http://www.cisco.com/en/US/docs/security/fwsm/fwsm23/configuration/guide/switch.pdf
Thanks
Ajay

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.

WISM2 no Port-Channel on 6504-E

Hi there,
I have just been setting up a WISM2 in a test lab and for some reason the Supervisor is not creating a port channel on my 6500 as suggested in the WISM2 Deployment Guide. WISM2 is installed in an appropriate slot (according to same doco) and have attempted reset to factory defaults, removing and power cycling several times. Seems very odd.
Any suggestions?

ok.. so i figured out what was wrong. I had forgotten to trunk the supervisor vlan and set the native on the controller...
wism module 3 controller 1 native-vlan x
wism module 3 controller 1 allowed-vlan x-y

Port channeling a node between two 2248's

I have one Nexus 7009 with a pair of 2248's attached via port channels. I have several devices, a Cisco wireless lan controller, ESX servers, etc which I have multihomed to my current 6500's. I want to create port channels for these devices across the pair of 2248's. Currently have been working with the config for the WLC. I can create the port channel on the N7k with no problem as a trunk, and I am able to configure the first port to use the port channel, but when I add the second port I receive the following message:
command failed: port not compatible [Members in multiple FEX]
Thus I am unable to add the second interface. I assume I will run into the same problem with the ESX's as they have six 1 Gb interfaces in a port channel. I am new to the Nexus world and this is my first Nexus switch being moved into production. I have seen several post that are similiar but not really an answer. Does anybody have any idea as to what I am doing wrong. Thanks in advance.

Hi,
If I understand what you're trying to do correctly, then you're not doing anything wrong, but the topology you're trying to use is unsupported.
If you refer to the diagrams shown in Nexus 7000 Fex Supported/Not Supported Topologies then I believe you're trying to configure the topology shown on the last of the three pictures, labeled number 11. I don't know the exact details as to why this isn't a supported topology, but sadly it isn't.
As you only have a single Nexus 7000, the only option you would seem to have at this stage is to use an active/standby topology as shown in the first and second picture on the diagram labeled number five.
Regards

Disappointed: ASA 8.4 Redundant using Port-channels

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

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

Port channels across slots on a 6500

Similar Messages

Maybe you are looking for