| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
I was talking to a co-worker recently who just visited a hospital with
DEChub 900s installed. The co-worker upgraded the management station
to ClearVisn1.1a and then proceeded to test it by viewing the main
production hub. Of course, just to quickly check things out, the
person went to - you guessed it - LAN INTERCONNECT.
Everything lost connectivity everywhere. The major server got
disconnected and sent offline, folks dialed-in doing contract
development in California got bumped off (this was an east coast
location) and - in general - they were all *NOT* happy campers.
Now, you may well say that the person should have read the release
notes, checked out things etc. and prepared for an orderly upgrade.
Of course, you could also say that a measure of software quality is
that it does not cause production systems to fail because of gross user
error.
Bottom line - our 'flexibility' is killing us because of critical
design flaws. Field SEs are spending more than 50% of the time
supporting things like this (i.e. hand-holding on installed base)
instead of growing business because we do NOT publish 'how to'
documents with our management software.
And - for those of you upgrading CLEARvisn, please be sure to UPGRADE
THE FIRMWARE FIRST - before upgrading the management application.
Aarugh,
j
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4297.1 | Kentucky did it too! | PTOJJD::DANZAK | Pittsburgher � | Wed Mar 26 1997 22:29 | 10 |
Kentucky Cabinet for Natural Resources got their ClearVISN 1.1A
upgrade, installed it, and immediatly proceeded to manage
their MAM 4.x hubs with it.
No disasters yet, but they had a VN question and called me.
I stressed the need to NOT manage the MAM 4.x hubs with CV 1.1A
and need to IMMEDIATELY upgrade to V5.0 MAM.
Hopefully, they didn't crash anything...
| |||||
| 4297.2 | working on code in clearVISN to avoid this | NETCAD::MOWER | Thu Mar 27 1997 21:46 | 9 | |
We are taking this clearVISN <--> MAM version mis-match issue very seriously, and are working on adding code to clearVISN to eliminate such possibilities. Details about these changes at a future date. Just wanted you to know you have been heard, loud & clear. Carl Mower. | |||||
| 4297.3 | code has been added to check MAM version | NETCAD::MOWER | Sat Apr 12 1997 18:57 | 63 | |
> We are taking this clearVISN <--> MAM version mis-match issue very
> seriously, and are working on adding code to clearVISN to eliminate
> such possibilities. Details about these changes at a future date.
Code has been added to the LAN Interconnect view of MCM which checks
the MAM's firmware version. The next release of clearVISN, (_after_ 1.1A),
will have this code.
If MCM/LAN Interconnect finds the MAM to be at a version prior to the
version required by LAN Interconnect for proper operation, a descriptive
pop-up message is provided, and the user is prevented from invoking
LAN Interconnect. (An example of the dialog for a Hub900 follows):
+----------------------------------------------------+
| The DEChub900 MultiSwitch |
| MAM you are targeting is at version |
| v4.2 |
| |
| This version of LAN Interconnect requires |
| MAM version 5.0 or later. |
| |
| (Using this version of LAN Interconnect with |
| this older MAM could cause corruption of |
| existing backplane connections). |
| |
| The LAN Interconnect view will be terminated. |
| |
| [ OK ] |
+----------------------------------------------------+
If MCM/LAN Interconnect finds the MAM to be at a version "ahead" of the
version required by LAN Interconnect, a descriptive warning message is
produced in a dialog box, and after the user hits "OK", the LAN Interconnect
view is provided. (An example of the dialog for a Stack600 follows;
keep in mind this is just an example - no MAM v2.1 yet exists for the
Stack600, nor is one even in the works):
+----------------------------------------------------+
| The DIGITAL MultiSwitch 600 System |
| MAM you are targeting is at version |
| v2.1 |
| |
| This version of LAN Interconnect was built |
| to work with MAM version 1 and may or |
| may not work with this more recent MAM. |
| |
| Please refer to the documentation to |
| determine if LAN Interconnect will function |
| properly with this MAM version. |
| |
| [ OK ] |
+----------------------------------------------------+
The MAM versions expected by LAN Interconnect:
DEChub900 MultiSwitch .............. MAM v5.*
DIGITAL MultiSwitch 600 System ..... MAM v1.*
Carl Mower.
| |||||