IPX Routing

This chapter provides guidelines and other key information about how to implement Internet Packet Exchange (IPX) protocol routing on Multilayer Switching Modules. The chapter covers these topics:

• IPX Routing Overview

• Key Concepts

• Key Guidelines for Implementation

• IPX Interfaces

• IPX Routes

• IPX Servers

• IPX Forwarding

• IPX RIP Mode

• IPX SAP Mode

• IPX Statistics

• Standards, Protocols, and Related Reading

After you log in to the system and connect to a slot that houses a Multilayer Switching Module, you can manage IPX routing features from the ipx menu of the Administration Console. See the Switch 4007 Command Reference Guide.

The management interfaces display "cb9000" and refer to the Management Module as the Enterprise Management Engine (EME) because the heritage of the Switch 4007 is the CoreBuilder^® 9000 switch.

You can route packets from your system to an external destination using the Internet Packet Exchange (IPX) protocol. The IPX protocol is a NetWare LAN communications protocol that moves data between servers and workstation programs that are running on various network nodes. IPX is a User Datagram Protocol (UDP), which is used for connectionless communications. IPX packets are encapsulated and carried by Ethernet packets and Token Ring frames.

Figure 58 shows the relationship of the IPX protocol to the Open System Interconnection (OSI) reference model.

Figure 58 IPX Protocol in the OSI Reference Model

Features

Using the IPX protocol to route packets, you can create and support:

• IPX interfaces

• IPX routes (primary and secondary)

• IPX servers (primary and secondary)

• IPX forwarding

• IPX RIP mode

• IPX SAP mode

You can use IPX routing to:

• Provide services for connectionless communications.

• Reduce the cost of equipment moves, upgrades, and other changes and simplify network administration.

• Create VLAN-to-IPX interfaces to create virtual workgroups with most of the network traffic staying in the same IPX interface broadcast domain.

• Help avoid flooding and minimize broadcast and multicast traffic.

This section explains how IPX routing works and provides a glossary of IPX routing terms.

How IPX Routing Works

To route packets using the IPX protocol, take these general steps:

1 .   Define an IPX protocol or a virtual LAN (VLAN) with a grouping of ports.

2 .   Define an IPX routing interface.

3 .   Decide which IPX route and server options you want to use and select these options from the Administration Console.

4 .   Enable IPX forwarding.

The IPX routing interface defines the relationship between an IPX VLAN and the subnetworks in the IPX network.

Each IPX VLAN interface is associated with a VLAN that supports IPX. The Multilayer Switching Module has one interface defined for each subnetwork to which it is directly connected.

A router operates at the network layer of the Open Systems Interconnection (OSI) Reference Model. The router receives instructions to route packets from one segment to another from the network-layer protocol. IPX, with the help of the Routing Information Protocol (RIP), performs network-layer tasks, including:

• Addressing packets

• Routing packets

• Switching packets

An IPX packet consists of a 30-byte header followed by packet data. The packet header contains network, node, and socket addresses for both the destination and the source.

Figure 59 shows the IPX packet format.

Figure 59 IPX Packet Format

The IPX packet contains the following elements:

• Checksum - A 16-bit checksum that is set to 1s.

• Packet length - A 2-byte field that indicates the packet's length in bytes. This length includes both header and data. The length must be at least 30 bytes.

• Transport control - A 1-byte field that indicates how many routers a packet has passed through on its way to its destination. Packets are discarded when this value reaches 16. A network node sets this field to 0 before sending the IPX packet.

• Packet type - A 1-byte field that specifies the upper-layer protocol that receives the packet.

• Destination network - A 4-byte field that contains the network number of the destination node. When a sending node sets this field to 0, the system routes the packet as if the sending and destination nodes were on the same local segment.

• Destination node - A 6-byte field that contains the physical address of the destination node.

• Destination socket - A 2-byte field that contains the socket address of the packet's destination process.

• Source network - A 4-byte field that contains the source node network number. If a sending node sets this field to 0, the source's local network number is unknown.

• Source node - A 6-byte field that contains the source node, physical address. Broadcast addresses are not allowed.

• Source socket - A 2-byte field that contains the socket address of the process that transmitted the packet.

• Packet data - A field that contains information for upper-layer network processes.

Successful packet delivery depends both on proper addressing and on the network configuration. The packet's Media Access Control (MAC) protocol header and IPX header address handle packet addressing.

