Recovering From Dns Misconfiguration; Recabling Management Switch From Primary - Lenovo ThinkAgile CP Part Replacement And Component Maintenance Procedures

If you were unable to copy /etc/dhcp/dhcp-failover.conf from the primary interconnect, create it
Step 4.
with the following content.
failover peer "failover-partner" {
primary;
address 100.64.253.1;
port 647;
peer address 100.64.253.2;
peer port 647;
max-response-delay 60;
max-unacked-updates 10;
auto-partner-down 1;
mclt 120;
split 255;
load balance max seconds 3;
}
Step 5. Disconnect the hardware management network cable from the former primary interconnect and
connect it to the current primary (former secondary) interconnect.
Figure 49. Recabling management switch from primary to secondary interconnect
Step 6. Start the DHCP server in the new primary interconnect with the following command:
> > s s u u d d o o s s e e r r v v i i c c e e i i s s c c - - d d h h c c p p - - s s e e r r v v e e r r s s t t a a r r t t

Recovering from DNS misconfiguration

When specifying DNS settings for the first time, specifying incorrect DNS settings can cause issues with DNS
resolution
If this happens, do not attempt to rerun the script v3/tacp_switch_config_v3.
Important: This procedure can be performed only by Lenovo Professional Services.
To recover from DNS misconfiguration, follow these steps:
Update /etc/tacp/tacp_switch_resource.sh with the correct DNS IP address on both interconnect
Step 1.
switches:
### Hardware management network DHCP configuration ###
BMC_DHCP_START=10.103.31.2
BMC_DHCP_END=10.103.31.253
BMC_ROUTER_IP=$BMC_VLAN_IP
BMC_PREFIX=$BMC_VLAN_IP_PREFIX
DNS=10.0.64.10
#SWITCH_HA="DS-V3"|"SS-V3"
SWITCH_HA="DS-V3"
.
Chapter 7 Interconnect switch maintenance procedures
79