Ipx Rip No Connectivity over Ipx Rip Router

Symptom: IPX RIP routers are blocking connections. Clients cannot connect to servers over one or more routers running IPX RIP.

Note Procedures for troubleshooting connectivity problems not specific to IPX RIP routing are described in the section "Novell IPX: Client Cannot Connect to Server on Remote LAN" earlier in this chapter.

Table 8-6 outlines the problems that might cause this symptom and describes solutions to those problems.

Table 8-6: IPX RIP: No Connectivity over IPX RIP Router

Possible Problem

Solution

IPX RIP routing not configured o0r misconfigured on the router

Step 1 Use the show running-config privileged exec command to view the router configuration.

Step 2 Check the configuration to make sure there is an ipx routing global configuration command entry. If there is not, enter the ipx routing command to enable IPX routing.

Issuing the ipx routing command on a router automatically enables IPX RIP routing on all interfaces that have a network number assigned to them.

Missing ipx network commands on interface

Step 1 Use the show ipx interface privileged exec command to view the state of all IPX interfaces.

Step 2 If the output indicates that there are no interfaces running IPX, or if an interface that should be running IPX is not, you must configure the appropriate interfaces with an IPX address. The Novell server administrator can provide the IPX network number for the segment to which your router is attached.

Missing ipx network commands on interface

To enable IPX protocol processing on an interface, enter the ipx network number interface configuration command: ipx network network [encapsulation encapsulation-type [secondary]]

Syntax Description:

• network---Network number. This is an eight-digit hexadecimal number that uniquely identifies a network cable segment. It can be a number in the range 1 to FFFFFFFE. You do not need to specify leading zeros in the network number. For example, for the network number 000000AA you can enter just AA.

• encapsulation encapsulation-type---(Optional) Type of encapsulation. It can be one of the following values:

m arpa (for Ethernet interfaces only)---Use Novell's Ethernet II encapsulation. This encapsulation is recommended for networks that handle both TCP/IP and IPX traffic. m hdlc (for serial interfaces only)---Use HDLC encapsulation.

m novell-ether (for Ethernet interfaces only)---Use Novell's Ethernet 802.3 encapsulation. This encapsulation consists of a standard 802.3 MAC header followed directly by the IPX header with a checksum of FFFF. It is the default encapsulation used by NetWare Version 3.11.

m sap (for Ethernet interfaces)---Use Novell's Ethernet 802.2 encapsulation. This encapsulation consists of a standard 802.3 MAC header followed by an 802.2 LLC header. This is the default encapsulation used by NetWare Version 4.0. (for Token Ring interfaces)---This encapsulation consists of a standard 802.5 MAC header followed by an 802.2 LLC header. (for FDDI interfaces)---This encapsulation consists of a standard FDDI MAC header followed by an 802.2 LLC header.

Missing ipx network commands on interface

m snap (for Ethernet interfaces)---Use Novell Ethernet Snap encapsulation. This encapsulation consists of a standard 802.3 MAC header followed by an 802.2 SNAP LLC header. (for Token Ring and FDDI interfaces)---This encapsulation consists of a standard 802.5 or FDDI MAC header followed by an 802.2 SNAP LLC header.

• secondary---(Optional) Indicates an additional network configured after the first (primary) network.

RIP timer mismatch

You can change RIP timer values changed on servers running NetWare 4.x or later. Mismatches between routers and servers can cause connectivity problems.

Step 1 Use the show ipx interfaces privileged exec command on the router to view the state of IPX interfaces. Look for output similar to the following:

C4500#show ipx interface

Updates each 60 seconds, aging multiples RIP: 3 SAP: 3 [...]

Compare the timer value configured on the router with that configured on Novell servers.

Step 2 The timer values configured on servers and routers should be the same across the whole IPX network.

Reconfigure the router or the servers to bring the timer values into conformance. On the router, use the ipx update-time interface configuration command to change the RIP timer interval.

For information on changing the timer value configured on Novell servers, consult your server documentation.

Router not propagating RIP updates

Step 1 Use the debug ipx routing activity privileged exec command on the router. Look for routing updates sent by the router out each interface.

Step 2 If you do not see RIP updates being sent out the interfaces, try disabling RIP routing using the no ipx routing global configuration command and then reenabling it using the ipx routing command.

Use the show running-config command to verify that the rest of the IPX configuration is still correct.

Step 3 If disabling and reenabling IPX does not work, try restarting the router.

Misconfigured network filters

Step 1 Use the show access-lists privileged exec command on suspect routers to see whether there are Novell IPX access lists configured.

Step 2 Use the show running-config privileged exec command to view the router configuration. You can see whether access lists are specified in an ipx input-network-filter or ipx output-network-filter interface configuration command.

Examples:

In the following example, access list 876 controls which networks are added to the routing table when IPX routing updates are received on Ethernet Interface 1:

access-list 876 permit 1b interface ethernet 1

ipx input-network-filter 876

Routing updates for Network 1b will be accepted. Routing updates for all other networks are implicitly denied and are not added to the routing table.

The following example is a variation of the preceding that explicitly denies Network 1a and explicitly allows updates for all other networks:

access-list 876 deny 1a access-list 876 permit -1

Misconfigured network filters

Step 3 If access lists are used by one of these commands, disable the filters by using the no ipx input-network-filter or no ipx output-network-filter command.

Step 4 Check whether the client can access the server normally. If the connection is successful, one access list or more needs modification.

Step 5 To isolate the problem access list, apply one IPX filter at a time until you can no longer create connections.

Step 6 When the problem access list is isolated, examine each access-list statement to see whether it blocks traffic from desired networks. If it does, configure explicit permit statements for networks that you want to be advertised normally in updates.

Step 7 After altering the access list, re-enable the filter to make sure connections between the client and the server still work. Continue testing access lists until all your filters are enabled and the client can still connect to the server.

Routes not redistributed correctly

Step 1 Use the show ipx route privileged exec command to see the IPX routing table.

Step 2 Examine the routing table and make sure routes have been learned by the expected protocol and from the expected interface.

Step 3 Use the show running-config privileged exec command to view the router configuration. Check each ipx router global configuration command entry and the associated redistribute commands, if any.

Routes not redistributed correctly

Step 4 Make certain redistribution is configured between IPX RIP and the desired protocols. Make sure all the desired networks are specified for redistribution.

Note: Route redistribution is enabled automatically between IPX RIP and Enhanced IGRP1 and between IPX RIP and NLSP.2

For detailed information on configuring route redistribution, see the Network Protocols Configuration Guide, Part 1.

Router not propagating SAPs

For information on troubleshooting this problem, refer to the following section "IPX RIP: SAP Updates Not Propagated by Router."

1Enhanced IGRP = Enhanced Interior Gateway Routing Protocol 2NLSP = NetWare Link Services Protocol

0 0

Post a comment