The sending node must have the destination's complete network address, including the destination network, node, and socket. After the sending node has the destination address, it can address the packet.

However, the way the IPX packet's MAC header is addressed depends on whether a router separates the sending and destination nodes.

Figure 60 shows an example of IPX format routing.

Figure 60 IPX Packet Routing

Sending Node's Responsibility

When sending and destination nodes have the same network number, the sending node addresses and sends packets directly to the destination node. If sending and destination nodes have different network numbers, as in Figure 60, the sending node must find a router on its own network segment that can forward packets to the destination node's network segment.

To find this router, the sending node broadcasts a RIP packet, requesting the best route to the destination node's network number. The router on the sending node's segment that has the shortest path to the destination segment responds to the RIP request. The router's response includes its network and node address in the IPX header. After the sending node determines the intermediate router's address, it can send packets to the destination node.

If the sending node is a router rather than a workstation, the node's internal routing tables supply the destination's network location. The destination router does not need to broadcast a RIP request.

Router's Responsibility

A router handles a received IPX packet in one of two ways:

• If the packet is destined for a network number to which the router is directly connected, the sending router:

  • Places the destination node address from the IPX header in the destination address field of the packet's MAC header

  • Places its own node address in the source address field of the packet's MAC header

  • Increases the transport control field of the IPX header by 1 and transmits the packet on the destination node segment

• If the packet is destined for a network number to which the router is not directly connected, the router sends the packet to the next router along the path to the destination node. The sending router:

  • Looks up the node address in the routing information table of the next router and places the address in the destination address field of the packet's MAC header

  • Places its own node address in the source address field of the packet's MAC header

  • Increments the transport control field in the IPX header and sends the packet to the next router

Review the following IPX routing terms that are used extensively throughout this chapter:

• Address - Unique 4-byte network address of a segment that is located in your Multilayer Switching Module's routing table.

• Age - The time in seconds since the network's last update.

• Cost - A number between 1 and 65534 that the system uses to calculate route ticks. Assign a cost of 1 to each IPX interface unless your network has special requirements like the need for redundant paths.

• Frame formats - Frame encapsulation format.

• Hops - The number of routers that must be crossed to reach a network segment.

• Interface - The system-assigned number for an IPX interface.

• NetBIOS protocol - Network Basic Input Output System protocol. An application programming interface (API) that adds special functions for PC-based LANs.

• Node - The node address of the router that can forward packets to each network segment (when this is set to all 0s, the router is directly connected).

• RIP - Routing Information Protocol. Allows the exchange of routing information on a NetWare network. IPX routers use RIP to create and maintain their dynamic routing tables.

• SAP - Service Advertisement Protocol. Provides routers and servers that contain SAP mode agents with a means of dynamically exchanging network service information.

• Ticks - An estimate of the time that is necessary to reach a network segment. One second is 18.21 ticks.

• VLAN interfaces - Your Multilayer Switching Module's point of attachment to a given VLAN. A VLAN interface exists entirely within a given IPX interface.

Consider the guidelines in this section when you configure your Multilayer Switching Module for IPX routing.

Procedural Guidelines

Complete the following steps to set up IPX routing on your Multilayer Switching Module:

1 .   Set up your VLAN interfaces.

2 .   Define the IPX interfaces before you define the routes and servers.

3 .   Define routes.

4 .   Define servers.

5 .   Select RIP or SAP, if you plan to use them.

6 .   Define IPX forwarding.

See the Command Reference Guide for commands that you use for these steps.

General Guidelines

Consider the following general guidelines before you configure IPX routing on your Multilayer Switching Module:

• Every IPX interface has one IPX VLAN and other associated information.

• The IPX router has one IPX interface defined for each network to which it is directly connected.

• Before you define an associated IPX interface for a network, you must first define a VLAN. See Chapter 14.

• The IPX router has one IPX interface defined for each network to which it is directly connected.

An IPX interface has the following information associated with it:

• IPX network address - A 4-byte address that you assign. Make each address unique within the network.

• Cost - A number between 1 and 65534 that the system uses to calculate route ticks. A tick is an estimate of how long it takes a packet to reach a network segment. One tick is approximately 1/18 of a second (there are 18.21 ticks in a second). Assign a cost of 1 to each IPX interface unless your network has special requirements like the need for redundant paths.

