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.

Similar Messages

Port Channel Issue on Cisco 2960s-24ts

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

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

Port channel issue

Hello
I need help plz , i have 2X stacking Cisco core switch 3850 and access switches 2960X over the floors. I did the configuration but port channel still down , kindly check the below config:-
3850
interface Port-channel1
switchport mode trunk
inter gi1/0/1
switchport trunk allowed vlan 85,90,95
switchport mode trunk
channel-group 1 mode active
inter gi1/0/2
switchport trunk allowed vlan 85,90,95
switchport mode trunk
channel-group 1 mode active
2960
interface Port-channel1
switchport mode trunk
inter Tengi1/0/1
switchport trunk allowed vlan 85,90,95
switchport mode trunk
channel-group 1 mode active
inter Tengi2/0/1
switchport trunk allowed vlan 85,90,95
switchport mode trunk
channel-group 1 mode active
The goal that i have access switch should connect to my two core switches using two uplinks and i need to merge the uplinks speed.
Any idea

Hello
Kindly find the below
Core_switch#show etherchannel summary
Number of channel-groups in use: 6
Number of aggregators: 6
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
3 Po3(SD) LACP Gi1/0/5(I) Gi2/0/5(I)
ACCESS_Floor_3#show etherchannel summary
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
3 Po3(SD) LACP Te1/0/1(D) Te2/0/1(D)
I need to connect my stack switches which located on 1st floor to core switch using two uplinks one uplink teng1/0/1 to 1st core port 1/0/5 in stack and other uplink 2/0/1 to 2nd core on the stack port. 2/0/5.
thanks

Port-Channel Issue: SP-5-CANNOT_BUNDLE_LACP

I'm having an issue with the port-channel coming up. Right now it's "down down". I'm not really sure why. All other port-channels on the 6500's in VSS work fine. This one seems to be giving me an issue though.
-Both interfaces that are using this port-channel are "up up".
-I've done "shut's, no shut's" on all interfaces involved.
sh etherchannel summary
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
Po4(SD)         LACP      Gi1/1/4(I)     Gi2/1/4(I)
interface Port-channel4
switchport
switchport access vlan (vlan number)
switchport mode access
load-interval 30
flowcontrol receive desired
spanning-tree portfast edge
end
interface GigabitEthernet1/1/4
switchport
switchport access vlan   (vlan number)
switchport mode access
load-interval 30
flowcontrol receive desired
spanning-tree portfast edge
channel-protocol lacp
channel-group 4 mode active
end
interface GigabitEthernet2/1/4
switchport
switchport access vlan (vlan number)
switchport mode access
load-interval 30
flowcontrol receive desired
spanning-tree portfast edge
channel-protocol lacp
channel-group 4 mode active
end
sh log
149886: Jul 3 15:20:34 CDT: %EC-SW1_SP-5-CANNOT_BUNDLE_LACP: Gi2/1/4 is not compatible with aggregators in channel 4 and cannot attach to them (flow control receive of Gi2/1/4 is desired, Gi1/1/4 is on)
149887: Jul 3 15:20:35 CDT: %EC-SW2_SPSTBY-5-CANNOT_BUNDLE_LACP: Gi2/1/4 is not compatible with aggregators in channel 4 and cannot attach to them (flow control receive of Gi2/1/4 is desired, Gi1/1/4 is on)
Thank you for your help.

HI Mark,
1. Can you please check your ethernet card ...where this port channel connected..on the server.
    may be there are 2 different card.
2. from cisco websites:
Error Message
Explanation
This port has different port attributes than other ports within the port channel.
Recommended Action
Match the port attributes to that of the port channel.
Regards
Please rate if it helps.
Match the port attributes to that of the port channel.This port has different port attributes than other ports within the port channel.
EC-5-CANNOT_BUNDLE_LACP: [char] is not compatible with aggregators in
channel [dec] and cannot attach to them ([char])

Port channel issue in ASA

We have two Cisco ASA 55XX Firewalls and both are in HA (Active/Standy). Two ports from each Firewall is connecting two ports of Nexus 5K Switch and running port channel between Firewall & Nexus Switch and port-channel is UP. And Switches having back to back connection with allowed all VLAN trunk port.
FW01 ----------------- SW01 (Two ports with Port channel)
FW02 ----------------- SW02 (Two ports with Port channel)
I have VLAN 10 with IP Subnet 10.10.10.0/28
SW01 : 10.10.10.2
SW02 : 10.10.10.3
HSRP IP : 10.10.10.1
FWs : 10.10.10.4 & 10.10.10.5
Firewall Default Gateway : 10.10.10.1
Problem : I am not able Ping Firewall IPs from Nexus Switches. When I checked ARP table in Nexus Switch; I have observed that Firealls two IPs having same MAC address; when I checked that MAC address in the Firewall; that MAC address is Port channel interface MAC address.
This is issue (two IPs learing same MAC address) from ASA.
How to fix this issue ?
Thanks
Venkat

