2024 တကိုယ်ရေ ကျေးဇူးတင်မှတ်တမ်း

 ၂၀၂၄ ခုနစ်အတွက်မှာ အကောင်းအဆိုး အကြောင်းအကျိုး ပြန်တွက်ပြီး သူတပါးဂုဏ်ကျေးဇူးတွေ ရေတွက်ရမယ်ဆိုရင်

၂၀၂၄ မှာ စလုံးမြေကနေ နိုင်ငံအသစ်ကို ရွေ့ပြောင်းနေ့ထိုင်မယ် လို့ ရည်မှန်းချက် ထားခဲ့တယ် ..

အဲတုန်းက CA လား US လား သေချာ မဆုံးဖြတ်ရသေးပေမယ့် US မှာ နေဖြစ်အောင် အကူအညီပေးခဲ့တဲ့ လမ်းပြ ပေးတဲ့ US က ညီအကို ဆွေမျိုးအားလုံးကို အထူးကျေးဇူးတင်ရပါတယ် ..

လိုအပ်တဲ့အချိန်မှာ ငွေရေးကြေးရေးက အစ စိတ်မပူပဲ နိုင်ငံပြောင်းနိုင်အောင် ကူညီပေးတဲ့ သူငယ်ချင်း ကိုလဲ အမြဲကျေးဇူးတင်ရပါတယ်.

ဘယ်နိုင်ငံရောက်ရာက် ပညာနဲ့ အသက်မွေးနိုင်အောင် ပညာသင်ခွင့်ပေးတဲ့ မိခင်ကြီး ကျေးဇူး နဲ့အတူ သင်ဆရာ မြင်ဆရာ ကြားဆရာ အားလုံးရဲ့ ဂုဏ်ကျေးဇူးကို အမြဲ အမှတ်ရ ကန်တော့ပါတယ် ..

၂၀၂၄ မှာ တသက်လုံး စိတ်ထင်သလို သောက်လာတဲ့ အရက်သေစာ ဘီယာ ကို လုံး၀(လုံး၀) ရှောင်ကြည်နိုင်ခဲ့တာ အမြတ်တခု ထွက်တယ် ပြောရမယ်.

၂၀၂၄ မှာ မိသားစုဝင် ၁ ယောက်တိုးလာတယ် သမီးလေးက ကိုယ်တို့ ဘ၀ ထဲကို ရောက်လာတယ် .. ကိုယ်လိုချင်တဲ့ မိသားစုဘ၀ အိပ်မက်ကို ဖြည့်ဆည့်ပေးလို့ကော ဘယ်လိုဆုံးဖြတ်ချက်ပဲချချ အမြဲ အားပေးတဲ့ မိန်းမ ကို အထူးကျေးဇူးတင်ရပါတယ်

၂၀၂၄ မှာ ပဌာန်း အကျယ် ပရိတ်ကြီး ၁၁ သုတ် ကို ပါဌိ အတိုင်း ရွတ်တတ် ဖတ်တတ်လာတယ် .အဲဒါကလဲ ဆရာတော် ဦးစိတ္တရ ရဲ့ မေတ္တသုတ် အဖွင့် စာအုပ်ဖတ်ပြီး ဖြစ်လာတဲ့ စိတ်ကနေ တောက်လျှောက် ယုံယုံကြည်ကြည် ရွတ်တတ် ဖတ် တတ် လာတာပါပဲ ..

ဘာသာရေးနဲ့ ပတ်သက်ပြီး လမ်းမှန်ရောက်အောင် ဆိုဆုံးမပေးတဲ့ ဆရာတော် ဦးစိတ္တရ ( ဇင်ဝေသော်) ကိုလဲ ကျေးဇူးတင် ပါတယ် ..

Indianapolis က မြန်မာ ကွန်မြူနတီမှာ ကိုယ်တတ်နိုင်သလောက်လေး ပါဝင်အားဖြည့်ပေးနိုင်အောင် အခွင့်အရေးပေးတဲ့ Community Leaders တွေကို ကျေးဇူးတင်ပါတယ်

၂၀၂၄ မှာ ဗုဒ္ဓဘာသာကော ခရစ်ယာန် အသိုင်းအ၀ိုင်းကကော သူတော်ကောင်း တွေရဲ့ ကူညီ ဆောင်မ ခြင်း ခံရလို့ အထူးဝမ်းမြောက်ရပါတယ်..

ချစ်ခင်ရတဲ့ မိတ်ဆွေများအားလုံးလဲ ယခု လာမည့် ၂၀၂၅ ခုနှစ်မှာ လိုအင်ဆန္ဒ များပြည့်မြောက်ကြပြီးလို့ စိတ်၏ ချမ်းသာခြင်း ကိုယ်၏ ကျမ်းမာခြင်း နဲ့ တလုံးတ၀ နဲ့ ပြည့်စုံနိုင်ကြပါစေ လို့ ဆုမွန်ကောင်းတောင်းပါတယ်

ကျနော်တို့မိသားစုလဲ ၂၀၂၅ မှာ ကိုယ်ကျမ်းမာ စိတ်ချမ်းသာလို့ သူတော်မဟုတ် သူယုတ်မာ နဲ့ ကင်းဝေးရပြီး အမျိုးဘာသာ သာသနာ နဲ့ ရောက်ရာအရပ်မှာ အများအကျိုးကို ဆထက်တပိုး ထမ်းရွက်ဆောင်နိုင်တဲ့ ပုဂ္ဂိုလ်များ ဖြစ်ခွင့်ရပါရစီ.

