[Top][Contents][Prev][Next][Last]Search

Configuring IPX Routing

This chapter covers these topics:
Introduction to IPX routing
Enabling IPX routing in the MAX
Configuring IPX routing connections
Creating static IPX routes
Creating and applying IPX SAP filters
Monitoring IPX connections

Introduction to IPX routing

This section describes how the MAX supports IPX routing between sites that run Novell NetWare version 3.11 or newer. The MAX operates as an IPX router, with one interface on each of its two local Ethernet interfaces and the third across the WAN. Each IPX Connection profile defines an IPX WAN interface.

The most common use for IPX routing in the MAX is to integrate multiple NetWare LANs to form an interconnected wide-area network

The MAX supports IPX routing over PPP and Frame Relay connections. Support for both the IPXWAN and PPP IPXCP protocols makes the MAX fully interoperable with non-Ascend products that conform to these protocols and associated RFCs.

Note: IPX transmission can use multiple frame types. The MAX, however, routes only one IPX frame type (which you configure), and it routes and spoofs IPX packets only if they are encapsulated in that frame. If you enable bridging and IPX routing in the same Connection profile, the MAX bridges any other IPX packet frame types. (For more information see Chapter 8, Configuring Packet Bridging.)

Unlike an IP routing configuration, where the MAX uniquely identifies the calling device by its IP address, a MAX IPX routing configuration does not include a built-in way to uniquely identify callers. For that reason, use PAP and CHAP that requires password authentication, unless you configure IP routing in the same Connection Profile.

Note: If you have a MAX running Multiband Simulation, IPX routing is disabled.

IPX Service Advertising Protocol (SAP) tables

The MAX follows standard IPX SAP behavior for routers. However, when it connects to another Ascend unit configured for IPX routing, the two units exchange their entire SAP tables. Each unit immediately adds all remote services to its SAP table.

NetWare servers broadcast SAP packets every 60 seconds to make sure that routers (such as the MAX) know about their services. Each router builds a SAP table with an entry for each service advertised by each known server. When a router stops receiving SAP broadcasts from a server, it ages its SAP-table entry for that server and eventually removes it from the table.

Routers use SAP tables to respond to client queries. When a NetWare client sends a SAP request to locate a service, the MAX consults its SAP table and replies with its own hardware address and the internal address of the requested server. This is analogous to proxy ARP in an IP environment.

Then the client transmits packets whose destination address is the internal address of the server. When the MAX receives those packets, it consults its RIP table. If it finds an entry for that destination address, it brings up the connection or forwards the packet across the active connection.

IPX RIP (Routing Information Protocol) tables

The MAX follows standard IPX RIP behavior for routers when connecting to non-Ascend units. However, when two Ascend units configured for IPX routing connect, they immediately exchange their entire RIP tables. In addition, the MAX maintains those RIP entries as static until you reset or power-cycle the Ascend unit.
Note: In this chapter, RIP always refers to IPX RIP.

IPX RIP is similar to the routing information protocol in the TCP/IP protocol suite, but it is a different protocol.

The destination of an IPX route is the internal network of a server. For example, the network administrator assigns NetWare file servers an internal IPX network number and typically use the default node address of 000000000001. This is the destination network address for file read/write requests. (If you are not familiar with internal network numbers, see your NetWare documentation for details.)

IPX routers broadcast RIP updates periodically and when you establish a WAN connection. The MAX receives RIP broadcasts from a remote device, adds 1 to the hop count of each advertised route, updates its own RIP table, and broadcasts updated RIP packets on connected networks in a split-horizon fashion.

The MAX recognizes network number -2 (0xFFFFFFFE) as the IPX RIP default route. When it receives a packet for an unknown destination, it forwards the packet to the IPX router advertising the default route. For example, if the MAX receives an IPX packet destined for network 77777777, and it does not have a RIP table entry for that destination, it forwards the packet towards network number FFFFFFFE, if available, instead of simply dropping the packet. If more than one IPX router is advertising the default route, the MAX makes a routing decision based on Hop and Tick count.

Ascend extensions to standard IPX

