Programming instructions

32
3300 ICP Technician’s Handbook
5. In the DHCP Options form, program the options listed in Table 78 on
page 301 for the scope you just programmed. Always create the
following options:
- 3 Router, IP address
- 125 Vendor-Identifying Vendor-Specific Information or Option 43
Vendor Specific Information. Option 125 is the preferred option.
- 66 TFTP Server, IP address format
- 67 Boot file, string value (always /sysro/E2T8260)
If there are 5230 IP Appliances, create the following options:
- 6 DNS Server, IP address format
- 44 NetBIOS Name Server, IP address format
6. In the DHCP Options form, for a cluster environment, program IP
Console (if any) with a static IP Address. Then, do the following:
Program Option 125 (preferred) or Option 43 with:
- Format: ASCII String
- Value: IP Address of the controller that controls the device and
different VLAN tagging and priority information if needed for the
console
- Scope: Static: <device name><subnet>.
Assign the address Option 125 (or 43) as above, specifying different
VLAN tagging and priority information if needed for the console.
Tip: The following IP addresses are reserved to provide backward
compatability for legacy AMBs and ASUs:
192.168.10.1 to 192.168.10.15 through 192.168.13.1 to 192.168.13.15
The ASU II and legacy AMBs and ASUs with upgraded firmware use the
following reserved addresses:
169.254.10.0 to 169.254.10.15 through 169.254.19.0 to 169.254.19.15
Note: IP sets require a firmware upgrade to support the new DHCP
options introduced in Release 7.0; otherwise, the sets will fail to boot. Such
failures can occur, for example, in a resilient cluster of mixed software
releases or when sets with old firmware are added to a controller after it
was upgraded to Release 7.0. For the sets to boot, DHCP options 128-133
must be present in the DHCP server. After the sets have booted, options
128-133 may be removed to avoid future conflicts with standard use or
other vendors’ use of these options.