|
|
This chapter helps you prepare for first-time startup. Read it before you power up your server product.
By preparing for first-time startup, you can take advantage of the full range of configurations available on the server product. You are not required to plan your network before sitting at the console and using the setup command facility for the first time, but you must connect an ASCII terminal to the server product's system console port, as described in the "Overview" chapter. By separating the planning tasks from the configuration tasks, you can set up the server product in one sitting. You can also tailor it to meet your needs and to fit within a consistent scheme.
This chapter helps you complete the following tasks:
Use the blank configuration worksheets in the "Blank Worksheets" appendix to record parameter values, according to the information in this chapter. The Global Configuration Worksheet can accommodate global information about a single server product. If you plan to install more than one server product, make additional copies of the blank worksheet. The Interface Configuration Worksheet can accommodate four interfaces. If you plan to install more than four interfaces on your server product, make additional copies of the blank worksheet.
You use these worksheets to help gather and maintain information about your server product. The worksheets map to the two-part configuration process of the setup command facility, which is automatically invoked at first-time startup. In the first part of the configuration process, you use the values recorded on the Global Configuration Worksheet to specify global or system-wide parameters. In the second part, you configure each individual interface using the values you recorded on the Interface Configuration Worksheet.
The Global Configuration Worksheet, when properly filled in, contains all the values you need to enter at the Configuring Global Parameters portion of the setup command facility. Remember, the setup command facility is automatically invoked at first-time startup. Preparing the pertinent information before you start up the server product enables you to get your system up and running quickly and uneventfully.
The worksheet lists two levels of information:
The setup command facility does not request system hardware information at first-time startup, but it is useful to write the information on the worksheet to complete your records. The facility does request global parameters at first-time startup.
Figure 2-1 and Figure 2-2 show a sample Global Configuration Worksheet. Retrieve the blank, two-page Global Configuration Worksheet from the "Blank Worksheets" appendix before continuing. As you proceed through the following descriptions, record your information on it. Be sure to record information on both pages before powering up your server product for the first time.
Use this section to record system hardware information on your Global Configuration Worksheet.
A Default: label marks the factory default, and an Action: label marks the action you take to fill in the worksheet.
Our server products accommodate a wide variety of needs. Customers can choose among the following system types:
All our systems provide protocol translation. The ASM-CS and 500-CS provide asynchronous routing for IP and IPX. The Cisco 2500 features full routing capability, in addition to its communication server functionality.
Default: None.
Action: Circle your system type on the worksheet, or write it in.
The serial number is on the back or bottom panel. This information can help you track your physical inventory.
Default: None.
Action: Write your system serial number on the worksheet.
When you order your server product, you specify the number and type of synchronous interfaces, such as Ethernet, Token Ring, or synchronous serial interfaces, that the server product should have. The factory preconfigures your new server product with this information.
Check the back of your system to verify that your server product has synchronous interfaces you ordered.
Default: None.
Action: Write the number of interfaces on the worksheet.
The number of asynchronous lines depends on the type of server product you have. If you have a 500-CS or a Cisco 2500, you can have 8 or 16 asynchronous terminal lines. If you have an ASM, you can have 16 to 112 asynchronous lines (in increments of 16). Again, when you order your server product, you specify the number of asynchronous lines for the server. The factory preconfigures your server with the specified number of asynchronous lines.
Check the back of your system to verify the number of asynchronous lines.
Default: None.
Action: Write the number of interfaces on the worksheet.
This section contains information about each global parameter that you can configure through the setup command facility. A Default: label marks the factory default, and an Action: label marks the action you take to fill in the worksheet. Use this information to complete the Global Configuration Worksheet.
The host name is the name of the server product. The name you specify is used in the system prompts and can contain from 1 to 80 uppercase and lowercase alphanumeric characters. The host name is case sensitive. A number can be the first character. Leading spaces are ignored. For example, " 500cs" is interpreted as "500cs" (without the space).
Use a name that helps you identify the location of the server product, or to whom it is providing services. If you will be naming more than one host within your network, try to devise a consistent naming scheme so that host identification is easy.
Default: CS (for the 500-CS and ASM-CS) or Router (for the Cisco 2500).
Action: Write the host name on the worksheet the way you want it to appear in the system prompts.
Your system has two default levels of security: user and privileged. The commands available at the user level are a subset of those available at the privileged level. Because many privileged-level commands are used to set operating parameters, you should password-protect these commands to prevent unauthorized use. Users must enter the correct password, called the "enable password," to gain access to the privileged-level commands.
There is no factory default enable password. However, the enable password you set during first-time startup appears as the default the next time you run the setup command facility.
An enable password can contain from 1 to 80 uppercase and lowercase alphanumeric characters; a number cannot be the first character. Spaces are also valid password characters; for example, "two words" is a valid password. Leading spaces are ignored, though trailing spaces are recognized. For example, " woolly" is interpreted as "woolly" (without the space). On the other hand, "woolly " is recognized as "woolly " (with the space).
For more information about enable passwords, refer to the Access and Communication Servers Configuration Guide or the Access and Communication Servers Command Reference publication.
Default: None.
Action: Write an enable password on the worksheet.
In addition to the enable password, each virtual terminal line requires a password. If you do not set a password, by default the system responds to attempted connections by displaying an error message and closing the connection. (Virtual terminal lines are used when you access the server product remotely via the network.)
A virtual terminal password can contain from 1 to 80 uppercase and lowercase alphanumeric characters; a number cannot be the first character. Some spaces are also valid password characters. For example, "two words" is a valid password. Leading spaces are ignored, though trailing spaces are recognized. For example, " woolly" is interpreted as "woolly" (without the space). On the other hand, "woolly " is recognized as "woolly " (with the space).
The virtual terminal password is case sensitive. There is no factory default virtual terminal password. However, the virtual terminal password you set during first-time startup appears as the default the next time you run the setup command facility.
Although each virtual terminal line requires a password by default, you can disable password checking to allow line connections without passwords. With this configuration, users are not required to give a password, although one may exist. To disable passwords, use the no login command. Refer to the Access and Communication Servers Configuration Guide and Access and Communication Servers Command Reference publication for more information on disabling passwords. Refer to the Cisco Access Connection Guide to make line connections.
Default: None.
Action: Write your virtual terminal password on the worksheet. This single password applies to all virtual terminal lines.
The Simple Network Management Protocol (SNMP) is the most widely supported open standard for network management. It provides a means to access and set configuration and run-time parameters of routers and communication servers. SNMP defines a set of functions that can be used to monitor and control network elements.
You configure SNMP on a global basis only; you cannot specify it for individual interfaces.
Default: No.
Action: If you want to configure SNMP on a system-wide basis, circle Yes on the worksheet. At first-time startup, this value configures read-only SNMP with a blank password. If you do not want to run SNMP on your system, circle No.
If you configure SNMP, also specify a community string as follows:
mycommunity", "my community", and "mycommunity " are invalid community strings due to the leading, embedded, and trailing spaces, respectively. "ThisIsMyCommunity5" is a valid community string since no spaces exist. The community string is case sensitive.
DECnet is a protocol suite developed and supported by Digital Equipment Corporation. The DECnet protocol associates addresses with machines, not interfaces.
An access server can have only one DECnet address. DECnet addresses consist of area number and node number. For example, in DECnet address 53.6, DECnet node 6 is located in area 53.
An area can span many access servers, and many areas can be attached to a single cable. If a DECnet host such as a server exists on many cables, its area/node address is the same on all cables. This type of addressing is called DECnet Phase IV addressing.
Default: No.
Action: If you plan to use DECnet Phase IV addressing, circle Yes on the worksheet. If you do not want to use DECnet Phase IV, circle No. If you want Phase V addressing, select the Connectionless Network Services (CLNS) protocol (further down on the worksheet) in addition to circling No.
If you plan to use DECnet Phase IV addressing, provide the area number and node number of the access server, and indicate whether you want area routing. Write in values for the following:
The United States Department of Defense originally defined the Internet Protocol (IP) as a standard protocol for interconnecting computers from different manufacturers on a given network. IP is now the de facto standard for vendor-independent networking.
Default: Yes.
Action: If you plan to route IP, circle Yes. If not, circle No.
Select an interior routing protocol for IP. Using the setup command facility, you can specify only one of two interior routing protocols to operate on your system: Interior Gateway Routing Protocol (IGRP) or Routing Information Protocol (RIP). These protocols are mutually exclusive.
IPX is the network protocol used by Novell's NetWare products. Your server product supports IPX. For detailed information on IPX, refer to the Access and Communication Servers Configuration Guide.
Default: No.
Action: If you plan to configure IPX, circle Yes. If not, circle No.
Xerox Network Systems (XNS) was originally designed to run over Ethernet. XNS can also be routed over FDDI, Token Ring, and point-to-point serial lines. Your access server supports the XNS protocol suite. For detailed information on XNS, refer to the Router Products Configuration Guide.
Default: No.
Action: If you plan to configure XNS routing on your system, circle Yes. If not, circle No.
AppleTalk is a network protocol developed by Apple Computer. It is a client-server, or distributed, network system. Users share network resources such as files and printers with other users. Interaction with servers is transparent to the user.
Your server product supports the AppleTalk network protocol (both extended and nonextended) over FDDI, Ethernet, Token Ring, synchronous serial, and X.25 interfaces. For detailed information on AppleTalk, refer to the Access and Communication Servers Configuration Guide.
If you want to enable AppleTalk Remote Access on your server product, you must first configure AppleTalk routing.
Default: No.
Action: If you plan to configure AppleTalk or AppleTalk Remote Access, circle Yes. If not, circle No.
If you plan to configure AppleTalk on your server product, you must also decide whether to have multizone networks.
The Apollo Domain (Apollo) routing protocol is the native-mode networking protocol for Apollo workstations. This protocol enables an Apollo host to have interfaces on more than one physical network. Each physical network is identified by a unique 32-bit address in hexadecimal format. The address consists of a network number followed by a host number.
Your access server supports packet forwarding and routing for Apollo on Ethernet, FDDI, and serial interfaces using HDLC and X.25 encapsulation. Direct attachment to the 12-Mbps Domain Token Ring is not supported.
Default: No.
Action: If you plan to configure Apollo, circle Yes. If not, circle No.
If you plan to configure Apollo on your access server, you must also determine the Apollo routing number.
The software on your access server supports packet forwarding and routing for the Connectionless Network Services (CLNS) protocol, an International Organization for Standardization (ISO) implementation. CLNS provides the basis for DECnet Phase V.
To understand CLNS routing, you need to be familiar with the hierarchical concepts of domain and area. At the top of the hierarchy is a set of routing domains. The domain address uniquely identifies the routing domain. Within each routing domain are one or more areas. The area address uniquely identifies the area. For detailed information about how your access server implements CLNS, refer to the Router Products Configuration Guide.
Default: No.
Action: If you plan to configure CLNS, circle Yes. If not, circle No.
If you plan to configure CLNS on your system, you can provide router tag, domain, area, and station ID information, or you can use default values.
The Banyan Systems Virtual Integrated Network Service (VINES) protocol is designed for PC networks. Your access server supports the VINES network protocol over all media types. For detailed information about how your access server implements VINES, refer to the Router Products Configuration Guide.
Default: No.
Action: If you plan to configure VINES, circle Yes. If not, circle No.
Your access server supports transparent and source-route bridging. The setup command facility allows you to configure only transparent bridging. You cannot use the setup command facility to configure source-route bridging. To configure source-route bridging, you must use the command interpreter. Refer to the Router Products Configuration Guide for information on configuring source-route bridging.
You can configure transparent bridging only if the subset image you ordered includes bridging. You can verify that your subset image has bridging capability by looking at the installed hardware banner that appears at first-time startup.
You configure bridging, like routing, for the system as a whole. That is, if you bridge a protocol, you must bridge it on all interfaces. For example, you cannot bridge XNS on one interface and route it on another. If you bridge XNS, you must bridge it on all interfaces. However, on the same system, you can bridge some protocols (on all interfaces) and route other protocols (on all interfaces). For example, you can bridge XNS, Vines, and AppleTalk on all interfaces, and route IP, IPX, and DECnet on all interfaces.
For more information about bridging, refer to the Router Products Configuration Guide. For more information about bridging commands, refer to the Router Products Command Reference publication.
Default: No.
Action: If you plan to configure transparent bridging, circle Yes. If not, circle No.
The local area transport (LAT) protocol from Digital Equipment Corporation (Digital) is the protocol used most often to connect to Digital hosts. LAT is a Digital-proprietary protocol. Cisco uses LAT technology licensed from Digital.
With the LAT protocol, you can establish a connection to a host, then pass your keystrokes to the host. A user can establish a LAT connection through a server product running protocol translation to a Digital host, simply by entering the host name.
LAT cannot be routed because Digital's LAT protocol includes its own transport protocol (Layer 4 of the OSI reference model), which runs directly over Ethernet (Layer 2 of the OSI reference model) rather than over a standard routing layer. LAT must be bridged to pass between different network segments. The server product provides the option of transporting LAT in protocol translation mode. A server product with the protocol translation option can translate LAT to Telnet or X.25 for transmission over a WAN, which can be translated back to LAT on the other end of the connection.
You can configure this WAN-to-LAT translation to be transparent to the user. This configuration also avoids LAT time-out problems, which are common in WAN-bridged LAT. For more information about how your server products implements LAT, refer to the Protocol Translation Configuration Guide and Command Reference publication.
Default: No.
Action: If you plan to use LAT on this system, write Yes. If not, write No.
You can use the setup command facility to configure the asynchronous (async) lines on your server product at first-time startup.
Default: Yes.
Action: If you plan to configure your async lines, Circle Yes on the worksheet. If not, circle No.
The parameters that you can configure for async lines at the global level include the following:
We recommend that you globally set each parameter with the setup command facility, then configure the lines individually after you complete this process.
The asynchronous lines on your server product support several transmission speeds. This parameter sets both the transmit (to terminal) and receive (from terminal) speeds. Table 2-1 lists the available line speeds for each server product model.
| Server Product | Line Speeds |
|---|---|
| 500-CS | Any speed between 50 and 38400 |
| ASM-CS standard | 75, 110, 134, 150, 300, 600, 1200, 1800, 2000, 2400, 4800, 9600, 11520, 12800, 14400, 19200, 23,040, 28800, 38400, and 57600 |
| Cisco 2500 | Any speed from 50 to 115200 |
Default: 9600.
Action: Write the terminal line speed of your choice on the worksheet.
Configure your lines for hardware flow control if an async device (such as a modem) or communications protocol requires it. If you are configuring your lines for AppleTalk Remote Access (ARA), you must enable hardware flow control. ARA does not function with software flow control. SLIP lines explicitly turn off software flow control when a server product enters protocol mode on a line. Choosing this option has the same effect as issuing the flowcontrol hardware command in line configuration mode.
Default: Yes.
Action: If you plan to enable hardware flow control on your lines, circle Yes. If not, circle No.
You can configure your server product to support only incoming calls from modems, only outgoing calls to modems, or both incoming and outgoing modem calls. Using the setup command facility, you can configure your server product to support both incoming and outgoing calls on all async lines or you can configure your server product for no modem support. To configure your server product for only incoming or only outgoing modem calls, you must use the command interpreter. Refer to the Access and Communication Servers Configuration Guide for more information on configuring modem lines for a single direction.
You can also restrict the direction of modem calls by adjusting the configuration of the modem itself. Refer to the modem manual for details.
Choose Yes to enable both incoming and outgoing modem calls. (You can produce the same effect by entering the modem inout command in line configuration mode.) Choose No for no modem support.
Default: Yes/No. You must choose Yes or No before continuing to the next prompt.
Action: If you plan to support both incoming and outgoing calls on your async lines, circle Yes on the worksheet. If you do not want modem support for your server product, circle No.
You must define a chat script for dialing out on asynchronous lines. The setup command facility can assign a default chat script on a global basis. You can use this chat script in more complex dial-on-demand routing configurations for modem dialing. Enabling this feature has the same effect as the process of entering global configuration mode on your system; entering a chat-script command at the command prompt; issuing a regular expression; and then entering line configuration mode and issuing a script-dialer command. The following line, which is a chat script named cisco-default, is entered into your system's global configuration:
chat-script cisco-default ABORT ERROR "" "AT Z" OK "ATDT \T" TIMEOUT 30 \c CONNECT
Default: Yes.
Action: If you plan to use the default chat script cisco-default on your system, circle Yes. If not, circle No.
Use the setup command facility to permit dial-in IP access with the Serial Line Internet Protocol (SLIP) or Point-to-Point Protocol (PPP) from within EXEC mode. The alternative is dedicated asynchronous mode, which does not enable use of the slip and ppp from within EXEC mode. Enabling this option has the same effect as issuing the async mode interactive command from within interface configuration mode for each asynchronous interface on your system.
Default: No.
Action: If you plan to permit dial-in SLIP and PPP access from EXEC mode, circle Yes. If not, circle No.
This option specifies that users dynamically assign IP addresses. That is, a user can specify an IP address (or name) of a remote network host at the EXEC level when making a connection using the slip or ppp EXEC command. Enabling this option has the same effect as issuing the async dynamic address command from within interface configuration mode.
Default: Yes.
Action: If you plan to permit users to specify IP addresses at connection time, circle Yes. If not, circle No.
This option specifies that a default IP address can be used when a connection is made to a remote network device (such as a PC). That is, the user does not have to enter an IP address when connecting to the device, because the default IP address has been set in the configuration. Selecting this option has the same effect as issuing the async default ip address command from within interface configuration mode. If you set this parameter in global configuration mode of the setup command facility, the interface configuration portion of the setup command facility prompts you for specific default client IP addresses for each interface.
Default: No.
Action: If you plan to have the server product specify the IP address at connection time, circle Yes. If not, circle No.
Your server product supports Van Jacobsen TCP header compression on asynchronous lines. On SLIP and PPP lines, this option prevents transmission of compressed packets until one of the following events occurs:
Answering Yes has the same effect as entering the ip tcp header-compression passive command from within interface configuration mode. For more information about this command, refer to the Access and Communication Servers Command Reference publication.
Default: Yes.
Action: If you plan to enable header compression on SLIP and PPP lines, circle Yes. If not, circle No.
Routing updates can use a great deal of bandwidth, but most asynchronous links have very low bandwidth. Selecting No for this option prevents routing updates from being sent on your async lines. Selecting this option has the same effect as issuing the async dynamic routing command from within interface configuration mode.
Default: No.
Action: If you plan to permit routing updates on your async lines, circle Yes. If not, circle No.
Your server product supports routing of IPX packets across asynchronous lines. If you want to permit routing of IPX packets, enable this option.
Default: Yes.
Action: If you plan to permit IPX routing on async lines, circle Yes. If not, circle No.
Your server product supports the Network Computing Device, Inc. XRemote feature on all access and communication servers. When an NCD terminal does not include in ROM the fonts used by X applications, you must identify one or more font servers from which the server product and the NCD terminal can obtain fonts. You can identify as many XRemote font servers as you need; it is unlikely that you will ever reach the maximum number that the software allows you to identify.
You can use the setup command facility at first-time startup to identify one or more XRemote font servers. If you use setup to configure your XRemote font servers, the facility prompts you to enter an IP address for each font server. After first-time startup, you use the xremote tftp host command to configure XRemote font servers.
Default: No.
Action: If you want to configure one or more XRemote font servers during first-time startup, circle Yes on the worksheet. If you do not want to configure XRemote font servers on your system or you do not want to configure XRemote font servers using the setup command facility, circle No.
Enter an IP address for each XRemote font server.
For more information about XRemote configuration and management information, refer to the Access and Communication Servers Configuration Guide. For information about making XRemote connections, refer to the Cisco Access Connection Guide.
You can configure your server product as an AppleTalk Remote Access (ARA) server. Cisco's implementation of ARA gives Macintosh users at remote locations direct access to information and resources. Macintosh users can connect to other Macintosh computers or an AppleTalk network over standard async telephone lines.
Configuring your server product to act as an ARA server allows remote Macintosh users to dial in, become a network node, and connect to devices on other networks. For additional information about ARA, refer to the Access and Communication Servers Configuration Guide or the Access and Communication Servers Command Reference publication.
Default: Yes.
Action: If you plan to configure your server product as an ARA server, circle Yes. If not, circle No.
This parameter creates a pseudo network and network number, which exist only inside the server product. All ARA clients must belong to this pseudo network. The server product advertises the network number as if it is an existing AppleTalk network.
Selecting this option is equivalent to entering the arap network [net-number] command in global configuration mode. For more information about this command, refer to the Access and Communication Servers Command Reference publication.
Default: 1.
Action: Write the number of the AppleTalk network for ARA clients on the worksheet.
This parameter specifies the zone name for a pseudo AppleTalk network, which also exists only inside the server product. The server product automatically places all ARA clients in the network with this zone name and advertises the zone name as if it is an existing AppleTalk network.
Selecting this option is equivalent to entering the arap network [zone-name] command in global configuration mode. For more information about this command, refer to the Access and Communication Servers Command Reference publication.
Default: * (asterisk).
Action: Write a meaningful AppleTalk zone name on the worksheet.
After you complete the Global Configuration Worksheet, fill in the Interface Configuration Worksheet. You will use this information and the setup command facility to configure parameters for each installed interface.
The Interface Configuration Worksheet lists two levels of information:
The setup command facility does not request system hardware information, but it is useful to write the information on your worksheet to complete your records. The setup facility does request interface parameters at first-time startup. The interface parameters depend on the decisions you make about the global parameters. For example, if you have not configured a protocol at the global level, you do not need to configure it at the interface level.
Figure 2-3 shows a sample Interface Configuration Worksheet. The "Blank Worksheets" appendix contains a blank worksheet for your convenience. Record information about your interfaces on the blank worksheets as you proceed through the following descriptions.
The values for the following system hardware information should be the same as those you indicated on the Global Configuration Worksheet:
Refer to the "Determining Global Parameters" section earlier in this chapter for information about these values.
This section contains information about each interface parameter that you can configure through the setup command facility for the installed network. Use this information to complete the Interface Parameters portion of the worksheet.
In the following descriptions of the parameters that you determine, a Default: label marks the factory default and an Action: label marks your task for each parameter.
The setup command facility automatically presents each installed interface for you to configure. The facility prompts for interface information in the same order in which the interfaces are installed in the chassis. For example, if you have two Ethernet interfaces, the facility prompts you to first configure interface Ethernet0 and then to configure Ethernet1.
Default: The default is the order in which the interfaces are installed in the chassis.
Action: Write each interface name across the top of the worksheet in the row labeled "Interface Name."
You can decide whether you want to configure an installed interface at first-time startup. If at first-time startup you accept the configuration script, the system shuts down the interfaces you indicate you will not configure.
Default: No.
Action: If you plan to configure a particular interface at first-time startup, write Yes in the column for that interface. If not, write No.
If you have a Token Ring board installed, select a speed for your network. You can enter 4 to set the Token Ring speed to 4 Mbps, or 16 to set the Token Ring speed to 16 Mbps. Once you set this value, the setup command facility does not ask you for it again.
 | Caution If you select the wrong speed, the ring will be brought down. |
