| 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 |
I have a customer who is running hubwatch V4. for Windows. He also has
version 4 of the firmware for the hub900. His problem is that he has
amongst the modules a decserver 90TL. On one of his PCs, whilst he can
see the module, it has no LEDs lit on it, even though on the actual
module they are. On another of his PCs, whilst the power light, the
self-test Ok light and the network Ok light come on, there are no other
LEDs on the 90TL in hubwatch.
I have tested this on my terminal and whilst I had to set up the 90TL
in the community manage table (something which I have also taken the
customer through), it worked fine.
The customer gets an error message of no response from agent when he
tries to manage the 90TL on its own and also when he tries to refresh
the display, having set up the 90TL as an agent, in his Message Box
window, he gets an error: "RPT900 Missing LED Data.....".
I have two questions:
1. Why is the customer getting the error message about the missing
LED data?
2. Why isn't the 90TL working when it has been set up as an agent.
Can anyone help me at all?
Many thanks in advance for any help
Will
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2776.1 | Questions and HUBwatch bug | STEVEV::VINGERHOET | Thu Sep 21 1995 10:33 | 20 | |
I'm a bit confused here. You're talking about a DECserver 90TL but yet the message that pops up is in regard to DECrepeaters. I believe that the message that is printed out about RPT900 missing led data and the fact that the LEDs are not lit are due to HUBwatch not handling the MIB information properly. Currently, when a DECrepeater 900CP or DECrepeater 900TP have their button pushed in on the physical bezel (not HUBwatch), the firmware only returns the information on the LEDs shown on the module. HUBwatch unfortunately takes this to mean that not all the LED information is available and takes the action describe above. This will be fixed in V5.0. Do you know if the button is pressed on your module. If you are having a problem with the DECserver 90TL it may be caused the firmware not responding to all the SNMP requests. Check that the lastest firmware is installed. Steve HUBwatch Team | |||||
| 2776.2 | Further Questions On HUBwatch bug with 90TL | KERNEL::ELCOCKW | Thu Sep 21 1995 13:11 | 22 | |
Steve,
Many thanks for your reply.
I still have a query though:
If there is a problem with SNMP responses on the 90TL, why is it that
on one hubwatch session, there are some LEDs lit and on another none?
Is there a reason for the lack of consistancy on this problem?
In addition, why would the user be getting a 'no response from agent'
message when he tries to double-click on it in hubwatch, even when the
90TL has been successfully set up as an agent.
Again, I would be extremely grateful for any light which either you or
anyone else could shed upon this problem
Many thanks
Will
| |||||