Featured Article
Latest Post

Tuesday, 10 December 2013

How to Configuring the Cisco IOS NTP Server

In the real world can have a high end Cisco 7600 or 7,200 Cisco router as NTP server, the entire infrastructure, including Windows or Linux network from the same NTP server on the network to ensure each device gets its time is synchronized.

While getting training of  CCNA in Pakistan let us learn how to Configure IOS NTP Server using just a single command. Configured as an NTP server to support Cisco equipment you will use the NTP master # command in global configuration and # is the device of strata. For example,; NTP master 3 will act as a stratum 3 NTP servers, configuring Cisco devices.

In this lab you will configure R1 and R2 as a NTP server NTP client query the time from an NTP server R1.

Familiarize yourself with; the following new commands are listed below

Step 1: Manually configure the time and date on R1 to the current time and date.

Step 2: Configure R1 as an NTP Master server in the stratum 3 layer.

Step 3: Configure R2 as an NTP client using R1 as its NTP Server.

Step 4: Verify that the time and date and R1,R2 to be properly synchronized.

Read Me:

You may need to wait a few minutes, R1 and R2 before it's time, so don't get discouraged if it doesn't sync, sync.


How to Configuring IP DHCP Helper Address

So have you thought about how a single DHCP server can provide a DHCP IP address to each computer on a network, DHCP servers are not in the same broadcast domain? All DHCP request broadcast requests correctly?

A lot of people who are getting on-campus or CCNA online training don't know how to do this, but the answer is quite simple. This is called IP assistance programs address. DHCP IP assistance programs address previous routing interfaces (such as VLAN or a router Ethernet interface allows the specific device will act as a "middle man" forwards (broadcast) BOOTP DHCP requests it receives by assisting programs through unicast IP address of the DHCP server IP address configured on the interface.

To configure IP assistance program addresses connected to interface configuration mode in which you want to provide DHCP broadcast domains on the interface using the IP address a.b.c.d IP assistance programs address. For example, one VLAN on the interface or router's Ethernet interface to connect Cisco switch or have a separation layer 2 VLAN.

R1 and R2 in the lab put a different VLAN, your DHCP pool is created for each VLAN on the R1 and SW1 ′ s VLAN20 interfaces connected to R2 VLAN in order to ensure that the device on the Ethernet segment from the DHCP server (R1) receive assistance program a IP address is configured on the DHCP IP address. You will test your PC as a simulated host using the R2 configuration of DHCP and IP assistance programs.

Familiarize yourself with the following new commands;



  • Than load if you use GNS3 CCNA free Binder GNS3 topology than starting system R1, R2 and SW1
  • Establish a with R1, R2 and SW1 than load by copying the configuration file from the text box and paste it into a respectable router console provides the following initial configuration of the device console session.
Step 1: On R1 create a new DHCP pool called “LAB_POOL2″ and assign it the following attributes; network 10.116.20.0/24, default-router of 10.116.20.2, domain name TESTLAB.LOCAL, DNS servers 10.116.18.6 & 10.116.18.7

Step 2: About the SW1 IP interface configuration assistance programs address points to 10.116.10.1


Step 3: Verify that R2 can receive a DHCP address from R1 in the 10.116.20.0/24 network.


R2#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#interface FastEthernet0/0
R2(config-if)#shut
R2(config-if)#
%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
R2(config-if)#no shut
R2(config-if)#end
R2#
%SYS-5-CONFIG_I: Configured from console by console
R2#
%LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
R2#
%DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0/0 assigned DHCP address 10.116.20.3, mask 255.255.255.0, hostname R2

R2#ping 10.116.10.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.116.10.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 48/108/164 ms
R2#

How to Configuring RIP for IPv6 - RIPng

While getting Cisco Training in Pakistan, now its time for you to move to third, dynamic routing protocol free CCNA Binder discusses the fundamental understanding of IPv6. Created specifically for the IPv6 RIP next generation.

Operation mode such as RIPv2, RIPng sending updates every 30 seconds and the route expiration timer time is 180 seconds. Default garbage collection interval is 120 seconds. RIP to send updates to the IPv6 multicast groups, and by default uses port 521 FF02::9.

Configuring RIPng only RIPv2, slightly easier. RIPng, you configured in router configuration mode to a specific interface not using network x.x.x.x command no longer participate in the RIP process. RIPng you participate now RIP interface is configured on a per-interface basis.

To configure an interface name RIPng you use IPv6 RIP command is enabled on a per-interface basis. IPv4 is the name specified in the syntax of local major name is used to identify the router RIPng processes on multiple processes on a single router RIPng, RIP can only have a single process.

RIPng Protocol timers, and other relevant information you want to see, use this command to display shows the name of the IPv6 RIP. To view the database will use the show IPv6 RIPng user names or privileged mode in the RIP database command.

There is a new order, not RIP to show IPv6 RIP command names the next-hop IPv4 to IPv6. This command displays the number of routes to each next-hop (a neighboring router).

In this lab you will R1&R2 and R3, R2 located on each router interface loopback0 IPv6 traffic between IPv6 network for the routing on a frame relay subinterface configuration between RIPng.

Familiarize yourself with the following new commands;


Lab Prerequisites:

  • If you are using GNS3 than load the Free CCNA Workbook GNS3 topology than start device(s); R1, R2 and R3
  • Establish a console session with device(s) R1, R2 and R3 than load the initial configurations provided below by copying the config from the textbox and pasting it into the respected routers console.

