[f-nsp] ServerIron 4G Dest-NAT

[John G.]

yes, the box change to the GTC did resolve that issue.  i heard Foundry say
the same thing- the SI4G is basically the same as the GTC except it is
fixed.  however, it actually turned out that a subtle hardware difference
between the two allowed the GTC to work in this case and not the 4G.  it's
like a bad dream- i don't want to remember too many of the details.  hope
they work great for u man.

take care,
jg


On Jan 22, 2008 11:05 AM, Gerald Krause <gk at ax.tc> wrote:

> On Tuesday 22 January 2008 19:38:52 John G. wrote:
> > well, may the Force be with you Gerald.
> >
> > we ran code of theirs that came stock with the box about 7 months ago.
>  i
> > can't remember the code rev.  we experienced this same prob i described
> > running both the routing code and the non routing code.  i can't
> remember
> > if we ever tried upgrading the code on that particular box or not... it
> was
> > a crazy experience.  they would run for 2-3 days and then just puke.
> > hopefully they have fixed this issue....
>
> Ok, thank you John! I'll ask a Foundry SI I know for some details about
> such
> problems. Maybe (hopefully) he can dispel my doubts that I have now and
> confirm that strange behavior as a known but fixed bug :-/.
>
> A last question - did the change to a SI-GTC resolve your issue
> immediately?
> If so there must be much more differences between the 4G and GTC series
> than
> I thought. I assumed a 4G is only some kind of "fixed port GTC".
>
> --
> Gerald   (ax/tc)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20080123/d606e288/attachment.html>