| |
This topic provides the information you need to develop a comprehensive migration strategy for your IPX internetwork.
HINT: Use this topic as a point of reference when planning and implementing the migration.
This topic includes the following sections:
This section explains how to determine how many internal and external network numbers are represented on the internetwork.
This section outlines the steps you follow to develop the migration strategy that best suits your internetwork.
This section gives general guidelines for migrating your internetwork.
The migration strategy you adopt depends primarily on the number of networks and servers on your IPX internetwork. To determine this number, enter
DISPLAY NETWORKS
The screen displays the internal network number of each server and the external network number of each IPX network that can be reached from the server. The total number of network numbers is displayed at the end of the list.
A small internetwork---one having fewer than 400 network numbers---is easy to migrate, especially if it comprises only NetWare servers and includes no third-party routers that do not support NLSP software. In this case, you can install NLSP on the servers in any order.
A large internetwork---one having 400 or more network numbers---should be partitioned into routing areas .
HINT: You should also consider reserving a contiguous block of IPX network addresses through the Novell Network Registry service.
For information about partitioning your internetwork and participating in the Novell Network RegistrySM, refer to Partitioning an Internetwork into Routing Areas.
How you migrate your internetwork depends on the following characteristics:
This section provides a set of tasks that helps you determine what you need to do to migrate your internetwork. Each step directs you to complete a task and refers you to a section in this guide for specific instructions. The number of sections to which you must refer depends largely on the topological complexity of your internetwork.
To plan your migration strategy, complete the following tasks:
Routing areas provide a manageable hierarchy and preserve routing efficiency in large IPX networks. For further instructions, refer to Partitioning an Internetwork into Routing Areas.
In particular, NetWare 2 servers require special consideration because of their dependence on IPX RIP and SAP broadcasts. For further instructions, refer to Migrating an Internetwork with Different NetWare Versions.
Like NetWare 2, these products depend on RIP, SAP, or both. For further instructions, refer to Migrating an Internetwork with Products That Require RIP and SAP. This includes WAN connections using either Novell multiprotocol routing software or third-party routers that do not currently support NLSP. For further instructions, refer to Migrating an Internetwork with WAN Connections or Third-Party Routers. Some third-party routers do not currently support NLSP. For NLSP to interoperate with these routers, you can use a combination of IPX header compression and IP encapsulation (tunneling), or continue to use IPX RIP and SAP to interconnect the routers. For further instructions, refer to Migrating an Internetwork with WAN Connections or Third-Party Routers.
This section offers guidelines to help your migration progress smoothly.
IMPORTANT: To maintain connectivity between LANs during migration, do not disable RIP routing on any interface until you have installed NLSP on every system.
Because NLSP is fully compatible with RIP and SAP, you can migrate your NetWare LANs as needed; you do not need to migrate your entire internetwork at the same time.
Use the following guidelines if you need to partition your internetwork into routing areas:
Define the routing areas first. For information, refer to Guidelines to Follow When Defining Routing Areas.
Migrate the core routers first, then migrate one LAN at a time. Core routers are typically those that form the network backbone or share a high-speed transit LAN. For information, refer to the examples in Defining Routing Areas in an Internetwork.
If you do not need to partition your internetwork into routing areas, refer to the remaining topics in this section, as necessary, to migrate your internetwork.
If your internetwork has fewer than 400 network numbers and uses no WAN connections or routers that do not support NLSP, install NLSP on the NetWare servers or dedicated routers in any order.
| |