IBM Security Verify

Hello everyone,

I am dealing with an unusual behavior from my ISAM lab environment. 

My environment has a VM running ISAM 9.0.6 and and another VM running ISVA 10.0.6 (recently upgraded from 9.0.6) using VMWare Workstation. It should be noted that both VMs were functioning properly for a few months (pre-upgrade). The application interface IP address is used in WebSEALs and AAC in both VMs. 

The issue occurred after a restart of the VM running ISVA, afterwards sending requests to the WebSEALs or AAC whether it be by browser or through API (Postman was used here) was met with a connection refused error. At first I assumed the issue may have been a side-effect from the upgrade so i tried sending requests to ISAM 9.0.6 and met with the same problem.

I can reach the IP addresses used for the management interface and I can ping the non-management IP addresses that were refusing requests but telnet was not successful. Another point is that at most I can send only 1 request through before further requests get rejected. I have tried using a different device to send requests and it worked for while but now suffers from the same issue.

Thanks for your advice and suggestions. 

Check that your interfaces did not swap.  I've seen this in VMWare environments before.  The MAC/hardware address on the NIC changes at the virtualization side, and all of a sudden interface 1.1 and 1.2 (or others) are swapped and you're left scratching your head what's going on.  You should be able to quickly verify this under /isam/net#ifaces and make sure they are on the expected networks.

Hello everyone,

I am dealing with an unusual behavior from my ISAM lab environment. 

My environment has a VM running ISAM 9.0.6 and and another VM running ISVA 10.0.6 (recently upgraded from 9.0.6) using VMWare Workstation. It should be noted that both VMs were functioning properly for a few months (pre-upgrade). The application interface IP address is used in WebSEALs and AAC in both VMs. 

The issue occurred after a restart of the VM running ISVA, afterwards sending requests to the WebSEALs or AAC whether it be by browser or through API (Postman was used here) was met with a connection refused error. At first I assumed the issue may have been a side-effect from the upgrade so i tried sending requests to ISAM 9.0.6 and met with the same problem.

I can reach the IP addresses used for the management interface and I can ping the non-management IP addresses that were refusing requests but telnet was not successful. Another point is that at most I can send only 1 request through before further requests get rejected. I have tried using a different device to send requests and it worked for while but now suffers from the same issue.

Thanks for your advice and suggestions. 

I've checked the interfaces and nothing seems to be out of order. I'm only using 1.1 interface (the IPs are within the same sub net, of course). Is there something else I need to check?

Thanks for your help.

Check that your interfaces did not swap.  I've seen this in VMWare environments before.  The MAC/hardware address on the NIC changes at the virtualization side, and all of a sudden interface 1.1 and 1.2 (or others) are swapped and you're left scratching your head what's going on.  You should be able to quickly verify this under /isam/net#ifaces and make sure they are on the expected networks.

Hello everyone,

I am dealing with an unusual behavior from my ISAM lab environment. 

My environment has a VM running ISAM 9.0.6 and and another VM running ISVA 10.0.6 (recently upgraded from 9.0.6) using VMWare Workstation. It should be noted that both VMs were functioning properly for a few months (pre-upgrade). The application interface IP address is used in WebSEALs and AAC in both VMs. 

The issue occurred after a restart of the VM running ISVA, afterwards sending requests to the WebSEALs or AAC whether it be by browser or through API (Postman was used here) was met with a connection refused error. At first I assumed the issue may have been a side-effect from the upgrade so i tried sending requests to ISAM 9.0.6 and met with the same problem.

I can reach the IP addresses used for the management interface and I can ping the non-management IP addresses that were refusing requests but telnet was not successful. Another point is that at most I can send only 1 request through before further requests get rejected. I have tried using a different device to send requests and it worked for while but now suffers from the same issue.

Thanks for your advice and suggestions. 

In the AAC runtime configuration where you configure the network interfaces to be used by the AAC runtime, (re) submit the configuration and restart the runtime. That might solve your problem.

Kind regards

Serge Vereecke (IBM)

I've checked the interfaces and nothing seems to be out of order. I'm only using 1.1 interface (the IPs are within the same sub net, of course). Is there something else I need to check?

Thanks for your help.

Check that your interfaces did not swap.  I've seen this in VMWare environments before.  The MAC/hardware address on the NIC changes at the virtualization side, and all of a sudden interface 1.1 and 1.2 (or others) are swapped and you're left scratching your head what's going on.  You should be able to quickly verify this under /isam/net#ifaces and make sure they are on the expected networks.

Hello everyone,

I am dealing with an unusual behavior from my ISAM lab environment. 

My environment has a VM running ISAM 9.0.6 and and another VM running ISVA 10.0.6 (recently upgraded from 9.0.6) using VMWare Workstation. It should be noted that both VMs were functioning properly for a few months (pre-upgrade). The application interface IP address is used in WebSEALs and AAC in both VMs. 

The issue occurred after a restart of the VM running ISVA, afterwards sending requests to the WebSEALs or AAC whether it be by browser or through API (Postman was used here) was met with a connection refused error. At first I assumed the issue may have been a side-effect from the upgrade so i tried sending requests to ISAM 9.0.6 and met with the same problem.

I can reach the IP addresses used for the management interface and I can ping the non-management IP addresses that were refusing requests but telnet was not successful. Another point is that at most I can send only 1 request through before further requests get rejected. I have tried using a different device to send requests and it worked for while but now suffers from the same issue.

Thanks for your advice and suggestions.