LRS Reference Manual


6 - IPX

6.1 - Introduction
6.2 - Routing
6.3 - IPX Networks
6.3.1 - Internal and External networks
6.3.2 - IPX Address Assignment
6.4 - Routing Tables
6.4.1 - Locally Added Entries
6.4.2 - Statically Added Entries
6.4.3 - Dynamically Added Entries
6.5 - Routing with File Servers
6.5.1 - Workstation to File Server Connections
6.6 - LAN to LAN Routing
6.6.1 - Routing Sequence
6.6.2 - Configuration
6.6.2.1 - Ethernet Interface
6.6.2.2 - Static Routing
6.6.2.3 - Sample LAN to LAN Configuration
6.6.2.3.1 - Configuring LRS "Alpha"
6.6.2.3.2 - Configuring LRS "Bravo"
6.7 - RIP and SAP
6.8 - Spoofing
6.9 - Common Service Types
6.10 - Common Sockets
6.11 - Examples
6.11.1 - LAN to LAN
6.11.2 - LRS in San Diego
6.11.3 - LRS in Los Angeles
6.11.4 - Packet Filters
6.12 - Troubleshooting
6.12.1 - NetWare Error Codes
6.12.2 - Checking Network Numbers
6.13 - Quick Reference

6.1 Introduction

This chapter explains some important concepts about IPX NetWare setup and routing. This information is only necessary for those using the IPX protocol.

To configure IPX for remote networking, see Chapter 3 - Basic Remote Networking and Chapter 4 - Additional Remote Networking. For specific IPX commands, see Chapter 12 - Command Reference.


6.2 Routing

Routers accept packets from one network that are destined to another network, then direct them to the appropriate destination. Routers may seem similar to bridges, but there's an important distinction: bridges forward packets based on the destination Ethernet address, and routers forward packets based on the destination IPX address.

Bridges operate on the Data Link Layer, while routers operate on the Network Layer.

The destination address of each packet is examined; the packet is then sent to its destination using the most efficient route. The "most efficient route" is determined using two factors: the network that the address is part of (See , below) and the router's Routing Table (see Routing Tables).


6.3 IPX Networks

The IPX router allows multiple IPX networks to be connected and traffic to pass between them. Each IPX network has a unique network number. Every node on a given IPX network uses the same IPX network number.

For a node on one IPX network to talk to a node on another IPX network, the packets must go through an IPX router, which knows how to talk on both IPX networks. This is depicted in Figure 6-1, where IPX network 1 and IPX network 2 are both attached to IPX router Alpha.

Figure 6-1: Simple IPX Routing

Alpha is configured with two interfaces, one using IPX network number 1 and the other using IPX network number 2. Packets from nodes on network 1 which have to go to nodes on network 2 are actually sent to Alpha which then sends the packets to network 2, and vice-versa. Thus no traffic goes directly between the two networks; they all go through the router. This is a simplified network.

A more complex network is depicted in Figure 6-2, where IPX networks 3, 4, and 5 are added. Note that there is a router between each network. A router is required; nodes on different IPX networks can't communicate directly to one another.

Figure 6-2: More Complex IPX Routing

6.3.1 Internal and External networks

Some NetWare nodes such as file servers and routers use an internal network number. This number is unique across the IPX network. It is a different network than the network that's associated with the network connection, which for clarity will be referred to as the external network.

The external network is the network that all IPX nodes share. The internal network is unique to a particular IPX node. For example, when addressing IPX packets to a file server, the destination network number is the file server's internal network number. Since workstations don't have internal networks, when addressing packets to a workstation, the destination network is the external network number.

The internal network number for the LRS is the last four bytes of the unit's Ethernet address, for example, a3001234. If necessary, this number can be changed; however, it must be changed to a unique number, as two IPX nodes can't have the same internal network number.

6.3.2 IPX Address Assignment

Every IPX network (including all serial links to remote sites) must be assigned a unique IPX network number. When the LRS is initially configured, a range of IPX network numbers (called a netrange) must be defined. The LRS will use the netrange to allocate a network number to each port.

To specify the base number of the range, use the Set/Define IPX Netrange command. Each serial port will be assigned an IPX network number equalling the sum of the base number and its port number.

Figure 6-3: Defining IPX Netrange

Local>> DEFINE IPX NETRANGE 0x100
On the LRS16, the netrange shown in Figure 6-3 is 0x101 to 0x110.