အားလုံး ကျမ်းမာ ချမ်းသာလို့ ဘေးဘယာ ဝေးပြီး ဆန္ဒ နဲ့ ဘ၀ ထပ်တူကြပါစီ..

CCIE certified

Long time no post and never look back my blog  more than 1 year. 
After constantly studying and doing LAB for nearly 2 yrs  , i just Certified my first CCIE .
Really thank to my Mentor , Senior and friends who stand together during this journey .
It was really hard and under high pressure with my work and study schedule .
Now , time to review my path walked thru to get Certificate . Life will be more touch and harder after getting this Expert Lvl certificate . It still confusing in my mind , i want to Learn about DC environment and Security as future study plan also I heard from my ex boss and get encourage from him to  try for CCNA Sec Ops Certificate to realize and disgust to understand daily Sec Ops . Then i listed and bought study materials for CCNA Ops and don't know how long this journey will take ? ..... Yes .. Today is my first day for  CCNA Sec Ops Track . 

Default Distance Value Table

This table lists the administrative distance default values of the protocols that Cisco supports:

Route Source	Default Distance Values
Connected interface	0
Static route	1
Enhanced Interior Gateway Routing Protocol (EIGRP) summary route	5
External Border Gateway Protocol (BGP)	20
Internal EIGRP	90
IGRP	100
OSPF	110
Intermediate System-to-Intermediate System (IS-IS)	115
Routing Information Protocol (RIP)	120
Exterior Gateway Protocol (EGP)	140
On Demand Routing (ODR)	160
External EIGRP	170
Internal BGP	200
Unknown*	255

* If the administrative distance is 255, the router does not believe the source of that route and does not install the route in the routing table.

Source : http://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/15986-admin-distance.html

OSPF Note

·         Type 1 – Router LSA: The Router LSA is generated by each router for each area it is located. In the link-state ID you will find the originating router’s ID.

·         Type 2 – Network LSA: Network LSAs are generated by the DR. The link-state ID will be the router ID of the DR.

·         Type 3 – Summary LSA: The summary LSA is created by the ABR and flooded into other areas.

·         Type 4 – Summary ASBR LSA: Other routers need to know where to find the ASBR. This is why the ABR will generate a summary ASBR LSA which will include the router ID of the ASBR in the link-state ID field.

·         Type 5 – External LSA: also known as autonomous system external LSA: The external LSAs are generated by the ASBR.

·         Type 6 – Multicast LSA: Not supported and not used.

·         Type 7 – External LSA: also known as not-so-stubby-area (NSSA) LSA: As you can see area 1 is a NSSA (not-so-stubby-area) which doesn’t allow external LSAs (type 5). To overcome this issue we are generating type 7 LSAs instead.

Credit - Networklessons.com 

Routing Protocol Changes and Migration

Migrating from one routing protocol to another is always a disruptive change to the network.It requires careful planning to minimize the outages, and even then, they are inevitable,although their duration can be kept very low. Therefore, a routing protocol migration always requires a maintenance window.

Routing protocol migration is usually accomplished with the following steps:

Step 1. Plan the migration strategy.
Step 2. Activate the new routing protocol on all routers in the topology, raising its
administrative distance (AD) above the ADs of the current IGP. If the new IGP
is Routing Information Protocol (RIP) or Enhanced Interior Gateway Routing
Protocol (EIGRP), redistribution from the current into the new IGP has to be
configured on each router as well. The current IGP is left intact.
Step 3. Verify the new IGP’s adjacencies and optionally the working database
contents.
Step 4. Deactivate the current IGP in a gradual fashion.
Step 5. Remove the temporary settings from the new IGP.

EIGRP

===============================================================================

EIGRP topology table and the FD value

===============================================================================

Per Cisco doc:

"The feasible distance is the  best metric to reach the destination or the best metric that was known  when the route went active. This value is used in the feasibility  condition check. If the reported distance of the router (the metric  after the slash) is less than the feasible distance, the feasibility  condition is met and that path is a feasible successor."

The blue and the red number normally match, and that is the FD.

R1#sh ip eigrp topology  10.6.6.0/24

EIGRP-IPv4 Topology Entry for AS(1)/ID(10.1.1.1) for 10.6.6.0/24

  State is Passive, Query origin flag is 1, 1 Successor(s), FD is 161280

  Descriptor Blocks:

  10.0.13.3 (FastEthernet0/0), from 10.0.13.3, Send flag is 0x0

      Composite metric is (161280/158720), route is Internal

      Vector metric:

        Minimum bandwidth is 100000 Kbit

        Total delay is 5300 microseconds

        Reliability is 255/255

        Load is 1/255

        Minimum MTU is 1500

        Hop count is 3

        Originating router is 10.6.6.6

R1#sh ip eigrp topology

EIGRP-IPv4 Topology Table for AS(1)/ID(10.1.1.1)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,

       r - reply Status, s - sia Status

P 10.6.6.0/24, 1 successors, FD is 161280

        via 10.0.13.3 (161280/158720), FastEthernet0/0

        via 172.16.15.5 (670720/158720), Serial1/0

R1#sh ip route 10.6.6.6

D        10.6.6.0/24 [90/161280] via 10.0.13.3, 00:21:14, FastEthernet0/0

      172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks

