[f-nsp] Flapping stack

i3D.net - Martijn Schmidt martijnschmidt at i3d.net
Thu Aug 13 11:45:40 EDT 2015


Hi Nick,

You could just try to de-configure the flapping port as a stack-link,
and then proceed to disable it quickly afterwards. That chunk of config
should be right at the top of your "show running-config".

Best regards,
Martijn Schmidt

On 08/13/2015 05:42 PM, Nick Cutting wrote:
> Good afternoon chaps,
>
> I have a flapping stack cable - but I can't seem to disable one of the cables - anyone knowhow to do this?
>
> Any Ideas?
>
> Boot-Monitor Image size = 370695, Version:10.1.00T7f5 (grz10100)
>   HW: Stackable ICX6610-24
>
> SAN02#sh stack stack-ports 
>     active       standby                                                       
>      +---+        +---+                                                        
>  =2/6| 1 |2/1==2/6| 2 |2/1=                                                    
>  |   +---+        +---+   |                                                    
>  |                        |                                                    
>  |------------------------|                                                   
>
> U#  Stack-port1                                  Stack-port2            
> 1   up (1/2/1-1/2/2)                             up (1/2/6-1/2/7)       
>     up ports: 1/2/1, 1/2/2, 1/2/3, 1/2/4, 1/2/5
>     up ports: 1/2/6, 1/2/7, 1/2/8, 1/2/9, 1/2/10
>
> 2   up (2/2/1-2/2/2)                             up (2/2/6-2/2/7)       
>     up ports: 2/2/1, 2/2/2, 2/2/3, 2/2/4, 2/2/5
>     up ports: 2/2/6, 2/2/7, 2/2/8, 2/2/9, 2/2/10
>
>
>
>
> Aug 13 16:30:48:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:47:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:47:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:45:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:45:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:44:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:43:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:42:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:41:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:40:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:40:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:39:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:38:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:37:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:36:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:35:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:34:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:33:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:33:I:System: Interface ethernet 2/2/6, state up
> Aug 13 16:30:32:I:System: Interface ethernet 2/2/6, state down
> Aug 13 16:30:31:I:System: Interface ethernet 2/2/6, state up
>
>
> Also why does the sh stack connection - change what is connected everytime I run it?
>
>     active       standby                                                       
>      +---+        +---+                                                        
>  =2/6| 1 |2/1==2/6| 2 |2/1=                                                    
>  |   +---+        +---+   |                                                    
>  |                        |                                                    
>  |------------------------|                                                   
>
> trunk probe results: 2 links
> Link 1: u1 -- u2, num=4
>   1: 1/2/2 (T0) <---> 2/2/7 (T1)   
>   2: 1/2/3 (T0) <---> 2/2/8 (T1)   
>   3: 1/2/4 (T0) <---> 2/2/9 (T1)   
>   4: 1/2/5 (T0) <---> 2/2/10(T1)   
> Link 2: u1 -- u2, num=5
>   1: 1/2/6 (T1) <---> 2/2/1 (T0)   
>   2: 1/2/7 (T1) <---> 2/2/2 (T0)   
>   3: 1/2/8 (T1) <---> 2/2/3 (T0)   
>   4: 1/2/9 (T1) <---> 2/2/4 (T0)   
>   5: 1/2/10(T1) <---> 2/2/5 (T0)
>
> Link 1: u1 -- u2, num=5
>   1: 1/2/1 (T0) <---> 2/2/6 (T1)   
>   2: 1/2/2 (T0) <---> 2/2/7 (T1)   
>   3: 1/2/3 (T0) <---> 2/2/8 (T1)   
>   4: 1/2/4 (T0) <---> 2/2/9 (T1)   
>   5: 1/2/5 (T0) <---> 2/2/10(T1)   
> Link 2: u1 -- u2, num=5
>   1: 1/2/6 (T1) <---> 2/2/1 (T0)   
>   2: 1/2/7 (T1) <---> 2/2/2 (T0)   
>   3: 1/2/8 (T1) <---> 2/2/3 (T0)   
>   4: 1/2/9 (T1) <---> 2/2/4 (T0)   
>   5: 1/2/10(T1) <---> 2/2/5 (T0)   
> CPU to CPU packets are fine between 2 units.
>
> I am so confused - I need to get this healthy remotely if possible.
>
> Thanks!
>
> Nick
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

-- 
Met vriendelijke groet / Kindest regards,
Martijn Schmidt


i3D.net performance hosting 	
*Martijn Schmidt | Network Engineer*
Email: martijnschmidt at i3d.net <mailto://martijnschmidt@i3d.net> | Tel:
+31 10 8900070

*i3D.net B.V. | Global Backbone AS49544*
Van Nelleweg 1, 3044 BC Rotterdam, The Netherlands
VAT: NL 8202.63.886.B01

Website
<http://www.i3d.net/?utm_source=emailsignature&utm_medium=email&utm_campaign=home>
| Case Studies
<http://www.i3d.net/partners/?utm_source=emailsignature&utm_medium=email&utm_campaign=case-studies>
| LinkedIn <https://www.linkedin.com/company/i3d-net>
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20150813/898d0d78/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: i3Dlogo-email.png
Type: image/png
Size: 1685 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20150813/898d0d78/attachment.png>


More information about the foundry-nsp mailing list