BGP MASTER LAB

BGP LAB DAY 1

https://networkengineerstuff.blogspot.com/2020/10/bgp-lab-day-1.html

 BGP LAB DAY 2

https://networkengineerstuff.blogspot.com/2020/10/bgp-lab-day-2.html

BGP LAB DAY 3

https://networkengineerstuff.blogspot.com/2020/11/bgp-lab-day-3.html

 BGP LAB DAY4

https://networkengineerstuff.blogspot.com/2020/12/bgp-lab-day-4.html

BGP LAB DAY 3

 

Tasks

===========

Configuring Authentication for eBGP Neighborship R1 and R2

 !!Shutting & Unshutting BGP Neighborship 

 

!! Configuring Authentication for eBGP Neighborship R1 and R2
R1(config)#router bgp 100
R1(config-router)#neighbor 2.2.2.2 password ?
  <0-7>  Encryption type (0 to disable encryption, 7 for proprietary)
  LINE   The password

R1(config-router)#neighbor 2.2.2.2 password cisco@123
R1(config-router)#
R1(config-router)#^Z
!
R2(config)#
R2(config)#router bgp 200
R2(config-router)#neighbor 1.1.1.1 password cisco@123
R2(config-router)#^Z
R2#

R1#sh run | section  bgp
router bgp 100
 bgp log-neighbor-changes
 network 10.1.1.0 mask 255.255.255.0
 network 10.1.2.0 mask 255.255.255.0
 network 10.1.3.0 mask 255.255.255.0
 network 10.1.4.0 mask 255.255.255.0
 neighbor 2.2.2.2 remote-as 200
 neighbor 2.2.2.2 description **eBP with R2**
 neighbor 2.2.2.2 password 7 05080F1C22436E584B56 ====> the password got encrypted with type 7 password
 neighbor 2.2.2.2 ebgp-multihop 255
 neighbor 2.2.2.2 update-source Loopback0
 neighbor 2.2.2.2 soft-reconfiguration inbound
 neighbor 13.1.1.3 remote-as 300
 neighbor 13.1.1.3 description **eBP with R3**
 
 !!Shutting & Unshutting BGP Neighborship

R1#sh ip bgp summary
BGP router identifier 10.1.4.1, local AS number 100
BGP table version is 25, main routing table version 25
20 network entries using 2880 bytes of memory
28 path entries using 2240 bytes of memory
6/5 BGP path/bestpath attribute entries using 816 bytes of memory
4 BGP AS-PATH entries using 96 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 6032 total bytes of memory
BGP activity 20/0 prefixes, 28/0 paths, scan interval 60 secs

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
2.2.2.2         4          200     103     103       25    0    0 01:27:48       16
13.1.1.3        4          300     100     102       25    0    0 01:27:30        8
R1#

R1#sh run | section bgp
router bgp 100
 bgp log-neighbor-changes
 network 10.1.1.0 mask 255.255.255.0
 network 10.1.2.0 mask 255.255.255.0
 network 10.1.3.0 mask 255.255.255.0
 network 10.1.4.0 mask 255.255.255.0
 neighbor 2.2.2.2 remote-as 200
 neighbor 2.2.2.2 description **eBP with R2**
 neighbor 2.2.2.2 password 7 05080F1C22436E584B56
 neighbor 2.2.2.2 ebgp-multihop 255
 neighbor 2.2.2.2 update-source Loopback0
 neighbor 2.2.2.2 soft-reconfiguration inbound
 neighbor 13.1.1.3 remote-as 300
 neighbor 13.1.1.3 description **eBGP with R3**
!
R1#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#
R1(config)#router bgp 100
R1(config-router)# neighbor 2.2.2.2 shut
R1(config-router)# neighbor 2.2.2.2 shutdown
R1(config-router)#^Z
R1#
*Nov 30 09:30:31.851: %BGP-5-NBR_RESET: Neighbor 2.2.2.2 reset (Admin. shutdown)
*Nov 30 09:30:31.863: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Down Admin. shutdown
*Nov 30 09:30:31.863: %BGP_SESSION-5-ADJCHANGE: neighbor 2.2.2.2 IPv4 Unicast topology base removed from session  Admin. shutdown
*Nov 30 09:30:33.007: %SYS-5-CONFIG_I: Configured from console by console
R1#
R1#sh ip bgp sum
R1#sh ip bgp summary
BGP router identifier 10.1.4.1, local AS number 100
BGP table version is 33, main routing table version 33
12 network entries using 1728 bytes of memory
12 path entries using 960 bytes of memory
6/3 BGP path/bestpath attribute entries using 816 bytes of memory
4 BGP AS-PATH entries using 96 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 3600 total bytes of memory
BGP activity 20/0 prefixes, 28/16 paths, scan interval 60 secs

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
2.2.2.2         4          200       0       0        1    0    0 00:00:10 Idle (Admin)
13.1.1.3        4          300     106     109       33    0    0 01:32:38        8
R1#

