HP3000-L Archives

May 1998, 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:
"Stigers, Greg ~ AND" <[log in to unmask]>
Reply To:
Stigers, Greg ~ AND
Date:
Fri, 22 May 1998 17:44:23 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (42 lines)
As we are testing Ethernet vs. Token Ring on our 3K, I need to answer a
question correctly, which I hope I can describe adequately. Our goal is
to allow our customer to test coming in on Ethernet instead Token Ring
as they are now, starting with a test lab and a small number of users,
and deciding on further testing as we go. We want everyone else to
continue to come in on Token Ring for multiple applications. The
customer has a dedicated router on the Token Ring, and so they had their
own Configured Gateway for their class B range of IP addresses. I think
that the Ethernet users come in on one link, and go back out on that
link's Configured Gateway.

In NMMGR, under NETXPORT.NI, we have two Configured Network Interfaces,
which I'll call CNI1 and CNI2 (names and addresses changed to keep me
out of trouble). CNI1 is Type LAN, and CNI2 is Type TOKEN.

For CNI1, under NETXPORT.NI.CNI1.INTERNET, we have a Configured Gateway
named DEFAULT;
under NETXPORT.NI.CNI1.INTERNET.DEFAULT we have an IP Network Address of
@, and a Neighbor Gateway IP Internet Address of B 111.222 111.222.

For CNI2, under NETXPORT.NI.CNI2.INTERNET, we have two Configured
Gateways, named COMPANY and CUSTOMER.
Under NETXPORT.NI.CNI2.INTERNET.COMPANY, we have an IP Network Address
of @, and a Neighbor Gateway IP Internet Address of B 111.222 123.111.
Under NETXPORT.NI.CNI2.INTERNET.CLIENT, we have an IP Network Address of
111.222 000.000, an IP Mask of 255.255.000.000, and a Neighbor Gateway
IP Internet Address of B 111.222 123.112.

Now, a network engineer for the client writes: "If the HP works like
every other IP device I've worked with, it has no awareness of which
interface a packet came in over. It only knows the source IP address on
the packet. To reply to a packet, it puts the source into the
destination field and consults a routing table to figure out where the
packet should be forwarded. Unless you have made some configuration
changes on the HP, it has no idea that it can get to 111.222 through its
ethernet interface."

Well, I know how to spell "IP", so I can't be sure about this, except to
say that the HP seems to know where something came from and where we
want it to go, and we have "made some configuration changes on the HP",
so... Are we OK, or is there more to this than I know?

ATOM RSS1 RSS2