NetWare uses dynamic routing and service location, so clients expect to be able to locate a server dynamically, regardless of where it is physically located. To help accommodate these expectations in a WAN environment, Ascend provides two IPX extensions: IPX Route profiles and IPX SAP filters.

(For information about the Handle IPX parameter and IPX bridging, see Chapter 8, Configuring Packet Bridging.)

IPX Route profiles

IPX Route profiles specify static IPX routes. When the MAX clears its RIP and SAP tables because of a reset or power-cycle, it adds the static routes when it reinitializes. Each static route contains the information needed to reach one server.

If the MAX connects to another Ascend unit, some sites choose not to configure a static route. Instead, after a power-cycle or reset, the initial connection to that site must be manually activated. After the initial connection, the MAX downloads the RIP table from the remote site and maintains the routes as static until the next power-cycle or reset.

Static routes need manual updating whenever you remove the specified server or change the address. However, static routes help prevent timeouts when a client takes a long time to locate a server across a remote WAN link. (For more information, see Configuring static IPX routes, or see the Configurator Online Help for information about parameters in a profile.)

IPX SAP filters

Many sites do not want the MAX SAP table to include long lists of all services available at a remote site. IPX SAP filters enable you to exclude services from, or explicitly include certain services in, the SAP table.

SAP filters can be applied to inbound or outbound SAP packets. Inbound filters control which services you add to the MAX unit's SAP table from advertisements on a network link. Outbound filters control which services the MAX advertises on a particular network link. (For more information, see Creating and applying IPX SAP filters.

WAN considerations for NetWare client software

NetWare clients on a wide-area network do not need special configuration in most cases. Following are some considerations regarding NetWare clients in an IPX routing environment, and Ascend's recommendations.

Consideration

Recommendation
Preferred servers

 If the local IPX network supports NetWare servers, configure NetWare clients with a preferred server on the local network, not at a remote site. If the local Ethernet does not support NetWare servers, configure local clients with a preferred server on the network with the lowest connection costs. (See your NetWare documentation for more information.)

Local copy of LOGIN.EXE

 Because of possible performance issues, executing programs remotely is not recommended. You should put LOGIN.EXE on each client's local drive.

Packet Burst (NetWare 3.11)

 Packet Burst lets servers send a data stream across the WAN before a client sends an acknowledgment. The feature is enabled by default in server and client software for NetWare 3.12 or later. If local servers are running NetWare 3.11, they should have PBURST.NLM loaded. (See your NetWare documentation for more information.)

Macintosh or UNIX clients

 Both Macintosh and UNIX clients can use IPX to communicate with servers. But they also support native communications via AppleTalk or TCP/IP, respectively. If Macintosh clients must use AppleTalk software (rather than MacIPX) to access NetWare servers across the WAN, the WAN link must support bridging. Otherwise, AppleTalk packets do not make it across the connection. If UNIX clients access NetWare servers via TCP/IP (rather than UNIXWare), the MAX must be configured as either a bridge or an IP router. Otherwise, TCP/IP packets do not make it across the connection.

Enabling IPX routing in the MAX

The Ethernet profile configures system-global parameters that affect all IP interfaces in the MAX. The related parameters are:

For details on each parameter, see the MAX Reference Guide.

Understanding the global IPX parameters

This section provides some background information about IPX routing in the Ethernet profile.

Enabling IPX routing

IPX Routing enables IPX routing mode. When you enable IPX routing in the MAX and close the Ethernet profile, the MAX comes up in IPX routing mode, uses the default frame type 802.2 (which is the suggested frame type for NetWare 3.12 or later), and listens on the Ethernet to acquire its IPX network number from other IPX routers on that segment.

Specifying which frame type to route and spoof

The MAX routes and spoofs only one IPX frame type (IEEE 802.2 by default), specified in the IPX Frame parameter. If some NetWare software transmits IPX in a frame type other than the type specified here, the MAX drops those packets, or if you enable bridging, it bridges them. If you are not familiar with the concept of packet frames, see the Novell documentation.

Setting or learning the proper IPX network number

IPX Enet specifies the IPX network number for the Ethernet interface of the MAX. The easiest way to ensure that the number is correct is to leave the default null address. This causes the MAX to listen for its network number and acquire it from another router on that interface. If you enter a number other than zero, the MAX becomes a seeding router and other routers can learn their IPX network number from the MAX. For details about seeding routers, see the Novell documentation.

Defining a virtual IPX network for dial-in clients

Dial-in clients do not belong to an IPX network, so they must be assigned an IPX network number to establish a routing connection with the MAX. The MAX advertises the route to this virtual network and assigns it as the network address for dial-in clients. If the client does not have a unique node address, the MAX assigns the node address as well.

Example IPX routing configurations

This section shows the simple configuration, where the MAX uses the default frame type and learns its network number from other routers on the Ethernet. It also shows a more complex router configuration, where these values are entered explicitly.

A basic configuration using default values

In this example, the MAX routes IPX packets in 802.2 frames and learns its IPX network number from other routers on the Ethernet. It does not define a virtual network for dial-in clients. To configure the MAX Ethernet profile:

  1. Open the Ethernet profile.

  2. Set IPX Routing to Yes.

  3. Close the Ethernet profile.

When you close the Ethernet profile, the MAX comes up in IPX routing mode, uses the default frame type 802.2, and acquires its IPX network number from other routers.

A more complex example

In this example, the MAX routes IPX packets in 802.3 frames (other frame types are bridged), and uses the IPX network number CF0123FF. It also supports a virtual IPX network for assignment to dial-in clients.

To verify that the MAX should use 802.3 frames, go to the NetWare server's console and type LOAD INSTALL to view the AUTOEXEC.NCF file. Look for lines similar to these:

The last line specifies the 802.3 frame type. To verify that the IPX network number you assign to the MAX Ethernet interface is compatible with other servers and routers on that interface, check the BIND line in the AUTOEXEC.NCF file. The second line in the example shown above specifies the number CF0123FF.

Note: IPX network numbers on each network segment and internal network within a server on the entire WAN must have a unique network number. So, you should know both the external and internal network numbers in use at all sites.

To configure the Ethernet profile:

  1. Open Ethernet > Mod Config and set IPX Routing to Yes.

  2. Open the Ether Options subprofile.

  3. Specify the 802.3 frame type and set the IPX network number for the Ethernet interface.

  4. Assign a network number for assignment to dial-in clients.

    Note: The most common configuration mistake on NetWare internetworks is in assigning duplicate network numbers. Make sure that the network number you specify in the IPX Pool# field is unique within the entire IPX routing domain of the MAX unit.

  5. If more than one frame type needs to cross the WAN, make sure that you enable Bridging. See Chapter 6, "Configuring Packet Bridging."

  6. Close the Ethernet profile.

Verifying the router configuration

 You can IPXPING a NetWare server or client from the MAX to verify that it is up and running on the IPX network. To do so:

  1. Invoke the terminal server command-line interface.

  2. Enter the IPXPING command with the advertised name of a NetWare server. For example:

  3. Terminate IPXPING at any time by typing Ctrl-C.

Configuring IPX routing connections

This section describes how to configure IPX routing connections. The related Answer and Connection parameters are:

For more information on each parameter, see the MAX Reference Guide.

Understanding the IPX connection parameters

This section provides some background information about IPX connections.

Enabling IPX routing in the Answer profile

You must enable IPX routing in the Answer profile for the MAX to pass IPX packets to the bridge/router software.

Authentication method used for passwords received from the far end

The Recv Auth parameter specifies which protocol to use for authenticating the password sent by the far end during PPP negotiation. IPX connections require this parameter, because the MAX cannot verify Connection profiles by address as it does for IP connections.

Applying IPX SAP filters

You can apply an IPX SAP filter to exclude or explicitly include certain remote services from the MAX SAP table. If you apply a SAP filter in a Connection profile, you can exclude or explicitly include services in both directions. See Creating and applying IPX SAP filters.

Specifying the station name and password in a Connection profile

The MAX requires name and password authentication for IPX connections, because the MAX cannot verify Connection profiles by address as it does for IP connections.

Peer dialin for routing to NetWare clients

