[c-nsp] Active Portchannel - Adding new member fails

mb at adv.gcomm.com.au mb at adv.gcomm.com.au
Thu Jul 28 18:32:42 EDT 2011


Thanks John - I resolved the problem last night during outage window.

What worked was setting eth int to default (default interface 
fastEthernet 0/x) and then re-adding the original eth port 
config...working now with both eth ints as members of portchan.

Thanks again to all who responded.


Quoting John Gill <johgill at cisco.com>:

> Sorry, I believe the mailer or my mail was delayed a bit and I didn't 
> see the previous response.
>
> This is bad behavior, your config looks good. I suspect it could be this bug:
> CSCsd11234    ports fail to bundle when nonegotiate is configured
>
> What version of software are you running?
>
> Release note mentions this (found on 4500, but applicable to desktop 
> switch code too):
> If a physical interface is configured in shutdown mode, then 
> configured with the same configuration including "switchport 
> nonegotiate," when it is later enabled by the no shutdown command, it 
> can not join the bundle and the following error message displays:
>
> %EC-5-CANNOT_BUNDLE2: Gi3/16 is not compatible with Po1and will be 
> suspended (trunk mode of Gi3/16 is dynamic, Po1 is trunk)
>
>
> The following configuration sequence will prevent interface g3/16 
> from joining the bundle:
>
> int g3/16
> shut
> switchport mode trunk
> switchport nonegotiate
> channel-group 1 mode on
>
>
> int po1
> switchport trunk enacp dot1q
> switchport mode trunk
> switchport nonegotiate
>
> int g3/16
>  no shut
>
>
> Workaround: Do NOT configure the channel-port with the same 
> configuration while all physical ports are still in shutdown mode. 
> Instead, issue the unshutdown command on the physical ports to carry 
> over the first unshutdown to the channel port. (CSCsd11234)
>
> Regards,
> John Gill
> cisco
>
>
> On 7/27/11 6:05 PM, mb at adv.gcomm.com.au wrote:
>> Quoting John Gill <johgill at cisco.com>:
>>
>>> Can you check the config on port-channel 2? perhaps there is
>>> difference between port trunk config of 0/20 and the channel trunk
>>> config.
>>>
>>
>> Thanks for the response - Already just sent that info, but here it is
>> again:
>>
>> interface Port-channel2
>> description FEC_TO_ESW02_BNE
>> switchport trunk allowed vlan
>> 1,11,12,14,30,35,68,99,100,103,104,106-108,112
>> switchport trunk allowed vlan add
>> 113,115,120-123,129,132-136,138,156,158,160
>> switchport trunk allowed vlan add
>> 206,289,311,312,340,345,377-396,398,399,402
>> switchport trunk allowed vlan add
>> 422,444,472,473,475,478-488,492,493,497,498
>> switchport trunk allowed vlan add
>> 500,546,590,591,700,801-806,808,809,811-815
>> switchport trunk allowed vlan add
>> 865,866,868,869,957,970,973,974,978,987,1829
>> switchport trunk allowed vlan add 2501,2506,2516,2518-2525
>> switchport mode trunk
>> switchport nonegotiate
>>
>> #sh interface port-channel 2 switchport Name: Po2
>> 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
>>
>>
>> And as stated, the portchan is currently up and running with FA0/21
>>
>> #sh int port-channel 2 Port-channel2 is up, line protocol is up (connected)
>> Hardware is EtherChannel, address is 0017.5af5.6695 (bia 0017.5af5.6695)
>> Description: FEC_TO_ESW02_BNE
>> MTU 1530 bytes, BW 100000 Kbit, DLY 1000 usec, reliability 255/255,
>> txload 87/255, rxload 116/255
>> Encapsulation ARPA, loopback not set
>> Full-duplex, 100Mb/s, media type is unknown media type
>> input flow-control is off, output flow-control is off
>> Members in this channel: Fa0/21 ARP type: ARPA, ARP Timeout 04:00:00
>> Last input 00:00:00, output 09:28:14, output hang never
>> Last clearing of "show interface" counters never
>> Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
>> Queueing strategy: fifo
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> This e-mail was sent via GCOMM WebMail http://www.gcomm.com.au/
>>
>>
>



-------------------------------------------------------------------------
This e-mail was sent via GCOMM WebMail http://www.gcomm.com.au/




More information about the cisco-nsp mailing list