[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1796.0. "HUBwatch and GIGAswitch mgmt question's" by COL01::LINNARTZ () Mon Dec 19 1994 12:27
Hi,
OSF V2.1, gotta admit, that I can't deliver the actual Version/
Revision of the Gigaswitch and Hubwatch, but they are the latest.
I'll will provide them asap.
I found it very difficult to manage the Gigaswitch. If the
Gigaswitch output is selected, everything looks fine. All
Modules/slots are shown as they are actually installed.
selecting a port on a slot via doubleclick, fires up the
next window, but the window title doesn't confim to the port
you've selected with the mouse. (ex. clicking on slot 1 - port 3,
slot 1 - port 1 is dispalyed as the window title. Also the
port type and neighbour isn't consistent.)
We checked it then with the VMS version of HUBwatch, and the effect
was the same.
another thing we realized was, when clicked on a slot, used the
port picture at the bottom of the newly created window to disable
the port, it refused a couple of times the disable action. When
we finally succeeded in getting it disabled, I monitored that IP
packets still got forwarded.
I skimmed through this conference, and didn't find a related entry.
Has nobody seen this yet?
A networking support guy assured, that the GIGAwitch modules are at
the latest revision, and that he is configured right. (for being able
to monitor them correctly, every port has got his own Ip address).
HUBwatch is running fine and correct on several HUB 900's.
Thanks in advance for any hint where to look for.
rgds
Pit
T.R | Title | User | Personal Name | Date | Lines
|
---|