Hi Andras,
Exactly the same result: sw1(config-if)#*Mar 13 12:45:50.936: %EC-5-CANNOT_BUNDLE2: Te1/16 is not compatible with Po5 and will be suspended (trunk mode of Te1/16 is dynamic, Po5 is trunk) Date: Wed, 13 Mar 2013 12:24:27 +0100 Subject: Re: [c-nsp] 4500-X VSS %EC-5-CANNOT_BUNDLE2 From: [email protected] To: [email protected] CC: [email protected]; [email protected] And if you add "switchport" and "switch virtual link 1" on the port-channel before adding Te1/16 as a member interface, like below? int po5 switchport switch virtual link 1 int te1/16 channel-group 5 mode on Best regards,Andras On Wed, Mar 13, 2013 at 4:57 AM, CiscoNSP List <[email protected]> wrote: Thanks Andras - I removed portchan5, defaulted te1/16, re-added portchan5 and then only added "channel-group 5 mode on" under te1/16, and still get the following error: *Mar 12 19:51:33.155: %EC-5-CANNOT_BUNDLE2: Te1/16 is not compatible with Po5 and will be suspended (trunk mode of Te1/16 is dynamic, Po5 is trunk) These are 2 new switches, so dont have smartnet on them (yet)....Ill get smartnet this week and open a TAC case as it does look like it is a bug. Thanks again for your help. Date: Wed, 13 Mar 2013 03:14:14 +0100 Subject: Re: [c-nsp] 4500-X VSS %EC-5-CANNOT_BUNDLE2 From: [email protected] To: [email protected] CC: [email protected]; [email protected]; [email protected] Those config lines are added because it's a VSL (Virtual Switch Link) between the two VSS boxes. When you configure VSL, all existing configurations are removed from the interface except for specific allowed commands. When you configure VSL, the system puts the interface into a restricted mode. This means that only specific configuration commands can be configured on the interface. The following VSL configuration commands are inserted automatically on all VSL member ports:switchport mode trunk switchport nonegotiate no lldp transmit no lldp receive no cdp enable service-policy output VSL-Queuing-Policy Also note the following:In VSL restricted mode, only these configuration commands are available: channel-group ... This seems to suggest that you should not try to configure switchport commands on your VSL link. Please see the Configuration Guide below for details: http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/15.1.2/XE_340/configuration/guide/vss.html If you still find that there's an error in the simple process of adding interfaces to the port-channel when it's used as a VSL, then I'd suggest to open a TAC case because it might be a new bug, given that VSS on 4500 is a pretty new feature, but it seems you just don't need to mess with switchport config on VSL ports. Best regards,Andras On Wed, Mar 13, 2013 at 12:39 AM, CiscoNSP List <[email protected]> wrote: Thanks for the reply Gert. On the 4500X, the sequence is (As you describe): Create portchan, then add portchan to physical/member Int. For VSS on the 4500X, it is: SW1(config)#int port-channel 5 SW1(config-if)#switchport SW1(config-if)#switch virtual link 1 SW1(config-if)#no shut SW1(config-if)#exit SW1(config)#int TenGigabitEthernet1/16 SW1(config-if)#switchport mode trunk SW1(config-if)#channel-group 5 mode on The 4500X then "automagically" adds the following to the physical Int (And also restricts what commands you can enter on the member Interface) switchport nonegotiate no lldp transmit no lldp receive no cdp enable service-policy output VSL-Queuing-Policy > Date: Tue, 12 Mar 2013 09:39:58 +0100 > From: [email protected] > To: [email protected] > CC: [email protected]; [email protected]; > [email protected] > Subject: Re: [c-nsp] 4500-X VSS %EC-5-CANNOT_BUNDLE2 > > Hi, > > On Tue, Mar 12, 2013 at 12:42:46PM +1100, CiscoNSP List wrote: > > Portchan conf (That fails): (Hotmail will probably screw the formatting): > > > > interface Port-channel5 > > switchport > > switchport mode trunk > > switchport nonegotiate > > switch virtual link 1 > > > > And Int conf: > > > > interface TenGigabitEthernet1/16 switchport mode trunk > > switchport nonegotiate > > no lldp transmit > > no lldp receive > > no cdp enable > > channel-group 5 mode on > > service-policy output VSL-Queuing-Policy > > Don't configure stuff on member interfaces after joining a channel. Ever. > > (IOS should just disallow this in the first place) > > > The "right" sequence of things is: > > int te1/16 > switchport > channel-group 5 mode on > no shut > > and then *everything else* is configured under "int port-channel 5", including > trunk/no trunk, vlans, service-policy, ... > > (For some stupid reasons, switchport/no switchport needs to be set on the > interface first, before joining the channel) > > gert > -- > USENET is *not* the non-clickable part of WWW! > //www.muc.de/~gert/ > Gert Doering - Munich, Germany [email protected] > fax: +49-89-35655025 [email protected] _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
