Contents

1   Front End Management Tool Introduction

This instruction describes how to set up the VIP Front End Management Tool to create, delete, or move VIP Front End Elements (FEE) in the SAPC.

Front ends are the elements used by VIP to communicate externally the SAPC with other nodes. During an installation, these front ends are added by the Adapt Cluster Tool. The VIP front ends are added by the Adapt Cluster Tool at installation phase. The VIP Front End Management Tool adds front ends during an expansion or in case more front ends are needed at any other point.

2   Front End Management Tool Prerequisites

Before starting this procedure, ensure that the following conditions are met:

• Good understanding and knowledge about networking and routing, as well as VIP component.
• Good understanding and knowledge about the SAPC networking.
• General knowledge about Linux systems and shell commands.

3   Front End Management Tool

3.1   Front End Management Tool Purpose

The purpose of Front End Management Tool is to create, move or delete front ends from a running SAPC deployment without traffic disturbance. Every traffic payload is connected to the external network, but without front ends, no traffic can be processed by the payload. Payloads with front ends have more overhead than the others so it is good to have more front ends depending on the number of payloads in the cluster.

3.2   Front End Management Tool Parameters

Main parameters come from VIP as they are used to configure the new front ends. Those parameters explained as "VIP configuration parameters" imply special VIP knowledge and in case there is a need to modify them, follow VIP documentation.

3.3   Front End Management Tool Modes

1. Logon on in the SAPC as "root" userId, the system administrator must use:

   Terminal: # ssh root@<OAM VIP> -p <COM Port>

   where <OAM VIP> is the SAPC VIP OAM

   and <COM Port> is normally 830

   ssh root@10.42.118.235 -p 830

2. SC-X: # sapcFeeManagement <mode> <source_alb> <source_fee> <source_node> <destination_node>

Execute the tool from the system controller which accesses to the COM.

Five modes are available: move, dump, create, delete, and show.

3.3.1   Move Mode

Moves the front end from the <SOURCE_NODE> to the <DESTINATION_NODE>. Copies all the VIP configuration parameters from one node to the other one. It can be done with traffic as there is no need to use cluster reboot for the configuration to be in place. Keep in mind though that the <DESTINATION_NODE> needs the external networking ready (specially important in NSP deployments).

SC-1:# sapcFeeManagement move alb_trf fee_1 3 7

3.3.2   Dump Mode

Dumps the info related to the <ALB>, <FEE>, and <SOURCE_NODE> into a file called sapcFeeManagement.cfg. This file can be used as template to add a new VIP front end.

SC-1:# sapcFeeManagement dump alb_trf fee_1 3

3.3.3   Create Mode

Creates a front end with the values explained in the file sapcFeeManagement.cfg.

This is the most complex scenario as you need to add all the values of the table, specially the configuration parameters. Normally one front end is used as template by executing the dump mode.

Check that the values are correct before applying it but some hints are explained here.

• EXTERNAL_INTERFACE, EVIP_SUPERVISED_REMOTE_GATEWAY and EVIP_SUPERVISED_REMOTE_GATEWAY2 could change depending on to which gateway the payload is connected to. But if the payload is connected to the same router as the reference one used in the dump command, these values do not change.
• OSPF_LOCAL_ADDRESS and OSPF_ROUTER_ID need spare values in the specific network where the front end is added.
• The rest of parameters normally are equal to the values of existing front ends.

SC-1:# sapcFeeManagement create

3.3.4   Delete Mode

Deletes an existing front end specified by SOURCE_ALB, SOURCE_FEE and SOURCE_NODE.

SC-1:# sapcFeeManagement delete alb_trf fee_1 3

3.3.5   Show Mode

Similar as dump mode, but the info is shown through the console.

SC-1:# sapcFeeManagement show alb_trf fee_1 3