| 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 |
Seen by customer: Connect Hubwatch v4.1.1 to DETMM in a hub. Zoom in to one of the repeater ports. Now set the name of that port. After pressing the 'apply' button hubwatch reports a time-out and lost the connection. But more seriously: All existing communications to the station connected to that port is gone!! Lat users lost the session and DECnet reports adjacency down. Has this seen before and what can be done to cure this? rgds, Ton. [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3815.1 | NETCAD::MILLBRANDT | answer mam | Thu Aug 29 1996 18:34 | 12 | |
Not a known problem. Presumably the DETMM version and DMHUB version are of a similar generation to the HUBwatch at V4.1.1? Did the DETMM reset? What does it's error log say? Are you sure your customer didn't inadvertently set the little green enable connection symbol to disable? The symptoms match what would be seen if a repeater port were disabled. Dotsie | |||||
| 3815.2 | and automatic re-enable ? | NETRIX::"[email protected]" | Ton Dekker | Fri Aug 30 1996 05:32 | 14 |
re. 1: The repeater does NOT reset. Traffic only stops on the 'related' port; i.e. where the name gets set/changed. I have to admit that the fw rev. on the repeater is 1.1 and not (yet) 2.0. However, reading the 'release notes' of detmm200 I did not find anything related to the setting of port-names. I'm pretty sure (although I've not seen it myself) that the customer did not disable the port, because after about 10-20 seconds traffic is possible again. Ton. [Posted by WWW Notes gateway] | |||||