| Can the Repeater90FS be configured :
1 with both ports as NON-Responder ports ie like two 90FA modules
>> Yes.
2 with both ports as Responder ports, in order to connect two of
these modules to two other -90FS modules configured as
master port pairs
>> Yes.
3 one as NON-responder and the other as responder
>> Yes.
>> The ports can also be configured as a redundant master pair.
When it is plugged into a 90/900 what is the default configuration ?
>> The default configuration whether plugged into a hub or stand-alone is no
>> redundancy configured on either port (i.e. neither port is configured as a
>> redundant responder or master). Of course, once a port has been configured
>> for redundancy, that setting is non-volatile.
Does the 900FM operate the same way and what is it's default config ?
>> The DECrepeater 900FP (or DEFMM) behaves the same way, in terms of
>> redundancy, as the DECrepeater 90FS (including its default configuration).
What version of HUBwatch (VMS or Windows) manages / will manage these
modules ?
>> HUBwatch version 3.0 or greater manage these modules. Currently
>> HUBwatch 3.0 is only available on OpenVms but will be available in the near
>> future on Windows.
Re 2 above :
All All
responder ports prim/sec link ports
1 --------------------------------- 1
+-- 90 FS 90FS master port pair
| 2 ---------+ +----------------- 2 SITE B
LOGICAL| | |
CONNECT| SITE A +---- | ----+
eg UTP | 1 ---+ +----------------------- 1
+-- 90 FS 90FS master port pair
2 --------------------------------- 2 SITE C
Will this config give full redundant links to both sites B and C.
Any limitations to this config ?
>> This configuration provides full fault-detection/redundancy against cable
>> plant failures as well as failures of the responder modules/hubs.
>> Obviously if a module/hub containing a master port pair on a given site
>> fails, that site will be isolated from the network.
Regards,
Rich
|