<div dir="ltr">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.<div><br></div><div>Mike</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 17, 2015 at 11:17 PM, Rajesh Singh <span dir="ltr"><<a href="mailto:Rajesh.Singh@admedia.ae" target="_blank">Rajesh.Singh@admedia.ae</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Brocade have released ICXR08030a.bin it may resolve your issue.<br>
<br>
Rajesh Singh,<br>
<br>
<br>
<br>
________________________________________<br>
From: foundry-nsp <<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>> on behalf of Frank Bulk <<a href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>><br>
Sent: Monday, August 17, 2015 5:46 PM<br>
<span class="">To: 'Nick Cutting'<br>
Cc: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
</span>Subject: Re: [f-nsp] Flapping stack<br>
<div><div class="h5"><br>
Thanks for sharing. We're running 10k.<br>
<br>
Frank<br>
<br>
-----Original Message-----<br>
From: Nick Cutting [mailto:<a href="mailto:ncutting@edgetg.co.uk">ncutting@edgetg.co.uk</a>]<br>
Sent: Monday, August 17, 2015 2:36 AM<br>
To: Frank Bulk <<a href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>><br>
Cc: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
Subject: RE: Flapping stack<br>
<br>
I was running FCXR08010g.bin<br>
I am now running FCXR08010m.bin<br>
<br>
Has been stable since the upgrade / reload on Thursday night.<br>
<br>
Thank you<br>
<br>
Nick<br>
-----Original Message-----<br>
From: Frank Bulk [mailto:<a href="mailto:frnkblk@iname.com">frnkblk@iname.com</a>]<br>
Sent: 15 August 2015 00:15<br>
To: Nick Cutting<br>
Cc: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
Subject: RE: Flapping stack<br>
<br>
What code are you running on that ICX6610?<br>
<br>
Frank<br>
<br>
-----Original Message-----<br>
From: foundry-nsp [mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net">foundry-nsp-bounces@puck.nether.net</a>] On Behalf Of<br>
Nick Cutting<br>
Sent: Thursday, August 13, 2015 10:42 AM<br>
To: <a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
Subject: [f-nsp] Flapping stack<br>
<br>
Good afternoon chaps,<br>
<br>
I have a flapping stack cable - but I can't seem to disable one of the<br>
cables - anyone knowhow to do this?<br>
<br>
Any Ideas?<br>
<br>
Boot-Monitor Image size = 370695, Version:10.1.00T7f5 (grz10100)<br>
HW: Stackable ICX6610-24<br>
<br>
SAN02#sh stack stack-ports<br>
active standby<br>
<br>
+---+ +---+<br>
<br>
=2/6| 1 |2/1==2/6| 2 |2/1=<br>
<br>
| +---+ +---+ |<br>
<br>
| |<br>
<br>
|------------------------|<br>
<br>
<br>
U# Stack-port1 Stack-port2<br>
1 up (1/2/1-1/2/2) up (1/2/6-1/2/7)<br>
up ports: 1/2/1, 1/2/2, 1/2/3, 1/2/4, 1/2/5<br>
up ports: 1/2/6, 1/2/7, 1/2/8, 1/2/9, 1/2/10<br>
<br>
2 up (2/2/1-2/2/2) up (2/2/6-2/2/7)<br>
up ports: 2/2/1, 2/2/2, 2/2/3, 2/2/4, 2/2/5<br>
up ports: 2/2/6, 2/2/7, 2/2/8, 2/2/9, 2/2/10<br>
<br>
<br>
<br>
<br>
Aug 13 16:30:48:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:47:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:47:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:45:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:45:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:44:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:43:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:42:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:41:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:40:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:40:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:39:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:38:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:37:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:36:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:35:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:34:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:33:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:33:I:System: Interface ethernet 2/2/6, state up Aug 13<br>
16:30:32:I:System: Interface ethernet 2/2/6, state down Aug 13<br>
16:30:31:I:System: Interface ethernet 2/2/6, state up<br>
<br>
<br>
Also why does the sh stack connection - change what is connected everytime I<br>
run it?<br>
<br>
active standby<br>
<br>
+---+ +---+<br>
<br>
=2/6| 1 |2/1==2/6| 2 |2/1=<br>
<br>
| +---+ +---+ |<br>
<br>
| |<br>
<br>
|------------------------|<br>
<br>
<br>
trunk probe results: 2 links<br>
Link 1: u1 -- u2, num=4<br>
1: 1/2/2 (T0) <---> 2/2/7 (T1)<br>
2: 1/2/3 (T0) <---> 2/2/8 (T1)<br>
3: 1/2/4 (T0) <---> 2/2/9 (T1)<br>
4: 1/2/5 (T0) <---> 2/2/10(T1)<br>
Link 2: u1 -- u2, num=5<br>
1: 1/2/6 (T1) <---> 2/2/1 (T0)<br>
2: 1/2/7 (T1) <---> 2/2/2 (T0)<br>
3: 1/2/8 (T1) <---> 2/2/3 (T0)<br>
4: 1/2/9 (T1) <---> 2/2/4 (T0)<br>
5: 1/2/10(T1) <---> 2/2/5 (T0)<br>
<br>
Link 1: u1 -- u2, num=5<br>
1: 1/2/1 (T0) <---> 2/2/6 (T1)<br>
2: 1/2/2 (T0) <---> 2/2/7 (T1)<br>
3: 1/2/3 (T0) <---> 2/2/8 (T1)<br>
4: 1/2/4 (T0) <---> 2/2/9 (T1)<br>
5: 1/2/5 (T0) <---> 2/2/10(T1)<br>
Link 2: u1 -- u2, num=5<br>
1: 1/2/6 (T1) <---> 2/2/1 (T0)<br>
2: 1/2/7 (T1) <---> 2/2/2 (T0)<br>
3: 1/2/8 (T1) <---> 2/2/3 (T0)<br>
4: 1/2/9 (T1) <---> 2/2/4 (T0)<br>
5: 1/2/10(T1) <---> 2/2/5 (T0)<br>
CPU to CPU packets are fine between 2 units.<br>
<br>
I am so confused - I need to get this healthy remotely if possible.<br>
<br>
Thanks!<br>
<br>
Nick<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<br>
</div></div>---------------------------------------------------------------------------------------<br>
DISCLAIMER<br>
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.<br>
---------------------------------------------------------------------------------------<br>
Please consider the environment before printing this email<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</div></div></blockquote></div><br></div>