Novell TCP/IP

This chapter describes issues yet to be resolved for Novell® TCP/IP for the NetWare 6 Support Pack 1 release.


Configuration through INETCFG

  1. If the NETINFO.CFG file is corrupted and on loading INETCFG you get a message asking you to reconfigure, delete the TCPIP.CFG. We recommend that you back up NETINFO.CFG, NETINFO.CHK, and TCPIP.CFG once the network configuration of the server is finalized. In case of corruption, restore from the backed up configuration.
  2. In machines with multiple NICs, if already in-use IP addresses are selected for binding an ARP, a conflict error message is displayed for each binding. The system should automatically trigger unbinding of the IP addresses. If the binding persists, you must manually delete the bindings and reinitialize the system.

Supernetting

Once the server is configured with a supernet mask, it behaves as an end node because IP Forward gets disabled. It continues to behave as an end node even if the mask is changed to a non-supernet one and the system is reinitialized. To make it work like a router, change the state of IP Packet forwarding or RIP or LAN Static Routing in INETCFG and then reinitialize the system.


Fault Tolerance

Fault tolerance is supported on ODITM compliant drivers. Some of the drivers supported are CE100B, IBMFE, PCNTNW, 3C90XC, N100, and CPQNF3.


Load Balancing

Load balancing might not work when all the clients' IP addresses are mapped to a single NIC of the server and clients start data transfer simultaneously.


NIC Failover Time

Currently the NIC failover time is 1 second.


Routing

EGP is not functional and OSPF is only partly functional in this release.


NIAS

Novell Internet Access Server is not supported in this release.


RAM

In cases where the server is to be stressed with heavy network operations, make sure that 512 MB or more RAM is available.


IP Trace

  1. Once the IP Trace is loaded, you cannot load anything from the console until the trace finishes. To load something, close the IP Trace screen.
    2.
  2. A blank space is not permissible between the command arguments and the equal sign (=) following them.
  3. Source option is not supported in this release.
    4.
  4. In some destination addresses, the utility stops at the hop before the target.

Application Dependency

An application might stop working if the IP address it uses is changed. For more information on this, refer to the documentation of the specific product or application.


NIC Teaming

Currently only one User Specified Protocol is supported.



Previous | Next