RIPE NCC Training Course Material
Latest version: 20190815
Table of Contents
- LIR Training Course
This is a one-day introduction to the RIPE NCC administrative procedures and RIPE Policies related to obtaining and distributing Internet number resources (i.e. IP addresses, AS Numbers), operating a Local Internet Registry (LIR) and working with the RIPE Database. - RIPE Database Training Course
This one-day course will teach you how to use the RIPE Database like a pro. Using a combination of hands-on activities with theory, you will get a comprehensive idea of what the RIPE Database is and what you can do with it. - Basic IPv6 Training Course
This one-day course will teach you about the need for IPv6 and provide you with basic information about how to start planning your deployment. - Advanced IPv6 Training Course
This is a two-day practical course about IPv6 technical details, including dynamic protocols such as OSPF and BGP. - IPv6 Security Training Course
This one-day course provides an overview of the most relevant IPv6 security topics. You will gain insight into industry best practice and gain a high-level understanding of the most pressing IPv6 security concerns today. - BGP Operations and Security Training Course
This one-day course offers an in-depth look into Border Gateway Protocol (BGP). After this course, you will be capable of reinforcing theory through practice with our interactive exercises following each topic. - DNSSEC Training Course
This is a one-day practical training course that will teach you how DNSSEC works and the related procedures and tools.
- Measurements and Tools Training Course
This one-day introductory hands-on course will teach you the basics of RIPEstat and RIPE Atlas. - Additional information
Here you will find a list of useful links.
Training Courses
Local Internet Registry (LIR) Training Course
RIPE Database Training Course
Basic IPv6 Training Course
- Course Slides
- Training Exercise: Addressing Plan with Possible Solutions
- Training Exercise: IPv6 Address Notation Solution
- IPv6 Address Types
- IPv6 Subnetting Card
Advanced IPv6 Training Course
IPv6 Security Training Course
BGP Operations and Security Training Course
- Course Overview
- Course Slides
- Course Laboratories Appendix
- Course Database Objects Appendix
- Route Object Creation Flowchart
Additional references (External links)
- BGP:
- A Border Gateway Protocol 4 (RFC-4271)
- Multiprotocol Extensions for BGP-4 (RFC-4726)
- BGP-4 Implementation Report (RFC-4276)
- Experience with the BGP-4 Protocol (RFC-4277)
- Capabilities Advertisement with BGP-4 (RFC-2842)
- BGP Communities Attribute (RFC-1997)
- BGP Extended Communities Attribute (RFC-4360)
- BGP Route Reflection (RFC-4456)
- RIPE Database:
- RPSL:
- Routing Policy Specification Language (RFC-2622)
- Routing Policy System Security (RFC-2725)
- Using RPSL in Practice (RFC-2650)
- Recomendations on IPv4 Route Aggregations
- An Application of the BGP Community Attribute in Multi-home Routing (RFC 1998)
- Routing Policy Specification Language next generation (RFC 4012)
- Routing Information Service Project
- Routing Registry Consistency Project
- Resource Certification:
DNSSEC Training Course
Measurements and Tools Training Course
(covering RIPEstat and RIPE Atlas)
- Course Overview
- Course Slides
- Course Exercises
- Course Exercises Solutions
- Course Slides in Keynote format (with additional notes and explanations)
- Course Slides in PowerPoint format
Additional Information
All material is provided by the RIPE NCC under 2-Clause BSD License.Created: 31 Dec 2010 – Last updated: 27 Aug 2019 “” TRAINING
Huawei Wi-Fi 6 (802.11ax) Technology White Paper
huawei ağ ekipmanlarında basit martini vpls uygulaması
aşağıdaki topoloji üzerinde huawei ağ ekipmanlarını kullanarak basit bir mpls martini vpls örneği yapalım.
öncelikle loopback ve ip tanımlarını sırasıyla yapalım.
sysname R1
interface GigabitEthernet0/0/0
ip address 10.1.1.1 255.255.255.0
interface LoopBack0
ip address 192.168.0.1 255.255.255.255
sysname R2
interface GigabitEthernet0/0/0
ip address 10.1.1.2 255.255.255.0
interface GigabitEthernet0/0/1
ip address 10.2.2.2 255.255.255.0
interface LoopBack0
ip address 192.168.0.2 255.255.255.255
sysname R3
interface GigabitEthernet0/0/1
ip address 10.2.2.1 255.255.255.0
interface LoopBack0
ip address 192.168.0.3 255.255.255.255
tüm arayüzler aktif olduktan sonra örnekte ospf yönlendirme protokolünü kullanacağımız için yönlendiriciler üzerinde ospf leri aktif etmek için gerekli yapılandırmasını yapalım.
sysname R1
ospf 1
area 0.0.0.0
network 192.168.0.1 0.0.0.0
network 10.1.1.0 0.0.0.255
sysname R2
ospf 1
area 0.0.0.0
network 192.168.0.2 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.2.2.0 0.0.0.255
sysname R3
ospf 1
area 0.0.0.0
network 10.2.2.0 0.0.0.255
network 192.168.0.3 0.0.0.0
ospf de aktif olduktan sonra mpls tanımlarına başlayabiliriz. tüm yönlendiriciler de global de mpls i aktif edelim.
mpls lsr-id 192.168.0.x
mpls
mpls l2vpn
mpls ldp
sonrasında ağımızda yönlendiriciler arasındaki arayüz bağlantıları altında mpls, mpls ldp aktif ediyoruz.
interface GigabitEthernet0/0/x
mpls
mpls ldp
en temel kontrolleri yaptık bir sorun görülmüyor. şimdi pc1 – pc2 arasındaki haberleşmenin sağlanması için gerekli yapılandırmaya sıra geldi. öncelikle r1 den r3 , r3 den r1 doğru ldp remote tanımlarını yapmalıyız.
sysname R1
mpls ldp remote-peer ldp_peer_to_r3
remote-ip 192.168.0.3
sysname R3
mpls ldp remote-peer ldp_peer_to_r1
remote-ip 192.168.0.1
şimdi yapabileceğimiz bazı kontrolleri yapalım.
<R1>display mpls interface
Interface Status TE Attr LSP Count CRLSP Count Effective MTU
GE0/0/0 Up Dis 4 0 1500
<R1>
<R1>display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
------------------------------------------------------------------------------
PeerID Status LAM SsnRole SsnAge KASent/Rcv
------------------------------------------------------------------------------
192.168.0.2:0 Operational DU Passive 0000:01:45 423/423
192.168.0.3:0 Operational DU Passive 0000:01:53 455/455
------------------------------------------------------------------------------
TOTAL: 2 session(s) Found.
[R1]display mpls route-state
Codes: B(BGP), I(IGP), L(Public Label BGP), O(Original BGP), U(Unknow)
--------------------------------------------------------------------------------
Dest/Mask Next-Hop Out-Interface State LSP VRF Type
--------------------------------------------------------------------------------
192.168.0.1/32 127.0.0.1 InLoop0 READY 1 0 I
192.168.0.2/32 10.1.1.2 GE0/0/0 READY 2 0 I
192.168.0.3/32 10.1.1.2 GE0/0/0 READY 2 0 I
[R1]display mpls lsp
-------------------------------------------------------------------------------
LSP Information: LDP LSP
-------------------------------------------------------------------------------
FEC In/Out Label In/Out IF Vrf Name
192.168.0.2/32 NULL/3 -/GE0/0/0
192.168.0.2/32 1028/3 -/GE0/0/0
192.168.0.3/32 NULL/1025 -/GE0/0/0
192.168.0.3/32 1029/1025 -/GE0/0/0
192.168.0.1/32 3/NULL -/-
şimdi vsi ları oluşturalım. burada dikkat edilmesi gereken en önemli nokta vsi-id lerin aynı olması gerektiğidir.
sysname R1
vsi vsi_for_pc static
pwsignal ldp
vsi-id 100
peer 192.168.0.3
sysname R3
vsi vsi_for_pc static
pwsignal ldp
vsi-id 100
peer 192.168.0.1
son aşamaya gelmiş olduk. bilgisayarların bağlı arayüzler için tanımları da tapalım.
sysname R1
interface Ethernet0/0/1
l2 binding vsi vsi_for_pc
sysname R3
interface Ethernet0/0/1
l2 binding vsi vsi_for_pc
tüm yapılandırmaları tamamlamış olduk. şimdi bilgisayarlara ip leri girerek erişim kontrolleri yapalım. bilgisayarlarda ağ geçidi olarak karşı bilgisayarın iplerini girelim.
PC>ping 100.1.1.2
Ping 100.1.1.2: 32 data bytes, Press Ctrl_C to break
From 100.1.1.2: bytes=32 seq=1 ttl=128 time=94 ms
From 100.1.1.2: bytes=32 seq=2 ttl=128 time=156 ms
From 100.1.1.2: bytes=32 seq=3 ttl=128 time=62 ms
From 100.1.1.2: bytes=32 seq=4 ttl=128 time=94 ms
From 100.1.1.2: bytes=32 seq=5 ttl=128 time=110 ms
--- 100.1.1.2 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 62/103/156 ms
yönlendiricilere ait yapılandırmaların tam hali aşağıda yer almaktadır.
sysname R1
mpls lsr-id 192.168.0.1
mpls
mpls l2vpn
mpls ldp
vsi vsi_for_pc static
pwsignal ldp
vsi-id 100
peer 192.168.0.3
mpls ldp remote-peer ldp_peer_to_r3
remote-ip 192.168.0.3
interface Ethernet0/0/1
l2 binding vsi vsi_for_pc
interface GigabitEthernet0/0/0
ip address 10.1.1.1 255.255.255.0
mpls
mpls ldp
interface LoopBack0
ip address 192.168.0.1 255.255.255.255
ospf 1
area 0.0.0.0
network 192.168.0.1 0.0.0.0
network 10.1.1.0 0.0.0.255
sysname R2
mpls lsr-id 192.168.0.2
mpls
mpls ldp
interface GigabitEthernet0/0/0
ip address 10.1.1.2 255.255.255.0
mpls
mpls ldp
interface GigabitEthernet0/0/1
ip address 10.2.2.2 255.255.255.0
mpls
mpls ldp
interface LoopBack0
ip address 192.168.0.2 255.255.255.255
ospf 1
area 0.0.0.0
network 192.168.0.2 0.0.0.0
network 10.1.1.0 0.0.0.255
network 10.2.2.0 0.0.0.255
sysname R3
mpls lsr-id 192.168.0.3
mpls
mpls l2vpn
mpls ldp
vsi vsi_for_pc static
pwsignal ldp
vsi-id 100
peer 192.168.0.1
mpls ldp remote-peer ldp_peer_to_r1
remote-ip 192.168.0.1
interface Ethernet0/0/1
l2 binding vsi vsi_for_pc
interface GigabitEthernet0/0/1
ip address 10.2.2.1 255.255.255.0
mpls
mpls ldp
interface LoopBack0
ip address 192.168.0.3 255.255.255.255
ospf 1
area 0.0.0.0
network 10.2.2.0 0.0.0.255
network 192.168.0.3 0.0.0.
nokia sros için araçlar
genel olarak network ekipmanlarında cli ile konfigürasyon yapıyorsanız sıklıkla kopyala – yapıştır yapıyorsunuzdur. ancak bu yöntem hatalara oldukça açıktır.
bu hatayı minimize etmek adına python ile yazılmış nokia sros güzel bir kod bulmuştum. bunu paylaşmak istedim. örnek için aşağıdaki şekilde bir konfigürasyonumuz olsun.. bunu c1.txt olarak kaydediyoruz.
vpls 11 customer 1 vpn 11 i-vpls create
backbone-vpls 100:11
exit
stp
shutdown
exit
sap 1/5/1:11 create
exit
sap 1/5/1:12 create
exit
no shutdown
exit
vpls 100 customer 1 vpn 100 b-vpls create
service-mtu 2000
stp
shutdown
exit
mrp
flood-time 10
no shutdown
exit
sap 1/5/1:100 create
exit
spoke-sdp 3101:100 create
exit
spoke-sdp 3201:100 create
exit
no shutdown
exit
t.py olarak kaydettiğimiz python kodunu çalıştığımızda mevcut kodumuz aşağıdaki örnekte görüleceği üzere yeniden düzenleniyor. bu şekilde bir yapı bir çok olası hatanın önüne geçecektir.
fcicek@cicek:~/mpls/sros$ python t.py c1.txt
/configure vpls 11 customer 1 vpn 11 i-vpls create backbone-vpls 100:11
/configure vpls 11 customer 1 vpn 11 i-vpls create stp shutdown
/configure vpls 11 customer 1 vpn 11 i-vpls create sap 1/5/1:11 create
/configure vpls 11 customer 1 vpn 11 i-vpls create sap 1/5/1:12 create
/configure vpls 11 customer 1 vpn 11 i-vpls create no shutdown
/configure vpls 100 customer 1 vpn 100 b-vpls create service-mtu 2000
/configure vpls 100 customer 1 vpn 100 b-vpls create stp shutdown
/configure vpls 100 customer 1 vpn 100 b-vpls create mrp flood-time 10
/configure vpls 100 customer 1 vpn 100 b-vpls create mrp no shutdown
/configure vpls 100 customer 1 vpn 100 b-vpls create sap 1/5/1:100 create
/configure vpls 100 customer 1 vpn 100 b-vpls create spoke-sdp 3101:100 create
/configure vpls 100 customer 1 vpn 100 b-vpls create spoke-sdp 3201:100 create
/configure vpls 100 customer 1 vpn 100 b-vpls create no shutdown
kullanılan t.py
#!/usr/bin/env python3
import re
import math
import sys
def pop(stack):
try:
stack.pop()
except Exception as err:
print("ERROR: Unable to flush stack - %s" %err)
def output(stack):
output = " ".join(stack)
print(output)
return output
def sros_flatten(data):
stack = []
exit_detected = False
indent = 0
new_conf = ""
for line in data.lstrip().splitlines():
l = len(line) - len(line.lstrip())
nxt_indent = math.ceil(float(l/4))
if line.startswith(("#", "echo")) or line.strip() == "":
pass
elif line.strip() == "exit all":
new_conf = new_conf + "\n" + output(stack)
else:
if nxt_indent == 0 and line.strip() == "configure":
new_line = str("/") + str(line.strip())
stack.append(new_line)
elif nxt_indent > indent:
if line.strip() != "configure" and len(stack) == 0:
stack.insert(0, "/configure")
stack.append(line.lstrip())
elif nxt_indent == indent:
if line.strip() != "exit":
if exit_detected:
stack.append(line.strip())
else:
if len(stack) != 0:
new_conf = new_conf + "\n" + output(stack)
pop(stack)
stack.append(line.strip())
else:
stack.insert(0, "/configure")
stack.append(line.strip())
exit_detected = False
else:
if line.strip() == "exit":
if not exit_detected:
new_conf = new_conf + "\n" + output(stack)
del stack[-2:]
else:
pop(stack)
exit_detected = True
else:
new_conf = new_conf + "\n" + output(stack)
exit_detected = False
pop(stack)
indent = nxt_indent
return new_conf
def main():
filename = sys.argv[1]
with open(filename, 'r') as f:
data = f.read()
sros_flatten(data)
if __name__ == "__main__":
main()
huawei ağ ekipmanlarında basit ospf uygulaması
ospf detaylarına girmeden huawei ağ ekipmanlarında ospf nasıl kullanabiliriz ve kontrol edebiliriz aşağıdaki örnek topolojide incelemeye çalışalım.
yönlendiriciler üzerine öncelikle arayüz iplerini girelim
sysname R1
router id 192.168.0.1
interface Ethernet0/0/1
ip address 192.168.100.1 255.255.255.0
interface GigabitEthernet0/0/0
ip address 192.168.1.1 255.255.255.252
interface LoopBack0
ip address 192.168.0.1 255.255.255.255
sysname R2
router id 192.168.0.2
interface Ethernet0/0/1
ip address 192.168.101.1 255.255.255.0
interface GigabitEthernet0/0/0
ip address 192.168.1.2 255.255.255.252
interface LoopBack0
ip address 192.168.0.2 255.255.255.255
arayüzlerin durumunu kontrol edelim
<R1>display ip interface brief
*down: administratively down
!down: FIB overload down
^down: standby
(l): loopback
(s): spoofing
(d): Dampening Suppressed
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 8
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 8
Interface IP Address/Mask Physical Protocol
Ethernet0/0/0 unassigned down down
Ethernet0/0/1 192.168.100.1/24 up up
GigabitEthernet0/0/0 192.168.1.1/30 up up
GigabitEthernet0/0/1 unassigned down down
GigabitEthernet0/0/2 unassigned down down
GigabitEthernet0/0/3 unassigned down down
LoopBack0 192.168.0.1/32 up up(s)
NULL0 unassigned up up(s)
Serial0/0/0 unassigned down down
Serial0/0/1 unassigned down down
Serial0/0/2 unassigned down down
Serial0/0/3 unassigned down down
tüm arayüzlerimiz aktif durumda. yönlendirme tablolarını da kontrol edelim
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost Flags NextHop Interface
127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0
127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
192.168.0.1/32 Direct 0 0 D 127.0.0.1 LoopBack0
192.168.1.0/30 Direct 0 0 D 192.168.1.1 GigabitEthernet0/0/0
192.168.1.1/32 Direct 0 0 D 127.0.0.1 GigabitEthernet0/0/0
192.168.100.0/24 Direct 0 0 D 192.168.100.1 Ethernet0/0/1
192.168.100.1/32 Direct 0 0 D 127.0.0.1 Ethernet0/0/1
R1 üzerinde görüleceği üzere pc1 den pc2 ye ulaşmak istersek R1 üzerinden gerekli yönlendirme yapılamayacaktır. bu yönlendirme işlemini ospf ile yapmaya çalışalım..
R1 üzerine area 0 oluşturalım ve cihaz üzerindeki tüm networkleri ekleyelim
[R1]ospf 1 router-id 192.168.0.1
[R1-ospf-1]area 0
[R1-ospf-1-area-0.0.0.0]network 192.168.100.0 0.0.0.255
[R1-ospf-1-area-0.0.0.0]network 192.168.1.0 0.0.0.3
[R1-ospf-1-area-0.0.0.0]network 192.168.0.1 0.0.0.0
r1 üzerinde ospf için gerekli ayarları yaptıktan sonra gerekli kontrolleri sağlayalım.
[R1]display ospf lsdb
OSPF Process 1 with Router ID 192.168.0.1
Link State Database
Area: 0.0.0.0
Type LinkState ID AdvRouter Age Len Sequence Metric
Router 192.168.0.1 192.168.0.1 440 60 80000005 1
<R1>display ospf nexthop
OSPF Process 1 with Router ID 192.168.0.1
Routing Nexthop information
Next hops:
Address Type Refcount IntfAddr Intf Name
----------------------------------------------------------------
192.168.100.1 Local 1 192.168.100.1 Ethernet0/0/1
192.168.1.1 Local 1 192.168.1.1 GigabitEthernet0/0/0
192.168.0.1 Local 1 192.168.0.1 LoopBack0
<R1>display ospf routing
OSPF Process 1 with Router ID 192.168.0.1
Routing Tables
Routing for Network
Destination Cost Type NextHop AdvRouter Area
192.168.0.1/32 0 Stub 192.168.0.1 192.168.0.1 0.0.0.0
192.168.1.0/30 1 Stub 192.168.1.1 192.168.0.1 0.0.0.0
192.168.100.0/24 1 Stub 192.168.100.1 192.168.0.1 0.0.0.0
Total Nets: 3
Intra Area: 3 Inter Area: 0 ASE: 0 NSSA: 0
[R1]display ip routing-table
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost Flags NextHop Interface
127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0
127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
192.168.0.1/32 Direct 0 0 D 127.0.0.1 LoopBack0
192.168.1.0/30 Direct 0 0 D 192.168.1.1 GigabitEthernet0/0/0
192.168.1.1/32 Direct 0 0 D 127.0.0.1 GigabitEthernet0/0/0
192.168.100.0/24 Direct 0 0 D 192.168.100.1 Ethernet0/0/1
192.168.100.1/32 Direct 0 0 D 127.0.0.1 Ethernet0/0/1
şimdi R2 üzefinde ospf konfigürasyonu yapmaya başlayalım. ilk önce area 0 oluşturalım ve R1 arayünün ip networke ekleyelim ve değişimleri gözlemleyelim
<R1>display ospf lsdb
OSPF Process 1 with Router ID 192.168.0.1
Link State Database
Area: 0.0.0.0
Type LinkState ID AdvRouter Age Len Sequence Metric
Router 192.168.0.2 192.168.0.2 35 36 80000003 1
Router 192.168.0.1 192.168.0.1 31 60 80000009 1
Network 192.168.1.1 192.168.0.1 31 32 80000002 0
<R1>display ospf routing
OSPF Process 1 with Router ID 192.168.0.1
Routing Tables
Routing for Network
Destination Cost Type NextHop AdvRouter Area
192.168.0.1/32 0 Stub 192.168.0.1 192.168.0.1 0.0.0.0
192.168.1.0/30 1 Transit 192.168.1.1 192.168.0.1 0.0.0.0
192.168.100.0/24 1 Stub 192.168.100.1 192.168.0.1 0.0.0.0
Total Nets: 3
Intra Area: 3 Inter Area: 0 ASE: 0 NSSA: 0
<R1>display ospf nexthop
OSPF Process 1 with Router ID 192.168.0.1
Routing Nexthop information
Next hops:
Address Type Refcount IntfAddr Intf Name
----------------------------------------------------------------
192.168.100.1 Local 1 192.168.100.1 Ethernet0/0/1
192.168.1.1 Local 1 192.168.1.1 GigabitEthernet0/0/0
192.168.0.1 Local 1 192.168.0.1 LoopBack0
<R1>display ip routing-table
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 7 Routes : 7
Destination/Mask Proto Pre Cost Flags NextHop Interface
127.0.0.0/8 Direct 0 0 D 127.0.0.1 InLoopBack0
127.0.0.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
192.168.0.1/32 Direct 0 0 D 127.0.0.1 LoopBack0
192.168.1.0/30 Direct 0 0 D 192.168.1.1 GigabitEthernet0/0/0
192.168.1.1/32 Direct 0 0 D 127.0.0.1 GigabitEthernet0/0/0
192.168.100.0/24 Direct 0 0 D 192.168.100.1 Ethernet0/0/1
192.168.100.1/32 Direct 0 0 D 127.0.0.1 Ethernet0/0/1
R2 için diğer networkleride ekleyelim. yönlendirme tabloları , lsdb vb deki değişimleri gözlemleyelim.
ospf 1 router-id 192.168.0.2
area 0.0.0.0
network 192.168.1.0 0.0.0.3
network 192.168.0.2 0.0.0.0
network 192.168.101.0 0.0.0.255
tüm networkleri r2 üzerinde tamamladıktan sonra yönlendirme tablosunu kontrol ederek pc1 den pc2 ye erişimi kontrol edelim.
<R1>display ospf routing
OSPF Process 1 with Router ID 192.168.0.1
Routing Tables
Routing for Network
Destination Cost Type NextHop AdvRouter Area
192.168.0.1/32 0 Stub 192.168.0.1 192.168.0.1 0.0.0.0
192.168.1.0/30 1 Transit 192.168.1.1 192.168.0.1 0.0.0.0
192.168.100.0/24 1 Stub 192.168.100.1 192.168.0.1 0.0.0.0
192.168.0.2/32 1 Stub 192.168.1.2 192.168.0.2 0.0.0.0
192.168.101.0/24 2 Stub 192.168.1.2 192.168.0.2 0.0.0.0
Total Nets: 5
Intra Area: 5 Inter Area: 0 ASE: 0 NSSA: 0
PC>ping 192.168.101.1
Ping 192.168.101.1: 32 data bytes, Press Ctrl_C to break
From 192.168.101.1: bytes=32 seq=1 ttl=254 time=62 ms
From 192.168.101.1: bytes=32 seq=2 ttl=254 time=94 ms
From 192.168.101.1: bytes=32 seq=3 ttl=254 time=78 ms
From 192.168.101.1: bytes=32 seq=4 ttl=254 time=78 ms
From 192.168.101.1: bytes=32 seq=5 ttl=254 time=47 ms
--- 192.168.101.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 47/71/94 ms
Huawei Stack & SVF Assistant
huawei’nin support sayfaları arasında huawei network ekipmanlarının stack bağlantılarında yardımcı olacak bir araç mevcut.
http://support.huawei.com/onlinetoolsweb/virtual/index?lang=en&domain=1
Oktay hocam söylerde paylaşmaz mıyım hiç 🙂
huawei network ekipmanlarında mevcut yapılandırmaları sıfırlamak
bazı zamanlarda yapılandırmayı sıfırdan yapmak bir zorunluluk veya tercih olacaktır. bu gibi durumlarda huawei ekipmanları üzerindeki mevcut yapılandırmalardan kurtulmanın en kolay yöntemi bir çok network ekipmanında olduğu gibi açılış sırasında işletilen yapılandırma dosyasını / ayarlarını yok etmek ve ekipmanı yeniden başlatmaktır.
huawei de bu yapmak için konfig moda girmeden “reset saved-configuration” ile konfigürasyon dosyasını silerek sürece başlıyoruz.
<r6>reset saved-configuration
Warning: The action will delete the saved configuration in the device.
The configuration will be erased to reconfigure. Continue? [Y/N]:Y
Warning: Now clearing the configuration in the device.
Apr 30 2019 23:57:46-08:00 r6 %%01CFM/4/RST_CFG(l)[2]:The user chose Y when deci
ding whether to reset the saved configuration.
Info: Succeeded in clearing the configuration in the device.
sonrasında ise network ekipmanımızı reboot ediyoruz… promttan görüleceği üzere örneğimizde router konfigürasyonu sıfırlanmış oldu.
<r6>reboot
Info: The system is now comparing the configuration, please wait.
Warning: All the configuration will be saved to the configuration file for the n
ext startup:, Continue?[Y/N]:N
Info: If want to reboot with saving diagnostic information, input 'N' and then e
xecute 'reboot save diagnostic-information'.
System will reboot! Continue?[Y/N]:Y
Apr 30 2019 23:57:57-08:00 r6 %%01CMD/4/REBOOT(l)[3]:The user chose Y when decid
ing whether to reboot the system. (Task=co0, Ip=**, User=**)
<r6>####################
<Huawei>
huawei network ekipmanlarında dhcp
bir önceki https://ferhatcicek.com/2019/04/28/huawei-network-ekipmanlarinda-en-basitinden-dhcp/yazıda huawei network ekipmanlarından en basit dhcp ayarlarının nasıl yapılacağı anlatılmıştı. şimdi işi biraz daha kurallarına uygun şekilde yapalım.
topolojimizde bir değişiklik yapmıyoruz. bu örneğimizde iki farklı ip havuzu oluşturacağız ve portlar da atadığımız vlana göre ip dağıtımı yapacağız. dhcp yi globalde aktif ettikten sonra ip havuzlarımızı oluşturalım.
dhcp enable
ip pool pool1
gateway-list 192.0.1.1
network 192.0.1.0 mask 255.255.255.0
lease day 10 hour 0 minute 0
dns-list 8.8.8.8
ip pool pool2
gateway-list 192.0.2.1
network 192.0.2.0 mask 255.255.255.0
lease day 6 hour 0 minute 0
dns-list 8.8.8.8
sonrasında kullanacağımız vlanları oluşturarak dhcp ile ilişkilendirmesini yapalım
vlan batch 10 to 11
interface Vlanif10
ip address 192.0.1.1 255.255.255.0
dhcp select global
interface Vlanif11
ip address 192.0.2.1 255.255.255.0
dhcp select global
kulanacağımız portları aktif ederek uygun vlan atamasını yapalım.
interface GigabitEthernet0/0/1
port hybrid pvid vlan 10
port hybrid untagged vlan 10
interface GigabitEthernet0/0/2
port hybrid pvid vlan 11
port hybrid untagged vlan 11
sıra geldik kontrolleri yapmaya
display ip pool name pool1
Pool-name : pool1
Pool-No : 0
Lease : 10 Days 0 Hours 0 Minutes
Domain-name : -
DNS-server0 : 8.8.8.8
NBNS-server0 : -
Netbios-type : -
Position : Local Status : Unlocked
Gateway-0 : 192.0.1.1
Mask : 255.255.255.0
VPN instance : --
------------------------------------------------------
Start End Total Used Idle(Expired) Conflict Disable
------------------------------------------------------
192.0.1.1 192.0.1.254 253 1 252(0) 0 0
------------------------------------------------------