Hi,
What version of IOS are you running on the ASAs?
see table-12-3 in this link:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/interface_start.html
Also, since the 4500x are in VSS mode, you need to bundle one link from each switch and use LACP.
HTH

Port-Channel issue between UCS FI and MDS 9222i switch

Hi
I have a problem between UCS FI and MDS switch port-channel. When MDS-A is powered down the port-channel fails but UCS blade vHBA does not detect the failure of the port-chanel on UCS-FI and leaves the vHBA online. However, if there is no port-channel between FI-->MDS it works fine.
UCS version
System version: 2.0(2q)
FI - Cisco UCS 6248 Series Fabric Interconnect ("O2 32X10GE/Modular Universal Platform Supervisor")
Software
BIOS:      version 3.5.0
loader:    version N/A
kickstart: version 5.0(3)N2(2.02q)
system:    version 5.0(3)N2(2.02q)
power-seq: Module 1: version v1.0
             Module 3: version v2.0
uC:        version v1.2.0.1
SFP uC:    Module 1: v1.0.0.0
MDS 9222i
Software
BIOS:      version 1.0.19
loader:    version N/A
kickstart: version 5.0(8)
system:    version 5.0(8)
Here is the config from MDS switch
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/1      103    auto   on      trunking         swl    TF      4    10
fc1/2      103    auto   on      trunking         swl    TF      4    10
fc1/9      103    auto   on      trunking         swl    TF      4    10
fc1/10     103    auto   on      trunking         swl    TF      4    10
This is from FI.
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/29     103    NP     on      trunking         swl    TNP     4    103
fc1/30     103    NP     on      trunking         swl    TNP     4    103
fc1/31     103    NP     on      trunking         swl    TNP     4    103
fc1/32     103    NP     on      trunking         swl    TNP     4    103
Any thoughts on this?

Sultan,
This is a recently found issue and is fixed in UCSM 2.0.3a version .
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCua88227
which got duped to CSCtz21585
It happens only when following conditions are met
FI in End host mode
FC uplinks are configured for portchannel + trunking
Certain link event failures ( such abrupt power loss by upstream MDS switch )
Padma

Port-channel issue with FI-N7k using rate-mode share

Hi Dears,
I'm trying to using port-channel between Fabric Interconnect (FI) and N7K. in N7K use rate-mode share and LACP but the port-channel in N7K was suspended.
I was trying :
1. I using non dedicated port in Nexus 7010.
      - rate-mode share
      - channel-group 1 mode active
      - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
2. I using non dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode on
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
3. I using dedicated port in Nexus 7010
     - rate-mode share
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
4. I using dedicated port in Nexus 7010
     - rate-mode dedicated
     - channel group 1 mode active
     - switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up and running well.
is any other way to configure port-channel in N7K with rate-mode share and LACP ?
or it's some of limitation in port-channel when using rate-mode share at N7K ?
nb: fabric interconnect only support LACP and cannot be configurable.
regards,
Berwin H

HI Mark,
1. Can you please check your ethernet card ...where this port channel connected..on the server.
    may be there are 2 different card.
2. from cisco websites:
Error Message
Explanation
This port has different port attributes than other ports within the port channel.
Recommended Action
Match the port attributes to that of the port channel.
Regards
Please rate if it helps.
Match the port attributes to that of the port channel.This port has different port attributes than other ports within the port channel.
EC-5-CANNOT_BUNDLE_LACP: [char] is not compatible with aggregators in
channel [dec] and cannot attach to them ([char])

Port-channel issues

