<div dir="ltr"><div><div>Hello,<br><br></div>On my side, I used to see BFD flapps when changing ISIS metrics on B2B core interface.<br><br><br></div><div>Thank you for the feedback.<br><br>Best regards.<br><br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-03-06 9:14 GMT+01:00 Darren O'Connor <span dir="ltr"><<a href="mailto:darrenoc@outlook.com" target="_blank">darrenoc@outlook.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">So far so good on the CER.<br><br><a href="http://SSH@core00.cll.uk#sh" target="_blank">SSH@core00.cll.uk#sh</a> bfd neighbors details<br>Total Entries:1 R:RXRemote(Y:Yes/N:No)H:Hop(S:Single/M:Multi)<br>
NeighborAddress State Interface Holddown Interval R/H<br>x.x.x.x UP eth 1/24 900000 300000 Y/S<br> Registered Protocols(Protocol/VRFID): ospf/0<br> Local: Disc: 1, Diag: 0, Demand: 0 Poll: 0<br>
MinTxInterval: 300000, MinRxInterval: 300000, Multiplier: 3<br> Remote: Disc: 24, Diag: 0, Demand: 0 Poll: 0<br> MinTxInterval: 300000, MinRxInterval: 300000, Multiplier: 3<br> Stats: RX: 769964 TX: 912706 SessionUpCount: 1 at <b>SysUpTime: 2:14:7:51.198</b><br>
<b> Session Uptime: 2:14:5:36.63</b>, LastSessionDownTimestamp: 0:0:0:0.0<br> Physical Port:TX: eth 1/24,RX: eth 1/24,Vlan Id: 4001<br><b> Using PBIF Assist: Y</b><br><br><br><br><a href="http://SSH@core00.cll.uk#sh" target="_blank">SSH@core00.cll.uk#sh</a> ver<br>
System: NetIron CER (Serial #: xxxxxxx, Part #: 40-1000617-02)<br>xxxxxxxx<br><b>IronWare : Version 5.6.0bT183</b> Copyright (c) 1996-2013 Brocade Communications Systems, Inc.<br>Compiled on Jan 19 2014 at 11:47:42 labeled as ce05600b<br>
<br><br>Previously BFD flapped whenever rancid did a config copy. Since the upgrade a couple of days ago there has not been a single flap.<br><br><br><br><br>Thanks<br>Darren<br><a href="http://www.mellowd.co.uk/ccie" target="_blank">http://www.mellowd.co.uk/ccie</a><br>
<br><br><br><div><hr><div class="">Subject: Re: [f-nsp] IronWare version on XMR-4000<br></div>From: <a href="mailto:youssef@720.fr" target="_blank">youssef@720.fr</a><br>Date: Wed, 5 Mar 2014 22:39:24 +0100<br>CC: <a href="mailto:clement@cavadore.net" target="_blank">clement@cavadore.net</a>; <a href="mailto:stefan.larsson@king.com" target="_blank">stefan.larsson@king.com</a>; <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
To: <a href="mailto:darrenoc@outlook.com" target="_blank">darrenoc@outlook.com</a><div><div class="h5"><br><br><div>Hello Darren,</div><div><br></div><div>Looking at 5.6 mainly for the exact same reason : BFD assisted hardware for CER.</div>
<div><br></div><div>Is it a game changer ? Did you notice improvements ?</div><div><br></div><div>Thanks.</div><div><br></div><div>BR.<br><br><br></div><div><br>Le 5 mars 2014 à 18:40, "Darren O'Connor" <<a href="mailto:darrenoc@outlook.com" target="_blank">darrenoc@outlook.com</a>> a écrit :<br>
<br></div><blockquote><div>
<div dir="ltr">You don't need to be on the latest two versions. They are still releasing updated versions of 5.2 and so on.<br><br>We are running 5.4E on our XMRs and 5.6B on the couple of CERs we have simply because of BFD hardware for CER in that code version<br>
<br>Thanks<br>Darren<br><a href="http://www.mellowd.co.uk/ccie" target="_blank">http://www.mellowd.co.uk/ccie</a><br><br><br><br><div>> From: <a href="mailto:clement@cavadore.net" target="_blank">clement@cavadore.net</a><br>
> To: <a href="mailto:Stefan.Larsson@king.com" target="_blank">Stefan.Larsson@king.com</a><br>> Date: Tue, 4 Mar 2014 15:22:55 +0100<br>> CC: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
> Subject: Re: [f-nsp] IronWare version on XMR-4000<br>> <br>> Hello Stefan,<br>> <br>> Maybe you should explain which reasons makes you think you need to<br>> upgrade ? If you have any specifics reasons, it may help to choose any<br>
> version.<br>> <br>> AFAIK, if you have support, you may need to be on the two last versions<br>> (ie: 5.5 or 5.6), whith the highest level of patchs. Otherwises, in case<br>> you'd neet to open a ticket, you'd only get "upgrade first, then we'll<br>
> have a look" from the TAC.<br>> <br>> I had no real issues on 5.5 versions. On 5.6, a few, but not anything<br>> really disturbing (see my last post regarding 5.6 on that list).<br>> <br>> Regards,<br>
> <br>> -- <br>> Clément Cavadore<br>> <br>> On Tue, 2014-03-04 at 12:58 +0000, Stefan Larsson wrote:<br>> > Hi networkers,<br>> > <br>> > I was merely wondering if anyone on the list could advice me as to what IronWare version one is recommended to run these days for production XMR-4000 routers running BGP?<br>
> > <br>> > We are currently on 5.3.0T165 but looking to upgrade for several reasons.<br>> > <br>> > Thanks in advance for any and all pointers.<br>> > <br>> > - s<br>> > _______________________________________________<br>
> > foundry-nsp mailing list<br>> > <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>> > <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
> <br>> <br>> _______________________________________________<br>> foundry-nsp mailing list<br>> <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>> <a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</div> </div>
</div></blockquote><blockquote><div><span>_______________________________________________</span><br><span>foundry-nsp mailing list</span><br><span><a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a></span><br>
<span><a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></span></div></blockquote></div></div></div> </div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Youssef BENGELLOUN-ZAHR<br>
</div></div>