ASN OSPF Compatibility Problem

[Googer]

I am trying to get OSPF to talk between our existing ASN router and a new Adtran 1224R router. The Adtran works fine with another Adtran and with our Passport 8600. The ASN works fine with the Passport 8600 and is also working well with an ARN router. The problem seems to be on the ASN side as it does not detect that it is receiving Hellos from the Adtran, however I have confirmed that these are being sent and received. The Adtrans sees the Hello packets from the ASN and shows it as a neighbor. I get the following message in the log of the ASN.

630: 05/12/2005 07:09:22.421 TRACE SLOT 1 PPP Code: 51
Sending Protocol-Reject for protocol 0x2145 on circuit 3.

I have called this in to support but so far their only suggestion was to turn off BOFL on the PPP link. Needless to say that did nothing useful.

Any help would be appreciated.

Thanks,

Googer

 

[Alainv]

As far as i can see it, you have problems with the ppp negotiations and not with ospf...probably chap problems (lcp options)
Is the connection with the arn also using ppp? or directly connected with ethernet as the 8600?
is your ip link up?
And if ospf is the problem, you still must be able to ping the neighbour.
try to ping and specify the source address with the -a options on the asn.

 

[Googer]

I have full PPP connectivity. The PPP curcuit is fully funcitonal and both routers can ping each other without any problem. The only thing now working is OSPF. If I put in static routes it works fine and if I switch to RIP it works fine.

Why ping and specify the IP?

Googer

 

[Alainv]

then the error command you gave was not in relation with your problem.
why ping and specify the address....if ospf ain't working, and if you log into the box, the opposite site has problems with returning the packet...but since static routing works...
OSPF doesn't come up, what is the status of ospf?
Do they see eachother?
are they staying in init phase?
If ospf is configured, and when it sees an ospf packet, something must come into the log file.
Perhaps db loggings and that normally means that you have mtu problems. If that happens change you ospf mtu size.


If it stays in init phase, perhaps the address resolutions isn't working fine, so add an adjacency...

A

 

[dane775]

From Site Manager Select --> Protocols --> IP --> OSPF --> Interfaces --> MTU Size (at the bottom).

If it's set to 1, change it to 2...(limits MTU to 1500) I've seen this fix problems with Nortel router's forming an adjacency with Adtran routers.

 

[dane775]

*wonders what version of code you're running*

 

[Googer]

I finally tracked this down useing some PCAP/TAP data. It turns out the Adtran router does not use a standard OSPF packet when sending OSPF over PPP. Adtran has acknowledged this is their problem and their developers are working on a patch for this problem. The non-standard packet was the reason the Nortel router was rejecting the packets.

Googer

 

[dane775]

If you have trouble bringing it up after the patch, check MTU. We had problems with Adtrans talking to ASNs and BCNs, changing MTU fixed it.

Did they give you any specfics on the "non-standard" packets??

 

[Googer]

No nothing specific from Adtran. I did try adjusting the MTU size already though and that did not fix the problem.

Thanks,

Googer

 

[Googer]

I did get an update from Adtran on this. They have run into this problem before with Nortel Shasta products and it has to do with the way PPP is handled. They fixed the problem on the Shasta and are now working on fixing it for the ASN/BayRS routers.

Googer

 

[Googer]

Update. Adtran came out with a patch that fixes this problem.


Googer

 

[dane775]

Cool...

Are you operational at this point? Or still waiting for the patch??