System information

Troubleshooting XNS
Book Title
14-308
Missing or misconfigured xns
helper-address command
Example:
In the following example, the server at address 0000.0c00.23fe
receives all broadcasts on network 51:
xns helper-address 51.0000.0c00.23fe
Step 4
If the command is present, make sure the MAC address specified in
this command is a type of broadcast.
Following is an example of an all-nets broadcast:
interface ethernet 0
xns helper-address -1.ffff.ffff.ffff
Following is an example of a directed broadcast:
interface ethernet 1
xns helper-address 40.ffff.ffff.ffff
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.
Step 1 Enable the debug xns packet privileged exec command and check
the output for XNS packets that have an unknown type xx
specification.
Missing xns forward-protocol
router configuration command
Step 2 Use the show running-config privileged exec command to view the
router configuration. Look for an xns forward-protocol global
configuration command entry.
Step 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
Step 1 Use the show access-lists command to check whether there are
access lists configured on the router.
Step 2 Disable any access lists that are enabled on the router.
Step 3 Test the connection to see whether connections are now possible. If
the connection is successful, an access list is blocking traffic.
Step 4 Enable access lists one at a time until connections are no longer
possible.
Step 5 Alter the problem list so traffic can pass. Configure explicit permit
statements for traffic that you want to be forwarded by the router.
Step 6 If problems persist, continue testing for problem access lists on all
routers in the path from source to destination.
Possible Problem Solution