From: Jason Edelman \(jaedelma\) (jaedelma@cisco.com)
Date: Sat Nov 12 2005 - 13:55:28 GMT-3
From a working config: refuse-message for VTY 5.
line vty 0 4
password cisco
login
line vty 5
password cisco
login
refuse-message ^C
Sorry, LINE 5 IS IN USE!!! (refuse-message)
^C
rotary 1
Output:
SWITCH1>telnet 10.1.20.2 3001
Trying 10.1.20.2, 3001 ... Open
Sorry, LINE 5 IS IN USE!!! (refuse-message)
[Connection to 10.1.20.2 closed by foreign host]
However, I could not get this to work without changing the port to 3001.
-Jason
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Ralph
Sent: Friday, November 11, 2005 11:59 AM
To: kevin@gannons.net
Cc: chrlewiscsco@yahoo.com; Dehong.Wang@motorola.com;
ccielab@groupstudy.com
Subject: refuse-message again!
Can we CONCLUSIVELY say that "refuse-message" works only with TTY lines,
while "busy-message" is for VTY lines.
Has anyone ever got refuse-message to work with VTY lines?
The documentation is obviously not clear on this; maybe a little clear
on busy-message, but not with refuse-message.
refuse-message works on my 2509 access-server, when all the lines are
currently open, and I try to connect again to any line, the
refuse-message is displayed.
here is a sample config and verification:
hostname ACCESS-SERVER
!
ip host r1 2001 1.1.1.1
ip host r2 2002 1.1.1.1
ip host r3 2003 1.1.1.1
ip host r4 2004 1.1.1.1
ip host r5 2005 1.1.1.1
ip host r6 2006 1.1.1.1
ip host SW1 2007 1.1.1.1
ip host SW2 2008 1.1.1.1
!
!
line 1 8
refuse-message ^C
This Line is currently in use, Please try again later.
^C
no exec
transport input all
!
!
ACCESS-SERVER# sh line
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns
Int
0 CTY - - - - - 0 0 0/0
-
* 1 TTY 9600/9600 - - - - - 1 15 0/0
-
* 2 TTY 9600/9600 - - - - - 1 32 0/0
-
* 3 TTY 9600/9600 - - - - - 1 0 0/0
-
* 4 TTY 9600/9600 - - - - - 1 22 0/0
-
* 5 TTY 9600/9600 - - - - - 1 40 0/0
-
* 6 TTY 9600/9600 - - - - - 1 1 0/0
-
* 7 TTY 9600/9600 - - - - - 1 13 0/0
-
* 8 TTY 9600/9600 - - - - - 1 10 0/0
-
9 AUX 9600/9600 - - - - - 0 0 0/0
-
* 10 VTY - - - - - 11 0 0/0
-
!
!
ACCESS-SERVER#r1
Translating "r1"
This Line is currently in use, Please try again later.
ACCESS-SERVER#
I agree with Kevin that if all the vty lines are in use in the first
place, how then will the refuse-message get to the other router!
Is this a documentation bug or we just have to learn to read between the
lines!
Regards
Ralph.
-----Original Message-----
From: kevin gannon <kevin@gannons.net>
To: Chris Lewis <chrlewiscsco@yahoo.com>
Date: Fri, 11 Nov 2005 07:53:58 +0000
Subject: Re: Testing refuse-message
Sorry read what I wanted from your post. The refuse-message
seems to be for reverse telnet sessions try the below
! line aux is line 65
line aux 0
transport all in
line aux 0
refuse-message ^C
TEST
Now telnet to 2065 locally and you will get the AUX port now try it
again and you will get the refuse-message.
The reason I think it can not work for VTYs is that the message is
generated by the TCP rst being sent from the router as it has no
more sockets free.
Thanks & Regards
Kevin
On 11/10/05, Chris Lewis <chrlewiscsco@yahoo.com> wrote:
> Not quite Dehong,
>
> What you are describing is busy-message
>
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
ffun_c/ffcprt1/fcf004.htm#1001212
>
> That is simple to setup and works nicely.
>
> The setup I'm testing is R1 directly connected to R2, R2 is configured
with the refuse-message. When R2's VTY lines are full I try to telnet
from R1 to R2 and I get the standard message. I get the same result if I
put the refuse mesage on R1.
>
> I would really like to hear from anyone that has actually got this
working.
>
> Chris
>
> Wang Dehong-DWANG1 <Dehong.Wang@motorola.com> wrote:
> Here is the way I understand the refuse message. It is a message that
> router itself fails to access the a particular router and displays on
> itself. Here is the way to set it up if you have router R1 and R3.
>
> R1 <----------- > R3
>
> On R1 you set a
> ip host R3 < ip address>
> Line vty 0 4
> Refuse-message
>
> Then try to telnet R3 use "telnet R3", if it fails, you should see a
> refuse-message.
>
> - Dehong
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Chris Lewis
> Sent: Thursday, November 10, 2005 2:41 PM
> To: ccielab@groupstudy.com
> Subject: Testing refuse-message
>
> Hi,
>
> Configuring the refuse message is pretty trivial, as per below:
>
> Router1(config)#line vty 0 4
> Router1(config-line)#refuse-message "
> Enter TEXT message. End with the character '"'.
> Try back in 10 minutes
> "
>
> However I seem to be having difficulty testing this correctly to get
the
> refuse-mesage to show. Simply telneting to the router enough times
does
> not seem to work, I just get the standard connection refused message,
> and not the custom message I configured displayed. If anyone has
tested
> this and got the message displayed, please share the test methodology.
>
> Cheers
>
> Chris
>
>
> ---------------------------------
> Yahoo! FareChase - Search multiple travel sites in one click.
>
>
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3