This example shows how to configure NetWare for Macintosh for TokenTalk, EtherTalk 1.0, and LocalTalk in a file server with Micro-Channel architecture, running NetWare v3.12. The basic network is shown in Figure 34.
Figure 34
AppleTalk Networks Using Micro-Channel Adapters
When Macintosh clients are connected to Token Ring, you must load the ATTOKLLC NLM as described in this example configuration. If you have not already manually copied the NLM to the server's SYS:SYSTEM directory, see If the Server Has Macintosh Clients on Token Ring. In this example, the router uses the information in Table 15.
Using Token Ring with Macintosh Clients
Example 8 Configuration Data
Table 15. Example 8 Configuration
| Configurable Component | Example Data |
|
|---|---|---|
Internal AppleTalk network |
net=50001 zone={"Engineering"} |
Use a unique network number. Use a valid zone name. |
EtherTalk 1.0 |
net=10 zone={"North"} |
Use a valid network number. Use a valid zone name. |
LocalTalk |
net=11 zone={"South"} |
Use a valid network number. Use a valid zone name. |
TokenTalk |
net=20-25 zone={"North","South"} |
Use a valid network range. Use a list of at least one zone name. |
3c523 LAN driver |
frame=ETHERNET_II |
|
DL/2 LAN driver |
No frame required |
|
Token Ring LAN driver |
frame=TOKEN-RING_SNAP |
|
AFP file services |
Installed (no options used) |
|
ATPS print services |
Installed, two print queues for ImageWriter (named "Reports IW") on LocalTalk |
|
See AppleTalk Configuration in NetWare for Macintosh for information about the configuration data and syntax.
Figure 35 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 35
EtherTalk 1.0, LocalTalk, and TokenTalk Configurations
To enter a configuration that will be in effect when you bring up the server, follow the steps in this section. 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.
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. 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 36. Figure 36
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.
Load the AppleTalk module and configure the internal network: load appletlk net=50001 zone={"Engineering"}
If you would like more information about this command line, see Loading the AppleTalk Module. Load the LAN drivers and AppleTalk frame types: load 3c523 slot=6 frame=ethernet_ii name=etalk1 load dl2 slot=4 name=ltalk load token int=2 saps=4 ls=32 frame=token-ring_snap name=ttalk
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, see Loading LAN Drivers with AppleTalk Frame Types. Bind AppleTalk to the LAN drivers and configure the AppleTalk networks: bind appletlk etalk1 net=10 zone={"North"} bind appletlk ltalk net=11 zone={"South"} bind appletlk ttalk net=20-25 zone={"North","South"}
The names etalk1, ltalk, and ttalk each refer to the driver names assigned in Step 5. Please see Binding AppleTalk to a LAN Driver if you need more information about BIND command lines. NOTE: Because this example has already configured IPX and APPLETLK on the same Token-Ring LAN driver, you do not need to load the frame type TOKEN-RING for the Token-Ring LAN driver being used for AppleTalk. In this example, the TOKEN-RING frame type is already loaded. It is the default frame used by IPX on Token Ring boards.
Load the Token-Ring Source Routing NLM (ROUTE.NLM) for the Token-Ring board with the TOKEN-RING frame type: load route board=1 load route board=2
Load ATTOKLLC.NLM: load attokllc
There are no options for this NLM. (Remember that you manually copy this NLM from the NW-MAC diskette to the server's SYS:SYSTEM.) Bind ATTOKLLC to the Token-Ring board handling TOKEN-RING frames: bind attokllc to tring-ipx
Note that this is not the same logical board to which APPLETLK is bound. Load the file and print service modules: 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. 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 37. Figure 37
The--o option is used to create a name for the AppleTalk print spooler that advertises the print queue in the Chooser. In Figure 37, two AppleTalk print spoolers are created; one is named "IW_queue" and the other is named "Color_queue." See Assigning a Descriptive Name: -o for details. The -t option enables you to specify a printer type. In Figure 37, "IW_queue" will send print jobs to an ImageWriter named "Reports IW." "Color_queue" will send print jobs to the same ImageWriter with a color ribbon loaded. This allows users with color Macintosh applications to generate the proper codes for an ImageWriter with a color ribbon. See Specifying a Color ImageWriter: -t and -c. See Print Services Configuration for a complete discussion of your options in configuring queues. Exit INSTALL, saving your changes. 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. Verify that the modules have loaded. When you see the console colon (:) prompt, type MODULES <Enter>
A list of loaded NLMs appears on the screen. 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. 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, the file server appears in the Engineering zone, because this is the zone of the internal network.Example 8 Configuration Procedure

Example 8 AUTOEXEC.NCF (Micro Channel)
ImageWriter and Color ImageWriter Print Queues
Verifying Services from a Macintosh Client
