MPLS-TE over Port-channel on 7206

Hi Guys,
I need an information: on a 7206vxr (ios 15.2S) I tried to configure an mpls-te over an etherchannel link but it doesn't seems to work (the TE tunnel never go up and the "show mpls traffic-eng tunnel tunnel 0 det" show the reason as "invalid path" but I guarantee that it's absolutely valid).
I tried to search into feature navigator but I don't found any of that: It figure out as 7206 don't support it, it's right?
Thanks in advance
Giulio

Hi Giulio, can you please confirm that to me?
In the IOS feature navigator the feature "MPLS TE - Bundled interface support (EtherChannel and MLP)" seems to be available only in 7600 platform and not in 7200 series. And with 7200 series I have had some difficulty with MPLS TE in a port-channel interface.
Thankyou
Gianrico
Itesys srl

Similar Messages

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?

Pppoe over port-channels on ios xe

has the ability to do pppoe and QinQ over port-channels been added to IOS XE? as of 2.6 it was not but I cannot find any documentation on 3.1-3.3 to say that it has or hasn't
Does any one use a asr1000 as a BRAS and if so how do you handle redundancy in case of the loss of a primary interface handling your pppoe sessions?

Hi Artyom,
Try removing "ipv6 nd managed-config-flag" and see if it helps.
Regards

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 over L2 MPLS links

Hello.
I was hoping that someone could over some suggestions on best practice or recommendations for configuring port channel to bundle to layer 2 MPLS links that we have.
We have racks in two geographically separated data centres, each rack has a stack of Cisco 3850 switches, and there are two 100Mbps layer 2 connections linking these stacks together. The links are provided by our supplier and runs over their core network (I can get more info on their setup if need be).
I had initially just configured a simple port channel bundling the two ports on "Switch A", and the same on "Switch B". However I have since noticed that one of the ports was put into error disabled state, and I have my doubts that we ever had 200Mbps throughput over the portchannel.
The logs showed:
UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gix/x/x, aggressive mode failure detected
%PM-4-ERR_DISABLE: udld error detected on Gix/x/x, putting Gix/x/x in err-disable state
How I understand is that one of ports recieved an unexpected (or incorrect) BPDU packet, and shut the port down as part of spanning tree process to stop a loop forming.
For the time being I have removed the port channel config and re-opened all the ports, so I believe one of the ports is now in blocking state.
Whilst redundancy for these links is great, ideally I would like to have the links bundled so I also get the benefit of higher throughput.
Any thoughts are greatly appreciated.
Thank you

