Lenovo ThinkAgile CP, Hardware Part Replacement And Component Maintenance Procedures

Page: 129 / 162

Interconnect switch maintenance procedures
This section covers the ThinkAgile CP interconnect switch maintenance procedures.
Refer to Chapter 2 “Roles and responsibilities” on page 15 to determine who can perform these procedures.
Power off the interconnect switch in an SS-V3 environment
This section covers the procedure to power off the interconnect switch in an SS-V3 environment.
Procedure performed by
: Solution administrator
Execution
: On hardware only (with exceptions for procedures dependencies)
Since inter-component communication is not possible while the interconnect is not operational, all hardware
components and VMs must be shut down.
To power off the interconnect switch in an SS-V3 environment, follow these steps:
Step 1. Sign in as an infrastructure administration into the Cloud Controller portal.
Step 2. Navigate to
Infrastructure
➙
Hardware
.
Step 3. Select the stack in the top tab. It lists all hardware connected to the interconnect switch.
Step 4. Perform the “Shutting down the storage block” on page 35 procedure. This shuts off the storage
block in the stack that you have selected, and will ask to shut down the VMs as well.
Step 5. Perform the “Shutting off a compute node” on page 85 procedure to shut off the compute node in
the selected stack.
Step 6. Sign in to the primary interconnect via Support Mode or, if at the data center, with a method
provided by the manufacturer. The username is
admin
and the password is the one you set during
the installation
Step 7. Execute the following command:
> > ssu ud do o ssh hu uttd do ow wn n --h h n no ow w
The interconnect switch can now be unplugged safely.
Make the secondary interconnect switch the primary interconnect
Procedure for making the secondary ThinkAgile CP interconnect switch into the primary interconnect.
Attention:
You have between 6 and 12 hours to fix the primary interconnect before you notice network
connectivity problems, as that is the default lease time of the DHCP server. If you cannot replace the
interconnect or DHCP server within 6 to 12 hours, you should attempt to make existing DHCP users static
IPs.
• If the primary interconnect is still accessible, back up
/etc/dhcp/dhcp-failover.conf
.
• If the primary interconnect is still accessible, back up
/var/lib/dhcp/dhcpd.leases
) and hardware
management network settings in
/etc/dhcp/vlan-mgmt.conf
and
/etc/dhcp/vlan-main.conf
.
• Obtain the hardware management network settings (BMC_ DHCP_START, BMC_DHCP_END, BMC_
ROUTER_IP, BMC_PREFIX) from the primary network interconnect (if still accessible) or from the
customer install journal. These settings are not backed up in the Cloud Controller. If these settings are not
available, pick a new range for this network (for example, 10.65.0.0/24) since it is internal to the network
stack.
Chapter 5
.
Part replacement and maintenance procedures
121