Scribd
Upload
68 views

CCNP ENCOR Command Reference

The document discusses various routing protocols and concepts: 1. It covers configuration examples for EIGRP route summarization and passive interfaces. 2. It then discusses EIGRP load balancing and the use of the variance command to enable unequal-cost load balancing. 3. The document also briefly mentions configuration for OSPF concepts like summarization, area filtering, and distributed lists.

Uploaded by

Jose Scott
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
68 views

CCNP ENCOR Command Reference

The document discusses various routing protocols and concepts: 1. It covers configuration examples for EIGRP route summarization and passive interfaces. 2. It then discusses EIGRP load balancing and the use of the variance command to enable unequal-cost load balancing. 3. The document also briefly mentions configuration for OSPF concepts like summarization, area filtering, and distributed lists.

Uploaded by

Jose Scott
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 62

1.

Packet Forwarding
2.Spanning Tree Protocol

3.Advanced STP Tunning


4.Multiple Spanning Tree Protocol – MST
5.VLAN Trunks and EtherChannel Bundles
6.IP Routing Essentials

6.1.VRF
7.EIGRP
EIGRP Route Summarization

By default EIGRP summarizes the classfull addresses. So generally “no


auto-summary” command is used on Cisco router to avoid this
situation. In the EIGRP Configuration below, you can find an example
of  EIGRP Route Summarization.
 
Router (config) # router eigrp 100

Router (config-router) # no auto-summary


 
You can also use EIGRP Summary Routes manually. You can use this
by “ip summary-address” command on Cisco Routers. Below there is a
route summarization with 10.0.0.0/8 prefix.
 
Router (config) # interface fa0/1

Router (config-if) # ip summary-address eigrp 100  10.0.0.0 255.0.0.0


 

Passive Interface EIGRP Configuration


If you want to prevent one interface or all interfaces to receive EIGRP
update and EIGRP hello packets , you can use “passive interface”
command. By using this command, no update and hello packets come to
that interface anymore.
 
For example, with “passive interface” command, you can prevent fa0/1
to receive update and hello packets like below EIGRP Config.
Router (config) # router eigrp 100
Router (config-router) # passive-interface fa0/1
 
You can also prevent all the interfaces to receive these packets and then
you can open the ones you want. Below, firstly we prevent all
interfaces and then allow fa0/5 and fa0/6.
 
Router (config) # router eigrp 100

Router (config-router) # passive-interface default

Router (config-router) # no passive-interface fa0/5

Router (config-router) # no passive-interface fa0/6


 

Unicast Neighbours
 
In EIGRP, Multicast Address 224.0.0.10 is used . If you want , you can
change this to a specific neighbour address with “neighbour ip-
address” command on Cisco routers. You can use this command like
below:
 
Router (config) # router eigrp 100

Router (config-router) # neighbour 10.0.0.1


EIGRP Stub
 
EIGRP Stub router is the router that is not a transit router and only
has one EIGRP neighborship. EIGRP Stub provides less queries. You
can configure EIGRP Stub, like below:
 
Router (config) # router eigrp 100

Router (config-router) # eigrp stub [receive-only, connected , static,


summary, redistributed]
 
After stub command, you can optionally use some parameters. These
parameters are receive-only, connected , static, summary, redistributed.
The meaining of these parameters are given below:
 
Receive-only : Update are not shared with neighbors.
Connected : Only connected routes will be advertised.
Static : Only static routes will be advertised.
Summary :  Only summary routes will be advertised.

7.1.EIGRP Unequal-Cost Load Balancing Lab


There are two things you must be aware of when using EIGRP unequal-cost
load balancing, and we’ll cover those (and a whole lot more) in this lab.

In the previous lab, we saw equal-cost load balancing in action.   Now it’s time
to do a little unequal-cost balancing, using this network:
R1’s routing table shows EIGRP equal-cost load balancing in action.  The metrics
for the two available paths to 172.12.23.0 /27 are exactly the same, so both
paths are in the routing table.

Checking R1’s EIGRP topology table, we note there are two entries for both
2.2.2.0 /24 and 3.3.3.0 /24.  Each route has one successor and one feasible
successor.
Our routing would be more efficient if we balanced the load from R1 to
2.2.2.0 /24 over those two available paths.  The metrics of those two paths are
so close (2297856 and 2300416)  that it doesn’t make sense to leave one idle
while letting the other path handle the full load for traffic heading for 2.2.2.0
/24.

That’s where EIGRP unequal-cost load balancing comes in.   EIGRP runs equal-
cost load balancing by default, but unequal-cost balancing requires a little
configuration, a little math, and an eye for details and unexpected results.   
We’ll use all of those as we proceed with this lab.

One magic word enables unequal-cost load balancing in EIGRP. 


The variance command is a multiplier and has a default value of 1.  Using
variance is a two-step process:

1. The router will multiple the Feasible Distance of the route by the
variance value.
2. Any feasible successor with a metric less than that new value will be
entered into the routing table.

In print, I admit that sounds a little confusing, perhaps even a tad askew. 
Thankfully, the reality of this command is simple.   Consider the two paths from
R1 to R2’s loopback in the topology table.
The successor has a metric of 2297856.  By setting the EIGRP variance to 2 on
R1, any route to 2.2.2.0 /24 with a metric of less than 4595712 (2 x 2297856) will
be entered into the EIGRP routing table and will participate in unequal-cost
load sharing.   The only feasible successor to that route has a metric of
2300416, so it certainly qualifies!  Let’s run variance 2 on R1.

With unequal-cost load balancing enabled, R1’s EIGRP routing table now shows
both the successor and feasible successor for 2.2.2.0 /24.  Note that the actual
metrics of the routes do not change.

The feasible successor and successor are also showing up for R3’s loopback
network.  This illustrates a very important point regarding variance,  and you
gotta watch out for it – it’s an all-or-nothing command.  When you
change  variance, you’re changing it for your router’s entire EIGRP configuration. 
(That’s one of the important variance tips I mentioned at the top of the page. 
The second one’s coming up.)

You can verify the variance setting with our pal show ip protocols.
Note the maximum path value of 4.  This value defines how many paths can be
used for load balancing to a single destination.   You can change the value from
the default of 4 with the maximum-paths command, but if you set it to 1, you’re
disabling load balancing!

Time for that second vital variance tip!

You might have looked at that lab and thought “Hey, I don’t need to do any
math.  I’ll just enter variance 255 and I’ll get all the load balancing I want!”
You also might just get load balancing you don’t want.  Let’s say we have three
valid paths to the same network.  Path 1 has a metric of 5000, Path 2 a metric
of 7000, and Path 3 a metric of 55000.  That gives us two links with similar
speeds and a third path that’s way out of line when compared to the other
two.  Do you really want to load balance over that third path?  Probably not.  It’s
a good backup link, but not one I want to use in load balancing.

Bonus tip:  With unequal-cost load balancing in effect, the load each link carries
is proportional to the metric.  If one path’s metric is twice as good as another,
that path will carry roughly twice as much data.

8. OSPF
9.Advanced OSPF
Summarization
Area filtering
Distributed Lists -> To avoid a network to be installed into the local RIB
10.OSPFv3
OSPFv3 IPv4
Configurations took it from an OSPFv3 lab on routers and
switches:
On switches:
Summarization:

Show commands:
11.BGP
IPv6 Configuration
R2# show bgp ipv4 unicast neighbors 10.1.2.1 advertised-routes

R2# show bgp ipv6 unicast neighbors 2001:db8:acad:1012::1 advertised-routes


12.Advanced BGP

You might also like