SOI-Spectrum connector does not received Alarms from Spectrum

Document ID : KB000005464
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

On a multihomed windows 2012 or Microsoft 2012 cluster server, the CA SAM Integration Service of the Spectrum Connector server binds to the wrong Network Interface.

Environment:
SOI 4.0 SP2Spectrum Connector 2.0.0.240Spectrum 10.xWindows 2012 ClusterMultihomed Windows 2012 server
Cause:

In windows 2012 with two NIC cards the first Network Card IPAddress is used to bind by the CA SAM Integration Service of the Spectrum Connector server.

In some environments the first NIC is not reachable but the second NIC is the correct one which has to be used for communication.


ping -4 <hostname> returns the ipaddress of the first interface but this is not reachable.

route print will show that the Interface Metric of the first interface is higher than of the second one.

Do a route print and you will see something like this, for example:

                                                                                                Interface Metric
111.111.111.111  255.255.255.255         On-link    111.111.111.111    306
10.10.10.10         255.255.255.255         On-link    110.10.10.10           272

So the Interface Metric on 111.111.111.111 is higher than the Metric on 10.10.10.10

Try again the ping -4 <hostname>, it should return the interface with the highest metric.

If not, and still return the first interface, try adding the ip address with the highest metric to hosts file (C:\Windows\System32\Drivers\etc\hosts).

For this, edit the file, and make sure exist an entry as, and if not, add it and save the file.

111.111.111.111   <hostname>

 where <hostname> is the hostname of the connector machine, and 111.111.111.111 the ip address of the interface with highest metric. The one it should use the connector.

Note:  All IPAddresses mentioned in the case are examples and not from any real environment

 

 

Resolution:

In the properties of your NIC with 111.111.111.111 , Internet Protocol Version 4 (TCP/IPv4) , Advanced...
uncheck "Automatic metric" and put 1 as the value.


Do a route print again, now you should have something like as:

                                                                                                 Interface Metric
111.111.111.111  255.255.255.255         On-link    111.111.111.111    251
10.10.10.10         255.255.255.255         On-link    10.51.0.2           272

Restart the CA SAM Integration Service

Doublecheck with

netstat -an | findstr 14001

that the correct IPAddress 10.10.10.10 is now used.

Note:  All IPAddresses mentioned in the case are examples and not from any real environment

Additional Information:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/de4492d9-75ca-4586-94f9-c0f959c02c75/ping-at-wrong-address?forum=winserverNIS