Dial-in NetWare clients do not have an IPX network address. To allow those clients an IPX routing connection to the local network, the clients must dial in using PPP software and the Connection profile must specify Peer=Dialin. In addition, the MAX must have a virtual IPX network defined for assignment to these clients (see Understanding the global IPX parameters).

Peer=Dialin causes the MAX to assign the virtual IPX network number to the dial-in client during PPP negotiation. If the client does not provide its own unique node number, the MAX assigns a unique node number to the client as well. It does not send RIP and SAP advertisements across the connection and ignores RIP and SAP advertisements received from the far end. However, it does respond to RIP and SAP queries received from dial-in clients. See "An example dial-in client connection" on page 7-18.

Controlling RIP and SAP transmissions across the WAN connection

IPX RIP and IPX SAP in a Connection profile define how the MAX handles RIP and SAP packets across this WAN connection.

Set IPX RIP to Both by default, indicating that RIP broadcasts will be exchanged in both directions. You can disable the exchange of RIP broadcasts across a WAN connection, or specify that the MAX only send or only receive RIP broadcasts on that connection.

Set IPX SAP to Both by default, indicating that SAP broadcasts will be exchanged in both directions. If you enable SAP to both send and receive broadcasts on the WAN interface, the MAX broadcasts its entire SAP table to the remote network and listens for SAP table updates from that network. Eventually, both networks have a full table of all services on the WAN. To control which services are advertised and where, you can disable the exchange of SAP broadcasts across a WAN connection, or specify that the MAX only send or only receive SAP broadcasts on that connection.

Dial query for bringing up a connection based on service queries

Dial Query configures the MAX to bring up a connection when it receives a SAP query for service type 0004 (File Server) and that service type is not present in the MAX SAP table. If the MAX has no SAP table entry for service type 0004, it brings up every connection that has Dial Query set. If 20 Connection profiles have Dial Query set, the MAX brings up all 20 connections in response to the query.

Note: If the MAX unit has a static IPX route for even one remote server, it chooses to bring up that connection as opposed to the more costly solution of bringing up every connection that has Dial Query set.

IPX network and alias

IPX Net # specifies the IPX network number of the remote-end router. It is rarely needed, and is provided only for those remote-end routers that require the MAX to know that router's network number before connecting. The IPX Alias is a second IPX network number, to be used only when connecting to non-Ascend routers that use numbered interfaces.

IPX client or server bridging

Handle IPX defines the handling of bridged connections. When you enable IPX routing for a connection, IPX Routing = N/A. See Chapter 8, Configuring Packet Bridging.

Watchdog spoofing

Netware t/o defines the number of minutes the MAX enables clients to remain logged in even though their connection terminates.

NetWare servers send out NCP watchdog packets to monitor which logins are active and logout inactive clients. Only clients that respond to watchdog packets remain logged in.

Repeated watchdog packets would cause a WAN connection to stay up, but if the MAX simply filtered those packets, client logins would be dropped by the remote server. To prevent repeated client logouts while allowing WAN connections to be brought down in times of inactivity, the MAX responds to NCP watchdog requests as a proxy for clients on the other side of an offline IPX routing or IPX bridging connection. Responding to these requests is commonly called watchdog spoofing.

To the server, a spoofed connection looks like a normal, active client login session, so it does not log the client out. The timer begins counting down as soon as the link goes down. At the end of the selected time, the MAX stops responding to watchdog packets and the client-server connections may be released by the server. If there is a reconnection of the WAN session before the end of the selected time, the MAX resets the timer.

Note: The MAX filters watchdog packets automatically on all IPX routing connections and all IPX bridging connections that have watchdog spoofing enabled. The MAX applies a call filter implicitly, which prevents the Idle timer from resetting when the MAX sends or receives IPX watchdog packets. You apply this filter after the standard data and call filters.

SAP HS Proxy (NetWare SAP Home Server Proxy)

This provides the ability to configure the MAX to forward SAP broadcasts to specified IPX networks to assure that remote users access the same resources as local users.

By default, when you initially load any IPX client software on your PC, the MAX broadcasts a SAP Request packet asking for any servers to reply. The MAX takes the first SAP reply received to be the nearest server, and attaches your PC to that server.

If you load your client software from another PC, or use the same PC when travelling, the initial SAP Request could receive responses from different servers and attaching you to different servers. This new feature adds the ability for you to direct SAP Requests to specific networks. The SAP Responses come from servers on these specified networks rather than coming from servers that are near the MAX. To configure this parameter, see Configuring the NetWare SAP Home Server Proxy.

Example IPX routing connections

This section shows example WAN connections using IPX routing. If the MAX has not yet been configured for IPX routing, see Enabling IPX routing in the MAX.

Configuring a dial-in client connection

In this example, a NetWare client dials into a corporate IPX network using PPP dial-in software. Figure 9-1 shows corporate network supporting both NetWare servers and clients.

Figure 9-1. A dial-in NetWare client

To configure an IPX routing connection for this client:

  1. Open Ethernet > Mod Config > Ether Options and verify that a IPX Pool assignment exists. For example:

  2. Close the Ethernet profile.

  3. Open Answer > PPP Options.

  4. Enable IPX routing and PAP/CHAP authentication.

  5. Close the Answer profile.

  6. Open the Connection profile for the dial-in user.

  7. Specify the dial-in client's login name and activate the profile.

  8. Enable IPX routing.

  9. Select PPP encapsulation and configure the dial-in client's password.

  10. Open the IPX Options subprofile and specify a dial-in client.

  11. Close the Connection profile.

Configuring a connection between two LANs

 In this example, the MAX connects to an IPX network that supports both servers and clients and connects with a remote site that also supports both servers and clients. See Figure 9-2.

Figure 9-2. A connection with NetWare servers on both sides

Site A and site B both exist on Novell LANs that support NetWare 3.12 and NetWare 4 servers, NetWare clients, and a MAX. The NetWare server at site A has this configuration information:

The NetWare server at site B has this configuration information:

To establish the connection shown in Figure 9-2, you would configure the MAX at site A, enable IPX routing for its Ethernet interface, and configure a static route to the remote server. The same procedures would apply to site B.

Configuring the MAX at site A:
  1. Make sure you assign the MAX a system name in the System profile. This example uses the name SITEAGW.

  2. If you have not done so already, configure the Ethernet profile. (See Enabling IPX routing in the MAX.)

  3. In Answer > PPP Options, enable IPX routing and PAP/CHAP authentication, and then close the Answer profile.

    (If the MAX needs to support multiple IPX frame types, you must also enable bridging in the Answer profile.)

  4. Open the Connection profile for site B.

    In this example, the Connection profile for site B is profile #5. A profile's number is the unique part of the number you assign in the Connections menu. For example, the Connection profile defined as 90-105 is #5.

  5. Set up the Connection profile like this:

  6. Close Connection profile #5.

  7. Open an IPX Route profile.

    Set IPX RIP to None in the Connection profile, and configure a static route to the remote server.

  8. Set up a route to the remote NetWare server (SERVER-2) using these settings:

    Note: The Connection # parameter in the IPX Route profile must match the number of the Connection profile you configured to that site. If you specify the internal network number of a server, make sure you specify Server Name and Server Type. If you specify an external network, do not specify Server Name or Server Type.

  9. Close the IPX Route profile.

Configuring the MAX at site B:
  1. Assign a system name to the Ascend unit at site B in the System profile. This example uses the name SITEBGW.

  2. Verify that the site B unit's Ethernet interface has a configuration defined for IPX routing. (See Enabling IPX routing in the MAX.)

  3. Verify that the site B unit's Answer profile enables IPX routing and PAP/CHAP authentication.

  4. Open the Connection profile for site A.

    In this example, the Connection profile for site A is profile #2. A profile's number is the unique part of the number you assign in the Connections menu. For example, the Connection profile defined as 90-102 is #2.

  5. Set up the Connection profile like this:

  6. Close Connection profile #2.

  7. Open an IPX Route profile.

    Set IPX RIP to None in the Connection profile, and configure a static route to the remote server.

  8. Set up a route to the remote NetWare server (SERVER-1) using these settings:

    Note: The Connection # parameter in the IPX Route profile must match the number of the Connection profile you configured to that site. If you specify the internal network number of a server, make sure you specify Server Name and Server Type. If you specify an external network, do not specify Server Name or Server Type.

  9. Close the IPX Route profile.

