Overview

You may need to reset an FWL node; for example, after running a Health Check and finding it has been up and running for a long time (e.g., more than a year), which is not recommended. This article details the steps to create a backup and reboot an FWL node.

Requirements

• VPN Access to the End-User System
• Release 12.4.1

Hardware Check

Before any reboot, the hardware needs to be checked to make sure no hardware issue might affect the reboot. To do so, run the following commands as root (the command could also be hpssacli):

# hpacucli ctrl all show config
# hpacucli ctrl all show config detail

For any failure found, inform the end-user about it so they can check it before planning a reboot.

You can access the iLO GUI to check the status of all the hardware and any alarm in iLO and IML logs. If you cannot access the iLO GUI or SSH to the iLO IP,  it will need to be verified with the hardware support and network teams. The iLO access will be required in case there are any issues with the reboot because the server can still be accessed via console.

Process

FWL Backup and Reboot

Reboot one FWL node at a time since it is handling traffic. Do not proceed to the next FWL node if the reboot is not finished yet for the first FWL or if there is an issue after the reboot.

1. Copy important files to another server or external PC.

   1. As a TextPass user, copy the content of the directories below. There are hidden files, so please use the a option in the ls command to see the content.

      • /usr/TextPass/etc/

      • /usr/TextPass/.store/

   2. As root user, copy the route and ifcfg files in /etc/sysconfig/network-scripts/.

2. As TextPass user, save the output of the commands below.

   1. $ tp_status

   2. $ m3ua_link

   3. $ tp_walk –tp_pbc pbcDiamTransportGroupTable

   4. $ tp_walk –tp_pbc pbcDiamTransportTable

   5. $ netstat -rn

   6. $ ifconfig -a

   7. $ cat /etc/fstab

   8. $ cat /etc/mtab

3. As TextPass user, stop the NMM process.

   1. $ tp_status

   2. $ tp_stop

   3. $ tp_status

   4. $ stv_poller --status

   5. $ stv_poller --stop

4. As root user, reboot the server.

   # init 6

5. After reboot, check the status of the NMM node as TextPass user.
   

   1. $ tp_status

   2. $ stv_poller --status

6. Check system logs for any persistent error.

   # tail -f /var/log/messages

7. Check the command output of step 2.

   For PBC, the admin state should be active.

Confirmation

1. Check system logs for any persistent error.

2. Check if LGP is running the collector.

   # tail -f /var/log/messages

3. Check the MySQL process as a root user.

   1. # service mysql status

   2. # ps -ef | grep -i sql

Back to top