Unsolved
This post is more than 5 years old
4 Posts
0
1618
October 11th, 2019 10:00
Web GUI not responding
Evening folks,
We're having a weird problem with OME 3.2.1 (Build 29). It's been working fine until we changed our firewall to a SonicWall 12K (something) and now the OME virtual appliance won't respond to traffic that transits that firewall. I can see the SYN packets arriving at the VM network interface but it never replies. Using a VM running a browser on the same subnet (i.e. not passing through the firewall) works absolutely fine. In addition, I can no longer reliably update my Dell Server estate, or get status or inventory information from them. Sometime it works, mostly not. Again, these iDRACs are on a subnet that transits the new firewall...
I'm thinking that the packet is somewhat mangled, and is being discarded by the linux TCP stack (like martians or bogons) but I can't get at the log files to diagnose this.
has anyone seen anything like this before? Does anyone know how to get at the log files?
0 events found
Daniel My
12 Elder
•
6.2K Posts
1
October 11th, 2019 12:00
Hello
There is a port list in the OMEnt documentation. It sounds like you need to add some exceptions.
http://www.dell.com/openmanagemanuals/
Thanks
ianangles
4 Posts
0
October 12th, 2019 06:00
Hey Daniel,
Thanks for replying so quickly. So, the firewall was effectively open to/from this host (I'd rather not get into why just now:-) but I asked for those ports to be opened anyway. They have been, but still no difference.
I used the VMware vDS port mirroring feature to look at what's arriving at the VM - and from destinations outside the firewalled subnet I can see the SYN packets turning up - but no reply is sent, not even a RST - hence I'm thinking that the appliance is just dropping the packets without any further processing.
ian
---
ianangles
4 Posts
0
October 12th, 2019 06:00
Also, I deployed the latest version of the appliance last night on a different IP, same subnet with exactly the same behaviours. (could've been bit rot in the first appliance...)
ianangles
4 Posts
0
October 17th, 2019 03:00
So, it turns out that if you mistype the default router address - this kind of stuff happens
In my defence, the network engineer checked it as well and he didn't pick it up. (and 5 can look like 6 under certain conditions - right?)
Everything is now working fine and thanks to Danial for the advice.
ian
---