System information

Troubleshooting Novell IPX 8-147
Novell IPX: Client Cannot Connect to Server over ISDN
Novell IPX: Client Cannot Connect to Server over ISDN
Symptom: Clients cannot connect to servers over an ISDN link. Clients can connect to local servers.
Misconfigured LMI
5
type
(Frame Relay only)
Step 1 Use the debug frame-relay lmi privileged exec command to see the LMI
type being used by the Frame Relay switch.
Step 2 The LMI type is determined by your Frame Relay provider. Make sure
you use the LMI type specified by the provider.
Frame Relay broadcast queue
full (Frame Relay only)
This problem is most likely to occur on the hub router in a Frame Relay
hub-and-spoke topology.
Step 1 Use the show interfaces privileged exec command to check for dropped
Frame Relay broadcast frames.
Step 2 If the number of drops on the broadcast queue is excessively high,
increase the size of the queue using the frame-relay broadcast-queue
size byte-rate packet-rate interface configuration command.
Command Syntax:
frame-relay broadcast-queue size byte-rate packet-rate
Command Syntax:
• size—Number of packets to be held in the broadcast queue. The default
is 64 packets.
• byte-rate—Maximum number of bytes to be transmitted per second.
The default is 256000 bytes per second.
• packet-rate—Maximum number of packets to be transmitted per
second. The default is 36 packets per second.
Hub router not forwarding SAPs
(Frame Relay only)
In a Frame Relay hub-and-spoke topology, SAPs received on one of the hub
router’s interfaces will not be forwarded back out the same interface because of the
split horizon rule, which states that an incoming packet cannot be placed on the
same network interface from which it originated, preventing an infinite routing
loop if a link fails.
To allow SAPs to be forwarded appropriately, you must configure subinterfaces on
the Frame Relay interface of the hub router. Assign a subinterface to each spoke
site. The hub router will treat each subinterface as a physical interface, allowing it
to advertise SAPs without violating the split horizon rule. For specific information
on configuring subinterfaces, see the Wide-Area Networking Configuration Guide.
Note: Other problems can prevent a router from forwarding SAP packets. For
more information, see the section “IPX RIP: SAP Updates Not Propagated by
Router” later in this chapter.
Missing or misconfigured
multicast address (SMDS only)
Step 1 Use the show running-config privileged exec command to view the
router configuration. Check for an smds multicast ipx interface
configuration command entry.
Step 2 If the command is not present, add it to the configuration. If the command
is present, confirm that the multicast address configured is correct. The
SMDS multicast address is specified by your SMDS provider.
1 You can eliminate the need for Frame Relay address maps by using Inverse ARP instead. Use the frame-relay interface-dlci dlci
broadcast interface configuration command to configure an interface to use Inverse ARP. For more information about the use of
this command, refer to the Cisco IOS Wide-Area Networking Configuration Guide and Wide Area Networking Command Reference.
2 DLCI = data-link connection identifier
3 SMDS = Switched Multimegabit Data Service
4 HDLC = High-Level Data Link Control
5 LMI = Local Management Interface
Possible Problem Solution