patron
asked on
Config to be preserved before we upgrade esxi 4.1 to 5.1
I am upgrading my existing Esxi 4.1 to 5.1...have some queries regarding config to be preserved ..
1. we are using syslog server for esxi 4.1 ,is there something we have to check before upgrading host or we have to apply after host upgrade ?
2.form where we have to locate/set sys log config on esxi 4.1 and 5.1
3.any other config we have to preserver before upgrading host which we have to configure again after host is upgraded to 5.1?
like NTP Config,log rotation, security hardening in esxi,San related/Network related ...
1. we are using syslog server for esxi 4.1 ,is there something we have to check before upgrading host or we have to apply after host upgrade ?
2.form where we have to locate/set sys log config on esxi 4.1 and 5.1
3.any other config we have to preserver before upgrading host which we have to configure again after host is upgraded to 5.1?
like NTP Config,log rotation, security hardening in esxi,San related/Network related ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i can see after upgrade logs are not going to syslog server , where i have to check for syslog config on my esxi 5.1 ?
where to check for firewall rules in esxi 4.1/5.1 ?
where to check for firewall rules in esxi 4.1/5.1 ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
esxcli network firewall get -output for this command on esxi 5.1..
esxcli network firewall get
Default Action: DROP
Enabled: true
Loaded: true
how to check this in esxi 4.1 ?
and for syslog.conf..
in esxi 4.1...
/etc # cat syslog.conf
logfile=/vmfs/volumes/8888 8888-99999 9999-0000- e4e4e4e4e4 e4/log/mes sages
loghost=192.168.1.15
while on esxi 5.1
esxcli system syslog config get
Local Log Output: /scratch/log
Local Logging Default Rotation Size: 1024
Local Logging Default Rotations: 8
Log To Unique Subdirectory: false
Remote Host: 192.168.1.15
please advice what else to be checked/configured, as after upgrade no logs going to sys log server?
esxcli network firewall get
Default Action: DROP
Enabled: true
Loaded: true
how to check this in esxi 4.1 ?
and for syslog.conf..
in esxi 4.1...
/etc # cat syslog.conf
logfile=/vmfs/volumes/8888
loghost=192.168.1.15
while on esxi 5.1
esxcli system syslog config get
Local Log Output: /scratch/log
Local Logging Default Rotation Size: 1024
Local Logging Default Rotations: 8
Log To Unique Subdirectory: false
Remote Host: 192.168.1.15
please advice what else to be checked/configured, as after upgrade no logs going to sys log server?
check advanced settings, in ESXi with vSphere Client, to check Syslog Server IP Address is correct.
ASKER
yes , that ip is as same as it was on esxi 4.1,but no logs there on syslog server after upgrade
check firewall is open for syslog.
ASKER
firewall status..on esxi 5.1
esxcli network firewall get
Default Action: DROP
Enabled: true
Loaded: true
how to check for syslog status in firewall?
esxcli network firewall get
Default Action: DROP
Enabled: true
Loaded: true
how to check for syslog status in firewall?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, this one i have already dy done and reloaded the syslog service as well
anything i have to check/configure
i can see Path shwoing for scratch/log is different on each host..is that soemthing we have to configure ?
i mean to check for remote data store where logs should be deliverd ?
anything i have to check/configure
i can see Path shwoing for scratch/log is different on each host..is that soemthing we have to configure ?
i mean to check for remote data store where logs should be deliverd ?
are the IP Addresses correct ?
scratch/log should not matter.
scratch/log should not matter.
Are you able to ping the syslog server? or telnet to the appropriate ports?
ASKER
Thanks
But please make sure you have these settings documented, in case you need to reapply them after the upgrade.