Skip to main content

Host name resolution / Configuring host tables / Configuration backup and documentation

Host name resolution

3.2.6  This page will explain how Cisco IOS performs host name resolution.
Host name resolution is the process that a computer system uses to associate a host name with an IP address.
In order to use host names to communicate with other IP devices, network devices such as routers must be able to associate the host names with IP addresses. A list of host names and their associated IP addresses is called a host table.
A host table might include all devices in a network organization. Each unique IP address can have a host name associated with it. The Cisco IOS software maintains a cache of host name-to-address mappings for use by EXEC commands. This cache speeds up the process of converting names to addresses.
Host names, unlike DNS names, are significant only on the router on which they are configured. The host table will allow the network administrator to type either the host name such as Auckland or the IP address to Telnet to a remote host.
The next page will explain how host tables are configured.

Configuration host tables 

3.2.7  This page will teach students how to configure a host table.
To assign host names to addresses, first enter global configuration mode. Issue the command ip host followed by the name of the destination and all IP addresses where the device can be reached. This maps the host name to each of its interface IP addresses. To test connectivity to the host, use a telnet or ping command with the name of the router or an IP address that is associated with the router name.
The procedure to configure a host table is as follows:
  1. Enter global configuration mode.
  2. Enter the ip host command followed by the name of the router and all IP addresses associated with the router interfaces.
  3. Repeat Step 2 until all routers in the network are entered.
  4. Save the configuration to NVRAM.
In the Lab Activities, students will configure host tables that identify routers and interfaces.
The next page explains how configuration files should be managed.
Configuration backup and Documentation

3.2.8 This page will discuss the backup and documentation of configuration files. 
The configuration of network devices determines how the network will behave. Management of device configuration includes the following tasks:
  • List and compare configuration files on running devices.
  • Store configuration files on network servers.
  • Perform software installations and upgrades.
Configuration files should be stored as backup files in the event of a problem. Configuration files can be stored on a network server, on a TFTP server, or on a disk stored in a safe place. Include documentation with the offline information.

Comments

Post a Comment

Popular posts from this blog

Windowing

Windowing 11.1.5 This page will explain how windows are used to transmit data. Data packets must be delivered to the recipient in the same order in which they were transmitted to have a reliable, connection-oriented data transfer. The protocol fails if any data packets are lost, damaged, duplicated, or received in a different order. An easy solution is to have a recipient acknowledge the receipt of each packet before the next packet is sent. If a sender had to wait for an ACK after each packet was sent, throughput would be low. Therefore, most connection-oriented, reliable protocols allow multiple packets to be sent before an ACK is received. The time interval after the sender transmits a data packet and before the sender processes any ACKs is used to transmit more data. The number of data packets the sender can transmit before it receives an ACK is known as the window size, or window. TCP uses expectational ACKs. This means that the ACK number refers to the next packet that is...
Post a Comment
Read more

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...
Post a Comment
Read more

1.2.2 RIP V2 Features

 1.2.2 RIP V2 Features This page will discuss RIP v2, which is an improved version of RIP v1. Both versions of RIP share the following features: It is a distance vector protocol that uses a hop count metric. It uses hold down timers to prevent routing loops – default is 180 seconds. It uses split horizon to prevent routing loops. It uses 16 hops as a metric for infinite distance. RIP v2 provides prefix routing, which allows it to send out subnet mask information with the route update. Therefore, RIP v2 supports the use of classless routing in which different subnets within the same network can use different subnet masks, as in VLSM. RIP v2 provides for authentication in its updates. A set of keys can be used on an interface as an authentication check. RIP v2 allows for a choice of the type of authentication to be used in RIP v2 packets. The choice can be either clear text or Message-Digest 5 (MD5) encryption. Clear text is the default. MD5 can be used t...
Post a Comment
Read more