Example 7: An EtherTalk 1.0 and EtherTalk 2.0 Network

This example uses a file server that has an Ethernet and a LocalTalk connection, as shown in Figure 30.

Figure 30
Network with Both EtherTalk 1.0 and EtherTalk 2.0 Clients

For the purposes of this example, assume that some of the Macintosh clients have been upgraded to EtherTalk 2.0, and that other Macintosh clients are running EtherTalk 1.0.

NOTE:  To route both EtherTalk 2.0 and EtherTalk 1.0 packets on the same cable, you must configure the router for both EtherTalk 2.0 and 1.0 on the same LAN driver. The two versions of EtherTalk use different frame types, and as a result, AppleTalk sees EtherTalk 1.0 and EtherTalk 2.0 as two separate networks that happen to be running on the same Ethernet cable. See AppleTalkPacket Frames for more information.


Example 7 Configuration Data

In this example, you will configure the router for EtherTalk 2.0, EtherTalk 1.0 and LocalTalk, using the information in Table 14.


Table 14. Example 7 Configuration

Configurable Component Example Data

 

Internal AppleTalk network

net=50010 zone={"TechOps"}

Use a unique network number. Use a valid zone name.

LocalTalk

net=500 zone={"Sales"}

Use a valid network number. Use a valid zone name.

EtherTalk 2.0

net=1000-1002 zone={"TechOps","Marketing"}

Use a valid network range. Use a list of at least one zone name.

EtherTalk 1.0

net=100 zone={"TechOps"}

Use a valid network number. Use a valid zone name.

NE2000 LAN driver

frame=ETHERNET_SNAP frame=ETHERNET_II

For EtherTalk 2.0 For EtherTalk 1.0

AFP file services

Installed (no options used)

 

ATPS print services

Installed, one print queue for LaserWriter (named "Sales NT") on LocalTalk

 

See AppleTalk Configuration in NetWare for Macintosh for information about the configuration data and syntax.

Figure 31 shows the AppleTalk network configuration when the installation is complete. No clients are shown, to enable you to see the actual networks more clearly.

Figure 31
Configuring Both EtherTalk 1.0 and 2.0 on the Same Ethernet Cable


Example 7 Configuration Procedure

To enter a configuration that will be in effect when you bring up the server, follow the steps in this section.

  1. Load INSTALL, select Product Options in the main INSTALL menu, and then press <Enter> on the line specifying NW-MAC v3.12.

    If you have just finished installing the NetWare for Macintosh software and are running INSTALL, skip this first step.

    When you press <Enter>, the Editable Configuration Files menu opens.


  2. Highlight STARTUP.NCF and press <Enter>.

    Add these to the existing commands in STARTUP.NCF:

    load mac

    set minimum packet receive buffers=100

    See The Macintosh Name Space and AppleTalk Stack/Router Memory Requirements if you would like an explanation of these commands.

    Press <Esc> and then <Enter> to save changes to STARTUP.NCF.

  3. Use the arrow keys to highlight AUTOEXEC.NCF and then press <Enter>.

    Add the NetWare for Macintosh configuration commands to the existing commands in AUTOEXEC.NCF. The commands required for this example configuration appear in bold monospace type in Figure 32.

    Figure 32
    Example 7 AUTOEXEC.NCF

    NOTE:  Before loading the AFP or ATPS modules, you must load the AppleTalk module and bind AppleTalk to one or more LAN drivers, as shown below.

  4. Load the AppleTalk module and configure the internal network:

    load appletlk net=50010 zone={"TechOps"}

    You can use any valid AppleTalk network number, as long as it is unique on the internet. For more information, see Loading the AppleTalk Module.

  5. Load LAN drivers (and AppleTalk frame types, if applicable):

    load ne2000 int=2 port=300 frame=ethernet_ii name=etalk1

    load ne2000 int=2 port=300 frame=ethernet_snap name=etalk2

    load dl2000 int=3 port=320 name=ltalk

    The NAME option is a NetWare driver-naming feature that lets you specify a name for a specific configuration. This option is described in the NetWare v3.12 System Administration manual. For more information about the FRAME option and AppleTalk frame types, see Loading LAN Drivers with AppleTalk Frame Types.

  6. Bind AppleTalk to the LAN drivers and configure AppleTalk networks:

    bind appletlk etalk1 net=100 zone={"TechOps"}

    bind appletlk etalk2 net=1000-1002 zone={"TechOps","Marketing"}

    bind appletlk ltalk net=500 zone={"Sales"}

    The names etalk1, etalk2, and ltalk refer to the driver configuration names assigned in Step 5.

    The NET option configures the AppleTalk networks shown in Table 14. See Binding AppleTalk to a LAN Driver if you need more information about BIND command lines.

  7. Load file and print services:

    load afp

    load atps

    For details on the AFP configuration options you can specify on the LOAD command line, see Setting Up a Specialized Environment.

    Press <Esc> and then <Enter> to save your changes and to return to the "Editable Configuration Files" menu.

  8. If you are ready to enter a print queue configuration, highlight ATPS.CFG in the menu and then press <Enter>; otherwise, go to Step 9.

    Add a queue configuration command line, such as the example queue shown in Figure 33.

    Figure 33
    Print Queue Using the Default Syntax

    This example uses the default "printer-name:zone-name" syntax, where printer-name is the name of the AppleTalk printer, and zone-name is the zone in which the printer resides.

    This syntax creates a NetWare print queue and an AppleTalk print spooler that advertises the queue in the Chooser. The AppleTalk spooler will use the name "NW printer-name" (for example, "NW Sales NT"). The queue name will be derived from the spooler name; in this case, it will be "NW_SALES_NT."

    The AppleTalk spooler will be visible in the zone of the internal network. In this example, it will appear in "TechOps." The printer itself resides in the "Sales" zone.

    See Print Services Configuration for information about your options in configuring and naming queues.

  9. Exit INSTALL, saving your changes.

  10. Down the file server and bring it back up.

    If you don't wish to down the file server at this time, re-enter at the console prompt all configuration commands specified in the STARTUP.NCF and AUTOEXEC.NCF files. This action brings up NetWare for Macintosh for the current server session. The next time you down the server, the specifications in STARTUP.NCF and AUTOEXEC.NCF will apply.

    If you can down the server at this time, follow your usual procedure, for example:

    DOWN <Enter>

    EXIT <Enter>

    SERVER <Enter>

    A series of messages appears, indicating that the system is loading the modules you specified.

  11. Use the MODULES command to verify that the NLMs loaded.

    See Step 2 if you would like an example.

  12. Use ATCON to verify the configuration.

    Now that the router is up and running, you should make sure that it is using the correct AppleTalk configuration. At the file server console, type

    LOAD ATCON <Enter>

    Then, choose View Router Interfaces in the main ATCON menu. A window opens, showing the networks and zones you configured. Please see Checking the Router's Configuration and Function for more information.


Verifying Services from a Macintosh Client

After you have configured NetWare for Macintosh and have installed the required Macintosh client software, you can follow the instructions in the Using the NetWare for Macintosh Client guide to check the configuration from a Macintosh client.

In this example, both the file server and its print queue appear in the TechOps zone (the zone of the internal network).


To see the print queue "NW Sales NT," click the LaserWriter icon and choose the TechOps zone.


In this example, the AppleTalk print spooler appears in the default zone of the internal network, because only one zone was configured on the internal network. See Example 4: EtherTalk 2.0 with Other AppleTalk Routers for an example showing how to configure multiple zones on the internal network.