Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

CHAPTER 3
INFRASTRUCTURE

1
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

CHAPTER3: INFRASTRUCTURE
- Chapter’s Agenda:
3.1 Layer 2
3.1.1 Troubleshoot static and dynamic 802.1q trunking protocols
3.1.2 Troubleshoot static and dynamic EtherChannels
3.1.3 Configure and verify common Spanning Tree Protocols (RSTP and MST)

3.2 Layer 3
3.2.1 Compare routing concepts of EIGRP and OSPF
(advanced distance vector vs. linked state, load balancing, path selection, path operations, metrics)
3.2.2 Configure and verify simple OSPF environments,
including multiple normal areas, summarization, and filtering
(neighbor adjacency, point-to-point and broadcast network types, and passive interface)
3.2.c Configure and verify eBGP between directly connected neighbors
(best path selection algorithm and neighbor relationships)

3.3 IP Services
3.3.1 Describe Network Time Protocol (NTP)
3.3.2 Configure and verify NAT/PAT
3.3.3 Configure first hop redundancy protocols, such as HSRP and VRRP
3.3.4 Describe multicast protocols, such as PIM and IGMP v2/v3

2
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.1 Layer 2 Infrastructure Technologies

3.1.1 Static and Dynamic 802.1q trunking protocols

- Static is to configure every port as either:
- Auto (default): waiting for the other side to negotiate
- Desirable: starts negotiating trunking
- Dynamic (enabled by default)
- only requires one side to enable trunking
- negotiations will dynamically
- negotiations can be “Disabled”

3
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.1.2 Static and Dynamic EtherChannels

- EtherChannels are supported on Cisco switches
- supporting both LACP and PAgP negotiations protocols
- those are the static negotiation etherchannel protocols

- LACP uses:
- Active: initiates bundling negotiations
- Passive: waits for other side to initiate
- PAgP uses:
- Desirable: initiates bundling negotiations
- Auto: waits for other side to initiate
- Dynamic:
- Mode ON: no negotiations, direct bundling (mostly L3)
4
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.1.3 Common Spanning Tree Protocols

- We need redundancy, but there will be a broadcast message!
- What will happen?
- Then how can we prevent what is called a “LOOP”,
AKA “Broadcast Storm”?
- STP requires election to be performed first
- The Winner must be: 1-Lowest Priority, 2-Lowest MAC Address
- After that port roles and states will happen:
- Designated Port: Forwarding state
- Root Port: Forwarding State
- Alternative Port: Blocking State
- The entire process of election takes (30 – 50) Seconds
Max Age = 20 + (Forwarding Delay = 15) + (Learning Delay = 15) = 50 Seconds

5
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- In order to speed things up:

- Rapid STP: NO Listening, NO Blocking,
only (Discard, Forwarding, Learning)
- Then delay will become = 3 + 3 = 6 Seconds
- What is the BIG benefit of Redundancy then!!!!! If STP is blocking ports
- There will be a Per-VLAN STP (PVST)
- Each VLAN can have an ELECTION!!
- Each VLAN will have its own root!
- Things are much better now
- Specially that there is a RPVST+ (faster)!
- RPVST+ can be further simplified by using MST
- Instances (Groups) that requires domain names/revision numbers
- each instance will have its own Tree

6
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.2 Layer 3 Infrastructure Technologies

3.2.1 Enhanced Interior Gateway Routing Protocol (EIGRP)

- A Hybrid Protocol
- classified as a “Distance Vector” protocol
- it does combine both the D.V. and L.S. methods of measuring the metric
- IP Protocol = 88
- Defusing Update Algorithm (DUAL)
- AD = 90
- Metric = Result of the 5K’s formula:
256 * ((K1*Bandwidth) + (K2*Bandwidth)/(256-Load) + K3*Delay) * (K5/(Reliability + K4)))

- The default “K Values”:

- K1 = 1, K2 = 0, K3 = 1, K4 = 0, K5 = 0
- Bandwidth is per link, while Delay is cumulative
7
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- EIGRP will apply the formula to elect its main path

- for redundant paths, Feasibility Condition (FC) is used
- the main path is the lowest metric calculated among available paths
- The Feasible Distance (DF)
- Successor
- the redundant path is the lowest “Advertised” metric from the neighbor!
- The Reported/Advertised Distance (RD)
- Feasible Successor (FS)
- only those paths can be used for UCLD
- which requires the activation of “variance”

8
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.2.2 Open Shortest-Path First (OSPF)

- Link State Protocol
- Dijkstra algorithm
- SPF algorithm for route decision
- AD = 110
- Metric = Cost (lesser = Better)
- Process ID for multiple instances
- Area ID for Data Base isolation

- Link-State Advertisements: negotiation between OSPF Routers

- it contains: LSRequest: provide the missing Information
LSUpdate: reply for the LSR
LSAcknowledgement: reply for the LSU
9
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- Neighboring Process:

10
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- Link State Advertisements (LSA’s)

