OSPF Init stuck


Userlevel 2
Hello Community,

I'm in a odd journey trying to understand what's going on here.
There are two Extreme switchs connected by 2 10G ports running LACP.

The master port is UP and the member also is UP and everything is okay with LACP and OSPF between them.
But if the master port is disabled, the OSPF get stucked into Init state.

I tried to took off the port from the sharing and tried to solo running the ospf , but it didn't worked.

The stranger thing here is if that member port is in the sharing group it ran fine, without any loss.

What should I do? Any advices?

Thanks 🙂

12 replies

Userlevel 4
Hello Julian,

The issue looks like known bug - https://gtacknowledge.extremenetworks.com/articles/Solution/Local-multicast-traffic-is-not-egressing...

Best Regards,
Nikolay
Userlevel 2
Hey there,

So I'm using the version 16.1.3.6 16.1.3.6-patch1-11.

Now the port isn't on the LACP and the OSPF is not getting up.

Also did the clear igmp command to test but nothing happened.
Userlevel 4
perhaps it would help to post The relevant parts of the configuration?
perhaps tracing on both sides to make sure the hello's are seen at the port level then work up the stack from there?
Of course the GTAC is available as well as the fine folks on the HUB.
Userlevel 2
Hello Daniel,

What do you mean about port level? Is there a way to tpcdump that?

THanks
Userlevel 4
I would have to leave that to my EXOS teammates to comment on.
Userlevel 1
Is there any acl on port or vlan where ospf deployed? If yes, try to remove it.
Userlevel 2
newly vlan create to check that, problem still happening.
the switch has just one acl but is for another port to meter and shape a customer.
Userlevel 1
show me pls:

sh forw conf
sh conf | i to-cpu
Userlevel 2
Alexander Romanov wrote:

show me pls:

sh forw conf
sh conf | i to-cpu

Alexander,

Somehow the interface was with ipmcforwarding to-cpu off.
Enabling it solved the problem, thanks!
Userlevel 1
Alexander Romanov wrote:

show me pls:

sh forw conf
sh conf | i to-cpu

glad to help you.
Userlevel 4
Once an hello packet has been received, neighbor state will immediately transition from down to INIT state indicating that the hello packet was received but that the receiving router's ID was not the neighbor hello packet. In this state there is no bidi communication yet.

Once the router's ID is present in the hello packets, the neighbor state transitions to 2-WAY.
Check peers configuration accordingly.

Best Regards,
Nikolay
Userlevel 2
Necheporenko, Nikolay wrote:

Once an hello packet has been received, neighbor state will immediately transition from down to INIT state indicating that the hello packet was received but that the receiving router's ID was not the neighbor hello packet. In this state there is no bidi communication yet.

Once the router's ID is present in the hello packets, the neighbor state transitions to 2-WAY.
Check peers configuration accordingly.

Best Regards,
Nikolay

I'm receiving the hello from one side, but not for the other side.
There's a Bidi SFP+ connecting both switch and the ports are up.

Reply