Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) TFTP losing configuration
I've found this usually occurs when going up to a version with new added
features not in the previous version. Sometimes the whole config gets
blown and other times it gets blown part way through (I've upgraded maxen
that will remember to answer calls but they don't have an IP address,
etc.). You might want to tftp the config over before upgrading and then
if the config is blown out after upgrade, re-config it and do a diff on
the config files. They're probably some parts the new config has that the
other one doesn't, but this is strictly a guess.
And speaking of new added features, I think it's been a poor decision to
do away with the seperate incremental and patch versions of software.
I liked being able to get bugfixes with patch releases instead of new
features which more times than not break some fucntionality I need. I
have been treating the 6.x branch of code like a rabid dog after the
numerous troubles I've heard about from people with simple setups. Lord
only knows how broken it would be doing stacking and OSPF on my maxen.
And these software loads are starting to get huge. How long before the
MAX 4xxx will be like the Pipeline 400 and not have the necessary
resources to function? We've already seen it with several pipeline models
(yet you guys are still selling one of the worst routers ever, the
MAX200+) and I guess it will only be a matter of time before Ascend sticks
one too many new features into the latest batch of code and the MAX won't
be able to deal with it. With some of the memmory leak problems a lot of
us have faced, I believe that moment may not be far off. Will you guys
start considering more bare bones loads then? Right now I'd just like to
see a load with every major TR that's left open fixed and no new
features or functionality.
Hope everyone's had a nice holidy weekend. "If you're driving don't
drink, and if you're drinking, don't drive." - MCA, Beastie Boys.
Joe Shaw - jshaw@insync.net
NetAdmin - Insync Internet Services
On Sat, 4 Jul 1998, robert wrote:
> Is there any special trick to TFTP'ing new versions of code to a
> pipeline 50/75/130? I've done it maybe 30 times, using the correct syntax
> [tload host loadcode], however maybe one out of every 5 times when the
> unit reboots, its config has been reset. I tried typing fsave before the
> load, and it still happened.. then I tried fsave after the tload,
> followed by reset to reboot, same thing. I was wondering if anyone has
> experienced the same problem before; or if there's any reliable method out
> there to ensure that the configuration remains intact after the load?
>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: