| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5874.1 | DECnet Routing; "Prior Version" Support | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Thu Mar 06 1997 16:56 | 20 |
|
DECnet phase IV end-nodes do not automatically fail-over among the
available working circuits, and require some explicit user-supplied
NCP commands to engender fail-over.
DECnet phase IV routers and DECnet-Plus end-nodes do automatically
fail-over among available (working) circuits, and the fail-over
process requires no manual intervention.
DECnet-Plus also transparently supports multiple Ethernet rails, and
multiple Ethernet controllers connected to the same Ethernet rail.
OpenVMS V6.1 and OpenVMS V6.2, and the associated DECnet releases, are
now only presently supported with a "prior version support" contract.
DECnet Phase IV presently requires a specific support contract -- the
"default" DECnet for OpenVMS V7.1 is DECnet-Plus. I know of no explicit
announced end-of-prior-version-support dates for the V6.x-vintage OpenVMS
releases, nor for DECnet Phase IV.
|
| 5874.2 | please clarify | KYOSS1::SLAGLE | | Fri Mar 07 1997 08:51 | 7 |
| Please pardon my ignorance, but what is a "prior version support"
contract? What does that mean?
Would it be better to recommend the upgrade to DECnet/OSI and not worry
about all of that?
Thanks
|
| 5874.3 | "Prior version support" | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Mar 07 1997 13:32 | 22 |
| : Please pardon my ignorance, but what is a "prior version support"
: contract? What does that mean?
"Prior version support" (PVS) is a set of extra-cost software support
contracts for specific products or older releases available from MCS.
PVS has two levels: "Sustaining Engineering", and "Best Endevour"
contracts.
The standard software support contracts cover the most recent releases
of OpenVMS -- currently V6.2-1Hx (*not* V6.2!), V7.0 and V7.1, and recent
versions of DECnet. Support for specific earlier versions of specific
products is available via PVS, at an extra cost.
(This info should be available via http://webir.das.dec.com/ or VTX IR.)
: Would it be better to recommend the upgrade to DECnet/OSI and not worry
: about all of that?
I'd recommend staying current, but this is up to the customer, as the
customer may have specific local requirements.
|
| 5874.4 | DECnet-Plus on TCP/IP (Dual Rails) | TKOV60::MORIG | | Sat May 17 1997 02:13 | 33 |
| > <<< XDELTA::HOFFMAN "Steve, OpenVMS Engineering" �ˤ��Ρ��� 5874.1 >>>
> -< DECnet Routing; "Prior Version" Support >-
>
>
> DECnet phase IV routers and DECnet-Plus end-nodes do automatically
> fail-over among available (working) circuits, and the fail-over
> process requires no manual intervention.
>
> DECnet-Plus also transparently supports multiple Ethernet rails, and
> multiple Ethernet controllers connected to the same Ethernet rail.
>
We are trying to resolve our customer requirement.
They are using dual rail ethernet with FDDI on OpenVMS v6.2 and DECnet/OSI
v6.3.
They are trying to change the protocol from DECnet to TCP/IP.
They understand that UCX can't handle dual homing IP nor Path Splitting on
the dual rail.
I heard DECnet-plus works on UCX for TCP/IP stack.
Do you mean they can use TCP/IP with dual rail and automatic fail over?
If possible, we want to use DECmessageQ on TCPIP with DECnet-Plus.
I asked about the dual homing IP support at DMQ note conference, but DMQ
didn't support it.......
Please let me know.
Best regards,
Yukio Moriguchi
|
| 5874.5 | Asking Wrong Audience... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon May 19 1997 17:36 | 38 |
| :We are trying to resolve our customer requirement.
:They are using dual rail ethernet with FDDI on OpenVMS v6.2 and DECnet/OSI
:v6.3.
I assume this configuration works fine.
:They are trying to change the protocol from DECnet to TCP/IP.
Why? (I've seen folks try switching protocol stacks for good
reasons, and I've seen folks trash good and working network
configurations solely because the network protocols in use
were "out of fashion".)
:They understand that UCX can't handle dual homing IP nor Path Splitting on
:the dual rail.
Donno. Ask over in LASSIE::UCX.
:I heard DECnet-plus works on UCX for TCP/IP stack.
DECnet-PLUS operates over a variety of protocol stacks, including
IP. (And DECnet-Plus operates with several different IP stack
vendors, including UCX.)
:Do you mean they can use TCP/IP with dual rail and automatic fail over?
Donno. Ask over in LASSIE::UCX, or HELP::DECNET-OSI_FOR_VMS.
:If possible, we want to use DECmessageQ on TCPIP with DECnet-Plus.
:I asked about the dual homing IP support at DMQ note conference, but DMQ
:didn't support it.......
None of this list of products is covered by this conference -- if
the DECmessageQ folks (at PAMSRC::DECMESSAGEQ) told you they don't
support this configuration, then they likely don't support it...
The DECnet-Plus notes conference is at HELP::DECNET-OSI_FOR_VMS.
|