Installing PeerMaster LAN Software
PeerMaster adapter in expansion slot 1 into the VNET being formed,
i2 indicates the PeerMaster adapter in slot 2, and so forth. You can
name each VNET separately, using the NAME keyword on the load
command. Each VNET, when bound to a protocol, must be
assigned a different network number. The following example shows
the loading of multiple VNETs.
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=11 NAME=SLOT11
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=12 NAME=SLOT12
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=13 NAME=SLOT13
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=14 NAME=SLOT14
:BIND IPX SLOT11 NET=11
:BIND IPX SLOT12 NET=12
:BIND IPX SLOT13 NET=13
:BIND IPX SLOT14 NET=14
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=21
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=22
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=23
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=24
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=31
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=32
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=33
:LOAD C:\PATH\MXPCI4BT.LAN SLOT=34
(where C: is the primary drive and PATH is the directory)
Create two named VNETs (VNET2 and VNET3) using the 'i_'
keywords to include specific adapters into each VNET.
:LOAD C:\PATH\VNET.LAN i2 NAME=VNET2
:LOAD C:\PATH\VNET.LAN i3 NAME=VNET3
:BIND IPX VNET2 NET=2
:BIND IPX VNET3 NET=3
(where C: is the primary drive and PATH is the directory)
58 PC Server 520 User's Handbook for PCI/EISA