| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 603.1 | | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Wed Jan 09 1991 19:37 | 7 |
| For Vitalink bridge information contact:
Dave Terzian (DELNI::TERZIAN) marketing contact
Doug McPherson (TOOK::MCPHERSON) engineering contact
Jon Goodridge (TOOK::JSG) 3rd party engineering mgr
JCE
|
| 603.2 | Thanks John | RTPSWS::BRILEY | Are you a rock or leaf in the wind | Thu Jan 10 1991 11:54 | 1 |
|
|
| 603.3 | Who out there is managing Vitalink Translans and How ? | TOOK::MCPHERSON | i'm only 5 foot one... | Tue Feb 12 1991 09:50 | 27 |
|
Hi.
I would like to get a better fix on those people within DEC that are
currently managing Vitalink Translans (NOT TransPATHs) on the Easynet:
1) How many Translans are you managing?
2) What kinds of Translans are you managing ? (e.g. TL350, 320, 335,
III etc)
3) What rev software are you currently running on the Translans?
4) How are you *currently* managing them (e.g. WANmanager, a bunch of
terminals, DECmcc? ,VCS?, not at all)
5) How much do you use the "Protocol Type Filtering" on the Translans?
6) Do you use the pattern match filters options ?
7) Would you be willing to fieldtest baselevels of the Translan AM on
DECmcc when they become available?
It's probably best to respond via mail to TOOK::MCPHERSON.
Thanks.
/doug
|
| 603.4 | Minimum Software requirements for Translan AM | TOOK::MCPHERSON | i'm only 5 foot one... | Wed Feb 13 1991 16:59 | 35 |
|
If you are planning on using the Vitalink Translan AM to manage
Translan Bridges in DEC, here are a few pieces of information that you
should know:
First: The AM (because of management protocol changes) presupposes a
certain minimum version of VMS (Vitalink Management Software) on the
Translans. Because of the way in which Vitalink numbers their
software, this can get a little confusing.
That list of Translan models and their corresponding minimum required
version of VMS (that I know about) are as follows:
Translan III: V6.10
Translan 320: V20.2
Translan 335: V10.4
Translan 350: V10.4
So for example: If you're managing a network of TLIIIs at V6.9 and you
want to be able to manage them using the Translan AM, then upgrade to
6.10 *soon*.
Secondly, the Translan management protocol (RBMS) has *no* provisions
for remote management of a couple of Translan management functions such
as setting up pattern matching filters and changing the bridge name.
These specific management duties will _still_ require that the user
execute these commands from the REC menu at an attached console,
either wired up or via a virtual remote management console from another
Translan; The AM simply cannot affect those attributes.
It is not yet decided how this "ancilliary" management will be provided
in conjunction with the AM in its final release. For the purposes of
fieldtesting the Vitalink AM within DEC, this remote console facility
will not be provided, unless something changes very soon,
|