<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Maybe I've been lucky, but I have always sailed right past T1 TAC
towards their L3 escalation, and if the case is marked as P1 you've
got good chances of engineering getting involved on short notice. <br>
<br>
It all comes down to how well you describe your problem when first
opening the case. That means including a show tech / support-save
for all of the involved devices right from the beginning, as well as
a network diagram if applicable, and a good amount of text
explaining the symptoms you are experiencing and the results you'd
expect to see so the TAC engineer can dive right in. After your case
engineer has been assigned, give them a call and walk them through
the problem to make sure there are no questions on their end.
Finally, cc'ing your Brocade SE into the case so they're aware
something's going on never hurts.<br>
<br>
I do have to say that if TAC identifies a new defect, you'll have to
hope there is a workaround to solve your problem for the time being
because it'll usually take several weeks for bugfixes to trickle
down to a new GA release.<br>
<br>
Best regards,<br>
Martijn<br>
<br>
<div class="moz-cite-prefix">On 02/24/2016 10:51 PM, Michael
Gehrmann wrote:<br>
</div>
<blockquote
cite="mid:CABFO8RRqk+MR=8S-X2=n72HyFYnu0miX9VsUSGq9B8ZrGHu53A@mail.gmail.com"
type="cite">
<div dir="ltr">Not just your bad luck. We have had VRRP, STP and
BGP issues around ICX. As an experienced engineer getting past
T1 & 2 is painful with TAC.
<div><br>
</div>
<div>Cheers</div>
<div>Mike</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 25 February 2016 at 02:45, Robert
Hass <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:robhass@gmail.com" target="_blank">robhass@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi
<div>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.</div>
<div><br>
</div>
<div>Maybe it's just my bad luck.</div>
<div><br>
</div>
<div>
<div>I'm looking for people having experiences with
reporting bugs to Brocade TAC.</div>
</div>
<div><br>
</div>
<div>Are you have positive experience with Brocade TAC ?
How fast they can fix problems ? How professional they
are ?</div>
<div><br>
</div>
<div>Rob</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a moz-do-not-send="true"
href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>
<a moz-do-not-send="true"
href="http://puck.nether.net/mailman/listinfo/foundry-nsp"
rel="noreferrer" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Michael Gehrmann
<div>Senior Network Engineer - Atlassian</div>
<div>m: +61 407 570 658</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
foundry-nsp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></pre>
</blockquote>
<br>
</body>
</html>