6.4 Routing Tables

The IPX router uses a routing table to keep track of which networks are reachable, and the shortest route to each network. A typical routing table entry consists of the destination network, and which router is the best path to that network. Routing tables also keep track of the cost or metric required to get to a given network.

Entries may be added to the routing table in three ways: locally, statically, or dynamically.

6.4.1 Locally Added Entries

When a route is added locally, it is automatically determined from the LRS's IPX network number. The LRS always keeps a local route to the Ethernet that it is attached to; this route is never deleted.

6.4.2 Statically Added Entries

Statically-entered routes are entered and removed by the administrator. These routes are used when dynamic routes cannot be. For example, before an LRS dials a remote site, it doesn't have any routes to networks at the remote site. The LRS cannot forward packets to these networks unless static routes are defined for them. These routes should have the site parameter set. Static routes can also point to routers on the Ethernet.

6.4.3 Dynamically Added Entries

These routes are automatically learned from other routers on the network, and are managed by a dynamic routing protocol. The LRS currently supports one dynamic routing protocol, RIP. Routes are automatically entered when new networks come on line, and automatically removed if the networks are no longer reachable.

Dynamic routes learned via sites are the exception - they are never timed out. The LRS assumes that these networks are reachable by bringing up a link. This allows the LRS to learn about extended networks at the remote site without the administrator's intervention.


6.5 Routing with File Servers

Novell file servers (version 3.11 and above) function as IPX routers. What they typically route to is their internal network. File servers have a network number associated with each Ethernet port that is configured for IPX and they have one internal network number.

When the file server sends SAP messages it's advertising the services it offers as living on this internal network. They also send out RIP packets announcing that they know how to get to this internal network.

When a workstation connects to a file server the destination network number is actually the file server's internal network, not the Ethernet's network. This is illustrated in Figure 6-4. In this figure, file server Frank and workstation Wally are both connected to the Ethernet.

Figure 6-4: Routing to Internal Network Number

The network number for the Ethernet segment is 2, but Frank's internal network number is 12ab. Wally can't access network 12ab directly so it goes through Frank's routing agent, which "internally routes" packets to 12ab.

6.5.1 Workstation to File Server Connections

When the client shell is loaded on Wally it sends a SAP request for the nearest file server (see Figure 6-4). The routing process on Frank receives this SAP request and sends a reply containing the IPX address of Frank's file server service.

The IPX address consists of the network number, the node number, and the socket number. The network number is Frank's internal network number (12ab), the node number is usually 00-00-00-00-00-01, and socket number is 0x0451.

After Wally receives this SAP reply, it sends a RIP request for network 12ab. Frank sends a RIP reply stating that it knows how to get to network 12ab. Wally receives this and starts sending packets to Frank's routing process, which internally routes the packets to the file server process.

Figure 6-5 shows an additional router, Alpha, between Wally and Frank. When Wally tries to connect to Frank, Alpha will perform the function of Frank's routing process, replying to Wally's RIP and SAP requests. The end result is that packets from Wally are sent to router Alpha which sends them to Frank's routing process, which internally routes to them to the file server process.

Figure 6-5: Router Between Workstation and File Server


6.6 LAN to LAN Routing

Figure 6-6 depicts two networks separated by a phone link. Now there are three routers between Wally and the file server: Alpha, Bravo, and Frank's routing process.

Figure 6-6: File Server and Workstation Separated by Phone Link

For this to work, router Alpha needs to know how to get to network 12ab and needs to know about file server Frank, and router Bravo needs to know how to get to network 1. This information can either be sent via RIP and SAP across the phone link or configured statically on Alpha and Bravo.

See Statically Added Entries for information on static routes.

6.6.1 Routing Sequence

Assuming that Alpha and Bravo know the necessary information, the following sequence of events will occur:

1. When Wally wants to connect to Frank it will send a SAP request for a file server.

2. Alpha will send a SAP response with information about Frank, which is connected to network 12ab.

3. Wally receives this response and sends a RIP request for network 12ab.

4. Alpha sends a response to this since it has a route to 12ab.

5. Wally sends an establish connection packet to Alpha destined for network 12ab.

6. Alpha sends this packet to Bravo, which sends it to Frank.

7. File server Frank sends the reply to Bravo destined for network 1.

8. Bravo sends this to Alpha which sends it to Wally.

