Month: April 2012

If we want to send previously prepared configs commands to Router via TFTP we can do this in very simple way and in this article we will se how to do it on Cisco and Juniper device.

CISCO

When we use TFTP to download configuration commands to the router, he is not making an echo of each command which reduces overall time consumption, CPU consumption and increases speed.

In this example, we will configure this router by making it receive the file named RConfig from the server at 20.20.1.1 by using the Trivial File Transfer Protocol – TFTP. The router will use the whole file received via TFTP before entering all the commands into the running configuration. This is particularly good because some commands in the configuration process could prevent your access to the router by locking you out or disconnecting you from the network, but the rest of the commands might fix the issue. If you enter the same configurations manually using telnet or “configure t”, you would simply lock yourself out of the router and not be able to continue with your work. A usual example of this issue happens when you change an active access-list. When you enter the first line, the router puts an implicit deny at the end, which will break your connection. Entering commands by using TFTP avoids any of this kind of problem.

The unique Gopher arrangements were taken as public in the year 1991 and you can view its depiction from the RFC 1436. This protocol was given the almost same name as of the sport’s team of Minnesota University, “Golden Gophers”.

The TCP/IP Application layer protocol “Gopher” was launched to share out, uncover, and to process documents online. Though initially, it was opened for communal as a smart option against WWW (World Wide Web) because of its menu documentation support, but in due course it remained completely futile to receive any popularity. The reason behind this infamy was that it offered some non maintainable, by the Web, features. According to one school of thought, the reason of this protocol’s collapse was its some degree of structure too and that was its non-flexibility especially when compared it to Hypertext Transfer Protocol or HTML, which is Gopher’s real competitor.

Administrative distance is the measure used by Cisco routers to help them decide how to select the best path when there’s more that one route to the same destination from different routing protocols. We can say that in this manner administrative distance shows the real reliability of a routing protocol in one system. It shows which routes are more important based on the routing protocol from which they derived. Each routing protocol is prioritized in order of most to least reliable using an administrative distance value. Don’t get confused, a lower numerical value is preferred. For example, an EIGRP with an administrative distance of 90 will be chosen over a RIP route with an administrative distance of 120 and over OSPF route with an administrative distance of 110 to.

Here is a table with all default administrative distances used by Cisco routers:

Routed Protocols vs. Routing Protocols
In this article we will cover the difference between Routed Protocols and Routing Protocols. This is one of the thing that can be asked of you if you are attending a job interview or if you are going to CCNA exam so, you must know the difference between a “routed” protocol and a “routing protocol” as one of the key concepts in the Routing world and networking world.

IMAP – Internet Message Access Protocol is a means of getting the right of entry to an e-mail. This code of behavior is also suitable for accessing the bulletin board posts which are held in reserve on a mail server and that is perhaps communal. Additionally, that commonly well known mailing IMAP protocol is an Application layer protocol which is used to grant permission to an e-mail client to get reach to the e-mail that resides over a far flung e-mail server.