[f-nsp] Flapping stack
Mike Allen
mkallen at gmail.com
Tue Aug 18 12:56:53 EDT 2015
Actually 8.0.30b is out, and a better choice if you are looking to upgrade
to an 8.0.30 train. There were a large number of defects closed with that
release. 8.0.20d is due out very soon as well for those that want to
venture past the 8.0.10 code.
Mike
On Mon, Aug 17, 2015 at 11:17 PM, Rajesh Singh <Rajesh.Singh at admedia.ae>
wrote:
> Brocade have released ICXR08030a.bin it may resolve your issue.
>
> Rajesh Singh,
>
>
>
> ________________________________________
> From: foundry-nsp <foundry-nsp-bounces at puck.nether.net> on behalf of
> Frank Bulk <frnkblk at iname.com>
> Sent: Monday, August 17, 2015 5:46 PM
> To: 'Nick Cutting'
> Cc: foundry-nsp at puck.nether.net
> Subject: Re: [f-nsp] Flapping stack
>
> Thanks for sharing. We're running 10k.
>
> Frank
>
> -----Original Message-----
> From: Nick Cutting [mailto:ncutting at edgetg.co.uk]
> Sent: Monday, August 17, 2015 2:36 AM
> To: Frank Bulk <frnkblk at iname.com>
> Cc: foundry-nsp at puck.nether.net
> Subject: RE: Flapping stack
>
> I was running FCXR08010g.bin
> I am now running FCXR08010m.bin
>
> Has been stable since the upgrade / reload on Thursday night.
>
> Thank you
>
> Nick
> -----Original Message-----
> From: Frank Bulk [mailto:frnkblk at iname.com]
> Sent: 15 August 2015 00:15
> To: Nick Cutting
> Cc: foundry-nsp at puck.nether.net
> Subject: RE: Flapping stack
>
> What code are you running on that ICX6610?
>
> Frank
>
> -----Original Message-----
> From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf
> Of
> Nick Cutting
> Sent: Thursday, August 13, 2015 10:42 AM
> To: foundry-nsp at puck.nether.net
> Subject: [f-nsp] Flapping stack
>
> 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
>
>
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
>
> ---------------------------------------------------------------------------------------
> DISCLAIMER
> This message (including any attachments) is confidential and intended
> solely for the person or organization to whom it is addressed. It may
> contain privileged and confidential information. If you are not the
> intended recipient, you should not copy, distribute or take any action in
> reliance on it. If you have received this message in error, please notify
> us immediately by telephoning or E-mailing the sender. This footnote also
> confirms that this E-mail message has been scanned for the presence of
> computer viruses.
>
> ---------------------------------------------------------------------------------------
> Please consider the environment before printing this email
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20150818/84b31094/attachment.html>
More information about the foundry-nsp
mailing list