HCIA第十二天-OSPF实验

发布时间：2026/7/27 19:20:19

HCIA第十二天-OSPF实验

HCIA第十二天-OSPF实验

一、地址划分

骨干链路--3段+1段（需要4个地址）

环回地址需要5段

172.16.0.0/16

172.16.0.0/24

1段：172.16.0.0/25

3段：172.16.0.128/25

172.16.0.128/30 172.16.0.132/30 172.16.0.136/30

环回地址：172.16.1.0/24 172.16.2.0/24 172.16.3.0/24 172.16.5.0/24

R1地址

[R1]int [R1]interface loopback 0 [R1-LoopBack0]ip address 172.16.1.1 24 [R1-LoopBack0]q [R1]inter [R1]interface s4/0/0 [R1-Serial4/0/0]ip address 172.16.0.129 30 [R1-Serial4/0/0]

R2地址

[R2]int [R2]interface loopback 0 [R2-LoopBack0]ip address 172.16.2.1 24 [R2-LoopBack0]q [R2]int [R2]interface s4/0/0 [R2-Serial4/0/0]ip address 172.16.0.130 30 [R2-Serial4/0/0] Dec 8 2024 19:45:46-08:00 R2 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol PPP IPCP on the interface Serial4/0/0 has entered the UP state. [R2-Serial4/0/0]q [R2]int [R2]interface g0/0/0 [R2-GigabitEthernet0/0/0]ip address 172.16.0.1 25 Dec 8 2024 19:46:32-08:00 R2 %%01IFNET/4/LINK_STATE(l)[3]:The line protocol IP on the interface GigabitEthernet0/0/0 has entered the UP state. [R2-GigabitEthernet0/0/0]

R3地址

[R3]int [R3]interface loopback 0 [R3-LoopBack0]ip address 172.16.3.1 24 [R3-LoopBack0]q [R3]int [R3]interface g0/0/0 [R3-GigabitEthernet0/0/0]ip address 172.16.0.3 25 Dec 8 2024 19:50:14-08:00 R3 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP on the interface GigabitEthernet0/0/0 has entered the UP state. [R3-GigabitEthernet0/0/0]q [R3]int [R3]interface s4/0/0 [R3-Serial4/0/0]ip address 172.16.0.133 30 [R3-Serial4/0/0]

R4地址

[R4]inter [R4]interface loop [R4]interface LoopBack 0 [R4-LoopBack0]ip address 172.16.4.1 24 [R4-LoopBack0]q [R4]int [R4]interface s4/0/0 [R4-Serial4/0/0]ip address 172.16.0.134 30 [R4-Serial4/0/0] Dec 8 2024 19:54:50-08:00 R4 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol PPP IPCP on the interface Serial4/0/0 has entered the UP state. [R4-Serial4/0/0]q [R4]int [R4]interface s4/0/1 [R4-Serial4/0/1]ip address 172.16.0.137 30 [R4-Serial4/0/1]q [R4]inter [R4]interface g0/0/0 [R4-GigabitEthernet0/0/0]ip address 172.16.0.4 25 Dec 8 2024 19:56:23-08:00 R4 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP on the interface GigabitEthernet0/0/0 has entered the UP state. [R4-GigabitEthernet0/0/0]

R5地址

[R5]int [R5]interface loopback 0 [R5-LoopBack0]ip address 172.16.5.1 24 [R5-LoopBack0]q [R5]interface s4/0/0 [R5-Serial4/0/0]ip address 172.16.0.138 30 [R5-Serial4/0/0] Dec 8 2024 20:01:20-08:00 R5 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol PPP IPCP on the interface Serial4/0/0 has entered the UP state. [R5-Serial4/0/0]q [R5]int [R5]interface g0/0/0 [R5-GigabitEthernet0/0/0]ip address 172.16.0.5 25 [R5-GigabitEthernet0/0/0] Dec 8 2024 20:01:52-08:00 R5 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol IP on the interface GigabitEthernet0/0/0 has entered the UP state. [R5-GigabitEthernet0/0/0]

