Filter
Top Products
342 APPENDIX B: AUTOMATED BRANCH OFFICE INSTALLATION
Sample DHCP Configuration File (continued)
option subnet-mask 255.255.255.0;
The previous line defines the subnetwork mask for the branch office
network.
CHANGE FOR EACH BRANCH: Most likely, the same subnetwork mask
is used in each of the branch offices. Change this setting only if branch
offices use different subnetwork masks.
option vendor-class-identifier "3Com-VCX-7200-7.0.1c";
The previous line defines the vendor class identifier string sent by the VCX
server in the branch office when it sends a DHCP request. The string for
BRANCH_CALLP changes with each VCX software release. For example,
on a server running release 7.0.3c, 3Com-VCX-7200-7.0.3c would be
used.
option host-name "branch-21";
The previous line defines the host name that you want to assign to the
VCX branch office server.
NOTE: These host names are not posted to any DNS servers.
CHANGE FOR EACH BRANCH: The host name must be unique for each
branch office VCX server.
option domain-name "yourcompany.com.";
The previous line defines the domain name that you want the branch
office server to use.
option bootfile-name "/tftpboot/VCXConfiguration21.xml";
The previous line defines the pathname of the configuration file that will
be transferred from the TFTP server to the VCX server. The file is used to
configure the VCX server.
CHANGE FOR EACH BRANCH: Each branch office is configured slightly
differently, and each VCX server must have a unique configuration file on
the TFTP server.