=====================================================

There are several reasons why the EIGRP neighbor router(s) might not respond to the Query. Common reasons for this include the following:

1.       The neighbor router’s CPU is overloaded and the router either cannot respond in time or is even unable to process all incoming packets including the EIGRP packets.

2.       Quality issues on the link are causing packets to be lost.

3.       Low-bandwidth links are congested and packets are being delayed or dropped.

4.       The network topology is excessively large or complex, either requiring the Query to propagate to a significant depth or causing an inordinate number of prefixes to be impacted by a single link or node failure.

===================================================

How to Setup the Switching Lab With Web IOU v 22

Normally we used packet tracer and GNS 3 for Routing & switching Lab and it will be okay for routing but some switching features can’t making with this .
Here, I used Web IOU v 22 for Switching Lab , it can be do almost switching features as like real devices .
To Setup the IOU, we will need VM ware like Virtual Box or VM workstation that can be easy download from Internet .
Here isthe some Ovf for IOU VM and useful link for easy setup.

At first , need to import the ovf to VM ware workstation . 

Figure 1. Importing IOU ovf to VMWare

                                   

  Figure 2 : Installation of VM machine

              Installation will take 5 – 10 mins based on your computer performance.

Figure 3 : Now Cent OS 6.4 is installing

Figure 4 : Login page for Cent OS

Use browser and Access 192.168.138.128, the IP address will base differ based on machine .

Figure 5 : Login page Of IOU

 Her You will see a lot ready-made setup lab , If  you want clear Page can delete all exiting lab using trash Icon

Figure 6 : How to create new Own Lab

 To create a new Own Lab, click the new lab icon as shown in figure:

Figure 7 : Key in the Lab Information

Figure 8 : Adding Net map Inter Switch Link

Here, I added 12 Interswitch link for full mesh topology , If you want to add more switches  , can add more links or want just want only 4 switches can copy/paste the below Net map .

1:0/0 2:0/0

1:0/1 2:0/1

1:0/2 3:0/0

1:0/3 3:0/1

1:1/0 4:0/0

1:1/1 4:0/1

2:0/2 3:0/2

2:0/3 3:0/3

2:1/0 4:0/2

2:1/1 4:0/3

3:1/0 4:1/0

3:1/1 4:1/1

Figure 9 : Choosing IOS for Switch

Here I Choose the L2 IOS for switches images  assign physical requirements for all switches . If you want to setup Routing lab can use the L3 IOS .

Add caption

 ·         R Okay , Now successfully setup the switch Lab . J

 Start the Switches and Access with Console Icon.

Add caption

Can check the Physical Link and Diagram for your reference.

Accessing with Telnet  , as in figure we can also setup telnet connect as 192.168.138.128:2001 .

Here we can add the any labs file as we want .

·         Here we can add the any labs file as we want .

C Here can play all switches with our terminal. HOPE YOU ENJOY .

    Credit : All the Lab info are I learned from Internet and created this blog post for education Purpose .Collected download for better aces in One place . If have anything that have incorrect or not proper information is my fault. Thank you very much and Cheer All 

Basic MPLS L3 VPN

This lab is according to A small MPLS VPN tutorial (by Alexandre Ribeiro, alexandregomesribeiro@gmail.com) pdf file.

Step1: IGP configuration inside the MPLS backbone
Step2: Basic MPLS configuration
Step3: VRF configuration
Step4: MP-BGP configuration
Step5: IGP configuration between CE and PE
Step6: Redistribute IGP route between CE and PE to MP-BGP
Step7: Verify connectivity between CEs

Using IOS - (C3660-JK9O3S-M)

MPLS VPN Cheatsheet

Basic VPN

Detail Config ::

P_router

P_router#sh running-config 
Building configuration...

Current configuration : 1109 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname P_router
!
boot-start-marker
boot-end-marker
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
ip cef
no ip domain lookup
!      
!
mpls label range 100 199
!
interface Loopback0
 ip address 172.16.1.1 255.255.255.255
 ip ospf network point-to-point
!
interface FastEthernet0/0
 description P_router_to_PE_A
 ip address 192.168.1.2 255.255.255.252
 duplex auto
 speed auto
 mpls ip
!
interface FastEthernet0/1
 description P_router_to_PE_B
 ip address 192.168.1.5 255.255.255.252
 duplex auto
 speed auto
 mpls ip
!
router ospf 1
 log-adjacency-changes
 network 172.16.0.0 0.0.255.255 area 0
 network 192.168.1.0 0.0.0.255 area 0
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
end
===================================================================

PE_A#sh running-config
Building configuration...

Current configuration : 2171 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname PE_A
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
ip cef
no ip domain lookup     
ip vrf siteA
 rd 100:1
 route-target export 100:1
 route-target import 100:1
!
ip vrf siteB
 rd 100:2
 route-target export 100:2
 route-target import 100:2
!
mpls label range 200 299
!
interface Loopback0
 ip address 172.16.1.2 255.255.255.255
 ip ospf network point-to-point
!
interface FastEthernet0/0
 description PE_A_to_P_router
 ip address 192.168.1.1 255.255.255.252
 duplex auto
 speed auto
 mpls ip
!
interface FastEthernet0/1
 description PE_A_to_SiteA1
 ip vrf forwarding siteA
 ip address 10.1.1.2 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet1/0
 description PE_A_to_SiteB1
 ip vrf forwarding siteB
 ip address 10.1.1.2 255.255.255.252
 duplex auto
 speed auto
