INITIAL BGP CONFIGS
Friday, November 14, 2008
the first requirement is that the serial link between sanjose1 should be used rather than sanjose2
here are the configs for that .. i created route maps and applied it on the neig statements
take a look at the values of metric and local pref
CODE
sanjose1#show route
route-map rakesht1pref_1.5, permit, sequence 10
Match clauses:
Set clauses:
local-preference 150
Policy routing matches: 0 packets, 0 bytes
route-map rakesh1_metric1.5, permit, sequence 20
Match clauses:
Set clauses:
metric 50
Policy routing matches: 0 packets, 0 bytes
sanjose1#
as#3
[Resuming connection 3 to r3 ... ]
sanjose2#show route
route-map rakesh1locpref_1.1, permit, sequence 10
Match clauses:
Set clauses:
local-preference 125
Policy routing matches: 0 packets, 0 bytes
route-map rakesh1_metric1.1, permit, sequence 20
Match clauses:
Set clauses:
metric 100
Policy routing matches: 0 packets, 0 bytes
sanjose2#
route-map rakesht1pref_1.5, permit, sequence 10
Match clauses:
Set clauses:
local-preference 150
Policy routing matches: 0 packets, 0 bytes
route-map rakesh1_metric1.5, permit, sequence 20
Match clauses:
Set clauses:
metric 50
Policy routing matches: 0 packets, 0 bytes
sanjose1#
as#3
[Resuming connection 3 to r3 ... ]
sanjose2#show route
route-map rakesh1locpref_1.1, permit, sequence 10
Match clauses:
Set clauses:
local-preference 125
Policy routing matches: 0 packets, 0 bytes
route-map rakesh1_metric1.1, permit, sequence 20
Match clauses:
Set clauses:
metric 100
Policy routing matches: 0 packets, 0 bytes
sanjose2#
here is the beauty of extended pings now i wanted to ping 192.168.100.1 ip addr from sanjose 2 look at the path the packets travelled ...
remember to enable the record option if you wanna do that
CODE
//after metric change
sanjose2#
sanjose2#ping
Protocol [ip]:
Target IP address: 192.168.100.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.16.32.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: record
Number of hops [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[RV]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.1, timeout is 2 seconds:
Packet sent with a source address of 172.16.32.1
Packet has IP options: Total option bytes= 39, padded length=40
Record route: <*>
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
Reply to request 0 (156 ms). Received packet has options
Total option bytes= 40, padded length=40
Record route:
(172.16.1.2)
(192.168.1.6)
(192.168.100.1)
(192.168.1.5)
(172.16.1.1)
(172.16.32.1) <*>
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
End of list
Reply to request 1 (104 ms). Received packet has options
Total option bytes= 40, padded length=40
Record route:
(172.16.1.2)
(192.168.1.6)
(192.168.100.1)
(192.168.1.5)
(172.16.1.1)
(172.16.32.1) <*>
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
End of list
Success rate is 100 percent (2/2), round-trip min/avg/max = 104/130/156 ms
sanjose2#
sanjose2#
sanjose2#ping
Protocol [ip]:
Target IP address: 192.168.100.1
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.16.32.1
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: record
Number of hops [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[RV]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.1, timeout is 2 seconds:
Packet sent with a source address of 172.16.32.1
Packet has IP options: Total option bytes= 39, padded length=40
Record route: <*>
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
Reply to request 0 (156 ms). Received packet has options
Total option bytes= 40, padded length=40
Record route:
(172.16.1.2)
(192.168.1.6)
(192.168.100.1)
(192.168.1.5)
(172.16.1.1)
(172.16.32.1) <*>
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
End of list
Reply to request 1 (104 ms). Received packet has options
Total option bytes= 40, padded length=40
Record route:
(172.16.1.2)
(192.168.1.6)
(192.168.100.1)
(192.168.1.5)
(172.16.1.1)
(172.16.32.1) <*>
(0.0.0.0)
(0.0.0.0)
(0.0.0.0)
End of list
Success rate is 100 percent (2/2), round-trip min/avg/max = 104/130/156 ms
sanjose2#
no where the path of 192.168.1.1 has been used .. if you wanna check it , disable it and see that it prefers the 1.1 route