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 |
Hi , has anybody tried to manage a Hub900 with Firmware V5.0 from a UNIX System using Hubwatch V4.1.1 ? Anyway when I try to do this Hubwatch dies with a segmentation fault. I downgraded the hub to V4.2.0 and then the UNIX based Hubwatch worked again on the same Hub900. If this is to be expected ( hubwatch/chassismanager Version and the Firmware in the MAM must be compatible) what should we tell customers that use the UNIX platform ? (leave it ,change to WIN95/NT) OTTO
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
4365.1 | NETCAD::MILLBRANDT | answer mam | Thu Apr 17 1997 18:06 | 9 | |
You cannot run MAM V5.* with HUBwatch V.Anything.Whatsoever. It will not work. Read the Release Notes, that's what they're for. You must use clearVISN V1.1A. I don't know what's up with the clearVISN UNIX release. Til there is one, customers who are stuck on UNIX should use MAM V4.2. They cannot use VNswitches or MultiStack 600 modules in those hubs. Dotsie |