Configuring a connection with local servers only

 In this example, the MAX connects to a local IPX network that supports both servers and clients, and connects to a geographically remote network that supports one or more NetWare clients. Figure 9-3 shows the example setup.

Figure 9-3. A dial-in client that belongs to its own IPX network

In this example, site A supports NetWare 3.12 servers, NetWare clients, and a MAX. The NetWare server at site A has this configuration information:

Site B is a home office that consists of one PC and an Ascend unit. It is not an existing Novell LAN, so the Ascend unit configuration creates a new IPX network (e.g., 1000CFFF).

Note: The new IPX network number assigned to site B in this example cannot be in use anywhere on the entire IPX wide-area network. (It cannot be in use at site A or any network to which site A connects.)

This example assumes that the Ethernet profile and Answer profile have already been set up to enable IPX routing. The initial connection between the two Ascend units should be manually dialed (using the DO menu) because you do not use static routes.

To configure the MAX at site A
  1. Assign a system name in the System profile for the MAX. This example uses the name SITEAGW.

  2. Open the Connection profile for site B.

  3. Set up the Connection profile like this:

  4. Close the Connection profile.

To configure the Ascend unit at site B
  1. Assign a system name in the System profile for the MAX. This example uses the name SITEBGW.

  2. Open the Connection profile for site B.

  3. Set up the Connection profile like this:

  4. Close the Connection profile.

Configuring the NetWare SAP Home Server Proxy

  1. Open the Ethernet > Connections > Any Connection Profile > IPX Options menu.

  2. Set the SAP HS Proxy parameter to Yes.

  3. Specify the IPX network address to which SAP broadcasts will be directed. For example:

    This indicates any SAP Broadcast Requests received from this user will be directed to IPX network CB1123BC.

  4. If you want to define other networks, repeat Step 3 for SAP HS Proxy Net#2.

Creating static IPX routes

Most sites configure only a few static IPX routes and rely on RIP for most other connections. IPX Route profiles define static IP routes. Each static route contains the information needed to reach one NetWare server.

The related parameters are:

For details on each parameter, see the MAX Reference Guide.

Configuring static IPX routes

A static IPX route includes all of the information needed to reach one NetWare server on a remote network. When the MAX receives an outbound packet for that server, it finds the referenced Connection profile and dials the connection. You configure the static route in an IPX Route profile.

You do not need to create IPX static routes to servers that are on the local Ethernet.

Most sites configure only a few IPX routes and rely on RIP for most other connections. If you have servers on both sides of the WAN connection, you should define a static route to the remote site even if your environment requires dynamic routes. If you have one static route to a remote site, it should specify a master NetWare server that knows about many other services. NetWare workstations can then learn about other remote services by connecting to that remote NetWare server.

Note: Remember that you manually configure static IPX routes, so you must update them if there is a change to the remote server.

Understanding the static route parameters

This section provides some background information on static route configurations.

Example static route configuration

 This example shows a static route configuration to a remote NetWare server. Remember that you manually configure static IPX routes, so you must update them if there is a change to the remote server. To define an IPX Route profile:

  1. Open an IPX Route profile.

  2. Specify the name of the remote NetWare server and activate the route.

  3. Because this is a route to a server's internal network, specify the server's internal network number, node, socket, and service type. For example:

  4. Specify the distance to the server in hops and IBM PC clock ticks. (The default values are appropriate unless the server is very distant.)

  5. Specify the number of the Connection profile; for example:

  6. Close the IPX Route profile.

Creating and applying IPX SAP filters

IPX SAP filters include or exclude services from the MAX service table or from being sent across the WAN to be made visible to remote sites. You can also prevent the MAX from sending its SAP table or receiving a remote site's SAP table by turning off IPX SAP in a Connection profile. See Understanding the IPX connection parameters.

The parameters related to IPX SAP filters are:

For more information on each parameter, see the MAX Reference Guide.

Understanding the SAP filter parameters

This section provides some background information on SAP filters.

Input and Output filters

