A.2 Troubleshooting Linux Access Gateway Installation

This section contains the following troubleshooting scenarios for Linux Access Gateway:

A.2.1 Some of the New Hardware Driver or Network Card are Not Detected During Manual or Advanced Installation

Sometimes, the advanced or manual installation of the Linux Access Gateway might fail if some of the hardware drivers or network cards are not detected. If this happens, you must upgrade the hardware drivers manually as follows:

  1. Start the Manual installation of the Linux Access Gateway. See Section 5.0, Installing the Linux Access Gateway.

  2. Select Kernel Module (Hardware Driver) in the Main Menu, then click OK.

  3. Select Add Driver Update, then click OK.

  4. Select the Driver Update Medium. The driver update medium can be CD-ROM or floppy disk. Click OK. The hardware driver is updated.

  5. Continue with the Linux Access Gateway installation.

A.2.2 Manually Configuring a Network Interface

If you have configured a network interface during installation and it is not showing up, you can configure it manually through the command line interface (CLI) interface.

NOTE:If Linux Access Gateway is not imported, modifications to the Linux Access Gateway configuration should be done using nash. If the Linux Access Gateway is already imported, any modifications to the configuration should be done using the Administration Console.

Before you begin, make sure you have done the following:

  • You have rebooted the system after installation.

  • You have logged in as root.

  1. At the command prompt, enter the following command:

    nash

  2. At the nash shell prompt, run the following command to enter the configuration mode:

    configure .current

  3. To display the current IP address for the eth0 network card, enter the following:

    show interface eth0

  4. To change the IP address of eth0, enter the following:

    interface eth0

  5. To replace the IP address of eth0, enter the following command:

    replace <current IP address> with <IP address/netmask>

    Replace <IP address/netmask> with the IP address of the network interface card and the subnet mask. For example:

    replace 10.0.0.1 with 12.1.1.1/23

    IMPORTANT:Do not use the interface eth0 no <ip_address> command to remove the IP address. Always use the above command.

  6. To return to the configuration mode, enter the following command:

    exit

  7. To save the configuration, enter the following command:

    save .current

  8. For the configuration to take effect, enter the following command:

    apply

  9. To exit from the configuration mode, enter the following command:

    exit

  10. To exit from the nash shell, enter the following command:

    exit

A.2.3 Manually Setting and Deleting the Default Gateway

NOTE:If Linux Access Gateway is not imported, modifications to the Linux Access Gateway configuration should be done using nash. If the Linux Access Gateway is already imported, any modifications to the configuration should be done using the Administration Console.

  1. Log in as root.

  2. At the command prompt, enter the following shell command:

    nash

  3. At the nash shell prompt, run the following command to enter the configuration mode: configure .current

  4. To set up the default gateway IP address, enter the following command:

    ip route 0.0.0.0/0 <gateway_IP_address> 1

    Replace <gateway_IP_addres>s with the IP address of your gateway server.

  5. To delete the default gateway IP address, enter the following command:

    no ip route 0.0.0.0/0 <gateway_IP_address> 1

    Replace <gateway_IP_address> with the IP address of your gateway server.

  6. To save the configuration, enter the following command:

    save .current

  7. For the configuration to take effect, enter the following command:

    apply

  8. To exit from the configuration mode, enter the following command:

    exit

  9. To exit from the nash shell, enter the following command:

    exit

A.2.4 Manually Configuring the Hostname, Domain Name and DNS Server

  1. At the command prompt, enter the following shell command:

    nash

  2. At the nash shell prompt, run the following command to enter the configuration mode: configure .current

  3. Configure the domain name and hostname.

    1. To set up the domain name, enter the following command:

      ip domain-name < domain_name>

      Replace <domain_name> with the domain name for this network interface card.

    2. To set up the hostname, enter the following command:

      hostname < host_name>

      Replace <host_name> with the hostname of the Linux Access Gateway machine.

    3. If the hostname is not resolvable using an external DNS server, do the following to add the hostname and IP address mapping:

      hosts <ip-address><host_name>

      hosts ip-address host-name.domainname

      Replace <ip_address> with the IP address of this Access Gateway machine. Replace <host_name> with the computer name for this Access Gateway machine.

    4. To set up the DNS server, enter the following command:

      ip name-server <DNS_IP_address>

      Replace <DNS_IP_address> with the IP address of your DNS server.

  4. To save the configuration, enter the following command:

    save .current

  5. For the configuration to take effect, enter the following command:

    apply

  6. To exit from the configuration mode, enter the following command:

    exit

  7. To exit from the nash shell, enter the following command:

    exit

  8. You must exit from the bash shell for configuration changes to hostname, domain name and DNS server to take effect. To exit from the bash shell, enter the following command:

    exit

  9. Enter the following command to log in again:

    root

  10. To manually import the Linux Access Gateway to the Administration Console, enter the following command from the bash prompt:

    /chroot/lag/opt/novell/bin/lagconfigure.sh

A.2.5 Troubleshooting Import Failure

There are several reasons for auto-import failure. The following sections list the causes and workarounds:

Manually Importing the Device to Administration Console

If the Linux Access Gateway failed to import during installation, follow the steps given below:

  1. Log in as root.

  2. Configure the network interface. For information on configuring the network interface, see Section A.2.2, Manually Configuring a Network Interface.

  3. Configure the domain name and hostname. For information on configuring the hostname and domain name, see Section A.2.4, Manually Configuring the Hostname, Domain Name and DNS Server.

  4. Configure the default gateway. For information on configuring the default gateway, see Section A.2.3, Manually Setting and Deleting the Default Gateway.

Hostname Is Not Configured Properly

If you have not configured the hostname properly, the following error messages are displayed:

  • Hostname is not set. Please set the hostname in nash and run /chroot/lag/opt/novell/bin/lagconfigure.sh to trigger the configuration steps again.

  • Default Hostname set. Please set the hostname in nash and run /chroot/lag/opt/novell/bin/lagconfigure.sh to trigger the configuration steps again.

To resolve the problem, manually configure the hostname. For information on how to manually configure hostname, see Section A.2.4, Manually Configuring the Hostname, Domain Name and DNS Server.

Hostname Is Not Resolvable

When hostname is not resolvable, the following error message is displayed:

Hostname cannot be resolved. Please set host entry in nash and run /chroot/lag/opt/novell/bin/lagconfigure.sh to trigger the configuration steps again.

To resolve the problem, manually configure the hostname. For information on how to manually configure hostname, see Section A.2.4, Manually Configuring the Hostname, Domain Name and DNS Server.

Some of the Components Failed to Install

  1. Check the install logs at the following location:

    /tmp/novell_access_manager

    This directory has the install logs in the following format:

    inst_component-name_date_time.log

    For more information on collecting logs, see Linux Access Gateway Logs in the Novell Access Manager 3.0 SP4 Administration Guide.

  2. Send the log to Novell Support.