From: Chris Lewis (chrlewiscsco@yahoo.com)
Date: Thu Nov 10 2005 - 19:54:31 GMT-3
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