6.6.2 Configuration

To display the current IPX configuration, use the Show IPX command. This will display the state of the IPX routing and the Ethernet port configuration. The default IPX configuration is as follows:

6.6.2.1 Ethernet Interface

The first step in setting up IPX routing is to enable IPX routing on the LRS. Use the following command:

Figure 6-7: Enabling IPX Routing

Local>> DEFINE IPX ROUTING ENABLED
Next, the Ethernet interface must be configured to match the IPX network configuration. Two pieces of information are required: the frame type and the network number.

IPX can run on any of four different Ethernet frame types: ETHERNET_II, 802.3, 802.2, or SNAP. Typically all file servers and workstations on a network are configured to use one frame type. Check the configuration of the Novell file servers and workstations to see what frame type they are using.

Novell file servers also have an IPX network number associated with their Ethernet interfaces. This is not the internal network number. This a common network number that all IPX nodes share for a given network; all file servers on the network will have the same number.

To display the frame type and network number, type CONFIG on a file server console screen. Using the displayed type and number, configure the Ethernet interface:

Figure 6-8: Configuring the Ethernet Interface

Local>> DEFINE IPX FRAME 802.2 NETWORK abcd

Local>> DEFINE IPX FRAME 802.2 ENABLED

In the example above, the frame type is 802.2 and the network number is abcd.

Once a frame type is enabled, the IPX router process will send RIP and SAP requests to that interface to get all available routes and services. To confirm that the frame type and number are correct, use the Show IPX Interface command.

Figure 6-9: Confirming the Ethernet Interface Configuration

Local>> SHOW IPX INTERFACE 802.2
The active IPX routing interfaces will be displayed, along with counts for packets received and sent on that interface. If the frame type and network number are correct, these values should be non-zero.

6.6.2.2 Static Routing

The IPX router can be configured to only use static routes and services. This limits the router to only routing data among the configured static routes.

This section illustrates an example of static route configuration between a workstation, Wally, and a file server, Frank. Wally and Frank are connected by a phone link between LRS Alpha and LRS Bravo. See Figure 6-6 for an illustration.

6.6.2.3 Sample LAN to LAN Configuration

The following section details a sample LAN to LAN configuration, displayed in Figure 6-6.

6.6.2.3.1 Configuring LRS "Alpha"

LRS Alpha must have IPX routing enabled and an IPX network number configured for the Ethernet:

Figure 6-10: Enabling IPX Routing and Configuring the Ethernet Interface

Local>> DEFINE IPX ROUTING ENABLED

Local>> DEFINE IPX FRAME 802.3 NETWORK 1

The range of network numbers for Alpha is defined using the Define IPX Netrange command:

Figure 6-11: Defining Range of Network Numbers

Local>> DEFINE IPX NETRANGE 10
Next, RIP and SAP listening are disabled.

Figure 6-12: Disabling RIP/SAP Listening

Local>> DEFINE IPX FRAME 802.3 RIP LISTEN DISABLED

Local>> DEFINE IPX FRAME 802.3 SAP LISTEN DISABLED

IPX routing is enabled on the 802.3 frame type using the following command:

Figure 6-13: Enabling IPX Routing on 802.3

Local>> DEFINE IPX FRAME 802.3 ENABLED
The route to file server Frank's internal network is statically configured to point to site idaho, which handles all connections to Frank.

Figure 6-14: Configuring Static Route to Network 12ab

Local>> DEFINE IPX ROUTE 12ab SITE idaho
A service named frank is configured using the Set/Define IPX Service command:

Figure 6-15: Creating Service

Local>> DEFINE IPX SERVICE frank 4 12ab 00-00-00-00-00-01 451
Note in the above example that the static service frank does not reference site idaho. It is only specified that frank is on IPX network 12ab; the Define Route command used in Figure 6-14 specified that the static route to network 12ab points to site idaho.

6.6.2.3.2 Configuring LRS "Bravo"

LRS Bravo must also have IPX routing enabled and an IPX network number configured for its Ethernet interface. The following commands are used:

Figure 6-16: Enabling IPX Routing and Configuring the Ethernet Interface

Local>> DEFINE IPX ROUTING ENABLED

Local>> DEFINE IPX FRAME SNAP NETWORK 2

The range of network numbers for Bravo is defined using the Define IPX Netrange command:

Figure 6-17: Defining Range of Network Numbers

Local>> DEFINE IPX NETRANGE 20
RIP and SAP listening are disabled using the following command:

Figure 6-18: Disabling RIP/SAP Listening

Local>> DEFINE IPX FRAME SNAP RIP LISTEN DISABLED

Local>> DEFINE IPX FRAME SNAP SAP LISTEN DISABLED

IPX routing is enabled on the SNAP frame type:

Figure 6-19: Enabling IPX Routing on SNAP

Local>> DEFINE IPX FRAME SNAP ENABLED
The route to network 1 is statically configured to point to site nevada, which handles all connections to network 1.

Figure 6-20: Configuring Static Route to Network 1

Local>> DEFINE IPX ROUTE 1 SITE nevada
When the client shell on Wally is loaded the following sequence of events will occur:

1. Wally will request the nearest file server.

2. LRS Alpha has a static route to a file server, so it will respond with information about Frank.

3. Wally will then ask for a route to Frank's IPX network, 12ab.

4. LRS Alpha has a static route to 12ab so it will respond with that information.

5. Wally will then send an establish connection packet to IPX network 12ab.

6. LRS Alpha receives this packet and will route the packet to site idaho. If the link between Alpha and Bravo isn't currently up, Alpha will establish the connection.

7. When LRS Bravo receives the packet, it will get routed out the Ethernet interface to Frank.

8. Frank will send a reply to IPX network 1.

9. LRS Bravo consults its routing table, and routes this packet to site nevada.

Imagine that there is another file server on network 2, Delta, which has internal network number 74fca132 and hardware address
00-00-12-00-12-34. The following commands entered on LRS Alpha will allow workstations to connect to Delta:

Figure 6-21: Enabling Connections to File Server Delta

Local>> DEFINE IPX ROUTE 74fca132 SITE idaho

Local>> DEFINE IPX SERVICE delta 4 74fca132 00-00-12-00-12-34 451

The commands in Figure 6-21 tell LRS Alpha that file server Delta is on network 74fca132 and that network is reachable through site idaho.


6.7 RIP and SAP

RIP (Routing Information Protocol) and SAP (Service Advertising Protocol) packets enable the LRS to broadcast its known routes and services and obtain this information from other routers. Each site may configure RIP and SAP in a number of ways.

When a new site is created, by default, the site will listen to RIP and SAP packets and will send RIP and SAP updates when information has changed. In some situations (for example, to reduce network traffic), RIP and/or SAP should be disabled. For configuration instructions, see RIP and SAP.


6.8 Spoofing

Spoofing enables an LRS to send keepalive packets and responses to and from a file server and workstation. This permits the connection between the workstation and file server (or between two LRS units) to remain idle when there isn't interactive packet traffic; connections will not be initiated simply for keepalive packets.

Spoofing is discussed in detail in Chapter 4 - Additional Remote Networking.


6.9 Common Service Types

Unknown0000
Print Queue0003
File Server 0004
Job Server0005
Print Server 0007
Archive Server0009
Administration 000B
NAS SNA Gateway0021
Remote Bridge Server0024
TCP/IP Gateway0027
Time Synch Server002D
Advertising Print Server0047
NetWare Access Server 0098
Portable NetWare 009E
WildcardFFFF


6.10 Common Sockets

NetWare Core Protocol (NCP)0451
Service Advertising Protocol (SAP) 0452
Routing Information Protocol (RIP)0453
Novell NetBIOS0455
Diagnostics0456


6.11 Examples

6.11.1 LAN to LAN

In this example, there are two different LANs, one in Los Angeles and one in San Diego. The LANs are connected via two LRS units and a leased line.

This LAN to LAN connection must meet the following criteria:

6.11.2 LRS in San Diego

This LAN is running NetWare on frame type 802.2. The network number is 1234ABCD.

The leased line is connected to port 2 of the LRS.

Figure 6-22: San Diego LRS Configuration

Local>> DEFINE IPX ROUTING ENABLED

Local>> DEFINE IPX FRAME 802.2 NETWORK 1234ABCD

Local>> DEFINE IPX FRAME 802.2 ENABLED

Local>> DEFINE IPX NETRANGE 100

Local>> DEFINE PORT 2 AUTOSTART ENABLED

Local>> DEFINE PORT 2 PPP DEDICATED

Local>> INITIALIZE DELAY 0