Lab Objectives:
  • Enable RIPng R1 ′ s and serial 0/0.122 interface Loopback0 used RIPng process name "none".
  • Enable RIPng R2 ′ s Loopback0, serial 0/0.221 serial 0/0.223 interface using RIPng process name "CCNA".
  • Enable RIPng R3 ′ s and serial 0/0.322 interface Loopback0 used RIPng process name "Binder".
  • Validation R1 R2 ′ s ′ s Loopback0 network routing serial 0/0.223 link-local IPv6 address of the next hop of the R3 ′ s the IPv6 exists in the IPv6 routing table.
  • Verified by pinging the R1 from R3 ′ s ′ s Loopback0 interface Loopback0 interface IPv6 traffic.
Step 1: Enable RIPng on R1′s Loopback0 and Serial0/0.122 interfaces using the RIPng process name “CCNA”.

R1>enable
R1#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#interface loopback0
R1(config-if)#ipv6 rip FREE enable
R1(config-if)#interface Serial0/0.122
R1(config-subif)#ipv6 rip FREE enable   
R1(config-subif)#end
R1#
%SYS-5-CONFIG_I: Configured from console by console
R1#

Step 2: Enable RIPng on R2′s Loopback0, Serial0/0.221 and Serial0/0.223 interfaces using the RIPng process name “CCNA”.

R2>enable
R2#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
R2(config)#interface loopback0
R2(config-if)#ipv6 rip CCNA enable
R2(config-if)#interface Serial0/0.221
R2(config-subif)#ipv6 rip CCNA enable
R2(config-if)#interface Serial0/0.223
R2(config-subif)#ipv6 rip CCNA enable  
R2(config-subif)#end
R2#
%SYS-5-CONFIG_I: Configured from console by console
R2#

R3 as shown ′ s routing table; the route to the 2001:ABAD:BEEF:1001::/64 display FE80::C800:11FF:FE84:8 serial 0/0.322 the next-hop network. You should immediately recognize that the address is a link-local address, it begins with "FF80 ″. You can further verify this is through the use of R2, as shown in the following display interface R2 ′ s serial 0/0.223 serial 0/0.223 command IPv6 link-local addresses. Please pay attention to the bottom line of the link-local address from the R3 and R2 ′ s ′ s routing table matches the serial 0/0.223 interface.

Step 5: Verify that by pinging the R1 from R3 ′ s ′ s Loopback0 interface Loopback0 interface IPv6 traffic.



How to Configuring Basic IPv6 OSPFv3

N the real world, many companies use multiple suppliers, network equipment, like Cisco, Juniper, Adtran, and others, and solution needs more suppliers supporting routing protocols. OSPFv3 (open shortest path first version 3) is setting the industry standard for the internal dynamic gateway routing protocols. Because OSPF is an industry standard routing from any dealer that almost every platform supports it.

Migration from IPv4 have OSPF and IPv6. Most of the concepts and the rules remain the same, including the stub zone, the backbone area, default information is originating from, and more. If you need to view OSPF CCNA Binder section 9.

But there are a few changes, configuring OSPFv3 vs OSPF for IPv4. Instead of the OSPF router configuration mode use the network x.x.x.x WC.WC.WC.WC # command now you configure the OSPFv3 interface configuration mode, use the IPv6 OSPF area PROCID# # commands on a per-interface basis.

There are many reasons why you need to enter the OSPFv3 router configuration mode to configure the router ID or set the default information or distribution lists. In this case, you would use the IPv6 router OSPF global configuration mode PROCID# command. But keep in mind that network commands in OSPFv3 does not exist.

In addition if you recall OSPF IPv4 if you remember the highest OSPF router ID on the IPv4 address of the loopback or physical interfaces, whether or not it is not statically assigned. Have strict IPv6 network while working, you will need a static ID through the IPv6 OSPFv3 router OSPF router ID x.x.x.x command in router configuration mode using.

OSPF authentication command a lot already shows the IPv6 OSPF neighbor ported to IPv6, show IPv6 OSPF interfaces and display the IPv6 OSPF database commands.

To view important OSPFv3 information, such as the current timer, router ID, you will need to use the show IPv6 OSPF reference bandwidth user or privileged mode PROCID# command.

In this lab you will R1&R2 between the frame relay subinterface and R3, and 1, 2, and 3 to each router on the loopback interface configured on R2 0 x. When you are finished, you should be able to route located on each router interface loopback0 simulation between IPv6 IPv6 network traffic.

Familiarize yourself with the following new commands;



  • According to its number of router R1, R2 and R3 ′ s OSPFv3 router ID. Subsection e; 1.1.1.1
  • Configure R1 0/0.221 0/0.122&R2 ′ s ′ s serial port serial port interfaces to participate in OSPF area 0.
  • R2 0/0.322 0/0.223&R3 ′ s ′ s serial port serial port interfaces to participate in OSPF area 0.
  • Configure OSPF areas 1 to participate in and ensure that R1 released as 64 Lo0 of ′ s Loopback0 interface subnet and host routes, not (128).
  • Configure OSPF area 2 to participate in and ensure that R1 R2 ′ s Loopback0 interface Lo0 released as 64 subnet and host routes, not (128).
  • Configure OSPF areas 3 to participate in and ensure that R1 released as 64 Lo0 of ′ s Loopback0 interface subnet and host routes, not (128).
  • Verify that the R1 ′ s Loopback0 network is R3 in the IPv6 routing table.
  • Verify R3 R1 ′ s ′ s Loopback0 network Loopback0 network using PING to IPv6 connections.
Step 1: Configure R1, R2 and R3′s OSPFv3 Router-ID according to their router number. I.e; 1.1.1.1


Step 2: Configure R1′s Serial0/0.122 & R2′s Serial0/0.221 interfaces to participate in OSPF Area 0.


Step 3: Verify that R1′s Loopback0 network is in the IPv6 routing table of R3.

Step 4: Verify that R3′s Loopback0 network has IPv6 connectivity to R1′s Loopback0 network using PING


Popular Posts

Powered by Blogger.