Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 559
  • Last Modified:

Nortel to Cisco Wan Link

I have a nortel Router in one site runing LLC, IP and ospf. I need to put a cisco at the other end of the Wan link. I have verfied that the T1 is good by having 2 Cisco's at each end and 2 nortel routers on the ckt. when i mix the rotuers i have can not get the circuirt up and running. I have configured both ends with IP and the proper subnet.
enc PPP

I am not sure where to go from here.
  • 3
  • 2
1 Solution
If you are using ppp encapsulation, on the Cisco side, try setting the serial interface mtu to 1492 to match the Nortel
JaysonJacksonAuthor Commented:
Tried setting the MTU to 1492 no line still down. I belive the LLC layer is not comming up and i am not sure why.
Don JohnstonInstructorCommented:
It's been awhile since I worked with a Nortel router (actually, they were called Bay routers back then :-)). but I recall them having two serial encapsulations Standard (which was Bay's HDLC) and PPP. When we connected a Bay to a Cisco using serial links, we set the interfaces to PPP on both ends.

When Nortel acquired Bay, did they change the terminology and now they're refering to PPP as LLC?

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Found this on a nortel FAQ site. I had the MTU adjustment at the wrong end. Agree w/Don that you need a common encapsulation at both ends
How do I get a Bay to talk to a Cisco on a Pt-Pt line?
last updated: 5/18/1999

A. Both Cisco & Bay default to a proprietary HDLC on WAN circuits. So, they won't talk to each other by default.

However, you can use PPP, which is an RFC standard WAN protocol, and get them to communicate.

Hang on a minute, first. You also have to change the default MTU sizes.

Bay defaults to 1600 bytes and Cisco defaults to 1500. Also, Bay doesn't include the datalink header in its MTU count. So, you should set the Bay's MTU to 1506 and leave the Cisco to it's default.

Test it by sending a 2000-byte ping through. If it works, then the MTU size is fragmentting correctly.

If you need clocking, then let the Cisco provide it.

JaysonJacksonAuthor Commented:
This work with a little more research but this pointed me in the correct direction.
What was your final thing that made it work?

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now