API Gateway: Having issue with external NIC mapped on GW10 server

Products

• CA API Gateway
• API SECURITY
• STARTER PACK-7

Issue/Introduction

We have recently upgraded to Gateway v10 in our QA cluster. We have completed all the configuration steps and added them on the load balancer. While adding the servers to the DMZ, one of the servers is unresponsive. We are not able to ping the NIC from SERVER2 but we can ping SERVER1 from SERVER 2.

In the Network Configuration menu, ssg_eth1 on SERVER2 is not visible.

When we go to below steps, there are 3 network interfaces. 

1) Configure system settings
1) Configure networking and system time settings

Available network interfaces available for configuration.

1) ens192
2) ssg_eth0
3) ssg_eth1
4) configure unlisted interface
Please select an interface to configure:

Environment

API Gateway 10.0 with multiple Network Interfaces

Cause

The ifcfg-ssg_ethX configuration file(s) on the non-working server are missing one or more parameters.

Resolution

Compare the ifcfg-ssg_ethX file(s) from the working server with the one on the non-working server. The required parameters are HWADDR, NAME, UUID, DEVICE. If any of these are missing, add them to the appropriate file and restart the appliance.

Additional Information

REF: Installing Additional Network Interfaces to An Existing Gateway 10.x Appliance on CentOS 7