Hi,
Thank you for your reply and suggestions. I have been reading up on layer 2 protocol tunnelling and I'm not sure if this will work for us. According to these guidelines for the catalyst 3550 (http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3550/software/release/12-1_19_ea1/configuration/guide/3550scg/swtunnel.html#wp1006657) it states:
•If you enable PAgP or LACP tunneling, we recommend that you also enable UDLD on the interface for faster link-failure detection.
•Tunneling is not supported on trunk ports. If you enter the l2protocol-tunnel interface configuration command on a trunk port, the command is accepted, but Layer 2 tunneling does not take affect unless you change the port to a tunnel port or an access port.
•EtherChannel port groups are compatible with tunnel ports when the 802.1Q configuration is consistent within an EtherChannel port group.
(maybe its a different and is supported on 3850's)
Also, I cant use layer 3 over this link as I am looking to extend VLANs over the link so devices and virtual machines in each of the datacentre are in the same subnet and broadcast domain.
I will speak with the supplier to see what they are willing to do.
Thanks again.

Multiple vsan traffic over single port-channel

Hi -
Scenario - 2 interface uplink (port-channel - Po10 ) from NetApp FAS-A to N5548-A & B. Po10 is currently configured with vPC10 and vFC10 at N5k end. single vfc currently mapped with a single vsan (vfc10 with vsan 1011).
Q - Is it possible to make the Port-channel to pass multiple vsan (vsan 1011 & 1012). If yes, then how (over same vfc or by separate vfc on same port-channel)
Subhankar

This router’s capability is only limited and dependent on the services that your ISP has given or allowed for you to use. I think it really has to be a one is to one configuration, not only with this router because I haven’t noticed any router that has this feature so far. This is really another idea for Linksys can work on.

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

Right way of configuring higher MTU over a Port Channel

Hi guys,
I have a running critical Port-Channel between two locations.
Here's the config
SW1:
interface Port-channel2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
end
interface GigabitEthernet1/45
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode active
end
interface GigabitEthernet1/46
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode active
end
SW2
interface GigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode passive
end
interface GigabitEthernet1/2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode passive
end
interface Port-channel2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
end
Now I need to increase the MTU from default value to 9198. What the right way to do it and avoid any connectivity loss, PortChannel restart.
Does it matter what switch I start first?
Thanks!
L.E. both SW are WS-C4948

Hi,
Because you are using layer 2 interfaces - there is no fragmentation support at layer 2, and interfaces receiving frames which have an unsupported size will be dropped.
I think the best way for you to proceed is to lab this up; and verify what happens - it may be that you need to make changes on switches at either end of the channel within a very short time frame to prevent too large an outage.
When you are ready to maike your change - think the best way to do this is to use the interface range command, and apply the 'mtu' command to all the interfaces in this range. I don't think it matters which switch you apply this change to first, and I don't believe if you are hinting at the 802.3ad (controlled by system-priority) decision maker, that it makes any difference.
HTH
Mike

Does Solaris 10 support cisco Virtual Port Channels over IP?

Does anyone know if Solaris 10 support cisco Virtual Port Channels open IP?

Hi user11114413,
The issue you are seeing actually has little to do with VIP, and more to do with there being multiple IP addresses for us to choose from on your box. For such multi-IP boxes, you'll want to tell us the IP to use, and in your case you want to tell as a VIP. This can be done either by editing your operational configuration file, and including an <address> element within the <unicast-listener> element, or via the tangosol.coherence.localhost system property. For example:
<unicast-listener>
    <well-known-addresses>
        <socket-address id="1">
            <address>1.2.3.260</address> 
            <port>8088</port>
        </socket-address>
    </well-known-addresses>
    <address>1.2.3.260</address> 
    <port>8088</port>
</unicast-listener>or
java ... -Dtangosol.coherence.localhost=1.2.3.260If you are using the same operational configuration on all nodes in your cluster then the system property approach is likely preferable, and would only be necessary on the two machines sharing the VIP.
As for using VIP or an extended WKA list, the choice is yours, either will work. If you do go the VIP route, it would obviously be a very bad idea to simultaneously use the same VIP and port at the same time from the two machines.
thanks,
Mark
Oracle Coherence

Port-channel issue over Ciena DWDM

Hi all,
I'm currently working on an issue encountered on a DC.
We currently use 2 3750 stacks (1 in each DC), connected with a Po.
We use dark fiber between each DC, so we have a Ciena DWDM transponder on each side.
The problem is that, if we have an issue on the inter-DC fiber, the Ciena interface on the 3750 side is still up. Using LACP on the Po, the issue can be detected in about 3 X 30 sec = 90 sec.
Before the issue is detected by LACP, the impacted port-channel interface is still used by the Po, which can cause big issues.
I thought use an EEM applet in order to monitor the CDP neighbor on each interface, and exclude the interface from the Po till the CDP neighbor is down, but the CDP timers are even bigger (180 sec hold-time).
Is there any way to address this problem, other than UDLD ?
In our others DC, we have two NX7K on each side, and we are able to use LACP with fast-rate, but this is not available on 3750...
Thank you very much !

the best way to use pair of transponders on each side in protection group.

HSRP over L3 port-channel, switches do not ping each other

Hello guys,
I have a L3 port-channel between 2 gigabit ethernet interfaces (one per switch Catalyst 6509), towards two giga interfaces in another two Catalyst 6509 in the other end. The port-channel is configured as follows in one of the ends (the first pair of 6509):
interface GigabitEthernet3/37
description Conexion
no ip address
channel-group 8 mode on
interface GigabitEthernet3/38
description Conexion
no ip address
channel-group 8 mode on
For each Catalyst 6509, the port-channel 8 has a HSRP group, 254. In one of the Catalyst (Central-1) the IP assigned is 192.168.254.253/24 and in the other (Central-2), 192.168.254.254/24. Here is the conf for one Catalyst 6509 (Central-1):
interface Port-channel8
description CENTRALES
ip address 192.168.254.253 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
no ip route-cache
load-interval 30
standby delay minimum 20 reload 300
standby preempt delay minimum 120
standby 254 ip 192.168.254.254
standby 254 timers 1 3
As you can see, HSRP group 254 is defined and it is answering from L3, (from any host or switch, for the 3 IPs), but my doubt is about the HSRP behaviour between both Catalyst. They can't find which one is the master and in fact, they can't ping each other. The status of the group defined for po 8 is:
CENTRAL-1#sh standby port-channel 8
Port-channel8 - Group 254
Local state is Active, priority 100
Hellotime 1 sec, holdtime 3 sec
Next hello sent in 0.865
Virtual IP address is 192.168.254.254 configured
Active router is local
Standby router is unknown
Virtual mac address is 0000.0c07.acfe
5 state changes, last state change 2w3d
IP redundancy name is "hsrp-Po8-254" (default)
CENTRAL-2#sh standby port-channel 8
Port-channel8 - Group 254
Local state is Active, priority 110
Hellotime 1 sec, holdtime 3 sec
Next hello sent in 0.645
Virtual IP address is 192.168.254.254 configured
Active router is local
Standby router is unknown
Virtual mac address is 0000.0c07.acfe
5 state changes, last state change 6w1d
IP redundancy name is "hsrp-Po8-254" (default)
A "sh standby br" shows each switch considers itself the master and does not know the standby.
The thing is both switches have not an interface to connect L3 from network 192.168.254.0/24 directly. I mean, they only have one interface connected to the other end of the etherchannel, but not between them. Is this the reason why they can't ping each other, and consequently, they can't properly use HSRP group?
Could you tell me which could be a solution to this issue? I can't guess what can be done since the physical interfaces gi3/37 and gi3/38 exist and I think no any other interface should be configured in this network (192.168.254.0/24).
Thank you very much in advance.

Hello Jon,
Thank you very much for your answer. For the 3 possibilities, I answer you:
1) The pair are interconnected with a L2 trunk but the thing is this network, 192.168.254.0/24, is not associated to a vlan, but to a L3 etherchannel, so there is no way to associate it to a VLAN, am I right?
2) The other end of connections I think is configured at L3 too.
3) I am pending to know about the other end, but I think it is L3 too.
Anyway, although you have been very clear, try to imagine just 2 switches connected towards another 2 by one interface per each:
Central-1: gi3/37 ---> Ext1: gi1/20
Central-2: gi3/38 ---> Ext2: gi1/30
If etherchannel from Central is L3, I do not know how to include this traffic in vlan 2....
Well, I keep on thinking. Thank you very much.