Default: 16.
Action: Write the correct Token Ring speed for your network on the worksheet.
Determine whether to use IP routing for a particular interface.
Default: No.
Action: If you plan to use IP routing for an interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
If you plan to use IP routing on an interface, provide the IP address and subnet mask bits for that interface. Indicate values on the worksheet as follows:
| First Class | First Byte | Network Bits | Host Bits | |
|---|---|---|---|---|
| Max Subnet Bits | Min Address Bits | |||
| A | 1-126 | 8 | 22 | 2 |
| B | 128-191 | 16 | 14 | 2 |
| C | 192-223 | 24 | 6 | 2 |
Determine whether to use DECnet Phase IV addressing on a particular interface.
Default: No.
Action: If you plan to use DECnet Phase IV addressing for the interface, write Yes on the worksheet. If not, write No. Repeat this for each of the installed interfaces you plan to configure.
If you will be using DECnet Phase IV addressing on an interface, you must also provide the route cost for that interface. Indicate a value on the worksheet as follows:
Determine whether to use IPX on a particular interface.
Default: No.
Action: If you plan to use IPX on the interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
If you will use IPX on an interface, you must also provide the network number for that interface as follows:
Determine whether to use XNS on a particular interface.
Default: No.
Action: If you plan to use XNS on the interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
If you plan to use XNS on an interface, you must also provide the network number for that interface. Indicate the information on the worksheet as follows:
Determine whether to use AppleTalk on a particular interface. You must enable AppleTalk on at least one network interface for AppleTalk Remote Access to function on the server product's asynchronous lines.
Default: No.
Action: If you plan to use AppleTalk on the interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
Remember, during configuration of the global parameters, you specified whether you wanted to configure multizone networks. Your answer applies to every interface you configure.
If you plan to use AppleTalk on an interface, you must also provide the other information for that interface as follows.
Determine whether to use Apollo Domain (Apollo) addressing on a particular interface.
Default: No.
Action: If you plan to use Apollo addressing on the interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
If you will use Apollo on an interface, you must also provide the network number for that interface as follows:
Determine whether to use CLNS on a particular interface.
Default: No.
Action: If you plan to use CLNS on the interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
Determine whether to use Banyan VINES on a particular interface.
Default: No.
Action: If you plan to use VINES on the interface, write Yes on the worksheet. If no, write No. Repeat this for each installed interface you plan to configure.
Determine whether to use transparent bridging on a particular interface. (Remember that you cannot use the setup command facility to configure source-route bridging. To configure source-route bridging, you must use the command interpreter. Refer to the Router Products Configuration Guide for information on configuring source-route bridging.)
Default: No.
Action: If you plan to use transparent bridging on the interface, write Yes on the worksheet. If not, write No. Repeat this for each installed interface you plan to configure.
The local area transport (LAT) protocol from Digital Equipment Corporation (Digital) is the protocol used most often to connect to Digital hosts. LAT is a Digital-proprietary protocol. Cisco uses LAT technology licensed from Digital.
With LAT, you can establish a connection to a host, then pass your keystrokes to the host. A user can establish a LAT connection through the server product to a Digital host simply by entering the host name.
The server product provides the option of transporting LAT in protocol translation mode. You can configure the server product software to translate LAT to Telnet or X.25 for transmission over a WAN. Telnet or X.25 is then translated back to LAT on the other end of the connection. You can configure this WAN-to-LAT translation to be transparent to the user. This configuration also avoids LAT time-out problems, which are common in WAN-bridged LAT. For more information about LAT, refer to the Access and Communication Servers Configuration Guide.
Default: Yes.
Action: If you plan to use LAT on the interface, write Yes on the worksheet. If you do not want to use LAT on the interface, write No. Repeat this for each of the installed interfaces you plan to configure.
For IPX, you must associate a network number with every network segment. Specify the IPX network number for each asynchronous line. An IPX network number is a 32-bit value. It must be a hexadecimal number between 1 and FFFFFFFF.
Default: The default is 3 for the first async line, 4 for the second async line, and so on.
Action: Write the IPX network number on the worksheet for each installed async line you plan to configure.
If you specified on the Global Configuration Worksheet that a default IP address be used for each async line when a connection is made to a remote network device (such as a PC), then specify on the Interface Configuration Worksheet the specific default IP address for each async interface.
A default client IP address means that users do not have to enter an IP address when connecting to a device, because you have set the default IP address in the configuration. Specifying a default client IP address limits user access from a particular async interface to specific devices.
Default: None.
Action: If you plan to configure a default client IP address for an async interface, write the IP address for each async interface on the worksheet. Note that if you enter an address for one async interface, the setup command facility increments the IP address one digit for each subsequent async interface. You can accept the default increments or change the IP addresses as you like.
|
|