From: mcc@WLV.IIPO.GTEGSC.COM (Merton Campbell Crockett)
Subject: Support for Multiple Frame Types
Keywords: bind, load, frame=
Organization: GTE Government Systems
Date: Wed, 26 Aug 92 13:07:52 GMT

I would like to change the packet frames used on our network from the default
ETHERNET_802.3 to ETHERNET_II (type 8137).  Owing to the number of users on
each of our servers, I would like to have the servers support both frame
types while each of the workstations are upgraded.

Before making any changes to the servers, I used ECONFIG to change IPX on
my system to use frame type 8137.  In my AUTOEXEC.BAT file, QEMM is used
to load both IPX and NET5 in high memory.  I rebooted my system to load the
ECONFIG'ed version of IPX.  When the login sequence in my AUTOEXEC.BAT file
executed, I received an error message complaining that no file server could
be found--the expected result.

I restored my original IPX.COM and used RCONSOLE to access the least heavily
used server and modified its AUTOEXEC.CNF(?) file.  I added a second LOAD
statement for the interface to our Novell LAN in which I used the FRAME=
option to specify ETHERNET_II.  Both LOAD statements were identical save
for the FRAME= option and elimination of the NAME= option on the second state-
ment.  I added a second BIND statement which specified the interface and
second frame type that IPX was to use.

Then I "down"ed the server and brought it back up.  I received a complaint
or warning that I had re-entrantly loaded 3C505.LAN and when the BIND state-
ments were processed received a prompt asking me which binding to use.  I
selected 2 for the ETHERNET_II frame type and requested that I specify a
network.  It complained when I used the default 1.  I then specified 2.

I modified my AUTOEXEC.BAT file to remove all commands after loading NET5
and changed the preferred server to the modified server.  Rebooted my system.
Everything worked fine.  I restored my original AUTOEXEC.BAT which includes
an autologin into my normal server.  I rebooted the system.  Instead of
getting some complaint or being connected to the modified server as expected,
I was connected to my normal server.

With everything appearing to work why am I asking a question?  Its, basically,
that I'm unclear as to what has occurred.  As my initial test indicated that
I could not find any server when IPX was ECONFIG'ed, is the modified server
picking up the connect/attach/whatever request and relaying to my normal
server?  Or, is the modified server notifying the other servers that they
need to support ETHERNET_II?

Other questions:

   1.  Are two LOAD statements for the same interface really required?
   2.  If there is only one LOAD statement will two fully-qualified BIND
       statements accomplish the same purpose of having both packet types
       supported?
   3.  An "fc" of IPX.COM and the ECONFIG'ed version reveals one difference
       around 29C0 displayed as 1110.  This doesn't equal 8137.  Are these
       flags?
   4.  What is the significance of the NET= option?
   5.  Is the modified server really using both packet types?
   6.  If no to the preceding, what mechanism is used to provide the link
       between the workstation and the preferred server?

Thanks for any comments or responses.  As there are some time constraints
involved would you mail them directly to me, if possible, instead of just
posting them to this group.


Merton Campbell Crockett
mcc@wlv.iipo.gtegsc.com