6.11.3 LRS in Los Angeles

This LAN is running NetWare on frame type 802.2. The network number is FED.

The leased line is connected to port 2 of the LRS.

Figure 6-23: Los Angeles LRS Configuration

Local>> DEFINE IPX ROUTING ENABLED

Local>> DEFINE IPX FRAME 802.2 NETWORK FED

Local>> DEFINE IPX FRAME 802.2 ENABLED

Local>> DEFINE IPX NETRANGE 200

Local>> DEFINE PORT 2 AUTOSTART ENABLED

Local>> DEFINE PORT 2 PPP DEDICATED

Local>> INITIALIZE DELAY 0

6.11.4 Packet Filters

An LRS in Irvine uses site dallas to manage connections to an LRS in Dallas. A filter list must be configured for this site to forward only 3 types of packets: IPX RIP, IPX SAP, and packets from a file server with internal network number 0x1234abcd.

Figure 6-24: LAN to LAN Connection Between Irvine and Dallas

The following commands must be used to create the filter list:

Figure 6-25: Creating the Filter List

Local>> DEFINE FILTER texasfilt CREATE

Local>> DEFINE FILTER texasfilt ADD ALLOW IPX SNET 0xffffffff 0x1234abcd

Local>> DEFINE FILTER texasfilt ADD ALLOW IPX DSOCK EQ RIP

Local>> DEFINE FILTER texasfilt ADD ALLOW IPX DSOCK EQ SAP

Local>> DEFINE FILTER texasfilt ADD ALLOW IPX TYPE RIP

Local>> DEFINE FILTER texasfilt ADD ALLOW IPX TYPE SAP

Local>> SAVE FILTER texasfilt

To associate filter list texasfilt with site dallas, the Define Site Filter command is used.

Figure 6-26: Associating the Site with the Filter List

Local>> DEFINE SITE dallas FILTER OUTGOING texasfilt
Site dallas will use texasfilt as an outgoing filter list. When dallas is used for a connection, outgoing packets will be compared to the filters in this list before they are forwarded.

For complete filter list configuration instructions, see Packet Filters and Firewalls.


6.12 Troubleshooting

This section offers some troubleshooting tips that may help you isolate and correct IPX configuration problems.

6.12.1 NetWare Error Codes

If the LRS detects NetWare problems (file server connection problems, unsent packets, etc.), it will record the problem in the form of an error code. To display these error codes, use the Show NetWare command.

In the Error Reasons field, a hexadecimal value may be displayed. To determine the error, translate the error code to binary digits, note which bits are set and consult Table 6-1.

Table 6-1: NetWare Error Codes

Bit SetErrorRemedy (if any)
0The LRS received a packet for an unknown IPX protocol. The packet was discarded.This is a minor error; no correction is necessary.
1The LRS received a packet for an unknown socket. The packet was discarded.This is a minor error; no correction is necessary.
2The LRS couldn't attach to the print queue on the NetWare file server. If the LRS cannot attach to the file server, the print queue cannot be provided as an LRS service. Try deleting and recreating the print queue. Ensure that the LRS and the service on the LRS are in the print queue's "Print Servers" list.
3The LRS couldn't connect to a file server. Check the number of licenses; ensure that enough licenses are available. Check the file server's security configuration.
4The LRS couldn't log out of the file server. 
5The LRS couldn't get its credentials from the file server. Obtaining credentials is part of the file server login process. If the LRS doesn't receive credentials, the login will fail. Try deleting and recreating the print queue and print servers.
6The file server didn't accept the LRS credentials. This error may occur when the LRS login password has been changed, and doesn't match the print server password on the file server.

 

Try deleting and recreating the print queue and print servers. Also, ensure that the LRS login password matches the print server password. To change the login password, see Login Password.

If the LRS login password has not been changed from the default login password (access), a password is not required to log into the print server. Ensure that the print server has not been issued a password.

7The LRS couldn't log into the file server. The file server's login slots may be full; ensure that there is an adequate number of licenses.
8The check membership call failed. When the LRS scans for print queues, it checks the membership of various objects. This is a minor error; no correction is necessary.
9The LRS couldn't map user to trustee.

 

Try deleting and recreating the print queue and print servers, and recreating them. Also, ensure that the LRS login password matches the print server password. To change the login password, see Login Password.

