| | Will this configuration work?
| Immediate questions:
| 1. Does the ATMworks 350 interoperate with the Cellplex 7000?
|
We have not formally tested the ATMworks 350 against the Cellplex,
to my knowledge. 3Com did not participate with the 7000 at the
last ATM interop lab.
| 2. Does DECsafe/TruCluster work with ATM transport?
While ATM (both CLIP and LANE) is part of V4.0B, neither has been formally
qualified for use with DECsafe/TrueCluster. As far as I know, official
support for DECsafe and LANE is being qualified as part of a 4.0x release
currently in the works (Eric, correct me if I wrong here).
ATM can be used in so many ways. How would you like to use it in this
particular configuration? Primary network between ASE nodes? As client
access network? Are you planning to use Clip or LANE? According to my
documentation, the Cellplex 7000 is a hybrid unit, allowing both ATM
and Ethernet connections in one box suggestion you could easily glue
things together with LANE.
I am not a DECsafe/cluster expert, so bear with me.
>Per
|
| Per,
Thanks for your replies. Some answers..
1. Cellplex is basically customer requirement (they're a 3Com shop,
using a lot of 3Com equipment.
2. I'm just trying to find out what kind of options I have with ATM for
a DECsafe/TCR solution:
- ATM/LANE for primary network between ASE nodes, and ATM/LANE for
client access also
- Memory channel for primary network, and ATM/LANE for client access
- any others?
Regards,
Wai Sun
|
| Hi Wai Sun --
| 2. I'm just trying to find out what kind of options I have with ATM for
| a DECsafe/TCR solution:
| - ATM/LANE for primary network between ASE nodes, and ATM/LANE for
| client access also
| - Memory channel for primary network, and ATM/LANE for client access
| - any others?
I think the real appeal would be to use it for Client access. A side benefit
may be as primary access between ASE nodes. Do note, ATM *CANNOT* be used in
lieu of MC in TCR. I have no idea what the load would be between ASE Servers,
but, correct me if I am wrong, I'd expect the real volume of traffic to flow
from the ASE Server(s) to the Clients. Maybe, to some extent, the other way
around too. Once again, I am not an expert on ASE.
You could, in theory, create a number of ELANs each representing some sort of
workgroup accessing the ASE environment. Both ASE nodes would be members of
all ELANs, thereby making it possible for clients to fail over from one
server to the other. Some high powered clients may have native ATM interfaces,
instead of Ethernet, transparent to ASE Servers and Ethernet based clients.
Depending on the complexity of your installation and the distance between
clients and servers, you may want to use mutiple switches linked into one
network. Do you have any indication of how big the installation will be?
BTW, what timeframe are we talking about?
>Per
|