How to setup IANS fault tolerance

  • 10098252
  • NOVL102700
  • 11-Jul-2005
  • 25-Jul-2005

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Goal

How to setup IANS fault tolerance

Fact

Novell NetWare 6.5 SP3

IANS - Intel Advanced Network Services

Symptom

How to enable IANS (Intel Advanced Network Services) fault tolerance

Fix

This example uses IANS and CE1000.LAN

type INETCFG at the server console.

select Boards and note the physical slot numbers of your current physical boards

press <ESC> and then select Bindings and note the IP address currently bound

press <ESC> and go back into Boards and delete existing boards

press <INSERT> and select IANS - give it a descriptive name such as IANS_1

press <INSERT> and select CE1000.  Give it a descriptive name such as CE1000_1 and enter the slot number.

press <ESC> and select Protocols and then select User-specified Protocol

press <INSERT> to insert a new protocol.  type IANS for the Protocol Name.

select PostBindCommands.  type LOAD IANS COMMIT MODE=AFT and press <ENTER> and then <ESC> back to the main menu.  Note:  you must type the word LOAD or the post bind command will not work and the IANS driver will not load.

select Bindings and press <INSERT> and then select User-specified protocol.  Select A Network Interface and then select the first CE1000 NIC (typically CE1000_1).  type IANS for Protocol.  Select ETHERNET_II for Frame Type.  for Parameters type in TEAM=1 PRIMARY and then press <ENTER> and <ESC> back to the Protocol to Interface/Group Bindings menu. 

Press <INSERT> again and and select User-specified protocol.  Select A Network Interface and then select the second CE1000 NIC (typically CE1000_2).  type IANS for Protocol.  Select ETHERNET_II for Frame Type.  Enter TEAM=1 for parameters and then press <ENTER> then <ESC> back to the Protocol to Interface/Group Bindings menu.  Note that only 1 NIC can have the PRIMARY switch.

Press <INSERT> again and select TCP/IP.  Select A Network Interface and then select the IANS entry (typically IANS_1).  Enter the Local IP address and subnetwork mask.

Exit INETCFG and reset the server.

When the server has rebooted, type IANS status to verify that IANS is loaded and both NICS are bound to it.

Note

In INETCFG before resetting the server you can select View Configuration and then All INETCFG Commands to see the Load and Bind commands.  It should look similar to:

LOAD IANS NAME=IANS_1_EII FRAME=Ethernet_II                                
LOAD CE1000 NAME=CE1000_1_EII FRAME=Ethernet_II SLOT=10016 RXDESCRIPTORS=64
     TXDESCRIPTORS=96 SPEED=100 FORCEDUPLEX=2 FLOWCONTROL=3 PMEDISABLE=0 COA
LOAD CE1000 NAME=CE1000_2_EII FRAME=Ethernet_II SLOT=10017 RXDESCRIPTORS=64
     TXDESCRIPTORS=96 SPEED=100 FORCEDUPLEX=2 FLOWCONTROL=3 PMEDISABLE=0 COA
#!LOAD                                                                     
#PROTONAME IANS                                                            
BIND IANS CE1000_1_EII TEAM=1 PRIMARY                                             
BIND IANS CE1000_2_EII TEAM=1                                       
#!BEGINPOSTBIND                                                            
#!IANS                                                                     
load ians commiT                                                           
#!ENDPOSTBIND                                                              
LOAD TCPIP RIP=No Static=Yes LoadSharing=Yes Forward=No VIPASupport=No     
BIND IP IANS_1_EII ARP=Yes Mask=255.255.255.0 Address=xxx.xxx.xxx.xxx

 

Please note that while IANS will allow you to have adapters with different speeds in a fault tolerant setup, there have been instances reported where having adapters running at different speeds can cause a poison pill abend on the cluster node when rebooting a Cisco switch (full power off/on cycle).  When both adapters are configured for the same speed, this abend did not occur.