IBM Books

Network Utility User's Guide

Chapter 3. Performing the Initial Configuration

This chapter introduces the basics of configuring Network Utility, and gives specific procedures for configuring a new Network Utility. These procedures move the Network Utility from a passive state where it is waiting to be configured, to a state where it has active network interfaces and protocols.

Before using these procedures, you must connect a user console as described in Chapter 2, "Bringing Up a User Console".

Configuration Basics

A Network Utility configuration is a collection of data items that control how the software operates, including such elements as:

When you boot up a Network Utility, the system reads its configuration information from a file on the hard disk, and activates interfaces and protocols according to the information in that file. You create the file in one of two ways:

Choosing Your Configuration Method

Some IBM routing product users prefer the Configuration Program, others prefer the command-line interface, and still others use a combination of the two. The approach you take is up to you.

Here are some of the factors users cite in favor of the Configuration Program:

Here are some of the factors users cite in favor of the command-line interface:

Getting Started from Config-only Mode

If you boot a Network Utility and see the Config (only)> prompt from the user console, you are in config-only mode. A Network Utility boots up into config-only mode when the current configuration file on the hard disk has no data items that would allow it to do any useful functions like forward data packets3. You need to configure at least one adapter port and one protocol (for example, IP, DLSw, or APPN) and reboot in order for the Network Utility to start up in normal working mode.

If you have a Network Utility at the Config (only)> prompt, perform these actions:

  1. Choose whether you want to use the command line or the Configuration Program for your initial configuration. It is easy to switch methods later if you want to try both.

  2. Based on your choice, follow one of these procedures:

Procedure A: Command-Line Procedure for Initial Configuration

Use this procedure to configure a Network Utility for the first time starting from the Config (only)> command-line prompt:

Part 1: Create a Minimal, Basic Configuration

  1. Use the add device command to configure at least one network interface as follows:

    1. Type add dev ? to see a list of supported adapter types.

    2. Type add dev type, where type consists of the first few letters from a row of the adapter list. For example, add dev tok selects the Token-Ring adapter. Type enough letters to uniquely identify the adapter you want.

    3. When prompted for slot number, enter 1 for the left-hand adapter slot of the Network Utility, or 2 for the right-hand slot.

    4. If you are adding a multiport adapter, the system prompts you for the port number of the interface you want to configure. Port numbers on adapters are fixed as follows:
      • Ports on multi-port LAN adapters are numbered 1 and 2 and are labelled on the adapter face.
      • Ports on multi-port WAN adapters are numbered starting with 0 and are labelled on the connectors at the end of the adapter cable.

    5. The system then assigns a logical interface number, also known as a net number. This is the key number by which you refer to this interface on every other command in the system. For example, if you want to delete the configuration for this interface, type delete interface and then give the logical interface number.

    6. If necessary, make the following adjustments to the default device configuration:

      If you added a Token-Ring port and you want it to run at 16 Mbps instead of the default 4 Mbps, type these commands:

      net interface number
      speed 16
      exit

      If you added a 10 Mbps (not 10/100) Ethernet port and you want to use the BNC (10BASE2) connector instead of the default RJ45 (10BASET) connector, type these commands:

      net interface number
      conn bnc
      exit

    Repeat step 1 for each interface you want to configure.

  2. If you want to be able to dynamically add interfaces in the future without needing to reboot Network Utility, type set spare number from the Config (only)> prompt, where number is the maximum number of interfaces you need to add without rebooting.

  3. Use the qconfig command to start the "Quick Config" program. Use this program to configure IP and SNMP access to Network Utility as shown below.

    Quick Config is a feature of the command-line configuration process. Instead of waiting for you to type commands, it asks you questions and creates configuration data based on your replies. An example of a Quick Config question is: 

        Configure Bridging? (Yes, No, Quit): [Yes]

    The values in parentheses are the possible responses. The value in square brackets is the default response. To accept the default, press Enter.

    Respond as follows to the Quick Config questions (some of these are default responses):

    1. Configure Bridging by responding no to Configure Bridging?

    2. Configure Protocols by responding yes to Configure Protocols?

    3. Configure IP as follows:

      1. Enter yes to Configure IP?

      2. For any interfaces to which you want to assign an IP address, respond yes to Configure IP on this interface? If you intend to use the PCMCIA EtherJet card as your only IP interface, respond no for every configured network interface.

      3. Enter the IP address at the IP Address prompt.

      4. Enter the IP mask at the Address Mask prompt.

      5. If you want to enable RIP or OSPF, respond yes to Enable Dynamic Routing? and respond to subsequent related questions.

      6. If at some point you may want to send a configuration directly from the Configuration Program to this Network Utility, respond yes to Define Community with Read_Write_Trap Access? and enter any single-word name you want as the community name.

        If you never expect to use the Configuration Program, respond no.

      7. Respond yes to Save this configuration? This saves the IP part of the configuration in memory.

    4. Save the Configuration file by responding yes to Do you want to write this configuration?

Part 2: Activate the New Configuration

You have now configured at least one interface and one protocol (IP, with SNMP). This small configuration is sufficient to leave config-only mode.

  1. From the Config (only)> prompt, type reload and respond yes to the confirmation prompt. The Network Utility reboots and activates your new configuration.

    If you see a prompt about saving configuration changes, that means you have made some configuration changes after saving the configuration file when you completed Part 1 of this procedure. Type yes to save these changes as part of your new configuration before the reboot proceeds.

  2. Verify the Network Utility reboot

    If your user console is using a dial or Telnet connection, reboot causes you to lose your connection. Reconnect after a few minutes. Otherwise just watch the boot messages from your console.

    When the reboot completes, your console should display the * command prompt, indicating that you are in normal operating mode and no longer in config-only mode. The configuration you created in Part 1 of this procedure is now active.

Part 3 - Add Additional Protocol Information

You are now in normal operating mode with the interfaces you configured, running only IP.

If you are a new user and want to become familiar with the product before configuring the rest of your functions (such as TN3270 or DLSw), skip the rest of this procedure and see the guidelines in What to Do Next.

If you want to configure all your functions right now, continue here.

  1. Select the configuration scenario from Part 3, "Configuration and Management Specifics" that most nearly resembles the use to which you are placing this Network Utility.

    If none of these scenarios is suitable, use the MAS Protocol Configuration and Monitoring Reference, MAS Using and Configuring Features, and MAS Software User's Guide to determine what you need to configure.

  2. In the "Example Configuration Details" chapter that follows your selected scenario, find the configuration parameter table that corresponds to that scenario4. Use the "Command-Line Commands" column to guide you in configuring that scenario, changing the values for your particular adapters and network.

    If you find that you are having trouble navigating the command line and entering commands, you may want to get more familiar with general command-line configuration before proceeding. See What to Do Next for suggestions on how to proceed.

  3. When you have finished entering configuration commands, repeat the steps in Part 2: Activate the New Configuration, but issue the reload command from the * prompt instead of the Config (only)> prompt.

Procedure B: Configuration Program Initial Configuration

Use this procedure to configure a Network Utility for the first time using the Network Utility Configuration Program.

Part 1: Create the Configuration at the Configuration Program

  1. From the Configuration Program CD-ROM, install the appropriate version of the Configuration Program onto your workstation.

    For installation instructions, see:

    Start the Configuration Program. If you want to try the program by doing a new configuration from scratch, select New configuration and Network Utility from the Configure option on the menu bar in the Navigation Window.

  2. Select the configuration scenario from Part 3, Configuration and Management Specifics that most nearly resembles the use to which you are placing this Network Utility. If none of these scenarios is suitable, use the MAS Protocol Configuration and Monitoring Reference, MAS Using and Configuring Features, and MAS Software User's Guide manuals to determine what you need to configure. Use any of configuration parameter tables in Part 3, Configuration and Management Specifics as an example of mapping command-line commands to Configuration Program panels. When you have completed your configuration, skip to step 7.

  3. In the "Example Configuration Details" chapter that follows your selected scenario, find the configuration parameter table that corresponds to that scenario.4

  4. From your Web browser, follow the Support and Downloads links from the main Network Utility web page 
    http://www.networking.ibm.com/networkutility,
    and find the example configuration file that matches your selected scenario. Download this file in binary and transfer it to the workstation running the Configuration Program.

  5. Select Open Configuration ... from the Navigation Window and select the path and file name of the example configuration file you downloaded.

  6. Use the "Configuration Program Navigation" and "Configuration Program Values" columns in the table from step 3 to guide you in moving through the configuration and changing the values for your particular adapters and network.

  7. When you have a configuration ready to send to your Network Utility, select Save configuration as ... to save the configuration on your workstation. You may want to choose a new name so you can leave the original example configuration file unchanged.

Part 2: Transfer the Configuration to the Network Utility and Activate It

You have now created the initial configuration. All that remains is to transfer the configuration to the Network Utility hard disk and reboot the Network Utility to activate it. How you should do this transfer depends on your connection setup, as follows:

You can also refer to Loading New Configuration Files for a complete list of the ways to transfer a configuration to Network Utility. You will need TFTP server software on a TCP/IP workstation if you choose not to follow either Procedure A or B.

Procedure A: Direct transfer through Network Utility PCMCIA EtherJet or a network adapter

