| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4221.1 | Not officially supported - upgrade hub to V5.0 | NETCAD::MILLBRANDT | answer mam | Thu Feb 20 1997 10:04 | 16 |
| Hi Brad -
Well, it will look okay with a "pure" V4.2 hub - one whose modules are at
compatible versions. However, if the hub contains modules not supported
on V4.2 (particularly VNswitches), MCM V5.1/V6.0 has been seen to paint
"imaginative" LAN Interconnect screens. Backward compatibility was not
a release goal nor is supported.
MAM V5.0 will be available at the same time as MCM V5.1, so it will be
best to upgrade the hub, then the NMS. The release notes say this (about
ten times). If you have any customers who used VNswitch seed units with V4.2,
make sure they are aware.
Thanks,
Dotsie
|
| 4221.2 | | CSC32::B_GOODWIN | Brad Goodwin - NSIS | Thu Feb 20 1997 11:05 | 10 |
| Thanks Dotsie,
I was just asking because my customer is ordering alot of VNswitches
and they have alot of hubs. The hubs with VNswitches will get upgraded
to MAM V5, but they have alot of hubs without VNswitches running MAM
V4.x that might take some time to upgrade because they are spread all
over the country. I wanted to find out if they could use MCM V5.1/6.0
on those hubs until they can get them upgraded.
Brad
|
| 4221.3 | | NETCAD::DOODY | Michael Doody | Thu Feb 20 1997 14:51 | 9 |
| Unfortunately, it doesn't matter what modules are in the hub.
MCM 6 cannot manage a V4.x hub. I'm not a clearvisn person
so I can't remember all the version numbers, but I know the
latest clearvisn MCM cannot manage a v4.2 hub. You have
to stick with the MAM / MCM combinations that are shipped
together on the cdrom.
-mike
|
| 4221.4 | very important to keep correct MAM/MCM pairs | NETCAD::MOWER | | Sat Mar 01 1997 23:02 | 21 |
|
Mike is exactly correct: use MAM/MCM combinations as they are shipped
together - extremely important.
MAM 4.2 -- clearVISN 1.0
MAM 5.0 -- clearVISN 1.1a
I understand that for large installations at any time you will have some
hubs at 4.2 and some at 5.0. This will require you to have two clearVISN
installations: clearVISN 1.0 and clearVISN 1.1a, and you will need to
keep it straight which clearVISN with which hubs. (Since it is difficult
to run two clearVISN versions on the same PC, you will need 2 PCs during
the transition).
I understand the great trouble this causes; we, (specifically, I) are/am
looking into ways to at the very least, improve this.
Carl Mower
"clearVISN person"
|