| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2869.1 | firmware image or ? | NETCAD::DJERBAKA | | Wed Oct 18 1995 13:09 | 2 |
| Just a guess, but have you tried an older firmware image than 311
to see if that works?
|
| 2869.2 | | NPSS::WADE | Network Systems Support | Thu Oct 19 1995 11:23 | 9 |
| I've been in touch with Dan at the CSC. I loaded 2.0 in my lab and was
successful in going to 3.1.1 both directly and through the MAM.
Something else is going on here and the CSC will get in touch with the
customer to give them my results and get more data.
Bill
|
| 2869.3 | | CSC32::B_GOODWIN | MCI Mission Critical Support Team | Thu Oct 19 1995 16:22 | 6 |
| I just updated my DC900MX yesterday to V3.1.1 and had problems with loading via
the mam. It loaded almost completly than stoped. It did it twice. I was using
the downline load option on the DH900. When I loaded direct, it loaded ok. I was
not using hubloader, I was just using the normal tftp deamon on osf.
Brad
|
| 2869.4 | It's like getting off the freeway @rush hour - crowded | NETCAD::BATTERSBY | | Thu Oct 19 1995 17:24 | 6 |
| Loading direct is always the preferred method....it's faster.
Loading via the serial channel MAM to module is subject to the
baud rate of the serial line which is light-years slower than
wire speed (or light speed) of a FDDI LAN connection.
Bob
|
| 2869.5 | | NPSS::WADE | Network Systems Support | Wed Oct 25 1995 12:03 | 10 |
| re .0
I did more testing in the lab and at one point the 2.0.0 version got
into a state where it would not send out the TFTP req for the image.
A factory reset fixed this and I was able to load 3.1.1.
I advised Dan to have the customer set the DEF6X's back to factory defaults
and the problem was solved.
Bill
|