测试连通性

[R2]ping 172.16.0.129 PING 172.16.0.129: 56 data bytes, press CTRL_C to break Reply from 172.16.0.129: bytes=56 Sequence=1 ttl=255 time=50 ms Reply from 172.16.0.129: bytes=56 Sequence=2 ttl=255 time=20 ms Reply from 172.16.0.129: bytes=56 Sequence=3 ttl=255 time=30 ms Reply from 172.16.0.129: bytes=56 Sequence=4 ttl=255 time=30 ms Reply from 172.16.0.129: bytes=56 Sequence=5 ttl=255 time=20 ms ​ --- 172.16.0.129 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 20/30/50 ms ​ [R2]ping 172.16.0.3 PING 172.16.0.3: 56 data bytes, press CTRL_C to break Reply from 172.16.0.3: bytes=56 Sequence=1 ttl=255 time=80 ms Reply from 172.16.0.3: bytes=56 Sequence=2 ttl=255 time=40 ms Reply from 172.16.0.3: bytes=56 Sequence=3 ttl=255 time=30 ms Reply from 172.16.0.3: bytes=56 Sequence=4 ttl=255 time=40 ms Reply from 172.16.0.3: bytes=56 Sequence=5 ttl=255 time=50 ms ​ --- 172.16.0.3 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 30/48/80 ms ​

证明可以直通

二、路由宣告

R1

[R1]ospf 1 router-id 1.1.1.1 [R1-ospf-1]area 1 [R1-ospf-1-area-0.0.0.1]net [R1-ospf-1-area-0.0.0.1]network 172.16.0.0 0.0.255.255 [R1-ospf-1-area-0.0.0.1]

R2

[R2]os [R2]ospf 1rou [R2]ospf 1 [R2]ospf 1 rou [R2]ospf 1 router-id 2.2.2.2 [R2-ospf-1]area 1 [R2-ospf-1-area-0.0.0.1]network 172.16.0.130 0.0.0.0 [R2-ospf-1-area-0.0.0.1] Dec 8 2024 20:27:34-08:00 R2 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=129.0.16.172, Neigh borEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R2-ospf-1-area-0.0.0.1] Dec 8 2024 20:27:34-08:00 R2 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=129.0.16.172, Neigh borEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart) [R2-ospf-1-area-0.0.0.1] Dec 8 2024 20:27:34-08:00 R2 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=129.0.16.172, Neigh borEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Ex change) [R2-ospf-1-area-0.0.0.1] Dec 8 2024 20:27:34-08:00 R2 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=129.0.16.172, Neigh borEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Load ing) [R2-ospf-1-area-0.0.0.1] Dec 8 2024 20:27:34-08:00 R2 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=129.0.16.172, Neigh borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) ​ [R2-ospf-1-area-0.0.0.1]q [R2-ospf-1]area 1 [R2-ospf-1-area-0.0.0.1]net [R2-ospf-1-area-0.0.0.1]network 172.16.2.1 0.0.0.0 [R2-ospf-1-area-0.0.0.1]q [R2-ospf-1]area 0 [R2-ospf-1-area-0.0.0.0]network 172.16.0.1 0.0.0.0 [R2-ospf-1-area-0.0.0.0]

R3

[R3]ospf 1rou [R3]ospf 1 rout [R3]ospf 1 router-id 3.3.3.3 [R3-ospf-1]area 0 [R3-ospf-1-area-0.0.0.0]network 172.16.0.3 0.0.0.0 [R3-ospf-1-area-0.0.0.0]q [R3-ospf-1] Dec 8 2024 20:37:13-08:00 R3 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R3-ospf-1] Dec 8 2024 20:37:13-08:00 R3 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) [R3-ospf-1] Dec 8 2024 20:37:13-08:00 R3 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) [R3-ospf-1] Dec 8 2024 20:37:13-08:00 R3 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exch ange) [R3-ospf-1] Dec 8 2024 20:37:13-08:00 R3 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadin g) [R3-ospf-1] Dec 8 2024 20:37:13-08:00 R3 %%01OSPF/4/NBR_CHANGE_E(l)[5]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R3-ospf-1]area 2 [R3-ospf-1-area-0.0.0.2]net [R3-ospf-1-area-0.0.0.2]network 172.16.3.1 0.0.0.0 [R3-ospf-1-area-0.0.0.2]net [R3-ospf-1-area-0.0.0.2]network 172.16.0.133 0.0.0.0 [R3-ospf-1-area-0.0.0.2]

