The reason for its continued deployment is that some organizations use servers as low-end routers. RIP comes free of charge on UNIX servers from companies such as Sun Microsystems and on Windows NT server software from Microsoft. RIP is used in server-based routing scenarios, because it enables servers to make dynamic routing decisions while incurring little CPU and network overhead. In today's large networks, though, RIP has tended not to scale particularly well, in part because it has a 15-hop limit. These protocols use scalable methods for making best-path routing decisions through networks, offering an optimized set of possible routes from source to destination.
Metrics set by different groups can be inconsistent.
This situation, if gone unnoticed, can adversely affect network performance. Redundancy Pros and Cons One way to work around incompatibilities in routing protocols is to implement them redundantly. This approach can be undertaken in varying degrees, depending on needs. At one extreme, for example, it might seem an easy solution to implement two routing protocols on every router in the internetwork. This action would result in each router having two sets of routing tables, performing two sets of table updates, and converging twice after topology changes.