Skip to main content

EIGRP IPv4 Name mode

 



EIGRP name mode operates the same way as EIGRP classic mode. EIGRP name mode provides one place for all configurations.




Since IOS 15, EIGRP has had a new method of configuration called mode EIGRP. 
When we use the classic EIGRP version, before IOS 15, we configured EIGRP globally and a few other things like authentication on interfaces, but with named mode EIGRP, we can do everything globally 




 In EIGRP name mode, we can create a single instance of EIGRP.



Topology:


















Task

  • configure the topology as pr the diagram 
  • assign IP addresses to their interfaces as per our topology 
  • configure EIGRP IPv4 name mode.

R1(config)#Interface fastethernet 0/0
R1(config-if)#Ip address 10.1.1.1   255.0.0.0
R1(config-if)#No shutdown
R1(config-if)#No keepalive
R1(config-if)#Exit

R1(config)#Interface serial 3/0
R1(config-if)#Ip address  1.1.1.1 255.0.0.0
R1(config-if)#No shutdown
R1(config-if)#Exit


R2(config)#Interface fastethernet 0/0
R2(config-if)#Ip address 20.1.1.1   255.0.0.0
R2(config-if)#No shutdown
R2(config-if)#No keepalive
R2(config-if)#Exit

R2(config)#Interface serial 3/0
R2(config-if)#Ip address  1.1.1.2 255.0.0.0
R2(config-if)#No shutdown
R2(config-if)#Exit


R1#show ip interface brief
Interface              IP-Address      OK? Method Status                Protocol
FastEthernet0/0        10.1.1.1        YES manual up                    up
Serial3/0                    1.1.1.1         YES manual up                    up

R2#show ip interface BRief
Interface              IP-Address      OK? Method Status                Protocol
FastEthernet0/0        20.1.1.1        YES manual up                    up
Serial3/0                     1.1.1.2         YES manual up                    up


R1(config)#router eigrp ccie
R1(config-router)#address-family ipv4 unicast autonomous-system 100
R1(config-router-af)#network 1.0.0.0
R1(config-router-af)#network 10.0.0.0
R1(config-router-af)#exit

*Dec  3 20:34:51.331: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 1.1.1.2 (Serial3/0) is up: new adjacency

R2(config)#router eigrp ccie
R2(config-router)#address-family ipv4 autonomous-system 100
R2(config-router-af)#network 1.0.0.0
R2(config-router-af)#network 20.0.0.0
R2(config-router-af)#exit

*Dec  3 20:34:51.323: %DUAL-5-NBRCHANGE: EIGRP-IPv4 100: Neighbor 1.1.1.1 (Serial3/0) is up: new adjacency


R1#show ip eigrp interfaces
EIGRP-IPv4 VR(ccie) Address-Family Interfaces for AS(100)
                              Xmit Queue   PeerQ        Mean   Pacing Time   Multicast    Pending
Interface              Peers  Un/Reliable  Un/Reliable  SRTT   Un/Reliable   Flow Timer   Routes
Se3/0                    1        0/0       0/0          44       0/16         180           0
Fa0/0                    0        0/0       0/0           0       0/0            0           0

R1#show ip eigrp neighbor
EIGRP-IPv4 VR(ccie) Address-Family Neighbors for AS(100)
H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq
                                                   (sec)         (ms)       Cnt Num
0   1.1.1.2                 Se3/0                    11 00:17:16   44   264  0  4

R1#show ip route eigrp
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
       + - replicated route, % - next hop override

Gateway of last resort is not set

D     20.0.0.0/8 [90/13607262] via 1.1.1.2, 00:17:28, Serial3/0

