Unknown ip address, Dhcp/bootp problems, Callback problems – Perle Systems IOLAN SCS User Manual

Page 397: Language problems

Advertising
background image

Troubleshooting 397

Unknown IP Address

Unknown IP Address

You have already configured the IOLAN and you do know your password, and have lost,
misconfigured, or don't know the IP address of the IOLAN, so you cannot obtain a successful
login.

z

If the IOLAN resides within the local network segment, you can use DeviceManager to find the
IOLAN.

z

You can connect directly to the serial port of the IOLAN, as explained in

Using a Direct Serial

Connection to Specify an IP Address on page 67

.

DHCP/BOOTP Problems

Messages:

host name too long

or

filename too long.

z

The IOLAN can only accept host names of 14 characters or file names of 64 characters, so verify
that you are not attempting to pass a string that is longer than those maximums.

DHCP or BOOTP have been set up to configure my IOLAN, but does not seem to have done
anything.

z

Check that the server DHCP/BOOTP service is set to on, if not set it to on and reboot.

z

Check that your BOOTP server is configured for your IOLAN or that your DHCP server has an
active lease pool (scope) with at least 1 free IP address.

You observe TFTP errors when the IOLAN boots, for example:

TFTP: File not found : filename

TFTP: Timed out

This has a number of causes, including:

z

The file names you specified to DHCP/BOOTP do not exist or are in the wrong place.

z

The server for any of the downloadable files in your bootfile has no TFTP server running.

z

Verify that lease data in your DHCP server manager is correct.

z

Reset or restart the DHCP server.

Callback Problems

User Callback

is

On

, and a number is configured for the line, but the IOLAN is not calling the

user back:

z

Verify that the phone number is entered under the user (not the line).

z

Verify that the callback

Phone Number

is valid.

z

Verify that the modem at the user’s end is set to ‘auto-answer’.

Language Problems

In a customized language, the text strings appear in the wrong place in the Menu, CLI, or
WebManager.

z

Check the original ASCII text file you used to translate to your customised language. The
sequence of the line much match exactly (be aware that comments don’t affect line sequence, but
can affect the actual line that the strings appear on). So, if you strip out all comments, if the
original file says line 1000 should be string

none

, then line 1000 (stripped of comments) should

be the translated version of

none

.

Advertising