Avaya Configuring XNS Services User Manual download pdf (Page 25)

XNS Overview

303548-A Rev 00

1-9

When you enable external server support on a particular XNS interface, you

specify the service request type to be routed and the destination of the service. The

router then forwards incoming requests for that service type to the remote

destination.

Static Routes

Static routes are manually configured routes that specify the next hop in the

transmission path a datagram must follow based on the datagram’s destination

address. A static route specifies a transmission path to another network.

The Bay Networks router running XNS software allows you to configure static

routes on each logical XNS interface. For example, in Figure 1-2

the route from

the interface on Router Host ID 1 to Network 5 is a static route. Unlike routes

learned through RIP, static routes remain in the RIP tables until you delete them.

Static route support for XNS allows you to do the following:

• Direct all XNS traffic destined to a given network to an adjacent host

• Reduce routing traffic by disabling RIP Supply on all or a subset of attached

interfaces and by manually configuring static routes

• Eliminate all dynamic routing capabilities and all RIP Supply and listen

activities over an XNS interface

Note:

You should enable external server support only when a service is not

available on the local network. The default setting for this feature is Disabled.

Caution:

To establish a data link layer connection in a Frame Relay or SMDS

network (with the router sending frames over a static route), you must

configure an adjacent host and enter a locally significant DLCI. (Refer to

“Configuring Adjacent Host Parameters

” in Chapter 4.)

1 ... 24 25 26 ... 72

No comments

Avaya Configuring XNS Services User Manual Page 25