!
router ospf 1
 log-adjacency-changes
 network 172.16.0.0 0.0.255.255 area 0
 network 192.168.1.0 0.0.0.255 area 0
!
router rip
 !
 address-family ipv4 vrf siteB
 redistribute bgp 100 metric 1
 network 10.0.0.0
 no auto-summary
 version 2
 exit-address-family
 !
 address-family ipv4 vrf siteA
 redistribute bgp 100 metric 1
 network 10.0.0.0
 no auto-summary
 version 2
 exit-address-family
!
router bgp 100
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 172.16.1.3 remote-as 100
 neighbor 172.16.1.3 update-source Loopback0
 !
 address-family vpnv4
 neighbor 172.16.1.3 activate
 neighbor 172.16.1.3 send-community extended
 exit-address-family
 !
 address-family ipv4 vrf siteB
 redistribute rip metric 1
 no synchronization
 exit-address-family
 !
 address-family ipv4 vrf siteA
 redistribute rip metric 1
 no synchronization
 exit-address-family
!
no ip http server
no ip http secure-server
!

control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
======================================================================

PE_B#sh running-config 
Building configuration...

Current configuration : 2143 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname PE_B
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
ip cef
no ip domain lookup
!     
ip vrf siteA
 rd 100:1
 route-target export 100:1
 route-target import 100:1
!
ip vrf siteB
 rd 100:2
 route-target export 100:2
 route-target import 100:2
!
!
mpls label range 300 399
!
interface Loopback0
 ip address 172.16.1.3 255.255.255.255
 ip ospf network point-to-point
!
interface FastEthernet0/0
 description PE_B_to_P_router
 ip address 192.168.1.6 255.255.255.252
 duplex auto
 speed auto
 mpls ip
!
interface FastEthernet0/1
 description PE_B_to_SiteB2
 ip vrf forwarding siteA
 ip address 10.1.1.6 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet1/0
 ip vrf forwarding siteB
 ip address 10.1.1.6 255.255.255.252
 duplex auto
 speed auto
!
router ospf 1
 log-adjacency-changes
 network 172.16.0.0 0.0.255.255 area 0
 network 192.168.1.0 0.0.0.255 area 0
!
router rip
 !
 address-family ipv4 vrf siteB
 redistribute bgp 100 metric 1
 network 10.0.0.0
 no auto-summary
 version 2
 exit-address-family
 !
 address-family ipv4 vrf siteA
 redistribute bgp 100 metric 1
 network 10.0.0.0
 no auto-summary
 version 2
 exit-address-family
!
router bgp 100
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 172.16.1.2 remote-as 100
 neighbor 172.16.1.2 update-source Loopback0
 !
 address-family vpnv4
 neighbor 172.16.1.2 activate
 neighbor 172.16.1.2 send-community extended
 exit-address-family
 !
 address-family ipv4 vrf siteB
 redistribute rip metric 1
 no synchronization
 exit-address-family
 !
 address-family ipv4 vrf siteA
 redistribute rip metric 1
 no synchronization
 exit-address-family
!
no ip http server
no ip http secure-server
!

control-plane

line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
end
================================================================

Site_A1#sh running-config 
Building configuration...

Current configuration : 948 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Site_A1
!
boot-start-marker
boot-end-marker
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
interface Loopback0
 ip address 192.168.1.1 255.255.255.255
!
interface FastEthernet0/0
 description SiteA1_to_PE_A
 ip address 10.1.1.1 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router rip
 version 2
 network 10.0.0.0
 network 192.168.1.0
 no auto-summary
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
=============================================================
Site_A2#sh running-config 
Building configuration...

Current configuration : 948 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Site_A2
!
boot-start-marker
boot-end-marker
!
interface Loopback0
 ip address 192.168.2.1 255.255.255.255
!
interface FastEthernet0/0
 description SiteA2_to_PE_A
 ip address 10.1.1.5 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router rip
 version 2
 network 10.0.0.0
 network 192.168.2.0
 no auto-summary
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
==================================================================
Site_B1#sh running-config 
Building configuration...

Current configuration : 927 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Site_B1
!
boot-start-marker
boot-end-marker
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
!
ip cef
no ip domain lookup
!
interface Loopback0
 ip address 192.168.1.1 255.255.255.255
!
interface FastEthernet0/0
 description SiteB1_to_PE_A
 ip address 10.1.1.1 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router rip
 version 2
 network 10.0.0.0
 no auto-summary
!
no ip http server
no ip http secure-server
!
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
================================================================
Site_B2#sh running-config 
Building configuration...

Current configuration : 927 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Site_B2
!
boot-start-marker
boot-end-marker
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
!
ip cef
no ip domain lookup
!
interface Loopback0
 ip address 192.168.2.1 255.255.255.255
!
interface FastEthernet0/0
 description SiteB2_to_PE_B
 ip address 10.1.1.5 255.255.255.252
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router rip
 version 2
 network 10.0.0.0
 no auto-summary
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end

My Study Techniques

