The 8371 is a plug-and-play device that boots with a default configuration. All possible interfaces are automatically configured at boot time. The following table shows the network interfaces available on the 8371.
Table 7. Network Interfaces Automatically Configured on the 8371
| Device Type | Slot | Ports | Interface Net Numbers |
|---|---|---|---|
| 10/100 Ethernet (fixed ports on base switch) | 0 | 1 - 16 | 0 - 15 |
| 10/100 Ethernet Feature Card | 1 | 1 - 8 | 16 - 23 |
| 10/100 Ethernet Feature Card | 2 | 1 - 8 | 24 - 31 |
| LAG | 3 | 1 - 4 | 32 - 35 |
| ATM | 1 | 1 - 2 | 36 - 37 |
| ATM | 2 | 1 - 2 | 38-39 |
| Ethernet LAN Emulation Client | 3 | 5 - 29 | 40 - 63 |
| Note: | All of the above interfaces cannot be active at the same time. For example, if Ethernet Feature cards are installed in both slots 1 and 2, there is no place to install ATM interfaces. |
In addition to the network interfaces, the transparent bridge is also automatically configured. All the Ethernet interfaces and all of the LECs are configured as ports on the transparent bridge. Interfaces that are configured but are disabled or not actually present, are inactive bridge ports.
Table 8. Network Interfaces Automatically Configured on the 8265 Blade
| Device Type | Slot | Ports | Interface Net Numbers |
|---|---|---|---|
| 10/100 Ethernet (fixed ports on base switch) | 0 | 1 - 16 | 0 - 15 |
| 10/100 Ethernet Feature Card | 1 | 1 - 8 | 16 - 23 |
| Reserved | 2 | 1 - 8 | 24 - 31 |
| LAG | 3 | 1 - 4 | 32 - 35 |
| Reserved | 1 | 1 | 36 - 37 |
| ATM (connection to 8265 backplane) | 2 | 1 | 38 |
| Reserved | 2 | 1 - 2 | 39 |
| Ethernet LAN Emulation Client | 3 | 5 - 29 | 40 - 63 |
Table 9. Network Interfaces Automatically Configured on the 8260 Blade
| Device Type | Slot | Ports | Interface Net Numbers |
|---|---|---|---|
| 10/100 Ethernet (fixed ports on base switch) | 0 | 1 - 16 | 0 - 15 |
| 10/100 Ethernet Feature Card | 1 | 1 - 8 | 16 - 23 |
| Reserved | 2 | 1 - 8 | 24 - 31 |
| LAG | 3 | 1 - 4 | 32 - 35 |
| ATM | 1 | 1-2 | 36-37 |
| Reserved | 2 | 1 - 2 | 38-39 |
| Ethernet LAN Emulation Client | 3 | 5 - 29 | 40 - 63 |
Only one of the 24 automatically Ethernet LEC interfaces is enabled by default. The LEC with an interface number of 40 is enabled, while LECs with interface numbers of 41 - 63 are disabled. The configured LEC has:
This chapter explains how to access the 8371 using a workstation and how to manage operational software images and configuration files. It also provides a brief overview of the configuration methods available for the 8371.
These are the various configuration and monitoring tools that are supported by the physical connections:
If you supply the Web browser the SLIP address, one of the configured IP addresses of the 8371, or its name (when using an IP name server), the Web browser interface will come up.
| Note: | The configured IP addresses of the 8371 include the IP addresses of all the LAN emulation clients . |
This interface must be reached over a serial link before the 8371 is operational in the network; you can use TTY or SLIP to access it. If you use SLIP, you can Telnet into the 8371.
After the 8371 is operational in the network, you can Telnet into the 8371 over IP to bring up this interface. If one connection to the 8371 is a Telnet session, the 8371 can support two connections at one time.
The command line interface is marked by an asterisk (*) prompt.
| Important: | If you use a serial connection, (either local or remote), you must press a key to bring up the asterisk that is the prompt for the command line interface. When you make the connection, the message Please press a key to obtain console appears and reminds you to do this. |
When accessing the 8371 locally on a null modem cable attached to the EIA service port, use VT100 terminal emulation. Because VT100 does not define function keys above F4, edit the keyboard mapping manually as follows: For F6, enter the mapping (ESC)OU. For F9, enter the mapping (ESC)(Left square bracket)009q.
| Note: | (ESC) represents the carat symbol followed by the left square bracket. |
Table 10 defines the ways in which configuration files and operational
software files can be transferred to and from the 8371.
| File Transfer Method | Type of Connection | ||
|---|---|---|---|
| TFTP Get command from the 8371 to the workstation that has the binary
configuration file, to download operational software images and configuration
files to the 8371. Files sent using TFTP must be binary, or the 8371
cannot use them. You should use the Create command of the Configuration
Program to save configuration files in binary format before downloading them
to the 8371.
After the 8371 is operational in the network, you can use the TFTP Put command over IP to upload a file from the 8371 to a workstation. The file will be uploaded in binary format. Both operational software and configuration files can be uploaded. You should use the Read device configuration option of the Configuration Program to make an uploaded configuration file usable by the Configuration Program so that you can change some parameter values in it.
|
| ||
| The Communications Option of the Configuration Program (actually, the protocol for this is SNMP). This method cannot be used until the 8371 is operational in the network. The files are not binary, but are in a format that is internal to the Configuration Program. This function can send configuration files to the 8371 and retrieve them from the server. | IP connection of operational 8371 over functioning network. |
| Important: | After the IBM 8371 is configured and operational, always back up
the active configuration file. Keeping this file enables you to
re-establish the IBM 8371 on the network should the active configuration
become corrupted.
Back up the active configuration file by retrieving it and storing it in the workstation. See "File Transfer" for more information. |
You may find it hard to detect problems caused by configuration errors. A configuration error can initially appear to be a hardware problem because the IBM 8371 will not start or data will not flow through a port. In addition, problems with configuration may not result in an error initially; an error may occur only when specific conditions are encountered or when heavy network traffic occurs.
If you cannot resolve a problem after making a few changes to the configuration or after restoring the active configuration file, it is recommended that you generate a new configuration. Too many changes to a configuration often compound the problem, whereas you can usually generate and test a new configuration within a few hours.
To help manage operational software upgrades and configurations, the IBM 8371 has a software change management feature. This utility enables you to determine which operational software file and which configuration file is active while the IBM 8371 is running. In addition to storing the active operational software and the active configuration file, the IBM 8371 stores two backup images of the operational software and up to 4 configuration files in non-volatile memory.
To use the change management tool in the command line interface to view the operational software image and the configuration files, follow these steps:
See "List" for sample list output and a description of file statuses.
| Note: | A reset interrupts the function of the IBM 8371 for up to 90 seconds. Be sure that the network is prepared for the interruption. |
As previously stated, PENDING and LOCAL files are not loaded into active memory until you reset the IBM 8371.
To reset the IBM 8371, type reload at the OPCON prompt (*) .
See "TFTP" for a sequence of commands to transfer a file from a workstation or server to the IBM 8371 using TFTP. You will need to substitute your own values for the IP address and path, which are given as examples.
To store a configuration file created using the command line interface, type write at the Config> prompt. When using the Web browser interface, select Write. The Write command creates a binary configuration file that contains the most current value of each of the configuration parameters.
This file is stored in the ACTIVE bank and is given PENDING status. If the status of the file is not changed by a Set command, it becomes the ACTIVE configuration when the IBM 8371 is reset.
These are the ways to change the statuses of image and configuration files:
If it is an AVAIL file, resetting the IBM 8371 does not change its status.
See "Set" for information about the set command.
These are the other change management commands:
See "Describe" for information about the Describe function.
This command enables the dumping of memory without intervention from anyone in the event that the IBM 8371 has a catastrophic error. The IBM 8371 will dump memory onto the hard disk. Once a successful dump has been taken, the IBM 8371 attempts to restart. Depending upon the failure of the IBM 8371, it cannot always restart. In this case, you should restart it manually and call a service person, who will dial into the IBM 8371 to determine the nature and the causes of the failure.
To enable dumping, type t 6 at the *, press Enter and then type enable dump or ena du at the Config> prompt. You will see the message:
Config> Automatic memory dump enabled
The default state is to have dumping enabled.
See "Erase" for information about the erase command.
The Copy command moves a file from one location in the storage area to another. This command allows you to change the status as well. The file moved always receives the status of the storage area that it is moved to. For example, suppose that you have this scenario:
In this case, the original configuration file in BANK A CONFIG 1 remains unchanged and AVAIL. The configuration that was in BANK B CONFIG 1 is overwritten by a copy of the configuration file that is in BANK A CONFIG 1. This copy retains the status of the file that it overwrote, in this case, PENDING.
See "Copy" for additional information about the copy command.
The lock command prevents the device from overwriting the selected configuration with any other configuration.
See "Lock" for additional information about the lock command.
The unlock command removes the lock from a configuration allowing the configuration to be updated.
See "Unlock" for additional information about the unlock command.