Information Technology Reference
In-Depth Information
Table14-2 XNS: XNS Broadcast Packets Not Forwarded by Router (continued)
Possible Problem
Solution
Missing or
misconfigured
xns
helper-address
command
(continued)
The helper address specification differs depending on the
network configuration. For more information, refer to the
Cisco IOS
Network Protocols Configuration Guide, Part 2,
and
Network Protocols Command Reference
,
Part 2
.
Missing
xns
forward-protocol
router
configuration
command
Caution:
Because debugging output is assigned high priority in
the CPU process, it can render the system unusable. For this
reason, use
debug
commands only to troubleshoot specific
problems or during troubleshooting sessions with Cisco
technical support staff. Moreover, it is best to use
debug
commands during periods of lower network traffic and fewer
users. Debugging during these periods decreases the likelihood
that increased
debug
command processing overhead will affect
system use.
1.
Enable the
debug xns packet privileged exec
command and
check the output for XNS packets that have an unknown type
xx
specification.
2.
Use the
show running-config privileged exec
command to
view the router configuration. Look for an
xns forward-protocol
global configuration command entry.
3.
If the
xns forward-protocol
command is not present, add it
as appropriate.
Syntax:
xns
forward-protocol
protocol
Syntax Description:
•
protocol
—
Number of an XNS protocol, in decimal. See the
documentation accompanying your host's XNS
implementation for a list of protocol numbers.
Misconfigured
access list
Use the
show access-lists
command to check whether there
are access lists configured on the router.
1.
Disable any access lists that are enabled on the router.
2.
Test the connection to see whether connections are now
possible. If the connection is successful, an access list is
blocking traffic.
3.
Enable access lists one at a time until connections are no
longer possible.
4.
Alter the problem list so traffic can pass. Configure explicit
permit
statements for traffic that you want to be forwarded
by the router.
5.
If problems persist, continue testing for problem access lists
on all routers in the path from source to destination.
6.
