HCIA第十二天-OSPF实验
HCIA第十二天-OSPF实验一、地址划分骨干链路--3段1段需要4个地址环回地址需要5段172.16.0.0/16172.16.0.0/241段172.16.0.0/253段172.16.0.128/25172.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/24R1地址[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: bytes56 Sequence1 ttl255 time50 ms Reply from 172.16.0.129: bytes56 Sequence2 ttl255 time20 ms Reply from 172.16.0.129: bytes56 Sequence3 ttl255 time30 ms Reply from 172.16.0.129: bytes56 Sequence4 ttl255 time30 ms Reply from 172.16.0.129: bytes56 Sequence5 ttl255 time20 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: bytes56 Sequence1 ttl255 time80 ms Reply from 172.16.0.3: bytes56 Sequence2 ttl255 time40 ms Reply from 172.16.0.3: bytes56 Sequence3 ttl255 time30 ms Reply from 172.16.0.3: bytes56 Sequence4 ttl255 time40 ms Reply from 172.16.0.3: bytes56 Sequence5 ttl255 time50 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. (ProcessId256, NeighborAddress129.0.16.172, Neigh borEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress129.0.16.172, Neigh borEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress129.0.16.172, Neigh borEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateEx 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. (ProcessId256, NeighborAddress129.0.16.172, Neigh borEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoad 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. (ProcessId256, NeighborAddress129.0.16.172, Neigh borEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) ​ [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventAdjOk?, NeighborPreviousState2Way, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateExch 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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoadin 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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventAdjOk?, NeighborPreviousState2Way, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEventAdjOk?, NeighborPreviousState2Way, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateExch 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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateExch 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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoadin 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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighb orEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoadi 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. (ProcessId256, NeighborAddress3.0.16.172, Neighb orEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [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. (ProcessId256, NeighborAddress133.0.16.172, Neig hborEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) ​ [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. (ProcessId256, NeighborAddress133.0.16.172, Neig hborEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentStateExStart ) [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. (ProcessId256, NeighborAddress133.0.16.172, Neig hborEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateE 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. (ProcessId256, NeighborAddress133.0.16.172, Neig hborEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoa 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. (ProcessId256, NeighborAddress133.0.16.172, Neig hborEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [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. (ProcessId256, NeighborAddress4.0.16.172, Neighbo rEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress4.0.16.172, Neighbo rEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventAdjOk?, NeighborPreviousState2Way, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighbo rEventAdjOk?, NeighborPreviousState2Way, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress4.0.16.172, Neighbo rEventAdjOk?, NeighborPreviousState2Way, NeighborCurrentState2Way) [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. (ProcessId256, NeighborAddress1.0.16.172, Neighbo rEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateExch 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. (ProcessId256, NeighborAddress3.0.16.172, Neighb orEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateExc 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. (ProcessId256, NeighborAddress1.0.16.172, Neighb orEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoadi 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. (ProcessId256, NeighborAddress1.0.16.172, Neighb orEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [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. (ProcessId256, NeighborAddress3.0.16.172, Neighb orEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoadi 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. (ProcessId256, NeighborAddress3.0.16.172, Neighb orEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [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. (ProcessId256, NeighborAddress137.0.16.172, Neig hborEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) ​ [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. (ProcessId256, NeighborAddress137.0.16.172, Neig hborEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentStateExStart ) [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. (ProcessId256, NeighborAddress137.0.16.172, Neig hborEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateE 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. (ProcessId256, NeighborAddress137.0.16.172, Neig hborEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoa 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. (ProcessId256, NeighborAddress137.0.16.172, Neig hborEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) [R5-ospf-1-area-0.0.0.2]查看路由R1display 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 ​测试连通性R1ping 172.16.4.1 PING 172.16.4.1: 56 data bytes, press CTRL_C to break Reply from 172.16.4.1: bytes56 Sequence1 ttl254 time100 ms Reply from 172.16.4.1: bytes56 Sequence2 ttl254 time50 ms Reply from 172.16.4.1: bytes56 Sequence3 ttl254 time40 ms Reply from 172.16.4.1: bytes56 Sequence4 ttl254 time30 ms Reply from 172.16.4.1: bytes56 Sequence5 ttl254 time60 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网络R2display 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. (ProcessId256, NeighborAddress133.0.16.172, Neigh borEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress133.0.16.172, Neigh borEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress133.0.16.172, Neigh borEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateEx 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. (ProcessId256, NeighborAddress133.0.16.172, Neigh borEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoad 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. (ProcessId256, NeighborAddress133.0.16.172, Neigh borEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) ​ [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. (ProcessId256, NeighborAddress137.0.16.172, Neigh borEventHelloReceived, NeighborPreviousStateDown, NeighborCurrentStateInit) [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. (ProcessId256, NeighborAddress137.0.16.172, Neigh borEvent2WayReceived, NeighborPreviousStateInit, NeighborCurrentStateExStart) [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. (ProcessId256, NeighborAddress137.0.16.172, Neigh borEventNegotiationDone, NeighborPreviousStateExStart, NeighborCurrentStateEx 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. (ProcessId256, NeighborAddress137.0.16.172, Neigh borEventExchangeDone, NeighborPreviousStateExchange, NeighborCurrentStateLoad 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. (ProcessId256, NeighborAddress137.0.16.172, Neigh borEventLoadingDone, NeighborPreviousStateLoading, NeighborCurrentStateFull) ​ [R5-Serial4/0/0] 至此试验结束实验总结熟练运用ospf相关知识

相关新闻

深度解析Deep-Live-Cam:3步实现高效实时人脸交换的完整指南

深度解析Deep-Live-Cam:3步实现高效实时人脸交换的完整指南

深度解析Deep-Live-Cam:3步实现高效实时人脸交换的完整指南 【免费下载链接】Deep-Live-Cam real time face swap and one-click video deepfake with only a single image 项目地址: https://gitcode.com/GitHub_Trending/de/Deep-Live-Cam 你是否曾想过&am…

2026/10/16 20:33:03 阅读更多 →
Magpie窗口超分辨率工具:让老旧窗口焕然一新的终极指南

Magpie窗口超分辨率工具:让老旧窗口焕然一新的终极指南

Magpie窗口超分辨率工具:让老旧窗口焕然一新的终极指南 【免费下载链接】Magpie A general-purpose window upscaler for Windows 10/11. 项目地址: https://gitcode.com/gh_mirrors/mag/Magpie 还在为老旧游戏在4K屏幕上模糊不清而烦恼吗?或者想…

2026/10/18 6:32:38 阅读更多 →
AI写的稿一眼假?没数据?试试这几个Codex Skill,帮你去掉AI生硬感

AI写的稿一眼假?没数据?试试这几个Codex Skill,帮你去掉AI生硬感

为什么用AI写的内容看着很完整,逻辑上也没问题,发出去数据却很一般。 那问题很可能就出在这些细节里:句子太规整、套话太多,没有具体经历,也没有明确态度。观众看几句就觉得一股 AI味 ,很容易直接划走。 像…

2026/10/17 22:45:16 阅读更多 →

最新新闻

Linux账号与权限管理实战:从用户规划到事故排障全解析

Linux账号与权限管理实战:从用户规划到事故排障全解析

我刚接手服务器运维时遇到的第一起事故,至今印象很深。那天业务方反馈内部管理后台登录不上,我看了一下,不是密码错,而是系统直接提示账户被锁定。当时第一反应是去改密码,改完依然进不去,后来才发现是账户…

2026/10/19 7:40:22 阅读更多 →
STM32自动浇花系统源码解析:从土壤湿度采集到水泵控制与Flash阈值存储

STM32自动浇花系统源码解析:从土壤湿度采集到水泵控制与Flash阈值存储

简介:STM32自动浇花系统是一套面向嵌入式初学者与电子爱好者的完整智能硬件实践项目,以STM32F103C8T6为核心,结合土壤温湿度、光敏、空气温湿度等传感器与OLED显示、DC-DC电源、水泵控制模块,实现按湿度阈值或定时策略自动灌溉&am…

2026/10/19 7:40:22 阅读更多 →
内核空间初始化:从引导程序到start_kernel的完整流程解析

内核空间初始化:从引导程序到start_kernel的完整流程解析

1. 内核空间初始化的整体蓝图1.1 初始化到底在做什么很多做应用开发的同事一听到"内核空间初始化",第一反应是"那不就是开机跑一段汇编把硬件摸一遍嘛"。这个理解不算错,但跟实际的内核初始化工作相比,显得太过乐观了。我…

2026/10/19 7:40:22 阅读更多 →
升维与降维互为因果:构建永续认知螺旋

升维与降维互为因果:构建永续认知螺旋

先说一个我最近的经历。某个产品功能上线不到两周,数据就出现明显下滑,团队开会复盘时,现场出现了两种截然不同的声音:一种说,要想清楚这个功能到底在服务谁、解决什么问题,别让短期指标牵着走;…

2026/10/19 7:40:21 阅读更多 →
RAG落地实战:检索增强生成的原理、架构与参数调优全解析

RAG落地实战:检索增强生成的原理、架构与参数调优全解析

最近大模型圈子里最绕不开的一个词就是RAG(Retrieval-Augmented Generation,检索增强生成)。不管是做知识库问答、企业私有数据助手,还是给大模型配上"长期记忆",背后基本都是这套架构。我自己在过去一段时间…

2026/10/19 7:40:21 阅读更多 →
把Claude当成AI同事:一套减少返工的高效工作流搭建指南

把Claude当成AI同事:一套减少返工的高效工作流搭建指南

1. 为什么我决定把 Claude 当成"同事"而不是"搜索框"1.1 一个月的试验是怎么开始的事情要从上个月说起。那段时间我手头同时压着三个项目:一个老活动的复盘报告还没交,一个新上线的功能要赶推广方案,还有日常的周报、邮件…

2026/10/19 7:39:21 阅读更多 →

日新闻

频率跟踪型PWM电源设计:臭氧发生器谐振点漂移与软开关实现

频率跟踪型PWM电源设计:臭氧发生器谐振点漂移与软开关实现

简介:本资源为电源技术方向的学术研究文档,聚焦介质阻挡放电型臭氧发生器电源的频率跟踪型PWM控制策略,面向电力电子、高压电源及臭氧应用领域的科研人员与工程技术人员。针对负载呈容性、等效电容随外加电压升高而增大、谐振频率随之漂移的难…

2026/10/19 0:00:47 阅读更多 →
Vibe Coding 遇上 TaoToken:把开发者思维圣殿的灵感流接入统一 Key 通道

Vibe Coding 遇上 TaoToken:把开发者思维圣殿的灵感流接入统一 Key 通道

/* MD / 富文本中的 .toc(含博客园搬家等嵌套结构);.toc-box 在侧栏,不受影响 */#content_views .toc,/* 编辑器常在目录前后插入空 p(:empty 仍占 20px),一并去掉避免顶空隙 */#content_views.markdown_views > p:empty:has(+ .toc),#content_views.markdown_views …

2026/10/19 0:00:47 阅读更多 →
HundredCV-Chat话题建模实战教程:利用4,871个内置话题标签构建主题分析系统

HundredCV-Chat话题建模实战教程:利用4,871个内置话题标签构建主题分析系统

【免费下载链接】HundredCV-Chat 项目地址: https://ai.gitcode.com/hf_mirrors/Jax-dan/HundredCV-Chat 点击查看 免费下载 HundredCV-Chat 是一个由 100 位青年简历数据开发而来的中文多轮对话数据集,共包含 24,750 组日常闲聊对话和 4,871 个话题标签…

2026/10/19 0:00:47 阅读更多 →

周新闻

基于GMM的语音识别系统原理与MATLAB实现详解

基于GMM的语音识别系统原理与MATLAB实现详解

说到基于高斯混合模型(GMM)的语音识别系统,很多人第一反应就是一堆数学公式,觉得门槛很高。但如果你真的在MATLAB里把它落地跑通,会发现核心其实就是三件事:把声音变成特征向量,用GMM给每个类别…

2026/10/18 0:00:55 阅读更多 →
数字图像处理入门:反白、灰度化、调色板修改与导出txt实践

数字图像处理入门:反白、灰度化、调色板修改与导出txt实践

数字图像处理这四个字听起来挺唬人,但落到具体操作上,无非就是让计算机按你的想法“摆弄”像素。我在一个模拟项目X里用了一套特别经典的基础处理流程:对图像做反白、改调色板、彩色转灰度,最后把像素数据导出成txt文件。单看每一…

2026/10/18 0:00:55 阅读更多 →
机器人大脑技术盘点:具身智能的感知、决策与数据闭环

机器人大脑技术盘点:具身智能的感知、决策与数据闭环

如果你的信息流最近也天天刷到“机器人大脑”这个词,你会发现一个很有意思的现象:每个人说的“大脑”根本不是同一个东西。有人指的是大语言模型,有人指的是运动控制系统,还有人指的是能理解物理世界的端到端模型。在2026年这个时…

2026/10/19 1:30:52 阅读更多 →

月新闻

我发现了一个新思路:用 Remotion + Claude Code 像写代码一样自动化生成短视频

我发现了一个新思路:用 Remotion + Claude Code 像写代码一样自动化生成短视频

/* MD / 富文本中的 .toc(含博客园搬家等嵌套结构);.toc-box 在侧栏,不受影响 */#content_views .toc,/* 编辑器常在目录前后插入空 p(:empty 仍占 20px),一并去掉避免顶空隙 */#content_views.markdown_views > p:empty:has(+ .toc),#content_views.markdown_views …

2026/10/19 2:54:50 阅读更多 →
Windows下 Codex 中 Chrome 和 Computer Use 插件不可用问题排查及解决参考方式:TaoToken 统一 Key 配置与验证

Windows下 Codex 中 Chrome 和 Computer Use 插件不可用问题排查及解决参考方式:TaoToken 统一 Key 配置与验证

/* MD / 富文本中的 .toc(含博客园搬家等嵌套结构);.toc-box 在侧栏,不受影响 */#content_views .toc,/* 编辑器常在目录前后插入空 p(:empty 仍占 20px),一并去掉避免顶空隙 */#content_views.markdown_views > p:empty:has(+ .toc),#content_views.markdown_views …

2026/10/17 17:22:31 阅读更多 →
黑夜航拍船只数据集训练YOLOV5模型全流程解析

黑夜航拍船只数据集训练YOLOV5模型全流程解析

/* MD / 富文本中的 .toc(含博客园搬家等嵌套结构);.toc-box 在侧栏,不受影响 */#content_views .toc,/* 编辑器常在目录前后插入空 p(:empty 仍占 20px),一并去掉避免顶空隙 */#content_views.markdown_views > p:empty:has(+ .toc),#content_views.markdown_views …

2026/10/18 12:16:16 阅读更多 →