Filter
Top Products
USER’S GUIDE
404 CyberSWITCH
TRIGGERED RIP/SAP START UP
Problem:
The CyberSWITCH does not display a triggered RIP/SAP starting message for a WAN peer.
Action:
Verify that the WAN peer is properly configured. Issue the device command in Manage Mode to
display the current Device List. Or, you may view the WAN peer list through CFGEDIT, Options,
IPX Configuration, Triggered RIP/SAP. Be sure that the device (WAN peer) has IPX routing enabled
and triggered RIP/SAP (active) selected as routing protocol.
TRIGGERED RIP/SAP OPERATION
Problem:
Routes or Services are not propagated between peers.
Changes are not propagated between peers.
Action:
1. Verify triggered RIP/SAP has successfully started for peers. Issue the
dr
console command
and look for the “starting” message in the log.
2. Generate a triggered RIP/SAP update request to the devices in question. Issue the following
console command for each device:
ipx trigreq <device>
3. Verify that the statistics are incremented properly. Issue the following console commands:
ipx trigrip stats
ipx trigsap stats
4. If routes/services are not propagated on either side, contact Customer Support.
APPLETALK ROUTING
This section provides methods for diagnosing problems in the following areas of AppleTalk
routing:
• AppleTalk routing initialization
• AppleTalk routing over the LAN connection
• AppleTalk routing over the WAN connection
Use the following example configuration to diagnose AppleTalk routing operational problems. The
example below uses AppleTalk addresses, zones, and resource names specific to the example.
Substitute those of your network when you perform the diagnosis steps.