• Encapsulation format - Formats that IPX routing uses: Ethernet Type II, Novell 802.3 Raw, 802.2 LLC, and 802.3 SNAP

• State - The status of the IPX interface. The IPX interface status can be up (available for communication) or down (unavailable for communication).

• VLAN interface index (VLAN index) - The VLAN that is associated with a IPX interface. When the system prompts you for this option, it indicates the available VLAN indexes.

Consider the following guidelines when you set up an IPX interface:

• The first line in an interface display indicates whether:

  • IPX forwarding is enabled

  • IPX RIP mode is active

  • IPX RIP mode triggered updates are enabled

  • IPX SAP mode is active

  • IPX SAP triggered updates are enabled

  • The secondary route/server option is enabled on the system

• An IPX interface defines the relationships among an IPX VLAN, the IPX router, and the IPX network. The IPX router has one IPX interface defined for each network to which it is directly connected.

• When you define an IPX interface, you define:

  • IPX address

  • Cost

  • Format

  • Associated IPX VLAN index

• Before you define the IPX (routing) interface, you must define a VLAN and select IPX, IPX-II, IPX-802.2, IPX-802.2 LLC, or IPX-802.3-SNAP as the protocol to be supported by the VLAN. See Chapter 14 for information about creating VLANs.

• Unless your network has special requirements, such as the need for redundant paths, assign a cost of 1 to each interface and do not modify this setting.

• When you modify an IPX interface, you can change its:

  • IPX address

  • Cost

  • Format

  • Associated IPX VLAN index

• If you use the OddLengthPadding feature (10 MB switching modules support only), make sure that you select only those interfaces that require odd-length padding. If you enable this option for every interface, network performance is degraded.

For more detailed information that explains how to create an IPX interface, see the Switch 4007 Command Reference Guide.

Per-Interface Options

You can set the NetBIOS and OddLengthPadding options on each interface. For details about how to use these options, see the Administering IPX Routing chapter in the Command Reference Guide.

NetBIOS Option

This option determines whether the system handles IPX Type 20 packet forwarding.

OddLengthPadding Option

This option only supports 10 MB switching modules. To provide a compatibility mode for older network interface cards (NICs), it enables an interface to pad IPX packets that have an odd number of bytes. (Older NICs discard IPX packets that have an odd number of bytes.)

Your system maintains a table of routes to other IPX networks. You can:

• Use RIP mode to exchange routing information dynamically.

• Use the Administration Console to make static entries in the table.

Consider the following guidelines when you set up an IPX route:

• The first line in the output (the status line) indicates whether:

  • IPX forwarding is enabled

  • IPX RIP mode is active

  • IPX RIP mode triggered updates are enabled

  • IPX SAP mode is active

  • IPX SAP triggered updates are enabled

  • The secondary route/server option is enabled on the system

• The route table display shows the range for routing table Primary entries in the N-M format, where N is the current number of entries and M is the maximum number of Primary entries.

• A Secondary route entry can replace a Primary route entry when the Primary route is removed from the routing table for any reason (for example, if the route reaches its age limit).

• To view entries for any Secondary routes:

  • Establish alternate paths to the same IPX network.

  • Enable the IPX Secondary route/server option.

• The maximum number of hops, or routers that a packet can cross, is 16, except for NetBIOS packets, which can cross no more than 7 routers.

• Before you define static routes on your system, you must define at least one IPX interface.

• Static routes remain in the routing table until you remove them or until you remove the corresponding interface.

• If an interface goes down, routes are temporarily removed from the routing table until the interface comes back up.

• Static routes take precedence over dynamically learned routes to the same destination. You can have a maximum of 32 static routes.

• When you use the ipx route remove option to remove a route, that route is immediately removed. All servers that depend on the removed route are also removed from the Server Information Table, including all static servers.

• When you use the ipx route flush option to remove dynamically learned routes from the IPX routing table, all dynamically learned routes are removed immediately. All dynamic servers that depend on these routes are also removed from the Server Information Table.

You can set up both Primary and Secondary routes in the routing table.

To set up routes in the routing table, see the IPX routing chapter in the Switch 4007 Command Reference Guide.

Static Routes

You manually configure a static route. Static routes are useful in environments in which no routing protocol is used or in which you want to override a routing protocol's generated route.

Static routes do not change until you change them, and they do not time out. Because static routes do not change in response to network topology changes, manually configure only a small number of reasonably stable routes.

Dynamic Routes Using RIP

A router uses RIP to exchange its routing table with other routers at regular intervals. This automatic method of learning routes helps you keep up with a changing network environment and allows you to reconfigure routes quickly and reliably. Interior Gateway Protocols (IGPs), which operate within intranetworks, provide this automated learning. The system uses RIP (one of the most widely used IGPs) to dynamically build routing tables.

RIP operates with active and passive network devices. Active devices, usually routers, broadcast their RIP messages to all devices in a network; they update their own routing tables when they receive a RIP message. Passive devices, usually hosts, listen for RIP messages and update their routing tables; they do not send RIP messages. On your system, you select a RIP mode to determine how RIP operates, as described in "IPX RIP Mode" later in this chapter.

An active router sends a RIP message every 60 seconds. This message contains both the network number for each destination network and the number of hops to reach it. In RIP, each router through which a packet must travel to reach a destination counts as one network hop.

Routing Tables

A routing table collects information about all intranetwork segments. This table allows a router to send packets toward their destinations over the best possible routes.

The table contains an entry for every network number that the router knows about. The router uses this information when the router is not directly connected to a packet's destination network. The routing information table provides the address of another router that can forward the packet toward its destination.

The routing table consists of the following elements:

• Interface - The interface number of the router that is used to reach a network segment

• Address - The network segments that the router knows about

• Hops to network - The number of routers that must be crossed to reach a network segment

• Ticks to network - An estimate of the time that it takes to reach a network segment. There are 18.21 ticks in a second.

• Node - The node address of the router that can forward packets to each network segment. When the node is set to all 0s, the router is directly connected.

• Age - The time since the network's last update

Figure 61 shows an example of a typical routing information table.

Figure 61 Sample Routing Table

The routing information table is updated statically or dynamically.

Selecting the Best Route

Large networks contain many possible routes to each destination. A router performs the following steps to find the best route toward a destination:

• If one route requires the lowest number of ticks, the router selects it as the best route.

• If multiple routes require the same lowest number of ticks, the router selects the route that requires the lowest number of hops as the best route.

• If multiple routes require the same lowest number of ticks and hops, the router may select any of them as the best route.

Your system creates and maintains a server information table that lists all the servers that reside on other IPX networks. You can:

• Use SAP to exchange server information dynamically

• Make static entries in the server table

Consider the following guidelines when you set up an IPX server:

• The first line in the output (status line) indicates whether:

  • IPX forwarding is enabled

  • IPX RIP mode is active

  • IPX RIP mode triggered updates are enabled

  • IPX SAP mode is active

  • IPX SAP triggered updates are enabled

  • The secondary route/server option is enabled on the Multilayer Switching Module

• Static servers remain in the table until you:

  • Remove them

  • Remove the corresponding interface

  • Remove the route to the corresponding network address

• A static server must have an IPX network address that corresponds to a configured interface or to a static route. If an interface goes down, any static servers on that interface are removed from the server table until the interface comes back up.

• Static servers take precedence over dynamically learned servers to the same destination. You can have a maximum of 32 static servers.

• Before you define static servers on the system, first define at least one IPX interface.

• When you use the ipx server remove option to remove a server, that server is immediately removed from the Server Information Table.

• When you use the ipx server flush command to remove all dynamically learned servers, all dynamically learned servers are immediately removed from the Server Information Table.

You can set up both Primary and Secondary servers in the server table. Secondary servers serve as a backup to the Primary server set up on the same IPX server.

To set up Secondary servers on your system, see the Switch 4007 Command Reference Guide.

Static Servers

Static servers are useful in environments in which no routing protocol is used, or when you want to override some of the servers that generated with a routing or server protocol. Because static servers do not automatically change in response to network topology changes, manually configure only a small number of relatively stable servers.

Dynamic Servers Using SAP

Servers are automatically added to and removed from the information table through SAP. This automatic SAP update helps you keep up with changing network environments and allows servers to advertise their services and addresses quickly and reliably.

As servers boot up, they advertise their services. When servers are brought down, they use SAP to broadcast that their services are no longer available.

Client systems do not use this server information directly. Instead, SAP agents within each router on the server's network segment collect this information. The SAP agents store the information in their server information tables. Client systems then contact the nearest router or file server SAP agent to obtain server and service information.

