http://www.cisco.com/univercd/home/home.htm


DOC-785315=
DOC-1600-HIG=






cisco.partnerelearning.com


contact2.cisco.com

http://ciscoinanutshell.com/cisco.html

cisco press.com CCNA Exam #640-507 Cert

ISBN 0735709718

12.2.18S5
emkdni


Select to find common software releases	Product Family	Compatible Hardware Product Number(s)	Minimum Supported Software Release(s) per release train	
	7500	PA-A3-OC12-MM=	12.0(11)S, 12.1(3)E, 12.2(7)T, 12.2(14)S, 12.3(1)


The ip tftp source interface command makes shore that the source address vor tftp is the ip adres of the just mengoned command.

Inuyasha(config)#ip tcp path-mtu-discovery
Inuyasha(config)#exit
Inuyasha#sh ip bgp nei | include max data
Datagrams (max data segment is 536 bytes):
Datagrams (max data segment is 4430 bytes):
Datagrams (max data segment is 4430 bytes):
Datagrams (max data segment is 1460 bytes):
Inuyasha#

----

Subject: Re: banner-exec vs exec-banner vs banner incoming
Hi Tim,
In that case, this is what i found in Doc CD
"When a user connects to the router, the message-of-the-day (MOTD) banner
(if configured) appears first, before the login prompt. After the user
successfully logs in to the router, the EXEC banner or incoming banner will
be displayed, depending on the type of connection. For a reverse Telnet
login, the incoming banner will be displayed. For all other connections, the
router will display the EXEC banner. "

I don't know but well i think it's quite clear, at least for me.
if you use banner exec (configued on router itself), the banner appears
anytime you telnet directly to router.
and for banner incoming, it just show up if you configured on access server
and try to make a reverse telnet to router.

----


The SNMP-SERVER  HOST  command specifies which hosts will receive SNMP
notifications, and whether you want the notifications sent as traps or
inform requests.

The SNMP-SERVER ENABLE TRAPS command globally enables the production
mechanism for the specified notification types (such as Border Gateway
Protocol [BGP] traps, config traps, entity traps, Hot Standby Router
Protocol [HSRP] traps, and so on).


-----

In the future you can test for a space by using the below method:

Router(config-if)#ip os message-digest-key 2 md5 CISCO2 <-space
Router(config-if)#^Z
Router#sho run | include CISCO2$
Router#sho run | include CISCO2 $
ip ospf message-digest-key 2 md5 CISCO2
Router#

As you can see the regular expression was able to detect the space at
the end of the password.

----

int e0/0
ip access-group 101 in
access-list 101 permit tcp any any eq telnet established

AND

int e0/0
ip access-group inbound in
ip access-group outbound out

access-l extended inbound
 permit tcp any any eq telnet
 evaluate  myreflect

access-l extended outbound
 permit tcp any any reflect myreflect

----

<Quote>
If summary route is announced to BB router, there is no way to find if
it
work or not.
</Quote>

It would actually be really easy to test.  Just create a loopback
interface (or use an existing interface) that has an IP address in part
of the summarized range and then ping the BB router sourcing the ping
off of the loopback (or existing interface).  If you get a reply to the
ping, you will know that the BB is receiving the summarized route.

----