Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: (ASCEND) P75 upgrades
Actually, you may be onto something. I upgrade all my Pipeline 75s here in the office before sending them to the field. When I later upgrade them to a newer rev in the field (remotely using Telnet), I have had a 100% success rate. However, when I upgrade them before sending them to the field I occasionally lose the configuration after the upgrade. I have assumed that I just made a simple mistake causing me to reload the configuration or that terminal mode didn't work as well as telnet. In any case I didn't think anything of it. I do agree that this problem may only affect devices with the factory configuration (a device that has never been upgraded) because I have never had this problem on a Pipeline 75 after its first upgrade.
Mitch
-----Original Message-----
From: Joseph Bridgewater <Joseph@dontspamaustintx.net.bungi.com> [mailto:Joseph@dontspamaustintx.net.bungi.com]
Sent: Wednesday, May 13, 1998 10:42 AM
To: <ascend-users@bungi.com>
Subject: Re: (ASCEND) P75 upgrades
I nearly always use a telnet session, but have seen the failure both ways.
I've followed that exact procedure (tload -> fsave ->nvramclear ->doesn't
restore fsaved config). Again; appears to only be devices never upgraded
before.
On those that have worked for you, have any/all of them never been upgraded
before?
At 09:46 PM 5/13/98 -0400, Mitchell.Arnone@occ.treas.gov wrote:
>I have configured and deployed 20 Pipeline 75s. When upgrading my
firmware to 6.0, I first do the tload then fsave then nvramclear. When I
do this from a telnet session, it has worked without losing the original
configuration 100% of the time. I did experience a failure one time but I
was doing the upgrade from a terminal connection using hyperterminal. I
don't know if it realy matters whether or not the connection to the
pipeline is established via telnet or hyperterm but this has been my
experience so far.
>
>Semper Fi, Mitch
>---------- Original Text ----------
>
>From: Joseph Bridgewater <Joseph@dontspamaustintx.net.bungi.com>, on
5/12/98 7:10 AM:
>
>I've done the fsave immediately after the tload and the P75 *still* don't
>come back up without prodding via serial cable. Need to work with a client
>to fix one this evening in fact (5.1A -> 5.1Ap9)
>
>I do think the instructions have been amended as such, but it doesn't do
>any good.
>
>It seems (I think I read this here a couple month or so back) that if the
>Pipeline hasn't been upgraded via tload before, it will not come back up.
>Once it has, it will work as expected.
>
>At 03:08 PM 5/12/98 -0700, Kevin A. Smith wrote:
>>At 04:51 PM 5/12/98 -0400, Charlie Taylor wrote:
>>>I've been upgrading a number of Pipeline75 from various versions of
>>>5.0 to 6.0.2 via tloadcode. The steps are
>>>
>>> 1. fsave
>>> 2. tloadcode hostname filename
>>
>>2.a fsave
>>
>>> 3. nvramclear
>>>
>>>This seems to work about 50% of the time. The other 50%, when the pipeline
>>>reboots it comes up in the factory config. If I then put a serial cable on
>>>it, go do diags and type "nvramclear" again, it reboots and comes up with
>>>its correct (saved) configuration.
>>>
>>>Am I doing something wrong? Is there some trick to getting this to work
>>>reliably? Clearly, having to go out and stick a serial cable on these
>>>units to upgrade them is time consuming and should be unnecessary.
>>
>>I thought the upgrade process had been modified to include the fsave *after*
>>the tload?
++ 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>
Follow-Ups: