03-06-2002 11:51 PM - edited 03-01-2019 08:46 PM
Is anyone familier with how hosts attached (via x.25) to the old BBN packet switches were able to obtain there addresses dynamicly ? They do it with the CALL REQUEST packet (utilizing an x.25 facility I believe). When they did this, it was the actual IP address of the packet switch port that they assumed as their own to communicate with other hosts.
I would like to find out if this can be done with the Cisco IOS (so I can replace a couple of old BBN packet switches) to support a couple of legacy hosts that do not allow for staticly assigning IP addresses. The software is proprietary so I am very limited as to what I can do with the host.
03-13-2002 12:51 AM
Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen
If anyone else in the forum has some advice, please reply to this thread.
Thank you for posting.
06-13-2017 12:13 AM
I just noticed this question doing an unrelated search. Though my answer is 15 years late, I thought I'd add this note to the memory hole.
What you seem to have is DDN X.25. Cisco was a leader in this in the early 1990s. This was IP over X.25 with a static mapping of IP address to X.121 address. The method is described in https://tools.ietf.org/html/rfc1236 and the command on the serial port is
encapsulation x25 ddn
There is a lot of quirkiness to X.25 config. In the extemely unlikely event that this system is still running a decade and a half later, you have options!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide