cciejourney: 2012

I would like to introduce how is BGP mpls configuration between service provider network and customer end. There is 8 routers included in my topology. R1 and R2 is belong to Customer Edge router. R7 and R8 is belong to Customer Edge Router as well.
R3 and R6 is Service Provider PE ( Provider Edge router especially running MP-BGP configuration). R4 and R5 is Provider router which is running their own ospf protocol in order to be reachable during service provider network.

MPLS - BGP Par1 (Static Route on CE)

R3 Configuration for MP-BGP
=================

sh run | s bgp
router bgp 1
no synchronization
bgp log-neighbor-changes
neighbor 150.1.6.6 remote-as 1
neighbor 150.1.6.6 update-source Loopback0
neighbor 150.1.6.6 next-hop-self
no auto-summary
!
address-family vpnv4
neighbor 150.1.6.6 activate
neighbor 150.1.6.6 send-community both
exit-address-family
!
address-family ipv4 vrf PHILIP
redistribute connected
redistribute static
no synchronization
exit-address-family
!
address-family ipv4 vrf OCBC
redistribute connected
redistribute static
no synchronization
exit-address-family
R3#

R6 Configuration for MP-BGP

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

R6# sh run | s bgp

router bgp 1

no synchronization

bgp log-neighbor-changes

neighbor 150.1.3.3 remote-as 1

neighbor 150.1.3.3 next-hop-self

no auto-summary

address-family vpnv4

neighbor 150.1.3.3 activate

neighbor 150.1.3.3 send-community both

exit-address-family

address-family ipv4 vrf PHILIP

redistribute connected

redistribute static

no synchronization

exit-address-family

address-family ipv4 vrf OCBC

redistribute connected

redistribute static

no synchronization

exit-address-family

R6#

There is vrf connectivity as follow:

R1 can able to reach R7

R2 can able to reach R8.

R1 route distinguisher is 1:1

R2 route distinguisher is 1:2

R7 route distinguisher is 1:7

R8 route distinguisher is 1:8

mpls configuration basic is to learn how to import and export rd from one PE to another PE.

R3#sh run | s vrf
ip vrf OCBC
rd 1:1
route-target export 1:1
route-target import 1:7
ip vrf PHILIP
rd 1:2
route-target export 1:2
route-target import 1:8
ip vrf forwarding OCBC
ip vrf forwarding PHILIP
address-family ipv4 vrf PHILIP
address-family ipv4 vrf OCBC
ip route vrf OCBC 150.1.1.1 255.255.255.255 10.1.37.1
ip route vrf PHILIP 150.1.2.2 255.255.255.255 10.1.38.1

R3#sh ip bgp vpnv4 all
BGP table version is 49, local router ID is 150.1.3.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 1:1 (default for vrf OCBC)
*> 10.1.37.0/24 0.0.0.0 0 32768 ?
*>i10.1.45.0/24 150.1.6.6 0 100 0 ?
*> 150.1.1.1/32 10.1.37.1 0 32768 ?
*>i150.1.7.7/32 150.1.6.6 0 100 0 ?
Route Distinguisher: 1:2 (default for vrf PHILIP)
*> 10.1.38.0/24 0.0.0.0 0 32768 ?
*>i10.1.46.0/24 150.1.6.6 0 100 0 ?
*> 150.1.2.2/32 10.1.38.1 0 32768 ?
*>i150.1.8.8/32 150.1.6.6 0 100 0 ?
Route Distinguisher: 1:7
*>i10.1.45.0/24 150.1.6.6 0 100 0 ?
*>i150.1.7.7/32 150.1.6.6 0 100 0 ?
Route Distinguisher: 1:8
*>i10.1.46.0/24 150.1.6.6 0 100 0 ?
*>i150.1.8.8/32 150.1.6.6 0 100 0 ?
R3#

R6#sho run | s vrf
ip vrf OCBC
rd 1:7
route-target export 1:7
route-target import 1:1
ip vrf PHILIP
rd 1:8
route-target export 1:8
route-target import 1:2
ip vrf forwarding OCBC
ip vrf forwarding PHILIP
address-family ipv4 vrf PHILIP
address-family ipv4 vrf OCBC
ip route vrf OCBC 150.1.7.7 255.255.255.255 10.1.45.2
ip route vrf PHILIP 150.1.8.8 255.255.255.255 10.1.46.2

R6#sh ip bgp vpnv4 all
BGP table version is 57, local router ID is 150.1.6.6
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 1:1
*>i10.1.37.0/24 150.1.3.3 0 100 0 ?
*>i150.1.1.1/32 150.1.3.3 0 100 0 ?
Route Distinguisher: 1:2
*>i10.1.38.0/24 150.1.3.3 0 100 0 ?
*>i150.1.2.2/32 150.1.3.3 0 100 0 ?
Route Distinguisher: 1:7 (default for vrf OCBC)
*>i10.1.37.0/24 150.1.3.3 0 100 0 ?
*> 10.1.45.0/24 0.0.0.0 0 32768 ?
*>i150.1.1.1/32 150.1.3.3 0 100 0 ?
*> 150.1.7.7/32 10.1.45.2 0 32768 ?
Route Distinguisher: 1:8 (default for vrf PHILIP)
*>i10.1.38.0/24 150.1.3.3 0 100 0 ?
*> 10.1.46.0/24 0.0.0.0 0 32768 ?
*>i150.1.2.2/32 150.1.3.3 0 100 0 ?
*> 150.1.8.8/32 10.1.46.2 0 32768 ?
R6#

Here is the step to upgrade extreme xos image. Extreme switch is rarely used in enterprise network. Now some techinical engineer know only how to handle and configure the commands on it. By reading the steps on my blog, reader will easily learn how to upgrade firmware image on extreme within 5 minutes.

There are two partition in extreme switch in order to store extreme xos firmware image file. Before upgrading firmware image, you have to make sure the firmware image file will be downloaded into primary partition or secondary partition. I prefer to download secondary partition first and then set secondary partition as boot image. So we don't need to worry for crashing downloaded process of new image. If something is wrong with downloaded new image, we still have primary partition which is already running with previous firmware image .

1. Download image to secondary partition

# download image 172.16.41.1 summitX-12.6.1.3.xos vr "VR-Default" secondary

2. Set secondary partition as boot image

# use image secondary