How to configure a port channel with VLAN trunking (and make it work..)

We're trying to configure a port channel group with trunked ports to connect a NetApp HA pair. We want to create two data LIFs and connect them to the switch stack. We are trying to create 2 data lifs, one for cifs and one for nfs that are on different vlans.
We want the same ports to be able to allow multiple vlans to communicate. (trunked)
These data lifs should be able to fail over to different nodes in the HA pair and still be able to communicate on the network.
What this means is that we have to connect 4 ports each for each node in the NetApp HA Pair to the switches and create a port channel of some type that allows for trunked vlans. When we configure the ports, the configuration is as follows (below):
We are only able to configure an IP on one of the vlans.
When we configure an IP from another vlan for the data lif, it does not respond to a ping.
Does anyone have any idea what I'm doing wrong on the Cisco switch?
interface GigabitEthernet4/0/12
description Netapp2-e0a
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet4/0/13
description Netapp2-e0c
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet6/0/12
description Netapp2-e0b
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet6/0/13
description Netapp2-e0d
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface Port-channel20
description Netapp2-NFS
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
spanning-tree portfast
spanning-tree bpduguard enable
end

Our problem was fixed by the storage people. They changed the server end to trunk, and the encapsulation / etherchannel.
I like all the suggestions, and they probably helped out with the configuration getting this to work.
Thanks!
interface Port-channel20
description Netapp2-NFS
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
interface GigabitEthernet4/0/12
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet4/0/13
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet6/0/12
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet6/0/13
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active

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

Ironport S380 - Port Channel for P1/P2 - & - Bypass Traffic Mechanism

Dear Team,
One of my customer has purchased WSA S380.
1. He has a requirement to bundle P1/P2 Ports and create a port-channel in a switch. Is it Possible ? If No, then what can be the Solution ?
2. Also, Is it possible to detect failover, means if our WSA will go down then will it able to bypass the traffic ? If yes then please explain how can we achieve that ?
Thanks.
Milin

1. no, you can't port channel the WSA.
2. It depends on how you get the traffic to the WSA. Are you using transparent redirection (eg WCCP), then yes, when the WSA goes down, it will be detected and traffic will quit being redirected to it. If you're using explicit redirection, it won't be detected, unless you have 2 WSAs and you cluster them.
Once you get the first WSA up and running, you can request a virtual license and install a vWSA and use that for fail over...

MPLS-TE over Port-channel on 7206

Similar Messages

Maybe you are looking for