kevin wallace on bgp preference...
nothing new here, but always good to review...
1. BGP prefers the path with the highest weight. Note that the BGP weight parameter is a Cisco-specific parameter.
2. BGP prefers the path with the highest local preference value.
3. BGP prefers the path originated by BGP on the local router.
4. BGP prefers the path with the shortest autonomous system.
5. BGP prefers the path with the lowest origin type. (NOTE: IGP < EGP
< INCOMPLETE.)
6. BGP prefers the path with the lowest multi-exit discriminator (MED).
7. BGP prefers eBGP paths over iBGP paths.
8. BGP prefers the path with the lowest IGP metric to the BGP next-hop.
9. BGP prefers the path that points to a BGP router with the lowest BGP router ID.
Search insearchofthecert
Showing posts with label kevin wallace. Show all posts
Showing posts with label kevin wallace. Show all posts
Thursday, December 27, 2012
Monday, December 24, 2012
kev's tshoot...
it's a mess, but it's mine...
it's close... lmfao...
r1 is a physical router... the qinq switch begins the gns3 topology...
r1#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
dlsw1.ozlan Fas 0/0 175 R S I WS-C3560- Fas 0/20
r2#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
bb2.lab.local Ser 1/0.2 155 R S I 3640 Ser 1/0.2
bb1.lab.local Ser 1/0.1 154 R S I 3640 Ser 1/0.2
dlsw2.ozlan Fas 0/0 131 R S I WS-C3560- Fas 0/24
the labor is over, now it's fun time...
i made the left side eigrp 1 and the right side ospf area 0... and redistributed mutually at r2...
bb2#sh ip route | beg Gate
Gateway of last resort is not set
O E2 192.168.10.0/24 [110/20] via 172.16.2.1, 00:03:32, Serial1/0.2
172.16.0.0/30 is subnetted, 2 subnets
O 172.16.1.0 [110/65] via 10.1.2.1, 00:03:32, FastEthernet0/0
C 172.16.2.0 is directly connected, Serial1/0.2
10.0.0.0/8 is variably subnetted, 6 subnets, 4 masks
O 10.2.2.2/32 [110/65] via 172.16.2.1, 00:03:32, Serial1/0.2
C 10.1.3.0/30 is directly connected, Serial1/0.1
O 10.3.3.3/32 [110/2] via 10.1.2.1, 00:03:32, FastEthernet0/0
C 10.1.2.0/24 is directly connected, FastEthernet0/0
O E2 10.0.0.0/8 [110/20] via 172.16.2.1, 00:03:32, Serial1/0.2
C 10.4.4.4/32 is directly connected, Loopback0
O E2 192.168.1.0/24 [110/20] via 172.16.2.1, 00:03:32, Serial1/0.2
r1#sh ip route | beg Gate
Gateway of last resort is not set
C 192.168.10.0/24 is directly connected, Loopback1
172.16.0.0/30 is subnetted, 2 subnets
D EX 172.16.1.0
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 172.16.2.0
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
10.0.0.0/8 is variably subnetted, 7 subnets, 4 masks
D EX 10.2.2.2/32
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 10.1.3.0/30
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 10.3.3.3/32
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 10.1.2.0/24
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D 10.0.0.0/8 is a summary, 00:06:33, Null0
C 10.1.1.1/32 is directly connected, Loopback0
D EX 10.4.4.4/32
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
at some point i should return to the lab...
it's close... lmfao...
r1 is a physical router... the qinq switch begins the gns3 topology...
r1#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
dlsw1.ozlan Fas 0/0 175 R S I WS-C3560- Fas 0/20
r2#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
bb2.lab.local Ser 1/0.2 155 R S I 3640 Ser 1/0.2
bb1.lab.local Ser 1/0.1 154 R S I 3640 Ser 1/0.2
dlsw2.ozlan Fas 0/0 131 R S I WS-C3560- Fas 0/24
the labor is over, now it's fun time...
i made the left side eigrp 1 and the right side ospf area 0... and redistributed mutually at r2...
bb2#sh ip route | beg Gate
Gateway of last resort is not set
O E2 192.168.10.0/24 [110/20] via 172.16.2.1, 00:03:32, Serial1/0.2
172.16.0.0/30 is subnetted, 2 subnets
O 172.16.1.0 [110/65] via 10.1.2.1, 00:03:32, FastEthernet0/0
C 172.16.2.0 is directly connected, Serial1/0.2
10.0.0.0/8 is variably subnetted, 6 subnets, 4 masks
O 10.2.2.2/32 [110/65] via 172.16.2.1, 00:03:32, Serial1/0.2
C 10.1.3.0/30 is directly connected, Serial1/0.1
O 10.3.3.3/32 [110/2] via 10.1.2.1, 00:03:32, FastEthernet0/0
C 10.1.2.0/24 is directly connected, FastEthernet0/0
O E2 10.0.0.0/8 [110/20] via 172.16.2.1, 00:03:32, Serial1/0.2
C 10.4.4.4/32 is directly connected, Loopback0
O E2 192.168.1.0/24 [110/20] via 172.16.2.1, 00:03:32, Serial1/0.2
r1#sh ip route | beg Gate
Gateway of last resort is not set
C 192.168.10.0/24 is directly connected, Loopback1
172.16.0.0/30 is subnetted, 2 subnets
D EX 172.16.1.0
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 172.16.2.0
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
10.0.0.0/8 is variably subnetted, 7 subnets, 4 masks
D EX 10.2.2.2/32
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 10.1.3.0/30
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 10.3.3.3/32
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D EX 10.1.2.0/24
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
D 10.0.0.0/8 is a summary, 00:06:33, Null0
C 10.1.1.1/32 is directly connected, Loopback0
D EX 10.4.4.4/32
[170/2560002560] via 192.168.1.22, 00:04:01, FastEthernet0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
at some point i should return to the lab...
tshoot topo, book...
i like kevin wallace's videos for tshoot... although i'm not a big fan of video style learning, i prefer books (pdf's), i have come to regard his content as top notch...
but to the book...
nice thing here is the videos and book follow...
i think some more thought could have been put into the numbering for this, i prefer there to be some sort of logic between the dlci's, interfaces and ip's, but that's just me and my brand of insanity...
here is the topo...
it's kind of messy... something doc brown might have built... 'hey marty, wanna take a ride in a tshoot delorean time machine?"
here is the frame portion... i used 3640's because for some reason i was having difficulty with 7200's and getting all the pvc's active last night with the gns3 frame-switch...
the addressing and dlci's follow the book exactly...
bb1#sh frame pvc
PVC Statistics for interface Serial1/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 2 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 811, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.2
input pkts 37 output pkts 39 in bytes 10008
out bytes 10746 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 29 out bcast bytes 9706
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:34:08, last time pvc status changed 00:27:42
DLCI = 881, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.1
input pkts 40 output pkts 38 in bytes 9730
out bytes 9345 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 23 out bcast bytes 7785
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:28:00, last time pvc status changed 00:27:35
r2#sh frame lmi
LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = ANSI
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 209 Num Status msgs Rcvd 210
Num Update Status Rcvd 0 Num Status Timeouts 3
Last Full Status Req 00:00:01 Last Full Status Rcvd 00:00:01
note status enq's/msgs should be nearly the same...
bb2#sh frame map
Serial1/0.2 (up): point-to-point dlci, dlci 821(0x335,0xCC50), broadcast
status defined, active
Serial1/0.1 (up): point-to-point dlci, dlci 882(0x372,0xDC20), broadcast
status defined, active
and without routing we have expected behavior from the pings...
bb1#ping 10.1.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.2, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 20/28/48 ms
bb1#ping 172.16.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/22/32 ms
bb1#ping 172.16.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.2.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
bb1#ping 10.1.3.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.3.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/24 ms
bb1#
bb2#sh ip int brie | inc up
FastEthernet0/0 10.1.2.2 YES manual up up
Serial1/0 unassigned YES unset up up
Serial1/0.1 10.1.3.2 YES manual up up
Serial1/0.2 172.16.2.2 YES manual up up
Loopback0 10.4.4.4 YES manual up up
and now for my next trick...
but to the book...
nice thing here is the videos and book follow...
i think some more thought could have been put into the numbering for this, i prefer there to be some sort of logic between the dlci's, interfaces and ip's, but that's just me and my brand of insanity...
here is the topo...
it's kind of messy... something doc brown might have built... 'hey marty, wanna take a ride in a tshoot delorean time machine?"
here is the frame portion... i used 3640's because for some reason i was having difficulty with 7200's and getting all the pvc's active last night with the gns3 frame-switch...
the addressing and dlci's follow the book exactly...
bb1#sh frame pvc
PVC Statistics for interface Serial1/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 2 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 811, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.2
input pkts 37 output pkts 39 in bytes 10008
out bytes 10746 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 29 out bcast bytes 9706
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:34:08, last time pvc status changed 00:27:42
DLCI = 881, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.1
input pkts 40 output pkts 38 in bytes 9730
out bytes 9345 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 23 out bcast bytes 7785
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 00:28:00, last time pvc status changed 00:27:35
r2#sh frame lmi
LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = ANSI
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 209 Num Status msgs Rcvd 210
Num Update Status Rcvd 0 Num Status Timeouts 3
Last Full Status Req 00:00:01 Last Full Status Rcvd 00:00:01
note status enq's/msgs should be nearly the same...
bb2#sh frame map
Serial1/0.2 (up): point-to-point dlci, dlci 821(0x335,0xCC50), broadcast
status defined, active
Serial1/0.1 (up): point-to-point dlci, dlci 882(0x372,0xDC20), broadcast
status defined, active
and without routing we have expected behavior from the pings...
bb1#ping 10.1.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.2, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 20/28/48 ms
bb1#ping 172.16.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/22/32 ms
bb1#ping 172.16.2.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.2.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
bb1#ping 10.1.3.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.3.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/19/24 ms
bb1#
bb2#sh ip int brie | inc up
FastEthernet0/0 10.1.2.2 YES manual up up
Serial1/0 unassigned YES unset up up
Serial1/0.1 10.1.3.2 YES manual up up
Serial1/0.2 172.16.2.2 YES manual up up
Loopback0 10.4.4.4 YES manual up up
and now for my next trick...
Friday, November 30, 2012
quote of the day... kevin wallace...
below are good definitions of the following...
Logical topology diagram: A logical topology diagram shows the interconnection of network segments, the protocols used, and how end users interface with the network. However, this diagram is not concerned with the physical locations of network components.
Physical topology diagram: Unlike a logical topology diagram, a physical
topology diagram shows how different geographical areas (for example, floors within a building, buildings, or entire sites) interconnect. The diagram reflects where various network components are physically located.
Logical topology diagram: A logical topology diagram shows the interconnection of network segments, the protocols used, and how end users interface with the network. However, this diagram is not concerned with the physical locations of network components.
Physical topology diagram: Unlike a logical topology diagram, a physical
topology diagram shows how different geographical areas (for example, floors within a building, buildings, or entire sites) interconnect. The diagram reflects where various network components are physically located.
Monday, November 26, 2012
kevin wallace...
http://www.1examamonth.com/
this guy is a great instructor... i purchased his tshoot video set and i'm very happy i did...
you just have to get used to him saying, fasht for fast...
he has a great delivery and no bullshit approach... this set is a must for the ccnp...
and of course, i also have his tshoot book... (duh)
nothing is free... if you want to be the best, you need to pay for the best...
this guy is a great instructor... i purchased his tshoot video set and i'm very happy i did...
you just have to get used to him saying, fasht for fast...
he has a great delivery and no bullshit approach... this set is a must for the ccnp...
and of course, i also have his tshoot book... (duh)
nothing is free... if you want to be the best, you need to pay for the best...
Sunday, March 4, 2012
tshoot demo and kevin wallace...
this link is a cisco demo of the tshoot exam... it is very informative and presents the topologies for the exam... it can be downloaded here...
http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_tutorial.html
also, this link is to kevin wallace videos on youtube... he outlines strategies not only for tackling the exam, but for troubleshooting in general... a must see here...
http://www.youtube.com/watch?v=3Bo4Pw82G2M
and of course the tshoot topologies themselves, here...
https://learningnetwork.cisco.com/thread/10965
have you joined CLN yet...
this has been a public service announcement
http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_tutorial.html
also, this link is to kevin wallace videos on youtube... he outlines strategies not only for tackling the exam, but for troubleshooting in general... a must see here...
http://www.youtube.com/watch?v=3Bo4Pw82G2M
and of course the tshoot topologies themselves, here...
https://learningnetwork.cisco.com/thread/10965
have you joined CLN yet...
this has been a public service announcement
Labels:
ccnp switch,
cisco,
kevin wallace,
topologies,
tshoot
Subscribe to:
Posts (Atom)