R4

[R4]os [R4]ospf 1 rou [R4]ospf 1 router-id 4.4.4.4 [R4-ospf-1]area 0 [R4-ospf-1-area-0.0.0.0]network 172.16.0.4 0.0.0.0 [R4-ospf-1-area-0.0.0.0]q [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[5]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[6]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exch ange) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[7]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exch ange) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[8]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadin g) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[9]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[10]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighb orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi ng) [R4-ospf-1] Dec 8 2024 20:40:40-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[11]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighb orEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R4-ospf-1]area 2 [R4-ospf-1-area-0.0.0.2]net [R4-ospf-1-area-0.0.0.2]network 172.16.2.1 0.0.0.0 [R4-ospf-1-area-0.0.0.2]net [R4-ospf-1-area-0.0.0.2]network 172.16.0.134 0.0.0.0 [R4-ospf-1-area-0.0.0.2] Dec 8 2024 20:41:44-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[12]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neig hborEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) ​ [R4-ospf-1-area-0.0.0.2] Dec 8 2024 20:41:44-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[13]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neig hborEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart ) [R4-ospf-1-area-0.0.0.2] Dec 8 2024 20:41:44-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[14]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neig hborEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=E xchange) [R4-ospf-1-area-0.0.0.2] Dec 8 2024 20:41:44-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[15]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neig hborEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loa ding) [R4-ospf-1-area-0.0.0.2] Dec 8 2024 20:41:44-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[16]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neig hborEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R4-ospf-1-area-0.0.0.2]net [R4-ospf-1-area-0.0.0.2]network 172.16.0.137 0.0.0.0 [R4-ospf-1-area-0.0.0.2]

R5

[R5]os [R5]ospf 1 rou [R5]ospf 1 router-id 5.5.5.5 [R5-ospf-1]area 0 [R5-ospf-1-area-0.0.0.0]net [R5-ospf-1-area-0.0.0.0]network 172.16.0.5 0.0.0.0 [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:25-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=4.0.16.172, Neighbo rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:25-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=4.0.16.172, Neighbo rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:26-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:26-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:29-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:29-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[5]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:29-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[6]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:29-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[7]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighbo rEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:29-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[8]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=4.0.16.172, Neighbo rEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=2Way) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:29-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[9]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighbo rEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exch ange) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:30-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[10]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighb orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc hange) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:30-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[11]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighb orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi ng) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:30-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[12]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=1.0.16.172, Neighb orEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:30-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[13]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighb orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi ng) [R5-ospf-1-area-0.0.0.0] Dec 8 2024 20:44:30-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[14]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=3.0.16.172, Neighb orEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R5-ospf-1-area-0.0.0.0]q [R5-ospf-1]area 2 [R5-ospf-1-area-0.0.0.2]network 172.16.5.1 0.0.0.0 [R5-ospf-1-area-0.0.0.2]net [R5-ospf-1-area-0.0.0.2]network 172.16.0.138 0.0.0.0 [R5-ospf-1-area-0.0.0.2] Dec 8 2024 20:46:07-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[15]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neig hborEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) ​ [R5-ospf-1-area-0.0.0.2] Dec 8 2024 20:46:07-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[16]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neig hborEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart ) [R5-ospf-1-area-0.0.0.2] Dec 8 2024 20:46:07-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[17]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neig hborEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=E xchange) [R5-ospf-1-area-0.0.0.2] Dec 8 2024 20:46:07-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[18]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neig hborEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loa ding) [R5-ospf-1-area-0.0.0.2] Dec 8 2024 20:46:07-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[19]:Neighbor changes ev ent: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neig hborEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) [R5-ospf-1-area-0.0.0.2]

查看路由

<R1>display ip routing-table protocol ospf Route Flags: R - relay, D - download to fib ------------------------------------------------------------------------------ Public routing table : OSPF Destinations : 7 Routes : 7 ​ OSPF routing table status : <Active> Destinations : 7 Routes : 7 ​ Destination/Mask Proto Pre Cost Flags NextHop Interface ​ 172.16.0.0/25 OSPF 10 49 D 172.16.0.130 Serial4/0/0 172.16.0.132/30 OSPF 10 97 D 172.16.0.130 Serial4/0/0 172.16.0.136/30 OSPF 10 97 D 172.16.0.130 Serial4/0/0 172.16.2.1/32 OSPF 10 48 D 172.16.0.130 Serial4/0/0 172.16.3.1/32 OSPF 10 49 D 172.16.0.130 Serial4/0/0 172.16.4.1/32 OSPF 10 49 D 172.16.0.130 Serial4/0/0 172.16.5.1/32 OSPF 10 49 D 172.16.0.130 Serial4/0/0 ​ OSPF routing table status : <Inactive> Destinations : 0 Routes : 0 ​

测试连通性

<R1>ping 172.16.4.1 PING 172.16.4.1: 56 data bytes, press CTRL_C to break Reply from 172.16.4.1: bytes=56 Sequence=1 ttl=254 time=100 ms Reply from 172.16.4.1: bytes=56 Sequence=2 ttl=254 time=50 ms Reply from 172.16.4.1: bytes=56 Sequence=3 ttl=254 time=40 ms Reply from 172.16.4.1: bytes=56 Sequence=4 ttl=254 time=30 ms Reply from 172.16.4.1: bytes=56 Sequence=5 ttl=254 time=60 ms ​ --- 172.16.4.1 ping statistics --- 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 30/56/100 ms

三、查看MA网络

<R2>display ospf peer ​ OSPF Process 1 with Router ID 2.2.2.2 Neighbors ​ Area 0.0.0.0 interface 172.16.0.1(GigabitEthernet0/0/0)'s neighbors Router ID: 3.3.3.3 Address: 172.16.0.3 State: Full Mode:Nbr is Master Priority: 1 DR: 172.16.0.1 BDR: 172.16.0.3 MTU: 0 Dead timer due in 35 sec Retrans timer interval: 5 Neighbor is up for 00:22:30 Authentication Sequence: [ 0 ] ​ Router ID: 4.4.4.4 Address: 172.16.0.4 State: Full Mode:Nbr is Master Priority: 1 DR: 172.16.0.1 BDR: 172.16.0.3 MTU: 0 Dead timer due in 40 sec Retrans timer interval: 4 Neighbor is up for 00:19:03 Authentication Sequence: [ 0 ] ​ Router ID: 5.5.5.5 Address: 172.16.0.5 State: Full Mode:Nbr is Master Priority: 1 DR: 172.16.0.1 BDR: 172.16.0.3 MTU: 0 Dead timer due in 39 sec Retrans timer interval: 5 Neighbor is up for 00:15:14 Authentication Sequence: [ 0 ]

四、R3与R4明文，R4与R5密文

R3与R4

[R3]int [R3]interface s4/0/0 [R3-Serial4/0/0]ospf [R3-Serial4/0/0]ospf au [R3-Serial4/0/0]ospf authentication-mode si [R3-Serial4/0/0]ospf authentication-mode simple c [R3-Serial4/0/0]ospf authentication-mode simple cipher huawei [R3-Serial4/0/0] [R4-Serial4/0/0]os [R4-Serial4/0/0]ospf au [R4-Serial4/0/0]ospf authentication-mode si [R4-Serial4/0/0]ospf authentication-mode simple c [R4-Serial4/0/0]ospf authentication-mode simple cipher huawei [R4-Serial4/0/0] Dec 8 2024 21:09:36-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neigh borEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R4-Serial4/0/0] Dec 8 2024 21:09:36-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neigh borEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart) [R4-Serial4/0/0] Dec 8 2024 21:09:36-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neigh borEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Ex change) [R4-Serial4/0/0] Dec 8 2024 21:09:36-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neigh borEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Load ing) [R4-Serial4/0/0] Dec 8 2024 21:09:36-08:00 R4 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=133.0.16.172, Neigh borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) ​ [R4-Serial4/0/0]