R1#show ip eigrp topology
EIGRP-IPv4 VR(ccie) Topology Table for AS(100)/ID(10.1.1.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status

P 10.0.0.0/8, 1 successors, FD is 13107200
        via Connected, FastEthernet0/0
P 1.0.0.0/8, 1 successors, FD is 1735175958
        via Connected, Serial3/0
P 20.0.0.0/8, 1 successors, FD is 1741729558
        via 1.1.1.2 (1741729558/13107200), Serial3/0

R1#show ip protocol
*** IP Routing is NSF aware ***

Routing Protocol is "eigrp 100"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
  EIGRP-IPv4 VR(ccie) Address-Family Protocol for AS(100)
    Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 K6=0
    Metric rib-scale 128
    Metric version 64bit
    NSF-aware route hold timer is 240
    Router-ID: 10.1.1.1
    Topology : 0 (base)
      Active Timer: 3 min
      Distance: internal 90 external 170
      Maximum path: 4
      Maximum hopcount 100
      Maximum metric variance 1
      Total Prefix Count: 3
      Total Redist Count: 0

  Automatic Summarization: disabled
  Maximum path: 4
  Routing for Networks:
    1.0.0.0
    10.0.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    1.1.1.2               90      00:18:08
  Distance: internal 90 external 170


R2#show ip eigrp interfaces
EIGRP-IPv4 VR(ccie) Address-Family Interfaces for AS(100)
                              Xmit Queue   PeerQ        Mean   Pacing Time   Multicast    Pending
Interface              Peers  Un/Reliable  Un/Reliable  SRTT   Un/Reliable   Flow Timer   Routes
Se3/0                    1        0/0       0/0          39       0/16         192           0
Fa0/0                    0        0/0       0/0           0       0/0            0           0


R2#show ip eigrp neighbor
EIGRP-IPv4 VR(ccie) Address-Family Neighbors for AS(100)
H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq
                                                   (sec)         (ms)       Cnt Num
0   1.1.1.1                 Se3/0                    14 00:19:05   39   234  0  3

R2#show ip route eigrp
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
       + - replicated route, % - next hop override

Gateway of last resort is not set

D     10.0.0.0/8 [90/13607262] via 1.1.1.1, 00:19:16, Serial3/0


R2#show ip protocol
*** IP Routing is NSF aware ***

Routing Protocol is "eigrp 100"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Default networks flagged in outgoing updates
  Default networks accepted from incoming updates
  EIGRP-IPv4 VR(ccie) Address-Family Protocol for AS(100)
    Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 K6=0
    Metric rib-scale 128
    Metric version 64bit
    NSF-aware route hold timer is 240
    Router-ID: 20.1.1.1
    Topology : 0 (base)
      Active Timer: 3 min
      Distance: internal 90 external 170
      Maximum path: 4
      Maximum hopcount 100
      Maximum metric variance 1
      Total Prefix Count: 3
      Total Redist Count: 0

  Automatic Summarization: disabled
  Maximum path: 4
  Routing for Networks:
    1.0.0.0
    20.0.0.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    1.1.1.1               90      00:19:28
  Distance: internal 90 external 170


R1#ping 20.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 20.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms


R2#ping 10.1.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/34/60 ms







Comments

Popular posts from this blog

What is Classification and marking? What is IP Precedence and DSCP Values? What is AF and EF?

  Classification and Marking Classification and marking are the processes of identifying the priority of each packet. This is the first step of QOS control and should be done near the source hosts. Classification is the process of identifying and categorising traffic into classes, typically based upon incoming interface IP precedence, DSCP Source or Destination address. Application classification is the most fundamental QOS building block. Without classification, all packets are treated the same.   The table lists the criteria of classification                                  Marking  Marking is the QOS feature component that colours a packet so it can be identified and distinguished from other packets in QOS treatment. Commonly used markers: link-layer: COS (ISL, 802.1q), MPLS EXP bits,...

What is of NBAR (network- based application recognition),classification QOS How to configure NBAR?

 When we implement Quality of Service (QoS ) the first step is classification, by default our router does not care about what kind of IP packets it is. Our router just looks at the routing table to find the correct destination IP address and forwards. When we configure QoS technologies like queuing, policing, or shaping before doing first we have to identify what kind of traffic is running on our routers so we can figure out what kind of application it belongs to. This is classification. What is Quality of Service (QOS)? What is Modular Quality of service CLI (MQC)? What is Classification and marking? What are IP Precedence and DSCP Values? What is AF and EF?     Once we identify our traffic (classify). Now we can mark and apply QoS policy to it. There are a few methods on IOS routers for classification: Header inspection It is a simple classification method and it works really good but has some disadvantages. Let’s say we configure our router all th...

OSPF Tunnels Vs Virtual-links

OSPF VIRTUAL LINKS  An Open Shortest Path First (OSPF) autonomous system has all areas physically connected to the backbone area (Area 0). In some cases, if this is not possible, we can use a virtual link to connect to the backbone (Area 0) through a non-backbone area. We can also use the virtual links to connect two parts of a partitioned backbone (Area 0) through a non-backbone area. The area through which we configure the virtual link, known as a transit area, must have full routing information. Remember, the transit area cannot be a stub area. Virtual link must be configuring both sides with the same area ID and the corresponding virtual link OSPF neighbor router ID. Show IP OSPF neighbors command give you the router ID information. OSPF Transit Area from Tunnel When configuring OSPF with tunnel interfaces as transit areas, there are several important considerations to ensure proper routing functionality. Here's what you need to know: Key Concepts Transit Area : In OS...