On R1 the state will be Idle (Admin) whereas on R2 it will be Idle .

R2#
*Nov 30 09:30:32.155: %BGP-5-NBR_RESET: Neighbor 1.1.1.1 reset (Peer closed the session)
*Nov 30 09:30:32.171: %BGP-5-ADJCHANGE: neighbor 1.1.1.1 Down Peer closed the session
*Nov 30 09:30:32.171: %BGP_SESSION-5-ADJCHANGE: neighbor 1.1.1.1 IPv4 Unicast topology base removed from session  Peer closed the session
R2#
R2#
R2#
R2#
R2#sh ip bgp sum
R2#sh ip bgp summary
BGP router identifier 20.1.4.1, local AS number 200
BGP table version is 25, main routing table version 25
16 network entries using 2304 bytes of memory
16 path entries using 1280 bytes of memory
4/4 BGP path/bestpath attribute entries using 544 bytes of memory
2 BGP AS-PATH entries using 48 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 4176 total bytes of memory
BGP activity 20/4 prefixes, 28/12 paths, scan interval 60 secs

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
1.1.1.1         4          100       0       0        1    0    0 00:02:22 Idle
24.1.1.4        4          300     112     118       25    0    0 01:34:28       12
R2#


!!Unshut the BGP Neighborship
R1#   sh run | section bgp
router bgp 100
 bgp log-neighbor-changes
 network 10.1.1.0 mask 255.255.255.0
 network 10.1.2.0 mask 255.255.255.0
 network 10.1.3.0 mask 255.255.255.0
 network 10.1.4.0 mask 255.255.255.0
 neighbor 2.2.2.2 remote-as 200
 neighbor 2.2.2.2 description **eBP with R2**
 neighbor 2.2.2.2 password 7 05080F1C22436E584B56
 neighbor 2.2.2.2 shutdown
 neighbor 2.2.2.2 ebgp-multihop 255
 neighbor 2.2.2.2 update-source Loopback0
 neighbor 2.2.2.2 soft-reconfiguration inbound
 neighbor 13.1.1.3 remote-as 300
 neighbor 13.1.1.3 description **eBGP with R3**
R1#
R1#config
Configuring from terminal, memory, or network [terminal]?
Enter configuration commands, one per line.  End with CNTL/Z.
R1(config)#router bgp 100
R1(config-router)#no neighbor 2.2.2.2 shutdown
R1(config-router)#^Z
R1#
*Nov 30 09:35:03.887: %BGP-5-ADJCHANGE: neighbor 2.2.2.2 Up
*Nov 30 09:35:04.071: %SYS-5-CONFIG_I: Configured from console by console

R1#sh ip bgp summary
BGP router identifier 10.1.4.1, local AS number 100
BGP table version is 41, main routing table version 41
20 network entries using 2880 bytes of memory
28 path entries using 2240 bytes of memory
6/5 BGP path/bestpath attribute entries using 816 bytes of memory
4 BGP AS-PATH entries using 96 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 6032 total bytes of memory
BGP activity 28/8 prefixes, 44/16 paths, scan interval 60 secs

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
2.2.2.2         4          200      11      11       41    0    0 00:00:12       16
13.1.1.3        4          300     111     116       41    0    0 01:37:12        8


Thanks for reading 

amartechstuff

Generic Routing Encapsulation (GRE) Tunnel Configuration in Cisco Packet Tracer (LAB)

 

PART 1 - Configure Basic Stuff
============================================================================

Step 1:- Create the topology as shown in the diagram in Packet Tracer.

Step 2:- Configure Hostname and IP addresses Routers, Switches and PCs as shown in the diagram.

Step 3:- On Pune Router & Chennai Router configure default route pointing towards ISP.

PART 2 -Configure GRE Tunnel Between Pune Router & Chennai Router
==============================================================================

Step 1:-Configure GRE Tunnel interfaces on Pune Router & Chennai Router as shown in the diagram
        keeping source as WAN interfaces

Step 2:-Verify the status of the GRE Tunnel 0 , Tunnel Protocol , Tunnel source & destination.

Step 3:-Ping accross tunnel from both routers.

Step 4:-Traceroute to determine the path to the tunnel. =====> one hop !!!!!

PART 3 - Configure Routing over GRE Tunnel
===============================================================================

Step 1:- Configure EIGRP AS 100 on Pune Router & Chennai Router and advertise the tunnel , LAN networks.

Step 2:-Verify EIGRP Neighborship.

Step 3:-Verify the routing table.

Step 4:-Check end to end connectivity by ping PC1 to PC2 and vice versa.

Cisco Nexus Models Overview

  In this blog we will focus on Cisco Nexus Switches Models

+ Cisco Nexus Switches were introduced by Cisco in Jan 2008

+ These are DATA Center Switches

+ NX-OS is the operating system which runs on these switches which is quite different from the catalyst IOS .

+ There are various models in Cisco Nexus Switches which are deployed in Data Center as per requirement .

+ Gives you option of Modular and Fixed Switches .

1) Cisco Nexus 9000 Series

 

+ These can operate in ACI (Application Centric Infrastructure) mode which no other switches can operate .

+ Gives you option of Modular and Fixed Switches .

+ Supports VXLAN

https://www.cisco.com/c/en_in/products/switches/nexus-9000-series-switches/models-comparison.html

2) Cisco Nexus 7000 Series

 

+ Modular Switches

+ Supports DCI Technologies - OTV & LISP

+ Also supports VDC ,FCOE

https://www.cisco.com/c/en/us/products/switches/nexus-7000-series-switches/models-comparison.html

+ Nexus 7018 can provide Switching capacity upto 17.6 Tbps.

+ Nexus 7718 can provide Switching capacity upto 90 Tbps.

3) Cisco Nexus 5000 Series

 

+ Fixed Switches

+ Data Center Access Layer Switches (End of Row)

https://www.cisco.com/c/en/us/products/switches/nexus-5000-series-switches/models-comparison.html

+ 10G platform switch Nexus 5672UP can provide Switching capacity upto 2.56 Tbps.

+ 40G platform switch Nexus 5624Q can provide Switching capacity upto 7.68 Tbps.

+ Supports VXLAN and FCOE

4) Cisco Nexus 3000 Series

 

+ Fixed Switches

+ The 3000 Series offers low-latency, highly programmable, high-density switches.

+ These compact fixed switches are excellent for general-purpose deployments, high-performance computing (HPC),  high-frequency trading (HFT), massively scalable data center (MSDC), and cloud networks.

https://www.cisco.com/c/en/us/products/switches/nexus-3000-series-switches/models-comparison.html#~tab-nexus3600

+ Nexus 3000 can provide Switching capacity upto 176 Gbps.

+ Nexus 3600 can provide Switching capacity upto 7.2 Tbps.

5) Cisco Nexus 2000 Series

 

+  Fabric Extenders (FEX)

+  They appear as an extension to the parent switch to which they connect.

+Parent switch support spans Cisco Nexus 5000, 6000, 7000, and 9000 Series Switches and Cisco UCS fabric interconnects.

https://www.cisco.com/c/en/us/products/switches/nexus-2000-series-fabric-extenders/models-comparison.html

6) Cisco Nexus 6000 Series

+ End of Sale
 

https://www.cisco.com/c/en/us/products/switches/nexus-6000-series-switches/index.html

7) Cisco Nexus 1000v Series

https://www.cisco.com/c/en/us/products/switches/nexus-1000v-switch-vmware-vsphere/index.html

+ The 1000v is a virtual switch for use in virtual environments including both VMware vSphere and Microsoft Hyper-V[2]
+ It is as such not a physical box but a software application that interacts with the hypervisor so you can virtualize the networking environment and be able to configure your system as if all virtual servers have connections to a physical switch and include the capabilities thata switch offers such as multiple VLANs per virtual interface, layer-3 options, security features etc.