[f-nsp] Experiences with Brocade TAC -> ICX products

[frnkblk at iname.com]

Our VAR is just as frustrated.

Frank

-----Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Eldon Koyle
Sent: Wednesday, February 24, 2016 3:27 PM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Experiences with Brocade TAC -> ICX products

Also, if you don't feel like TAC is handling your case as quickly as
they should, you can contact your SE and/or your VAR to put some
pressure on them.

-- 
Eldon

On Wed, Feb 24, 2016 at 10:32 AM, Nick Cutting <ncutting at edgetg.co.uk> wrote:
> I found with OSPF – coming from cisco world – it has a much lower maximum
> metric value.
>
> I did however fix this issue before TAC even got back to me.
>
>
> So make sure you BW values are not too small.. like tunnel interfaces etc.
>
>
>
> From: foundry-nsp [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of
> Robert Hass
> Sent: 24 February 2016 15:45
> To: foundry-nsp at puck.nether.net
> Subject: [f-nsp] Experiences with Brocade TAC -> ICX products
>
>
>
> Hi
>
> We just deployed test network running ICX switches for connecting many
> office users. We hit some software bugs (for example with not working OSPF
> as expected). We trying passing them to Brocade TAC, but my current
> experience is that cooperation with TAC is slow like a hell.
>
>
>
> Maybe it's just my bad luck.
>
>
>
> I'm looking for people having experiences with reporting bugs to Brocade
> TAC.
>
>
>
> Are you have positive experience with Brocade TAC ? How fast they can fix
> problems ? How professional they are ?
>
>
>
> Rob
>
>
>
>
>
>
> _______________________________________________
> 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