| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 332.1 | Please use latest versions of firmware | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Aug 10 1993 14:07 | 21 |
| >> HUBwatch V1.1.0 VMS and ULTRIX
>> DECAgent SW X1.76
>> DECBridge HW V1.0
>> ROM V1.0
>> SW V3.0
You should be running DECagent SW V1.1 and DECbridge SW V3.1
>> Problem 1.
>>
>> I can no longer de-active or active thinwire ports on the DECrepeater90C'c
This seems to imply that you could do this before but cannot now. What did you
upgrade? HUBwatch? See above for the latest firmware that should be running in
your devices.
>> Problem 2.
Sorry, I can't help you here.
...Roger...
|
| 332.2 | and still more! | SLINK::HOOD | I'd rather be surfing | Tue Aug 10 1993 14:53 | 29 |
|
>> Problem 1.
>>
>> I can no longer de-active or active thinwire ports on the DECrepeater90C'c
Can so!
Method 1:
From physical front-panel, double-click on coax connector icon.
From logical front panel, click on port number.
Repeater Port Summary screen appears. Press "Disable" button to
disable, or press "Enable" button to enable.
Method 2:
From front panel, double-click on 90C module.
Repeater Summary screen appears. Press on the green closed-switch
icon to disable, or press the red open-switch icon to enable. Then
press Apply or OK.
In HUBwatch 1.1 (and 2.0 and ...) the only thing you can't do is click on a
front panel led to enable or disable the port, as you could in 1.0
>> Problem 2.
>>
>> In the lower right hand coner of the hub backplan is a button that use to
>> bring up the hub enviroment. That no longer works.
In HUBwatch V1.1, that button is just a cheery little decoration.
It doesn't do anything. I don't know why we never removed it.
To get agent info in V1.1, double click on the Agent module from the
front-panel view, or use the Community->Manage Current menu item.
|
| 332.3 | Could it be the repeaters??? | AKOCOA::NCOLLINS | | Mon Aug 23 1993 09:19 | 17 |
| Ok, I'm still running HUBwatch V1.1. The bridges have been upgraded to V3.1. The
DECagents are now running V1.1 of the agent software, and still I can't disable
DECrepeater90C ports. I have tried the methods suggested and it still is not
working. Could it be the rev level of the repeaters that I am using? Looking
on the back of one, here is the information:
PN DECMR-M
REV H02
FTZ C-208/90
I also have another problem. I'm also using DECserver90TL's. I wanted to upgrade
the load image, but come to find out that I have to go from 1MG of memory to 4!
How is this done? Do I have to go into each server and replace something? I have
over 200 servers. Not to mention the replacement units.
Norm
|
| 332.4 | Bridge filtering? | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Aug 23 1993 13:18 | 9 |
| I doubt the repeaters are at fault.
Do you have any protocol filters set in the bridge? If you are filtering RBMS
traffic (08-38), some things won't work.
Also, could you be more specific about your setup (hub type, which modules are
in which slots)?
...Roger...
|
| 332.5 | Upgrading 90TL's | SLINK::HOOD | I'd rather be surfing | Mon Aug 23 1993 13:48 | 6 |
| I can't speak for either the terminal server people or for field service,
but I have upgraded our DECserver90TL's here in HUBwatchland from 1meg to
4meg. The memory in those devices is a SIP, part number MS40-WB.
Replacement time is about 3 minutes per 90TL.
Tom
|
| 332.6 | Bridge filtering | AKOCOA::NCOLLINS | | Tue Aug 24 1993 10:15 | 10 |
| All the bridges(DECbridged90) are as they come out of the box. I have not
changed them at all.
As for the configuration, in most setups, I have 4 - 16 slot hubs per SER.
2 are all repeaters, 2 are all servers. I have the bridge in slot 8.
All the hubs are connected to a DEMPR via the thinwire connection on the front
of the bridge. The agents are connected to the same DEMPR as the HUBs.
Norm
|
| 332.7 | Are we talking to the bridge? | ROGER::GAUDET | Because the Earth is 2/3 water | Tue Aug 24 1993 12:55 | 10 |
| OK, no bridge filters. Good. Do you have access to the agent's console? If
so, I'd like to know if the agent is communicating with the bridge. You can
tell this by looking at the Show Community screen for slots 1-8 of each
community and checking that the bridge is not highlighted or flashing. Are the
repeaters getting auto-discovered? This is another way to verify that the agent
is talking to the bridge. If all of the above checks out, then I'm at a loss to
understand why you cannot disable the repeater ports. Perhaps we need to talk
offline. DTN: 226-6792.
...Roger...
|
| 332.8 | Still broken? | ROGER::GAUDET | Because the Earth is 2/3 water | Wed Sep 22 1993 09:54 | 3 |
| Norm...did you get this resolved?
...Roger...
|
| 332.9 | controlling DECrepeater ports...problem not resolved | AKOCOA::NCOLLINS | | Wed Oct 06 1993 14:39 | 21 |
| I have tried everything that everyone has told me to do, in order to disable or
enable DECrepeater90C ports. None of which has worked.
So maybe it is my configuration. Here it is:
16 slot DEChub w/ DECbridge90 in slot 8. A DEMPR is used to connect the hub to
the network via the thinwire port on the DECbridge.
The DECagent90 is connected to the network via the same DEMPR as the HUB.
HUBwatch is running on the ULTRIX v1.1 platform.
I have the latest version of the bridge and agent firmware installed.
Can anyone see a problem in this configuration?
Norm
|
| 332.10 | Problem resolved | SLINK::HOOD | I'd rather be surfing | Thu Oct 07 1993 13:07 | 7 |
| re: seeing but not being able to disable/enable repeater ports...
It turns out there was a password set on the bridge and it wasn't entered
when the bridge was added to the hub thru HUBwatch. This makes things
read-only.
Tom Hood
|