Filter
Top Products
Black Box Console Server user guide 252
Introduction
This appendix contains solutions for problems that may arise while Console Server (the
‘unit’).
- if you bought your unit from a registered Black Box Supplier, you must contact
their Technical Support department; they are qualified to deal with your problem.
- if you are a registered Black Box Supplier, and bought your unit from Black Box,
please contact the Technical Support department of your nearest Black Box office.
The addresses and telephone numbers of your nearest Black Box office are shown
on the cover of this manual.
General communication matters
General communication checks and practices are as follows:
•ping your host; if you cannot ping at all, check the cabling between the unit and
your network. If you can ping but packet loss is reported, ping another host/
device on the same network. You will appreciate whether the problem is
specific to a host/device or general to the network. If there is a problem with
the network check the state of the network, including number of nodes.
•after entering or changing ip information for your unit (internet address,
broadcast address, subnet mask) reboot the unit (does not apply when using
BOOTP or DHCP). Once the unit has rebooted other network devices can
communicate with it (ping, telnet, etc.). Also, protocols such as ARP and
proxy-ARP will work properly
If you don’t reboot unit the ip information you have entered/changed will not
be recognised by other network devices.
•use the show routes command (command line only). See if there a route to the
host?
•implement load-balancing in your network by distributing the processing. For
example, try not to cluster on the unit devices which require high
throughput.
•ensure routes to/from your host are as direct as possible; e.g. ensure the unit is
on the same network as your host so that bridges/routers do not act as
bottlenecks.