Cisco 1005-CH - 1005 Router - EN Instrukcja Użytkownika Strona 5

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 8
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 4
5
IPeXchange Caveats
IPeXchange Caveats
There are no caveats at this time.
Release 11.0(12)NA Caveats/Release 11.0(14)NA Modifications
The following caveats apply to Release 11.0(12)NA but were fixed in Release 11.0(14)NA:
Second Telnet session to VTY (virtual terminal) does not echo characters.
When a user connected to the router through more than one connection with Telnet or the
console, the second connection did not echo typed characters. The problem occurred when a
second Telnet session to the router was established, or from a console session with a second
Telnet session. [CSCdj05366]
Process thrashing in IPeXchange DNS process.
If a large amount of DNS traffic from IPX clients simultaneously accessed the Internet, the
IPeXchange Gateway displayed the following warning:
Feb 6 11:20:53 fake 13: 0:06:02dSCHED-3-THRASHING:
Process thrashing on watched queu=e 'UDP Socket' (count 1).
Feb 6 11:20:53 fake 14: -Process= "IpxIpGw Dns", ipl= 4, pid= 35
Feb 6 11:20:53 fake 15: -Traceback= 2091146 20913E4 221BE42
This could be seen by enabling the IPX IP gateway in the router and allowing a significant
number of clients to perform DNS queries at the same time. One situation could be many clients
using Netscape Navigator to access different sites at the same time.
The message that appeared was only a warning; the gateway continued to function normally.
[CSCdi90482]
ISDN Line activates without traffic present on LAN.
When clients accessed remote sites through the ISDN line, sometimes the client application was
left in a LASTACK state. This caused the application to retransmit and activate the ISDN line
endlessly. [CSCdi81940]
Name lookups were cached by the router, voiding DNS server rotation.
When a host was looked up and resolved by DNS, the router cached the response and used the
first IP address returned for future lookups. The correct behavior should be that a new lookup is
sent to the DNS every time so that IP address rotation by the DNS server takes effect.
This bug was closed without resolution. [CSCdi69675]
Przeglądanie stron 4
1 2 3 4 5 6 7 8

Komentarze do niniejszej Instrukcji

Brak uwag