Downloads |
Document ID: 17038
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Static SAP
Cisco Support Community - Featured Conversations
Related Information
Introduction
This document discusses static SAP.
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.
Static SAP
In 9.1, there is a feature called "static SAP," and it is described on page 17-5 of the Router Configuration Manual (9.1), Vol III. With this feature you can add extra hops for the servers in order to enter the servers into the server table as an entry other than the first.
This way you can put the servers which should not respond to Get Nearest Server requests further down in the server table. 9.1 software responds to GNS requests with the first entry in the server table. So the servers in the table with the extra hops are not included in the GNS response from Cisco.
In 9.21 and later, a static SAP does not override the position of the service in the service table. In 9.21 the SAP table is ordered by routing metric (ticks) and then by the server hops field. The Service table is by default displayed in a sorted order by type, metric, and name. In order to see which server is actually at the top of the list for a particular type, use the command show ipx server unsort.
In order to control how we answer Get Nearest Server replies use the output-gns-filter command.
Cisco Support Community - Featured Conversations
Related Information
| Updated: Oct 05, 2005 | Document ID: 17038 |