Understanding NetWare Routing Tables
Novell Cool Solutions: Tip
Digg This -
Posted: 24 Feb 2005
A reader asks this question:
This problem has been bothering me lately - every time I reboot my BorderManager server, I have to manually input my IP route in TCPCON again. It's not all that much work, but it still annoys me. (And all my customers are annoyed, because they can't access the network.)
Does anyone have any idea what might cause this? I know that the Filtcfg changes are kept in a text file - is it the same with the routing table? When I reboot, could I just copy/paste a text file that has the routing table? Or better yet, does anyone have a fix for this problem?
And here's some advice from Scott Jones --
There are two different places that you can view and modify the NetWare routing table -- TCPCON and INETCFG.
TCPCON is a dynamic tool -- it displays the routing table that is in effect at that moment. It's an aggregate result of static routing, OSPF, and other route discovery protocols that may be in use. Any changes made in TCPCON will be in effect only temporarily. Changes are not written to disk. Therefore, when you reboot, the server goes back to the permanent configuration. TCPCON is designed primarily for monitoring and troubleshooting.
INETCFG is where you administer the server's permanent configuration options. It lets you enable different types of routing (static, OSPF, etc.) and create/modify the permanent static routing table. Changes made here are written to the various text files in the SYS:\etc directory and are retained on reboot. So, to avoid the problem you're having, use INETCFG to make changes instead of TCPCON.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com