- multiple types
- depends on the advertisement they are doing
- LSA Type.1 (Router LSA): investigates local OSPF connections
- LSA Type.2 (Network LSA): investigates local OSPF connections for a DR
- LSA Type.3 (Network Summary LSA): for ABR to reach links in Areas
- LSA Type.4 (ASBR Summary LSA): for ABR to reach ASBR’s
- LSA Type.5 (External LSA): for ASBR redistribution
- LSA Type.7 (NSSA External LSA): for ASBR NSSA

11
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- OSPF Neighbor Types:

- A Neighboring router can be a P2P neighbor
- in this case no problems
- or can be connected through a “SWITCH”!!
- broadcast will happen
- elections must take place
- only One router should update the topology (DR)

- a DR (Designated Router): Highest Router Priority (0-255), Def=128

- Or Highest Router ID
- Router ID (R.ID): 32-bit Address
- DR needs BDR (second best of everything)

12
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- OSPF Summarization
- To make all the routers in all the Areas be able to communicate
- LSDB’s must synchronize
- routes and advertisements must be exchanged
- some Routers will receive “Too Much” information about other Areas
- utilizing more resources
- this can be Filtered (ON ABR’s)
- just summarize some prefixes and advertise one prefix instead
- done by generating a Type.3 LSA
- or, filter these prefixes by not generating Type.3 LSA to the other router

13
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.2.3 Border Gateway Protocol (BGP)

- the only WAN routing protocol
- developed from EGP
- uses TCP 179
- isolates peering from neighbor advertising
- needs ASN’s to operate
- can be used internally (iBGP) or externally (eBGP)
- flexible to apply filters, maps, polices, and attributes
- AD = 20/200
- Metric = Attributes
- Attributes affect path selection for packets

14
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- BGP Attributes:
- Next-hop
- Weigh Highest
- Local Preference Highest
- Locally originated
- AS-Path Shortest
- Origin
- MED Lowest
- External over Internal
- IGP Metric to Next-Hop
- Multipath

15
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- BGP Neighbor Relationships

16
Edgeworth B., Rios R.G., Hucaby D., Gooley J. - CCNP and CCIE Enterprise Core ENCOR 350-401 (Official Cert Guide)
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.3 IP Services

3.3.1 Network Time Protocol (NTP)

- we have to stay synchronized
- give a precise information, with real timing and date
- either by setting an inner clock manually
- or asking someone to inform us about timing
- uses UDP = 123

- each network device can either be a Server or a Client

- Stratum is needed:
- how preferred and accurate this source is
- starts from 0 – 15
- the closest, the better
- by default: a cisco router = 8
17
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.3.2 Network Address Translation (NAT)

- Private IP Addresses must not go to the Internet!
- Public IP Addresses should not be assigned to private devices!
- Then!!!, NAT will translate Private to Public and vice-versa
*NAT is done “ONLY” “ONLY” by Routers, no Switches, no MLS’s

- it can be:
Static: one-one translating
Dynamic: Group-Group Translating
- also, this did not solve everything, IP exhaustion still there
- so here comes PAT (Port Address Translation)
- also called NAPT, or NAT-Overload
- PAT will do a one-65535 Translation!!!
18
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.3.3 First Hop Redundancy Protocol (FHRP)

- what if the gateway went down!!!!!!!!
- a redundant gateway must be there
- but how to redirect the requests from one to another?
- how many back-ups can there be?
- What protocols will do this:

Hot-Standby Redundancy Protocol Virtual-Router Redundancy Protocol Gateway Load-Balancing Protocol

(HSRP) (VRRP) (GLBP)

- Cisco Only - Open Standard - Cisco Only

- 2 Gateways - 2 Gateways - 4 Gateways

- No Load-Balancing - No Load-Balancing - Load-Balancing

19
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

3.3.4 Multicast
- the one – to – group transmission
- only one sender, but multiple “specific” receivers
- better than having multiple senders and multiple receivers
- the one sender will send only 1 packet to a Multicast Router
- the multicast router will “Replicate” the packet to multiple destinations
- The Multicast Router = “Rendezvous Point”

- so, the entire operation will be done by the multicast router

- in order to assign specific receivers, create a “Group”
- and “join” the receivers and that one sender to the group
- uses IPv4 block of 224.0.0.0/4
- uses MAC range of 0100:5E00:0000 – 0100:5E7F:FFFF
20
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- Two types of protocols are needed

- Protocol that joins the receivers to the Group:
- Internet Group Management Protocol (IGMP)
- responsible for joining the receivers with the Rendezvous point
- tells the RP that some receivers want to receive from “224.X.X.X”
- BUT, those receivers have no idea about the sender
- IGMP comes in 3 versions
- IGMPv1 (obsolete)

- IGMPv2 (default of Cisco)

- builds a shared tree
- creates (*, G)

21
Cisco CCNP & CCIE Enterprise Core - ENCOR 350-401

- IGMPv3
- builds shortest path tree (SPT)
- creates (S, G)
- uses Source Specific Multicast (SSM)
- SSM Block = 232.0.0.0/8
- SSM informs the receivers about the sender
- NO need for RP
- Also, a Routing Protocol is needed
- Protocol Independent Multicast (PIM)
- routes between receivers’ routers and RP
- requires IGP
- v2 is default
- 2 Modes:
- Dense Mode: like broadcast (obsolete)
- Sparse Mode: connects the receiver's router to the RP
22