OSPF fault-CodePudding

R1 old error can't own interface
S1 S2 can ping R1

CodePudding user response:

R1PING impassability interface, how can I understand?? Don't understand

CodePudding user response:

Problem description is not very clear, screenshots looked tired eyes

CodePudding user response:

Circle the two switch device of three OSPF can also ping ping R1 R1ping impassability switches blocked his mouth G01 and G02

CodePudding user response:

reference qq_41603506 reply: 3/f

the three devices on OSPF can ping two switches R1 R1ping impassability switches also can own G01 mouth and G02

111111111

CodePudding user response:

Qq_41603506

reference 4 floor response:

Quote: refer to the third floor qq_41603506 response:
the three devices on OSPF can ping two switches R1 R1ping impassability switches also can own G01 mouth and G02

111111111

1111111111

CodePudding user response:

You say so, do you have PING cannot, even through the mouth straight.. That is what you wrote? The traffic can go out?

CodePudding user response:

R1 no two switch routing flow can access the experimental requirements have become the R1 has been an error

CodePudding user response:

Based configuration done, suggest you put the first test is no problem to configure other configuration, or failure, because do not know what do you configured, so unable to determine the fault, but there is a question that a device ping different interface address, or physical interface port is up, or line fault, or suggest that you start to empty the configuration on the basic configuration,

CodePudding user response:

reference free heart on the eighth floor response:

based configuration done, suggest you put the first test is no problem to configure other configuration, or failure, because do not know what do you configured, so unable to determine the fault, but there is a question that a device ping different interface address, or physical interface port is up, or line fault, or suggest that you start to empty the configuration on the basic configuration,

R1 on MPLS VPN MP - BGP ISIS experiment succeeded is R1ping impassability and two switches

CodePudding user response:

references 9 f qq_41603506 response:

Quote: refer to the eighth floor of free inner response:
based configuration done, suggest you put the first test is no problem to configure other configuration, or failure, because do not know what do you configured, so unable to determine the fault, but there is a question that a device ping different interface address, or physical interface port is up, or line fault, or suggest that you start to empty the configuration on the basic configuration,

R1 on MPLS VPN MP - BGP ISIS experiment succeeded is R1ping impassability and two switches

https://b23.tv/BV1g7411u7SV/p26
I do really succeeded in the experiment of according to the video is a little problem on r1 do r1 is an error in the video but the teacher didn't tube can jump 5:28 there can see the error of r1

CodePudding user response:

Can see from the picture "xxer id conflict is detected on interface," I wonder if the Router id conflict, causes such as neighbors out of the question

CodePudding user response:

11 references Miaker response:

can be seen from the figure "xxer id conflict is detected on interface," I wonder if the Router id conflict, lead to neighbors out of the problems such as

Id is changed a few times to do this,,,,,,,

CodePudding user response:

refer to 12 floor qq_41603506 reply:

Quote: reference 11 floor Miaker response:
can be seen from the figure "xxer id conflict is detected on interface," I wonder if the Router id conflict, lead to neighbors out of the problems such as

Id has changed several times are so,,,,,,,

Change ID not restart the OSPF process yet, if you don't restart the process will not take effect