Ostatnio pracuję w środowisku heterogenicznej infrastruktury sieciowej. Ale co to znaczy dziś heterogeniczna infrastruktura sieciowa jest to twór w którym mamy kliku różnych producentów sprzętu. Co raz częściej w spotykam się z sytuacją, że dany blog funkcjonalny jest realizowany przez jakiegoś producenta, np.
- sieć WAN
- Sieć LAN
- Sieć DC
z czasem przychodzi potrzeba aby połączyć te bloki funkcjonalne np. zestawić routing dynamiczny, czy skonfigurować dziś popularny EVPN – na ten temat będzie poświęcony oddzielny wpis na blogu.
Dziś pokażę jak poruszać się jednocześnie w tej samej płaszczyźnie na wielu urządzeniach takich jak:
- Juniper
- Cisco
- Arista
- Cumulus Networks
Wszystko zostało uruchomione jako wirtualne maszyny na Vmware Workstation.
Poniżej poruszę podstawowe zagadnienia takie jak:
- podstawowe polecenia
- konfiguracja interfejsów
- konfiguracja routingu statycznego
- konfiguracja routingu dynamicznego w oparciu o OSPF
- weryfikacja konfiguracji
- na co zwracać uwagę
Spis Treści
Zaczynamy
Poniżej przedstawiam podstawy poruszania po poszczególnych urządzeniach a dokładnie w CLI na każdym z nich. Wiedza przedstawiona pozwoli zrozumieć jak konfigurujemy dane urządzenie oraz jak wygląda składnia CLI.
Schematy
L2
Aby lepiej było pracować poniżej rysunek poglądowy dla warstwy 2:
L3
Rysunek poglądowy dla warstwy 3
Podstawowe polecenia
Klika podstawowych poleceń dla każdego producenta.
| Polecenie | Arista | Cisco | Cumulus | Juniper |
| wyświetlenie konfiguracji aktywnej | show running-config | show running-config | net show configuration | show configuration
w setach show configuration | display set |
| zapisanie konfiguracji | copy running-config startup-config | write memory | brak | brak |
| przejście w tryb konfiguracji | configure | configure terminal | brak | configure |
| wyświetlenie ip interfejsów | show ip interface brief | show ip interface brief | net show interface | show interfaces terse |
| wyświetlenie tablicy routingu | show ip route | show ip route | net show route | show route |
| wyświetlenie wersji oprogramowania | show version | show version | net show version | show version |
| wyświetlenie konfiguracji hardware | show environment all | show inventory | brak | show chassis hardware |
| wygenerowanie show tech | show tech-support | show tech-support | request support information brief | |
| wyświetlenie czasu | show clock | show clock | net show time | show system uptime |
| wyświetlenie logów | show logging | show logging | show log messages | |
| wyświetlenie kont użytkowników | show user-account | show running-config | section username | users | show configuration system login | match user |
| kto jest zalogowany | show users | show users | who | show system users |
Linki do dokumentacji
Arista
Cisco
Cumulus
Juniper
Konfiguracja
Hostname
W tym miejscu pokaże jak zmienić hostname na poszczególnym urządzeniu.
Arista
Arista#configure Arista(config)#hostname Arista01 Arista01(config)#
Cisco
Cisco#conf Cisco#configure t Enter configuration commands, one per line. End with CNTL/Z. Cisco(config)#hostname Cisco01 Cisco01(config)#
Juniper
root@vMX02% cli root@vMX> configure Entering configuration mode [edit] root@vMX# set system host-name vMX01 [edit] root@vMX# commit commit complete [edit] root@vMX01#
Cumulus
cumulus@cumulus:~$ net add hostname Cumulus01 cumulus@cumulus:~$ comm comm command cumulus@cumulus:~$ net commit --- /etc/hosts 2017-06-21 03:30:04.415697558 +0000 +++ /var/run/nclu/netmisc/etc_hosts 2017-08-01 09:43:25.572201909 +0000 @@ -1,6 +1,6 @@ 127.0.0.1 localhost ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters -127.0.1.1 cumulus +127.0.1.1 Cumulus01 --- /etc/hostname 2017-06-21 03:30:04.415697558 +0000 +++ /var/run/nclu/netmisc/etc_hostname 2017-08-01 09:43:25.565201562 +0000 @@ -1 +1 @@ -cumulus +Cumulus01 net add/del commands since the last 'net commit' ================================================ User Timestamp Command ------- -------------------------- -------------------------- cumulus 2017-08-01 09:43:25.573340 net add hostname Cumulus01 cumulus 2017-08-01 09:43:32.108477 net commit cumulus@cumulus:~$
zmianę hostname zobaczymy po przelogowaniu.
Dodanie użytkownika
W tym miejscu pokażę jak dodać użytkownika z uprawnieniami administracyjnymi
Arista
Arista#configure Arista01(config)#username test privilege 15 secret 0 Qwert6 Arista01(config)#end
Cisco
Cisco#conf Cisco#configure t Enter configuration commands, one per line. End with CNTL/Z. Cisco(config)#username test privilege 15 password 0 Qwert6 Cisco01(config)#
Juniper
root@vMX02% cli root@vMX> configure Entering configuration mode [edit] root@vMX01# set system login user test class super-user authentication plain-text-password New password: Retype new password: [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Cumulus
Jeszcze nie rozgryzłem 🙂
Interfejsy
Konfigurujemy interfejsy zgodnie z rysunkiem dla połączeń L3
Arista
Arista01(config)#interface Ethernet1 Arista01(config-if-Et1)#description "DO-->vMX ge-0/0/3" Arista01(config-if-Et1)#no switchport Arista01(config-if-Et1)#ip address 10.10.40.2/30 Arista01(config-if-Et1)# Arista01(config-if-Et1)# Arista01(config-if-Et1)#interface Ethernet2 Arista01(config-if-Et2)#description "DO-->Cumulus swp3" Arista01(config-if-Et2)#no switchport Arista01(config-if-Et2)#ip address 10.10.50.2/30 Arista01(config-if-Et2)#interface Ethernet3 Arista01(config-if-Et3)#description DO-->Cisco Gi 4" Arista01(config-if-Et3)#no switchport Arista01(config-if-Et3)#ip address 10.10.60.2/30 Arista01(config-if-Et3)# Arista01(config-if-Et3)#end
Cisco
Cisco01(config)#interface GigabitEthernet1 Cisco01(config-if)#desc Cisco01(config-if)#description "Do-->Cumulus swp2" Cisco01(config-if)#no sh Cisco01(config-if)#ip address 10.10.20.2 255.255.255.252 Cisco01(config-if)# Cisco01(config-if)#interface GigabitEthernet2 Cisco01(config-if)#desc Cisco01(config-if)#description "DO-->vMX ge-0/0/2" Cisco01(config-if)# Cisco01(config-if)#ip address 10.10.30.2 255.255.255.252 Cisco01(config-if)# Cisco01(config-if)#interface GigabitEthernet4 Cisco01(config-if)#desc Cisco01(config-if)#description "DO-->Arista eth3" Cisco01(config-if)#no sh Cisco01(config-if)#ip address 10.10.60.1 255.255.255.252 Cisco01(config-if)#end Cisco01#
Juniper
root@vMX01# set interfaces ge-0/0/0.0 description "DO-->Cumulus swp1" root@vMX01# set interfaces ge-0/0/0 unit 0 family inet address 10.10.10.2/30 root@vMX01# set interfaces ge-0/0/2.0 description "DO-->Cisco gi 2" root@vMX01# set interfaces ge-0/0/2 unit 0 family inet address 10.10.30.1/30 root@vMX01# set interfaces ge-0/0/3.0 description "DO-->Arista eth1" [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Cumulus
cumulus@cumulus01:~$
cumulus@cumulus01:~$ net add interface swp1 ip address 10.10.10.1/30
cumulus@cumulus01:~$ net add interface swp1 alias "Do-->vMX ge-0/0/0"
cumulus@cumulus01:~$ net add interface swp2 ip address 10.10.20.1/30
cumulus@cumulus01:~$ net add interface swp2 alias "Do-->Cisco gi 1"
cumulus@cumulus01:~$ net add interface swp3 ip address 10.10.50.1/30
cumulus@cumulus01:~$ net add interface swp2 alias "Do-->Arista eth 2"
cumulus@cumulus01:~$ net commit
--- /etc/network/interfaces 2017-08-01 10:23:19.579855479 +0000
+++ /var/run/nclu/iface/interfaces.tmp 2017-08-01 10:25:33.973421975 +0000
@@ -4,20 +4,34 @@
source /etc/network/interfaces.d/*.intf
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
+auto swp1
+iface swp1
+ address 10.10.10.1/30
+ alias Do-->vMX ge-0/0/0
+
+auto swp2
+iface swp2
+ address 10.10.20.1/30
+ alias Do-->Arista eth 2
+
+auto swp3
+iface swp3
+ address 10.10.50.1/30
+
auto Test
iface Test
vrf-table auto
auto bridge
iface bridge
bridge-pvid 100
bridge-vids 100-102
bridge-vlan-aware yes
net add/del commands since the last 'net commit'
================================================
User Timestamp Command
------- -------------------------- -----------------------------------------------
cumulus 2017-08-01 10:23:48.092759 net add interface swp1 ip address 10.10.10.1/30
cumulus 2017-08-01 10:24:09.979614 net add interface swp1 alias Do-->vMX ge-0/0/0
cumulus 2017-08-01 10:24:25.156209 net add interface swp2 ip address 10.10.20.1/30
cumulus 2017-08-01 10:24:46.110179 net add interface swp2 alias Do-->Cisco gi 1
cumulus 2017-08-01 10:25:09.087218 net add interface swp3 ip address 10.10.50.1/30
cumulus 2017-08-01 10:25:31.064293 net add interface swp2 alias Do-->Arista eth 2
cumulus 2017-08-01 10:25:33.973234 net commit
cumulus@cumulus01:~$
Interfejs Loopback
Skonfigurujemy interfejs loopback na każdym z urządzeniu później posłuży nam do router id przy OSPF’ie oraz
Arista
Arista01#configure Arista01(config)#interface loopback 0 Arista01(config-if-Lo0)#ip address 3.3.3.3/32 Arista01(config-if-Lo0)#description Loopback0 Arista01(config-if-Lo0)#end Arista01#
Cisco
Cisco01#configure t Enter configuration commands, one per line. End with CNTL/Z. Cisco01(config)#interface loopback 0 Cisco01(config-if)#ip address 4.4.4.4 255.255.255.255 Cisco01(config-if)#description Loopback0 Cisco01(config-if)#end Cisco01#
Juniper
root@vMX01> configure Entering configuration mode [edit] root@vMX01# set interfaces lo0.0 family inet address 2.2.2.2/32 [edit] root@vMX01# set interfaces lo0.0 description "Loopback0" [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Cumulus
cumulus@cumulus01:~$
cumulus@cumulus01:~$ net add loopback lo ip address 1.1.1.1/32
cumulus@cumulus01:~$ net commit
--- /etc/network/interfaces 2017-08-01 10:25:34.564450853 +0000
+++ /var/run/nclu/iface/interfaces.tmp 2017-08-01 12:33:17.636468688 +0000
@@ -1,18 +1,19 @@
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*.intf
# The loopback network interface
auto lo
iface lo inet loopback
+ address 1.1.1.1/32
# The primary network interface
auto eth0
iface eth0 inet dhcp
auto swp1
iface swp1
address 10.10.10.1/30
alias Do-->vMX ge-0/0/0
net add/del commands since the last 'net commit'
================================================
User Timestamp Command
------- -------------------------- -----------------------------------------
cumulus 2017-08-01 12:33:09.177219 net add loopback lo ip address 1.1.1.1/32
cumulus 2017-08-01 12:33:17.635660 net commit
cumulus@cumulus01:~$
Routing Statyczny
Skonfigurujemy routing statyczny tak aby urządzenia mogły osiągnąć wszystkie adresy loopabck sąsiada
Arista
Arista#configure Arista01(config)#ip route 2.2.2.2/32 10.10.40.1 Arista01(config)#ip route 1.1.1.1/32 10.10.50.1 Arista01(config)#ip route 4.4.4.4/32 10.10.60.1 Arista01(config)#end Arista01#
Cisco
Cisco01#conf t Enter configuration commands, one per line. End with CNTL/Z. Cisco01(config)#ip route 1.1.1.1 255.255.255.255 10.10.20.1 Cisco01(config)#ip route 2.2.2.2 255.255.255.255 10.10.30.1 Cisco01(config)#ip route 3.3.3.3 255.255.255.255 10.10.60.2 Cisco01(config)#end Cisco01#
Juniper
[edit] root@vMX01# [edit] root@vMX01# set routing-options static route 1.1.1.1/32 next-hop 10.10.10.1 [edit] root@vMX01# set routing-options static route 3.3.3.3/32 next-hop 10.10.40.2 [edit] root@vMX01# set routing-options static route 4.4.4.4/32 next-hop 10.10.30.2 [edit] root@vMX01# [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Cumulus
cumulus@cumulus01:~$ cumulus@cumulus01:~$ net add routing route 2.2.2.2/32 10.10.10.2 cumulus@cumulus01:~$ net add routing route 4.4.4.4/32 10.10.20.2 cumulus@cumulus01:~$ net add routing route 3.3.3.3/32 10.10.50.2 cumulus@cumulus01:~$ net commit --- /var/run/nclu/quagga/pending_baseline.conf 2017-08-01 12:41:24.704218920 +0000 +++ /var/run/nclu/quagga/pending.conf 2017-08-01 12:41:38.562671304 +0000 @@ -5,10 +5,14 @@ router bgp 65001 neighbor 10.10.10.2 remote-as 65000 ! address-family ipv4 unicast network 10.100.10.0/24 exit-address-family end line vty end +ip route 2.2.2.2/32 10.10.10.2 +end +ip route 4.4.4.4/32 10.10.20.2 +end +ip route 3.3.3.3/32 10.10.50.2 +end net add/del commands since the last 'net commit' ================================================ User Timestamp Command ------- -------------------------- ------------------------------------------- cumulus 2017-08-01 12:41:24.707180 net add routing route 2.2.2.2/32 10.10.10.2 cumulus 2017-08-01 12:41:38.563843 net add routing route 4.4.4.4/32 10.10.20.2 cumulus 2017-08-01 12:41:38.593443 net add routing route 3.3.3.3/32 10.10.50.2 cumulus 2017-08-01 12:41:42.625126 net commit cumulus@cumulus01:~$
weryfikacja
wyświetlenie tablicy routingu
Arista
Arista01#show ip route
VRF name: default
Codes: C - connected, S - static, K - kernel,
O - OSPF, IA - OSPF inter area, E1 - OSPF external type 1,
E2 - OSPF external type 2, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type2, B I - iBGP, B E - eBGP,
R - RIP, I L1 - ISIS level 1, I L2 - ISIS level 2,
A B - BGP Aggregate, A O - OSPF Summary,
NG - Nexthop Group Static Route, V - VXLAN Control Service
Gateway of last resort is not set
S 1.1.1.1/32 [1/0] via 10.10.50.1, Ethernet2
S 2.2.2.2/32 [1/0] via 10.10.40.1, Ethernet1
C 3.3.3.3/32 is directly connected, Loopback0
S 4.4.4.4/32 [1/0] via 10.10.60.1, Ethernet3
C 10.10.40.0/30 is directly connected, Ethernet1
C 10.10.50.0/30 is directly connected, Ethernet2
C 10.10.60.0/30 is directly connected, Ethernet3
C 192.168.220.0/24 is directly connected, Management1
! IP routing not enabled
Cisco
Cisco01#show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
S 1.1.1.1 [1/0] via 10.10.20.1
2.0.0.0/32 is subnetted, 1 subnets
S 2.2.2.2 [1/0] via 10.10.30.1
3.0.0.0/32 is subnetted, 1 subnets
S 3.3.3.3 [1/0] via 10.10.60.2
4.0.0.0/32 is subnetted, 1 subnets
C 4.4.4.4 is directly connected, Loopback0
10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
C 10.10.20.0/30 is directly connected, GigabitEthernet1
L 10.10.20.2/32 is directly connected, GigabitEthernet1
C 10.10.30.0/30 is directly connected, GigabitEthernet2
L 10.10.30.2/32 is directly connected, GigabitEthernet2
C 10.10.60.0/30 is directly connected, GigabitEthernet4
L 10.10.60.1/32 is directly connected, GigabitEthernet4
Juniper
root@vMX01> show route
inet.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.1/32 *[Static/5] 00:00:26
> to 10.10.10.1 via ge-0/0/0.0
2.2.2.2/32 *[Direct/0] 05:24:47
> via lo0.0
3.3.3.3/32 *[Static/5] 00:00:26
> to 10.10.40.2 via ge-0/0/3.0
4.4.4.4/32 *[Static/5] 00:00:26
> to 10.10.30.2 via ge-0/0/2.0
10.10.10.0/30 *[Direct/0] 00:28:13
> via ge-0/0/0.0
10.10.10.2/32 *[Local/0] 00:28:14
Local via ge-0/0/0.0
10.10.30.0/30 *[Direct/0] 00:28:13
> via ge-0/0/2.0
10.10.30.1/32 *[Local/0] 00:28:14
Local via ge-0/0/2.0
10.10.40.0/30 *[Direct/0] 00:28:13
> via ge-0/0/3.0
10.10.40.1/32 *[Local/0] 00:28:14
Local via ge-0/0/3.0
192.168.220.0/24 *[Direct/0] 00:28:13
> via ge-0/0/5.0
192.168.220.138/32 *[Local/0] 00:28:14
Local via ge-0/0/5.0
Cumulus
cumulus@cumulus01:~$ net show route
show ip route
=============
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, P - PIM, T - Table, v - VNC,
V - VPN,
> - selected route, * - FIB route
K>* 0.0.0.0/0 via 192.168.220.2, eth0
C>* 1.1.1.1/32 is directly connected, lo
S>* 2.2.2.2/32 [1/0] via 10.10.10.2, swp1
S>* 3.3.3.3/32 [1/0] via 10.10.50.2, swp3
S>* 4.4.4.4/32 [1/0] via 10.10.20.2, swp2
C>* 10.10.10.0/30 is directly connected, swp1
C>* 10.10.20.0/30 is directly connected, swp2
C>* 10.10.50.0/30 is directly connected, swp3
C>* 10.100.10.0/24 is directly connected, vlan100
C>* 192.168.220.0/24 is directly connected, eth0
show ipv6 route
===============
Codes: K - kernel route, C - connected, S - static, R - RIPng,
O - OSPFv6, I - IS-IS, B - BGP, T - Table, v - VNC,
V - VPN,
> - selected route, * - FIB route
C * fe80::/64 is directly connected, swp1
C * fe80::/64 is directly connected, swp2
C * fe80::/64 is directly connected, swp3
C * fe80::/64 is directly connected, eth0
C * fe80::/64 is directly connected, bridge
C>* fe80::/64 is directly connected, vlan100
Ping
Arista
Arista01#ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 72(100) bytes of data. 80 bytes from 1.1.1.1: icmp_req=1 ttl=64 time=1029 ms 80 bytes from 1.1.1.1: icmp_req=2 ttl=64 time=36.3 ms 80 bytes from 1.1.1.1: icmp_req=3 ttl=64 time=8.09 ms 80 bytes from 1.1.1.1: icmp_req=4 ttl=64 time=10.4 ms 80 bytes from 1.1.1.1: icmp_req=5 ttl=64 time=20.4 ms --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3398ms rtt min/avg/max/mdev = 8.091/220.944/1029.442/404.371 ms, pipe 2, ipg/ewma 849.635/610.949 ms Arista01#ping 2.2.2.2 PING 2.2.2.2 (2.2.2.2) 72(100) bytes of data. 80 bytes from 2.2.2.2: icmp_req=1 ttl=64 time=1387 ms 80 bytes from 2.2.2.2: icmp_req=2 ttl=64 time=409 ms 80 bytes from 2.2.2.2: icmp_req=3 ttl=64 time=10.4 ms 80 bytes from 2.2.2.2: icmp_req=4 ttl=64 time=8.07 ms 80 bytes from 2.2.2.2: icmp_req=5 ttl=64 time=11.2 ms --- 2.2.2.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4349ms rtt min/avg/max/mdev = 8.072/365.364/1387.808/534.102 ms, pipe 2, ipg/ewma 1087.271/851.068 ms Arista01#ping 3.3.3.3 PING 3.3.3.3 (3.3.3.3) 72(100) bytes of data. 80 bytes from 3.3.3.3: icmp_req=1 ttl=64 time=0.059 ms 80 bytes from 3.3.3.3: icmp_req=2 ttl=64 time=0.032 ms 80 bytes from 3.3.3.3: icmp_req=3 ttl=64 time=0.055 ms 80 bytes from 3.3.3.3: icmp_req=4 ttl=64 time=0.050 ms 80 bytes from 3.3.3.3: icmp_req=5 ttl=64 time=0.036 ms --- 3.3.3.3 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 2ms rtt min/avg/max/mdev = 0.032/0.046/0.059/0.012 ms, ipg/ewma 0.567/0.052 ms Arista01#ping 4.4.4.4 PING 4.4.4.4 (4.4.4.4) 72(100) bytes of data. 80 bytes from 4.4.4.4: icmp_req=1 ttl=255 time=1113 ms 80 bytes from 4.4.4.4: icmp_req=2 ttl=255 time=122 ms 80 bytes from 4.4.4.4: icmp_req=3 ttl=255 time=29.9 ms 80 bytes from 4.4.4.4: icmp_req=4 ttl=255 time=7.28 ms 80 bytes from 4.4.4.4: icmp_req=5 ttl=255 time=10.5 ms --- 4.4.4.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3628ms rtt min/avg/max/mdev = 7.286/256.815/1113.714/430.504 ms, pipe 2, ipg/ewma 907.011/668.087 ms Arista01#
Cisco
Cisco01#ping 1.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 12/20/39 ms Cisco01#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 16/28/65 ms Cisco01#ping 3.3.3.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 43/388/1497 ms Cisco01#ping 4.4.4.4 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/3 ms Cisco01#
Juniper
root@vMX01> ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=64 time=48.283 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=5.032 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=6.277 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=2.355 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=64 time=4.177 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=64 time=1.688 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=64 time=3.172 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=64 time=5.061 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=64 time=2.275 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=64 time=2.552 ms 64 bytes from 1.1.1.1: icmp_seq=10 ttl=64 time=2.511 ms ^C --- 1.1.1.1 ping statistics --- 11 packets transmitted, 11 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.688/7.580/48.283/12.945 ms root@vMX01> ping 2.2.2.2 PING 2.2.2.2 (2.2.2.2): 56 data bytes 64 bytes from 2.2.2.2: icmp_seq=0 ttl=64 time=0.339 ms 64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=0.073 ms 64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=0.148 ms 64 bytes from 2.2.2.2: icmp_seq=3 ttl=64 time=0.146 ms 64 bytes from 2.2.2.2: icmp_seq=4 ttl=64 time=0.336 ms 64 bytes from 2.2.2.2: icmp_seq=5 ttl=64 time=0.066 ms 64 bytes from 2.2.2.2: icmp_seq=6 ttl=64 time=0.067 ms ^C --- 2.2.2.2 ping statistics --- 7 packets transmitted, 7 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.066/0.168/0.339/0.112 ms root@vMX01> ping 3.3.3.3 PING 3.3.3.3 (3.3.3.3): 56 data bytes 64 bytes from 3.3.3.3: icmp_seq=0 ttl=64 time=1515.648 ms 64 bytes from 3.3.3.3: icmp_seq=1 ttl=64 time=512.710 ms 64 bytes from 3.3.3.3: icmp_seq=2 ttl=64 time=42.362 ms 64 bytes from 3.3.3.3: icmp_seq=3 ttl=64 time=14.515 ms 64 bytes from 3.3.3.3: icmp_seq=4 ttl=64 time=9.158 ms ^C --- 3.3.3.3 ping statistics --- 6 packets transmitted, 5 packets received, 16% packet loss round-trip min/avg/max/stddev = 9.158/418.879/1515.648/580.492 ms root@vMX01> ping 4.4.4.4 PING 4.4.4.4 (4.4.4.4): 56 data bytes 64 bytes from 4.4.4.4: icmp_seq=0 ttl=255 time=11.342 ms 64 bytes from 4.4.4.4: icmp_seq=1 ttl=255 time=50.529 ms 64 bytes from 4.4.4.4: icmp_seq=2 ttl=255 time=26.060 ms 64 bytes from 4.4.4.4: icmp_seq=3 ttl=255 time=13.135 ms 64 bytes from 4.4.4.4: icmp_seq=4 ttl=255 time=5.393 ms ^C --- 4.4.4.4 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 5.393/21.292/50.529/16.099 ms root@vMX01>
Cumulus
cumulus@cumulus01:~$ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.142 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=0.101 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.051 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=64 time=0.060 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=64 time=0.053 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=64 time=0.059 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=64 time=0.061 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=64 time=0.060 ms --- 1.1.1.1 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7022ms rtt min/avg/max/mdev = 0.051/0.073/0.142/0.030 ms cumulus@cumulus01:~$ ping 2.2.2.2 PING 2.2.2.2 (2.2.2.2) 56(84) bytes of data. 64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=2.89 ms 64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=5.97 ms 64 bytes from 2.2.2.2: icmp_seq=3 ttl=64 time=3.26 ms 64 bytes from 2.2.2.2: icmp_seq=4 ttl=64 time=0.626 ms 64 bytes from 2.2.2.2: icmp_seq=5 ttl=64 time=1.07 ms 64 bytes from 2.2.2.2: icmp_seq=6 ttl=64 time=1.04 ms 64 bytes from 2.2.2.2: icmp_seq=7 ttl=64 time=0.944 ms 64 bytes from 2.2.2.2: icmp_seq=8 ttl=64 time=0.570 ms ^C --- 2.2.2.2 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7022ms rtt min/avg/max/mdev = 0.570/2.049/5.977/1.768 ms cumulus@cumulus01:~$ ping 3.3.3.3 PING 3.3.3.3 (3.3.3.3) 56(84) bytes of data. 64 bytes from 3.3.3.3: icmp_seq=1 ttl=64 time=1535 ms 64 bytes from 3.3.3.3: icmp_seq=2 ttl=64 time=509 ms 64 bytes from 3.3.3.3: icmp_seq=3 ttl=64 time=31.1 ms 64 bytes from 3.3.3.3: icmp_seq=4 ttl=64 time=44.6 ms ^C --- 3.3.3.3 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3042ms rtt min/avg/max/mdev = 31.184/530.307/1535.975/611.722 ms, pipe 2 cumulus@cumulus01:~$ ping 4.4.4.4 PING 4.4.4.4 (4.4.4.4) 56(84) bytes of data. 64 bytes from 4.4.4.4: icmp_seq=1 ttl=255 time=5.77 ms 64 bytes from 4.4.4.4: icmp_seq=2 ttl=255 time=0.320 ms 64 bytes from 4.4.4.4: icmp_seq=3 ttl=255 time=0.504 ms 64 bytes from 4.4.4.4: icmp_seq=4 ttl=255 time=0.406 ms 64 bytes from 4.4.4.4: icmp_seq=5 ttl=255 time=0.444 ms 64 bytes from 4.4.4.4: icmp_seq=6 ttl=255 time=0.559 ms 64 bytes from 4.4.4.4: icmp_seq=7 ttl=255 time=0.589 ms --- 4.4.4.4 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6003ms rtt min/avg/max/mdev = 0.320/1.228/5.774/1.857 ms
Kasowanie routingu statycznego
aby przygotować się do następnego etapu musimy skasować, co przygotowaliśmy krok wcześnij – cóż takie życie czasem trzeba coś zniszczyć
Arista
Arista#configure Arista01(config)#no ip route 1.1.1.1/32 10.10.50.1 Arista01(config)#no ip route 2.2.2.2/32 10.10.40.1 Arista01(config)#no ip route 4.4.4.4/32 10.10.60.1
Cisco
Cisco#conf Cisco#configure t Enter configuration commands, one per line. End with CNTL/Z. Cisco01(config)#no ip route 1.1.1.1 255.255.255.255 10.10.20.1 Cisco01(config)#no ip route 2.2.2.2 255.255.255.255 10.10.30.1 Cisco01(config)#no ip route 3.3.3.3 255.255.255.255 10.10.60.2 Cisco01(config)#end Cisco01#
Cumulus
kasowanie możemy zrobić na dwa sposoby, jedno z 2 urządzeń które tutaj używamy to potrafi.
Sposób pierwszy
Ręczne kasowanie wpisów.
cumulus@cumulus01:~$ cumulus@cumulus01:~$ net del routing route 2.2.2.2/32 10.10.10.2 cumulus@cumulus01:~$ net del routing route 4.4.4.4/32 10.10.20.2 cumulus@cumulus01:~$ net del routing route 3.3.3.3/32 10.10.50.2 cumulus@cumulus01:~$ net commit --- /var/run/nclu/quagga/pending_baseline.conf 2017-08-01 13:11:40.196432408 +0000 +++ /var/run/nclu/quagga/pending.conf 2017-08-01 13:12:47.705599560 +0000 @@ -2,16 +2,13 @@ service integrated-vtysh-config log file /var/log/quagga/quagga.log log timestamp precision 6 router bgp 65001 neighbor 10.10.10.2 remote-as 65000 ! address-family ipv4 unicast network 10.100.10.0/24 exit-address-family end -ip route 2.2.2.2/32 10.10.10.2 -ip route 3.3.3.3/32 10.10.50.2 -ip route 4.4.4.4/32 10.10.20.2 line vty end net add/del commands since the last 'net commit' ================================================ User Timestamp Command ------- -------------------------- ------------------------------------------- cumulus 2017-08-01 13:11:40.199532 net del routing route 2.2.2.2/32 10.10.10.2 cumulus 2017-08-01 13:12:09.260785 net del routing route 4.4.4.4/32 10.10.20.2 cumulus 2017-08-01 13:12:39.788223 net del routing route 3.3.3.3/32 10.10.60.2 cumulus 2017-08-01 13:12:47.706729 net del routing route 3.3.3.3/32 10.10.50.2 cumulus 2017-08-01 13:12:51.819782 net commit
Sposób drugi
Sposób szybszy – cofnięcie się do konfiguracji która była wcześniej.
szukamy konfiguracji z prze wprowadzenie zmian z routingiem statycznym
cumulus@cumulus01:~$ net show rollback 40 --- /etc/quagga/Quagga.conf 2017-08-01 13:16:04.382906506 +0000 +++ /.snapshots/40/snapshot/etc/quagga/Quagga.conf 2017-08-01 12:41:24.674213609 +0000 @@ -13,9 +13,5 @@ network 10.100.10.0/24 exit-address-family ! -ip route 2.2.2.2/32 10.10.10.2 -ip route 3.3.3.3/32 10.10.50.2 -ip route 4.4.4.4/32 10.10.20.2 -! line vty !
cofamy się do tego momentu w którym nie było dodanych wpisów statycznych.
cumulus@cumulus01:~$ net rollback
<number> : Any integer
description : Description
last : the most recent 'net commit' snapshot
cumulus@cumulus01:~$ net rollback 40
cumulus@cumulus01:~$ net commit
net add/del commands since the last 'net commit'
================================================
User Timestamp Command
------- -------------------------- ----------
cumulus 2017-08-01 13:21:31.687385 net commit
commit ignored...there were no pending changes
cumulus@cumulus01:~$ dis
discover discover-config discover-modprobe discover-pkginstall disown
cumulus@cumulus01:~$ net show ro
rollback : revert to a previous configuration state
route : Static routes
route-map : Route-map
Juniper
Drugie urządzenie które potrafi jak Cumulus cofać się do konfiguracji.
Sposób Pierwszy
Kasowanie ręczne
[edit] root@vMX01# [edit] root@vMX01# del routing-options static route 1.1.1.1/32 next-hop 10.10.10.1 [edit] root@vMX01# del routing-options static route 3.3.3.3/32 next-hop 10.10.40.2 [edit] root@vMX01# del routing-options static route 4.4.4.4/32 next-hop 10.10.30.2 [edit] root@vMX01# [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Sposób drugi
Wyszukujemy konfigurację przed dodaniem routingu statycznego
root@vMX02% cli
root@vMX> configure
Entering configuration mode
root@vMX01# show | compare rollback 1
[edit routing-options]
+ static {
+ route 1.1.1.1/32 next-hop 10.10.10.1;
+ route 3.3.3.3/32 next-hop 10.10.40.2;
+ route 4.4.4.4/32 next-hop 10.10.30.2;
+ }
[edit]
root@vMX01#
Cofamy się do tego punktu
[edit] root@vMX01# rollback 1 load complete [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Tym sposobem mamy przygotowaną infrastrukturę do następnego zadania.
Routing dynamiczny OSPF
przyszedł czas na konfigurację routingu dynamicznego w postaci OSPF’a będziemy rozgłaszać sieci które są w trybie direct.
Arista
Arista01#configure Arista01(config)#ip routing Arista01(config)#router ospf 1 Arista01(config-router-ospf)#router-id 3.3.3.3 Arista01(config-router-ospf)#redistribute connected Arista01(config-router-ospf)#network 3.3.3.3/32 area 0 Arista01(config-router-ospf)#network 10.10.40.0/30 area 0 Arista01(config-router-ospf)#network 10.10.50.0/30 area 0 Arista01(config-router-ospf)#network 10.10.60.0/30 area 0 Arista01(config-router-ospf)#
Cisco
Cisco01#configure t Enter configuration commands, one per line. End with CNTL/Z. Cisco01(config)#router ospf 1 Cisco01(config-router)#network 4.4.4.4 0.0.0.0 area 0 Cisco01(config-router)#network 10.10.20.0 0.0.0.3 area 0 Cisco01(config-router)#network 10.10.20.0 0.0.0.3 area 0 Cisco01(config-router)#network 10.10.30.0 0.0.0.3 area 0 Cisco01(config-router)#network 10.10.60.0 0.0.0.3 area 0 Cisco01(config-router)#redistribute connected
Juniper
Definiujemy politykę która będzie eksportować do OSPF sieci direct
root@vMX01# set policy-options policy-statement export_to_ospf_direct term direct from protocol direct [edit] root@vMX01# set policy-options policy-statement export_to_ospf_direct term direct then accept [edit] root@vMX01#
konfigurujemy ospf
root@vMX01# set routing-options router-id 2.2.2.2 [edit] root@vMX01# [edit] root@vMX01# set protocols ospf area 0 interface ge-0/0/0 [edit] root@vMX01# set protocols ospf area 0 interface ge-0/0/2 [edit] root@vMX01# set protocols ospf area 0 interface ge-0/0/3 [edit] root@vMX01# set protocols ospf area 0 interface lo0.0 [edit] root@vMX01# set protocols ospf export export_to_ospf_direct [edit] root@vMX01# commit commit complete [edit] root@vMX01#
Cumulus
cumulus@cumulus01:~$ net add ospf router-id 1.1.1.1 cumulus@cumulus01:~$ net add ospf network 1.1.1.1/32 area 0 cumulus@cumulus01:~$ net add ospf network 10.10.10.0/30 area 0 cumulus@cumulus01:~$ net add ospf network 10.10.50.0/30 area 0 cumulus@cumulus01:~$ net add ospf network 10.10.20.0/30 area 0 cumulus@cumulus01:~$ net add ospf redistribute connected cumulus@cumulus01:~$ net commit --- /var/run/nclu/quagga/baseline.daemons 2017-08-01 15:43:24.213859311 +0000 +++ /var/run/nclu/quagga/pending.daemons 2017-08-01 15:43:24.306863930 +0000 @@ -1,9 +1,9 @@ zebra=yes bgpd=yes -ospfd=no +ospfd=yes ospf6d=no ripd=no ripngd=no isisd=no pimd=no ldpd=no ******************************************************************** ******************************************************************** NOTE: 'net commit' will run 'systemctl restart quagga' to apply the change to /etc/quagga/daemons ******************************************************************** ******************************************************************** --- /var/run/nclu/quagga/pending_baseline.conf 2017-08-01 15:43:24.304863831 +0000 +++ /var/run/nclu/quagga/pending.conf 2017-08-01 15:44:35.426404421 +0000 @@ -5,10 +5,18 @@ router bgp 65001 neighbor 10.10.10.2 remote-as 65000 ! address-family ipv4 unicast network 10.100.10.0/24 exit-address-family end line vty end +router ospf + network 1.1.1.1/32 area 0 + network 10.10.10.0/30 area 0 + network 10.10.50.0/30 area 0 + network 10.10.20.0/30 area 0 + redistribute connected + ospf router-id 1.1.1.1 +end net add/del commands since the last 'net commit' ================================================ User Timestamp Command ------- -------------------------- ----------------------------------------- cumulus 2017-08-01 15:43:24.308605 net add ospf network 1.1.1.1/32 area 0 cumulus 2017-08-01 15:43:47.167303 net add ospf network 10.10.10.0/30 area 0 cumulus 2017-08-01 15:43:56.003703 net add ospf network 10.10.50.0/30 area 0 cumulus 2017-08-01 15:44:05.464953 net add ospf network 10.10.20.0/30 area 0 cumulus 2017-08-01 15:44:18.065819 net add ospf redistribute connected cumulus 2017-08-01 15:44:35.427114 net add ospf router-id 1.1.1.1 cumulus 2017-08-01 15:45:45.712212 net commit
Weryfikacja
tablica routingu
Arista
Arista01#show ip route ospf
VRF name: default
Codes: C - connected, S - static, K - kernel,
O - OSPF, IA - OSPF inter area, E1 - OSPF external type 1,
E2 - OSPF external type 2, N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type2, B I - iBGP, B E - eBGP,
R - RIP, I L1 - ISIS level 1, I L2 - ISIS level 2,
A B - BGP Aggregate, A O - OSPF Summary,
NG - Nexthop Group Static Route, V - VXLAN Control Service
O 1.1.1.1/32 [110/10] via 10.10.50.1, Ethernet2
O 2.2.2.2/32 [110/10] via 10.10.40.1, Ethernet1
O 4.4.4.4/32 [110/11] via 10.10.60.1, Ethernet3
O 10.10.10.0/30 [110/11] via 10.10.40.1, Ethernet1
O 10.10.20.0/30 [110/11] via 10.10.60.1, Ethernet3
O 10.10.30.0/30 [110/11] via 10.10.40.1, Ethernet1
via 10.10.60.1, Ethernet3
Arista01#
Cisco
Cisco01#show ip route ospf
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
Gateway of last resort is not set
1.0.0.0/32 is subnetted, 1 subnets
O 1.1.1.1 [110/1] via 10.10.20.1, 00:51:57, GigabitEthernet1
2.0.0.0/32 is subnetted, 1 subnets
O 2.2.2.2 [110/1] via 10.10.30.1, 01:02:02, GigabitEthernet2
3.0.0.0/32 is subnetted, 1 subnets
O 3.3.3.3 [110/11] via 10.10.60.2, 01:09:44, GigabitEthernet4
10.0.0.0/8 is variably subnetted, 10 subnets, 3 masks
O 10.10.10.0/30 [110/2] via 10.10.30.1, 01:02:02, GigabitEthernet2
O 10.10.40.0/30 [110/2] via 10.10.30.1, 01:02:02, GigabitEthernet2
O 10.10.50.0/30 [110/11] via 10.10.60.2, 01:09:44, GigabitEthernet4
[110/11] via 10.10.20.1, 00:51:47, GigabitEthernet1
Juniper
root@vMX01> show route protocol ospf
inet.0: 18 destinations, 19 routes (18 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.1/32 *[OSPF/10] 00:52:54, metric 1
> to 10.10.10.1 via ge-0/0/0.0
3.3.3.3/32 *[OSPF/10] 01:03:00, metric 11
> to 10.10.40.2 via ge-0/0/3.0
4.4.4.4/32 *[OSPF/10] 01:03:00, metric 2
> to 10.10.30.2 via ge-0/0/2.0
10.10.20.0/30 *[OSPF/10] 01:03:00, metric 2
> to 10.10.30.2 via ge-0/0/2.0
10.10.50.0/30 *[OSPF/10] 00:52:54, metric 11
> to 10.10.40.2 via ge-0/0/3.0
to 10.10.10.1 via ge-0/0/0.0
10.10.60.0/30 *[OSPF/10] 01:03:00, metric 2
> to 10.10.30.2 via ge-0/0/2.0
Cumulus
cumulus@cumulus01:~$ net show route ospf
RIB entry for ospf
==================
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, P - PIM, T - Table, v - VNC,
V - VPN,
> - selected route, * - FIB route
O 1.1.1.1/32 [110/0] is directly connected, lo, 00:54:00
O>* 2.2.2.2/32 [110/10] via 10.10.10.2, swp1, 00:53:55
O>* 3.3.3.3/32 [110/20] via 10.10.50.2, swp3, 00:53:51
O>* 4.4.4.4/32 [110/11] via 10.10.20.2, swp2, 00:53:55
O 10.10.10.0/30 [110/10] is directly connected, swp1, 00:54:00
O 10.10.20.0/30 [110/10] is directly connected, swp2, 00:54:00
O>* 10.10.30.0/30 [110/11] via 10.10.10.2, swp1, 00:53:55
* via 10.10.20.2, swp2, 00:53:55
O>* 10.10.40.0/30 [110/11] via 10.10.10.2, swp1, 00:53:55
O 10.10.50.0/30 [110/10] is directly connected, swp3, 00:53:51
O>* 10.10.60.0/30 [110/11] via 10.10.20.2, swp2, 00:53:55
sąsiedztwo ospf
Arista
Arista01#show ip ospf neighbor Neighbor ID VRF Pri State Dead Time Address Interface 2.2.2.2 default 128 FULL/BDR 00:00:31 10.10.40.1 Ethernet1 1.1.1.1 default 1 FULL/BDR 00:00:31 10.10.50.1 Ethernet2 4.4.4.4 default 1 FULL/DR 00:00:35 10.10.60.1 Ethernet3
Cisco
Cisco01#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 3.3.3.3 1 FULL/BDR 00:00:30 10.10.60.2 GigabitEthernet4 2.2.2.2 128 FULL/BDR 00:00:38 10.10.30.1 GigabitEthernet2 1.1.1.1 1 FULL/BDR 00:00:32 10.10.20.1 GigabitEthernet1
Juniper
root@vMX01> show ospf neighbor Address Interface State ID Pri Dead 10.10.10.1 ge-0/0/0.0 Full 1.1.1.1 1 34 10.10.30.2 ge-0/0/2.0 Full 4.4.4.4 1 38 10.10.40.2 ge-0/0/3.0 Full 3.3.3.3 1 30
Cumulus
cumulus@cumulus01:~$ net show ospf neighbor Neighbor ID Pri State Dead Time Address Interface RXmtL RqstL DBsmL 2.2.2.2 128 Full/DR 36.926s 10.10.10.2 swp1:10.10.10.1 0 0 0 3.3.3.3 1 Full/DR 38.225s 10.10.50.2 swp3:10.10.50.1 0 0 0 4.4.4.4 1 Full/DR 34.672s 10.10.20.2 swp2:10.10.20.1 0 0 0
zmianę hostname zobaczymy po przelogowaniu.
weryfikacyjny ping
Arista
Arista01#ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 72(100) bytes of data. 80 bytes from 1.1.1.1: icmp_req=1 ttl=64 time=151 ms 80 bytes from 1.1.1.1: icmp_req=2 ttl=64 time=94.2 ms 80 bytes from 1.1.1.1: icmp_req=3 ttl=64 time=24.4 ms 80 bytes from 1.1.1.1: icmp_req=4 ttl=64 time=18.5 ms 80 bytes from 1.1.1.1: icmp_req=5 ttl=64 time=84.8 ms --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 545ms rtt min/avg/max/mdev = 18.594/74.807/151.959/49.255 ms, ipg/ewma 136.416/111.940 ms Arista01#ping 2.2.2.2 PING 2.2.2.2 (2.2.2.2) 72(100) bytes of data. 80 bytes from 2.2.2.2: icmp_req=1 ttl=64 time=51.7 ms 80 bytes from 2.2.2.2: icmp_req=2 ttl=64 time=40.1 ms 80 bytes from 2.2.2.2: icmp_req=3 ttl=64 time=21.4 ms 80 bytes from 2.2.2.2: icmp_req=4 ttl=64 time=11.1 ms 80 bytes from 2.2.2.2: icmp_req=5 ttl=64 time=7.46 ms --- 2.2.2.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 192ms rtt min/avg/max/mdev = 7.462/26.396/51.712/17.004 ms, ipg/ewma 48.130/37.885 ms Arista01#ping 3.3.3.3 PING 3.3.3.3 (3.3.3.3) 72(100) bytes of data. 80 bytes from 3.3.3.3: icmp_req=1 ttl=64 time=0.130 ms 80 bytes from 3.3.3.3: icmp_req=2 ttl=64 time=0.045 ms 80 bytes from 3.3.3.3: icmp_req=3 ttl=64 time=0.073 ms 80 bytes from 3.3.3.3: icmp_req=4 ttl=64 time=0.045 ms 80 bytes from 3.3.3.3: icmp_req=5 ttl=64 time=0.043 ms --- 3.3.3.3 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3ms rtt min/avg/max/mdev = 0.043/0.067/0.130/0.033 ms, ipg/ewma 0.978/0.097 ms Arista01#ping 4.4.4.4 PING 4.4.4.4 (4.4.4.4) 72(100) bytes of data. 80 bytes from 4.4.4.4: icmp_req=1 ttl=255 time=42.5 ms 80 bytes from 4.4.4.4: icmp_req=2 ttl=255 time=33.1 ms 80 bytes from 4.4.4.4: icmp_req=3 ttl=255 time=16.9 ms 80 bytes from 4.4.4.4: icmp_req=4 ttl=255 time=24.0 ms 80 bytes from 4.4.4.4: icmp_req=5 ttl=255 time=11.2 ms --- 4.4.4.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 159ms rtt min/avg/max/mdev = 11.291/25.582/42.522/11.193 ms, ipg/ewma 39.930/33.360 ms Arista01#
Cisco
Cisco01#ping 1.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 2/9/18 ms Cisco01#ping 2.2.2.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 2/9/18 ms Cisco01#ping 3.3.3.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 25/43/86 ms Cisco01#ping 4.4.4.4 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/3 ms Cisco01#
Juniper
root@vMX01> ping count 5 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=64 time=11.263 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=3.556 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=12.002 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=6.014 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=64 time=3.728 ms --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 3.556/7.313/12.002/3.640 ms root@vMX01> ping count 5 2.2.2.2 PING 2.2.2.2 (2.2.2.2): 56 data bytes 64 bytes from 2.2.2.2: icmp_seq=0 ttl=64 time=0.379 ms 64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=0.116 ms 64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from 2.2.2.2: icmp_seq=3 ttl=64 time=0.231 ms 64 bytes from 2.2.2.2: icmp_seq=4 ttl=64 time=0.167 ms --- 2.2.2.2 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.048/0.188/0.379/0.113 ms root@vMX01> ping count 5 3.3.3.3 PING 3.3.3.3 (3.3.3.3): 56 data bytes 64 bytes from 3.3.3.3: icmp_seq=0 ttl=64 time=70.368 ms 64 bytes from 3.3.3.3: icmp_seq=1 ttl=64 time=9.457 ms 64 bytes from 3.3.3.3: icmp_seq=2 ttl=64 time=17.251 ms 64 bytes from 3.3.3.3: icmp_seq=3 ttl=64 time=9.931 ms 64 bytes from 3.3.3.3: icmp_seq=4 ttl=64 time=11.101 ms --- 3.3.3.3 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 9.457/23.622/70.368/23.540 ms root@vMX01> ping count 5 4.4.4.4 PING 4.4.4.4 (4.4.4.4): 56 data bytes 64 bytes from 4.4.4.4: icmp_seq=0 ttl=255 time=5.418 ms 64 bytes from 4.4.4.4: icmp_seq=1 ttl=255 time=2.295 ms 64 bytes from 4.4.4.4: icmp_seq=2 ttl=255 time=20.893 ms 64 bytes from 4.4.4.4: icmp_seq=3 ttl=255 time=6.589 ms 64 bytes from 4.4.4.4: icmp_seq=4 ttl=255 time=78.685 ms --- 4.4.4.4 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 2.295/22.776/78.685/28.678 ms
Cumulus
cumulus@cumulus01:~$ ping 1.1.1.1 -c 5 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=64 time=0.194 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=64 time=0.059 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=64 time=0.058 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=64 time=0.054 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=64 time=0.056 ms --- 1.1.1.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.054/0.084/0.194/0.055 ms cumulus@cumulus01:~$ ping 2.2.2.2 -c 5 PING 2.2.2.2 (2.2.2.2) 56(84) bytes of data. 64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=1.16 ms 64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=1.10 ms 64 bytes from 2.2.2.2: icmp_seq=3 ttl=64 time=0.931 ms 64 bytes from 2.2.2.2: icmp_seq=4 ttl=64 time=1.03 ms 64 bytes from 2.2.2.2: icmp_seq=5 ttl=64 time=0.986 ms --- 2.2.2.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 0.931/1.044/1.165/0.085 ms cumulus@cumulus01:~$ ping 3.3.3.3 -c 5 PING 3.3.3.3 (3.3.3.3) 56(84) bytes of data. 64 bytes from 3.3.3.3: icmp_seq=1 ttl=64 time=60.4 ms 64 bytes from 3.3.3.3: icmp_seq=2 ttl=64 time=9.62 ms 64 bytes from 3.3.3.3: icmp_seq=3 ttl=64 time=7.31 ms 64 bytes from 3.3.3.3: icmp_seq=4 ttl=64 time=6.94 ms 64 bytes from 3.3.3.3: icmp_seq=5 ttl=64 time=7.10 ms --- 3.3.3.3 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 6.943/18.286/60.442/21.100 ms cumulus@cumulus01:~$ ping 4.4.4.4 -c 5 PING 4.4.4.4 (4.4.4.4) 56(84) bytes of data. 64 bytes from 4.4.4.4: icmp_seq=1 ttl=255 time=0.398 ms 64 bytes from 4.4.4.4: icmp_seq=2 ttl=255 time=0.335 ms 64 bytes from 4.4.4.4: icmp_seq=3 ttl=255 time=0.328 ms 64 bytes from 4.4.4.4: icmp_seq=4 ttl=255 time=0.300 ms 64 bytes from 4.4.4.4: icmp_seq=5 ttl=255 time=0.322 ms --- 4.4.4.4 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4000ms rtt min/avg/max/mdev = 0.300/0.336/0.398/0.038 ms
Pliki konfiguracyjne
Poniżej znajdziemy pliki konfiguracyjne z urządzeń, z konfiguracji usunąłem użytkowników oraz ich hasła.
Arista_config
Cisco_config
Juniper_config
Cumulus
dla Cumulusa jest wynik polecenia net show configuration
I na tym kończymy dzisiejszy wpis, niebawem kolejny w podobnym stylu.
