T.R | Title | User | Personal Name | Date | Lines |
---|
3331.2 | It's happening | IOSG::ECHRISTIE | Eileen Christie | Tue Sep 28 1993 09:30 | 3 |
| Dave,
I'd be happy to give you lots more information, either via A1INFO or if
you mail me. We are very committed to Alpha AXP.
|
3331.3 | Says who? | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue Oct 05 1993 14:08 | 9 |
| I know of *ABSOLUTELY NO REASON* (yes, I am shouting :-) ) why a mixed
architecture cluster shouldn't support any version of ALL-IN-1 running
on the VAX nodes only.
If anyone knows differently, please tell me *NOW*!!
Graham Pye (ALL-IN-1 Engineering, Installation Supervisor)
PS Shortly it'll run on the AXP nodes too!
|
3331.4 | ALL-IN-1 works fine... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Nov 01 1993 11:19 | 4 |
| We've now discovered this is a Message Router, not ALL-IN-1
restriction. We're looking into the full story.
Graham
|
3331.5 | Apologies to Message Router! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Wed Nov 03 1993 08:47 | 8 |
| I'm told by several Message Router Experts that they can't see *ANY
REASON* (I'm shouting on their advice!) why Message Router shouldn't
work either.
We're now going to ask the original reporter of this problem for more
details.
Graham
|
3331.6 | Fixed in MR 3.3? | FORTY2::ASH | Mail Interchange Group, Reading | Thu Nov 04 1993 09:43 | 10 |
| In lieu of a statement from 'those who know', I'll add my 2p to this debate -
my understanding is that there is a problem with running MR on mixed clusters,
specifically with DDS, which uses the cluster alias and assumes it can use all
nodes in the cluster.
However, this assumption/restriction is likely to be removed with MR V3.3, and
at that time it will be perfectly possible to run the MR processes on the
VAXes only of a mixed cluster.
grahame
|
3331.7 | Listen to Graham! | FORTY2::ASH | Mail Interchange Group, Reading | Thu Nov 04 1993 16:56 | 5 |
| oops. Please ignore the previous reply.
.5 has the definitive statement.
grahame
|
3331.8 | Don't allow the alias to connect to Alpha | IOSG::TALLETT | Gimmee an Alpha colour notebook... | Tue Nov 09 1993 20:05 | 6 |
|
Presumably you could set up the Alpha's so that they don't field
cluster alias requests? Or wouldn't that help?
Regards,
Paul
|
3331.9 | | CSOA1::LENNIG | Dave (N8JCX), MIG, @CYO | Wed Nov 10 1993 12:57 | 20 |
| Exactimundo! There is nothing IOS/MR unique in this situation.
If you had a VAX-only cluster (Phase IV DECnet) with an alias where
some services were not available on a particular VAX, this is your
only recourse (exec alias inc dis). The same applies to AXP nodes.
(Note that if you don't do this, it isn't the end of the world wrt
MR - both TS and DDS will simply retry, and eventually the PhIV alias
link dispatch mechanism will select a 'valid' MR cluster node.)
Note that if the cluster is using Phase V DECnet, the alias link
dispatch mechanism has gotten smarter, and will only direct links
to nodes that support the target/requested 'object'. Hence you can
allow all nodes full use of the alias with no ill effects.
Dave
PS - MR V3.3, MRG V3.3, and MRX V3.3 all support DECnet/OSI (subject to
availability of node synonyms) and have been submitted to SSB. You'll
have to talk to ALL-IN-1 product mgmt about IOS support on DECnet/OSI.
|