HP Vectra VE C/xxx 7 HP Vectra VE C/xxx Series 7 PC - Network Administration G - Page 88

HP Ethernet Family Adapter cannot keep up with RPL.NLM.

Page 88 highlights

5 Configuring for Remote Boot Setting Up a Novell NetWare 3.x and 4.x Server for Remote Start The possible parameters are as follows: ACK Use this parameter if you wish to configure the RPL module to ACKnowledge FILE.DATA.RESPONSE frames sent by RPL.NLM. RPL.NLM will send FILE.DATA.RESPONSE frames in a burst mode by default. This parameter allows pacing by the workstation if the HP Ethernet Family Adapter cannot keep up with RPL.NLM. FRAME=ff Use this parameter if you wish to configure the bootstrap program (RBOOT.RPL) to use a frame type other than the default to access the file server. Valid frame types are: FRAME=802.2. Default FRAME=EII. ETHERNET_II protocol. (Only use on ETHERNET networks.) FRAME=SNAP. SNAP protocol. If FRAME=EII or FRAME=SNAP is selected, RPL.NLM forces the bootstrap program to do a "Get Nearest Server" (GNS). GNS This parameter specifies that you wish the workstation to do a Get Nearest Server request when the appropriate bootstrap program is downloaded. Normally, RPL.NLM will supply the bootstrap program with the file server information so that it does not need to do a Get Nearest Server request. Using the GNS parameter may cause the workstation to find a server other than one where RPL.NLM is located. This is mandatory for an SFT III installation. NODEFAULT This parameter tells RPL.NLM not to respond to a FIND frame unless the node address of the workstation is found in the BOOTCONF.SYS file. It is provided for security reasons. The workstation will not boot until the system administrator inserts - in the BOOTCONF.SYS file - the node address and associated Disk Image File name(s) to use when booting the workstation. 88 English

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112

5
Configuring for Remote Boot
Setting Up a Novell NetWare 3.x and 4.x Server for Remote Start
88
English
The possible parameters are as follows:
ACK
Use this parameter if you wish to configure the RPL module to
ACKnowledge FILE.DATA.RESPONSE frames sent by RPL.NLM.
RPL.NLM will send FILE.DATA.RESPONSE frames in a burst mode
by default. This parameter allows pacing by the workstation if the
HP Ethernet Family Adapter cannot keep up with RPL.NLM.
FRAME=ff
Use this parameter if you wish to configure the bootstrap program
(RBOOT.RPL) to use a frame type other than the default to access
the file server.
Valid frame types are:
FRAME=802.2. Default
FRAME=EII.
ETHERNET_II protocol. (Only use on ETHERNET
networks.)
FRAME=SNAP. SNAP protocol.
If FRAME=EII or FRAME=SNAP is selected, RPL.NLM forces the
bootstrap program to do a “Get Nearest Server” (GNS).
GNS
This parameter specifies that you wish the workstation to do a Get
Nearest Server request when the appropriate bootstrap program is
downloaded.
Normally, RPL.NLM will supply the bootstrap program with the file
server information so that it does not need to do a Get Nearest
Server request. Using the GNS parameter may cause the
workstation to find a server other than one where RPL.NLM is
located.
This is mandatory for an SFT III installation.
NODEFAULT
This parameter tells RPL.NLM
not
to respond to a FIND frame
unless the node address of the workstation is found in the
BOOTCONF.SYS file. It is provided for security reasons.
The workstation will
not
boot until the system administrator inserts
- in the BOOTCONF.SYS file - the node address and associated Disk
Image File name(s) to use when booting the workstation.