Migrating from IPX to IP in NetWare 5.1 - Page 2

 By Drew Bird
Page 2 of 2   |  Back to Page 1
Print Article

On both the workstation and the server, removing CMD support is as easy as unloading the driver.

Providing access to IPX-dependent services is one benefit of CMD; but if you're considering a phased approach to a pure IP environment, CMD's other functions will be of more interest. By using CMD, it is possible to configure a server to act as a gateway between an IP-only network segment and an IPX-only network segment. In this configuration, known as Migration Agent, the server with CMD running encapsulates and decapsulates packets to and from IPX and IP as required, providing access from all machines, to all machines, regardless of whether IPX or IP is being used. In addition to connecting two separate segments, CMD also makes it possible to have IP-only and IPX-only clients on a single network segment--again, by acting as a gateway between the two protocols.

A further feature of CMD is its ability to be configured in Backbone mode, which allows IPX information to be encapsulated into IP for transmission on links that do not support IPX traffic. This approach lets you use an IP backbone between two remote sites, while preserving the IPX configuration on LANs.

For more information, visit the NetWare 5.x homepage.


CMD gives those introducing a pure IP environment the luxury of knowing that you don't need to adopt an all-or-nothing approach to migration. Even if you only use CMD as a transition measure, the ease with which it can be configured and removed makes it a key tool during this process. //

Drew Bird (MCT, MCNI) is a freelance instructor and technical writer. He has been working in the IT industry for 12 years and currently lives in Kelowna, BC., Canada. You can e-mail Drew at drew.bird@tecmetrix.com.

This article was originally published on Jan 16, 2001
Get the Latest Scoop with Networking Update Newsletter