Clavister SG4300 Series, Руководство по началу работы, Страница: 54 / 68

3.5. Troubleshooting Setup
This appendix deals with connection problems that might occur when connecting a management
workstation to a Clavister Security Gateway.
If the management interface does not respond after the Clavister Security Gateway has powered up
and CorePlus has started, there are a number of simple steps to troubleshoot basic connection
problems:
1. Check that the correct interface is being used.
The most obvious problem is that the wrong Clavister Security Gateway interface has been used for
the initial connection. Only the first interface found by CorePlus is activated for the initial
connection from a browser after CorePlus starts for the first time.
2. Check that interface characteristics match.
If a Clavister Security Gateway's interface characteristics are configured manually then the interface
on a switch to which it is connected should be configured with the same characteristics. For
instance, the link speeds and half/full duplex settings must match. If they don't, communication will
fail. This problem will not occur if the interfaces are set for automatic configuration on both sides
and automatic is always the Clavister factory default setting.
3. Check that the workstation IP is configured correctly.
The second most obvious problem is if the IP address of the workstation running the web browser is
not configured correctly.
4. Is the management interface properly connected?
Check the link indicator lights on the management interface. If they are dark then there may be a
cable problem.
5. Check the cable type connected to the management interface.
Is the management interface connected directly to the management workstation or another router or
host? In this case, an Ethernet "cross-over" cable may be needed for the connection, depending on
the capabilities of the interface.
6. Using the ifstat CLI command.
To investigate a connection problem further, connect the a console to the RS-232 port on the
Clavister Security Gateway after CorePlus starts. When you press the enter key, CorePlus should
respond with the a standard CLI prompt. Now enter the following command a number of times:
Device:/> ifstat <if-name>
Where <if-name> is the name of the management interface. This will display a number of counters
for that interface. The ifstat command on its own can list the names of all the interfaces.
If the Input counters in the hardware section of the output are not increasing then the error is likely
to be in the cabling. However, it may simply be that the packets are not getting to the Clavister
Security Gateway in the first place. This can be confirmed with a packet sniffer if it is available.
If the Input counters are increasing, the management interface may not be attached to the correct
physical network. There may also be a problem with the routing information in any connected hosts
or routers.
7. Using the arpsnoop CLI command.
A final diagnostic test is to try using the console command:
Device:/> arpsnoop -all
3.5. Troubleshooting Setup
Chapter 3. CorePlus Configuration
54