Downloads |
Document ID: 17033
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Ticks and Equal Cost Paths (IPX)
Related Information
Introduction
This document discusses Ticks and Equal Cost Paths (IPX).
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
This document is not restricted to specific software and hardware versions.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Ticks and Equal Cost Paths (IPX)
Cisco routers do have ticks in the routing table and in RIP packets, but in 9.1 and earlier the hop count is the only route factor. In 9.21 and later, ticks are the primary route metric and hops are a tie breaker.
Ticks are an advantage when there are equal cost paths with different bandwidths. In those cases, a Cisco router that runs 9.1 software might pick a less desirable path. In 9.21 and later adjust the ipx delay x, where x is the appropriate ticks value for that bandwidth. In 9.21 and later, LAN interfaces have a default ticks value of 1 and WAN interfaces have a default ticks value of 6.
Some applications (reportedly NetWare SAA) set the timeouts based upon the ticks response in the RIP request we reply to. If we do not add a proper ticks to the ticks we receive, then the timeout might be set too short. There has been a handful of verified cases where adjusting the interface delay in 9.1, or the ipx delay in 9.21 or later, to a more accurate ticks value resolved client session timeouts.
In order to dynamically set the ticks to an appropriate value for a WAN interface in IOS® 10.0 or later, configure IPXWAN on both sides of the point-to-point link.
Related Information
| Updated: Oct 05, 2005 | Document ID: 17033 |