Znyx Networks bh5700 Manuale Utente
"zsp.primary.conf";
}
host SECONDARY {
fixed-address 100.0.0.31;
option dhcp-client-identifier
"SECONDARY";
option vendor-encapsulated-options
"zsp.secondary.conf";
}
}
The zsp.primary.conf and zsp.secondary.conf files must be placed in the tftp
location on the machine, often /tftpboot. The zsp.primary.conf and
zsp.secondary.conf files can be retrieved from the Surviving Partner switches. This is the
configuration that will be given to the switches. It is recommended that the zsp.conf be taken
from the primary as follows:
location on the machine, often /tftpboot. The zsp.primary.conf and
zsp.secondary.conf files can be retrieved from the Surviving Partner switches. This is the
configuration that will be given to the switches. It is recommended that the zsp.conf be taken
from the primary as follows:
The zsp.conf file created by hand on the primary is moved to /tftpboot/zsp.primary.conf on
the Central Authority.
the Central Authority.
Move /tftpboot/zsp_DC.conf.1 file on the primary created by zspconfig to
/tftpboot/zsp.secondary.conf on the Central Authority.
/tftpboot/zsp.secondary.conf on the Central Authority.
Create dhclient.conf files on the Surviving Partner switches. Examples can be found in
/etc/rcZ.d/surviving_partner/dhclient.conf. As an example:
/etc/rcZ.d/surviving_partner/dhclient.conf. As an example:
send dhcp-client-identifier "ZNYX";
request vendor-encapsulated-options;
require vendor-encapsulated-options;
Modify the dhclient.conf file on the primary switch as follows:
send dhcp-client-identifier "PRIMARY";
request vendor-encapsulated-options;
require vendor-encapsulated-options;
Modify the dhclient.conf file on the secondary switch as follows:
send dhcp-client-identifier "SECONDARY";
Ethernet Switch Blade User's Guide
release 3.2.2j
page 44