>The message from the Livingston rep goes like this:
>"Okay, I think I have the solution to your problem. What you need to do is
type 'set console' >and hit return. Type 'set debug 0x0' and hit return.
Type 'reset console' and hit return. >That should take care of your problem..."
In the interest of fairness and to thank those involved, I wanted to
document the "Excellent Support Story" that followed my post here yesterday
afternoon about the odd phone message left on our voice mail by an
(apparently new) support person.
Within 30 minutes of posting, Gryphon (Ben Hutchins) called to address the
situation, apologize, answer my questions and provide some beta code (scary,
but working. No calls from the PBI netcenter yet to tell me one or the
other frame circuits is bouncing up and down so that's a very good sign).
Since technical support has been my only gripe with Livingston in the past,
it's ironic that we have now experienced a combined response from Bri,
Gryphon and MegaZone within hours acknowledging that someone made a mistake
(or more accurately, didn't understand). Guess I'll have to eat some crow
for lunch now <g>!
Anyway, the misunderstanding has been cleared up.
Based on the continuing development of the IRX router code, and the
forthcoming release of BGP4, I'm much more comfortable knowing that the life
of the product has effectively been extended and is growing with us. By
itself, the BGP4 beta notice prompted us to scratch a rather large amount
from this year's budget that had been earmarked for Cisco equipment, since
it won't be needed now.
Despite the ocassional frustration, we're happy, Livingston-centric
networking folk. There are really only two things on my wish list (other
than a paid support program that isn't priced so high that the only people
who can afford it don't need it):
1. Unlimited multiple frame relay subinterfaces that don't need to be in
the same network (we could use this).
2. Allowing an 'ifconfig alias' IP address(es) on ether0 (because everyone
else wants this and it's part of the RFC.)
Once these features are implemented, I'm not sure if there is anything that
a Cisco product does that a Livingston router doesn't, which the majority of
people would really need, especially considering the cost differential.
Well, there's my $0.02.
Damien