Unable to access gateway with ssh after upgrade to latest platform patch
search cancel

Unable to access gateway with ssh after upgrade to latest platform patch

book

Article ID: 279402

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

Unable to access appliance gateway's  after patching to 10.1CR4 and latest platform patch.

We can connect using the vmware remote console but not by using  ssh.

Environment

10.x

Cause

Client has multiple nic's and some where only configure by name on reboot they got connected in the wrong sequence

There is a difference in the network interface configuration script located in /etc/sysconfig/network-scripts/ for working and non working nodes

On nodes that have succesfully started, the config file is like this:

$ more ifcfg-ssg_eth0
HWADDR=xx:xx:xx:xx:xx:xx
NAME=ssg_eth0
DEVICE=ssg_eth0
TYPE=Ethernet
BOOTPROTO=none
IPV6INIT=no
ONBOOT=yes
USERCTL=no
PEERDNS=no
IPADDR=
NETMASK=
GATEWAY=

On the node that became inaccessible, the configuration is like this:

$ more ifcfg-ssg_eth0

NAME=ssg_eth0
DEVICE=ssg_eth0
TYPE=Ethernet
BOOTPROTO=none
IPV6INIT=no
ONBOOT=yes
USERCTL=no
PEERDNS=no
IPADDR=
NETMASK=2
GATEWAY=

The problem interface is not binding to the correct nic by using is HW Address.

Resolution

The ssgmenu should create the network config with the hardware address, if this is not the case you can as a workaround add the mac address so it will bind to that mac.

ifconfig -a will show the current  mac address.

Add this to the  network config file to bind to the correct nic.

HWADDR=xx:xx:xx:xx:xx:xx