Previous Page: Dynamic Reconfiguration  Next Page: Managing

Configuring Router Management

The Manage Configuration menu within the Internetworking Configuration menu provides options to copy and transfer common configuration files, configure server access, and perform other network management tasks. Sets of preconfigured files can be imported or exported to specified server destinations. These files can also be loaded as part of the Novell® Internet Access Server 4.1 installation process.

Manage Configuration menu options are

The Simple Network Management Protocol (SNMP) enables network management clients to exchange information about the configuration and status of nodes on an internetwork. The information available is defined by a set of managed objects referred to as the Management Information Base (MIB).

The Manage Configuration menu provides two options for configuring SNMP parameters and information: Configure SNMP Parameters and Configure SNMP Information.

This topic contains the following sections:


Configuring SNMP Parameters

To configure SNMP parameters, complete the following steps:

  1. From the Internetworking Configuration menu, select Manage Configuration .

    The Manage Configuration menu is displayed.

    2.

  2. From the Manage Configuration menu, select Configure SNMP Parameters to configure SNMP for this server only.

    The SNMP Parameters menu is displayed.

    3.

  3. From the SNMP Parameters menu, select Monitor State .

    The following options allow you to indicate how the SNMP agent handles SNMP read operations coming from outside this node.

    Option Description

    Any Community May Read

    Allows all read operations, no matter what community name is provided in the incoming read request.

    Leave as Default Setting

    Avoids changing the Monitor Community name from its default (which is usually public). The default Monitor Community can still be changed manually through SNMP command-line options.

    No Community May Read

    Disables all read operations, no matter what community name is provided in the incoming read request.

    Specified Community May Read

    Allows only read operations that contain the name specified in the Monitor Community field.

  4. Select one of the options previously listed.

    5.

  5. If you selected Specified Community May Read , enter a name in the Monitor Community field.

    Enter the name of the community that is permitted to read management information. SNMP management stations that belong to this community can read the network management database.

    6.

  6. Select Control State .

    The following options enable you to indicate how the SNMP agent handles SNMP write operations coming from outside this node.

    Option Description

    Any Community May Write

    Allows all set operations, no matter what community name is provided in the incoming set request.

    Leave as Default Setting

    Avoids changing the Control Community from its default, which usually is to not allow any set requests. The default can be changed manually through SNMP command-line options.

    No Community May Write

    Disables all set operations, no matter what community name is provided in the incoming set request.

    Specified Community May Write

    Allows only set operations that contain the name specified in the Control Community field.

  7. Select one of the options previously listed.

    8.

  8. If you selected Specified Community May Write , enter a name in the Control Community field.

    Enter the name of the community that is allowed to read and write management information. SNMP management stations that belong to this community can read or modify (write) any value in the network management database.

    9.

  9. Select Trap State .

    The following options allow you to indicate how the SNMP agent handles SNMP trap operations coming from outside this node.

    Option Description

    Do Not Send Traps

    Disables all SNMP traps.

    Leave as Default Setting

    Avoids changing the Trap Community from its default, which is usually public. The default can still be changed manually through SNMP command-line options.

    Send Traps with Specified Community

    Specifies the community name that is included in trap messages in the Trap Community field.

  10. Select one of the options previously listed.

    11.

  11. If you selected Send Traps with Specified Community , enter a name in the Trap Community field.

    Enter the community name to be included in trap messages.

    12.

  12. Select Other SNMP Parameters and press Enter .

    The SNMP Other Parameters window is displayed.

    13.

  13. Enter the following SNMP command-line parameters in the window that is displayed.Enter

    1. Verbose=Yes/No

      Entering Verbose=Yes enables SNMP parameter configuration messages to the console.

      2.

    2. Enter AuthenticationTraps=Yes/No

      Entering AuthenticationTraps=Yes causes SNMP to send traps to trap targets when an authentication failure occurs in GET, GET-NEXT, or SET operations. These targets are configured using the SYS:\ETC\TRAPTARG.CFG file.

      Enter SNMP parameters in the same format in which they appear when entered on the LOAD SNMP command line. For more information, refer to Configuring SNMP Information.

      3.

  14. When you are finished, press Esc ; if prompted, select Yes to save changes, then press Enter .

    The Manage Configuration menu is displayed.

    15.

  15. Select another option from the Manage Configuration menu to continue, or press Esc to return to the Internetworking Configuration menu.

    16.

Configuring SNMP Information

To configure SNMP information, complete the following steps:

  1. From the Internetworking Configuration menu, select Manage Configuration .

    The Manage Configuration menu is displayed.

    2.

  2. From the Manage Configuration menu, select Configure SNMP Information to configure SNMP for this server only.

    3.

  3. Select Node Name for SNMP and press Enter .

    4.

  4. Enter the name SNMP reports to the management client for this node, then press Esc .

    By convention, this is the IP hostname for the node. If the node does not have an IP hostname, we recommend that you use the NetWare® file server name for this node.

    5.

  5. Select Hardware Description and press Enter .

    6.

  6. Enter the hardware description for this node, then press Esc .

    The hardware description can include the CPU type; bus speed; size of memory; and size and type of disks, printers, tape drives, and so on. This description, combined with the information about the software taken from the system, makes up the SNMP system description.

    7.

  7. Select Physical Location and press Enter .

    8.

  8. Enter the location description for this node, then press Esc .

    9.

  9. Select Human Contact and press Enter .

    10.

  10. Enter the contact information for the person (or persons) responsible for this node, then press Esc .

    The contact information should include phone numbers and mailing addresses.

    11.

  11. When you are finished, press Esc ; if prompted, select Yes to save the changes to the SNMP parameters, then press Enter .

    The Manage Configuration menu is displayed.

    12.

  12. Select another option from the Manage Configuration menu to continue, or press Esc to return to the Internetworking Configuration menu.

    13.

Export Configuration

To move configuration files among network servers, NIASCFG provides an option to export files to diskette or a specified server destination. Exported routing configuration files can be used as a set of preconfigured files for product installation on another system, product reinstallation on this system, or as a routing configuration backup. To copy files to a remote destination, remote server access and adequate disk space are required.

To create and transfer a routing configuration file set to a specified server volume, complete the following steps:

  1. From the Internetworking Configuration menu, select Manage Configuration .

    The Manage Configuration menu is displayed.

    2.

  2. From the Manage Configuration menu, select Export Configuration .

    The Configuration Export window is displayed.

    3.

  3. Indicate the export destination by specifying a DOS device or NetWare volume.

    4.

  4. Select Export Entire Server Configuration and press Enter . Select Yes and press Enter to export the entire server configuration.

    You can select No and specify a partial export by selecting from the X.25 Profiles, Call Destinations, or PPP Authentication Files menu options. Not all files are exported for some configurations.

    NOTE:  If you export an entire server configuration, information specific to that server is exported (for example, IPX addresses). This information must be modified when imported to another server.

    5.

  5. Select Export to copy the routing configuration files to the specified destination.

    The exported routing configuration file can be used during installation as a preconfigured file set or it can be imported, as explained in the section that follows.

    6.

Import Configuration

To move routing configuration files among network servers, NIASCFG provides an option to import files from diskette or a NetWare volume. To copy routing configuration files from a remote destination, remote server access and adequate disk space are required. The Import Configuration option backs up the original routing configuration before transferring new files.

To import a routing configuration file set, complete the following steps:

  1. From the Internetworking Configuration menu, select Manage Configuration .

    The Manage Configuration menu is displayed.

    2.

  2. From the Manage Configuration menu, select Import Configuration .

    The Configuration Import window is displayed.

    3.

  3. Specify the location of the files to be imported.

    NOTE:  If you import an entire server configuration, use NIASCFG to modify information specific to this server (for example, IPX addresses).

    4.

  4. Select Import and press Enter to copy routing configuration files from the specified source.

    The original routing configuration is backed up to the SYS:\ETC.BAK directory. This configuration can be restored using the Import Configuration option and specifying SYS:\ETC.BAK as the source.

    5.

Configuring Server Access

To configure a server for RCONSOLE access, complete the following steps:

  1. From the Internetworking Configuration menu, select Manage Configuration .

    The Manage Configuration menu is displayed.

    2.

  2. From the Manage Configuration menu, select Configure Remote Console Access To This Server .

    The Configure Remote Console Access To This Server window is displayed.

    3.

  3. Configure the remote parameters as described below.

    Option Description

    Remote Console Access

    Enables RCONSOLE access to this server. This option must be enabled to provide access to any of the other options listed in this table.

    Password

    Enter a password to secure remote communications. When enabled, this node requires the password of any user accessing this node through RCONSOLE, ACONSOLE, or XCONSOLE.

    RCONSOLE Connection (SPXTM)

    Enables remote console access to this node through RCONSOLE.

    RCONSOLE allows access to the file server console from a workstation.

    ACONSOLE Connection (ASYNC)

    Enables remote console access to this node through ACONSOLE or RCONSOLE Async (4.x RCONSOLE).

    COM Port Baud Rate

    ACONSOLE allows access to the file server console through a modem. When you enable this option, you also need to specify the communications port and baud rate used by the system.

    Expert Modem Setup

    You might also have to set up special commands for modems that do not respond to the standard modem AT command set through the Expert Modem Setup option.

    TELNET Connection

    Enables remote administration from a remote workstation running an X Window System* interface or a remote workstation that has VT100* or VT220* terminal emulation.

    Maximum Sessions

    When you enable the TELNET connection, you also need to specify the maximum number of concurrent TELNET sessions you want this node to support.

    Timeout

    Specifies an interval for the ASCII Esc key to take effect.

  4. When you are finished, press Esc . If prompted, select Yes to save the changes to the remote server access configuration, then press Enter .

    5.

  5. Press Esc to return to the Internetworking Configuration menu.

    6.

Edit AUTOEXEC.NCF

This option displays the View or Edit AUTOEXEC.NCF window, which contains the AUTOEXEC.NCF file.

As stated in this file, the LOAD and BIND commands are contained in the NETINFO.CFG file.



  Previous Page: Dynamic Reconfiguration  Next Page: Managing