HP3000-L Archives

October 1996, Week 3

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:
Tracy Johnson <[log in to unmask]>
Reply To:
Tracy Johnson <[log in to unmask]>
Date:
Fri, 18 Oct 1996 09:45:00 PDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
If you were using host based NMMGR I'd suggest to configure (what used to
be called) a gateway half on the 3000 as Allegro taught me to do.  But I
haven't used Openview in a few years but there must be an equivalent.  I
also think the 9000 must be set up in a similar manner.
 ----------
From:  owner-hp3000-l[SMTP:[log in to unmask]]
Sent:  Friday, October 18, 1996 10:59 AM
To:  HP3000-L
Subject:  HP/Router config problem?

Networking gurus:

We recently went through a "structural change" of the WAN the Navy has
set
up.  In the past the developer's and system support PCs were on the same
LAN as the HP3000 they connect to, and thus, were part of the same
network
(198).  Now they (an the HP9000 that runs HPOPENVIEW) have been moved to
another LAN on another network (164) with routers connecting the LANs.

Prior to the change the developers and system support personnel were able
to could connect (VT) to any of the 50+ HP3000's in the WAN, and
HPOPENVIEW would show all the HP3000s.

Now the developers and system support personnel cannot connect to any of
the HP3000 systems which are more than two routers away, and HPOPENVIEW
can't see any of the HP3000's more than two routers away, but can see
(and ping) the Cisco router's ethernet ports to which the ThinLAN cables
to the HP3000's are connected.

There is a big debate here as to what the problem is, with one group
saying that the problem is that the router local to the developers,
system support personnel, and HPOPENVIEW has been configured to act as a
firewall (which we cannot check as we don't have passwords for that
router), while another group says that the problem is with the
configuration of the HP3000s.  The battle is getting nasty and before any
blood is drawn, I thought I'd ask the real experts -- the members of the
HP3000L.

So!  Any thoughts?

Thanks for your help!

John
 --------------------------------------------------------------
John Korb                            email: [log in to unmask]
Innovative Software Solutions, Inc.

The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.

ATOM RSS1 RSS2