| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2305.1 | double-click on a port. | SLINK::HOOD | Maine state bird: The black fly | Tue May 23 1995 11:14 | 9 |
| To get Ethernet counters for PEswitch 900TX, DECswitch 900EE, DECswitch 900EF,
DECbridge 900MX, or RoamAbout Access, double-click on a port, either from
the front panel, or from the bridge/switch summary window.
Tom Hood
HUBwatch
>> I hope this is not a dumb question.
Nope, *I* could answer it. I refer all dumb questions to Roger Gaudet.
|
| 2305.2 | At no extra charge | ROGER::GAUDET | Because the Earth is 2/3 water | Tue May 23 1995 14:04 | 3 |
| And for those questions that Tom forwards, I always give a dumb answer. :-)
Answer_Grape
|
| 2305.3 | | CGOOA::PITULEY | Ain't technology wonderful? | Tue May 23 1995 14:21 | 5 |
| ....sounds like the whole system works *very* well........
:-)
|
| 2305.4 | Still doesn't work - Counters for DEcswitch 900EF Ethernet Ports | GIDDAY::STANISLAUS | | Wed May 24 1995 01:14 | 25 |
| Tom,
Regarding your response in 2305.1:
----------------------------------
I borrowed a DECswitch 900EF from field service and put it into our
DEChub 900 which has the Hubmanager at ver 3.1 and the DECswitch is at ver 1.4
I am running Hubwatch ver 3.0.0 of Hubwatch on a VMS ver 6.1 system.
As I stated in notes 2305.0 of HUB_MGNT notes conference, I double
clicked on the DECswitch900EF's Ethernet ports and nothing happens. I don't
get the hour-glass or the response for the double-click.
(I might mention here that I did not have anything connected to any of
the ports of the DECswitch 900EF.)
But if I do the above operation (double-click) on a DECrepeater 900TM,
900GM, 900FP or DECconcentrator 900MX, I get the counters for the selected
port. Again I don't have anything connected to these ports but yet I can get the
counters information screen. I can't seem to be doing anything stupid.
I shall upgrade Hubwatch to 3.1 and see what happens.
Regards,
Alphonse
|
| 2305.5 | Maybe by upgrading to HUBwatch 3.1 problem will dissapear | NETCAD::BATTERSBY | | Wed May 24 1995 10:16 | 21 |
| Alphonse, if you could, please see if you can re-direct to that
DECswitch 900EF via a console terminal, and help us fill in
some information which might prove useful in diagnosing your
problem.
- Please determine the hardware rev of the DECswitch.
IE: using menu 3 look at the HW=X/Y rev field and tell us
what you see.
- Please tell us the ASXXXXXXXX serial number and rev shown on
the rear label of the unit.
These two pieces of information will help me understand the vintage
of the DECswitch 900EF.
Come to think of it, the version of HUBwatch you are running may be
the real key though now that you mention it as being 3.0.0.
My recollection tells me that maybe the problem is that HUBwatch 3.0.0
*won't* fully recognize a DECswitch 900EF, but *will* fully recognize
the DECbridge 900EF. It may be by simply upgrading to HUBwatch 3.1.0
you may solve the problem of the port display for the DECswitch 900EF.
Bob
|
| 2305.6 | The problem is HUBwatch V3.0 | SLINK::HOOD | Maine state bird: The black fly | Wed May 24 1995 11:25 | 1 |
| The port counters window was added in V3.1. Upgrade!
|
| 2305.7 | If it ain't there it ain't gonna work! :-) | NETCAD::BATTERSBY | | Wed May 24 1995 11:30 | 3 |
| That's good enough reason to upgrade! :-)
Bob
|
| 2305.8 | Hubwatch version 3.1 works for Ethernet Port Counters on DECswitch 900EF | GIDDAY::STANISLAUS | | Wed May 24 1995 22:28 | 22 |
| Tom,
Thanks. Our VMS system manager would not let me upgrade to Hubwatch ver
3.1 on our Inhouse VMS node, because of the change-control procedures we follow
and strictly obey for our CSC systems.
Anyway, I got a PC, installed Hubwatch ver 3.1 and that worked fine for
getting Ethernet Port Counters. Thanks.
How all this started was a - A customer logged a call saying from his
Hubwatch PC he could not get Ethernet Port countters for his DEcswitch 900EF
units. Immediately I tried it on our VMS node inhouse and I had the same trouble
as the customer. Therefore I put note entry 2305.0.
Anyway to cut a long story short, the customer was running Hubwatch for
Windows ver 3.0 on his PC. I was running Hubwatch for VMS ver 3.0 on our CSC
machine and hence we both had the same problem. Once I installed Hubwatch ver
3.1 on my PC, everything works fine. I have asked the customer to upgrade as
well, to Hubwatch for Windows ver 3.1 on his PC.
Thanks Again,
Alphonse
|