专栏名称: 网络工程师俱乐部
CCIE俱乐部,即CCIE公会,弘扬“CCIE”精神,关注网络专家和相关精英人才的学习,事业和生活。
目录
51好读  ›  专栏  ›  网络工程师俱乐部

16日火热出炉的CCIE战报,也许下次你就抽到这组合!

网络工程师俱乐部  · 公众号  ·  · 2018-03-18 20:21

正文

请到「今天看啥」查看全文


2 10.2.123.1 0 msec

10.2.223.1 1 msec

10.2.123.1 0 msec

3 10.12.23.1 [AS 65001] 1 msec 0 msec 1 msec

4 10.1.113.2 [AS 65001] 1 msec 1 msec 1 msec

5 10.1.23.2 [AS 65001] 1 msec *  3 msec


First:

console to R12/13/22/23

sh run | s route-map

compare the configuration

If route-map has set metric 1 I change "set origin igp"

otherway set metric 2 I change to "set origin incomplete"


example:

route-map MED permit 10

match ip address 1

set metric 2

set origin incomplete

route-map MED permit 20

match ip address 2

set metric 1

set origin igp

route-map MED permit 30

I double checked and I discovered

SW110 output is:

4 10.2.223.2 [AS 65002] 1 msec 6 msec 1 msec

5 10.2.21.2 [AS 65002] 2 msec *  3 msec

But SW210

3 10.12.23.1 [AS 65001] 1 msec 0 msec 1 msec

4 10.1.113.2 [AS 65001] 1 msec 1 msec 1 msec

5 10.1.23.2 [AS 65001] 1 msec *  3 msec

then I configured

R12:

router bgp 65001

network 10.12.22.0 mask 255.255.255.252

R13

router bgp 65001

network 10.12.23.0 mask 255.255.255.252

remember clear ip bgp * so on R12/13/22/23

loopback was in process ip 10 are 0 on R23 --->

changed it:

int lo0

ip os 1 are 0

----> match output when we tracer successful.

Ticket 4.

specified to not change any BGP, so made lo0 of R20 higher, made a random number.

trace successful.

Ticket 5.

*DMVPN APEARED TO BE UP ( show dmvpn ), however a flap on tun0 revealed it was staged.

****SUGGEST ALWAYS FLAP DMVPN TUNNEL ON HUB BEFORE ATTEMPTING TICKET**********

R60,

tunel ip address mask was 255.255.255.255, changed to 255.255.255.0,

tunnel and ospf up. output matched.

Ticket 6.

could ping from the switch, show run ipv6 ospf int br,

vlan 2000 not int v6 ospf, added it,

ping successful from Server 1

Ticket 7.

Same with WB

ping was successful via dmvpn needs to go through mpls.

lo0 on R5 wrong area, changed to area 0,

verfieid mpls was up, vpnv4 was up, import export tags matched.

ping still went out the side,

did show ip bgp all on R5 no route, checked r10,

distance external 19, changed to 210,

trace successful

Ticket 8.

configured ip ar insp trust all port channel of SW310,301,300

When I configured ip arp ins trust on SW310 I cannot ping from User3 to R30 and then I configured for 2 int port channel of SW301 and 300.

result: trace and ping successsful

Ticket 9.

dmvpn was up.

ip ospf network mistmatch,

R71 - tun 0 - changed ip ospf net po-to-po to ip ospf net po-to-multipoint to match dmvpn hub,

ospf came up.

telnet successful.

Ticket 10.

Cannot telnet from NAS to server2

I check nat configuration on R24 and R25 by command:

sho run | s ip nat

and then I copy nat configuration of R24 and paste to R25

result: telnet successful and match with output

I finished TS in 1 hours and then I verified in 20 munites

Diag: H2+ Same with WB

filter key word: icmpv6.type == 134

and first frame id is 227 (FE80::666)

I remember the static route command:

R2(config)#ip mroute 10.4.1.1 255.255.255.255 10.0.0.14







请到「今天看啥」查看全文