OK, Tom raised a few highly interesting questions. We'll go into some
specifics.
> We are considering opening up a remote call center to support operations
closer to the West Coast. We currently operate five remote call centers;
however, they are located within 60 miles of our headquarters in Media, PA.
The new center may be located 2000 to 2500 miles away from here.
Presently, we connect our call centers via DTC72s connected to HP Bridges
over leased lines.
>
> 1. Can we connect one or more DTC72s directly to the Internet (via a HP
Bridge and an ISP) without having to pay the $$$ for a nailed-up line for
2500 miles? If so, do DTCs experience more problems over a 'Net connection
than they do over leased lines?
My recommendation fits in three words : forget about it !
The reason is that DTCs are not native TCP/IP equipments. They use an HP
proprietary protocol, AFCP, which is not routable by default. AFCP can be
routed (i.e. AFCP frames encapsulated into TCP/IP frames), but that
requires PC-based management, an Openview station at the remote site, and a
"mirror" (well, not exactly mirror, but you've sort of got the idea) DTC on
the local (i.e. system) side, to depack the TCP/IP frames and send them to
the system in their original AFCP form.
Another possibility would be to get rid of the DTC by replacing passive
terminals by PCs, turning serial printers into network printers and adding
a few hubs to connect all these network-enabled stations together. What's
more, this could require a complete recabling of your premises, depending
on what kind of cabling is currently in place.
And do not forget that Internet connections can be somewhat hogged at peak
hours (more or less all day long in the USA, a bit less in Europe). And
great care should be taken in choosing the right ISP and the right type of
site-to-ISP link. Ans I also would voice aa serious concern about security,
which is far from granted over the 'net.
> 2. If we decide to install another 3000 at the remote site, is there any
software available (HP or 3rd party) that would allow us to share files at
the remote site as if they were directly connected to our 3000 here (i.e.
we would view the files at the remote site as if they were disks connected
to our present 3000)? We'd also be interested in backing up the files at
the remote site here.
There are at least two ways to do it :
a) Duplicate the files from the remote site to the local site with
Shareplex. Shareplex/iX only needs a TCP/IP link, so it could theoretically
work pretty well over the 'net, providing you have the right kind of
permanent (otherwise your TCP/IP link will time out) access, with the
appropriate thruput. Backup only required on local system in that case,
providing you really duplicate all but everything.
b) Share the files with NFS/iX, which would allow your local system to see
the NFS-mounted "file systems" on your remote site as if they were local,
thus ensuring only one backup procedure.
But, once again, take great care about thruput and security.
Another alternative would be to consider frame relay. I do not know the US
situation re: frame relay, but it's really getting quite widespread in
Europe.
> I realize that I've tossed out a couple of tough ones!! I'm also sure
that somebody (or two!) has already swam through these shark-infested
waters once or twice.
Yep. Been there, done that. You bet !
> Thanks in advance for your help!!!
You're welcome.
And, oh, just a little plug before I sneak away for the weekend :
<plug>
I work for an HPSystems Integator. If you are interested in further contact
with my organization, please reply me privately. We are always willing to
help. We can provide engineering and consultancy services worldwide.
</plug>
Christian Lheureux
Head of Systems and Networks Department
APPIC R.H.
An HPConnect Systems Integrator
An HP3000 Expert
|