We installed a CISCO 6509e with 2 Sup 720 blades in one building that is about 600m from our corporate HQs. We have a CISC 4507 with 2 Sup 6-E with 10G. We have them connected with fiber using 10g gbic LMR optics in the 10g ports of the sup blades. The link comes up. We moved it to a trunk and set up port channeling. The link will come up as a trunk but the port channel is not coming up. We are at a bit of a loss, we have several closets through the 2 buildings and we utilize port channeling on all of our switches. Below are the interfaces for the 2 interfaces and port channels, we had hoped to add more interfaces to this port channel but we are on hold until we can determine the reason for the port channel not coming up.
6509E
interface Port-channel4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet5/4
description B2B 10G
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 4 mode auto
GigabitEthernet5/3 unassigned YES manual down down
TenGigabitEthernet5/4 unassigned YES unset up up
Port-channel4 unassigned YES unset down down
4507
interface Port-channel8
switchport
switchport mode trunk
interface TenGigabitEthernet1/1
description CORE-TO-CORE
switchport mode trunk
channel-group 8 mode desirable
TenGigabitEthernet1/1 unassigned YES unset up up
Port-channel8 unassigned YES unset down down

The physical port-channel configuration don't match. 4500 is "desirable" while the 6500 is "auto".

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

Port channel failure / lacp_switch_get_new_agg_id: secondary l3 agg are not supported

hi,
hope that someone can help.
I ran into port channel issue when trying to add 4 port Quantum Dxi server into a port channel in 3750 stack.
Configs looks ok:
interface Port-channel6
description qdx-server
switchport access vlan 3
switchport mode access
spanning-tree portfast
spanning-tree bpduguard enable
end
all four ports configured as follows
interface GigabitEthernet1/0/7 , 1/0/5 , 2/0/7 and 2/0/8
description qdx-server-ethx
switchport access vlan 3
switchport mode access
spanning-tree portfast
spanning-tree bpduguard enable
channel-protocol lacp
channel-group 6 mode active
end
all ports joined the channel except Gi 1/0/5 - it got suspended once joined the port channel
From the debug I got the following:
Dec 16 13:36:43.082 GMT: FEC: lacp_switch_get_new_agg_id: secondary l3 agg are not supported Po6
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_restart_if_needed(1): Gi1/0/5 in list
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_invoke_port_down: Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_invoke_port_up: Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:46.823 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:46.823 GMT: FEC: lacp_switch_calculate_oper_key: oper_key for port Gi1/0/5 is 0x6
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_first_agg_id_from_admin_oper_keys: found aggregator Po6 for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_first_associated_port_from_agg_id: found port Gi2/0/8 associated to Po6
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_next_agg_id_from_admin_oper_keys: aggregator next to Po6 not found for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:46.982 GMT: FEC: lacp_switch_get_new_agg_id: secondary l3 agg are not supported Po6
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_restart_if_needed(1): Gi1/0/5 in list
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_invoke_port_down: Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_invoke_port_up: Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:36:56.830 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:36:56.838 GMT: FEC: lacp_switch_calculate_oper_key: oper_key for port Gi1/0/5 is 0x6
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_first_agg_id_from_admin_oper_keys: found aggregator Po6 for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_first_associated_port_from_agg_id: found port Gi2/0/8 associated to Po6
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_next_agg_id_from_admin_oper_keys: aggregator next to Po6 not found for admin_key [0x6] and oper_key [0x6]
Dec 16 13:36:56.880 GMT: FEC: lacp_switch_get_new_agg_id: secondary l3 agg are not supported Po6
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_restart_if_needed(1): Gi1/0/5 in list
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_invoke_port_down: Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_invoke_port_up: Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: comparing GC values of Gi1/0/5 Gi1/0/7 flag = 1 1
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: compare LACP modes for Gi1/0/5
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_port_attrib_diff: Gi1/0/5 Gi1/0/7 same
Dec 16 13:37:06.837 GMT: FEC: pagp_switch_agc_compatable: GC values are compatable
Dec 16 13:37:06.837 GMT: FEC: lacp_switch_calculate_oper_key: oper_key for port Gi1/0/5 is 0x6
Dec 16 13:37:07.080 GMT: FEC: lacp_switch_get_first_agg_id_from_admin_oper_keys: found aggregator Po6 for admin_key [0x6] and oper_key [0x6]
Dec 16 13:37:07.080 GMT: FEC: lacp_switch_is_aggregator_valid: aggregator Po6 is still valid
Checked and compared the config from another server, all looks OK.. I tried to search the error message in bold, but can't find any.
Can anyone shed a light?
Many thanks.

we have the same issue with asa5525 and 3750E etherchannel.
The same error
lacp_switch_get_new_agg_id: secondary l3 agg are not supported on the SWITCH side
we are using LACP active from noth sides

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.

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

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.

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.

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

Port-channel issue over Ciena DWDM

Similar Messages

Maybe you are looking for