| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 934.1 | Upgrading from V2.20 to V3.10 | NPSS::RLEBLANC | | Tue Feb 18 1997 08:43 | 12 |
|
The SCP is the only Module that needs to transition to V2.20
before going to V3.10.
The FGLs/AGLs and Clock Card can be directly upgraded from V2.00
to V3.10 or V3.00 in the CLK card case.
Cheers,
Rene'
|
| 934.2 | SCP image | RDGENG::GREID | I'm a firestarter, twisted firestarter | Tue Feb 18 1997 10:31 | 22 |
| Rene',
I have the following SCP files on my local Digital/Unix
box, I presume the only one I need to TFTP to the two SCPs I have is
the one arrowed :-
scp_bb_200.mop
scp_bb_200.sys
scp_bb_200.tftp
scp_dl_100.mop
scp_dl_100.sys
scp_dl_100.tftp
scp_op_301.mop
scp_op_301.sys
scp_op_301.tftp
scp_op_306.tftp
scp_op_309.tftp <----------
What are the -bb- and -dl- files... do I need them ?
Giles.
|
| 934.3 | Note 914.0 Firmware release notification | NPSS::RLEBLANC | | Tue Feb 18 1997 11:42 | 7 |
|
Yes, tftp is the one you need. But I'll refer you to 914.0 on the
other questions :^).
Cheers,
Rene'
|
| 934.4 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Tue Feb 18 1997 12:48 | 8 |
| In case you didn't get the hint, you do *not* have the most current
firmware (BL3.1) on your Digital Unix system. The BL3.1 upgrade includes
two updates to the SCP module, one to the operational firmware, and one
to the bootblock image.
As Rene suggests, note 914 contains pointers to the BL3.1 release.
MDL
|
| 934.5 | BL3.1 it is then | RDGENG::GREID | I'm a firestarter, twisted firestarter | Wed Feb 19 1997 04:20 | 7 |
|
Cheers chaps, I'm off to take that HINT and look at #914.... ;-)
Mike, I'm just not worthy... 8)
Giles.
|
| 934.6 | Cannot NDU from VMS | RDGENG::GREID | I'm a firestarter, twisted firestarter | Fri Feb 21 1997 07:12 | 43 |
|
Well, I'm having a lot of trouble NDUing my GIGASWITCH from several
VMS boxes.
I have copied the .rsx and .sys files to ucx$tftp_root and made them World
Read and Execute. I have a running BOOTP and TFTP service in UCX. I
have the correct routes set up and see the BOOTP request arrive, but
it never gets any further than this ...
Peevie..>@DOWNLOAD_NDU_GIGA.COM;
Loading GIGA1 Line Cards
Loading GIGA1 Line Card Module 1 - FGL2
(c) Digital Equipment Corporation. 1993. All Rights Reserved.
HOSTNAME: peevie.reo.dec.com
Server: 16.37.96.6
DECNDU: (TFTP) Target address = 16.37.96.254
setting Slot Number
[GIGAswitch] Getting TFTP Server IP address.
16.37.96.6
[GIGAswitch] Setting TFTP Server IP Address.
[GIGAswitch] Getting TFTP Server IP address.
16.37.96.6
[GIGAswitch] Getting firmware image file name.
SYS$SYSDEVICE:[UCX$TFTP_ROOT]FGL2_OP_310.RSX
[GIGAswitch] Setting firmware image file name.
[GIGAswitch] Getting firmware image file name.
SYS$SYSDEVICE:[UCX$TFTP_ROOT]FGL2_OP_310.RSX
[GIGAswitch] Triggering image file transfer.
[GIGAswitch] Starting TFTP Server
I have tried this on there different VMS machines, with the same
effect. I have tried putting the files in MOM$LOAD and this makes no
difference.
So what's happening .....
Giles.
|
| 934.7 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Fri Feb 21 1997 09:48 | 21 |
| Uncloak your .COM file - i.e. turn verify on so we can see what
you're doing..., but for starters:
.sys files are for Ultrix MOP. .tftp files are for tftp - NDU+
and just about everything else uses tftp.
NDU+ on VMS loads it from the directory you're in. There is no
need to copy it to mom$load.
...and of course, do *NOT* run TFTP on IP services for VMS or
whatever you're using. NDU+ has its own TFTP server and having two
TFTP services doesn't work. I suspect from what .6 says that you are
running multiple TFTP servers.
This is an example of a working NDU+ command string on VMS:
$ Downline load 16.20.152.54 fgl_op_300.rsx /force=gigaswitch -
/password="08002ba1c780" /Module=14
P.S. Look at the notes under the keyword upgrade-problems for the
complete list of things you can do wrong.
|
| 934.8 | Still not working - have used checklist | RDGENG::GREID | I'm a firestarter, twisted firestarter | Fri Feb 21 1997 10:08 | 51 |
| Mike,
The system I am currently trying from is a VMS6.1
system with UCX V4.0. I have disabled TFTP and BOOTP. Here is
an uncloaking :-
Peevie..>@DOWNLOAD_NDU_GIGA.COM;
$ if p1 .nes. "" then goto
$ !
$ GIGA1:
$ !
$ ! GIGA1 Line cards
$ !
$ write sys$output "Loading GIGA1 Line Cards"
Loading GIGA1 Line Cards
$ !
$ ! Slot 1
$ write sys$output "Loading GIGA1 Line Card Module 1 - FGL2"
Loading GIGA1 Line Card Module 1 - FGL2
$ DOWNLOAD LOAD /MODULE=1 /PASS="08002bb4c100" -
/FORCE=GIGASWITCH 16.37.96.254
sys$sysdevice:[ucx$tftp_root]fgl2_op_310.rsx
(c) Digital Equipment Corporation. 1993. All Rights Reserved.
HOSTNAME: peevie.reo.dec.com
Server: 16.37.96.6
DECNDU: (TFTP) Target address = 16.37.96.254
setting Slot Number
[GIGAswitch] Getting TFTP Server IP address.
16.37.96.6
[GIGAswitch] Setting TFTP Server IP Address.
[GIGAswitch] Getting TFTP Server IP address.
16.37.96.6
[GIGAswitch] Getting firmware image file name.
SYS$SYSDEVICE:[UCX$TFTP_ROOT]FGL2_OP_310.RSX
[GIGAswitch] Setting firmware image file name.
[GIGAswitch] Getting firmware image file name.
SYS$SYSDEVICE:[UCX$TFTP_ROOT]FGL2_OP_310.RSX
[GIGAswitch] Triggering image file transfer.
[GIGAswitch] Starting TFTP Server
That's as far as it gets, even with the file modified
to reflect the .TFTP files for the SCP instead of .SYS files.
Giles.
|
| 934.9 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Fri Feb 21 1997 10:33 | 4 |
| Your filename looks rather long. Is there some reason you are
specifying the entire directory specification?
MDL
|
| 934.10 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Fri Feb 21 1997 10:43 | 4 |
| ...and I would double check the tftp/bootp server status to be certain
that however you disabled them truly removed all the traces.
MDL
|
| 934.11 | Just small file spec now | RDGENG::GREID | I'm a firestarter, twisted firestarter | Fri Feb 21 1997 10:44 | 27 |
| Mike,
Force of habit I guess that I usually copy firmware into
SYS$SYSDEVICE:[UCX$TFTP_ROOT] as that's where I load my DECHub software
from via UCX TFTP/BOOTP.
I have now copied all the files to my default login directory and
modified the DOWNLOAD_NDU_GIGA.COM script so that the spec is -
$ DOWNLOAD LOAD /MODULE=1 /PASS="08002bb4c100" -
/FORCE=GIGASWITCH 16.37.96.254 fgl2_op_310.rsx
The script runs from there anyway, but still no joy with the
program getting any further. 8(
Maybe the LAN is too busy ? The GIGAswitch is just purely connected
to our FDDI ring here with a single connection from port 9.1 which
is set-up as a priviledged port. There is nothing connected to it,
and the load host is only connected to a DEChub 900 (Repeater) which
is dual homed to the ring.
I certainly was seeing the BOOTP request come in.
Any more ideas ?
Giles.
|
| 934.12 | | RDGENG::GREID | I'm a firestarter, twisted firestarter | Fri Feb 21 1997 10:56 | 17 |
|
Peevie..>ucx sho service tftp
Service Port Proto Process Address State
TFTP 69 UDP UCX$TFTP 0.0.0.0 Disabled
Peevie..>ucx sho service bootp
Service Port Proto Process Address State
BOOTP 67 UDP UCX$BOOTP 0.0.0.0 Disabled
Peevie..>
This is after disabling them in the server side of UCX$CONFIG and then
doing a shutdown/startup
Giles.
|
| 934.13 | It works..... | RDGENG::GREID | I'm a firestarter, twisted firestarter | Fri Feb 21 1997 10:58 | 9 |
| Mike,
Amazingly, I have just run the proceedure and it's working now.
So just doing a disable of the services inside UCX isn't enough.
I will now put my thumb in my mouth and look sheepish. 8)
Giles.
|
| 934.14 | FGL4 won't upgrade to V3.1 | RDGENG::GREID | I'm a firestarter, twisted firestarter | Mon Feb 24 1997 03:29 | 62 |
|
One of my FGL4s will not upgrade to 3.1 as follows :-
Peevie..>DOWNLOAD LOAD /MODULE=11/PASS="08002bb4c100" /FORCE=GIGASWITCH
16.37.96
.254 fgl4_op_310.rsx
(c) Digital Equipment Corporation. 1993. All Rights Reserved.
HOSTNAME: peevie.reo.dec.com
Server: 16.37.96.6
DECNDU: (TFTP) Target address = 16.37.96.254
setting Slot Number
[GIGAswitch] Getting TFTP Server IP address.
16.37.96.6
[GIGAswitch] Setting TFTP Server IP Address.
[GIGAswitch] Getting TFTP Server IP address.
16.37.96.6
[GIGAswitch] Getting firmware image file name.
FGL4_OP_310.RSX
[GIGAswitch] Setting firmware image file name.
[GIGAswitch] Getting firmware image file name.
FGL4_OP_310.RSX
[GIGAswitch] Triggering image file transfer.
[GIGAswitch] Starting TFTP Server
DECNDU: (TFTP) Blocks sent = 426
DECNDU: (TFTP) Transfer Complete.
[GIGAswitch] Polling for file transfer completion.
5 - SUCCESS
[GIGAswitch] Getting slot number.
11
[GIGAswitch] Setting slot number.
[GIGAswitch] Getting slot number.
11
[GIGAswitch] Getting copyType.
[GIGAswitch] Triggering flash update.
[GIGAswitch] Polling for load completion.
3 - IN_PROGRESS
3 - IN_PROGRESS
3 - IN_PROGRESS
3 - IN_PROGRESS
3 - IN_PROGRESS
4 - FAILED
I have tried doing a management power cycle from the menu
but it still does the above. Initially the board is seen as a revision
mismatch, as I would expect, but after the above load fails it is just
seen as initialised at 2.00.
Should I get this board replaced ?
Giles.
|
| 934.15 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Feb 24 1997 09:50 | 3 |
| It's broken. Have it replaced.
MDL
|