Just another Cisco blog
Posts tagged CCIP
Policy-Based Routing Tutorial
Nov 18th
A friend asked me how to implement Policy-Based Routing (PBR) yesterday, after explaining it to him I thought it’d be nice to write a quick tutorial on here. PBR allows you to change a packet’s path based on different criteria. In this post I will use my friend’s scenario. We have a business with two internet connections, the powers that be have decided to use ISP B for all outbound SMTP traffic. Here’s our topology:
Let’s go through the config:
R1
hostname R1 ! ip access-list ext MATCH_SMTP 10 permit tcp 192.168.1.0 0.0.0.255 any eq 25 20 deny ip any any ! route-map SMTP_ISPB permit 10 match ip address MATCH_SMTP set ip next-hop 67.92.18.1 ! interface fa0/1 ip add 192.168.1.1 255.255.255.0 ip policy route-map SMTP_ISPB |
First we create our ACL that matches outgoing SMTP traffic, then we match the ACL in a route-map. After we match the traffic, we enter our action statement, “set ip next hop”. This route-map changes the next hope of all outgoing SMTP traffic. Finally we configure it on the LAN interface.
Free Cisco Lab
Nov 14th
Strech, the owner of PacketLife is now offering lab time for free. From his site:
Lab gear is broken into multiple “device blocks” to allow for multiple users to use independent portions of the lab simultaneously. Users can reserve one, several, or all of these blocks at once (however, a user may only have one unexpired reservation at any given time).
Block A
* 1x Cisco 2811 (with 2x WIC-2T)
* 2x Cisco 1841 (with 1x WIC-2T)
* 1x Cisco Catalyst 3550-24
* 1x Cisco Catalyst 3550-24 (with Inline Power)
* 1x Cisco ASA 5505
Block B
* 1x Cisco 2811 (with 2x WIC-2T)
* 2x Cisco 1841 (with 1x WIC-2T)
* 1x Cisco Catalyst 3550-24
* 1x Cisco Catalyst 3550-24 (with Inline Power)
BGP Backdoor Lab
Nov 12th
In this article we’ll be going over the BGP Backdoor feature. This is used in cases where two systems are connected via an IGP, but also receiving routes to the same system through BGP. I stumbled across this feature while checking out one of the labs on Darren’s Blog. The only way I could think of to complete one of his criteria was changing the Administrative Distance of either BGP or the IGP. That is essentially what this feature does, but on a route-by-route basis instead of changing the AD of an entire protocol. I asked Darren if that was the only solution and he pointed me to “BGP Backdoor”. As usual, I will be including my Dynagen/GNS3 .net file at the end of this post. Here is our topology:
Let’s go through the config:
R1
hostname R1 ! interface Serial0/0 ip address 10.1.1.1 255.255.255.0 ! interface Serial0/1 ip address 10.1.3.1 255.255.255.0 ! router bgp 65000 no synchronization bgp log-neighbor-changes neighbor 10.1.1.2 remote-as 65525 neighbor 10.1.3.2 remote-as 65535 no auto-summary |
OSPF LSA Types
Nov 4th
I can never seem to remember OSPF LSA Types for very long. I can cram them into my head for exams, but a week or so later they’re gone completely. I found a table from Internetwork Expert that is very, very helpful. I’m posting it here so I always have a copy and also in hopes that other people will find it useful as well.
(click image for fullsize)
Basic AToM Lab
Oct 14th
In this article we’ll go over a simple AToM (Any Transport over MPLS) configuration. I’ve been studying MPLS a lot lately and this is my first time playing with AToM and it’s very cool stuff. This article could be useful for anyone studying MPLS and/or CCIP/CCIE topics, or just someone who is interested in learning new things. I will be including my Dynagen/GNS3 .net file with this. Here is our topology:
Let’s go through the config:
P Router:
hostname P ! mpls label protocol ldp mpls ldp router-id lo0 force ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! interface FastEthernet1/0 ip address 10.1.1.1 255.255.255.252 duplex auto speed auto mpls ip ! interface FastEthernet1/1 ip address 10.1.2.1 255.255.255.252 duplex auto speed auto mpls ip ! router ospf 100 router-id 1.1.1.1 log-adjacency-changes network 1.1.1.1 0.0.0.0 area 0 network 10.1.1.0 0.0.0.3 area 0 network 10.1.2.0 0.0.0.3 area 0 |
Here we’ve set the hostname, configured the MPLS label protocol (note: LDP is the default on new IOSes), we set a loopback interface that will be our RID for MPLS and OSPF. We also configured our connections to the PE routers and brought up OSPF as our IGP.
PE1 Router:
hostname PE1 ! mpls label protocol ldp mpls ldp router-id lo0 force ! pseudowire-class one encapsulation mpls ! interface Loopback0 ip address 2.2.2.2 255.255.255.255 ! interface FastEthernet1/0 ip address 10.1.1.2 255.255.255.252 duplex auto speed auto mpls ip ! interface Serial2/0 no ip address xconnect 3.3.3.3 100 pw-class one ! router ospf 100 router-id 2.2.2.2 log-adjacency-changes network 2.2.2.2 0.0.0.0 area 0 network 10.1.1.0 0.0.0.3 area 0 |
PE2 Router:
hostname PE2 ! mpls label protocol ldp mpls ldp router-id lo0 force ! pseudowire-class one encapsulation mpls ! interface Loopback0 ip address 3.3.3.3 255.255.255.255 ! interface FastEthernet1/0 ip address 10.1.2.2 255.255.255.252 duplex auto speed auto mpls ip ! interface Serial2/0 no ip address xconnect 2.2.2.2 100 pw-class one ! router ospf 100 router-id 3.3.3.3 log-adjacency-changes network 2.2.2.2 0.0.0.0 area 0 network 10.1.2.0 0.0.0.3 area 0 |
Recent Comments