R4与R5

[R4]int [R4]interface s4/0/1 [R4-Serial4/0/1]os [R4-Serial4/0/1]ospf au [R4-Serial4/0/1]ospf authentication-mode m [R4-Serial4/0/1]ospf authentication-mode md5 1 huawei [R4-Serial4/0/1] [R5-Serial4/0/0]os [R5-Serial4/0/0]ospf au [R5-Serial4/0/0]ospf authentication-mode m [R5-Serial4/0/0]ospf authentication-mode md5 1 huawei [R5-Serial4/0/0] Dec 8 2024 21:17:11-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neigh borEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) [R5-Serial4/0/0] Dec 8 2024 21:17:16-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neigh borEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart) [R5-Serial4/0/0] Dec 8 2024 21:17:16-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neigh borEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Ex change) [R5-Serial4/0/0] Dec 8 2024 21:17:16-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neigh borEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Load ing) [R5-Serial4/0/0] Dec 8 2024 21:17:16-08:00 R5 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes eve nt: neighbor status changed. (ProcessId=256, NeighborAddress=137.0.16.172, Neigh borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) ​ [R5-Serial4/0/0] 至此，试验结束

实验总结

熟练运用ospf相关知识

相关新闻

Lyciumaker三国杀卡牌制作器：零基础5分钟打造专属武将的完整指南

Lyciumaker三国杀卡牌制作器：零基础5分钟打造专属武将的完整指南

Lyciumaker三国杀卡牌制作器&#xff1a;零基础5分钟打造专属武将的完整指南 【免费下载链接】Lyciumaker 在线三国杀卡牌制作器 项目地址: https://gitcode.com/gh_mirrors/ly/Lyciumaker 想为心爱的三国角色设计独一无二的卡牌却苦于没有设计经验&#xff1f;Lyciumak…

2026/7/27 19:20:19
网盘直链下载助手：告别限速，拥抱自由下载的终极指南

网盘直链下载助手：告别限速，拥抱自由下载的终极指南

网盘直链下载助手&#xff1a;告别限速&#xff0c;拥抱自由下载的终极指南 【免费下载链接】Online-disk-direct-link-download-assistant 一个基于 JavaScript 的网盘文件下载地址获取工具。基于【网盘直链下载助手】修改 &#xff0c;支持 百度网盘 / 阿里云盘 / 中国移动云…

2026/7/27 19:20:19
WebDeck：5个实用场景展示如何用浏览器打造高效远程控制面板

WebDeck：5个实用场景展示如何用浏览器打造高效远程控制面板

WebDeck&#xff1a;5个实用场景展示如何用浏览器打造高效远程控制面板 【免费下载链接】WebDeck The free stream deck alternative 项目地址: https://gitcode.com/gh_mirrors/we/WebDeck WebDeck是一款创新的免费开源远程控制解决方案&#xff0c;它彻底改变了传统物…

2026/7/27 19:20:19

最新新闻

Linux内核竞态条件检测与锁机制优化实战

Linux内核竞态条件检测与锁机制优化实战

1. 竞态条件&#xff1a;Linux内核中的隐形炸弹竞态条件&#xff08;Race Condition&#xff09;是Linux内核开发中最棘手的Bug类型之一。想象两个线程同时操作共享内存&#xff0c;就像两个人在黑暗房间里传递花瓶——谁先碰到、谁后松手都会导致完全不同的结果。我在处理ext4…

2026/7/27 20:26:24
广州知名垂直新闻媒体发稿公司推荐！深耕细分赛道 GEO 布局，软文发稿优选汇捷媒介 - 全域品牌推荐