၂၀၁၀ ေလာက္မွာ သူငယ္ခ်င္း CCIE တစ္ေယာက္နဲ ့ေတြ ့ျဖစ္ခဲ့ျပီး ေနာက္ပုိင္းမွာ က်ေနာ့္အတြက္
Cisco Certification Trend ကုိ စိတ္၀င္စားခဲ့ပါတယ္ .. အဲ့အရင္က သိခဲ့တယ္ ဆုိခဲ့ေပမယ့္ သိပ္ျပီး စိတ္၀င္တစားေတာ့ မရွိခဲ့ပါဘူး.. ဒါေပမယ့္ ေနာက္ပုိင္းမွာ တေျဖးေျဖး လုပ္ငန္းခြင္အတြက္ လုိအပ္တဲ့
လက္မွတ္ ဆုိတာ လုိအပ္ခ်က္ တစ္ခုလုိ ့ ျမင္လာပါတယ္ ။ အနည္းဆုံးေတာ့ CV ကုိ ကုိယ့္ CV ကုိ အေရြးခံရဖုိ ့ေတာ့ အခြင့္အလမ္းမ်ားလာမယ္လုိ ့ လုိခဲ့ပါတယ္ ။။
ပထမဦးဆံုး CCNA ကေတာ့ ၂ နွစ္ေလာက္ ၾကာခဲ့ပါတယ္ ။ ဘာလုိ ့လဲ ဆုိေတာ့ ေလ့လာပုံ ေလ့လာနည္း
လြဲခဲ့တာေၾကာင့္ အဲေလာက္ ၾကာခဲ့တာလုိ ့ ထင္ပါတယ္ ။ လုပ္ငန္းခြင္ အေတြ ့အၾကဳံနဲ ့ဆုိင္မယ္ ထင္ပါတယ္
ေနာက္ပုိင္း CCNP ကုိ ၂ နွစ္အတြင္းမွာ ျပီးနုိင္မယ္လုိ ့ မွန္းထားပါတယ္ ။ Paper Certified မျဖစ္ခ်င္တာေၾကာင့္လဲ တတ္နုိင္သမွ် ကို္ယ့္ဘက္ မွတ္သားနုိင္သေလာက္ ေလ့လာျပီး ေျဖဆုိခဲ့ပါတယ္
အခု စာေရးေနခ်ိန္မွာ Routing နဲ ့ Switching ကုိ ေျဖျပီးပါျပီ ။ လာမယ့္လေလာက္မွာ Tshoot ေျဖနိင္မယ္လုိ ့
ထင္ပါတယ္ ။ က်ေနာ္ကေတာ့ CCNP မွာ Self study လုပ္ျဖစ္တယ္ ။ အလုပ္က စီနီယာေတြရဲ ့ သင္ၾကားျပသမႈလဲ အမ်ားၾကီး ပါပါတယ္ . ဂရုေတြမွာ ပါ၀င္ေဆြးေႏြးတာကလဲ အက်ဳိးအမ်ားၾကီးရွိပါတယ္
ေဆြးေႏြးျခင္းက ကုိယ္မျမင္တဲ့ ေက်ာ္သြားမိတဲ့ Concept ေတြကုိ ျမင္မိေစပါတယ္ ။ က်ေနာ္ ့အတြက္ အဓိက
Study Material ေတြက CBT Nugget က Video Lessons ေတြနဲ ့ Cisco Official Press Book ေတြပါ ၊
ေနာက္ျပီး GNS3 vault , How to Master , Note ေတြက အေတာ္ေလး ထိေရာက္မယ္လုိ ့ ယူဆပါတယ္
တစ္ေန ့စာဖတ္ျပီးရင္ ဒီေန ့ ငါ ဘာသိလုိက္လဲ ကုိယ္ကုိကုိယ္ ျပန္ျပီးေတာ့ ဆန္းစစ္ၾကည့္ပါတယ္ ။
ဒါေပမယ့္ ေန ့စဥ္ အကၽႊမ္းတ၀င္ မျဖစ္တဲ့ ကိစၥေတြက ေမ့သြားတတ္ပါတယ္ ။အနည္းဆုံး ေနာက္တစ္ခါ ၾကည့္ရင္ေတာ့ လြယ္တာေပါ့ ။ ေနာက္ျပီး စာျပန္ရွာရမယ္ ဆုိရင္ေတာင္ ဘယ္နားမွာ ရွိတယ္ဆုိတာေတာ့
သိျဖစ္မယ္ ထင္ပါတယ္ ။ စာၾကည့္တာေတာ့ ညပုိင္းမွာ ၾကည့္ျဖစ္တယ္ ။ Lab ကေတာ့ ပုံမွန္ မဟုတ္ပဲ
ေတာ္ေတာ္မ်ားမ်ားလုပ္ၾကည့္ျဖစ္တယ္ ။ လုပ္ေနရင္းနဲ ့ ပုိသိလာရတဲ့ အေၾကာင္းေတြလဲ ရွိပါတယ္
Lab ကေတာ့ ရုံးက ေပးထားတဲ့ Lab ကေတာ့ အေတာ္ေလး အဆင္ေျပပါတယ္ ။ အေဆာင္ကုိ ျပန္ေ၇ာက္ရင္ေတာ့ GNS 3 က က်ေနာ့္ အေဖာ္မြန္ပါပဲ..
ဆက္ျပီးလဲ ေလ့လာစရာေတြ အမ်ားၾကီး ရွိေနပါေသးပါတယ္ . ...ဒီထက္လဲ နားလည္ ကၽႊမ္းက်င္တဲ့ အင္ဂ်င္နီယာ တစ္ေယာက္ ျဖစ္ဖုိ ့ၾကုိးစားေနပါတယ္ .....

