OSPF adjacency not forming when we create sub interfaces on Palo Alto

[srikanth]

Hi my OSPF adjacency is not working when i enable with a sub interface but works with physical interface.

Same is the case with QOS . Any help ?

Attached screenshots for your reference

[UhMayYeah]

Are the sub-interfaces untagged ? OSPF on un-tagged sub-interfaces  is not supported.

QOS can be applied on only physical egress interfaces.

-Ameya

[srikanth]

Hi ,

Yes the Sub interfaces are tagged in OSPF. Also we applied QOS on Physical interface. Its just that we created a wan interface for the internet traffic to move out.

In nut shell its something like this

eth1/2 - internal link flooding DHCP to end hosts

eth1/1.201 - external link going to internet

eth1/6.601 - configured with OSPF with a different router.

If I am not wrong QOS to be applied on egress links which is eth1/1 which is not working

eth1/6.601 routes are not visible.

Thanks

[licenselu]

Hello,

One possible reason why OSPF adjacency cannot be completed is MTU.

Check it on both devices...

Regards,

HA

[licenselu]

What I mean by MTU is MTU mismatch between OSPF  neighbor.

[srikanth]

We already did that. But no luck. How about QOS?

MTU are the same on both devices.

[das]

It works with the physical interface and not with the tagged sub-interface. Is the neighbor expecting the tag to be on the incoming hello packets?

[srikanth]

The neighbour is an untagged physical interface. We tried creating sub interface with the same tag at the other end as well. Still no luck.

How about QOS. Any idea why its showing that error?