On your system, you select a SAP mode to determine how SAP operates, as described in "IPX SAP Mode" later in this chapter.

Maintaining Server Information

When a router's SAP agent receives a SAP broadcast response indicating a change in a server's configuration, the agent updates its server information table and informs other SAP agents. Examples of such a change are when a server is disconnected or becomes accessible through a better route.

The SAP agent immediately sends an update broadcast to all directly connected network segments except the segment from which the information was received. All future periodic broadcasts contain the change information.

SAP Aging

Router SAP agents use a special aging mechanism to deal with a SAP agent that goes down suddenly without sending a DOWN broadcast. A hardware failure, power interruption, or power surge can cause this situation.

Each SAP agent maintains a timer for each entry in its server information tables. The timer tracks the elapsed time since this entry has been updated. This information is either new or changed, and the SAP agent immediately passes it on. Changes are quickly captured and stored throughout the intranetwork.

SAP Request Handling

When a SAP agent receives a general request, it notifies the sending source about all servers known to the agent. This response includes the same information that is sent out in periodic SAP broadcasts. When the request is specific, the SAP agent notifies the sending source about all servers of the requested type.

Server Tables

Server information tables contain data about all active servers on the intranetwork. SAP agents use these tables to store information received in SAP broadcasts. Server tables are dynamically and statically created.

Figure 62 shows an example of a Server Information Table.

Figure 62 Sample Server Information Table

This table contains the following data:

• Interface - The interface from which server information is received

• Server name - The name of the server

• Server type - The type of service that the server provides

• Network address - The address of the network that contains the server

• Node address - The server's node address

• Socket address - The socket number through which the server receives service requests

• Hops to server - The number of intermediate networks that must be crossed to reach the server

• Age of server - The time in seconds since the server's last table update

You can control whether the system forwards or discards IPX packets with the ipx forwarding option.

Important Considerations

Consider the following guidelines before you use the ipx forwarding option:

• When you enable ipx forwarding, the Multilayer Switching Module acts as a normal IPX router. It forwards IPX packets from one network to another when required.

• When you disable ipx forwarding, the Multilayer Switching Module discards all IPX packets.

You can exchange routing information on a NetWare network with the ipx rip mode option. This option selects the IPX RIP mode that is appropriate for your network and selects the routers that use RIP mode to create and maintain their dynamic routing tables.

In ipx rip mode, one router exchanges routing information with a neighboring router. When a router discovers any changes in the network layout, it broadcasts this information to any neighboring routers. IPX routers also send periodic RIP broadcast packets that contain all routing information. These broadcasts synchronize all routers on the network and age those networks that might become inaccessible if a router is abnormally disconnected from the network.

Important Considerations

Consider the following guidelines before you use the ipx rip mode option:

• The system has three RIP modes:

  • Off - The system processes no incoming RIP packets and generates no RIP packets of its own.

  • Passive - The system processes all incoming RIP packets and responds to RIP requests, but it does not broadcast periodic or triggered RIP updates.

  • Active - The system processes all incoming RIP packets, responds to explicit requests for routing information, and broadcasts periodic and triggered RIP updates.

• The system has two RIP triggered modes:

  • Disabled - Broadcasts IPX routes 3 seconds after learning them.

  • Enabled - Broadcasts IPX routes immediately after learning them.

Each router maintains a table of current routing information (the routing table). The routing protocols receive or advertise routes from the network. RIP policies control the flow of routing information among the network, the protocols, and the routing table manager.

Routing policies allow you to define:

• The import policies that specify which routes the router places into the routing table.

• The export policies that specify the routes that the router propagates to the network.

• Import/export policies for each peer.

Before the router adds a route to the routing table, it follows these steps:

• The protocol receiving the route forwards the route to the routing table manager.

• The routing table manager compares the route to the import policy to determine whether to accept or drop the route.

• If the routing table manager accepts the route, it stores the route in the routing table.

The default import policy is none; that is, the router places all routes into the routing table.

RIP Export Policies

At certain times, such as when the routing table changes, the protocol asks the routing table manager for routes to advertise to other routers. The routing table manager follows these steps:

• It compares the route to the export policy to determine whether to advertise the route to the network.

• If it accepts the route, the manager propagates it to the network.

The default import policy is none; that is, the router advertises all routes in the routing table.

RIP Policy Parameters