Basic VRF Lab

Step 1 : Assign Ip address at Fa 0/0 of R1 and R2.
Step 2 : Configure Vrf R1 on router R1 and add Loopback 0 and 11 to this vrf
Step 3 : Configure Vrf R2 on router R2 and add Loopback 0 and 11 to this vrf
Step 4 : Configure the tunnel1 interface on both routers. Make sure the source and destination IP addresses of the Fastethernet link are used for this.
Step 5 : Make sure the tunnel1 interface is added to VRF R1 and R2 .
Step 6 : Configure the 192.168.1.0 /24 subnet on the tunnel1 interface.
Step 7 : Configure EIGRP AS 100 as the routing protocol for these VRFs. Make sure both routers can ping each others loopback interfaces.

Note :::::  interfaces must be assigned to a VRF before being addressed; assigning an interface to a VRF wipes any IP addresses already configured on that interface.

:::::Task To do:::::

sh ip route
sh ip route vrf
R1#ping 2.2.2.2
R1#ping vrf R1 2.2.2.2
R1#ping vrf R1 2.2.2.2 loopback 0

================================================================
#######Devices Config ######

================================================================
::::::::::::::::R1:::::::::::::

R1#sh running-config
Building configuration...

Current configuration : 1275 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
!
ip cef
no ip domain lookup
!       
ip vrf R1
!     
interface Loopback0
 ip vrf forwarding R1
 ip address 1.1.1.1 255.255.255.0
!
interface Loopback11
 ip vrf forwarding R1
 ip address 11.11.11.11 255.255.255.0
!
interface Tunnel1
 ip vrf forwarding R1
 ip address 192.168.1.1 255.255.255.0
 tunnel source FastEthernet0/0
 tunnel destination 192.168.100.2
!
interface FastEthernet0/0
 ip address 192.168.100.1 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router eigrp 100
 no auto-summary
 !
 address-family ipv4 vrf R1
 network 1.0.0.0
 network 11.0.0.0
 network 192.168.1.0
 auto-summary
 autonomous-system 100
 exit-address-family
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end

=================================================================
::::::::::::::::::::::R2:::::::::::::::::::::::::::
R2#sh running-config
Building configuration...

Current configuration : 1275 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
no aaa new-model
memory-size iomem 5
no ip icmp rate-limit unreachable
ip tcp synwait-time 5
!
ip cef
no ip domain lookup
!       
ip vrf R2
!  
interface Loopback0
 ip vrf forwarding R2
 ip address 2.2.2.2 255.255.255.0
!
interface Loopback11
 ip vrf forwarding R2
 ip address 22.22.22.22 255.255.255.0
!
interface Tunnel1
 ip vrf forwarding R2
 ip address 192.168.1.2 255.255.255.0
 tunnel source FastEthernet0/0
 tunnel destination 192.168.100.1
!
interface FastEthernet0/0
 ip address 192.168.100.2 255.255.255.0
 duplex auto
 speed auto
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
router eigrp 100
 no auto-summary
 !
 address-family ipv4 vrf R2
 network 2.0.0.0
 network 22.0.0.0
 network 192.168.1.0
 auto-summary
 autonomous-system 100
 exit-address-family
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
end
======================================================================
Reference ::::::::::: GNS3Vault :: VRF Routing
======================================================================

Different Between IPv4 and IPv6

BGP Case Study

Objectives

• Plan, design, and implement the International Travel Agency core network.
• Plan, design, and implement the Travel Data Providers network.
• Allow the networks to communicate via BGP.
• Verify that all implementations are operational and functional according to the guidelines.

Requirements

1. Use the addressing scheme shown in the diagram.
2. Configure the ITA network to be in EIGRP AS 65001.
3. Configure the TDP network to be in EIGRP AS 65002.
4. Disable automatic summarization in both EIGRP domains.
5. Configure the ITA network to be in BGP AS 65001, and the TDP network to be in BGP AS 65002.
6. Advertise the 192.168.14.0/30 and 192.168.34.0/30 networks in both EIGRP autonomous systems.
7. Configure the interfaces on the border routers between the two EIGRP autonomous systems, so they do not send EIGRP packets.
8. All routers will be participating in BGP. Configure all routers for a full mesh of IBGP peers in each system.
9. Peer R1 and R2 using loopback addresses, not their directly connected interfaces.
10. Advertise all loopback interfaces into the BGP process, except on R2, where the only loopback advertised should be loopback 2.
11. On R2, create a static summary route for the rest of its loopback interfaces and advertise this static route in BGP.
12. R4 should send a summary route to ITA representing all the R4 loopback interfaces.
13. R4 should prefer the path to ITA networks via the Ethernet link between R1 and R4. Accomplish this by modifying the MED advertised to TDP.
14. Routers in the ITA AS should prefer the path to TDP networks via the Ethernet link between R1 and R4. Accomplish this by modifying the local preference of routes being advertised in from TDP.

Using the AS_PATH Attribute

Objectives


• Use BGP commands to prevent private AS numbers from being advertised to the outside world.
• Use the AS_PATH attribute to filter BGP routes based on their source AS numbers.


Background

