Title: | Terminal Servers |
Notice: | See Note 2 for Directory of important notes. Please use keywords. |
Moderator: | LAVC::CAHILL ON |
Created: | Tue May 14 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3547 |
Total number of notes: | 12300 |
My customer will upgrade VMS V6.2 with running DECNET/OSI V6.3 ECO5. I would like to ask the following questions for my customer 1) Does TSM V2.1 support VMS V6.2 with DECNET/OSI V6.1 ? 2) If TSM V6.2 is not supported. What software can replace TSM ? Can advice should be appreciated.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3502.1 | TSM works fine! | CSC32::D_SHAVEY | Thu Apr 24 1997 12:17 | 6 | |
TSM works fine on all versions of VMS and DECnet/OSI /plus. Your customer should have no problem. Darrell Shavey DTN 592-4712 | |||||
3502.2 | A problem you will often encounter... | TWICK::PETTENGILL | mulp | Tue Apr 29 1997 23:49 | 9 |
DECnet Classic uses names like BNA-1 to identify the circuit, ie., interface, to use for MOP while DECnet Plus will default to a name like CSMACD-1. If you convert the existing DECnet databases when installing DECnet Plus, the I believe the Classic name will be preserved, but if you perform a complete reconfiguration, or a completely new install, then the names will "change". If the symptom is "TSM under DECnet Plus returns an error for all TSM commands such as SHOW SERVER ALL", then check to make sure that the TSM circuit for each server matches the MOP circuit name. |