Installation guide

AppleTalk Access Problems
5-4
Verify AppleTalk Address Is Within the Network Range
It is possible that the AppleTalk address is outside the network range. This situation can
occur momentarily while the access server is booting and is considered normal. However,
if this situation persists for more than a minute after initialization, then the problem could
be caused by one of the following reasons:
• All valid addresses in the network range are in use. To eliminate this problem, increase
the AppleTalk network range to make more addresses available, or if there are other
access servers on the network using AppleTalk, reduce their defined AppleTalk cache
size.
• A rogue AppleTalk router is advertising an incorrect network range. To eliminate this
problem, verify the network range advertised by all AppleTalk routers on the network.
Verify Cache Size Is Correct
The access server caches a number of AppleTalk addresses to be given to attached hosts at
connection time. This number is specified using the DEFINE APPLETALK CACHE
SIZE command. The dynamic cache size is shown in the SHOW APPLETALK STATUS
display.
The dynamic cache size is always less than or equal to the defined value and fluctuates as
connections are created or torn down. However, in the steady state, the two values should
match.
If the dynamic cache size gets too small, or reaches zero, host connection attempts could
fail. Therefore, a dynamic cache size that is persistently lower than the defined value is a
problem. The following are possible causes and solutions:
• Access server memory usage is too high so cache entries cannot be created. If this
occurs, the access server sets the Last Error field in the SHOW APPLETALK STATUS
display as follows:
Could not create AppleTalk cache entry, insufficient
resources
Verify the access server memory usage. See the section Verify Access Server Memory
Usage (page 2-6).