HIROSS network error

[manunez]

Hello,

I have two Liebert HIROSS HPM interconnected with one LCD panel each in our datacenter.
In total there are 4 cables to interconnect network and these wires go to a switch.
Previously works perfect, we read the temperature of the HIROSS to put on a website and LCD panel was ok.
Now we have changed the switch on the other and now the LCDs do not work and can not get the temperature to the website only sometimes.
By testing I have found that with an isolated switch everything works correctly. And when I connect the switch to which must be connected is not working.
I've changed the 4 network wires, reboot power of 2 machines, reset the switch, 4 IPs changed, ... and the machine is still not working.

Making pings at 4 IPs of HIROSS can see how many packets lost:
PING 192.168.21.21 (192.168.21.21) 56(84) bytes of data.
From 192.168.21.254 icmp_seq=1 Destination Host Unreachable
From 192.168.21.254 icmp_seq=2 Destination Host Unreachable
From 192.168.21.254 icmp_seq=3 Destination Host Unreachable
64 bytes from 192.168.21.21: icmp_req=4 ttl=64 time=2626 ms
64 bytes from 192.168.21.21: icmp_req=5 ttl=64 time=1622 ms
64 bytes from 192.168.21.21: icmp_req=6 ttl=64 time=614 ms
64 bytes from 192.168.21.21: icmp_req=8 ttl=64 time=1920 ms
64 bytes from 192.168.21.21: icmp_req=10 ttl=64 time=0.535 ms
64 bytes from 192.168.21.21: icmp_req=23 ttl=64 time=26.9 ms
64 bytes from 192.168.21.21: icmp_req=42 ttl=64 time=0.517 ms

Any ideas?
I do not know what else I can do.

Thank you very much

[Brian_UK]

Why did you change the switch?

Also, have you replaced the switch with an exact match?

[manunez]

Hi,
We changed the switch because that failed.
The new switch is configured like the previous.

[manunez]

Hello,

This was a example of ping at one IP address.

We have 4 IPs:
- 192.168.21.21 - Icom controller board HIROSS 1
- 192.168.21.22 - Display HIROSS1
- 192.168.21.23 - Icom controller board HIROSS 2
- 192.168.21.24 - Display HIROSS 2

This are 4 examples of ping:

PING 192.168.21.21 (192.168.21.21) 56(84) bytes of data.
64 bytes from 192.168.21.21: icmp_req=1 ttl=64 time=0.543 ms
64 bytes from 192.168.21.21: icmp_req=5 ttl=64 time=925 ms
64 bytes from 192.168.21.21: icmp_req=6 ttl=64 time=1.57 ms
64 bytes from 192.168.21.21: icmp_req=11 ttl=64 time=595 ms
64 bytes from 192.168.21.21: icmp_req=16 ttl=64 time=581 ms

PING 192.168.21.22 (192.168.21.22) 56(84) bytes of data.
64 bytes from 192.168.21.22: icmp_req=1 ttl=64 time=9.44 ms
64 bytes from 192.168.21.22: icmp_req=2 ttl=64 time=0.549 ms
64 bytes from 192.168.21.22: icmp_req=3 ttl=64 time=0.540 ms
64 bytes from 192.168.21.22: icmp_req=4 ttl=64 time=0.544 ms
64 bytes from 192.168.21.22: icmp_req=5 ttl=64 time=0.549 ms
64 bytes from 192.168.21.22: icmp_req=6 ttl=64 time=3.82 ms
64 bytes from 192.168.21.22: icmp_req=7 ttl=64 time=3770 ms
64 bytes from 192.168.21.22: icmp_req=11 ttl=64 time=0.515 ms
64 bytes from 192.168.21.22: icmp_req=12 ttl=64 time=3966 ms
64 bytes from 192.168.21.22: icmp_req=16 ttl=64 time=37.6 ms
64 bytes from 192.168.21.22: icmp_req=17 ttl=64 time=1.64 ms
64 bytes from 192.168.21.22: icmp_req=20 ttl=64 time=954 ms
64 bytes from 192.168.21.22: icmp_req=21 ttl=64 time=7.81 ms

