|
|
This chapter provides the information you need to prepare for first-time startup. Read it before you power up your protocol translator.
By preparing for first-time startup, you can take advantage of the full range of configurations available on your protocol translator. 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 to the console port, as described in Chapter 1, "Overview." By separating the planning tasks from the configuration tasks, you can set up the protocol translator in one sitting. You can also tailor the system to meet your needs and to fit within a consistent network scheme.
This chapter describes how to fill in the Protocol Translator Configuration Worksheet. The values on this worksheet map to the configuration process of the setup command facility, which is automatically invoked at first-time startup. You will specify global or system-wide configuration information in addition to information about each individual interface. You will use the values you have filled in on the Protocol Translator Configuration Worksheet. A blank configuration worksheet has been provided in Appendix A for your convenience.
In the following descriptions of the parameters that you will determine, the factory default is marked with the Default: label.
The Protocol Translator Configuration Worksheet, if properly filled in, will contain all the values you need to enter at the System Configuration Dialog portion of the setup command facility. Remember, the setup command facility is automatically invoked at first-time startup. All of your preparations should be complete so that you can get your system up and running quickly and uneventfully.
The worksheet can assist you in gathering and maintaining information about your system. Three levels of information are listed on this worksheet:
System hardware information is not requested at first-time startup, but it is useful to write on the worksheet to complete your records. Global and interface parameters, however, are requested at first-time startup.
In the following parameter descriptions, the action you must take in the worksheet is marked with the Action: label.
The Protocol Translator Configuration Worksheet is shown in Figure 2-1. Retrieve the blank worksheet in Appendix A before continuing. As you proceed through the following descriptions, record your information on it.
This section contains information that helps you record the system hardware information on the Protocol Translator Configuration Worksheet. This information is not requested at first-time startup.
You can choose the CPT model protocol translator as a stand-alone unit, or use protocol translation on a communication server and some router models. The system type is clearly marked on the front of the chassis. Protocol translation is supported on the following systems:
If you are using protocol translation on a communication server or a router, refer to the getting started guide for that product in conjunction with the Protocol Translator Getting Started Guide.
Default: None
Action: Circle your system type on the worksheet or write it in.
Each system has a serial number placed on the back or bottom panel. This information may be useful in tracking your physical inventory.
Default: None
Action: Write your system serial number on the worksheet.
The number of interfaces depends on the type of system you have and the number of interface cards you have installed. If you are installing a new system, it will be preconfigured at the factory; this means the number of interfaces is determined when you order the system. Check the back of your protocol translator to determine the installed interfaces.
The number of interfaces installed will affect the second part of the configuration process. It will determine the information you need to provide at first-time startup.
Default: None
Action: Write the number of interfaces on the worksheet.
This section contains information about each global parameter that can be configured through the setup command facility. Use this information to complete the Global Parameters portion of the worksheet.
The host name is the name of the protocol translator. 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.
Try to use names that will help you identify the location of the protocol translator, or to whom it is providing routing 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: PT
Action: Write the host name on the worksheet the way you want it to appear in the system prompts.
Your system has two 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 of the privileged commands are used to set operating parameters, these should be password-protected to prevent unauthorized use.
The enable password allows users access to the privileged command level. There is no default enable password. However, the enable password you set during first-time startup will display 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 the enable password, refer to the Protocol Translator Configuration Guide or the Protocol Translator Command Reference publication.
Default: None
Action: Write the enable password on the worksheet.
In addition to the enable password, each virtual terminal line can also have an individual password. Virtual terminals require a password. If you do not set a password, the system responds to attempted connections by displaying an error message and closing the connection. (Virtual terminals are used when you access the protocol translator 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. 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 default virtual terminal password. However, the virtual terminal password you set during first-time startup, will display as the default the next time you run the setup command facility.
If desired, you can allow line connections without a password. Refer to the Protocol Translator Configuration Guide or the Protocol Translator Command Reference publication for more information. Refer to the Communication Server and Protocol Translator Connection Guide to make line connections.
Default: None
Action: Write the virtual terminal password on the worksheet.
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, communication servers, and protocol translators. SNMP defines a set of functions that may be used to monitor and control network elements.
SNMP is configured on a global basis only; it cannot be specified 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.
Your protocol translator supports the Network Computing Device, Inc. XRemote feature on all communication servers and protocol translators. When fonts used by X applications are not included in ROM on the NCD terminal, one or more font servers must be identified from which the protocol translator and the NCD terminal can obtain fonts from other than ROM. 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.
Default: No
Action: If you want to configure one or more XRemote font servers, circle Yes on the worksheet. If you do not want to configure XRemote font servers on your system, circle No.
If you will be using one or more XRemote font servers, you must also provide an IP address for each XRemote font server. This step is equivalent to specifying the IP address of a font server using the xremote tftp host configuration command. However, you cannot specify an XRemote host name through the setup command facility because the name service facility is not yet running.
Indicate an IP addresses on the worksheet for the XRemote font server as follows:
Table 2-1 provides a summary of subnetting parameters.
| First Class | First Byte | Network Bits | Host Bits |
|---|---|---|---|
| A | 1-126 | 8 | 24 |
| B | 128-191 | 16 | 16 |
| C | 192-223 | 24 | 8 |
For more information about XRemote configuration and management information, refer to the Protocol Translator Configuration Guide.
This section contains information about each interface parameter that is configurable through the setup command facility for the installed network. Use this information to complete the Interface Parameters portion of the worksheet.
The setup command facility automatically presents each installed interface for you to configure. The interfaces are presented in the same order as they are installed in the chassis. For example, if you had one Ethernet interface and one serial interface, you would be prompted to configure interface Ethernet0 then Serial0.
The number of interfaces indicates the number of columns in which you will need to provide information. If you have more than four interfaces, you will need more than one worksheet.
Default: The default is based on the interfaces installed in the chassis.
Action: Write each interface name across the top of the worksheet in the row labeled "Interface Name." Repeat this for each of the installed interfaces you plan to configure.
You must also provide the IP address and subnet mask bits for the installed interfaces. Indicate values on the worksheet as follows:
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.
The LAT protocol allows a user to establish a connection to a host, then passes the user's keystrokes to the host. A user can establish a LAT connection through the protocol translator 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 a standard routing layer. LAT must be bridged to pass between different network segments. The protocol translator provides the option of transporting LAT in protocol translation mode. With Cisco protocol translators, you can establish a configuration so that the protocol translator software will 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 protocol translator implements LAT, refer to the Protocol Translator 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.
|
|
