| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2330.1 | | SLINK::HOOD | Maine state bird: The black fly | Wed May 31 1995 15:18 | 7 |
| Is not a mistake. Is intentional.
The LAN interconnect stuff is MAM (hub) stuff, so you can only get to it
through the hub.
The docking stations are supported by HUBwatch V4.0.
|
| 2330.2 | OUI Mais.... | PADNOM::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Thu Jun 01 1995 04:22 | 6 |
|
Ok Tom,
agree for LAN interconnect but for the port switching (Front/back) ?
jean-yves
|
| 2330.3 | only get ligo choices if in hub900 or in dock sta | NETCAD::MOWER | | Thu Jun 01 1995 12:01 | 28 |
|
Front/back choices ("ligo choices") for a module in a hub900 are saved
in the hub900, (specifically, in the "MAM").
When you invoke HUBwatch against a module that resides in a hub900,
using a module's own IP address, there is no MAM in the picture - just
HUBwatch talking to a module, (that happens to be in a hub900).
In such a situation, you are not offered any ligo choices, since there
is no MAM available to store the choices you would make.
If you invoke HUBwatch against a module that resides in a docking
station, (either DEChub ONE "low-end docking station", or DEChub ONE/MX
"high-end docking station"), you are offered ligo choices. These
choices are stored in the module, and are erased if the module detects
that it has been moved between any of the following three "environments":
- a hub900
- a low-end docking station
- a high-end docking station
For example, if you make ligo choices for a module currently in a
high-end docking station, and then move that module to another high-end
docking station, your choices will persist. If you move that module to
a low-end docking station or to a hub900, your choices will be erased.
Carl Mower.
|
| 2330.4 | en cas de malheur... | CLPR01::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Fri Jun 02 1995 05:25 | 7 |
|
it will be the best to see if/where your Switch900 is connected
under this windows ,in case of MAM/IP server problem
isnt it ?
jean-yves
|
| 2330.5 | ligos for connecting on backplane are saved in MAM | NETCAD::MOWER | | Tue Jun 06 1995 12:04 | 19 |
|
When using HUBwatch to manage a hub900, using the MAM's IP services
address, I agree that it would be helpful if in HUBwatch's LAN
interconnect view the currently set ligo for each slot/module were
indicated. (There is no plan at this time to do this).
As to the second part of -.1, that it would be helpful to be able to
see the currently set ligo when communicating directly to a module,
(using the module's IP address), that would not be possible, since the
current ligo selection is stored in the MAM, and under your example the
MAM is not reachable due to a MAM/IP server problem.
Keep in mind that ligo selections used to connect modules across the
hub900 backplane are stored in the MAM, not in the modules, so when
HUBwatch is talking directly to a module, (using the module's own IP
address), that information is not available.
Carl.
|
| 2330.6 | Merci Carl | CLPR01::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Tue Jun 06 1995 15:13 | 3 |
| thanks Carl
JYP
|