HP3000-L Archives

July 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Phil Culver <[log in to unmask]>
Reply To:
Phil Culver <[log in to unmask]>
Date:
Mon, 24 Jul 1995 16:46:32 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
   We recently opened up a disaster recovery/remote development site
on the SGI campus in Mtn View. When designing the network, I was assured
that we could "bridge" one data center to the other. It turns out that
in the interim, 'bridging" became illegal here at dear old SillyCone
Graphics.
 
   So now I have been charged with implementing Routable Avesta Flow
Control Protocol, so that the remote data center's console and DTC72MX
can be monitored from the main data center. This has entailed a whole
slew of kludges...two separate PC's (a story in itself) running OV DTC
Manager, FTP, Reflection, and OV Windows. To make things even more
interesting, the remote site is MPE/iX 5.0 and the central site is MPE/iX
4.0.
 
   Has anyone out there in radioland done this successfully yet? We
have made changes to our DNS server to include WKS and TXT entries (
something nothing else in our DNS data base has). Autodiscovery seems
to die at the first router it finds, and there are about 5 other routers
that it SHOULD be able to find.
 
   The experience/advice of anyone who has done this (remember we are a
mixed MPE/iX version shop) would be GRATEFULLY appreciated.
 
As they say is Bosnia,
 
Tanks in Advance...
 
Phil

ATOM RSS1 RSS2