| I've seen this problem when you go from way out-of-rev firmware to the
latest. Uusally power-cycling the whole mess fixes it. (i.e. we
needed to physically pop a DECconcentrator out/in of the slot to fix
it)
And, of course, this is NOT a problem since you sold them the Recovery
Manager (aka Backup and Destroy...) Right?
(grin)
|
| Well, the potential of Recovery Manager licenses will grow as we
install VNSwitches, since many of them wil definitely use MCM V6
on the MAM V4.1 firmware, or MCM V5 on MAM V5.1 firmware.
Have the sales-force or installation force been informed about this
mismatch between MCM and MAM? They know the requirements for new
firmware in the MAM, when a VNswitch is installed in it, but have
anyone done some thinking of how to warn the customers about this
mismatch? A customer with 9 Multiswitch900 buys another MS900, with
VNswitches in it, and upgrades the PC to run MCM V6, and upgrades
his 10th MS900 (because it is never at rev 5.1). Before he upgrades
the 9 others, he uses MCM V6 to look at LAN Interconnect, and gets
the configuration screwed up!!! AND; this is happening right now.
Bj�rn Olav
|