Use this procedure if your Configuration Program workstation supports TCP/IP and has physical connectivity to the Network Utility PCMCIA EtherJet card or a network adapter in slot 1 or 2.

  1. Configure Network Utility quickly from the command line, so that it has an IP address on at least one interface, and IP and SNMP enabled.

    1. From your user console, perform the steps in Part 1: Create a Minimal, Basic Configuration. Be sure to:
      1. Use add device to define at least one interface in slot 1 or 2
      2. In Quick Config, respond yes to Define Community with Read_Write_Trap Access?

    2. In the Configuration Program, verify that the configuration you are about to send has SNMP enabled and the same community name defined with "read-write trap" access. This is required so that after you activate this configuration, you will be able to repeat step 3 of this procedure to send another configuration.

    3. Perform the steps in Part 2: Activate the New Configuration to reboot Network Utility and activate this temporary command-line configuration.

  2. If you plan to use the PCMCIA EtherJet card, set up its IP addresses as follows after the Network Utility reboot is complete:

    From the * prompt, type talk 6. From the Config> prompt, type system set ip and enter the following values as prompted:

    Next to each prompt, the system shows the current value as the default. To accept the default, press Enter. After you enter all the values, any address change you specified takes effect immediately. The values are stored in Network Utility NVRAM and not as part of any configuration file.

  3. Send the configuration from the Configuration Program (using SNMP):

    1. From the Configure drop-down menu, select Communications and Single router.

    2. On the  Communicate  panel, enter:
      • IP address or name: The IP address of the Network Utility interface you want to send the configuration through. This is either the PCMCIA EtherJet IP address, or the network interface IP address you assigned in Quick Config.
      • Community: The community name you assigned in Quick Config.

    3. Select Send configuration and Restart router. Accept or enter the current date and time, so that Network Utility will reboot with the new configuration immediately after receiving it.

    4. Click on OK. The Configuration Program immediately starts sending configuration data items to the specified routers using SNMP.

      The Configuration Program provides status and result messages about the transfer. If the send operation fails, the Configuration Program lists possible reasons which you should then verify and correct.

    After the Configuration Program completes its configuration transfer, the Network Utility stores the configuration on disk and reboots itself as you directed.

  4. Verify the Network Utility reboot

    If your console is through a dial or Telnet connection, reboot causes you to lose your connection. Reconnect after a few minutes. Otherwise just watch the boot messages from your user console.

    When the reboot completes, your console should display the * command prompt, indicating that you are in normal operating mode and no longer in config-only mode. The configuration you created in Part 1 of this procedure is now active.

Procedure B: Indirect Xmodem transfer through user console session

Use this procedure if your console is via ASCII terminal emulation and you prefer using Xmodem to setting up IP connectivity from the Configuration Program workstation.

  1. From the Configuration Program, export your configuration into the file format understood by Network Utility

    From the Configure drop-down menu, select Create router configuration and specify the path and file name for a .CFG file. Click on OK to write the file.

  2. If necessary, transfer the .CFG file from the Configuration Program workstation to your terminal emulation workstation.

  3. From your console at the Config (only)> prompt, follow this sequence: 
      Config (only)>boot
  Boot configuration
  Boot config>dis auto
  Select the duration to disable autoboot: (once, always): [always] once
  AutoBoot mode is now disabled once.
 
  Operation completed successfully.
  Boot config>exit
  Config (only)>rel y

    If you are prompted about saving configuration changes, respond no. Network Utility reboots and stops at the firmware menu.

    If your console is through a dial connection, reboot causes you to lose your connection. Reconnect after a few minutes and you see the firmware menu.

  4. Make the following sequence of firmware menu selections:
    1. System Management Services (main menu): Option 4, Utilities
    2. System Management Utilities: Option 12, Change Management
    3. Change Management Software Control: Option 12, Xmodem software
    4. Select Type: Config
    5. Select Bank: choose Bank A (active bank)
    6. Select Config: choose position 15

    The firmware tells you when to start the file transfer.

  5. Go to your terminal emulation package and start the transfer of the file from your workstation server, using whatever name you like. When the Network Utility has received the configuration file, the status of the file position will change from CORRUPT to AVAIL. You can verify that this has happened using option 7, List Software, from the firmware Change Management menu.

  6. Boot the Network Utility using the configuration you just loaded.
    1. Use Option 9 Set Boot Information to select the current op-code bank and the new configuration.
    2. Press Esc to reach the main menu and then F9 (Start OS) to boot the Network Utility with the new configuration.

  7. Verify the Network Utility boot

    If your console is through a dial connection, you do not lose the connection when you use the Start OS option. Watch the boot messages from your console.

    When the boot completes, your console should display the * command prompt, indicating that you are in normal operating mode and no longer in config-only mode. The configuration you created in Part 1 of this procedure is now active.

What to Do Next

If you have followed the procedures in this chapter, your Network Utility is now in full operational mode with a configuration you created. With your user console at the * prompt, you are now in a position to use the command-line interface to:

These are the basic tools to see whether your new configuration is working properly, and to make small adjustments to that configuration.

If the command-line interface is new to you, you can use Chapter 5, A Guided Tour through the Command-Line Interface to familiarize yourself with its concepts and how to use it.

If you have some previous experience with IBM routing products or prefer to try tasks without following a tutorial, you can use Chapter 4, Quick Reference to the User Interface as summary information about command-line navigation and some common tasks.

You can use Chapters 6 through 10 to get more background on:

You may have already used the example configuration information in Part 3, Configuration and Management Specifics. The chapters there also contain introductory information about configuring and monitoring the functions:

If you have already configured one of these functions in your initial configuration, use the "Managing" section from the corresponding chapter to begin monitoring and debugging that configuration.

Footnotes:

3
This also happens if your configuration becomes corrupted.

4
If no corresponding table exists, use the "Keys to Configuration" section for that scenario, to get started.

5
This selection of bank and configuration file position assumes that this is the first time you have booted this Network Utility. For more background on this topic, see Configuration Files on Disk.

[ Top of Page | Previous Page | Next Page | Table of Contents ]