Visara LINCS Features - Manual (Page 143)

133 707021-001
11. IP Routing
The LINCS IP Router feature allows a LINCS node to function as an IP router when attached
to a TCP/IP internetwork via one or more LAN boards or through a Frame Relay connection.
IP routing is supported between all LAN and Frame Relay connections. The LANs can be any
combination of Ethernet and/or Token Ring lines.
To enable IP routing, enable IP protocol for the desired LAN/WAN cards in configuration.
This will cause a Line Options, TCP/IP Options panel to appear.
You must configure the IP address, IP subnet mask, and enable one of the router options.
You may optionally choose to configure a default router. The default router is where LINCS
will forward a packet to, if no other entry in the routing table exists to match the packet to
a destination.
You can configure IP Routing in addition to any other feature supported by LINCS. You can
configure IP Routing for any LAN/HSC card (except for one that is configured for the IP
Channel Bridge feature).
LINCS supports the following types of IP Routing in Release 4.1:
• Static Routing
• Static and Dynamic
• RIP Version 1
• RIP Version 2
• Addressing
In order to operate correctly in your network, the IP addressing selected for the LAN cards on
the LINCS platform must be suitable. All nodes expected to use the LINCS platform to route
traffic for them must be addressed to be on the same subnet as LINCS. It is extremely important
that the subnet mask is selected correctly and entered correctly into the LINCS configuration.
If a Default Router is configured in the LINCS configuration for the purpose of forwarding
packets to (when no other destination is found in the LINCS table), it must also be on the same
subnet as the LINCS LAN card’s address implies.
Mixed Router Environment
LINCS can be interfaced into a network where routers from other vendors are installed. If the
other routers support RIP, you can configure LINCS as a RIP router (version 1 or version 2)
and LINCS should update routing tables based on the RIP packets received. If the other routers
in the network do not support RIP, and another routing protocol is being used, it may be
necessary to enter a static route (to LINCS) into the nearest router’s configuration for any
routes that can only be reached through the LINCS platform. You will also need to put one or
more entries into LINCS’ configuration to communicate through the existing network. The
simplest entry to add to LINCS would be to define the nearest non-LINCS router as the default
router for LINCS to send packets to. Thus any packets received for subnets other than the ones
connected to LINCS will be forwarded to the other router for determining the ultimate path to
the destination.