The International Travel Agency’s ISP has been assigned an AS number of 300. This provider uses BGP to exchange routing information with several customer networks. Each customer network is assigned an AS number from the private range, such as AS 65000. Configure the ISP router to remove the private AS numbers from the AS Path information of CustRtr. In addition, the ISP would like to prevent its customer networks from receiving route information from International Travel Agency’s AS 100. Use the AS_PATH attribute to implement this policy.

Step 1: Prepare the routers for the lab.

Step 2: Configure the hostname and interface addresses.

Step 3: Configure BGP.

Step 4: Remove the private AS.

a. Display the SanJose routing table using the show ip route command. SanJose should have a route to both 10.2.2.0 and 10.3.3.0. Troubleshoot if necessary.

Ping the 10.3.3.1 address from SanJose.
Q : Why does this fail?

Ans : This fails because SanJose sources the ping with its closest connected interface s0/0/0 with IP address 192.168.1.5. CustRtr does not have a route back to that interface, so the ping replies cannot return to SanJose.

Configure ISP to strip the private AS numbers from BGP routes exchanged with SanJose using the following commands.

Step 5: Use the AS_PATH attribute to filter routes.
As a final configuration, use the AS_PATH attribute to filter routes based on their origin. In a complex environment, you can use this attribute to enforce routing policy. In this case, the provider router, ISP, must be configured so that it does not propagate routes that originate from AS 100 to the customer router CustRtr.
AS-path access lists are read like regular access lists. The statements are read sequentially, and there is an implicit deny at the end. Rather than matching an address in each statement like a conventional access list, AS path access lists match on something called a regular expression. Regular expressions are a way of matching text patterns and have many uses. In this case, you will be using them in the AS path access list to match text patterns in AS paths.

For more details on configuring regular expressions on Cisco routers, see:

http://www.cisco.com/en/US/docs/ios/12_2/termserv/configuration/guide/tcfaapre_ps1835_TSD_Products_Configuration_Guide_Chapter.html

Final Device Config :

=========================================================================
SanJose#sh running-config
Building configuration...

Current configuration : 1167 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname SanJose
!
boot-start-marker
boot-end-marker
!
no aaa new-model
!
resource policy
!
memory-size iomem 5
ip subnet-zero
no ip icmp rate-limit unreachable
ip cef
ip tcp synwait-time 5
!        
no ip domain lookup
!
interface Loopback0
 ip address 10.1.1.1 255.255.255.0
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 192.168.1.5 255.255.255.252
 clock rate 128000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 shutdown
 clock rate 2000000
!
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 network 10.1.1.0 mask 255.255.255.0
 neighbor 192.168.1.6 remote-as 300
 no auto-summary
!
ip classless
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end

=========================================================================
CustRtr#sh running-config
Building configuration...

Current configuration : 1170 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname CustRtr
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
memory-size iomem 5
ip subnet-zero
no ip icmp rate-limit unreachable
ip cef
ip tcp synwait-time 5
!        
no ip domain lookup
!!
interface Loopback0
 ip address 10.3.3.1 255.255.255.0
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 172.24.1.18 255.255.255.252
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 shutdown
 clock rate 2000000
!        
router bgp 65000
 no synchronization
 bgp log-neighbor-changes
 network 10.3.3.0 mask 255.255.255.0
 neighbor 172.24.1.17 remote-as 300
 no auto-summary
!
ip classless
!
no ip http server
no ip http secure-server
!
control-plane
!
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
=========================================================================

ISP#sh running-config
Building configuration...

Current configuration : 1461 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname ISP
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
memory-size iomem 5
ip subnet-zero
no ip icmp rate-limit unreachable
ip cef
ip tcp synwait-time 5
!       
no ip domain lookup
!
interface Loopback0
 ip address 10.2.2.1 255.255.255.0
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 192.168.1.6 255.255.255.252
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 172.24.1.17 255.255.255.252
 clock rate 128000
!
interface Serial0/2
 no ip address
 shutdown
 clock rate 2000000
!
interface Serial0/3
 no ip address
 shutdown
 clock rate 2000000
!
router bgp 300
 no synchronization
 bgp log-neighbor-changes
 network 10.2.2.0 mask 255.255.255.0
 neighbor 172.24.1.18 remote-as 65000
 neighbor 192.168.1.5 remote-as 100
 neighbor 192.168.1.5 remove-private-as
 no auto-summary
!
ip classless
!
ip as-path access-list 1 deny ^100$
ip as-path access-list 1 permit .*
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
=========================================================================

Configuring BGP with Default Routing

Objectives

• Configure BGP to exchange routing information with two ISPs.

Step 1: Prepare the routers for the lab.

Step 2: Configure the hostname and interface addresses.

Step 3: Configure BGP on the ISP routers

Step 4: Configure BGP on the ITA boundary router.

Step 5: Verify BGP on the routers.

Q : What is the local router ID?

Ans : The local router ID is 192.168.1.1.

Q : Which table version is displayed?

Ans : The table version displayed is 5.
An asterisk (*) next to a route indicates that it is valid. An angle bracket (>) indicates that the route has been selected as the best route.

Q : From ISP1, what is the path to network 172.16.1.0/24?

Ans : The path is through AS 100 (ITA) and AS 300 (ISP2).

Q: Which table version is displayed? Why?

Ans : The table version displayed is an increment of the last one, which is 6 in the example. The shutdown command causes a routing table update, so the version should be one higher than the last.

Q : What happened to the route for network 10.1.1.0/24?

Ans : It is no longer in the BGP table because interface Lo0 on ISP1 is down.

