| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1081.1 | | TOOK::MORRISON | Bob M. LKG1-3/A11 226-7570 | Tue Jun 07 1994 22:40 | 3 |
| I am making inquiries off-line and I'm confident that I will eventually get
the new firmware installed. My reason for posting this is to express concern
over how customers will react to this.
|
| 1081.2 | | SLINK::HOOD | I'd rather be at the Kennebec | Tue Jun 07 1994 22:58 | 4 |
| Out of curiosity, what was the challenge in installing HUBwatch?
Tom Hood
HUBwatch
|
| 1081.3 | | TOOK::MORRISON | Bob M. LKG1-3/A11 226-7570 | Wed Jun 08 1994 17:22 | 5 |
| The main challenge in installing Hubwatch was that I had to install UCX first,
and I had some difficulty getting documentation and a kit for UCX. There was
also something else I had to install or set up (I forgot what) that was
difficult. Installing Hubwatch itself was not too difficult, once the other
stuff was in place.
|
| 1081.4 | We know our documentation leaves *much* to be desired | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Jun 08 1994 17:28 | 16 |
| RE: .0, .1
Bob, your concerns are noted and appreciated. We know there is a big hole in
the upgrade process, and its name is 'documentation'.
I am making a list of people who are having problems with the hub upgrade,
whether it's related to the firmware, documentation or the process in general.
Hopefully this will help us justify the necessary resources that were "diverted"
in the first round.
Anyone else having problems please make your opinions known. And yes, this
forum is a good place to be heard (well, "seen" maybe be more accurate). The
bigger the list, the more ammunition we have to justify devoting the resources
to fix the problems.
...Roger...
|
| 1081.5 | using ndu | NYOSS1::HERENDEEN | Tom Herendeen @NYO, 352-2936 | Thu Jun 09 1994 12:25 | 16 |
| This is probably not the right place to mention this, but since we're
talking about NDUplus, I'd like to pass on something that may make
things easier:
The binary for ULTRIX is called "decndup", but the man pages entry is
"decndu"
By the way, thanks for the examples in the man pages!!!!! I can't tell
you how many other entries don't have examples.
I've just finished using NDU to upgrade DH900's, DB900MX's and a
GIGAswitch, a bit of trial and error, but it all worked (now if I can
find out what an "ELCAMINO" is on a GS...)
Tom Herendeen
NY PSC
|
| 1081.6 | Success | TOOK::MORRISON | Bob M. LKG1-3/A11 226-7570 | Mon Jun 13 1994 18:32 | 21 |
| After some more trial and error, I successfully upgraded the MAM (using VMS).
Here are two more pitfalls that apply to VMS, which I hope will be documented.
(I don't know if these apply to U*ix.):
1. The default community-name is "public". If your community is not at default,
you must add switch "/password=<community>" to the command line. If your com-
munity is uppercase PUBLIC, it is not at default and you must add this switch,
or else the load will fail when it tries to write to the hub. (The first oper-
ation, which is an SNMP read, works, as does a DOWNLOAD LOAD SHOW <IP_addr>,
which is a standalone SNMP read.)
Also, the community-name in the switch must case-match the one on the hub.
If the hub's community-name is uppercase, you can enter it on the VMS command
line without quotes; it is uppercased by VMS. Otherwise, you must enclose it
in quotes to preserve case.
2. Do not enable TFTP on UCX. DECndu creates its own TFTP daemon and if you have
manually enabled TFTP on UCX, you have two TPTP servers going and trouble
occurs. Specifically, the job hangs at STARTING TFTP SERVER.
It appears that the problem in note 1092 is due to mismatched community name,
but could be something else.
|