| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1747.1 | PROBEwatch is what you need | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Dec 02 1994 11:26 | 9 |
| The DECpacketprobe 90 is monitored via a separate application called PROBEwatch. There
are numerous notes in this conference about it (DIR/TITLE=PROBE should do it).
PROBEwatch is not (yet) launchable from HUBwatch and thus must be invoked separately.
Also, the probe is a 90-style Ethernet-only device and cannot be connected to any of
the DEChub 900 flex channels. There is a token ring probe available (or soon to be
available) called the DECpacketprobe 900RR. Contact the product manager Jack
NAC::FORREST for further details.
...Roger...
|
| 1747.2 | a work around | KAOFS::S_HYNDMAN | Acronym Decoder Ring Architect | Fri Dec 02 1994 12:45 | 17 |
|
There is a way to contect the packet probe from the thinwire to a flex
channel if you have a Repeater 900 or Server 900. Both of these
modules will repeat between two segments if connected. In hubwatch you
will see in the lan interconnect window that the probe is on the
thinwire. The repeater or server has two pull downs. You can connect
one of the repeater/server pull downs to the flex channel you want and
the other to the thinwire. This effectively repeats all the traffic to
the thinwire and the probe for monitoring. Obviously you can use
different repeater to monitor different channels.
Be aware however that any thing on the thin wire will also be
connected so this may not be an option in your case.
Scott
|
| 1747.3 | From the SPD... | SLINK::HOOD | I'd rather be at the Penobscot | Fri Dec 02 1994 13:08 | 12 |
| The SPD for HUBwatch V3.1 says...
The following modules are displayed with a front bezel only. No mod-
ule management is available for these products.
DECwanrouter 90 DECmau 900TL
MUXserver 90 DECrepeater 900TL
DECpacketprobe 90 DECrepeater 900SL
Tom Hood
HUBwatch
|
| 1747.4 | NO.NO.NO. | CONSLT::BUZZELL | | Fri Dec 02 1994 20:11 | 8 |
|
RE: .2 You CANNOT use a DECserver 900TM to repeat between channels.
It has no intercoonect or repeater capability. DO NOT be confused
by the 2 stubs from the icon. No.1 is for connection of the active
users to the ThinWire or an IMB. No.2 is for a maintenance connection
to provide down-line load or up-line dump functions only.
|
| 1747.5 | Better remote management? | ZPOVC::AROBINDUBASU | | Mon Dec 05 1994 01:59 | 14 |
| Agree 100% with .4 .
We are allready using Probe watch software.
Does it mean that every time we want to monitor a separate Lan,
We have to go to remote place to make an external connection
somehow and then monitor?
Will there be any provision for a software selectable flexible
channel , so that remote management become easy ?
Thanks and regards,
Basu
|
| 1747.6 | Don't present them the same | KAOFS::S_HYNDMAN | Acronym Decoder Ring Architect | Mon Dec 05 1994 12:34 | 8 |
|
.4 ok.ok.ok. Thanks for the clarification. I was using the repeater
connection and assumed that the server worked the same way. Perhaps
the interconnect window in Hubwatch should not present the modules the
same way.
Scott
|
| 1747.7 | sorry, small modules cannot hop between LANs | NAC::FORREST | | Tue Dec 06 1994 20:30 | 9 |
| regarding .5
The DECpacketprobe 90, being a small module, cannot connect to the flex
channels on the DEChub 900 backplane, only to the ThinWire channel. We
understand this is a limitation for monitoring in the 900, and are
planning products to address the problem.
In the meantime, the suggestion to repeat one flex channel at a time
onto the ThinWire is the best workaround.
|