NOTE: In SLB mode, IPX traffic is
Loading frame types
After one or more network adapters are bound to a virtual adapter, additional frame types can only be loaded in the virtual adapter if the corresponding frame types are also loaded in the bound adapters. For example, ETHERNET_802.2 can be loaded in QASP VSLOT 1 only if ETHERNET_802.2 is loaded for the Q57 driver in SLOT 1 and 2.
Similarly, a virtual adapter can only be bound to a physical adapter if the physical adapter has all the frame types loaded in the virtual adapter.
Example:
LOAD ODINEB.NLM
LOAD QASP.LAN FRAME=ETHERNET_802.2 NAME=QASP_E82 VSLOT=1
LOAD Q57.LAN FRAME=ETHERNET_802.2 NAME=Q57_1_E82 SLOT=1
LOAD Q57.LAN FRAME=ETHERNET_802.2 NAME=Q57_2_E82 SLOT=2
Hot STANDBY
In Smart
Example:
BIND QASP1 Q57_1_EII
BIND QASP1 Q57_2_EII STANDBY
In the above example, Q57_1_EII and Q57_2_EII are bound as primary and hot standby adapters respectively.
Configuring VLANs
NOTE: VLANs are not supported on
To add VLANs to a team:
1.Load QASP.LAN with the all necessary frame types and specify the VLAN ID for each frame type. You can specify a maximum of 64 VLAN IDs and each VLAN ID can be loaded up to four times with four different frame types.
Example:
(VLAN ID 2 for Ethernet II)
LOAD QASP.LAN FRAME=ETHERNET_II NAME=QASP_1_V2_EII VSLOT=1 VLAN=2
2.Load the network drivers for the adapters in the team with all the frame types specified in step 1. One or more VLAN IDs specified in step 1 do not have to be specified when loading the network drivers. Each frame type loaded in step 1 only needs to be loaded once for each network driver even if in step 1 it is loaded multiple times with different VLAN IDs.
Example:
LOAD ODINEB.NLM
LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_1_EII SLOT=1 VLAN=1 LOAD Q57.LAN FRAME=ETHERNET_II NAME=Q57_2_EII SLOT=2 VLAN=1
3.Bind QASP.LAN to the adapters in the team for each protocol.
Example:
