Northern Credit Bureaus Inc wrote:

> Hi Jeff, it is for load sharing, i.e. one ethernet card for user access with
> the lan connection to say 192.168.1.1 to 192.168.1.255 and the other
> ethernet card to ftp between 2 hp3000 which would not hinder the traffic.  I
> understand that 10baseT has more limitations than 100baseT (RJ-45
> connections) in that the address cannot be in the range 192.168.1.1 to
> 192.168.1.255, but must differ as you suggested from 192.168.2.1 say to
> 192.168.2.255.  What I don't understand is why I would need a gateway if it
> is an internal ftp process between 2 hp3000 without going to the outside
> world.   I have labelled host 1 to be 192.168.2.2 and host 2 to be
> 192.168.2.7.  So far no luck, should I add the gateway 192.168.2.1 to both
> systems?

So, let's assume you are currently on 192.168.1.2 which has access to
your local lan of 192.168.1.1-192.168.1.255.  And you want the second
LANIC sort of "dedicated" to another 3000.  In this case...

Your "other" 3000 cannot be on 192.168.1.x, it would have to be on
192.168.2.x (or any other 192.168.whatever.x).  If the "other" 3000 is
also on 192.168.1.x and has no other NIC, you can't load share.  The
NICs must be on separate subnets, and each 3000 would require two NICs.
That way, 192.168.1.x would handle your internal traffic, while some
other subnet such as 192.168.2.x would handle your 3000-to-3000 traffic.

10BaseT and 100BaseT can occupy the same media (kind of, sort of) but
they can't talk to each other (obviously).  Much the same way as you can
have IP, IPX, Appletalk, etc coexist on the same segment.  What usually
happens in the PA-RISC 3000s (other than the A and N class) is that you
get a 10BaseT NIC in the MFIO card, but you might add on a 100BaseT
card.  In this case, you can use the 100BaseT for anything host-based
except for DTC traffic, which can go on the 10BaseT NIC and doesn't even
need an IP.

If you never go to the outside world, and the outside world doesn't need
to talk to the "other" 3000, then yes, you would setup the NICs between
the 3000s as 192.168.2.x and the original dual-NIC system would have the
other interface on 192.168.1.x.  You don't need a gateway unless you
want someone on 192.168.1.x to talk to the *other* 3000 on 192.168.2.x.
Then you need a router, or configure store-and-forward, etc.

I would not recommend using the 3000 as a router.  It barely functions
as a host, let alone a gateway or especially a router :-)

But otherwise you can go "point-to-point" with your other 3000 as long
as it is on a unique subnet.

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *