Blog Archives

IP SLA Lab

7/3/2013

IP SLA (Internet protocol service level agreement) is a feature of the Cisco Internetwork Operating System (Cisco IOS) that allows an IT professional to collect information about network performance in real time. Cisco IOS IP SLAs continuously collect data about such things as response times, latency, jitter and packet loss. This not only provides the network administrator with baseline information about network performance. IP SLAs are especially useful for wide area networks (WANs) that connect multiple geographies and needs to be monitored from one central location.

Requirement:

Configure IP addresses as per topology
Configure EIGRP among ISP1 routers and between ISP1 and ISP2
Configure Default and static routes as per need between customers and ISPs
Configure SLA for icmp echo between customer 3 and customer 1.
Configure SLA for path-echo between customer1 and customer2

verify results by using following commands
debug ip sla trace
show ip sla statistics
debug ip sla err

! Customer1 Configuration

interface Loopback0
ip address 150.1.1.1 255.255.255.255

interface Serial0/0
ip address 10.1.1.129 255.255.255.252
no shut

ip route 0.0.0.0 0.0.0.0 10.1.1.130

ip sla responder

ip sla 10

path-echo 10.1.1.194

verify-data

frequency 10

ip sla schedule 10 life 40 start-time now

! Cutomer2 Configuration

interface Loopback0
ip address 15.1.1.1 255.255.255.255

interface Serial0/0
ip address 10.1.1.194 255.255.255.252
no shut

ip route 0.0.0.0 0.0.0.0 10.1.1.193

ip sla responder

! Customer3 Configuration

interface Loopback0
ip address 90.1.1.1 255.255.255.255

interface Serial0/0
ip address 11.1.1.194 255.255.255.252
no shut

ip route 0.0.0.0 0.0.0.0 11.1.1.193

ip sla 1
icmp-echo 150.1.1.1
verify-data
frequency 5

ip sla schedule 1 life 60 start-time now

! ISPR1 Configuration

interface FastEthernet0/0
ip address 10.1.1.1 255.255.255.252
no shut

interface Serial0/0
ip address 10.1.1.130 255.255.255.252
no shut

router eigrp 10
redistribute static
network 10.0.0.0
no auto-summary

ip route 150.1.1.1 255.255.255.255 10.1.1.129

! ISP2R2 Configuration

interface FastEthernet0/0
ip address 10.1.1.2 255.255.255.252
no shut

interface Serial0/0
ip address 10.1.1.193 255.255.255.252
no shut

interface Serial0/1
ip address 11.1.1.1 255.255.255.252
no shut

router eigrp 10
redistribute static
network 10.0.0.0
network 11.0.0.0
no auto-summary

ip route 15.1.1.1 255.255.255.255 10.1.1.194

! ISP2R1 Configuration

interface Serial0/0
ip address 11.1.1.2 255.255.255.252
no shut

interface Serial0/1
ip address 11.1.1.193 255.255.255.252
no shut

router eigrp 10
redistribute static
network 11.0.0.0
no auto-summary

ip route 90.1.1.1 255.255.255.255 11.1.1.194

Configuration Explanation

Providing ip address to loopback 0

Providing IP address to serial 0/0

Default Route

The Cisco IOS IP SLAs Responder is a component embedded in the destination Cisco routing device
that allows the system to anticipate and respond to Cisco IOS IP SLAs request packets. The Cisco IOS
IP SLAs Responder provides an enormous advantage with accurate measurements without the need for dedicated probes

Enabling IP SLA. Number is the identification of this SLA and it is locally important.

The IP SLAs ICMP Path Echo operation records statistics for each hop along the path that the IP SLAs operation takes to reach its destination.

(Optional) Causes an IP SLAs operation to check each reply packet for data corruption.

(Optional) Set the rate at which a specified IP SLAs operation repeats.

Configures the scheduling parameters for a single IP SLAs operation. use the ip sla schedule command in global configuration mode

Verification by Debugging

Customer3(config)#
*Mar 1 02:17:29.311: IP SLAs(1) Scheduler: Starting an operation

*Mar 1 02:17:29.311: IP SLAs(1) echo operation: Sending an echo operation -

destAddr=150.1.1.1, sAddr=11.1.1.194

*Mar 1 02:17:29.311: IP SLAs(1) echo operation: Sending ID: 7

*Mar 1 02:17:29.527: IP SLAs(1) echo operation: RTT=212

*Mar 1 02:17:29.527: IP SLAs(1) Scheduler: Updating result

*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: life left 59784

*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: is it random? 0

*Mar 1 02:17:29.531: IP SLAs(1) Scheduler: start wakeup timer, delay = 4780