广州知名垂直新闻媒体发稿公司推荐！深耕细分赛道 GEO 布局，软文发稿优选汇捷媒介 - 全域品牌推荐

生成式 AI 营销全面普及，GEO 生成式引擎优化已经成为广州生物医药、科创硬科技、财经金融、跨境商贸、汽车智造企业抢占细分赛道精准流量的核心手段。豆包、DeepSeek、通义千问等 AI 大模型依托 E-E-A-T 标准评估品牌…

2026/7/27 20:26:24
2026双轨视觉筛选设备值得信赖品牌TOP6榜单 - 资讯报道

2026双轨视觉筛选设备值得信赖品牌TOP6榜单 - 资讯报道

随着智能制造升级，双轨及四轨光学筛选设备逐渐成为电子元器件、精密五金、服装饰品、密封件等行业质检环节的常用工具。相较于依赖肉眼判断的传统人工质检模式，机器视觉检测设备凭借高频采样、数据可追溯及连续作业能…

2026/7/27 20:26:24
记录一个初始化配置时机问题导致的401

记录一个初始化配置时机问题导致的401

记录一个初始化配置时机问题导致的401 背景&#xff1a;一个诡异的401错误上周&#xff0c;我负责维护的一个微服务突然在线上报出大量401错误。这个服务负责与第三方支付平台交互&#xff0c;需要在启动时加载API密钥和签名密钥等敏感配置。诡异的是&#xff0c;服务启动后前几…

2026/7/27 20:26:33
办公效率工具领域观察2026年手机录音转文字助手赛道出现了哪些新变量？

办公效率工具领域观察2026年手机录音转文字助手赛道出现了哪些新变量？

简短结论 2026年手机录音转文字助手赛道的核心新变量&#xff0c;是从「单纯转文字」进化到「场景化结构化整理」&#xff0c;头部工具都完成了大模型能力升级&#xff0c;细分场景开始出现垂直优化产品。没有通用的最优选择&#xff0c;不同工具匹配不同需求&#xff0c;听脑A…

2026/7/27 20:26:33
长时运行AI Agent的技术实现与工程挑战

长时运行AI Agent的技术实现与工程挑战

1. 长时运行Agent的行业背景与核心定义2025-2026年的AI领域正在经历一场静默的革命。当普通用户还在关注模型的单次响应速度时&#xff0c;行业前沿已经转向一个更关键的指标&#xff1a;AI系统持续处理复杂任务的能力。这种转变源于实际业务需求的演变——从简单的问答场景升级…

2026/7/27 20:26:33

日新闻

SolidWorks许可证预测优化：数据驱动降本增效

SolidWorks许可证预测优化：数据驱动降本增效

1. 项目背景与核心价值在工业设计领域&#xff0c;SolidWorks作为三维CAD软件的标杆产品&#xff0c;其许可证管理一直是企业IT成本管控的痛点。某中型制造企业曾因许可证短缺导致项目延期&#xff0c;而另一家则因过度采购造成每年近20万元的资源浪费——这正是我们开发这套预…

2026/7/27 0:00:07
OpenClaw开源智能体网关：AI助手与即时通讯的完美融合

OpenClaw开源智能体网关：AI助手与即时通讯的完美融合

1. 项目概述&#xff1a;当AI助手遇上即时通讯上周在调试一个自动化工作流时&#xff0c;我突然意识到&#xff1a;如果能把AI助手直接集成到日常使用的聊天软件里&#xff0c;很多重复性工作就能在对话中一键完成。这个想法促使我找到了OpenClaw——一个开源的智能体网关项目&…

2026/7/27 0:00:43
【JAVA毕设源码分享】基于SpringBoot的社区智能垃圾管理系统的设计与实现(程序+文档+代码讲解+一条龙定制)

【JAVA毕设源码分享】基于SpringBoot的社区智能垃圾管理系统的设计与实现(程序+文档+代码讲解+一条龙定制)

