<html><head><base href="x-msg://101/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Agreed, this should be a treated as a bug, not a feature request... But, Brocade is considering the "feature" is already available using inter-VRF static routes... (but for us, it's not quite the same) <div>As you are currently in eval for purchasing a lot of MLX, maybe your request will have more impact than our.</div><div><br></div><div>PS : sorry, mistyped in my previous mail : Defect ID is 95587 not 95585.<br><div><br><div><br></div><div><br><div><div>Le 26 janv. 2010 à 11:59, Ed Allen W. a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div ocsi="x"><div dir="ltr"><font face="Tahoma" color="#000000" size="2">Thank you for your speedy reply. 2011 is outrageous! This is not a feature request. The command set supports the configuration but it simply doesn't work. That is a bug not a feature.</font></div><div dir="ltr"><font face="tahoma" size="2"></font> </div><div dir="ltr"><font face="tahoma" size="2">We were seriously considering purchasing a quantity of the MLX but the work arounds are as you said "quite ugly" and unacceptable to us.</font></div><div dir="ltr"><font face="tahoma" size="2"></font> </div><div dir="ltr"><font face="tahoma" size="2">Brocade/Foundry will take the loss for this lack of attention to detail.</font></div><div dir="ltr"> </div><div id="divRpF487513" style="direction: ltr; "><hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b><span class="Apple-converted-space"> </span>Phou-Ngan Vannaxay [phou-ngan.vannaxay@aptiwan.com]<br><b>Sent:</b><span class="Apple-converted-space"> </span>Tuesday, January 26, 2010 3:32 AM<br><b>To:</b><span class="Apple-converted-space"> </span>Ed Allen W.<br><b>Cc:</b><span class="Apple-converted-space"> </span><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [f-nsp] MLX/XMR export maps broken Bug 95587<br></font><br></div><div></div><div>Hi Ed,<div><br></div><div>The bug as described in Defect ID 95585 was (partially) fixed in release 4.0g. However, it does not fully fix the whole problem with export map RT rewrite in VRF:</div><div>- it now works between 2 PE routers</div><div>- it still does not work between 2 VRF within the same PE</div><div><br></div><div>Brocade has acknowledged there is a problem but is treating this as a new feature request... And so far, the target date for the feature ("fix", I should say) in the road map is... 2011 !!</div><div>I suggest everybody who would need this feature to stress their SE Brocade and maybe Brocade will be willing to deliver the fix sooner.</div><div><br></div><div>The workaround suggested by Brocade is:</div><div>- to use inter-VRF static routes if you don't have a lot of routes (which is not our case)</div><div>- else, to use an external loop connected between the 2 VRF and run an OSPF process with filtered advertises using route-maps which is quite ugly.</div><div><br></div><div>Regards,</div><div><br></div><div><br><div><div>Le 25 janv. 2010 à 22:44, Ed Allen W. a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span"><div><div dir="ltr"><font face="Tahoma" color="#000000" size="2">We have a pair of MLXs running Version 4.0.1b on Eval. We have tried everything we can think of to get this thing to change/add RTs on export with no success. We did find an earlier thread with the above bug ID but nothing else. We have had no word back from our Rep.</font></div><div dir="ltr"><font face="tahoma" size="2"></font> </div><div dir="ltr"><font face="Tahoma" size="2">Has Foundry/Brocade given any workaround or timeframe if/when this will be fixed? Does anyone else have a potential work around to this problem?</font></div><div dir="ltr"><font face="tahoma" size="2"></font> </div><div dir="ltr"><font face="tahoma" size="2"></font> </div><br><hr><font face="Arial" color="black" size="2">Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing.<br></font>_______________________________________________<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" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></div></span></blockquote></div><br></div></div></div></span><br class="Apple-interchange-newline"></blockquote></div><br></div></div></div></body></html>