| 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 |
Hello,
I have a customer who is running Hubwatch V1.1 for Ultrix with a
dechub90, decagent 90 (V1.1) and decbridge 90 (V3.0).
He is trying to implement protocol filtering on the Decbridge90 and is
having problems.
He double clicks on the bridge, selects the filtering option, chooses
the protocol he wants and the type of filtering and then selects
"apply". After doing this the entry disappears and is not added (no
entries are added). There is no message in the hubwatch start up
window.
Has anyone seen this before and can offer an explanation?
Is V1.1 on Ultrix still supported?
I tried to use ccr to the bridge, but a connection only lasts about 5
seconds before it is disconnected with
"ccr Retry limit exceeded"
"ccr: Remote console released"
I can't reproduce this as I only have Hubwatch for VMS V2.0 & V3.0 &
filtering works on these versions.
Thanks for any help.
Jon
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1123.1 | Still not working... | KERNEL::WARDJO | Mon Jul 11 1994 12:35 | 16 | |
Can anyone tell me if Hubwatch for Ultrix V1.1 is supported.
I got the customer to upgrade his decbridge90 from V3.0 to V3.1 and he
found that having done one bridge, his other 10 could not see each
other (I don't know exactly what the problem was, but no one on his Lan
could work). After upgradeing all bridges it was ok again.
Anyone seen anything like this before - are v3.0 & V3.1 incompatable?
The original problem still persists - Can anyone help.
Thanks
Jon
| |||||
| 1123.2 | SLINK::HOOD | I'd rather be at the Kennebec | Mon Jul 11 1994 13:03 | 3 | |
(Answered via mail) Tom Hood | |||||