T.R | Title | User | Personal Name | Date | Lines |
---|
2935.1 | | NETCAD::DOODY | Michael Doody | Tue Oct 31 1995 09:30 | 6 |
| "What we have here, is a failure to communicate"�
What are you using for a tftp server? Can you ping the hub from the PC?
I don't think the packets are making it to the hub.
md
|
2935.2 | need a TFTP server | ZPOVC::HWCHOY | On a foul day, you can complain forever. | Thu Nov 02 1995 07:52 | 2 |
| You have to start the Netrider TFTP server (which gets installed along
with HUBloader).
|
2935.3 | THINKS ITS LOADING | VIVIAN::CHARLICK | " It's only a piece of string" | Fri Nov 03 1995 05:30 | 15 |
| Thanks for the reply's
The TFTP server I'm using is the one that comes with hubwatch
AND it seems to be working, I checked before I tried a load (opened the
tftp server window) and it was already loading.
The hubloader regularly gives an update once I start it, in the progress
log it updates every 15secs or is this just telling me its sending and
after 315secs it fails.
hubwatch works fine so I have the link !!!
rgds
steve
|
2935.4 | I have the same failure mode | NCMAIL::BANKOWSKIJ | | Tue Nov 07 1995 17:22 | 12 |
| I have the same thing happening to me. However, I'm going from a 4.0
MAM to a 4.1 MAM upgrade and I'm using HUBwatch 4.1 on my PC. The
connection is fine. I can see the Hub via HUBwatch and HUBloader
identifies each module in the hub when I select the slot.
Do I have to be plugged into the IP services module on the hub? If so,
what about a 20 hub network - or 5 hubs for that matter! I don't think
going to each hub to plug into the IP services module sounds the least
bit attractive.
Regards,
Jim
|
2935.5 | | CSC32::B_GOODWIN | MCI Mission Critical Support Team | Wed Nov 08 1995 09:53 | 63 |
| I don't know if this is the same problem. But, I had something like your problem
loading from my pc. *** Beware of the Digital PCBU PCMCIA ethernet card. It is
garbage. *** You can identify this card by:
Remove your PCMCIA ETHERNET card from your Laptop. The cards that
are generating problems have a yellow and purple background behind
a black digital logo in the upper left hand corner. Below this is
a black stripe with the words "Ethernet Adapter" and there is no
model number or part number on the back.
After trying to upgrade my mam, it would fail. When connected to the console of
the dh900 and doing option 3 "Show Current Settings" for "Status of Last
Downline Upgrade" it showed "CRC Error" or something of that nature.
More info on the card follows:
From: NETCAD::DENAULT "Adrienne DTN 226-6025 30-Oct-1995 1631 -0500"
30-OCT-1995 16:01:23.52
To: @IPCINTEREST.DIS,@NETWORKS.DIS
CC: DENAULT
Subj: More on the PCMCIA card problem
The PCBU is working on getting a process in place to take care of the
problem...They should have a solution soon and I will send that
out as soon as I get it.
Adrienne
From: PCBUOA::GLANTZ "now in the PC group at DTN 244-7478" 27-OCT-1995
17:15:21.32
To: @XXSUPPORT, @XSUPPORT, STAR::ROBIE, NOTAPC::VEAR, MANDEVILLE, KIRBY,
TINCUP::MOE, KALI::DENAULT
CC: SSMITH, LIGUORI, DUNIGAN, STOWOA::LAPOINTE, JSTONE, ERAINE, ODONNELL
Subj: ETHERNET CARD TO BE REPLACED
Based on PCBU Engineering's continual testing of PCMCIA Cards, we have un-
covered a reliability problem with the Digital-branded Ethernet card. We
have placed the following cards on SHIP HOLD:
FR-PCP78-AD (combo 10baseT/10base2)
FR-PCP78-AC (10baseT)
The typical symptoms on the combo card are intermittent bursts of CRC's, high
collision rates, and misaligned frames, eventually resulting in a crashed
network. Although the problems were only detected on 10base2, to be conser-
vative we placed on hold the 10baseT card as well. Retesting of that card
will be completed next week.
Please do not confuse this product with the DEPCM-A* product offered by the
Network Products BU.
It is the the intention of the PCBU to offer to replace defective cards with
the customer's choice of a card from a specified set of other cards that pass
our full compatibility and reliability test suite.
At this point, we do not have a process in place. We expect to announce a
simple swap process in the very near future.
Please understand that we fully realize how frustrating this entire scenario
has been with these cards and are doing everything possible to rectify this
situation as quickly as possible.
|
2935.6 | | NETCAD::DOODY | Michael Doody | Wed Nov 08 1995 11:13 | 19 |
| >The TFTP server I'm using is the one that comes with hubwatch AND it
>seems to be working, I checked before I tried a load (opened the tftp
>server window) and it was already loading.
It probably wasn't already loading if you checked it BEFORE...
probably the BOOTP request counter was ticking.
You need to see the TFTP request & response counters _both_ increment
by 1 to know that the MAM requested the image. Also, in the lower
window the "transfer cnt" number should be constantly increasing.
>The hubloader regularly gives an update once I start it, in the
>progress log it updates every 15secs or is this just telling me its
>sending and after 315secs it fails.
The Hubload update is merely polling the MAM to see what the current
status of the MAM is. You can't tell from the status how many
retries are happening for instance, or even if the MAM has seen any
packets at all yet - you just know that it is trying.
|
2935.7 | | NETCAD::DOODY | Michael Doody | Wed Nov 08 1995 11:19 | 23 |
| >I have the same thing happening to me. However, I'm going from a 4.0
>MAM to a 4.1 MAM upgrade and I'm using HUBwatch 4.1 on my PC. The
>connection is fine. I can see the Hub via HUBwatch and HUBloader
>identifies each module in the hub when I select the slot.
Check for the things in my previous reply -.1 . Also, make sure the
IP address and host name are correct for your PC in the
\netrider\load\loader.ini file.
>Do I have to be plugged into the IP services module on the hub? If so,
>what about a 20 hub network - or 5 hubs for that matter! I don't think
>going to each hub to plug into the IP services module sounds the least
>bit attractive.
Well, you need connectivity to your hub. If you manage your hub
in-band then you need connectivity to the IP services module. Just like
for Hubwatch. No different.
Regards,
-Mike
|
2935.8 | version 3.1 works ok | VIVIAN::CHARLICK | " It's only a piece of string" | Thu Nov 09 1995 10:07 | 18 |
| just back from site..
I had a copy of mam 3.1 so I tried that just to see as this
particular hub was running version 2.*.
This worked fine so I then tried v 4.1 again and got the failure???
when I look at the two images the V4 is about twice as big as V3.
I also checked the loader counts as per previous reply and they
do increase ok
still confused but maybe a reinstall of the "very latest" Version
of the software may fix this.
rgds
steve
|
2935.9 | This should work | NCMAIL::BANKOWSKIJ | | Mon Nov 13 1995 16:12 | 6 |
| In Reply to note .5. I have the DEPCM-A* card offered by NPBU and not
the inferior PCBU card. All my *.ini files have the correct IP host
address. That includes the netrider\load\loader.ini file. As far as
connecting in-band, I hope I can access the IP services module (DETMM)
thru an external port off a DECswitch 900EF and across the backplane of
the DEChub 900. This same config worked when I loaded 4.0 from 3.1!
|
2935.10 | success at last | NCMAIL::BANKOWSKIJ | | Fri Dec 08 1995 15:22 | 6 |
| Well, I directly connected the PC to the 900TM and it worked! It
should have worked going the through the 900EF and the backplane
segments. I don't think (feel) I should have needed to increase the
time-out value on the HUBloader.
Anyway, it finally worked...
|