Mailing List Archive

Check your DNS-settings. Most problems I have encountered with slow telnet/ssh sessions were the cause of an unresponisve / unreachable DNS..

Hope this helps..

Nils Kolstein
Senior Netwerkbeheerder
KPN Planet Technologies
Tel: 030-6588284
Fax: 033-4513101
E-mail: n.kolstein@planettechnologies.nl


-----Original Message-----
From: Michael Feng [mailto:wsf@vodatelsys.com]
Sent: Monday, May 26, 2003 10:24 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] slow telnet session


juniper-nsp?

what is the reason of slow telnet session?

When I try telnet M5, it took so long to come out the
login windows, what is the reason?
??

???????

?????? Michael Feng
wsf@vodatelsys.com

?????????? ? 2003-05-26
??????????????

Nils Kolstein£¬ÄúºÃ£¡

It didn't set domain name service on M5.
So, I am still not understood, you mean it is northing related with
M5?

What should I do? pls feel free to guide me.

Thanks in advance.

======== 2003-05-26 10:30:00 ÄúÔÚÀ´ÐÅÖÐдµÀ£º ========

Check your DNS-settings. Most problems I have encountered with slow telnet/ssh sessions were the cause of an unresponisve / unreachable DNS..

Hope this helps..

Nils Kolstein
Senior Netwerkbeheerder
KPN Planet Technologies
Tel: 030-6588284
Fax: 033-4513101
E-mail: n.kolstein@planettechnologies.nl


-----Original Message-----
From: Michael Feng [mailto:wsf@vodatelsys.com]
Sent: Monday, May 26, 2003 10:24 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] slow telnet session