*Mar 1 02:17:34.311: IP SLAs(1) Scheduler: saaSchedulerEventWakeup

*Mar 1 02:17:34.311: IP SLAs(1) Scheduler: Starting an operation

*Mar 1 02:17:34.311: IP SLAs(1) echo operation: Sending an echo operation -

destAddr=150.1.1.1, sAddr=11.1.1.194

*Mar 1 02:17:34.315: IP SLAs(1) echo operation: Sending ID: 7

*Mar 1 02:17:34.427: IP SLAs(1) echo operation: RTT=112

*Mar 1 02:17:34.427: IP SLAs(1) Scheduler: Updating result

*Mar 1 02:17:34.427: IP SLAs(1) Scheduler: life left 54884

*Mar 1 02:17:34.431: IP SLAs(1) Scheduler: is it random? 0

*Mar 1 02:17:34.431: IP SLAs(1) Scheduler: start wakeup timer, delay = 4880

Customer1(config)#

*Mar 1 02:33:24.391: IP SLAs(10) Scheduler: Starting an operation

*Mar 1 02:33:24.395: IP SLAs(10) pathEcho operation: Sending a pathEcho operation

*Mar 1 02:33:24.399: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 1

*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Return Value of ! for target 10.1.1.130

*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.130

*Mar 1 02:33:24.407: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 2

*Mar 1 02:33:24.619: IP SLAs(10) pathEcho operation: Return Value of ! for target 10.1.1.2

*Mar 1 02:33:24.623: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.2

*Mar 1 02:33:24.623: IP SLAs(10) pathEcho operation: Sending Packet to 10.1.1.194 with ttl = 3

*Mar 1 02:33:24.823: IP SLAs(10) pathEcho operation: Return Value of U for target 10.1.1.194

*Mar 1 02:33:24.823: IP SLAs(10) pathEcho operation: Adding hop - 10.1.1.194

*Mar 1 02:33:24.951: IP SLAs(10) pathEcho operation: Hop 10.1.1.130 Response Time 124

*Mar 1 02:33:25.103: IP SLAs(10) pathEcho operation: Hop 10.1.1.2 Response Time 152

*Mar 1 02:33:25.255: IP SLAs(10) pathEcho operation: Hop 10.1.1.194 Response Time 149

*Mar 1 02:33:25.255: IP SLAs(10) Scheduler: Updating result

*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: life left 39128

*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: is it random? 0

*Mar 1 02:33:25.263: IP SLAs(10) Scheduler: start wakeup timer, delay = 9128

Customer1(config)#

MPLS + OSPF + BGP Lab

7/1/2013

Requirement:

Configure ip addresses as per topology
Configure one loopback address on each router i.e. 10.10.10.10 on R1 ; 20.20.20.20 on R2 ; 30.30.30.30 on R3 ; 40.40.40.40 on R4 and 50.50.50.50 on R5
Configure ospf on specified networks
Configure ibgp and ebgp as per topology
Configure MPLS on core network
Verify connectivity annd communication via mpls

Verification commands:
traceroute ip 50.50.50.50 source 40.40.40.40
traceroute mpls ipv4 50.50.50.50/32 (very imp)
ping mpls ipv4 30.30.30.30/32
sh ip route :: Show ip bgp :: clear ip bgp *
show mpls ldp neigehbor
show mpls forwarding
show mpls ldp binding

! R1 configuration

hostname R1
ip cef
mpls label protocol ldp

interface Loopback0
ip address 10.10.10.10 255.255.255.0

interface Serial0/0
ip address 1.1.1.1 255.255.255.0
mpls ip
no shut

interface Serial0/1
ip address 9.9.9.1 255.255.255.252
no shut

router ospf 10
redistribute bgp 10 subnets
network 1.1.1.0 0.0.0.255 area 0
network 10.10.10.10 0.0.0.0 area 0

router bgp 10
neighbor 9.9.9.2 remote-as 100
neighbor 9.9.9.2 distribute-list 1 out
neighbor 30.30.30.30 remote-as 10
neighbor 30.30.30.30 update-source Loopback0
neighbor 30.30.30.30 next-hop-self
no auto-summary

access-list 1 deny 50.50.50.50
access-list 1 permit any

! R2 Configuration

hostname R2
ip cef
mpls label protocol ldp

interface Loopback0
ip address 20.20.20.20 255.255.255.255

interface Serial0/0
ip address 1.1.1.2 255.255.255.0
mpls ip
no shut

interface Serial0/1
ip address 1.1.10.1 255.255.255.0
mpls ip
no shut

router ospf 10
network 1.1.1.0 0.0.0.255 area 0
network 1.1.10.0 0.0.0.255 area 0
network 20.20.20.20 0.0.0.0 area 0

! R3 Configuration

hostname R3
ip cef
mpls label protocol ldp

interface Loopback0
ip address 30.30.30.30 255.255.255.255

interface Serial0/0
ip address 1.1.10.11 255.255.255.0
mpls ip
no shut

interface Serial0/1
ip address 6.6.6.1 255.255.255.252
no shut

router ospf 10
redistribute bgp 10 subnets
network 1.1.10.0 0.0.0.255 area 0
network 30.30.30.30 0.0.0.0 area 0

router bgp 10
neighbor 6.6.6.2 remote-as 200
neighbor 6.6.6.2 distribute-list 1 out
neighbor 10.10.10.10 remote-as 10
neighbor 10.10.10.10 update-source Loopback0
neighbor 10.10.10.10 next-hop-self
no auto-summary

access-list 1 deny 40.40.40.40
access-list 1 permit any

! R4 Configuration

hostname R4

interface Loopback0
ip address 40.40.40.40 255.255.255.255

interface Serial0/0
ip address 9.9.9.2 255.255.255.252
no shut

router bgp 100
network 40.40.40.40 mask 255.255.255.255
neighbor 9.9.9.1 remote-as 10
no auto-summary

ip route 0.0.0.0 0.0.0.0 9.9.9.1

! R5 Configuration

hostname R5

interface Loopback0
ip address 50.50.50.50 255.255.255.255

interface Serial0/0
ip address 6.6.6.2 255.255.255.252
no shut

router bgp 200
network 50.50.50.50 mask 255.255.255.255
neighbor 6.6.6.1 remote-as 10
no auto-summary

ip route 0.0.0.0 0.0.0.0 6.6.6.1

Verification:

R4#traceroute ip 50.50.50.50 source 40.40.40.40

Type escape sequence to abort.
Tracing the route to 50.50.50.50

1 9.9.9.1 56 msec 4 msec 8 msec
2 1.1.1.2 [MPLS: Label 16 Exp 0] 72 msec 16 msec 0 msec
3 1.1.10.11 60 msec 44 msec 20 msec
4 6.6.6.2 64 msec * 132 msec

R1#show mpls forwarding
Local Outgoing    Prefix            Bytes tag Outgoing   Next Hop
tag    tag or VC   or Tunnel Id      switched   interface
16     Pop tag     1.1.10.0/24       0          Se0/0      point2point
17     16          50.50.50.50/32    0          Se0/0      point2point
18     Pop tag     20.20.20.20/32    0          Se0/0      point2point
19     19          30.30.30.30/32    0          Se0/0      point2point
R1#

R2#show mpls ldp neighbor
    Peer LDP Ident: 10.10.10.10:0; Local LDP Ident 20.20.20.20:0
        TCP connection: 10.10.10.10.646 - 20.20.20.20.53911
        State: Oper; Msgs sent/rcvd: 151/151; Downstream
        Up time: 02:00:22
        LDP discovery sources:
          Serial0/0, Src IP addr: 1.1.1.1
        Addresses bound to peer LDP Ident:
          1.1.1.1         9.9.9.1         10.10.10.10

    Peer LDP Ident: 30.30.30.30:0; Local LDP Ident 20.20.20.20:0
        TCP connection: 30.30.30.30.37364 - 20.20.20.20.646
        State: Oper; Msgs sent/rcvd: 145/147; Downstream
        Up time: 01:59:44
        LDP discovery sources:
          Serial0/1, Src IP addr: 1.1.10.11
        Addresses bound to peer LDP Ident:
          1.1.10.11       6.6.6.1         30.30.30.30

MPLS service provider + EIGRP scenerio

7/1/2013

In this scenerio; we are trying to communicate two customers via MPLS SP cloud.

A CE router ( customer edge router ) is a router located on the customer premises that provides an Ethernet interface between the customer's LAN and the provider's core network. CE routers, P (provider) routers and PE (provider edge) routers are components in an MPLS (multiprotocol label switching) architecture. Provider routers are located in the core of the provider or carrier's network. Provider edge routers sit at the edge of the network. CE routers connect to PE routers and PE routers connect to other PE routers over P routers.

Requirement:

Configure IP address as per toplogy
Configure 2.2.2.2 as PE2 router ID, 3.3.3.3 P2 router ID, 4.4.4.4 P1 router ID and 1.1.1.1 as PE1 router ID.
Configure EIGRP as a routing protocol
Configure MPLS with-in cloud.
Verify communication via MPLS

Verificaton Command

show mpls ip binding
show ip cef
show mpls interfaces
show mpls ldp discovery
show mpls ldp nei
show mpls forwarding-table

! CE1 Configuration
ip cef

interface FastEthernet1/0
ip address 200.1.2.1 255.255.255.0
no shut

router eigrp 10
network 200.1.2.0
no auto-summary

! CE2 Configuration
ip cef

interface Loopback0
ip address 10.1.1.1 255.255.255.0

interface FastEthernet1/0
ip address 200.1.1.1 255.255.255.0
no shut

router eigrp 10
network 10.0.0.0
network 200.1.1.0
no auto-summary

! PE1 Configuration

ip cef

mpls label protocol ldp

interface Loopback0
ip address 1.1.1.1 255.255.255.255

interface FastEthernet1/0
ip address 200.1.2.2 255.255.255.0
no shut

interface Serial2/0
ip address 200.1.7.1 255.255.255.0
mpls label protocol ldp

mpls ip

no shut

interface Serial2/1
ip address 200.1.6.1 255.255.255.0
mpls label protocol ldp
mpls ip
no shut

router eigrp 10
network 1.0.0.0
network 200.1.2.0
network 200.1.6.0
network 200.1.7.0
no auto-summary

! PE2 Configuration

ip cef

mpls label protocol ldp

interface Loopback0
ip address 2.2.2.2 255.255.255.255

interface FastEthernet1/0
ip address 200.1.1.2 255.255.255.0
no shut

interface Serial2/0
ip address 200.1.4.1 255.255.255.0
mpls label protocol ldp
mpls ip
no shut
!
interface Serial2/1
ip address 200.1.3.1 255.255.255.0
mpls label protocol ldp
mpls ip
no shut

router eigrp 10
network 2.0.0.0
network 200.1.1.0
network 200.1.3.0
network 200.1.4.0
no auto-summary

! P1 Configuration
ip cef

mpls label protocol ldp

interface Loopback0
ip address 4.4.4.4 255.255.255.255

interface Serial1/0
ip address 200.1.7.2 255.255.255.0
mpls label protocol ldp
mpls ip
no shut
!
interface Serial1/1
ip address 200.1.4.2 255.255.255.0
mpls label protocol ldp
mpls ip
no shut
!
interface Serial1/2
ip address 200.1.5.2 255.255.255.0
mpls label protocol ldp
mpls ip
no shut

router eigrp 10
network 4.0.0.0
network 200.1.4.0
network 200.1.5.0
network 200.1.7.0
no auto-summary

!P2 Configuration
ip cef

mpls label protocol ldp

interface Loopback0
ip address 3.3.3.3 255.255.255.255
!
interface Serial1/0
ip address 200.1.6.2 255.255.255.0
mpls label protocol ldp
mpls ip
no shut
!
interface Serial1/1
ip address 200.1.3.2 255.255.255.0
mpls label protocol ldp
mpls ip
no shut
!
interface Serial1/2
ip address 200.1.5.1 255.255.255.0
mpls label protocol ldp
mpls ip
no shut

router eigrp 10
network 3.0.0.0
network 200.1.3.0
network 200.1.5.0
network 200.1.6.0
no auto-summary

Configuration Explanation
Cisco's Express Forwarding (CEF) is an Layer 3 fastest switching technology by which Cisco router forwards packets from ingress to egress interfaces.
Note: This is a essential command

For explanation; See above

Enabling IP address to loopback interface

Enabling EIGRP autonomous no 10

See above for command explanation

Enable LDP protocol globally. MPLS Label Distribution Protocol (LDP) enables peer label switch routers (LSRs) in an MPLS network to exchange label binding information for supporting hop-by-hop forwarding in an MPLS network

Globally enabling MPLS forwarding does not enable it on the router interfaces. You must enable MPLS forwarding on the interfaces as well as for the router.

CE1#traceroute 10.1.1.1 ====> Look at the output; MPLs is working

Type escape sequence to abort.
Tracing the route to 10.1.1.1

1 200.1.2.2 80 msec 44 msec 32 msec
2 200.1.7.2 [MPLS: Label 23 Exp 0] 80 msec 64 msec 60 msec
3 200.1.4.1 [MPLS: Label 23 Exp 0] 172 msec 60 msec 76 msec
4 200.1.1.1 92 msec * 176 msec

check all verification commands by yourself.

IP SLA Lab

Verification by Debugging

MPLS + OSPF + BGP Lab

Verification:

MPLS service provider + EIGRP scenerio

M Irfan

Archives

Categories