⏱ O‘qish vaqti: 2 daqiqa
Qisqacha
- Traffic‑Eng tunnelning joriy holatini
/interface traffic-eng monitorbuyrug‘i bilan ko‘rish. - Link uzilganda tunnel avtomatik yo‘lni o‘zgartiradi, lekin eski yo‘lni saqlab qoladi.
reoptimizebuyrug‘i yordamida tunnelni yangi eng yaxshi yo‘lga majburlash.- Yangi yo‘lni
explicit-routevarecorded-routemaydonlari orqali tasdiqlash. - Bandwidth va priority parametrlarini sozlash imkoniyatlari.
Traffic‑Eng (TE) LSP tunnellari tarmoqda optimal marshrutni ta’minlash uchun ishlatiladi. Biroq, link uzilganda tunnel eski yo‘lda qolishi yoki yangi yo‘lni tanlashi kerak. Ushbu qo‘llanma RouterOS’da TE tunnel holatini tekshirish, qo‘lda reoptimallashtirish va natijani tasdiqlashni ko‘rsatadi.
Talablar
- RouterOS 7+ qurilmaga admin kirish
- MPLS va Traffic‑Eng konfiguratsiyasi allaqachon yaratilgan
- CLI (terminal)ga kirish imkoniyati
Sozlash bosqichlari
1. Tunnel holatini monitoring qilish
/interface traffic-eng monitor buyrug‘i yordamida tunnelning joriy holatini ko‘rasiz. Natijada primary-path-state, active-path va explicit-route kabi maydonlar ko‘rsatiladi.
/interface traffic-eng monitor 0
tunnel-id: 12
primary-path-state: on-hold
secondary-path-state: established
secondary-path: static
active-path: static
active-lspid: 3
active-label: 66
explicit-route: "S:192.168.55.10/32,L:192.168.55.13/32,L:192.168.55.17/32"
recorded-route: "192.168.55.13[66],192.168.55.17[59],192.168.55.18[3]"
reserved-bandwidth: 5.0Mbps2. Link uzilganda avtomatik yo‘l o‘zgarishini tekshirish
Link uzilgandan keyin monitor buyrug‘ini qayta bajarish orqali tunnelning yangi yo‘lga o‘tganini tasdiqlang. primary-path-state “established” va active-path “dyn” ko‘rinadi.
/interface traffic-eng monitor 0
tunnel-id: 12
primary-path-state: established
primary-path: dyn
secondary-path-state: not-necessary
active-path: dyn active-lspid: 1
active-label: 67
explicit-route: "S:192.168.55.10/32,S:192.168.55.13/32,S:192.168.55.14/32,
S:192.168.55.17/32,S:192.168.55.18/32"
recorded-route: "192.168.55.13[67],192.168.55.17[60],192.168.55.18[3]"
reserved-bandwidth: 5.0Mbps3. Qo‘lda reoptimallashtirish
Tunnelni yangi eng yaxshi yo‘lga majburlash uchun reoptimize buyrug‘ini bajaring. Bu amaliyot tunnelni qayta hisoblab, optimal marshrutni tanlaydi.
/interface traffic-eng reoptimize 04. Yangi yo‘lni tasdiqlash
Reoptimallashtirishdan so‘ng monitor buyrug‘ini yana bir marta ishga tushiring. explicit-route va recorded-route qisqa yo‘lni ko‘rsatadi.
/interface traffic-eng monitor 0
tunnel-id: 12
primary-path-state: established
primary-path: dyn
secondary-path-state: not-necessary
active-path: dyn
active-lspid: 2 active-label: 81
explicit-route: "S:192.168.55.5/32,S:192.168.55.2/32,S:192.168.55.1/32"
recorded-route: "192.168.55.2[81],192.168.55.1[3]"
reserved-bandwidth: 5.0MbpsTekshirish
Monitor buyrug‘i natijasida primary-path-state “established” va explicit-route qisqa yo‘l ko‘rsatilgan bo‘lishi kerak.
/interface traffic-eng monitor 0
tunnel-id: 12
primary-path-state: established
primary-path: dyn
secondary-path-state: not-necessary
active-path: dyn
active-lspid: 2 active-label: 81
explicit-route: "S:192.168.55.5/32,S:192.168.55.2/32,S:192.168.55.1/32"
recorded-route: "192.168.55.2[81],192.168.55.1[3]"
reserved-bandwidth: 5.0MbpsDiqqat:
- Reoptimallashtirish vaqtida trafik qisqa muddatga yo‘qolishi mumkin.
reoptimize-intervalsozlamasini tekshiring, aks holda tunnel avtomatik qayta optimallashtirilmasligi mumkin.- Qo‘lda reoptimallashtirishdan oldin asosiy va ikkinchi yo‘llar to‘g‘ri belgilanganligiga ishonch hosil qiling.
Muammolar va yechimlar
Tunnel hali ham eski yo‘lda qoladi
reoptimize-interval ni sozlang yoki qo‘lda reoptimize buyrug‘ini qayta bajaring.
Xulosa
Traffic‑Eng tunnellarni monitoring qilish va qo‘lda reoptimallashtirish tarmoq unumdorligini oshiradi. RouterOS’da bu amallar oddiy CLI buyrug‘lari bilan bajariladi. Yangi yo‘l tasdiqlangandan so‘ng tunnel optimal ishlashda davom etadi.
