| 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 |
Hubwatch 4.0.1 on OSF 3.2c
I get the following core dump wheneven I try to manage gigaswitch
we have 2 gigaswitches and I get same error for both.. Works fine for
HUBS
# hubwatch -x 16.23.112.116
HUBwatch for Digital UNIX, Revision V4.0.1
(I) HUBWATCH_LIBRARY = /usr/users/rao
(I) Using community "public"
(I) Agent type GIGAswitch found for 16.23.112.116
Unaligned access pid=12441 <hubwatch> va=2e002e002d002d pc=12047b3f0
ra=12047b480 type=stl
Segmentation fault (core dumped)
#
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2788.1 | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Mon Sep 25 1995 16:16 | 6 | |
...are you trying to manage a firmware release more recent than BL2.2?
Hubwatch becomes confused when the GIGAswitch/FDDI firmware says it has
more than 36 bridge ports. This is supposed to be fixed in a new
Hubwatch release.
MDL
| |||||
| 2788.2 | MSE1::RAO | Tue Sep 26 1995 15:28 | 6 | ||
We are running firmware 2.2, Hubwatch is at 4.0.1
When is the next release for hubwatch
/Radha
| |||||