[c-nsp] Port-channel between Cisco 4948 and ASR 9k going err-disable
Dragan Jovicic
draganj84 at gmail.com
Tue Oct 11 10:16:47 EDT 2016
Hi,
Could you try no spanning-tree etherchannel guard misconfig on 4948.
Best
On Tue, Oct 11, 2016 at 3:03 PM, David Wilkinson <
cisco-nsp at noroutetohost.net> wrote:
> It doesn't do it on any topology change, Never had the this problem
> between classic IOS devices. This has happened since we migrated some links
> over to ASRs, It is making me wonder if I have missed something in the ASR
> configuration.
> The logs on the other devices in the network doesn't show any topology
> changes until after the error disable.
>
> Happens on both 4948 - ASR links within the same second, which then
> isolates the 4948s from the rest of the network.
>
> ASR 1 ------ ASR 2
> | |
> | |
> 4948 1 ---- 4948 2
>
>
> On 11/10/2016 12:20, Mattias Gyllenvarg wrote:
>
>> Spanning tree?
>>
>>
>> tis 11 okt. 2016 kl 13:01 skrev David Wilkinson <
>> cisco-nsp at noroutetohost.net <mailto:cisco-nsp at noroutetohost.net>>:
>>
>> Hi
>>
>> We have a couple of port-channels between Cisco 4948 and Cisco ASR
>> 9006
>> devices, periodicity we are seeing these error disable with the
>> following.
>>
>> 4948 log:
>> %SPANTREE-5-ROOTCHANGE: Root Changed for vlan 1234: New Root Port is
>> Port-channel2. New Root Mac Address is xxxx.xxxx.0cc0
>> %SPANTREE-5-ROOTCHANGE: Root Changed for vlan 1234: New Root Port is
>> Port-channel2. New Root Mac Address is xxxx.xxxx.0cc0
>> %SPANTREE-5-TOPOTRAP: Topology Change Trap for vlan 1234
>> %PM-4-ERR_DISABLE: channel-misconfig (STP) error detected on Po2,
>> putting Te1/50 in err-disable state
>> %EC-5-UNBUNDLE: Interface Te1/50 left the port-channel Po2
>> %PM-4-ERR_DISABLE: channel-misconfig (STP) error detected on Po2,
>> putting Te1/52 in err-disable state
>> %EC-5-UNBUNDLE: Interface Te1/52 left the port-channel Po2
>> %PM-4-ERR_DISABLE: channel-misconfig (STP) error detected on Po2,
>> putting Po2 in err-disable state
>>
>> ASR log:
>> ifmgr[209]: %PKT_INFRA-LINK-3-UPDOWN : Interface
>> GigabitEthernet0/0/0/18, changed state to Down
>> ifmgr[209]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface
>> GigabitEthernet0/0/0/18, changed state to Down
>> ifmgr[209]: %PKT_INFRA-LINK-3-UPDOWN : Interface
>> GigabitEthernet0/0/0/19, changed state to Down
>> ifmgr[209]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface
>> GigabitEthernet0/0/0/19, changed state to Down
>> BM-DISTRIB[1155]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/18 is no
>> longer
>> Active as part of Bundle-Ether2 (Link is down)
>> BM-DISTRIB[1155]: %L2-BM-6-ACTIVE : GigabitEthernet0/0/0/19 is no
>> longer
>> Active as part of Bundle-Ether2 (Link is down)
>> ifmgr[248]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether2,
>> changed
>> state to Down
>> ifmgr[248]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface
>> Bundle-Ether2, changed state to Down
>> ifmgr[248]: %PKT_INFRA-LINK-3-UPDOWN : Interface Bundle-Ether2.1234,
>> changed state to Down
>> ifmgr[248]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface
>> Bundle-Ether2.1234, changed state to Down
>>
>> Is there anything that I maybe missing on the ASR configuration which
>> might be causing this to happen?
>>
>> ------------------------------------------------------------
>> ----------------------------------------------
>> interface GigabitEthernet0/0/0/18
>> bundle id 2 mode active
>> cdp
>> negotiation auto
>> !
>> interface GigabitEthernet0/0/0/19
>> bundle id 2 mode active
>> cdp
>> negotiation auto
>> !
>> interface Bundle-Ether2
>> mtu 9198
>> !
>> interface Bundle-Ether2.1234 l2transport
>> encapsulation dot1q 1234
>> rewrite ingress tag pop 1 symmetric
>> !
>>
>> ------------------------------------------------------------
>> ----------------------------------------------
>>
>> #show bundle bundle-ether 2
>> Tue Oct 11 10:51:59.942 UTC
>>
>> Bundle-Ether2
>> Status: Up
>> Local links <active/standby/configured>: 2 / 0 / 2
>> Local bandwidth <effective/available>: 2000000 (2000000) kbps
>> MAC address (source): 00c1.6408.f1c3
>> (Chassis pool)
>> Inter-chassis link: No
>> Minimum active links / bandwidth: 1 / 1 kbps
>> Maximum active links: 64
>> Wait while timer: 2000 ms
>> Load balancing: Default
>> LACP: Operational
>> Flap suppression timer: Off
>> Cisco extensions: Disabled
>> Non-revertive: Disabled
>> mLACP: Not configured
>> IPv4 BFD: Not configured
>>
>> Port Device State Port ID
>> B/W, kbps
>> -------------------- --------------- ----------- --------------
>> ----------
>> Gi0/0/0/18 Local Active 0x8000,
>> 0x0004 1000000
>> Link is Active
>> Gi0/0/0/19 Local Active 0x8000,
>> 0x0003 1000000
>> Link is Active
>> ------------------------------------------------------------
>> ----------------------------------------------
>>
>>
>> Bundle-Ether2.1234 is attached to a VPLS going off to other parts
>> of the
>> network.
>>
>> Cisco 4948 config:
>> !
>> interface TenGigabitEthernet1/50
>> switchport trunk allowed vlan 1234,1235, etc
>> switchport mode trunk
>> mtu 9198
>> logging event link-status
>> channel-protocol lacp
>> channel-group 2 mode active
>> !
>> interface TenGigabitEthernet1/52
>> switchport trunk allowed vlan 1234,1235, etc
>> switchport mode trunk
>> mtu 9198
>> logging event link-status
>> channel-protocol lacp
>> channel-group 2 mode active
>> !
>> interface Port-channel2
>> switchport
>> switchport trunk allowed vlan 1234,1235, etc
>> switchport mode trunk
>> mtu 9198
>> !
>>
>> ------------------------------------------------------------
>> ----------------------------------------------
>>
>> #show etherchannel 2 detail
>> Group state = L2
>> Ports: 2 Maxports = 8
>> Port-channels: 1 Max Port-channels = 1
>> Protocol: LACP
>> Minimum Links: 0
>>
>>
>> Ports in the group:
>> -------------------
>> Port: Te1/50
>> ------------
>>
>> Port state = Up Mstr Assoc In-Bndl
>> Channel group = 2 Mode = Active Gcchange = -
>> Port-channel = Po2 GC = - Pseudo
>> port-channel = Po2
>> Port index = 1 Load = 0x00 Protocol = LACP
>>
>> Flags: S - Device is sending Slow LACPDUs F - Device is sending
>> fast
>> LACPDUs.
>> A - Device is in active mode. P - Device is in
>> passive mode.
>>
>> Local information:
>> LACP port Admin Oper Port
>> Port
>> Port Flags State Priority Key Key Number
>> State
>> Te1/50 SA bndl 32768 0x2 0x2 0x33
>> 0x3D
>>
>> Partner's information:
>>
>> LACP port Admin Oper
>> Port Port
>> Port Flags Priority Dev ID Age key Key
>> Number State
>> Te1/50 SA 32768 00c1.6408.f1c4 21s 0x0 0x2 0x4
>> 0x3D
>>
>> Age of the port in the current state: 0d:15h:36m:32s
>>
>> Port: Te1/52
>> ------------
>>
>> Port state = Up Mstr Assoc In-Bndl
>> Channel group = 2 Mode = Active Gcchange = -
>> Port-channel = Po2 GC = - Pseudo
>> port-channel = Po2
>> Port index = 0 Load = 0x00 Protocol = LACP
>>
>> Flags: S - Device is sending Slow LACPDUs F - Device is sending
>> fast
>> LACPDUs.
>> A - Device is in active mode. P - Device is in
>> passive mode.
>>
>> Local information:
>> LACP port Admin Oper Port
>> Port
>> Port Flags State Priority Key Key Number
>> State
>> Te1/52 SA bndl 32768 0x2 0x2 0x35
>> 0x3D
>>
>> Partner's information:
>>
>> LACP port Admin Oper
>> Port Port
>> Port Flags Priority Dev ID Age key Key
>> Number State
>> Te1/52 SA 32768 00c1.6408.f1c4 21s 0x0 0x2 0x3
>> 0x3D
>>
>> Age of the port in the current state: 0d:15h:36m:33s
>>
>> Port-channels in the group:
>> ---------------------------
>>
>> Port-channel: Po2 (Primary Aggregator)
>>
>> ------------
>>
>> Age of the Port-channel = 154d:19h:59m:09s
>> Logical slot/port = 21/2 Number of ports = 2
>> Port state = Port-channel Ag-Inuse
>> Protocol = LACP
>> Port security = Disabled
>>
>> Ports in the Port-channel:
>>
>> Index Load Port EC state No of bits
>> ------+------+------+------------------+-----------
>> 1 00 Te1/50 Active 0
>> 0 00 Te1/52 Active 0
>>
>> Time since last port bundled: 0d:15h:36m:32s Te1/50
>> Time since last port Un-bundled: 0d:15h:39m:40s Te1/52
>> ------------------------------------------------------------
>> ----------------------------------------------
>>
>> ASR is running XR 5.3.3
>> 4948 is running IOS 15.1(2)SG7
>>
>> Any ideas on what the issue might be?
>>
>> Thanks
>>
>> David
>>
>>
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> <mailto:cisco-nsp at puck.nether.net>
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list