博主介绍&#xff1a;✌️码农一枚 &#xff0c;专注于大学生项目实战开发、讲解和毕业&#x1f6a2;文撰写修改等。全栈领域优质创作者&#xff0c;博客之星、掘金/华为云/阿里云/InfoQ等平台优质作者、专注于Java、小程序技术领域和毕业项目实战 ✌️技术范围&#xff1a;&am…

2026/7/27 0:00:53

周新闻

Apex英雄目标检测数据集 深度学习框架YOLO如何训练APEX数据集

Apex英雄目标检测数据集 深度学习框架YOLO如何训练APEX数据集

Apex检测数据集数据集详情检测类别&#xff1a; allies enemy tag图片总量&#xff1a;7247张训练集&#xff1a;5139张验证集&#xff1a;1425张测试集&#xff1a;683张标注状态&#xff1a;全部已标注&#xff0c;即拿即用数据格式&#xff1a;支持YOLO格式及其他格式&#…

2026/7/27 7:47:45
智慧飞行 大疆无人机一站式智能管控平台/支持大疆机场/私有化部署 从航线规划、自动飞行、AI识别到数据管理，一个平台全搞定

智慧飞行 大疆无人机一站式智能管控平台/支持大疆机场/私有化部署 从航线规划、自动飞行、AI识别到数据管理，一个平台全搞定

智慧飞行-大疆无人机一站式智能管控平台/支持大疆机场/私有化部署 企业级全域智能无人机一体化管控平台源码&#xff01; 专为电力巡检、安防监控、应急救援、测绘勘察等行业打造&#xff0c;让您的无人机舰队实现 “无人化、自动化、智能化” 管理&#xff01; &#x1f3af; …

2026/7/27 5:35:46
揭秘ChatGPT+Mathematica协同教学：为什么92%的初学者在72小时内建立函数直觉？

揭秘ChatGPT+Mathematica协同教学：为什么92%的初学者在72小时内建立函数直觉？

更多请点击&#xff1a; https://codechina.net 第一章&#xff1a;AI帮助理解数学概念 人工智能正以前所未有的方式重塑数学学习的路径。通过自然语言处理与符号计算的深度融合&#xff0c;AI不仅能解析抽象定义&#xff0c;还能将定理、证明和几何直觉转化为可交互、可验证的…

2026/7/27 7:47:48

月新闻

[C++]内存管理：串顺序存储的内存回收

[C++]内存管理：串顺序存储的内存回收

在串&#xff08;字符串&#xff09;的顺序存储中&#xff0c;内存回收的方式取决于字符串的存储方式以及所使用的编程语言和相关库。以下以 C 为例进行说明&#xff0c;因为 C 对内存管理有较为直接的控制。 1. 基于 char 数组的串顺序存储 如果使用普通的 char 数组来存储字…

2026/7/26 21:51:47
移动端游戏功耗测试实战：电流、功率、亮度和场景对比

移动端游戏功耗测试实战：电流、功率、亮度和场景对比

移动端游戏功耗测试：先控制变量，再比较优化是否真的省电 摘要：功耗测试最容易犯的错误，是拿两次不同温度、不同亮度、不同场景的平均功率直接比较。本文给出一套可复现的游戏功耗测试方法，覆盖引擎特性验证、版本回归和黑盒体验测试，并说明如何把功耗与帧率、温控、CPU/G…

2026/7/27 1:01:39
足球口袋教练 HarmonyOS 离线应用实战（03/20）：ArkUI 首页仪表盘搭建

足球口袋教练 HarmonyOS 离线应用实战（03/20）：ArkUI 首页仪表盘搭建

本文是“足球口袋教练 HarmonyOS 离线应用实战”系列第 3 篇。示例项目是一个 HarmonyOS / ArkTS / ArkUI 编写的离线足球训练助手&#xff0c;围绕真实页面、真实截图和可复现操作展开。 本篇要解决的问题 训练 App 的首页不能只展示欢迎语&#xff0c;它要解决“我现在该点哪…

2026/7/27 9:28:36