rdntw Posted April 14, 2015 Posted April 14, 2015 Пытаюсь настроить немножко RSVP-TE в академических целях. Как обычно начинаются непонятки при использовании разных вендоров. Хочу настроить чтобы LSP2 использовался как основной. admin@mx80-pe_Himki> show configuration protocols mpls traceoptions { file mpls-log size 10m files 3; flag cspf; flag error; flag state; } label-switched-path Ximki>M10 { from 172.16.16.8; to 172.16.16.6; } label-switched-path Ximki>M9 { from 172.16.16.8; to 172.16.16.2; } path TO_M9_MED { 172.16.16.5 loose; } interface xe-0/0/0.78; admin@mx80-pe_Himki> admin@mx80-pe_Himki> show route table inet.3 inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 172.16.16.2/32 *[RSVP/7/1] 00:17:24, metric 2 > to 185.13.115.73 via xe-0/0/0.78, label-switched-path Ximki>M9 172.16.16.6/32 *[RSVP/7/1] 8w0d 21:38:42, metric 1 > to 185.13.115.73 via xe-0/0/0.78, label-switched-path Ximki>M10 admin@mx80-pe_Himki> admin@mx80-pe_Himki> show ted database 172.16.16.6 TED database: 0 ISIS nodes 44 INET nodes ID Type Age(s) LnkIn LnkOut Protocol 172.16.16.6 Rtr 967257 6 4 OSPF(0.0.0.0) To: 185.13.115.73-1, Local: 185.13.115.73, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 185.13.115.85-1, Local: 185.13.115.84, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 95.215.98.9-1, Local: 95.215.98.9, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 185.13.115.69-1, Local: 185.13.115.69, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 admin@mx80-pe_Himki> show ted database 172.16.16.2 TED database: 0 ISIS nodes 44 INET nodes ID Type Age(s) LnkIn LnkOut Protocol 172.16.16.2 Rtr 3577527 7 4 OSPF(0.0.0.0) To: 195.128.59.173-1, Local: 195.128.59.174, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 185.13.115.85-1, Local: 185.13.115.85, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 195.128.62.22-1, Local: 195.128.62.21, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 95.215.98.182-1, Local: 95.215.98.181, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 admin@mx80-pe_Himki> show ted database 172.16.16.5 TED database: 0 ISIS nodes 44 INET nodes ID Type Age(s) LnkIn LnkOut Protocol 172.16.16.5 Rtr 3581494 6 4 OSPF(0.0.0.0) To: 185.13.115.77-1, Local: 185.13.115.77, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 185.13.115.81-1, Local: 185.13.115.81, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 195.128.59.173-1, Local: 195.128.59.173, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 To: 195.128.59.177-1, Local: 195.128.59.177, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 admin@mx80-pe_Himki> Делаю Primary path через 172.16.16.5 и admin@mx80-pe_Himki# show protocols mpls traceoptions { file mpls-log size 10m files 3; flag cspf; flag error; flag state; } label-switched-path Ximki>M10 { from 172.16.16.8; to 172.16.16.6; } label-switched-path Ximki>M9 { from 172.16.16.8; to 172.16.16.2; primary TO_M9_MED; } path TO_M9_MED { 172.16.16.5 loose; } interface xe-0/0/0.78; [edit] admin@mx80-pe_Himki# admin@mx80-pe_Himki> show mpls lsp name Ximki>M9 extensive Ingress LSP: 2 sessions 172.16.16.2 From: 172.16.16.8, State: Dn, ActiveRoute: 0, LSPname: Ximki>M9 ActivePath: (none) LSPtype: Static Configured, Penultimate hop popping LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 Primary TO_M9_MED State: Dn Priorities: 7 0 SmartOptimizeTimer: 180 Will be enqueued for recomputation in 27 second(s). 30 Apr 14 13:51:38.796 Deselected as active 29 Apr 14 13:51:38.795 CSPF failed: no route toward 172.16.16.2 28 Apr 14 13:51:38.790 Clear Call 27 Apr 14 13:42:52.133 Selected as active path 26 Apr 14 13:42:52.133 Record Route: 185.13.115.73 185.13.115.85 25 Apr 14 13:42:52.132 Up 24 Apr 14 13:42:52.032 Originate Call 23 Apr 14 13:42:52.032 CSPF: computation result accepted 185.13.115.73 185.13.115.85 22 Apr 14 13:42:52.025 Clear Call 21 Apr 14 13:42:52.024 Deselected as active 20 Apr 14 13:23:36.304 Selected as active path 19 Apr 14 13:23:36.303 Record Route: 185.13.115.73 185.13.115.85 18 Apr 14 13:23:36.303 Up 17 Apr 14 13:23:36.204 Originate Call 16 Apr 14 13:23:36.204 CSPF: computation result accepted 185.13.115.73 185.13.115.85 15 Apr 14 13:23:14.661 CSPF failed: no route toward 172.16.16.2 14 Apr 14 13:22:44.753 Deselected as active 13 Apr 14 13:22:44.753 CSPF failed: no route toward 172.16.16.2 12 Apr 14 13:22:44.744 Clear Call 11 Apr 14 13:20:04.509 Selected as active path 10 Apr 14 13:20:04.508 Record Route: 185.13.115.73 185.13.115.85 9 Apr 14 13:20:04.506 Up 8 Apr 14 13:20:04.406 Originate Call 7 Apr 14 13:20:04.406 CSPF: computation result accepted 185.13.115.73 185.13.115.85 6 Apr 14 13:20:04.403 Clear Call 5 Apr 14 13:19:49.330 185.13.115.73: Explicit Route: bad loose route[9 times] 4 Apr 14 13:15:55.320 Originate Call 3 Apr 14 13:15:32.240 CSPF failed: no route toward 172.16.16.2[7 times] 2 Apr 14 13:13:05.241 CSPF failed: no route toward 195.128.59.177[3 times] 1 Apr 14 13:12:07.665 CSPF failed: no route toward 172.16.16.5[42 times] Created: Tue Apr 14 12:52:37 2015 Total 1 displayed, Up 0, Down 1 admin@mx80-pe_Himki> show log mpls-log Apr 14 13:51:38.697603 Allocated primary path Apr 14 13:51:38.698653 MPLS config finished. Apr 14 13:51:38.780433 mpls LSP update start Apr 14 13:51:38.790026 Reconfig LSP Ximki>M10 0x270471c Apr 14 13:51:38.790114 Reconfig LSP Ximki>M9 0x2704e38 Apr 14 13:51:38.790200 mpls LSP Ximki>M9 clearing restart flag Apr 14 13:51:38.790263 mpls lsp Ximki>M9 primary Clear Call Apr 14 13:51:38.791547 RPD_MPLS_PATH_DOWN: MPLS path down on LSP Ximki>M9 Apr 14 13:51:38.791605 CSPF adding path Ximki>M9(primary TO_M9_MED) to CSPF queue 0 Apr 14 13:51:38.791630 CSPF delay CSPF job, re-configuration in progress. Apr 14 13:51:38.791702 mpls LSP update complete Apr 14 13:51:38.791732 CSPF creating CSPF job Apr 14 13:51:38.795285 Apr 14 13:51:38.795323 CSPF for path Ximki>M9(primary TO_M9_MED), begin at 0000.0000.0000.00 , starting Apr 14 13:51:38.795370 bandwidth: CT0=0bps ; setup priority: 0; random Apr 14 13:51:38.795425 CSPF ERO 1 loose next hop to 172.16.16.5 Apr 14 13:51:38.795470 CSPF starting from 0000.0000.0000.00 (172.16.16.8) to 172.16.16.5, hoplimit 254 Apr 14 13:51:38.795553 CSPF Reached target Apr 14 13:51:38.795589 CSPF completed in 0.000131s Apr 14 13:51:38.795644 CSPF ERO for Ximki>M9(primary TO_M9_MED) (3 hops) Apr 14 13:51:38.795671 node 185.13.115.73/32 Apr 14 13:51:38.795693 node 185.13.115.85/32 Apr 14 13:51:38.795714 node 195.128.59.173/32 Apr 14 13:51:38.795734 CSPF credibility 0 Apr 14 13:51:38.795755 CSPF final destination 172.16.16.2 Apr 14 13:51:38.795794 CSPF starting from 0000.0000.0000.00 (172.16.16.5) to 172.16.16.2, hoplimit 251 Apr 14 13:51:38.795850 CSPF completed in 0.000066s Apr 14 13:51:38.795875 CSPF couldn't find a route to 172.16.16.2 Apr 14 13:51:38.795931 mpls lsp Ximki>M9 primary CSPF failed: no route toward 172.16.16.2 Apr 14 13:51:38.795957 CSPF for path Ximki>M9(primary TO_M9_MED) done! Apr 14 13:51:38.796330 mpls lsp Ximki>M9 primary Deselected as active Apr 14 13:51:38.797641 RPD_MPLS_LSP_DOWN: MPLS LSP Ximki>M9 down on primary(TO_M9_MED) Apr 14 13:52:08.190991 CSPF adding path Ximki>M9(primary TO_M9_MED) to CSPF queue 0 Apr 14 13:52:08.191560 CSPF creating CSPF job Apr 14 13:52:08.191677 Apr 14 13:52:08.191706 CSPF for path Ximki>M9(primary TO_M9_MED), begin at 0000.0000.0000.00 , starting Apr 14 13:52:08.191754 bandwidth: CT0=0bps ; setup priority: 0; random Apr 14 13:52:08.191809 CSPF ERO 1 loose next hop to 172.16.16.5 Apr 14 13:52:08.191854 CSPF starting from 0000.0000.0000.00 (172.16.16.8) to 172.16.16.5, hoplimit 254 Apr 14 13:52:08.192053 CSPF Reached target Apr 14 13:52:08.192091 CSPF completed in 0.000153s Apr 14 13:52:08.192151 CSPF ERO for Ximki>M9(primary TO_M9_MED) (3 hops) Apr 14 13:52:08.192177 node 185.13.115.73/32 Apr 14 13:52:08.192198 node 185.13.115.85/32 Apr 14 13:52:08.192219 node 195.128.59.173/32 Apr 14 13:52:08.192238 CSPF credibility 0 Apr 14 13:52:08.192258 CSPF final destination 172.16.16.2 Apr 14 13:52:08.192299 CSPF starting from 0000.0000.0000.00 (172.16.16.5) to 172.16.16.2, hoplimit 251 Apr 14 13:52:08.192355 CSPF completed in 0.000067s Apr 14 13:52:08.192380 CSPF couldn't find a route to 172.16.16.2 Apr 14 13:52:08.192436 mpls lsp Ximki>M9 primary CSPF failed: no route toward 172.16.16.2 Apr 14 13:52:08.192460 CSPF for path Ximki>M9(primary TO_M9_MED) done! admin@mx80-pe_Himki> admin@mx80-pe_Himki> show route table inet.3 inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 172.16.16.6/32 *[RSVP/7/1] 8w0d 21:51:04, metric 1 > to 185.13.115.73 via xe-0/0/0.78, label-switched-path Ximki>M10 admin@mx80-pe_Himki> куда копать?:) Вставить ник Quote
fomka31ru Posted April 14, 2015 Posted April 14, 2015 (edited) ... Edited April 14, 2015 by fomka31ru Вставить ник Quote
rdntw Posted April 14, 2015 Author Posted April 14, 2015 лупбеки в мплс загоните. from 172.16.16.8 уже давно не пишут - остатки прошлого. ну и картинку то хорошо было бы лупбеки куда загнать?:) если вы про OSPF они там есть, если как interface lo0.0 в контексте MPLS то я не уверен что поможет... картинка есть, какую еще нужно? Вставить ник Quote
fomka31ru Posted April 14, 2015 Posted April 14, 2015 ***, инет чудит, пока писал, половина отправилась, картинки не видно было, сорри Вставить ник Quote
fomka31ru Posted April 14, 2015 Posted April 14, 2015 чего посоветовать - проверяйте интерфейсы, фемели мплс. чего-то забыли Вставить ник Quote
rdntw Posted April 14, 2015 Author Posted April 14, 2015 чего посоветовать - проверяйте интерфейсы, фемели мплс. чего-то забыли да это всё уже проверено..самое интересное что напрямую на 16.5 и 16.2 LSP поднимаются. не работает именно rsvp ero Вставить ник Quote
fomka31ru Posted April 14, 2015 Posted April 14, 2015 Тогда такой квест. Линк между .2 и .6 потушите и постройте лсп от.8 до .2 Traffic engineering в оспф прописан? Router-id везде есть? Может быть, где-то есть router-id, где-то берется из лупбека, может они совпадают? Вставить ник Quote
rdntw Posted April 14, 2015 Author Posted April 14, 2015 Тогда такой квест. Линк между .2 и .6 потушите и постройте лсп от.8 до .2 Traffic engineering в оспф прописан? Router-id везде есть? Может быть, где-то есть router-id, где-то берется из лупбека, может они совпадают? нашел :) не хватало RSVP-нейбора на cat65, невнимательность :( спасибо! Вставить ник Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.