CCNA Cisco Certified Network Associate Study Guide - FTP Server

Introduction to Novell IPX 397
Sometimes—and only sometimes—you can intentionally have multiple
frame types present on the same network. Typically, you’ll start working in
an environment that already has all frame types configured—usually because
the administrator didn’t know what to do and just configured all available
frame types on all router and servers, as shown in Figure 8.3.
FIGURE 8.3 Multiple frame types on a single Ethernet segment
Ethernet_802.2
Novell Server A
Workstation 1
Ethernet_II
Ethernet_802.3
Novell Server B
Workstation 2
Ethernet_802.2
Ethernet_II
Novell Server C
Workstation 3
Ethernet_802.3
Each frame type in Figure 8.3 has a unique IPX network address. Even
though there’s a single Ethernet segment, there are three virtual IPX networks
and, therefore, three unique IPX network addresses. Each network
will be broadcast across the internetwork every 60 seconds.
In Figure 8.3, Workstation 1 can communicate only with Server C
because they’re both running Ethernet_II. Workstation 2 can communicate
only with Server A, and Workstation 3 can communicate only with Server B.
But what if you wanted all the workstations to communicate with all the
servers—what would you do? You can add a router that supports all frame
types, or you can add more frame types to each server. Adding a router
would allow any workstation to communicate with any of the servers, but
that router would have to route all packets among all the servers and clients
with dissimilar frame types. Adding multiple frame types to servers and routers
is not a good solution. It’s best to have one frame type, probably 802.2,
in your internetwork. However, NetWare 5 runs a native IP, so all this is
irrelevant unless you have to support older servers.