Q : Based on the output of this command, what is the BGP state between this router and ISP2?

Ans : The BGP state is established.

Q : How long has this connection been up?
Ans : The connection has been up for 00:16:00.

Step 6: Configure route filters.

If ITA advertises a route belonging to ISP1, ISP2 installs that route in its table. ISP2 might then attempt to route transit traffic through the ITA. Configure the ITA router so that it advertises only ITA networks 192.168.0.0 and 192.168.1.0 to both providers.

Note: The clear ip bgp * command is disruptive because it completely resets all BGP adjacencies. This is acceptable in a lab environment but could be problematic in a production network. Instead, if only a change of inbound/outbound routing policies is to be performed, it is sufficient to issue the clear ip bgp * in or clear ip bgp * out commands. These commands perform only a new BGP database synchronization without the disruptive effects of a complete BGP adjacency reset. All current Cisco IOS versions support the route refresh capability that replaces the inbound soft reconfiguration feature that previously had to be configured on a per-neighbor basis.

Step 7: Configure primary and backup routes using floating static routes.

With bidirectional communication established with each ISP via BGP, configure the primary and backup routes. This can be done with floating static routes or BGP.

Step 8: Configure primary and backup routes using a default network and a static route.

Another method for configuring primary and backup routes is to use the ip default-network command instead of a 0.0.0.0/0 route.

Q : Should ISP1 and ISP2 be able to ping all networks in the topology?'

Ans : No. Router ITA has been configured with route filters and does not advertise the ISP1 networks to ISP2 and vice versa. The ITA router advertises only ITA networks 192.168.0.0 and 192.168.1.0 to both providers. Pings from ISP1 to any of the ISP2 172.16.x.x networks will fail. Pings from ISP2 to any of the ISP1 10.x.x.x networks will fail.


Note: Another option for setting up default routing is to inject a default route via BGP. The following example configures the ISP1 router to inject a default route to itself that can be used by the ITA router:

Run the following Tcl script on router ITA to verify connectivity.

ITA# tclsh
foreach address {
10.0.0.1
10.0.0.2
10.1.1.1
172.16.0.1
172.16.0.2
172.16.1.1
192.168.0.1
192.168.1.1
192.168.100.1
} {
ping $address }


Final Device Config :
ISP1#sh running-config
Building configuration...

Current configuration : 1272 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname ISP1
!
boot-start-marker
boot-end-marker
!
no aaa new-model
!
resource policy
!
memory-size iomem 5
ip subnet-zero
ip cef
!
no ip domain lookup
ip domain name lab.local
!
!        
interface Loopback0
 description ISP1 Internet Network
 ip address 10.1.1.1 255.255.255.0
!
interface Loopback1
 ip address 192.168.100.1 255.255.255.0
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 description ISP1 -> ITA
 ip address 10.0.0.1 255.255.255.252
 clock rate 128000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 shutdown
 clock rate 2000000
!
router bgp 200
 no synchronization
 bgp log-neighbor-changes
 network 10.1.1.0 mask 255.255.255.0
 network 192.168.100.0
 neighbor 10.0.0.2 remote-as 100
 no auto-summary
!
ip classless
!
no ip http server
no ip http secure-server
    
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
=======================================================
ISP2#sh running-config
Building configuration...

Current configuration : 1196 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname ISP2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
memory-size iomem 5
ip subnet-zero
ip cef
!
no ip domain lookup
ip domain name lab.local
!       
interface Loopback0
 description ISP2 Internet Network
 ip address 172.16.1.1 255.255.255.0
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 description ISP2 -> ITA
 ip address 172.16.0.1 255.255.255.252
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 shutdown
 clock rate 2000000
!
router bgp 300
 no synchronization
 bgp log-neighbor-changes
 network 172.16.1.0 mask 255.255.255.0
 neighbor 172.16.0.2 remote-as 100
 no auto-summary
!
ip classless
!
no ip http server
no ip http secure-server
!
control-plane
!
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
!
end
========================================================
ITA#sh running-config
Building configuration...

Current configuration : 1573 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname ITA
!
boot-start-marker
boot-end-marker
!
no aaa new-model
!
resource policy
!
memory-size iomem 5
ip subnet-zero
ip cef
!
no ip domain lookup
ip domain name lab.local
!     
interface Loopback0
 description Core router network link 1
 ip address 192.168.0.1 255.255.255.0
!
interface Loopback1
 description Core router network link 2
 ip address 192.168.1.1 255.255.255.0
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 description ITA -> ISP1
 ip address 10.0.0.2 255.255.255.252
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 description ITA -> ISP2
 ip address 172.16.0.2 255.255.255.252
 clock rate 128000
!
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 network 192.168.0.0
 network 192.168.1.0
 neighbor 10.0.0.1 remote-as 200
 neighbor 10.0.0.1 distribute-list 1 out
 neighbor 172.16.0.1 remote-as 300
 neighbor 172.16.0.1 distribute-list 1 out
 no auto-summary
!
ip classless
ip default-network 192.168.100.0
ip route 0.0.0.0 0.0.0.0 172.16.0.1 220
!      
no ip http server
no ip http secure-server
!
access-list 1 permit 192.168.0.0 0.0.1.255
control-plane
line con 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line aux 0
 exec-timeout 0 0
 privilege level 15
 logging synchronous
line vty 0 4
 login
!
end
=========================================================