We deployed the OMIMSSC 7.2 using the provided OVA on ESXi 6.5. After performing the initial configuration provding admin password and netword details we were able to proceed via the web interface.
After some time the web interface became unavailable and after some investigation we realised that the appliance seem to lose the network connectivity every couple of minutes. Using a continous ping we saw that after around five minutes the network becomes available again. Just to repeat the same process after another three minutes.
We tried to use a different ip address on a different VLAN with no luck. We deployed the OVA again just to see the same behaviour and also replaced the E1000 network adapter with a vmxnet3 one. No difference
Using the web interface is impossible this way.
Has anybody seen a similar behaviour and a solution for it ?
Here is an update on the issue. I was on a session with development and they couldn't help. After the call we realized that, although a static ip address was configured, the device uses DHCP. The option is called " " and once we changed that to " " everything works as expected.
Unfortunately there is nothing in the documentation and to us this is clearly a bug in the UI. We've never seen a system that allows you to specify an ip address when it is it set for DHCP.
I've logged on using user readonly and performed the ping test to the gateway address. At the same time I had a ping running from my computer to the configured ip address of the appliance. Once my computer did not receive any more replies, the runnning ping in the remote console stopped working as well: ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ...
After a couple of minutes the ping replies report back ok in both the console and on my computer.
We have 60 ESX hosts and around 1300 running VMs. Moving the VM to another host or another VLAN would not make a difference and I've not seen such a behavior on any of the other systems.
All tests were done using the default E1000 network adapter.
I've opened a support request and got already some feedback. We were doing more tests using the appliance on Hyper-V and interestingly enough it shows exactly the same behaviour. We tested different network settings and both environments seem to have the same issue. We can also see lots of Java/Tomcat errors in the log files and I therefore suspect that there is something going inside the system that causes that problem. Since we don't have access to the messages.log file we cannot investigate further.
Dell support just told me that the case is now with level 3 support
Thorsten_S
1 Rookie
•
45 Posts
1580
0
Posted October 16th, 2020 04:00
Here is an update on the issue. I was on a session with development and they couldn't help. After the call we realized that, although a static ip address was configured, the device uses DHCP. The option is called " " and once we changed that to " " everything works as expected.
Unfortunately there is nothing in the documentation and to us this is clearly a bug in the UI. We've never seen a system that allows you to specify an ip address when it is it set for DHCP.
Thanks