| 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, We run HUBwatch T1.1.18 and agent X1.75. I tried the following: I had a LAT connection from a DS90L+. From HUBwatch I setted the port to disbled. (Opened the green arrow -->changed to red) After that the HUBwatch showed me "no session info availible". But after I was able to work on this port without any problems. Magic to work on a disabled port without any session info. Regards Roland
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 217.1 | "magic"? | SLINK::HOOD | Just add water | Wed Apr 28 1993 12:00 | 13 |
Changing the adminStatus on the DS90L+ to disabled does *not* reset that port. Rather it means that after the current sessions are completed, no further sessions will be allowed. So, when you set a port to disabled thru HUBwatch, HUBwatch correctly sends a message to the DS90L+ to set adminStatus to disabled. When HUBwatch then goes out for the DS90L+ summary screen, it gets back "disabled" adminStatus and does not try to get session information (which is sometimes unpredictable if the adminStatus is not enabled). Therefore, HUBwatch returns the "no session info available" message. It explicitly does NOT say "no sessions". Tom Hood HUBwatch devo | |||||
| 217.2 | Thanks | ZUR01::SCHNEIDERR | Thu Apr 29 1993 05:23 | 6 | |
Hello Tom, O.K., thanks for your answer Roland | |||||