Cyclades AlterPath BladeManager Instrukcja Obsługi Strona 179

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 240
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 178
165
Appendices
Appendix A: Troubleshooting
Port Mapping Fails When Using DirectCommand
This section describes some considerations that may apply if port mapping fails when a user
attempts DirectCommand access to a target device.
If DirectCommand is invoked by an unprivileged user (such as a regular user on a UNIX
-based
system), DirectCommand may not be able to open privileged TCP ports (numbered below 1024).
DirectCommand attempts to open the port by adding an offset to any requested port number that is
less than 1024 and by automatically modifying the URL to represent the new local port. However,
if the service provided by a target device can operate only on the original predetermined TCP port,
DirectConnect does not work properly and displays a descriptive warning. If this occurs,
DirectConnect connections may be made to the target device only by workstation administrators.
Another possible cause for failed port mapping by Direct Command is that the user’s workstation
may be running an application that uses a TCP port that is needed by DirectCommand. For
example, if the user’s workstation is running a web server on port 80 and the target device being
accessed through DirectCommand expects port 80 to be mapped, DirectCommand might not work.
To prevent this kind of conflict, make sure that local applications running on the user’s workstation
do not use the same TCP port numbers used by DirectCommand.
Network failure
This section summarizes the options for connecting to the MergePoint 5224/5240 SP manager for
troubleshooting in the event of an IP network failure.
Remote administrators can connect to the SP manager in case of network failure in any of the
following ways:
By bringing up the Web Manager or logging into the console over PPP after establishing a
dial
-in or callback connection to either of the following modem types :
An external modem optionally connected to the SP manager.
A modem on a PC modem card optionally installed in the SP manager
By logging into the console after establishing a dial
-in connection from a terminal emulation
program to an external modem optionally connected to the SP manager.
Local administrators can connect to the SP manager by logging into the Linux command line
through a terminal or workstation that is connected to the console port.
All of these connection methods must be previously configured as described elsewhere in this
manual. For example, to make it possible to dial in if the network connection becomes unavailable,
a modem must be installed and configured. Connecting to the console requires a terminal or a
APPENDICES
Przeglądanie stron 178
1 2 ... 174 175 176 177 178 179 180 181 182 183 184 ... 239 240

Komentarze do niniejszej Instrukcji

Brak uwag