juniper-nsp$B!$(J

what is the reason of slow telnet session?

When I try telnet M5, it took so long to come out the
login windows, what is the reason?
$B!!!!(J

$B!!!!!!!!!!!!!!(J

$B!!!!!!!!!!!!(J Michael Feng
wsf@vodatelsys.com

$B!!!!!!!!!!!!!!!!!!!!(J $B!!(J 2003-05-26
$B!!!!!!!!!!!!!!!!!!!!!!!!!!!!(J
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp

= = = = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Michael Feng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wsf@vodatelsys.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-05-26
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030526/9c3fa023/attachment.htm

I think what Nils was referring to was your external DNS servers. Are
you trying to telnet to the M5 by name? If so, then like Nils
suggested, check your external DNS server to make sure that they are
correctly set up and configured. I to have also encountered these
issues before but they were also related to my external DNS servers not
the M5. Hope this helps.


Mario

-----Original Message-----
From: juniper-nsp-bounces@puck.nether.net
[mailto:juniper-nsp-bounces@puck.nether.net] On Behalf Of Michael Feng
Sent: Monday, May 26, 2003 8:46 AM
To: Nils Kolstein; juniper-nsp@puck.nether.net
Subject: Re: RE: [j-nsp] slow telnet session


Nils Kolstein£¬ÄúºÃ£¡

It didn't set domain name service on M5.
So, I am still not understood, you mean it is northing related with
M5?

What should I do? pls feel free to guide me.

Thanks in advance.

======== 2003-05-26 10:30:00 ÄúÔÚÀ´ÐÅÖÐдµÀ£º ========




Check your DNS-settings. Most problems I have encountered with slow
telnet/ssh sessions were the cause of an unresponisve / unreachable
DNS..

Hope this helps..

Nils Kolstein
Senior Netwerkbeheerder
KPN Planet Technologies
Tel: 030-6588284
Fax: 033-4513101
E-mail: n.kolstein@planettechnologies.nl


-----Original Message-----
From: Michael Feng [mailto:wsf@vodatelsys.com]
Sent: Monday, May 26, 2003 10:24 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] slow telnet session


juniper-nsp$B!$(J

what is the reason of slow telnet session?

When I try telnet M5, it took so long to come out the
login windows, what is the reason?
$B!!!!(J

$B!!!!!!!!!!!!!!(J

$B!!!!!!!!!!!!(J Michael Feng
wsf@vodatelsys.com

$B!!!!!!!!!!!!!!!!!!!!(J $B!!(J 2003-05-26
$B!!!!!!!!!!!!!!!!!!!!!!!!!!!!(J
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp

= = = = = = = = = = = = = = = = = = = = = =

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡


¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Michael Feng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wsf@vodatelsys.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-05-26


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030526/cea659cb/attachment.htm

Junoguy£¬ÄúºÃ£¡

Actually I telnet to the M5 by ip address, not by name.
You still suggest to check external DNS server?

======== 2003-05-26 16:22:00 ÄúÔÚÀ´ÐÅÖÐдµÀ£º ========

I think what Nils was referring to was your external DNS servers. Are you trying to telnet to the M5 by name? If so, then like Nils suggested, check your external DNS server to make sure that they are correctly set up and configured. I to have also encountered these issues before but they were also related to my external DNS servers not the M5. Hope this helps.


Mario
-----Original Message-----
From: juniper-nsp-bounces@puck.nether.net [mailto:juniper-nsp-bounces@puck.nether.net] On Behalf Of Michael Feng
Sent: Monday, May 26, 2003 8:46 AM
To: Nils Kolstein; juniper-nsp@puck.nether.net
Subject: Re: RE: [j-nsp] slow telnet session


Nils Kolstein£¬ÄúºÃ£¡

It didn't set domain name service on M5.
So, I am still not understood, you mean it is northing related with
M5?

What should I do? pls feel free to guide me.

Thanks in advance.

======== 2003-05-26 10:30:00 ÄúÔÚÀ´ÐÅÖÐдµÀ£º ========

Check your DNS-settings. Most problems I have encountered with slow telnet/ssh sessions were the cause of an unresponisve / unreachable DNS..

Hope this helps..

Nils Kolstein
Senior Netwerkbeheerder
KPN Planet Technologies
Tel: 030-6588284
Fax: 033-4513101
E-mail: n.kolstein@planettechnologies.nl


-----Original Message-----
From: Michael Feng [mailto:wsf@vodatelsys.com]
Sent: Monday, May 26, 2003 10:24 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] slow telnet session


juniper-nsp$B!$(J

what is the reason of slow telnet session?

When I try telnet M5, it took so long to come out the
login windows, what is the reason?
$B!!!!(J

$B!!!!!!!!!!!!!!(J

$B!!!!!!!!!!!!(J Michael Feng
wsf@vodatelsys.com

$B!!!!!!!!!!!!!!!!!!!!(J $B!!(J 2003-05-26
$B!!!!!!!!!!!!!!!!!!!!!!!!!!!!(J
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp

= = = = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Michael Feng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wsf@vodatelsys.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-05-26


= = = = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Michael Feng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wsf@vodatelsys.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-05-27
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030527/e5920a28/attachment.htm

Hi Michael,

I think the slow telnet/ssh session is caused by,
1. your source ip (the PC, say ip#1) did not have name.
2. the dns server that serves the ip#1 did not seted properly.

When you telnet to router from the PC (ip#1), the router try
to resolves the ip#1 to name by querys the DNS server.

So, you can do one of these,
1. delete name-server setting by
[edit system]
delete name-server
delete domain-name
delete domain-search
then your router will not try to resolves ip to name.
also, you have to use ip instead of name when you
run the traceroute/ping... on router.
2. try to fix the dns server problem :p :p


Hope these help

BR,
Yu-lin Chang
Academia Sinica Computing Center, Taiwan.
--

----- Original Message -----
From: Michael Feng
To: Junoguy ; juniper-nsp@puck.nether.net
Sent: Tuesday, May 27, 2003 8:27 AM
Subject: Re: RE: RE: [j-nsp] slow telnet session

Junoguy

Actually I telnet to the M5 by ip address, not by name.
You still suggest to check external DNS server?

======== 2003-05-26 16:22:00 ========

I think what Nils was referring to was your external DNS servers.
Are you trying to telnet to the M5 by name?
If so, then like Nils suggested, check your external DNS s
erver to make sure that they are correctly set up and configured.
I to have also encountered these issues before but they were also
related to my external DNS servers not the M5. Hope this helps.


Mario

On Tue, May 27, 2003 at 08:27:51AM +0800, Michael Feng wrote:
> Actually I telnet to the M5 by ip address, not by name.
> You still suggest to check external DNS server?

What is the processor utilization? Is the router doing a large
amount of processing (e.g. rate limiting)? It may be busy doing
other things.

John

Got to be revesre lookup issue

> -----Original Message-----
> From: juniper-nsp-bounces@puck.nether.net
> [mailto:juniper-nsp-bounces@puck.nether.net] On Behalf Of
> John Kristoff
> Sent: 27 May 2003 12:53
> To: juniper-nsp@puck.nether.net
> Subject: Re: RE: RE: [j-nsp] slow telnet session
>
>
> On Tue, May 27, 2003 at 08:27:51AM +0800, Michael Feng wrote:
> > Actually I telnet to the M5 by ip address, not by name.
> > You still suggest to check external DNS server?
>
> What is the processor utilization? Is the router doing a
> large amount of processing (e.g. rate limiting)? It may be
> busy doing other things.
>
> John
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
>
>

John Kristoff£¬

Yes, rate limiting is used in that router.
How to check processor utilization?

Michael

======== 2003-05-27 06:52:00 ÄúÔÚÀ´ÐÅÖÐдµÀ£º ========

On Tue, May 27, 2003 at 08:27:51AM +0800, Michael Feng wrote:
>> Actually I telnet to the M5 by ip address, not by name.
>> You still suggest to check external DNS server?

What is the processor utilization? Is the router doing a large
amount of processing (e.g. rate limiting)? It may be busy doing
other things.

John

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp

= = = = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Michael Feng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wsf@vodatelsys.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-05-27
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030527/ae6215f0/attachment.htm

Farhan Memon£¬
Pls Tell me how to check it


¡¡¡¡

======== 2003-05-27 12:56:00 ÄúÔÚÀ´ÐÅÖÐдµÀ£º ========

Got to be revesre lookup issue

>> -----Original Message-----
>> From: juniper-nsp-bounces@puck.nether.net
>> [mailto:juniper-nsp-bounces@puck.nether.net] On Behalf Of
>> John Kristoff
>> Sent: 27 May 2003 12:53
>> To: juniper-nsp@puck.nether.net
>> Subject: Re: RE: RE: [j-nsp] slow telnet session
>>
>>
>> On Tue, May 27, 2003 at 08:27:51AM +0800, Michael Feng wrote:
>> > Actually I telnet to the M5 by ip address, not by name.
>> > You still suggest to check external DNS server?
>>
>> What is the processor utilization? Is the router doing a
>> large amount of processing (e.g. rate limiting)? It may be
>> busy doing other things.
>>
>> John
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
>>
>>

_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp

= = = = = = = = = = = = = = = = = = = = = =
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡ÖÂ
Àñ£¡

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Michael Feng
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡wsf@vodatelsys.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2003-05-27
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030527/4da10c3a/attachment.htm

On Tue, May 27, 2003 at 06:52:55AM -0500, John Kristoff wrote:
| On Tue, May 27, 2003 at 08:27:51AM +0800, Michael Feng wrote:
| > Actually I telnet to the M5 by ip address, not by name.
| > You still suggest to check external DNS server?
|
| What is the processor utilization? Is the router doing a large
| amount of processing (e.g. rate limiting)? It may be busy doing
| other things.

hardware based routers have the advantage that processing of packets
i.e. forwarding/rate-limiting etc. does not harm the control-plane CPU;

router health metrics like you may know from other router vendors
equipment may not be relevant in a hardare based router;

/hannes

I seemed to have missed this reply.

On Wed, 28 May 2003 16:59:48 +0100
"Farhan Memon" <faz@netfm.co.uk> wrote:

> > On Tue, May 27, 2003 at 06:52:55AM -0500, John Kristoff wrote:
> > | On Tue, May 27, 2003 at 08:27:51AM +0800, Michael Feng wrote:
> > | > Actually I telnet to the M5 by ip address, not by name.
> > | > You still suggest to check external DNS server?
> > |
> > | What is the processor utilization? Is the router doing a
> > large amount
> > | of processing (e.g. rate limiting)? It may be busy doing other
> > | things.
> >
> > hardware based routers have the advantage that processing of
> > packets i.e. forwarding/rate-limiting etc. does not harm the
> > control-plane CPU;
> >
> > router health metrics like you may know from other router
> > vendors equipment may not be relevant in a hardare based router;

However, I have noticed some initial slowdown in the login process. For
example, when large amounts of UDP traffic arrive on a gig interface
(say 100 Mb/s or more) and its rate-limited on ingress to something much
less (say about 10 Mb/s), the processor goes to about 50% and stays
there until the traffic subsides to somewhere below the rate limit
threshold.

Once logged in, response time is fine, but in my experience the initial
connection lag is noticeable.

Note: I do appreciate that this is still much better than a leading
competitor's survivability.

John

On Wed, May 28, 2003 at 11:09:04AM -0500, John Kristoff wrote:

> However, I have noticed some initial slowdown in the login process.
> For example, when large amounts of UDP traffic arrive on a gig
> interface (say 100 Mb/s or more) and its rate-limited on ingress to
> something much less (say about 10 Mb/s), the processor goes to about
> 50% and stays there until the traffic subsides to somewhere below the
> rate limit threshold.
>
> Once logged in, response time is fine, but in my experience the
> initial connection lag is noticeable.

If your DNS response traffic come in over the same interface, and you
rate limit all UDP traffic, you will drop 9 out of 10 DNS response
packets, which will obviously delay your login, as it waits for a DNS
response.

/Jesper

--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.

On Wed, 28 May 2003 18:23:13 +0200
Jesper Skriver <jesper@skriver.dk> wrote:

> If your DNS response traffic come in over the same interface, and you
> rate limit all UDP traffic, you will drop 9 out of 10 DNS response
> packets, which will obviously delay your login, as it waits for a DNS
> response.

Doh! That is exactly what I've seen and didn't even think about DNS
traffic flowing over that interface. Thanks for pointing out the
obvious. :-)

John