True this is ugly bug, not a feature request.
On Tuesday 26 January 2010 14:58:22 Phou-Ngan Vannaxay wrote: > 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) As you are > currently in eval for purchasing a lot of MLX, maybe your request will > have more impact than our. > > PS : sorry, mistyped in my previous mail : Defect ID is 95587 not 95585. > > Le 26 janv. 2010 à 11:59, Ed Allen W. a écrit : > > 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. > > > > We were seriously considering purchasing a quantity of the MLX but the > > work arounds are as you said "quite ugly" and unacceptable to us. > > > > Brocade/Foundry will take the loss for this lack of attention to detail. > > > > From: Phou-Ngan Vannaxay [[email protected]] > > Sent: Tuesday, January 26, 2010 3:32 AM > > To: Ed Allen W. > > Cc: [email protected] > > Subject: Re: [f-nsp] MLX/XMR export maps broken Bug 95587 > > > > Hi Ed, > > > > 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: - it now works between 2 PE routers > > - it still does not work between 2 VRF within the same PE > > > > 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 !! I suggest everybody who would > > need this feature to stress their SE Brocade and maybe Brocade will be > > willing to deliver the fix sooner. > > > > The workaround suggested by Brocade is: > > - to use inter-VRF static routes if you don't have a lot of routes (which > > is not our case) - 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. > > > > Regards, > > > > Le 25 janv. 2010 à 22:44, Ed Allen W. a écrit : > >> 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. > >> > >> 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? > >> > >> > >> > >> 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. > >> _______________________________________________ > >> foundry-nsp mailing list > >> [email protected] > >> http://puck.nether.net/mailman/listinfo/foundry-nsp > _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
