Targets on the shared-memory network can boot using BOOTP only if proxy ARP is enabled (see Proxy ARP Overview). A target on the shared-memory network keys its entry in the BOOTP database by its IP address. A shared-memory network target's entry in the BOOTP database looks something like:

vx232:ip=150.12.1.232:tc=global.dummy

A shared-memory network's master entry in the BOOTP database looks like:

vx230:ht=ethernet:ha=0000530e0018:ip=150.12.1.230:tc=global.dummy

The following example is a master processor using a combination of BOOTP, TFTP, proxy ARP, sequential addressing, and proxy default addressing for booting:¹

    [VxWorks Boot]: @ 
    boot device        : ln 
    processor number   : 0  
    flags (f)          : 0xc0  
 
    Attaching network interface ln0... done. 
    Getting boot parameters via network interface ln0. 
    Bootp Server:150.12.1.159  
[1]        Boot file: /usr/wind/target/vxBoot/vxWorks.vx230  
[1]        Boot host: 150.12.1.159  
[1]        Boot device Addr (ln0): 150.12.1.230 
[1]        Subnet mask: 0xffffff00 
    Attaching network interface lo0... done. 
    Loading... 370356 + 28040 + 20196 
    Starting at 0x1000...

 
[2]    Host Name: bootHost  
[2]    Target Name: vxTarget  
[2]    User: target  
    Attaching network interface ln0... done. 
    Initializing backplane net with anchor at 0x800000... done. 
    Backplane anchor at 0x800000... Attaching network interface sm0... done.

 
[3]    Backplane address: 150.12.1.231  
    Creating proxy network: 150.12.1.231 
    Attaching network interface lo0... done.

The parameters from the preceding output came from the following sources:

[1] These lines all display information retrieved from the BOOTP database.

[2] These lines display information you set during configuration (defaults).

[3] These lines appear because you have configured VxWorks with "proxy arp server," "auto address setup," and "default address for bp" (the configuration macros INCLUDE_PROXY_SERVER, INCLUDE_SM_SEQ_ADDR, and INCLUDE_PROXY_DEFAULT_ADDR). (Note that the address is one more than that of parameter inet on ethernet, in this case 150.12.1.230.)

The following example shows booting a slave processor using a combination of BOOTP, TFTP, and sequential addressing:

    [VxWorks Boot]: @ 
    boot device        : sm=0x800000 
    processor number   : 1  
    flags (f)          : 0x1c0  
 
    Backplane anchor at 0x800000... Attaching network interface sm0... done.

 
[1]    Backplane inet address: 150.12.1.232 
    registering proxy client: 150.12.1.232.done. 
    Getting boot parameters via network interface sm0. 
    Bootp Server:150.12.1.159 
[2]    Boot file: /usr/wind/target/vxBoot/vxWorks.vx232 
[2]    Boot host: 150.12.1.159 
[2]    Subnet mask: 0xffffff00 
    Attaching network interface lo0... done. 
    Loading... 370356 + 28040 + 20196 
    Starting at 0x1000... 
[3]    Host Name: bootHost  
[3]    Target Name: vxTarget  
[3]    User: target  
    Backplane anchor at 0x800000... Attaching network interface sm0... done. 
    Attaching network interface lo0... done.

The parameters from the preceding output came from the following sources:

[1] These lines appear because you have configured VxWorks with "proxy arp client" and "auto address setup" (the configuration constants INCLUDE_PROXY_CLIENT and INCLUDE_SM_SEQ_ADDR)² . (Note that the address is equal to the master CPU's backplane address plus the client's processor number.)

[2] These lines all display information retrieved from the BOOTP database.

[3] These lines display information you set during configuration(defaults).

1:  The use of sequential addressing can make it difficult to use DHCP.

2:  The use of sequential IP addressing makes this procedure incompatible with DHCP.