Hey all, I'm having a strange issue here with a site not establishing isis adjacency.
We have an almost all private mpls network running is-is . We have a few sites that are remote and we got a mesh circuit setup from a provider. One site we added to the circuit is not getting routes or adjacency with the rest of the sites on the circuit. The config is correct as it's the same template for the other sites as well. We are running Nokia 7705 platform.
When showing adjacency on the problem site, it sees the other sites in the mesh but they are all in initialize state. The other sites in the mesh do not see the new site in their adjacency tables. The logs show ldp sessions are in service and shows the adjacent nodes begin initializing but that's it. I've had the carrier(well 3 carriers total after all their hand-offs) verify the MTU and they say it is correct. They say they see traffic in both directions but very little. The end carrier had the vlan encapsulation wrong at first and I didn't see any anything in our adjacency table. When they fixed the encapsulation the adjacencies appeared in the init state. The port is discarding packets but not sure why.
The port on our router is a hybrid port tagged 2001 with dot1q encap and an MTU of 1576.
I've tried moving from a SFP port with a copper connection to a straight copper port and configured that port and it didn't change. The end carrier equipment is a zhone device that looks like a junk residential device which is different than the usual RAD equipment provided at the other sites..they are convinced the issue is on my end now. I'm no expert so I'm looking for some things to look at.. thanks
No comments:
Post a Comment