• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Syslogging and IP conflict

Joined
Nov 22, 2011
Messages
4
Hi All

Issue when trying to syslog using Kiwi Syslog Server.

Using ESXi4 embedded, set up syslogging but only 3 of the 4 hosts are showing. Checked into everything and have found out that the IP address assigned to Host 1 is the same IP address used for the Management Network.
I am surprised this has not caused any issues but has only come to light when setting up syslog.

Can any of you guys offer any advice on how to get around this without changing the IP address of the Host 1 as its a lot of work to migrate everything to change the network settings. Cant the management IP be changed safelty while all the 4 hosts and their VM's are running? Downtime and a performance hit are especially to be avoided but I realise that changing the Host IP is the simpliest.

Im just looking for possible problems this IP address being used by both the host and management network could cause, and any advice on an alternate way round this would be most appreciated

Many thanks

Regards

John
 
Not sure what you're saying here. Can you post a screenshot or two of your network config on that host?
 
Hi Netjunkie

Config is as follows:

Host 1 - 10.1.4.10
Host 2 - 10.1.4.11
Host 3 - 10.1.4.12
Host 4 - 10.1.4.13

Management Network Host 1 - 10.1.4.10 (vmk0)
Management Network Host 2 - 10.1.4.11 (vmk0)
Management Network Host 3 - 10.1.4.12 (vmk0)
Management Network Host 4 - 10.1.4.13 (vmk0)

VMKernel Host 1 - 10.1.5.10 (vmk1)
VMKernel Host 2 - 10.1.5.11 (vmk1)
VMKernel Host 3 - 10.1.5.12 (vmk1)
VMKernel Host 4 - 10.1.5.13 (vmk1)

This doesnt seem right to me. When I syslog the 4 hosts, 2, 3 and 4 all report but Host 1 wont syslog for some reason (has a scratch config set) and points to the correct syslog server. The other thing i noticed is that i connect to the host via Syslog, but the IP address it displays is the VMKernel IP address (10.1.5.11) for each host. Not the IP address (10.1.4.11) as you would expect. This doesnt seem right to me. The upshot is all i want to do is to be able to Syslog host 1, all other 3 hosts syslog fine. Just not entirely sure this setup i have inherited was done by best practise

spravtek - thanks for your reply. I have read through but still leaves me with an uneasy feeling. Following your link I have read a couple more and keep coming across this "You can change the addres and subnet of an existing service console. Remember that when doing so you network connection will be terminated."

This is certainly to be avoided if possible. So it would seem i need to migrate the vms off before changing the management IP which was what I was trying to avoid. But if it must it must. Have you made these changes before yourself?

Thanks guys for answers, this forum is one of the better ones when it comes to activity and general expertise. Glad I joined and hopefully will be able to contribute on my areas, im playing catchup with VMware at the moment :)

Regards

John
 
Back
Top