If the LRS login password has not been changed from the default login password (access), a password is not required to log into the print server. Ensure that the print server has not been issued a password.

10The LRS couldn't attach to the print queue on the NetWare file server. If the LRS cannot attach to the file server, the print queue cannot be provided as an LRS service.Try deleting and recreating the print queue. Ensure that the LRS and the service on the LRS are in the print queue's "Print Servers" list.
11The LRS couldn't service the print queue or couldn't read the job. Try clearing the jobs from the print queue and resubmitting them.
12The LRS couldn't open a file on the file server.Make sure the file exists and is located in the login directory of the file server's sys drive (e.g. f:\login). This bit gets set when using the source command if the LRS can't read the file.

The rightmost bit is bit zero. Bits 13 and above are currently unused.

An error code may denote multiple errors. For example, a hexadecimal value of 000043 translates to 0000 0000 0000 0000 0100 0011 in binary digits. In this case, bits 0, 1, and 6 are set, representing three different errors.

6.12.2 Checking Network Numbers

In addition to error codes, the Show NetWare command will display current network numbers; examine these numbers to ensure that they are correct. If the network numbers appear to be correct and the problem persists, consult the following table:

Table 6-2: Troubleshooting

ProblemPossible CausesRemedies
No packets are transferred, even though no settings have been adjusted.The LRS is not connected properly.

There is a duplicate internal network number on the network.

Ensure that all physical connections to and from the LRS are secure.

Check the internal network numbers of all IPX nodes to ensure that there is not a duplicate. If there is, change the LRS's internal network number. No two IPX nodes can have the same internal network number

Packets are transferred between some but not all nodes on the network.The LRS cannot communicate with either the source or destination IPX address.

Internal routing has been turned off. If more than one frame type is enabled, internal routing should also be enabled.

Ensure that the frame type(s) of both the origination node and destination node are enabled. Re-enable any frame types necessary.

Enable internal routing.


6.13 Quick Reference

IPX Address Assignment   
ToUse This CommandExample(s)What Example Does
Specify the Base Number of the IPX NetrangeSet/Define IPX NetrangeDEFINE IPX NETRANGE 0x100

 

Defines 0x100 as the base number of the LRS netrange. Each LRS port will be assigned an IPX network number equal to the sum of 0x100 and the port number.

On the LRS16, this netrange is 0x101 to 0x110.

For more information, see IPX Address Assignment.

Routing   
ToUse This CommandExample(s)What Example Does
Display the Current IPX ConfigurationShow/Monitor/List IPXSHOW IPXDisplays information about IPX RIP, SAP, frame types, and whether IPX routing is enabled or disabled.

For more information, see Ethernet Interface.

Enable IPX RoutingSet/Define IPX RoutingDEFINE IPX ROUTING ENABLED

 

Enables the LRS to route IPX packet traffic.

For more information, see Ethernet Interface.

Configure the Ethernet Frame Type and Network NumberSet/Define IPX EthernetDEFINE IPX ETHERNET FRAME 802.2 NETWORK abcd

DEFINE IPX ETHERNET FRAME 802.2 ENABLED

Enables frame type 802.2 on Ethernet abcd.

For more information, see Ethernet Interface.

Routing, cont.   
ToUse This CommandExample(s)What Example Does
Verify the Current IPX Frame Type and Network NumberShow/Monitor/List IPX InterfaceSHOW IPX INTERFACE 802.2

 

Displays the active IPX routing interfaces.

For more information, see Ethernet Interface.

Define a Static RouteSet/Define IPX RouteDEFINE IPX ROUTE 1234 NEXTROUTER 45af-00-00-ab-12-e2-38Specifies that the route to network 1234 is through router 45af-00-00-ab-12-e2-38.

For more information, see Statically Added Entries.

  DEFINE IPX ROUTE 1234 SITE dallas 2 50Specifies that the route to network 1234 is through site "dallas".
Define a Static ServiceSet/Define IPX ServiceDEFINE IPX SERVICE frank 4 12ab 00-00-00-00-00-01 451Creates a static service named "frank". This service is on network 12ab, node 00-00-00-00-00-01, socket 451. It is a type 4 service.

For more information, see Statically Added Entries.

Disable RIP or SAPSee RIP and SAP.  
Configure Keepalive SpoofingSee Spoofing.  

LRS Reference Manual - 4 MARCH 1996

Generated with Harlequin WebMaker