PING 192.168.21.23 (192.168.21.23) 56(84) bytes of data.
64 bytes from 192.168.21.23: icmp_req=1 ttl=64 time=7.30 ms
64 bytes from 192.168.21.23: icmp_req=2 ttl=64 time=0.552 ms
64 bytes from 192.168.21.23: icmp_req=3 ttl=64 time=0.538 ms
64 bytes from 192.168.21.23: icmp_req=4 ttl=64 time=0.625 ms
64 bytes from 192.168.21.23: icmp_req=5 ttl=64 time=4.95 ms
64 bytes from 192.168.21.23: icmp_req=11 ttl=64 time=4030 ms
64 bytes from 192.168.21.23: icmp_req=25 ttl=64 time=19.5 ms
64 bytes from 192.168.21.23: icmp_req=30 ttl=64 time=65.3 ms
64 bytes from 192.168.21.23: icmp_req=31 ttl=64 time=0.519 ms
64 bytes from 192.168.21.23: icmp_req=32 ttl=64 time=0.503 ms

PING 192.168.21.24 (192.168.21.24) 56(84) bytes of data.
64 bytes from 192.168.21.24: icmp_req=1 ttl=64 time=7.53 ms
64 bytes from 192.168.21.24: icmp_req=2 ttl=64 time=0.552 ms
64 bytes from 192.168.21.24: icmp_req=3 ttl=64 time=0.566 ms
64 bytes from 192.168.21.24: icmp_req=4 ttl=64 time=1.49 ms
64 bytes from 192.168.21.24: icmp_req=5 ttl=64 time=0.554 ms
64 bytes from 192.168.21.24: icmp_req=7 ttl=64 time=3.87 ms
64 bytes from 192.168.21.24: icmp_req=8 ttl=64 time=0.554 ms
64 bytes from 192.168.21.24: icmp_req=9 ttl=64 time=0.567 ms
64 bytes from 192.168.21.24: icmp_req=10 ttl=64 time=0.519 ms
64 bytes from 192.168.21.24: icmp_req=11 ttl=64 time=0.528 ms

In these pings you can see that icmp_req how the sequence is cut and takes too long to get the next frame.

Thanks

[Allrounder]

did you resolve this? did you replace the switch with another switch or a hub?

[manunez]

Hello,
Sorry for the delay, but I have not had time until now.
I still have not gotten it to work correctly HIROSS.
This is the machine configurations:

System 1
--- --- ---
Number of units connected - 2
Teamwork mode - No
U2U Group - 1
Secure configuration - OK - No
Config file state - Ok - No
Software version - EVB 1.60.070
IP - 192.168.20.3
Netmask - 255.255.0.0
Gateway - 0.0.0.0
U2U Protocol - GBP
U2U address - 63

System 2
--- --- ---
Number of units connected - 2
Teamwork mode - No
U2U Group - 1
Secure configuration - OK - No
Config file state - Ok - No
Software version - EVB 1.60.065
IP - 192.168.20.4
Netmask - 255.255.0.0
Gateway - 0.0.0.0
U2U Protocol - GBP
U2U address - 64


Unit 1
--- --- ---
Direction for monitoring - 1
U2U Group - 1
Unit Name - UNIT
SNMP listening port - 0
Microface IP address - 0.0.0.0
Monitoring protocol - HIRONET
IP - 192.168.20.1
Netmask - 255.255.0.0
U2U Protocol - GBP
U2U address - 1

Unit 2
--- --- ---
Direction for monitoring - 1
U2U Group - 1
Unit Name - UNIT
SNMP listening port - 0
Microface IP address - 0.0.0.0
Monitoring protocol - HIRONET
IP - 192.168.20.2
Netmask - 255.255.0.0
U2U Protocol - GBP
U2U address - 2

Any idea why this can happen?

Thanks

[RusBuka]

These are screens from ColdFire?

[manunez]

Hello,
I just changed the U2U for 33 and 34, and nothing has changed.
I do not know, but I think it has to be the new switch that supports the communication protocol of the machine, or something.
Any other ideas different?
Thank you very much

[manunez]

I try this change and not found.
These machines have always had a different IP and have been working properly so far.
I don't know what to do more.
Thanks

[Allrounder]

Did you replace the switch with a switch or a hub? if it is a hub and the cables in use are crossed cables it will not work.
also I would use netmask 255.255.255.0 but 255.255.0.0 should work.

[manunez]

We replaced the old switch with other new switch.

[Tiesse]

If the units are on the client network, have you confirmed that their IT guys have given either static IP addresses or reserved the MAC address of each iCOM device to give that MAC addres the required IP address on their network?

If the units are on a DHCP network & this is the 1st time that the units have been removed from the network before reinstating, it could be that another IT device (computer etc) plugged into the client network has taken the IP addresses.

If the units are on their own network, hook a laptop top the network using the same IP range & then sniff the network with Wireshark to identify IP addresses connected to the network.

If yo udo this, you shall be able to identify if the iCOM device Ethernet connections are healthy.