Each filter contains up to 8 Input filters and Output filters, which you define individually and apply in order (1-8) to the packet stream. Apply the Input filters to all SAP packets the MAX receives. They screen advertised services and exclude (or include) them from the MAX service table as specified by the filter conditions.

Apply Output filters to SAP response packets the MAX transmits. If the MAX receives a SAP request packet, it applies Output filters before transmitting the SAP response, and excludes (or includes) services from the response packet as specified by the Output filters.

Activating the current Input or Output filter

Valid enables the filter for use.

The type of action to take (include or exclude)

Type specifies whether this filter includes the service or excludes it.

Specifying the name of a NetWare server

Server Name can be a local or remote NetWare server name.

If the server is on the local network and this is an Output filter, the Type parameter specifies whether to include or exclude advertisements for this server in SAP response packets.

If the server is on the remote IPX network and this is an Input filter, the Type parameter specifies whether to include or exclude this server in the MAX service table.

Specifying a service type

Server Type specifies a hexadecimal number representing a type of NetWare service; for example, the number for file services is 0004.

In an Output filter, the Type parameter specifies whether to include or exclude advertisements for this service type in SAP response packets.

In an Input filter, the Type parameter specifies whether to include or exclude remote services of this type in the MAX service table.

Applying SAP filters

You can apply an IPX SAP filter to the local Ethernet or to WAN interfaces, or both.

Example IPX SAP filter configuration

 This example shows how to create an IPX SAP filter that prevents local NetWare users from having access to a remote NetWare server, and how to apply that filter to the Answer profile and the Connection profile used to reach the server's remote network.

To define an IPX SAP filter that excludes a remote file server from the MAX SAP table:

  1. Open IPX SAP Filter profile #1 (for this example) and then open the list of Input filters.

  2. Open Input SAP filter 01, activate it, and set Type to Exclude.

  3. Specify the NetWare server's name and service type (for a file server, 0004).

  4. Close the IPX SAP Filter profile.

To apply the IPX SAP Filter in the Answer profile and in a Connection profile:

  1. Open Answer > Session Options.

  2. Specify IPX SAP Filter profile #1, and then close the Answer profile.

  3. Repeat the same assignment in Connections > Session Options.

  4. Close the Connection profile.

Monitoring IPX connections

The terminal server command-line interface supports Show commands for monitoring IPX connections in the MAX. To use these commands, invoke the terminal server interface (System > Sys Diag > Term Serv).

Verifying the transmission path to NetWare stations

The IPXping command enables you to verify the transmission path to NetWare stations at the network layer. It works on the same LAN as the MAX or across a WAN connection that has IPX Routing enabled. It uses this format:

The arguments to the IPXping command are:

where <hostname> is either the IPX address of the NetWare workstation or the advertised name of a server. The IPX address consists of the IPX network and node numbers for a station; for example:

If you are using IPXping to verify connectivity with an advertised NetWare server, you can simply enter the symbolic name of the server; for example:

You can terminate the IPXping at any time by typing Ctrl-C.

During the IPXping exchange, the MAX calculates and reports this information:

These statistics include the following information:

To display statistics related to the IPXping command, type:

The output shows how many NetWare stations have pinged the MAX (InPing requests and replies) and how many times the IPXping command has been executed in the MAX.

Displaying IPX packet statistics

To display IPX packet statistics, enter this command:

The MAX drops packets that exceed the maximum hop count (that have already passed through too many routers).

Displaying the IPX service table

To display the IPX service table, enter this command:

The output contains these fields:

Displaying the IPX routing table

 To display the IPX routing table, enter this command:

The output contains these fields:

Fields

Descriptions
network

 The IPX network number.

next router

 The address of the next router, or 0 (zero) for a direct or WAN connection.

hops

 The hop count to the network.

ticks

 The tick count to the network.

origin

 The name of the profile used to reach the network.

Note: An S or an H flag can appear next to the origin. S indicates a static route. H indicates a hidden static route. Hidden static routes occur when the router learns of a better route.


[Top][Contents][Prev][Next][Last]Search

techpubs@eng.ascend.com

Copyright © 1998, Ascend Communications, Inc. All rights reserved.