These parameters define SAP policies:

Policy type - Import (apply the policy to received services) or Export (apply the policy to advertised services).

Route origin - The origin of the route for this policy if it is an export policy: static, RIP, or all.

Route - An IPX network address that specifies the route that applies to this policy.

Interface - One or more IP interfaces on this router that are associated with the RIP policy.

Source Node Address - The MAC address of the router that can forward packets to the network.

Action - Whether this router accepts or rejects a route that matches the policy.

Metric - Increase or decrease a route metric by a value that you specify. This parameter is valid only if the Policy Action is set to Accept (import policies).

To change the route metric of an export policy, you must adjust the metric of the import policy on the receiving router.

Weight - The metric value of this policy. This parameter specifies the order of precedence for policies that match the same route. A higher value takes precedence over a lower value.

IPX SAP provides routers and servers that contain SAP mode agents with a means of exchanging network service information. Through SAP, servers advertise their services and addresses. Routers gather this information and share it with other routers. With this process, routers dynamically create and maintain a database (server table) of network service information. Clients on the network determine what services are available and obtain the network address of the nodes (servers) where they can access those services. Clients require this information to initiate a session with a file server.

You determine how SAP operations on your system with the ipx sap mode option.

Important Considerations

Consider the following guidelines before you use the ipx sap mode option:

• The Multilayer Switching Module has three SAP modes:

  • Off - The system does not process any incoming SAP packets and does not generate any SAP packets of its own.

  • Passive - The system processes all incoming SAP packets and responds to SAP requests, but it does not broadcast periodic or triggered SAP updates.

  • Active - The system processes all incoming SAP packets, responds to explicit requests for routing information, and broadcasts periodic and triggered SAP updates.

• The system has two SAP triggered modes for updates:

  • Disabled - Broadcasts IPX SAP server addresses 3 seconds after learning them.

  • Enabled - Broadcasts IPX SAP server addresses immediately after learning them.

Each router maintains a table of current configured services (the service table). SAP receives information and advertises information about the network nodes that provide these services. SAP policies control which services the router places in the service table and advertises to the network.

SAP Import Polices

Each time the router receives an advertised service, it compares the services to the import polices to decide whether to add the service to the service table or drop it. If the router accepts the service, the router adds it to the service table.

The default import policy is none; that is, the router places all services into the service table.

SAP Export Policies

At certain times, such as when a router is started up or shut down, SAP advertises services to other routers. Each time the router prepares to advertise the service, it compares it to the export policies to decide whether to advertise the service. If the export policy does not prohibit the service, the router sends it out.

The default export policy is none; that is, the router advertises all services.

SAP Policy Parameters

These parameters define SAP policies:

• Policy type - Import (apply the policy to received services) or Export (apply the policy to advertised services).

• Route origin - The origin of the service for this policy, if it is an export policy: static, SAP, or all.

• Service type - The Novell standard 6-digit hexadecimal number that represents the type of service offered by the server. For details, consult your Novell documentation. Refer to the Command Reference Guide for a list of common service types.

• Server name - The name of the server providing the services.

• Network address - The IPX network address of the network on which the server resides.

• Node address - The 6-byte MAC address of the router that can forward packets to the network.

• Interfaces - One or more IP interface index numbers associated with this policy.

• Action - Whether this router accepts or rejects a service that matches the policy.

• Weight - The metric value that is associated with this policy. This parameter specifies the order of precedence for policies that match the same service. A higher value takes precedence over a lower value.

You can view the following IPX statistics on your system:

• IPX summary statistics

• IPX RIP statistics

• IPX SAP statistics

• IPX forwarding statistics

• IPX interface statistics

In the display, the status line indicates whether:

• IPX forwarding is enabled

• RIP mode is active

• RIP mode triggered updates are enabled

• SAP mode is active

• SAP mode triggered updates are enabled

• The secondary route/server option is enabled

See the Command Reference Guide for more information about IPX statistics.

The following standards and protocols apply when you use IPX to route packets on your system:

• IEEE 802.2

• IEEE 802.2 LLC

• IEEE 802.3

• IEEE 802.3-RAW

• IEEE 802.3-SNAP

• Internet Packet eXchange (IPX) - RFC 1234, RFC 1552

• Routing Information Protocol (RIP) - RFC 1058

• Service Advertisement Protocol (SAP) - NetWare Protocol